How tech-educators/software-dev-019 works
Project type and purpose
• This is an educational monorepo containing two top-level modules:
– “demos”: week-by-week code examples (pure HTML/CSS/JS front-end demos and later full-stack tutorials).
– “student-guides”: Markdown reference guides.
• Purpose: provide students with bite-sized front-end exercises (Weeks 1–3) and introduce build tools, server APIs, databases in Week 4, plus supplemental guides.
File structure
• Top-level directories:
– demos/ : subdivided by week (week-01, week-02, week-03, week-04).
– student-guides/ : collection of reference docs.
• Inside demos/week-XX:
– Weeks 1–3: each demo is a self-contained static HTML/CSS/JS folder.
– Week 4: some demos include a “client” (HTML + Vite/JS modules) and a “server” (Express.js, .js files, SQL or Supabase).
• No shared code between weeks—each demo is standalone.
• Build/config files appear only in Vite demos (package.json, .gitignore) and Node.js server demos.
Key insights from README
• No explicit architecture section—project is purely a teaching codebase.
• Emphasis on “demo code” and “useful guides.”
Detail
• Every layer: monorepo → module → runtime components.
• Don’t omit standalone static demos—they illustrate progressive curriculum.
• Avoid over-simplification: each demo is its own self-contained piece of the course.