Next.js in Practice · Part 2013 min read
Rendering Strategies - A Decision Map
How to choose between SSG, ISR, SSR, PPR, CSR and a full SPA in Next.js 16, and how the build decides on its own whether a route is static, partial or dynamic.
Archive
#rendering
8 notes match these filters
- Next.js in Practice · Part 2312 min read
PPR - Partial Prerendering with Cache Components
How Partial Prerendering works in Next.js 16 with Cache Components, from detecting dynamic access in the prerender to the postponed state and the resume render, and how to design pages for it.
- Next.js in Practice · Part 229 min read
SSR - Rendering Per Request
When and how a Next.js 16 page renders on every request, what the server does for that request, and how per-request rendering differs with and without Cache Components.
- Next.js in Practice · Part 2111 min read
SSG and ISR - Static Pages and generateStaticParams
Build static pages and keep them fresh in Next.js 16, with generateStaticParams, time-based and on-demand ISR, in both the Cache Components and the legacy model.
- Next.js in Practice · Part 2413 min read
CSR - Client-Rendered Islands
How to render parts of an App Router page only in the browser, from fetch-on-mount and client data libraries to next/dynamic with ssr false and React's browser() bailout, and how Next.js 16.4.3 implements each one.
- Next.js in Practice · Part 2513 min read
Fully Client-Side - SPA and Static Export
How output 'export' turns a Next.js 16.4.3 App Router app into static files, what the exporter checks and refuses, how client navigation works without a server, and how to build a true single-page app shell on top of it.
- How React Works · Part 129 min read
A Click, Start to Finish
One click on "Add" in the shopping list app, followed from the root listener through batched sync updates, rendering, keyed reconciliation and the commit to the moment the new item is painted.
- How React Works · Part 037 min read
What Rendering Really Means
Rendering is React calling your components to get a fresh description of the UI; it happens for four reasons, may run more than once or be thrown away, and does not by itself change the DOM.