Playbook: port a site
Webflow (or any static site) to Vercel, tracked and editable.
Fast path
Console → Port a site → paste the source URL and a project name (kebab-case, suffix -site for client sites). The porter runs the whole pipeline (see Porter). Takes a few minutes.
Verify (required)
- Live URL serves and matches the source visually.
- No Webflow badge, no blank pages (SRI strip worked).
data-website-idpresent in the page head (Umami injected).- Site appears in the console and pages list loads.
Manual path
~/Desktop/code/backpack/site-porter/clone.py <url> <dir> then --deploy --scope withunify. Use only when the Actions pipeline is unavailable.
Cloudflare path
For a domain whose DNS is on our Cloudflare account, the site can run as a Cloudflare Worker with static assets instead of a Vercel project. First used for withunify.org (Backpack-Ops/withunify-site, 2026-11-01).
python3 clone.py <url> <dir> --host cloudflare --domain <apex>, plus--alias <old origin>if the pages link to an older domain of the same site. This writes the site into<dir>/sitewithwrangler.jsonc, a Worker that 301s http and www to https on the apex,robots.txt,sitemap.xmland a GitHub Actions deploy.- Create the repo in Backpack-Ops and set secrets
CLOUDFLARE_API_TOKEN(vaultCLOUDFLARE_ACCOUNT_TOKEN, the only one with Workers custom-domain access) andCLOUDFLARE_ACCOUNT_ID, piped fromws keys run. - Snapshot the zone, then delete any A, AAAA or CNAME records for the apex and www. Custom domains will not attach over existing records.
- Push main. The workflow deploys and attaches both domains. Expect a minute of 404s while the edge picks up the new domains.
- Check every sitemap URL returns 200 with a browser user agent (the zone’s bot protection returns 403 to scripts’ default agents).
Cautions
- Do not port sites we do not own or manage. This was declined once (cursor.com) and stays declined.
- Forms still post to Webflow; keep the Webflow project alive until the forms module replaces them.