Static is a strategy,
not a shortcut.

This practice spent two days moving portfolio properties off a shared WordPress server onto static hosting. The reflexive read is that static is a cost cut. It is the opposite: it is a strategy about what a website owes its owner.

A static site has no admin login to brute-force, no plugin that stops being maintained, no database that corrupts quietly. Its failure mode is a flat file, and its recovery is a redeploy. The sites we shipped this week kept every video, every post, and every legacy URL — while their hosting surface shrank to files on a CDN.

Static is not right for everything. Anything that stores visitor data, takes payments, or changes by the minute wants a real application. But the majority of the small web is content that changes rarely and matters constantly — and for that, the static decision is a strategy about ownership: the site becomes files you can read, back up on a napkin, and host anywhere.

This essay concerns the practice's own migrations. Your project's constraints may differ; that is what the discovery step is for.