Static Rendering¶
Hallie, L., & Osmani, A. (2021). Static Rendering. Patterns.dev.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Decoupling Point
- In software architecture, the build-time/runtime split is the same structure, with the compiled artefact as the buffer — the upstream forecast is "what code will run," the downstream pull is "the specific user request" — and the choice between static site generation, server-side rendering, and client-side hydration is a choice of where on the flow to place the point.
This sourceTreats static rendering (build-time / SSG), server-side rendering (request-time), and client-side rendering / hydration as a spectrum of where work is placed relative to the request, with the explicit latency-versus-flexibility (TTFB, personalization, build cost) trade-off — the build-time/runtime positioning choice the marker invokes.
Supported in partVerified against the work's full text
Supports the build-time versus request-time rendering trade-offs among SSG, SSR and client-side hydration; the buffer and forecast/pull framing is the article's own.
“Static rendering — also called static site generation (SSG) — produces the HTML for every route at build time.”
- In software architecture, the build-time/runtime split is the same structure, with the compiled artefact as the buffer — the upstream forecast is "what code will run," the downstream pull is "the specific user request" — and the choice between static site generation, server-side rendering, and client-side hydration is a choice of where on the flow to place the point.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:bb9e902d0e42 · see in the full table