Small sites should stay small

A personal website has no growth targets. No conversion funnel, no engagement dashboard, no quarterly review where someone asks why time-on-page dipped in March. It is, almost uniquely on the modern web, allowed to just be a place.

This is worth protecting, because the defaults all push the other way. Add analytics to see if anyone’s reading. Add a newsletter modal because that’s what sites do. Add a comment system, a like button, a related-posts widget trained on someone else’s engagement data. Each addition is small, and each one quietly imports the logic of scale into a place that didn’t need it.

The alternative is to let smallness be the design. A page of text, typeset with care, that loads instantly and asks nothing. A list of posts that fits on one screen because there are only nine of them, and nine is fine. The site doesn’t need to grow; it needs to be true — an accurate reflection of one person’s thinking, updated when there’s something to say.

There’s a practical payoff too. A small static site is nearly immortal. No database to migrate, no framework churn to chase, no dependency with a security advisory. Text files in, HTML out. You could leave it alone for five years and it would still work, which is more than can be said for most software.

But the real payoff isn’t practical. It’s that a small site stays legible to its owner. You know every page, every decision, every line of CSS, and why it’s there. On a web that keeps consolidating into a few enormous platforms, keeping one legible place that answers only to you is a quiet, stubborn act. Stay small.