Structured Syllabus
Published Jul 4, 2026
Every lesson in Praxis924 lives inside a clear, three-level hierarchy: Technology → Framework → Lesson. That structure isn't decoration — it's how you always know where you are and what comes next. This walkthrough is for learners who want to browse the curriculum, read published lessons, and follow a coherent path from basics to advanced without getting lost. You don't even need an account to start.
What you'll need
Nothing, to browse. Published lessons are visible at /learn without logging in — you can read the full curriculum as a guest. You'll only need an account (register with email verification) when you want to practice, track progress, chat with Lucy, or run a mock interview. So: open the app, go to /learn, and read on.
How the hierarchy works
Think of it as three nested shelves:
| Level | What it is | Example |
|---|---|---|
| Technology | The broad subject | "Python" |
| Framework | A focused area within it | "Async Python" |
Lesson (ContentItem) | A single, self-contained unit | "Coroutines and await" |
A lesson is never a wall of text. Each one is built from four sections — main_explanation, practical_explanation, key_principles, and summary — plus a set of exercises. Every section is AI-reviewed and scored before it's allowed to ship, so what you read has already passed a quality bar.
Crucially, lessons within a framework are ordered basics → advanced. The syllabus is designed as a deliberate progression, not an alphabetical dump, so reading top-to-bottom is the recommended learning path.
Step 1 — Open the library
Go to /learn. You'll land in the browse view, organised by Technology. Pick the technology you care about, then drill into a Framework to see its ordered list of lessons. Only lessons with publish status published appear here — drafts and half-generated content stay hidden in the admin console, so everything you see is finished and reviewable.
Step 2 — Start at the top of a framework
Because lessons run basics → advanced, the first lesson in a framework is your entry point. You don't have to guess the sequence — the ordering is the sequence. Open the first lesson to enter the focused lesson viewer.
Step 3 — Read in the focused viewer
The lesson viewer is a single-column, distraction-light reading surface. It renders the four sections in order, with Sources cited inline where the lesson was grounded in a dataset (so you can trust and trace the material). A collapsible chapter rail lets you jump between sections or across the framework's timeline. Read main_explanation for the concept, practical_explanation for how it's applied, key_principles for what to remember, and summary to consolidate.
Tip: Use the chapter rail as a map. It shows the whole framework's ordered lessons, so you can always see what you've covered and what comes next — the "what's next?" question answers itself.
Step 4 — Move from reading to doing
Reading is only half of it. When you're ready to apply a lesson, head to the practice workspace at /practice/[lessonId], where the lesson's exercises live — mcq, fill_blank, and calculation types, plus a coding challenge graded in a real sandbox with line-level feedback. Practice is login-gated, so this is the point where an account pays off: your progress (completion, accuracy, streak) starts tracking, and a spaced-review schedule will resurface lessons at the right time.
Step 5 — Ask when you're stuck
If a section doesn't click, open Lucy, the AI teacher, from within the lesson. When launched from a lesson, Lucy folds that lesson's own content into her context, so her answers cite the material you're actually reading instead of drifting into generic explanations. It's the fastest way to unblock without leaving the page.
When it goes wrong
Most "problems" here are really just the hierarchy doing its job — hiding things that aren't ready.
| Symptom | Likely cause | What to do |
|---|---|---|
A lesson you expected isn't in /learn | It's still draft or not yet generated | Only published lessons show publicly; wait for an admin to publish it |
| Lessons feel out of order | You're jumping around | Follow the framework's built-in basics→advanced order |
| A section looks thin or generic | Grounding source was limited | Check the inline Sources; Lucy can expand on it |
| Practice or progress won't load | You're browsing as a guest | Register and verify your email, then open /practice/[lessonId] |
Note: A framework can be published incrementally. If early lessons are live but later ones aren't yet, that's expected — the syllabus grows lesson by lesson as each one is generated and reviewed.
What you get
By using the hierarchy the way it's designed, you get a self-navigating curriculum: Technology → Framework → Lesson tells you exactly where you are, the basics→advanced ordering tells you where to go next, and the four-section structure means every lesson teaches, demonstrates, distils, and summarises the same way. Browse freely as a guest to evaluate the material; sign in when you want practice, progress tracking, spaced review, and Lucy on your side.
Next: pick one framework, read its first three lessons end to end, then open /practice/[lessonId] on the first one and take the coding challenge. That single loop — read, practice, get graded — is the whole platform in miniature.