Next.js
posts (6)
- Frontend Rendering: from server-side pages to hybrid rendering17/17
Modern rendering is composition
Rendering stopped being a single stage. It is the placement of work across time, space and runtimes, and the framework is a consequence of those decisions.
- Frontend Rendering: from server-side pages to hybrid rendering11/17
Partial Prerendering: one page, several clocks
The route stops being the unit of decision. A static shell is produced earlier, dynamic fragments arrive at request time or through the stream.
- Frontend Rendering: from server-side pages to hybrid rendering9/17
Revalidation and ISR: static output that expires
ISR is not a separate rendering category but a cache with controlled inconsistency: precomputed HTML, expiration and regeneration.
- Frontend Rendering: from server-side pages to hybrid rendering7/17
SSG: rendering before the user exists
Build-time rendering trades request cost for build cost. You pay once, serve cheaply, and start having a data freshness problem.
- Frontend Rendering: from server-side pages to hybrid rendering5/17
SSR returns: the server renders HTML again
The server renders the first view not to make the frontend disappear, but to make content exist earlier. The rest of the cost stays on the client.
- series · 17 parts
Frontend Rendering: from server-side pages to hybrid rendering
A chronology of decisions about when, where and how the UI is produced: from a full document off the server to a composition of build, request, cache…