docs.vireondynamics.com

VitePress portal: Vireon hub at / and Liminal harness docs at /liminal/.

Where the content lives

What	Repository / path
Liminal docs (source of truth)	liminal-ai → docs/
Marketing site	vireondynamics-website (root — not this folder)
Built copy (gitignored)	liminal/ — synced from liminal-ai on each build

Edit harness docs in liminal-ai, then deploy this project so production picks them up.

Vercel (production)

This folder is a separate Vercel project from www.vireondynamics.com:

• Domain: docs.vireondynamics.com
• Root directory: docs-portal (if the Git repo is vireondynamics-website)
• Build: node scripts/vercel-build.mjs (clones latest liminal-ai main, then npm run build)

Why docs looked stale

Older builds cloned liminal-ai once into .liminal-ai-clone/ and reused it when Vercel cached the workspace. vercel-build.mjs now re-clones on every deploy.

Connect Git (recommended)

In the Vercel project for docs:

1. Connect the vireondynamics-website repository.
2. Set Root Directory to docs-portal.
3. Production branch main — any push that touches docs-portal triggers a rebuild.

Pushing liminal-ai alone does not redeploy docs until you either:

• Run a deploy hook / npm run docs-portal:deploy from the website repo, or
• Add a GitHub Action that calls the Vercel deploy hook when liminal-ai docs/** changes.

Manual deploy

cd docs-portal
npm install
npm run docs-portal:deploy   # from website repo root
# or:
npx vercel deploy --prod

Optional env:

• LIMINAL_REPO_URL — default https://github.com/traidy2222/liminal-ai.git
• LIMINAL_REPO_REF — default main
• LIMINAL_REPO_ROOT — skip clone; use local monorepo path

Local

# From website repo root (with liminal-ai sibling or set LIMINAL_REPO_ROOT)
npm run docs-portal:sync
npm run docs-portal:dev