Skip to main content

​
Keycli landing deployment checklist

​
Before deploy

  • npm install
  • npm run landing:typecheck
  • npm run landing:build
  • npm run docs:validate
  • verify apps/site/.env.example values are understood
  • set NEXT_PUBLIC_SITE_URL
  • decide docs mode:
    • fallback hub only (leave docs env vars unset)
    • redirect mode (NEXT_PUBLIC_DOCS_URL only)
    • proxy cutover (NEXT_PUBLIC_DOCS_URL + KEYCLI_DOCS_ORIGIN)
  • if using proxy cutover, confirm the external Mintlify origin is already real and smoke-tested
  • if using proxy cutover, confirm the docs origin behavior you want for:
    • /api/search
    • /api/request
    • /llms.txt
    • /mcp
  • configure one real lead-capture destination:
    • Resend (KEYCLI_DESIGN_PARTNER_RESEND_API_KEY, from, to)
    • or webhook (KEYCLI_DESIGN_PARTNER_WEBHOOK_URL)
  • decide whether Vercel Analytics should be enabled
  • sanity-check landing copy for honest product claims

​
Vercel deploy

  • import the GitHub repo in Vercel (canonical path; avoid ad-hoc local CLI deploys)
  • set project root to apps/site
  • confirm Next.js framework detected
  • add env vars
  • create first preview deployment
  • verify homepage, /docs, sitemap, robots
  • if using proxy mode, verify at least one nested docs page under /docs/<path>
  • if using proxy mode, verify the Mintlify auxiliary routes you expect to expose publicly
  • submit a test guided-help request

​
After deploy

  • capture deployed URL
  • decide whether to promote to production
  • if promoting, set/customize domain
  • verify guided-help capture delivery actually arrives
  • verify analytics events appear
  • if using redirect mode, verify /docs redirects to the intended external docs URL
  • if using proxy mode, verify refresh / deep-link behavior plus assets / search / request under the marketing domain
  • if using proxy mode, verify /llms.txt and /mcp behave exactly as intended
  • if using proxy mode, verify marketing-owned /robots.txt and /sitemap.xml still stay local
  • add the landing project as a scoped Vercel connection in Keycli
  • add scoped GitHub connection for the repo
  • dogfood first preview-safe config change through Keycli

​
First governed changes to test with Keycli

  • preview env update
  • guided-help webhook / email config change
  • GitHub Actions secret update
  • approval-gated prod-facing change