Static Sites Age Better Than Frameworks

The framework a five-year-old blog was built on is usually the first thing that has to be dragged forward before anything else can change. Dependency upgrades cascade, a plugin stops being maintained, and eventually a “quick post” turns into an afternoon fighting the build.

A static site sidesteps most of that by construction: the build step produces plain HTML, CSS and a handful of hashed assets, and what actually serves that output to a reader — CloudFront, S3 — barely changes release to release. The build tool can be swapped later without touching the hosting layer at all, because the contract between them is just files.

That’s the bet this project is making: keep the serving layer boring and stable, and let the parts that actually need to evolve — the editor, the scheduling, the search — live somewhere else entirely.