Static implementation guide
SSG Cost Controls
Keep the origin predictable by removing request-time rendering, regeneration, remote data, image transforms, and polling.
Last updated 2026-08-31
Move work to the build
Every guide is generated from local validated data during the production build. There is no server-side props function, revalidation interval, API route, database, or content request when a visitor arrives. With fallback false, unsupported slugs fail as 404s instead of triggering on-demand generation.
This narrow design makes platform usage easier to interpret. Repeated guide requests should not steadily increase function invocations or regeneration activity. The origin serves a fixed build artifact, and the gateway experiment changes only whether that artifact is reused at the external rewrite layer.
Avoid unrelated metered features
The pages use CSS and inline decoration rather than optimized remote images or large media. They do not poll, personalize by cookie, authenticate users, or vary by geography. Those features can be valuable in products, but each would add request paths or cache dimensions that obscure this test.
Review observability after the run. Persistent function, ISR, data-cache, or image-transformation usage indicates that the implementation has drifted from the static contract. Stop the comparison and locate that work before drawing conclusions about rewrite caching.