VexellDocs · v1.5

Getting started

Deployment

Both editions deploy to anything. The HTML edition writes a static dist/ folder. The Next edition produces a hybrid build that prerenders all current routes — so the same static-host flow works, with Vercel + Netlify giving you the optional SSR + ISR features.

Build & deploy

Pick your edition. The commands below cover the common targets.

bash
# Build the production bundle:
pnpm build         # writes .next/

# Deploy options:
#   Vercel       — vercel --prod  (recommended, fully Next-native)
#   Netlify      — netlify deploy --prod  (Netlify Next runtime auto-detected)
#   Self-host    — pnpm start (Node 20+ on a server / VPS)
#   Docker       — official Next dockerfile in https://nextjs.org/docs/deployment
#   Static export — set output: 'export' in next.config.ts; writes out/ ready for any static host

Environment variables

Vexell ships fully functional without any environment variables — the AI primitives have sensible local-state defaults. Add variables only when wiring vendors (analytics, model SDKs, auth providers).

bash
# Optional .env.local (Next edition)
NEXT_PUBLIC_ANALYTICS_HOST=https://app.posthog.com
NEXT_PUBLIC_ANALYTICS_KEY=phc_xxxxxxxxxxxxxxxx
NEXT_PUBLIC_SITE_URL=https://example.com

# Server-only (do not expose):
ANALYTICS_INGEST_TOKEN=xxxxxxxx

Vercel deploy details

  • HTML edition: framework preset is "Vite". Build command pnpm build, output directory dist.
  • Next edition: framework preset is "Next.js". Vercel auto-detects everything. No additional config needed.
  • Custom domain: add it in your Vercel project. Vexell's tokens and fonts are already production-grade — no extra setup.

Read next

  • Analytics — wire your vendor (PostHog, GA4, Plausible, Segment).