Why we still start with a static site
When a new client comes to us, the first question we ask is not which framework to use, but what actually changes on the site and how often. For most small businesses the answer is: opening hours, a price list, a few photos and occasional news.
What a database costs you
A database-backed CMS means updates, plugins, backups of two systems instead of one, and a larger attack surface. For a site that changes twice a month, that is a lot of moving parts.
What we do instead
We generate plain HTML from simple text files. Editing a price is a small change in a file; publishing is a single command. The result loads instantly, costs almost nothing to host and survives traffic spikes without effort.
When we do use a backend
Bookings, payments and anything with user accounts need a server. Even then we keep the public pages static and put the dynamic part behind a small, well-defined API.