Deploy

SwiftAgency builds to plain static files in dist/. Any host that serves HTML works; the theme ships ready-made configuration for the three most common ones.

Before you deploy

1. Set url in src/config/site.ts to your domain. Canonical URLs, the sitemap, hreflang links and social cards are built from it.

2. Change the Sitemap: line in public/robots.txt to the same domain.

3. Run npm run verify locally. If it passes, the build will pass on your host too.

4. Push the project to your own GitHub, GitLab or Bitbucket repository.

Pick a host

Netlify

Import the repository in Netlify. netlify.toml sets everything:

• build command npm run build, publish directory dist
• Node 22, and KEYSTATIC=false so the CMS never loads during a build
• pretty URLs, so /work is served from work.html

Cache and security headers come from public/_headers.

Vercel

Import the repository in Vercel. It detects Astro, and vercel.json adds:

• clean URLs without trailing slashes
• a year-long cache for hashed files in /_astro/
• security headers: nosniff, a strict referrer policy, frame blocking and a permissions policy

Cloudflare

wrangler.jsonc serves dist/ with Workers static assets, drops trailing slashes and uses the theme’s 404.html.

npm run build
npx wrangler deploy

Or connect the repository in the Cloudflare dashboard with build command npm run build. Change name in wrangler.jsonc first; it becomes part of your workers.dev address. Headers come from public/_headers.

Anywhere else

Run npm run build and upload the contents of dist/. Configure the server to:

• serve /work from work.html (the build uses build.format: 'file')
• answer unknown URLs with 404.html and status 404
• cache /_astro/* for a year; those file names change whenever their content does

One-click deploy buttons

The theme’s README has “Deploy to Netlify”, “Deploy with Vercel” and “Deploy to Cloudflare” buttons. They copy a repository into your account and deploy it in one go. They point at the theme’s own repository, so once your project lives in your repository, replace ilesscodex/SwiftAgency in the button links with yours.

Custom domain and HTTPS

All three hosts issue certificates automatically once you add a domain in their dashboard. Update url in site.ts to the final domain and redeploy, otherwise canonical links keep pointing at the old address.

The CMS is not deployed

Keystatic runs only with npm run dev. The deployed site has no /keystatic route and no admin login. To let people edit the live site, see Keystatic in GitHub mode.

Continuous integration

.github/workflows/ci.yml runs on every push and pull request:

1. npm ci and npm run verify: Astro Check, ESLint, Prettier and a full build.
2. Lighthouse CI on seven key pages, three runs each. The job fails if Accessibility, Best Practices or SEO drop below 100, or desktop Performance below 95.

Hosts build on their own, so CI is a safety net rather than a deploy step. See Performance.