Static Site Generation (SSG)
Design Processes
Building every page of a site into finished HTML at deploy time.
In practice
Static site generation renders all pages once, when the site is built, and serves those files unchanged until the next build. There is no server work per visit, so pages are as fast as the network allows and cost almost nothing to host. The trade-off is freshness: content changes appear when you rebuild, unless you combine it with on-demand regeneration.
Questions
What is Static Site Generation (SSG)?
SSG is pre-rendering a site's pages to static HTML at build time, so every visitor receives the same finished files from a CDN.
Why do you use Static Site Generation (SSG)?
Nothing beats a file already on the edge for speed, cost or reliability.
How do you use/apply Static Site Generation (SSG)?
Point a static framework at your content, build, deploy the output to a host like Vercel or Netlify, and rebuild — or regenerate on demand — when content changes.
When do you use Static Site Generation (SSG)?
For content that changes less often than it is read: portfolios, docs, blogs, marketing.
Who uses Static Site Generation (SSG)?
Designers and developers building fast, low-maintenance sites.
