How mdiannibelli/javascript-dioneldev works
Project type and purpose
• This is not a running application but an open-source “exercise bank” of JavaScript problems organized by difficulty (facil, intermedio, dificil, teoria).
• Its purpose is to help learners practice JS by cloning the repo, opening an exercise in their editor (e.g., RunJS), and executing solutions interactively.
File structure
• At the root you have README.md plus four top-level folders:
• facil
• intermedio
• dificil
• teoria
• Each of those folders contains subfolders or files, each representing a single exercise or group of related exercises (e.g., “programacion-orientada-a-objetos”).
• There are no build scripts, no server code, no configs—just pure .js solutions.
README for additional insights
• The README confirms it’s a collection of solved JS exercises.
• It references RunJS as the chosen local execution environment.
• No external dependencies or runtime services are mentioned.
a. Main components:
• User (developer/learner)
• GitHub repository (source of truth)
• Local clone (developer machine)
• RunJS (JS execution environment)
• Exercise folders (facil, intermedio, dificil, teoria)
b. Relationships / interactions:
1. User → clones repo from → GitHub
2. Cloned repo → lives in → Local filesystem
3. User opens a specific exercise folder in an editor → code file
4. User runs code in → RunJS
c. Architectural patterns / principles:
• Purely hierarchical directory structure (no inter-module dependencies).
• Each exercise is an isolated module (single responsibility).
• Convention-over-configuration: folder name denotes difficulty, file name denotes problem.
d. Relevant technologies:
• Git/GitHub (version control)
• JavaScript (.js files)
• RunJS (local REPL / execution tool)
Detail
• That there is zero runtime coupling—each exercise is self-contained.
• Keep it simple—this is a static content repo, so the “system” is really the workflows and file organization.