Platform

Deployment

Surface-local Vercel setup for the dashboard and docs app

One surface, one Vercel project

Treat the dashboard and docs as independent Next.js deployments even though they live in the same repo.

The agents repo has two deployable web surfaces: the dashboard and the docs site.

Surfaces

Dashboard

Root directory: apps/app

Runtime: Next.js 16

Docs

Root directory: apps/docs

Domain: docs.agents.creativeintelligencecompany.com

Use one Vercel project per deployable surface.

Dashboard

  • root directory: apps/app
  • config: repo root currently still contains the existing app deployment config
  • runtime: Next.js 16

Docs

  • root directory: apps/docs
  • config file: apps/docs/vercel.json
  • intended domain: docs.agents.creativeintelligencecompany.com

The surface-local docs config is:

{
  "buildCommand": "pnpm build",
  "outputDirectory": ".next",
  "framework": "nextjs"
}

Linking from the dashboard

Dashboard documentation buttons should point at the docs surface rather than GitHub. In development it is reasonable to target a local docs URL; in production they should resolve to the docs domain.

Local commands

pnpm -C apps/docs dev
pnpm -C apps/docs build
pnpm -C apps/app build

Deployment checklist

  1. Create a dedicated Vercel project for apps/docs.
  2. Set its root directory to apps/docs.
  3. Attach docs.agents.creativeintelligencecompany.com to that project.
  4. Keep the dashboard and docs deployments independent.
  5. Verify the dashboard documentation buttons land on real docs pages.

Source of truth

Docs deploy config
apps/docs/vercel.json
Dashboard deploy config
vercel.json
Workspace deployment guidance
apps/AGENTS.md and ~/.agents/rules/stack.md