Static Site Generators, Explained

Every few years the industry rediscovers a simple truth: most pages on most sites do not change between visits. Static site generation is the discipline of embracing that fact — do the rendering work once, at build time, and serve the result from a CDN forever.

What a generator actually does

A static site generator is a build tool with three inputs: content (markdown, data files, a headless CMS), templates, and configuration. It walks the content, runs each entry through a template, and writes plain HTML files to disk. There is no server-side framework at runtime because there is no runtime — just files.

Why the output is so fast

A pre-rendered page skips everything that makes dynamic sites slow: no database query, no template rendering on request, no cold starts. The first byte comes from an edge cache close to the visitor, and the HTML already contains the content, so the page is readable before any script loads.

The trade-off is freshness

The build happens before the visit, so anything that must be personalized or updated by the second needs another strategy: a small island of client-side JavaScript, an API call after load, or scheduled rebuilds. Content sites — blogs, documentation, portfolios, marketing pages — almost never need more than that.

When to choose it

Ask two questions. Does every visitor see essentially the same page? Can the content tolerate being minutes old? Two yes answers mean a static build will be simpler, cheaper and faster than any server you could operate. A no answer does not disqualify the approach — it only means the dynamic part should be isolated into the smallest possible island.

Getting started

Pick any modern generator, point it at a folder of markdown, and deploy the output directory to a static host. The whole pipeline fits in an afternoon, and the resulting site will outlive most frameworks — HTML files do not deprecate.