A studio site has two different needs: public pages must be fast and simple, but work and notes must be editable without a redeploy. This project uses a hybrid architecture: the public layer stays as static as possible, and only the parts that truly need live data are rendered on the server.
What stays static
Fonts, CSS, images and public files are served from the assets layer. Pages are built from a shared data layer, and each request reads only the content it needs from D1.
Why a server became necessary
Managing work, notes and contact settings without an admin panel was not possible. When content changes in the panel, request-time rendering means the change is visible immediately, with no manual build and deploy.
The costs
Server rendering means every HTML request reaches the Worker. For a site this size the cost is small, but caching, monitoring and failure paths must be designed from the start. The rule is simple: static where possible, dynamic where necessary.