0 of 29 chapters written · 3 levels planned
Next.js
Routing, rendering, the server
Not written yet
App router, server vs client components, caching layers, and the rendering strategy behind each page. Beginner through advanced, laid out the same way as the rest of the shelf.
The plan
- chapters planned
- 29
- levels
- 3
- chapters written
- 0
What is planned, level by level
Every stop below is an outline for now. Open one to see what it will cover.
Beginner
“I can build a working site.”
8 sections
- soon
- soon
- soon
- soon
- soon
Intermediate
“I understand the server/client boundary.”
11 sections
- soon
- soon
- soon
- soon
Advanced
“I can reason about the cache layers.”
10 sections
- soon
- soon
- soon
Meanwhile
Nothing here is written yet, but these are.
Three honest notes
The server/client component boundary shows up right after routing on purpose — almost every other intermediate topic (data fetching, server actions, middleware) assumes you already know which side of it you're on.
Next's caching model is famously confusing because it's four separate caches stacked on each other — it gets its own advanced chapter instead of being folded into data fetching.
Deployment and the edge runtime sit at the end of advanced because they're where every earlier decision (rendering strategy, caching, middleware) actually gets tested.