Pages Deployment Architecture

Build and Publish Path

1. Markdown and MkDocs config are maintained in dlongglobal-docs.
2. Cloudflare Pages runs the project-specific build command.
3. Built assets are emitted to each site's site/ directory.
4. Pages serves content through the custom domains.

Site Separation

• docs-site/ and knowledge-site/ build independently.
• each site has its own requirements, MkDocs config, and navigation.
• visual differentiation is enforced through separate Material palette settings.

Operational Guardrails

• no application secrets in static docs content
• no backend business logic embedded in docs surfaces
• identity gate handled by Cloudflare Access on target hostnames

Runtime Scope

This deployment model is intentionally static-first. Interactive or privileged workflows belong on separate authenticated application surfaces.

Version History

Version	Date	Change	Author
1.0	2026-03-06	Initial Pages deployment architecture documentation	Codex