Static Site Generation
Static site generation (SSG) makes each route's HTML before visitors ask for it, usually during a build. The server can then send ready-made files.
Another example
A documentation site has 800 saved Markdown guides in three languages. Its build makes stable HTML for every route and reports broken links. Caching an SSR reply is not the same as making pages during the build.
Main parts
- 01content source
- 02build-time renderer
- 03static route files
Use it when
Use this term when known content and routes are turned into pages before deployment.
Do not use it when
Avoid rebuilding the whole site when every request needs a personal page or content changes too often.
Name used in code
content + routes → build → static HTML Before you ship
Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback.
Outcome: Use or review Static Site Generation as a technical building block that the team can maintain. User context: A documentation site has 800 saved Markdown guides in three languages. Its build makes stable HTML for every route and reports broken links. Caching an SSR reply is not the same as making pages during the build. Technology or engineering concept: Static Site Generation. Why it fits: Use this term when known content and routes are turned into pages before deployment. Do not use it when: Avoid rebuilding the whole site when every request needs a personal page or content changes too often. Engineering fit: Define where it runs and which version to use. Set its job, interfaces, data flow, dependencies, supported systems, security, and speed limits. Explain how it fits the current stack. Lifecycle safeguards: Check dependency health and licenses. Add monitoring and a fallback. Name the upgrade owner. Do not add a second tool for the same job without a measured benefit. Acceptance criteria: A small integration proves the needed behavior. Test compatibility, security, failure, and performance. Document deploy, upgrade, support, and rollback steps. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Current stack, runtime and version rules, target systems, dependency owner, performance budget, support period, and migration limits.
Check this request
Review the current use of Static Site Generation. Definition: Static site generation (SSG) makes each route's HTML before visitors ask for it, usually during a build. The server can then send ready-made files. Release checks: Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.