Documentation

Deployment

How the Shaw apps ship to production.

Hosting

Each app deploys independently to Vercel on its own subdomain:

  • shawwebsolutions.com — website
  • docs.shawwebsolutions.com — docs
  • audit.shawwebsolutions.com — audit
  • studio.shawwebsolutions.com — studio
  • vector.shawwebsolutions.com — vector

Environment variables

Secrets are configured per app in Vercel (and .env.local in development) and are strictly server-side — never exposed with a NEXT_PUBLIC prefix, logged, or committed.

  • RESEND_API_KEY — website contact form delivery (Resend).
  • PAGESPEED_API_KEY — audit app's Google PageSpeed / Lighthouse integration.

Assets before deploying the website

Generated assets are committed, so a normal website deploy needs nothing extra. When source assets change, regenerate first (pnpm assets:build, and pnpm assets:screenshots when tool UIs changed), verify with pnpm assets:verify, and commit the regenerated files alongside the manifest.