HTML
posts (6)
- Frontend Rendering: from server-side pages to hybrid rendering14/17
Islands architecture: interactive fragments in a mostly static document
The starting point stops being the application. The page is a document, and only the fragments that truly need a client runtime get one.
- Frontend Rendering: from server-side pages to hybrid rendering10/17
Streaming SSR: stop waiting for the whole tree
The response stops being atomic. The server sends finished fragments and the slowest dependency no longer blocks the entire document.
- 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.
- Frontend Rendering: from server-side pages to hybrid rendering2/17
AJAX: the moment a page started behaving like an application
A request stopped meaning navigation. The browser keeps the current document alive and decides for itself what to do with the server's answer.
- Frontend Rendering: from server-side pages to hybrid rendering1/17
Server-rendered web: before the frontend became an application
The server assembled a full document for every request and the browser was a document renderer. A simple model, as long as the whole document could be the unit…