Essay · The craft
A smaller web
In praise of static pages, fewer dependencies, and sites you can still understand.
There is a particular pleasure in a website that is just a website. No build pipeline, no client-side router, no hydration step, no dependency tree deep enough to hide a small country. A few HTML files, a stylesheet, some images, and a server that knows how to send them. It is not a nostalgia project. It is a bet that the reader will still be there in ten years.
The cost of a dependency
Every dependency is a promise to maintain something you did not write. That is not an argument against dependencies; it is an argument for counting them. A library that saves a week of work and adds a monthly upgrade is a good trade. A library that saves an afternoon and adds a permanent surface area for security advisories is a worse one. The cost is not only in the bundle. It is in the attention.
Build tools are dependencies too. A pipeline that requires a specific version of a runtime, a lockfile, and a plugin ecosystem is a machine that must keep working for the site to exist. When it stops working, the site does not become slower; it becomes unbuildable. Static files do not have that problem.
Boring is a feature
A static site can be served by almost anything: nginx, a bucket, a tiny Go program, a CDN. It can be archived with a copy of the files. It can be read without JavaScript, indexed without a renderer, and opened from a USB stick. These are not exotic requirements. They are the definition of durability.
Boring does not mean primitive. It means choosing the smallest mechanism that solves the problem and then leaving it alone. The site can still be beautiful, fast, and accessible. It can still have a design system, a feed, and a search page built from a static index. What it cannot have is a hidden runtime that must succeed before the first word appears.
The best interface is one the reader never has to think about.
A site you can understand
There is a practical test for a small site: can one person hold the whole thing in their head? Can they open the directory, see every file, and explain what each one does? Can they change the color of a link without reading a framework’s documentation? If the answer is yes, the site is likely to survive its author’s attention span.
This is not only a matter of taste. Understandable systems are easier to secure, easier to migrate, and easier to hand over. They fail in obvious ways. They do not surprise you with a new rendering mode on a Tuesday. The constraint is a gift.
The reader
The reader does not care about the stack. They care about the words, the type, the speed, and whether the page respects their attention. A small site can give them all four: no cookie banner, no newsletter modal, no layout shift, no autoplay. Just the essay, the links, and a way to come back.
There is room for large applications and complex products. The web needs those too. But not every page needs to be an application, and not every essay needs a framework. Some things are better small.