Article
The Case for Smaller CSS Systems in Personal Sites
Why a restrained layer of custom CSS is often more useful than an elaborate styling stack for editorial work.
Personal sites do not need to win a contest for technical maximalism. They need to remain editable, expressive, and resilient over time. For that reason, smaller CSS systems often outperform more elaborate solutions in editorial projects.
Tokens before abstractions
The first useful layer is usually not a component library. It is a small set of variables for surface, text, border, accent, and spacing.
When those tokens are stable, pages can vary without falling apart visually.
Layout rules should be obvious
A shell, a reading column, a sidebar, and a few card variants may be enough for an entire publishing system. If every page type invents its own spacing and panel behavior, the site loses rhythm quickly.
Complexity should earn its place
There are valid reasons to adopt CSS-in-JS, utility frameworks, or design token pipelines. But editorial projects frequently end up paying for flexibility they never use.
Small systems are easier to revise
The design of a personal site evolves through taste. You revisit margins, color temperature, type scales, and how dense a page should feel. A smaller CSS system makes those revisions cheaper.
A note on elegance
Elegance is not the same as minimal code. It is the result of restraint in the right places and precision in the visible ones.
Conclusion
For personal publishing, the best CSS system is often the one that remains understandable after six months away from the codebase.