Intent
Deliver content as static assets for reliability and low ops overhead.
When to use
- Content is read-only or changes on a schedule.
- You want minimal operational complexity.
- Performance and caching are important.
Core mechanics
- Pre-render pages from content.
- Deploy to a static host.
- Cache assets and ensure link integrity.
Implementation checklist
- Define content sources and build steps.
- Set up build and deploy pipeline.
- Add link checks or basic validation.
- Configure cache headers.
- Document release steps.
Failure modes and mitigations
- Stale builds -> enforce builds on content changes.
- Broken links -> add link checking.
- Missing assets -> validate build output.
Observability and validation
- Build logs and deploy status.
- Link check results.
Artifacts
- Build output and sitemap.
- Release checklist.