liveBook · Manning

Rendering model

As explained in Vanilla Web

A rendering model is an architectural scheme that determines where and when web-page content is generated.

A rendering model determines where and when a page’s content becomes HTML. Choose it after deciding how navigation works: a multi-page application can serve a different page at each URL, while a single-page application typically renders later views with client-side code. The two decisions can also be combined. section 2.1.4

Match the model to the content and its update needs:

  • Static site: ship HTML, CSS, and JavaScript files as written. The server only serves files; little JavaScript is needed. section 2.1.4
  • Static site generation (SSG): build pages from templates and content sources before deployment. The server serves the generated files. section 2.1.4
  • Server-side rendering (SSR): run server logic on each request to combine data with templates and return HTML. section 2.1.4
  • Client-side rendering: after an initial page load, client-side code renders subsequent sections and data, optionally fetching them over HTTP. section 2.1.4
Table 2.2 Rendering models cheat sheet
Rendering model What you code What you build and ship What the server does on request What the client does

Static Site

You code raw HTML, CSS, and JS files directly.

None – you ship the files as-is.

The server serves static files (no logic).

The browser renders HTML, applies CSS, and executes minimal JS.

SSG

You code templates + content sources (Markdown, DB, CMS).

A build step generates static HTML/JS/CSS files.

The server only serves the pre-generated files, similar to a Static Site.

The browser renders static pages, with optional JS for interactivity.

SSR

You code templates + server logic (PHP, Node, Python, etc.).

Optional pre-compilation of templates or code. Ship source code or compiled binaries.

On each request, the server queries the DB, merges data with templates, and outputs HTML.

The browser receives ready HTML and CSS, plus optional JS that enhances interactivity.

CSR

You code mostly JS + an HTML shell + API endpoints.

Optional tooling. Ship source code.

The server serves static files, similar to a Static Site, and also provides JSON endpoints.

The browser runs JS, manages the DOM, and fetches data via APIs.

Universal

You code with a framework whose code runs both client- and server-side (typically JS).

A build step produces server and client bundles. Ship both to a Node-capable host.

On each request, the server renders the initial HTML for the route.

The browser displays the server-rendered HTML, then hydrates it to take over interactivity.

ISR

You code templates + content sources with a framework that supports revalidation.

A build step pre-generates pages; you configure revalidation rules. Ship to a platform with a cache and runtime.

The server serves cached static HTML and regenerates pages in the background, on a schedule or on-demand.

The browser renders the pre-generated HTML, then optionally hydrates for interactivity.

Islands

You code mostly static templates + isolated interactive components, such as custom elements.

A build step outputs static HTML plus small, per-island JS bundles.

The server serves static HTML (like SSG), optionally rendering per request.

The browser renders the static HTML and hydrates only the islands independently – or resumes them, in Qwik’s case.

Compare what each model requires you to code and ship, and what happens on the server and in the browser. section 2.1.4

How Vanilla Web covers it

How deep it goes
Compares coding, build, server, and browser responsibilities without detailing a full implementation.
Examples
Uses simple websites, blogs, e-commerce sites, and newspapers to illustrate static sites and static site generation.
What it assumes
Assumes familiarity with HTML files and basic server–browser navigation; defines the architectural options from that starting point.
What you can do after
Evaluate/understand which rendering model fits a site’s content, updates, and server or browser responsibilities.
How it connects
Relates rendering choices to multi-page applications, single-page applications, routing, templates, and HTTP requests.

Related concepts

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