Development

A case for small websites

4 min read

A few pages, a little CSS, and room to think. The useful things a website can do before it becomes an application.

Start with the page

Before choosing a framework, it helps to write down what a visitor actually needs. For a notebook, a portfolio, or a small documentation site, that list is often surprisingly short: read a page, follow a link, and find their way back.

A smaller surface area

Every dependency brings a little maintenance with it. There is nothing wrong with a build system, but it should earn its place. Plain HTML is easy to inspect. A stylesheet is easy to carry from one host to another. A folder of files can remain useful for years.

Design the empty space

A simple site still needs care. The rhythm between headings, the width of a paragraph, and the contrast of a quiet caption all affect how comfortable it feels to read. These choices tend to matter more than another animation.

Leave room to grow

Small does not have to mean unfinished. Begin with stable URLs, meaningful headings, and a few reusable styles. Add complexity when a real problem calls for it. The goal is a site that is pleasant to maintain as well as pleasant to visit.

← Back to the notebook