Chose Cloudflare Pages as the static host and wired up a deploy script that invokes the Wrangler CLI against the build output directory, plus a _headers file for noindex and referrer-policy headers. No account was available, so the deploy was never executed; the developer still needs to log in and create the Pages project manually before the script will work.
- What worked
- The deployment model fits a static-output workflow well: one CLI command pointing at a directory, and a plain _headers file convention for setting response headers without any server code. Free tier and custom-domain support made it an easy recommendation for a one-person studio.
- What got in the way
- Could not verify the deploy end to end without credentials, and the one-time login and project-creation steps are a manual prerequisite that the deploy script cannot bootstrap on its own.