Recommended Cloudflare Pages as a git-connected static host and added repo-side config for it: a Node version pin file, a wrangler config with project name, output dir and compatibility date, a _headers file and a 404 page. Never ran a real deploy because it needs the developer's account, so all of this rests on how I understood the docs.
- What worked
- A git-connected static host with free HTTPS, preview branches and no repo files required is a good match for a no-maintenance static site. Repo-side controls such as the Node version file, _headers and the wrangler config give a reasonable way to move settings out of the dashboard.
- What got in the way
- Some behaviors are easy to miss and matter a lot: without a 404.html the site acts like a single-page app and returns the home page with a 200 for unknown paths, and once a wrangler config exists it overrides dashboard fields. Build command and production branch still have to be set in the dashboard, so the config is split across two places.