A Practical Guide to Static Websites
What a static website is, how it is generated and why pre-built pages remain useful.
What “static” means
A static website serves files that have already been created: HTML documents, stylesheets, scripts, images and other assets. The web server does not need to assemble each page from a database every time a visitor arrives.
“Static” describes how pages are delivered, not whether they can look modern. A static site can have responsive layouts, search, navigation, animations and interactive features. Those features can be implemented in the browser without requiring a server-side application.
Content and templates
Many static sites are written using a static site generator. Authors keep content in simple formats such as Markdown, while templates define the shared page structure. The generator combines the two and produces a directory of ordinary web files.
This separation is useful. A site-wide navigation change can be made in one template, while an individual article remains a separate content file. The final output can be inspected, copied, backed up and served by almost any web server.
Benefits
Static sites have a small operational footprint. They do not require a database or an application process to render each page. There are fewer moving parts to patch and monitor, and the generated output can be deployed to a basic web server or object storage service.
They are also easy to version. Content and configuration can live in Git, making it possible to review changes and return to an earlier version.
Trade-offs
A static site is not automatically the right choice for every project. Features that depend on private user data, frequent updates or complex transactions usually need a backend service. A static site can call external services, but doing so introduces dependencies and may require careful handling of credentials and privacy.
Content updates also require a build and deployment step. For a site that changes occasionally, this is often a reasonable trade-off.
A good fit
Documentation, portfolios, reference pages, project notes and small publications are natural candidates for static generation. The best design is usually the simplest one that meets the site's actual needs.