Reading paths overview
Status: 🟩 COMPLETE Last updated: 2026-06-19 Plain-English tagline: The 7 curated journeys through the encyclopedia — pick the path that matches your current goal, follow numbered stops in order, and finish with a real mental model rather than scattered fragments.
In plain English
The encyclopedia has ~180 🟩 COMPLETE entries across 16 sections (plus glossary, how-tos, cheat sheets, common-errors references, decision frameworks, and gotchas). Reading random-walk works, but a guided sequence works better — especially for a specific goal.
That’s what reading paths are. Each one is a CURATED LIST of entries, ordered to build understanding step by step. Each “stop” along the way says:
- Why you’re here — what this stop adds to your understanding
- Read — which entries to read (often 1-3 per stop)
- Anchor concept — the one takeaway worth keeping
Paths are pedagogy, not new content. They route you through existing entries in the right order, with structure that makes the path coherent.
8 paths exist (7 goal-oriented + 1 case-study):
| Path | For someone who wants to… | Stops |
|---|---|---|
| Absolute beginner đźź© | Understand what all of this is, starting from zero | 20 |
| I want to build my first webapp đźź© | Go from idea to a deployed Next.js + Supabase app | 30 |
| LLMs đźź© | Grasp what LLMs are and how to use them well | ~25 |
| I want to master Claude Code đźź© | Get the most out of the CLI agent day-to-day | ~25 |
| I want to understand the deploy pipeline 🟩 | Follow code from git commit to “live on the internet” | 15 |
| I want to make my app secure đźź© | The minimum security baseline every webapp needs | 15 |
| I want to learn just the lingo đźź© | Speed-run the glossary to be conversationally fluent | 50 terms |
| Bible Quest origin walkthrough đźź© | See how the playbook came together in a real project | 8 phases |
Why use a reading path
The honest comparison:
| Approach | Best for |
|---|---|
| Random walk | Curiosity-driven exploration; not pursuing a specific goal |
| Targeted lookup (glossary/index) | Answer a specific question right now |
| Reading path | Build a structured mental model for a real goal |
| Section deep dive | Master one topic comprehensively |
Reading paths sit in the sweet spot for “I want to UNDERSTAND THIS WHOLE THING but don’t know where to start.”
How to use a path effectively
A few practical tips:
-
Pick ONE path at a time. Switching paths breaks momentum. Finish one (or get bored of it) before starting another.
-
Pace yourself. Most paths suggest 2-4 stops per sitting. The Absolute Beginner path could be 10 days at 2 stops/day. Don’t try to one-shot it.
-
Read the anchor concepts even if you skip entries. The “this is the one thing worth keeping” line in each stop preserves the value even if you don’t read deeply.
-
Follow links freely. A stop says “read X.” X mentions Y. Going down a rabbit hole on Y is fine — that’s how the network works.
-
Skip stops that don’t apply. If you already know HTML and the stop is “Read HTML,” skip ahead. The path is a guide, not a contract.
-
Use the section indexes as a back-reference. Each section has its own index (
01-foundations/index.mdetc.) listing every entry. If a path mentions something not on the path, you can find it via the section. -
Cross-link with how-tos. Most paths mention specific how-tos at relevant moments. Use them to PRACTICE concepts you’ve just learned.
When you finish a path
Two things happen:
- You can explain the topic to someone else in plain English
- You know where to look for any specific detail (because you’ve seen the map)
The encyclopedia is then no longer a stranger; it’s a map you can navigate. From there:
- Pick another path for a different goal
- Deep-dive a section that interested you
- Build something that uses what you learned
The “build something” part is the conversion. Paths give knowledge; building consolidates it.
What’s NOT a reading path
Some things are explicitly NOT paths:
- The glossary — A-Z definitions, not a learning sequence
- A section index — lists entries in topic order, not pedagogical order
- Random reading — wherever curiosity takes you
These are all valuable; they’re just different.
When to write a NEW reading path
If you find yourself wishing one existed:
- Start with the goal. “Someone who wants to ___” — concrete, specific
- List the entries that matter for that goal
- Sequence them by what’s foundational vs. dependent
- Group into stages of 3-5 stops each
- Write each stop’s “why” + “anchor concept”
Then add it to index.md and submit (or just commit, if it’s your encyclopedia).
For Bible Quest specifically: the 8 existing paths cover what George has wanted so far (the 7 goal-oriented paths + the Bible Quest origin case-study walkthrough). New ones would emerge if a new pursuit appeared (e.g., “I want to add monetization” → a new path).
See also
- Reading paths index — the 7 paths in detail
- How to navigate 🟩 — the broader navigation strategies
- Status labels explained 🟩 — what badges in paths mean
- How this evolves đźź©
- INDEX — master index
- CONVENTIONS — how entries are written
Sources
- This entry is meta. No external sources.