Week 23 • Day 1Week 23
Day 1:Designing the Public Learning Platform Architecture
Battle-tested daily lesson note • 100% runnable code, interview Q&A, test suite & interactive quiz
Day 1: Designing the Public Learning Platform Architecture
1. System Vision & Architecture
Building a public platform for a 6-month, 24-week, 168-lesson curriculum requires a clean, scalable architectural design:
- Zero Content Duplication: The repository itself (
d:\Spark\AI_Engineer) is the single source of truth. Every markdown guide, source code file, and test suite is rendered dynamically. - Dynamic Filesystem Crawling: As new weeks, days, or capstones are created, the platform automatically discovers, validates, and indexes them without requiring code edits to the frontend.
- RESTful Slug Routing: Clean, semantic URLs for bookmarks, search engines, and social sharing:
/curriculum-> Master 6-Month Roadmap/weeks/week21-> Weekly Architectural Overview/lessons/week21-day03-lora-matrix-math-> Daily Interactive Lesson/flashcards-> Filterable Senior Interview Cards/troubleshooting-> Real-World Production Bugs & Postmortems
Architecture Flow Diagram
weekXX_topic/
dayYY_subtopic/
README.md (Theory & Walkthrough)
src/ (Production Python Code)
tests/ (Automated Pytest Tests)
interview_questions.md (Beginner/Intermediate/Senior)
D->R & S & T & I
Filesystem Scanner (Crawls REPO_ROOT)
Metadata Validator & Slug Canonicalizer
CurriculumManifest (In-Memory Fast Index)
VALID->MANIFEST
GET /api/curriculum/manifest
GET /api/lessons/{slug}
GET /api/flashcards?seniority=senior
2. The Curriculum Manifest Data Schema
The platform relies on a typed hierarchical manifest schema:
DayLessonMeta:day_number,title,slug,readme_path,src_files,test_files,has_interview_questions.WeekMeta:week_number,title,overview_path,days: List[DayLessonMeta].MonthMeta:month_number,theme,weeks: List[WeekMeta],capstone_project.CurriculumManifest: Total counts, completion percentages, search index, and slug lookup table.
In Simple English: Structuring a Scalable Learning Website (Curriculum Architecture)
Look at why great technical websites (like this very AI platform!) separate Content (data/*.js) from UI Components (RoadmapClient.jsx):
- Every day has a clean stable
slug/id, structured Theory Markdown, Runnable Code Tabs, Interview Questions, and Self-Check Quizzes. - Adding a new lesson or fixing a typo requires editing data cleanly — never touching React layout code — while allowing instant static pre-rendering (SEO-crawlable HTML) across Google and Bing!