Skip to content

Cloudflare Pages Deployment

The Blaze docs site is a static VitePress build intended for a public Cloudflare Pages project connected to the private track-forge/adventure-kit repository.

Build settings

Configure the Pages project with these settings:

SettingValue
Production branchmain
Build commandnpm run build:docs
Build output directorydocs/dist-docs
Root directoryrepository root
Node.js22

The default docs base is /, which matches Cloudflare Pages preview and production hostnames such as https://<project>.pages.dev/. Set DOCS_BASE only for a non-root path host.

Local development

bash
npm ci
npm run build:docs
npm run preview:docs

The preview command serves the production build output and is the local check for static routing, clean URLs, and same-origin assets.

Production and previews

Cloudflare Pages should publish the main branch as production. Pull requests and non-production branches should create preview deployments, using the same build command and output directory.

Keep the repository private. The Pages site is public because Cloudflare serves only the generated docs/dist-docs artifact, not the source repository or local environment files.

Legacy GitHub Pages fallback

The existing GitHub Pages workflow remains as a temporary fallback until the Cloudflare Pages project is connected and a public Cloudflare production or preview URL is verified. That workflow passes a repository-path base for GitHub Pages only; Cloudflare should use the default root base.

BARKLINE mark is served from a local, hash-pinned repository asset.