Deployment workflow

Vercel baseline

This template builds to static output, so Vercel deployment is straightforward:

1. Import the GitHub repo into Vercel.
2. Keep the default Astro build command or set it explicitly to bun run build.
3. Set the output directory to dist if Vercel does not infer it automatically.

Preview deployments should work on every push once dependencies install cleanly.

The shared zuedocs() integration uses Vercel’s production project domain at build time to generate /sitemap.xml, so a normal Vercel consumer does not need a separate sitemap integration or site URL setting. The sitemap is built from the HTML pages Astro actually emitted for that project.

CLI path

If you prefer the CLI workflow:

vercel
vercel --prod

Use the first run to link the project and the production run once the branch is ready.

Cloudflare DNS pattern

When the domain is managed in Cloudflare, use the cf CLI on this machine instead of editing records manually.

Common patterns:

cf doctor
cf cname docs cname.vercel-dns.com --proxied=false
cf txt _vercel "verification-token"

Prefer --proxied=false for Vercel verification and DNS ownership records unless there is a deliberate reason to proxy traffic.

Post-deploy checks

After the Vercel project and DNS are wired:

1. Confirm the apex or subdomain resolves correctly.
2. Check that / and /docs both load without asset errors.
3. Open one deep docs route directly to verify static routing.
4. Open /sitemap.xml and confirm the production domain and current docs routes are present.
5. Re-run bun run build locally if the deploy behaves differently than expected.