Dual documentation stack (Docusaurus + Sphinx)
· One min read
The repository now ships a Docusaurus product site and Sphinx API reference.
Guides and blog posts live in Docusaurus; Python module docs are generated from
src/edox_ops and published under /api/.
This matches how we expect operators to use the project: prose and workflows in the main site, implementation detail in autodoc. Blog posts here are not versioned the same way as product docs—use versioned docs when you need release-specific operator guidance.