liveBook · Manning

Prerendering

As explained in Fast by Default

Static site generation creates web pages ahead of requests so they can be served as pre-rendered HTML.

Static site generation creates HTML ahead of requests for content that rarely changes and does not vary by user. A CDN can serve these pre-rendered pages directly, eliminating server processing and making delivery faster than dynamic rendering. section 5.2.1

Use static generation when:

  • Content changes infrequently and remains the same for every visitor. section 5.2.1
  • Pages can be deployed as pre-rendered HTML and served through a CDN. section 5.2.1
  • Interactive behavior is limited to isolated elements such as search boxes or signup forms; add islands only where needed. section 5.2.1

Documentation site

A documentation or marketing site can generate its pages during deployment, publish the resulting HTML to a CDN, and avoid request-time server work. Astro, Hugo, and Next.js static export are named tooling options. section 5.2.1

How Fast by Default covers it

How deep it goes
Explains selection criteria and delivery benefits but stops short of build configuration or deployment procedures.
Examples
Uses documentation sites, marketing pages, search boxes, and signup forms as examples.
What you can do after
Apply it via Astro, Hugo, or Next.js static export for suitable pages.
How it connects
Connects static HTML generation with CDNs, dynamic rendering, and islands architecture.

Also explained in

Compare how 5 books explain prerendering →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fast by Default. The section links point to the parts of the book it draws on.