Build and host a small business website with AI coding tools instead of Webflow, Squarespace or Wix

You are building a static marketing website for {{business_name}}. Read SITE_BRIEF.md in this folder first; it is the source of truth.

Requirements
- Pages: {{page_list}}. One HTML file per page in ./public (e.g. public/index.html, public/services/index.html) so URLs have no .html extension.
- Plain HTML + one shared CSS file (public/styles.css). No framework and no build step unless I ask. Minimal JavaScript (mobile menu only).
- Shared header/nav and footer must be identical on every page. Footer: {{footer_contents}}.
- Design: colours {{brand_colors}}, fonts {{fonts}}, tone {{design_tone}}. Mobile-first, readable at 375px wide, no horizontal scroll.
- Accessibility: semantic headings (one h1 per page), alt text on every image, visible focus states, colour contrast at least WCAG AA.
- SEO: unique <title> and meta description per page (use the ones in the brief), Open Graph tags, a sitemap.xml and robots.txt in public/, canonical URLs on {{domain}}.
- Contact form: {{form_approach}}.
- Redirects: create public/_redirects with 301s from each old URL in the brief to its new path.
- Images: put them in public/images, sized for the web (max ~1600px wide, compressed), with width/height attributes.
- Hosting: Cloudflare Workers static assets. Create wrangler.jsonc with name "{{worker_name}}", today's compatibility_date and "assets": {"directory": "./public"}. No Worker script unless the form approach needs one.

Process
1. Propose the file structure and a one-paragraph design direction. Wait for my OK.
2. Build the home page first. Stop so I can review it in the browser.
3. Build the remaining pages, then run a self-check: broken internal links, missing alt text, missing titles, pages wider than the viewport at 375px. Report what you found and fixed.
Do not invent testimonials, client names, prices, awards or statistics. Use clearly marked placeholders where content is missing.

I'm building a simple static website for {{business_name}} with these pages: {{page_list}}. All pages share one stylesheet called styles.css.
Here is my site brief:
{{site_brief}}
Now write the complete file for the "{{page_name}}" page, saved as {{file_path}}. Use plain HTML, link to /styles.css, include the shared header and footer exactly as in previous pages: {{shared_header_footer_or_none}}.
Use only content from the brief; mark anything missing as [PLACEHOLDER: ...]. Give me the whole file in one code block and nothing else.

Review every file in ./public for launch readiness on {{domain}}. Check and fix: broken internal links; images without alt text or width/height; pages missing a unique title or meta description; more than one h1; layout overflow at 375px; contrast below WCAG AA for {{brand_colors}}; any invented testimonials, numbers or client names; _redirects entries for these old URLs: {{old_urls}}.
Report a table of issues found, what you changed, and anything that needs my decision.

Change request for the {{business_name}} site: {{change_description}}.
Only edit the files needed. Keep header/footer identical across pages. Show me a summary of the diff, then run `npx wrangler deploy` once I confirm.

# Site brief – {{business_name}}
_Fill this in before you prompt the AI. The more specific, the less rework._

## 1. Basics
- Business name: {{business_name}}
- One-sentence description: {{one_liner}}
- Primary audience: {{audience}}
- Main action we want visitors to take: {{primary_cta}} (e.g. book a call, request a quote, call us)
- Domain: {{domain}} — registrar: ______ — DNS currently managed by: ______
- Current site URL (to migrate from): {{current_site_url}}

## 2. Pages (3–8)
| Page | URL path | Purpose | Key content | Old URL to redirect from |
|---|---|---|---|---|
| Home | / | Explain what we do, prove it, CTA | Hero, 3 services, testimonials, CTA | / |
| Services | /services | Detail each service | 3 sections + FAQ | /what-we-do |
| About | /about | Trust | Story, team photos, credentials | /about-us |
| Contact | /contact | Convert | Form, phone, address, map link, hours | /contact |
| (optional) Work / Case studies | /work | Proof | 3 short case studies | |
| Privacy | /privacy | Legal | Your privacy policy text | |

## 3. Brand
- Colours (hex): primary ____ accent ____ text ____ background ____
- Fonts: ____ (or "system fonts")
- Logo files: SVG/PNG paths
- Sites we like the look of (and why): ____
- Tone of voice: ____

## 4. Content inventory
- Copy: where it lives now (export from old site, Google Doc link)
- Images: folder link; all images we have rights to use? yes/no
- Testimonials (with permission): ____
- Legal: privacy policy, cookie notice needed? (depends on analytics/forms used and your location)

## 5. Forms and integrations
- Contact form fields: name, email, phone (optional), message, how did you hear
- Where submissions go: Google Form + Sheet / email via a small Worker / other
- Booking link (e.g. existing scheduler): ____
- Analytics: none / privacy-friendly analytics / Google Analytics
- Anything else from the old builder we rely on: blog, store, member area, newsletter signup, chat widget

## 6. SEO essentials
- Page titles and meta descriptions: keep the current ones? (copy them from the old site)
- Business address and phone shown consistently on every page footer
- Old URLs that get traffic (from your analytics) → redirect targets

## 7. Who maintains it
- Who will edit text after launch: ____
- How often: ____
- Their comfort level: edits in a code editor / asks the AI / needs a visual editor

{
  "$schema": "./node_modules/wrangler/config-schema.json",
  "name": "{{worker_name}}",
  // Set to the date you create the project
  "compatibility_date": "{{compatibility_date}}",
  "assets": {
    "directory": "./public"
  }
}