Building the documentation

This page is deliberately short: bridle already has a full-length guide to building its own documentation set — tooling install, the west/CMake invocation, developer-mode turbo options, cleaning, serving locally, and what to do about warnings — at Building Bridle documentation. Everything general about building this documentation lives there; this page states only what is specific to the rig documentation within it.

The rig documentation is one section of the larger bridle docset (doc/bridle/, built as the bridle-html target alongside zephyr-html, devicetree-html, kconfig-html and cannectivity-html), not a docset of its own — build it exactly as Building Bridle documentation describes for bridle, -W and all.

The Expander API pages are generated by autodoc, which imports every rigc module under scripts/rigc/ to read its docstrings. That works with no Zephyr tree present and no ZEPHYR_BASE set — the expander’s devicetree imports are all deferred into function bodies — so nothing beyond what Building Bridle documentation already installs is needed to render this section.