Deployment
Build Output
Learn about the structure and purpose of build outputs.
`build` writes a flat static site plus AI and machine-readable artifacts to the output directory. Only `published` content enters those outputs.
Site Files
- `index.html`: site root entry
- `<lang>/index.html`: language landing page
- `<lang>/<slug>/index.html`: canonical reader page
- `docs/<slug>/index.html` and `<lang>/docs/<slug>/index.html`: compatibility redirect pages for legacy paths
- `404/index.html`: static 404 page
Search and AI Artifacts
- `search-index.<lang>.json`: static search index
- `llms.txt`: lightweight AI entry point
- `llms-full.txt`: full-site text export
- `mcp/index.json`: machine-readable artifact index
- `mcp/pages.<lang>.json`: page-level summaries
- `mcp/chunks.<lang>.json`: chunked content payloads
- `mcp/navigation.<lang>.json`: published navigation data
- `mcp/openapi/index.<lang>.json`: machine-readable API source index when API sources are configured
- `build-manifest.json`: build metadata
Publication Rule
- Only `published` pages are emitted into the reader site, search indexes, `llms.txt`, and `mcp/` outputs
- `draft` and `in_review` pages remain in the source project, but are not exposed in public artifacts
- Treat page status as the publication boundary, not file existence
Custom Output Directory
Override the default `dist/` location with a CLI flag when needed.
npx @anydocs/cli build ./my-docs --output ./build