Current
Production Docs Rendering
How published Doxa docs sites are rendered for readers, and what changes when the renderer is updated
Overview
Every published Doxa docs site is rendered by one shared docs renderer. When a reader opens <slug>.doxa.page or a custom domain, the platform reads the published version of your project and renders it with the same MDX components, navigation, search, and API reference pages that your site uses. You do not choose or install a renderer. Your site uses whichever renderer release Doxa currently runs in production.
Saved production HTML and route data are covered in Production Docs Pre-rendering. The content injection flow is covered in Production Docs Content Injection.
Current production status
| Setting | Value |
|---|---|
| Rollout status | Enabled for all production sites |
| Renderer mode | all |
| Build selection per site | None. Every site runs the same current release. |
What a reader's request goes through
The public request for your hostname arrives at the Doxa docs dispatcher.
The dispatcher selects how the page is rendered. It either uses the shared renderer or a version-pinned renderer for the published version.
The renderer reads the published content for your project and returns the page.
Both paths render the same docs template. Pull-request previews and permanent generation URLs always use the shared renderer.
| Request type | Renderer used |
|---|---|
| Pull-request preview | Shared renderer |
| Permanent generation URL | Shared renderer |
| Published production site, dynamic mode off | Shared renderer |
| Safe fallback request | Shared renderer |
Renderer updates
The renderer is not versioned per site. Consequences for your project:
No site pins an older renderer. A site uses the current release, so a renderer update can change how every published site looks or behaves after the release is deployed.
Published content stays compatible. The renderer reads every content format Doxa has published, so existing sites keep working without republishing.
Updates are full rollouts. A canary rollout to a subset of sites is planned but not available. Every renderer release reaches all sites at once.
To pick up renderer changes in your content, you do not need to do anything. To confirm a change, open your site after publishing and check the page.
Unpublished hostnames
If a hostname has no published docs, the reader sees a short static 404 page. The page does not show project data or error details. Requests that do not accept HTML receive plain text. The response is not cached.
Note:
If you see the 404 page on your own domain, check that the project has a published version and that the custom domain is attached to the project. See Custom Domains and Branches, Previews, Publishing, and Restore.
Related pages
Production Docs Pre-rendering explains saved production HTML and route data.
Production Docs Content Injection describes how content reaches the renderer.
Docs Artifact Compatibility describes how published content formats stay readable across renderer releases.
Custom Domains explains how to attach your own domain.