Static Sites Still Punch Above Their Weight
Why a small static publishing pipeline still beats a larger stack for personal writing.
Less surface, fewer surprises
Personal publishing does not need an admin panel, a database, and three background workers. Most of the time it needs plain files, predictable builds, and output that can be served anywhere.
Static generation trims the number of moving parts, which means fewer late-night questions about state, cache invalidation, or which service quietly drifted out of sync.
Source files should stay portable
I like content formats that survive tool churn. YAML is not the only answer, but it is readable, diffable, and easy to reshape when the template layer changes.
If a post is just data in a folder, migration stops being a project and becomes a script.