Roadmap
The live status of the encyclopedia. Updated whenever I (with Claude) ship a meaningful change.
For status meanings (🟥 STUB / 🟨 DRAFT / 🟩 COMPLETE / 🟦 LIVING), see CONVENTIONS.md.
Status at a glance
| Section | Stub | Draft | Complete | Living | Total planned |
|---|---|---|---|---|---|
| 00. How to use | 0 | 0 | 4 | 0 | 4 |
| 01. Foundations | 0 | 0 | 9 | 0 | 9 |
| 02. Frontend | 0 | 0 | 14 | 1 (Next.js) | 15 |
| 03. Backend | 0 | 0 | 7 | 2 (Node.js, Server actions) | 9 |
| 04. Databases | 0 | 0 | 11 | 2 (Supabase, Postgres) | 11 |
| 05. Version control | 1 | 0 | 7 | 0 | 8 |
| 06. Hosting & deployment | 0 | 0 | 7 | 3 (Vercel, Netlify, Cloudflare) | 10 |
| 07. Security & auth | 0 | 0 | 11 | 1 (OWASP) | 11 |
| 08. Testing & quality | 0 | 0 | 6 | 1 (Code review) | 7 |
| 09. Tooling & dev environment | 0 | 0 | 4 | 4 (Node.js runtime, VS Code, Terminals, Claude Code overview) | 8 |
| 10. AI & LLMs | 0 | 0 | 14 | 3 (Claude models, MCP, Multimodal) | 14 |
| 11. AI-assisted development | 0 | 0 | 9 | 6 | 9 |
| 12. CS foundations | 0 | 0 | 6 | 0 | 6 |
| 13. Networking essentials | 0 | 0 | 7 | 0 | 7 |
| 14. Design & UX | 0 | 0 | 6 | 0 | 6 |
| 15. Broader tech bonus | 0 | 0 | 2 | 4 (Cloud, Mobile, Low-code, Game dev) | 6 |
| Glossary | ~30 starter terms | 0 | 1 (JWT) | 0 | ongoing |
| How-to | 0 | 0 | 12 (all originally planned guides shipped) | 0 | 12 done |
| Gotchas & tips | 10 | 0 | 0 | 0 | grows as I learn |
| Reading paths | 0 | 0 | 8 (7 planned + 1 bonus case-study) | 0 | 8 done |
| Cheat sheets | 0 | 0 | 6 (Git, npm, Vercel CLI, gh CLI, Supabase CLI, PowerShell) + index | 3 (Vercel CLI, gh CLI, Supabase CLI) | 6 done — natural completion |
| Common errors | 0 | 0 | 11 (build, Git, Supabase, browser, TypeScript, Vercel runtime, Node, OAuth, CSS/Tailwind, CI, performance) + index | 2 (Supabase, Vercel runtime) | 11 done — natural completion |
| Decision frameworks | 0 | 0 | 12 (Server/Client, merge/rebase/squash, RLS/server, custom-auth, tiers, TS strict, styling, tests, refactor, fetch/actions, self-host/SaaS, monorepo) + index | 1 (free/paid) | 12 done — natural completion |
| AI landscape (new) | ~150 vendor stubs | 0 | 6 (index, Western recommended, Chinese avoid, which-ai-for-which-job, privacy-and-data-training, how-to-access-us-ai-from-AUS) | 6 LIVING | active build-out (Phase A complete) |
What’s next (priority order)
This is the proposed order in which we deepen entries from 🟥 STUB to 🟨 DRAFT or 🟩 COMPLETE. It’s just a suggestion — happy to reshuffle based on what comes up in real work.
Phase A — the “I need this to read every other section” tier
Phase B — the day-to-day stack
- Git basics
- HTML ✅ COMPLETE
- CSS
- JavaScript
- TypeScript
- React
- Next.js ✅ COMPLETE (🟦 LIVING)
- Tailwind
- What is a database?
- Postgres
- Supabase ✅ COMPLETE (🟦 LIVING)
- Row-Level Security (RLS)
Phase C — hosting it
- Domains and DNS
- Vercel ✅ COMPLETE (🟦 LIVING)
- Environment variables
- Deploy a Next.js app to Vercel ✅ COMPLETE
Phase D — keeping it safe
- Authentication vs authorization
- Passwords and hashing
- Sessions and cookies
- JWT (currently glossary only)
- OWASP top 10
- Secrets management
Phase E — AI literacy
- What is an LLM?
- How LLMs work
- Tokens and context windows
- Prompt engineering
- Tool use
- Agents
- MCP — Model Context Protocol
- RAG — Retrieval Augmented Generation
Phase F — Claude Code mastery
Phase G — fill in the rest
Whatever stub looks most useful at the time.
How priorities get reshuffled
- If something blocks current work, jump the queue.
- If I encounter something new in a session, write at least a 🟨 DRAFT for it immediately.
- If a tool/service materially changes (e.g. Next.js 17 release), mark related entries 🟦 LIVING and refresh.