A beautiful site that's hard to update is a site that slowly rots. The reason this build stays fresh — new deals, copy tweaks, a re‑routed quiz — is the deployment setup: the code lives in GitHub, the live site is hosted by Vercel, and the two are wired together so that saving a change ships it. This module covers that workflow and why it's a genuine competitive advantage for a small operator.
1. What this stage is for
Make changing the live site safe, instant and reversible — so you actually keep it current instead of being afraid to touch it.
2. How the workflow runs
The loop, in plain terms:
- GitHub holds the code and its entire history. Every change is a recorded, labelled checkpoint. You can see exactly what changed, when, and undo any of it.
- Vercel watches GitHub. It's connected to the repository, so the moment a change is saved to the main version, Vercel rebuilds the site and pushes it live worldwide — usually in well under a minute.
- Claude‑Code makes the changes, and Cowork drives the GitHub/Vercel connectors to commit and deploy. You describe what you want changed; it's edited, committed and live shortly after.
That's the whole loop: describe → change → commit → live. No FTP, no manual uploads, no "the developer will get to it next week."
Every change a labelled, reversible checkpoint — the redesign, then a steady polish trail.
3. The features that make this powerful
This setup gives a one‑person operation capabilities that used to need a dev team:
- Push‑to‑deploy. Every saved change goes live automatically. Fixing a price typo is a 30‑second round trip, not a support ticket.
- Preview links before going live. Each proposed change can generate its own private preview URL — a complete copy of the site with just that change — so you can look at it before it touches the public site. You approve, then it ships.
- Instant rollback. Because every version is a saved checkpoint, if something looks wrong after a deploy you revert to the previous version in one click. This safety net is what makes frequent updates comfortable.
- A global content network. Vercel serves your pre‑built pages from servers close to every visitor, so the site is fast everywhere — which helps both experience and rankings.
- Built‑in analytics and performance insight. You can see real visitor traffic and real loading‑speed data without bolting on extra tools.
- Forms and logic run server‑side for free. The contact and enquiry forms (earlier modules) run on Vercel's serverless functions — no separate server to rent or maintain.
4. Why this beats a website builder for a growing business
A drag‑and‑drop builder is fine until you want control. This setup gives you:
- Ownership. The code is yours, in your GitHub. You're not locked into a platform's structure, pricing, or shutdown risk.
- Safety. Full history and one‑click rollback mean you can experiment without fear.
- Speed of iteration. The whole point of the modules in this series — the quiz, the booking wrapper, the reusable cards — is that they're cheap to build and cheap to change. The deploy setup is what makes "cheap to change" true.
- No per‑feature fees. No paying monthly for a form plugin, a popup plugin, a reviews plugin. You build what you need.
5. The practical habits that keep it clean
A few disciplines worth adopting from the start:
- Make changes in small, clearly‑labelled steps, ideally one page or one fix at a time, so the history reads like a changelog and any single change is easy to undo. (A giant all‑at‑once change is hard to review and hard to unpick.)
- Use the preview link to eyeball anything visual before it goes live.
- Check it on a phone. Most escape‑room traffic is mobile; a quick mobile check before shipping catches the majority of layout issues.
- Keep secrets and keys out of the code — store them in Vercel's environment settings, not in the files.
6. How I built it
- Claude‑Code made every code change and ran the build to catch errors before shipping.
- Cowork drove the GitHub connector to commit and the Vercel connector to deploy, returning the live/preview links.
- Each change went out as its own labelled checkpoint, so the live site improved in a steady, reversible stream.
7. The principle
The deployment setup isn't back‑office plumbing — it's what lets a small escape room keep a big‑business website. Save a change, see it live in under a minute, undo it in one click. Own your code, ship in small steps, preview before you publish, and the site stays sharp for years instead of freezing the day it launched.