When a Database Still Belongs

Say the exception out loud

A large newsroom with minute-by-minute publishing, a product with complex permissions, or a dataset that changes faster than a build can be a bad fit for a purely static render.

We would rather name that than stretch a static site into a poor application server.

Hybrid is usually enough

The marketing pages, guides, and location pages can be static while a booking tool, store, or member area remains a separate system. The homepage does not need to be PHP because checkout exists.

That split is how Anchorage Press and commerce projects stay fast in public and capable where the account system is required.

WordPress is a choice, not a habit

If a team truly has the editors, the hosting discipline, and the plugin restraint, WordPress can remain the CMS behind a cleaner frontend. That is a decision with a cost, not the starting assumption.

The future default is still the static site, adopted unless the exception is real.