Loading content
Static Site Generation (SSG) is an architectural approach where pages are pre-rendered at build time into static HTML, CSS, and JavaScript assets. This yields fast, cacheable and low-attack-surface deployments without runtime server rendering. SSG is well suited for documentation, marketing sites and blogs with largely stable content.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Static Site Generation (SSG) produces pages as HTML and asset files during a build.
SSG emerged from the need to generate largely stable web content before a request and distribute it efficiently; templates and content are compiled into static files.
A build combines content and templates into finished pages. At runtime those files are served, with no per-request page rendering. This improves cacheability and reduces runtime complexity, but changes require a rebuild or revalidation. SSG describes generation; Static Site Hosting describes delivery of the resulting files.
Pages are generated from content and templates as static files before requests arrive.
The build moves rendering into preparation and produces cacheable artefacts.
Documentation, blogs and marketing sites fit well; highly personalized or constantly changing pages need additions.
SSG informs architecture choices about build time, runtime, caching and content freshness.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.