liveBook · Manning

Prerendering

Prerendering is the generation of web-page HTML before it is requested or served, typically as prebuilt files.

How 2 Manning books explain it

Modern Angular

Static site generation is the process of producing web pages as prebuilt files before deployment rather than generating them for each request.

How it is used
Uses build-time rendering for mostly static Angular pages that can be deployed and served without per-request generation.
How deep it goes
Explains route discovery, configuration, build output, deployment, and host fallbacks, while deferring server-specific configuration details.
Examples
Demonstrates an HRMS promotional site with about-us and subscriptions routes, generated browser artifacts, and an optional routes file.
What you can do after
Operate/configure Angular prerendering, build static HTML with ng build, and deploy the resulting browser artifacts.

Read how Modern Angular explains prerendering →

Pro Angular 16

Prerendering is the generation of an application's HTML documents before they are sent to browsers, before client-side JavaScript executes.

How it is used
Reduces the empty-screen wait during application startup by serving HTML while JavaScript downloads.
How deep it goes
Defines static route documents generated once, contrasts them with per-request SSR, and notes that snapshots miss later shared-state changes.
Examples
Demonstrates an Angular application prerendered with `npm run prerender`, served over HTTP, and tested with JavaScript disabled or a slow network.
What you can do after
Operate an Angular prerender workflow by generating static files and serving them with a separate HTTP server.

Read how Pro Angular 16 explains prerendering →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.