CI and Delivery

The documentation delivery flow is split into two independent build outputs.

Output A: Runtime Image

• repository: datahub/v3/services/docs-site
• output: Docker image for static file serving
• change trigger: runtime or nginx configuration changes

Output B: Documentation Artifact

• repository: datahub/v3/docs
• output: versioned MkDocs site/ artifact
• change trigger: markdown, navigation, theme, or assets updates

Delivery Boundary

Documentation is not part of the product release package.

The expected flow is:

• CI in datahub/v3/docs builds the static site artifact
• the runtime image in datahub/v3/services/docs-site changes only when nginx/runtime behavior changes
• deployment of documentation content is handled separately from release-builder and product release assembly