Hosting sites quickly and elegantly with Cloudflare Workers

# Brief: build and deploy my website to Cloudflare Workers

You are setting up a brand-new static website for me and deploying it to
Cloudflare Workers on a custom domain. Do the whole thing: scaffold, build,
repo, deploy pipeline, first deploy, and verification.

I am not going to hand-edit config files. Ask me questions when you need a
decision, otherwise make sensible choices and tell me what you picked.

---

## What the site is

<<< REPLACE THIS with a few sentences about your site: what it is, what pages
you want, and roughly how it should look. Plain English is fine. If you have a
site you like the look of, name it. >>>

**Domain I want it on:** <<< e.g. jonexample.com or www.jonexample.com >>>

---

## Ground rules

- **Static only.** No server code, no database, no user accounts, no comment
  system, no contact form that stores anything. If something I asked for needs
  a server, stop and tell me before building a workaround.
- **No secrets in the repo.** Ever. If something needs a key, it goes in GitHub
  Actions secrets.
- **No asset over 25 MiB.** Cloudflare rejects the deploy. Check the built
  output before deploying and tell me if anything is close.
- **Cheap by default.** Don't add paid services. Don't add a framework I don't
  need. Don't add analytics without asking.

---

## Hosting setup

Use **Cloudflare Workers with Static Assets** — not Cloudflare Pages.

Requirements to verify before you start:

- The domain is already an active zone in my Cloudflare account.
- The exact hostname I want has **no existing CNAME record**. A custom domain
  cannot attach to a hostname that already has one. If it does, tell me — I
  need to delete that record first, and you must not delete it for me.

### wrangler.jsonc

Create it at the repo root, shaped like this:

```jsonc
{
  "$schema": "node_modules/wrangler/config-schema.json",
  "name": "<short-worker-name>",
  "compatibility_date": "<today's date, YYYY-MM-DD>",
  "assets": {
    "directory": "./dist",
    "not_found_handling": "404-page"
  },
  "routes": [{ "pattern": "<my-hostname>", "custom_domain": true }]
}
```

Notes:

- `not_found_handling` must be `"404-page"` for a content site, so unmatched
  URLs return a real 404. `"single-page-application"` returns HTTP 200 with
  index.html for every wrong URL, which search engines will index. Only use it
  if the site is genuinely a client-routed SPA.
- `custom_domain: true` makes Cloudflare create the DNS record and issue the
  TLS certificate on the first deploy. I should not have to touch DNS.
- Add `wrangler` as a devDependency. Static Assets need **3.78.10+**; use
  current v4.

### Deploy pipeline

GitHub Actions, deploying on push to `main`, plus a manual trigger:

```yaml
name: Deploy
on:
  push:
    branches: [main]
  workflow_dispatch:

concurrency:
  group: deploy
  cancel-in-progress: false

permissions:
  contents: read

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - uses: actions/setup-node@v7
        with:
          node-version-file: .nvmrc
          cache: npm
      - run: npm ci
      - run: npm run build
      - uses: cloudflare/wrangler-action@v4
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          command: deploy
```

Include `workflow_dispatch` so the first deploy can be triggered by hand after
I set the secrets, without needing an empty commit.

Also add a separate CI workflow that build-checks pull requests.

### Secrets

Two repo secrets, which **I** will set — do not ask me to paste the values into
the chat:

- `CLOUDFLARE_API_TOKEN` — created from the **Edit Cloudflare Workers**
  template, scoped to my account and my zone.
- `CLOUDFLARE_ACCOUNT_ID` — from the Workers & Pages overview page.

When you're ready for them, give me the exact `gh secret set` commands to run
myself, then wait.

---

## Repo

- Private GitHub repo unless I say otherwise.
- Add a `.gitignore` covering `node_modules/`, build output, `.env`, and
  `.wrangler/`.
- Add a `.gitattributes` with `* text=auto eol=lf` so line endings don't churn
  between my machine and CI.
- Pin Node in `.nvmrc` and have CI read it with `node-version-file`.
- Write a README that explains how to run it locally, how to add a page or
  post, and how deploying works. Assume I'll read it in six months having
  forgotten everything.

---

## Definition of done

Don't tell me it's finished until all of these are true, and show me the
evidence for each:

1. `npm run build` succeeds locally with no errors.
2. The dev server (`npm run dev`) starts clean. **Check this separately from
   the build** — some failures only appear in one or the other.
3. The deploy workflow run is green.
4. You have fetched the live URL and confirmed HTTP 200.
5. You have confirmed a nonsense URL returns a real **404**, not a 200.
6. **The live page actually renders in a browser.** A 200 from `curl` only
   proves bytes came back — a completely blank, broken page returns 200 too. If
   you can't open a browser, say so plainly and tell me to check it myself.
7. No file in the build output exceeds 25 MiB.

---

## How to work with me

- I'm not deeply technical. Explain what you're doing in plain language and
  skip the jargon, but don't hide problems from me or simplify to the point of
  being wrong.
- If something fails, tell me what broke and what you're trying — don't quietly
  retry six times.
- If you're about to do something hard to undo (deleting DNS records, force
  pushing, deleting files I made), ask first.
- Tell me what things cost before adding them.