Docs Build and Deploy
Purpose
Describe how the DSAMbayes documentation site is built, previewed, and deployed.
Documentation layers
DSAMbayes currently has two documentation layers with distinct purposes:
1. Package reference inputs
Package reference content is generated from:
- roxygen comments in
R/ - vignettes in
vignettes/ - generated
man/*.Rdfiles
This material supports package help pages and package-check workflows. It is not the deployed public docs site.
2. Public documentation site
The public docs site is built from hand-authored Markdown under docs/ plus the Hugo/Relearn wrapper under docs-site/.
Build locally:
Build flow:
docs/is the source of truth.docs-site/build_content.pymirrors and normalizes content intodocs-site/content/.- Hugo renders the final site into
docs-site/public/and cleans removed pages from prior builds.
There is no canonical automated deployment pipeline for the public docs site. Build and publish manually if you choose to host updated docs.
Preview locally:
- open Markdown files directly for quick edits, or
- serve/build the Hugo site for full navigation and theme rendering
If you maintain an external published mirror such as
https://dsambayes.docs.wppma.space/, treat it as a manual distribution
channel that may lag the repository. Verify freshness before linking to it in
release communication.
Configuration
docs/docs-config.json defines:
- metadata — site name, description, version.
- branding — logo, favicon, primary colour.
- navigation — navbar links and sidebar structure.
- features — math rendering (enabled), search (local).
Adding a new page
- Create the Markdown file in the appropriate section directory (e.g.
docs/modelling/new-page.md). - Add a sidebar entry in
docs/docs-config.jsonunder the appropriate section. - Add a row to the section’s
index.mdpage table. - Update
docs/_plan/content-map.mdif tracking authoring status.
Related pages
- Quality Gates —
QG-7docs build check