Reading paths
Curated journeys through the encyclopedia for specific goals. If you don’t know where to start, pick the path that matches what you want to do.
Planned paths
| Path | Status | For someone who wants to… |
|---|---|---|
| Absolute beginner | 🟩 COMPLETE | Understand what all of this is, starting from zero |
| I want to build my first webapp | 🟩 COMPLETE | Go from idea to a deployed Next.js + Supabase app |
| LLMs | 🟩 COMPLETE | Grasp what LLMs are and how to use them well |
| I want to master Claude Code | 🟩 COMPLETE | Get the most out of the CLI agent day-to-day |
| I want to understand the deploy pipeline | 🟩 COMPLETE | Follow code from git commit to “live on the internet” |
| I want to make my app secure | 🟩 COMPLETE | The minimum security baseline every webapp needs |
| I want to learn just the lingo | 🟩 COMPLETE | Speed-run the glossary to be conversationally fluent |
Case-study paths (bonus)
A different shape from the goal-oriented paths above: an actual project, walked through phase by phase, with the encyclopedia entries that explain each piece. Reading these is both a tour of how it all comes together in practice and a stress-test of the encyclopedia’s coverage.
| Path | Status | What it is |
|---|---|---|
| Bible Quest origin — an annotated walkthrough | 🟩 COMPLETE | The full St Mark’s Bible Quest build, May 7–17 2026, phase by phase, linked to every relevant entry |
What a reading path looks like
A reading path is just a numbered list of entries with a one-line note explaining why each one comes next. It’s not new content — it’s a curated trail through existing content.
Example:
## Path: I want to build my first webapp
1. [What is the web?](../01-foundations/how-the-web-works.md) — the basic mental model.
2. [Client vs server](../01-foundations/client-vs-server.md) — the foundational split.
3. [HTML](../02-frontend/html.md) — the structure.
4. ...