liveBook · Manning

Static site

As explained in Vanilla Web

A website whose pages are served as prebuilt files rather than assembled by application code for each visitor request.

A static site is a practical choice for a small website whose content changes infrequently. You write the HTML, CSS, and any JavaScript directly, then ship those files as-is. On each request, the server serves files rather than running application code to assemble a page. section 2.1.4

A static site needs no build step and typically uses little JavaScript. Static site generation reaches a similar deployment result by building files from templates and content sources first; server-side rendering instead generates HTML when a visitor requests it. 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 rendering model codes, ships, and does when a page is requested. section 2.1.4

How Vanilla Web covers it

How deep it goes
Defines the files shipped and the server’s role, but provides no deployment procedure.
Examples
Uses simple, infrequently updated websites as the concrete case.
What it assumes
Assumes familiarity with authoring HTML and CSS; requires no build step or server-side execution.
What you can do after
Evaluate/understand it as an option when directly authored files and a file-serving web server meet a site’s needs.
How it connects
Contrasts static site generation and server-side rendering by their build steps and request-time behavior.

Also explained in

Compare how 3 books explain static site →

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.