The Next.js half of munakalati. Next 16.2.4, React 19.2.4, App Router, Tailwind 4 — a content site where nearly everything is a Server Component and almost no JavaScript ships.
- 01 — App Router Structure — [Beginner → Intermediate] — route groups vs private folders vs dynamic segments vs optional catch-all,
_resourcesas the way to park a finished feature, whynot-found.tsxrepeats the chrome, where the"use client"boundary sits, Tailwind 4@themetokens - 02 — Data Fetching, ISR and Caching ⭐ — [Intermediate] — what
revalidate = 60actually does, stacked caches compose their staleness,Promise.allvs a genuine data dependency, eleven fetches on one page, thegenerateStaticParams20-post cap,params/searchParamsare Promises in Next 16 - 03 — Rendering CMS Content: The Fallback Pattern ⭐ — [Intermediate] — the view-model adapter that makes JSX source-agnostic, why an empty array is truthy, the safety net hides the fall, and the
cms/duplication a finished migration left behind
The three things to take away
Sequential awaits on independent data is the most common Server Component performance bug, and nothing about the code looks wrong.
A fallback that renders perfectly when the CMS query breaks is worse than a crash. Log when it fires.
A migration scaffold needs a demolition date. Nine components exist twice, and the dead half still compiles.
Related
- General: Next.js · rendering · state and data
- 03 — Sanity — where the data comes from
- interview: Next.js and rendering
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering