A multi-page application (MPA) gives different sections of a site or application different server URLs. Moving between sections makes a new browser navigation. The server can respond with a static HTML file or generate the page dynamically. section 2.1.4
Choose this navigation model separately from the rendering model. Unlike an MPA, a single-page application (SPA) typically loads one entry page, then handles later navigation through client-side routing without reloading the page context. Neither model requires an all-or-nothing choice: static sections can use MPA navigation while one area operates as an SPA. 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 static sites, static site generation, and server-side rendering as ways to produce pages after choosing a navigation model. section 2.1.4

