https://mgaitan.github.io/enContents © 2026 <a href="mailto:gaitan@gmail.com">Martín Gaitán</a> Mon, 04 May 2026 01:03:44 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://mgaitan.github.io/en/posts/federated-documentation-with-sphinx/Martín Gaitán<div><p>Most teams run into the same problem sooner or later: technical documentation is spread across different repositories, but the natural destination for publishing it is a single, coherent site.</p> <p>A central project may have its own development docs, but also depend on operations guides, infrastructure manuals, or integration documentation that live in other repositories and are often maintained by different teams.</p> <p>The question is how to publish all of it together — with consistent navigation and cross-references — without forcing the sources to be centralized as well.</p> <p>The idea we've been implementing at <a href="https://www.fierro.com.ar/">Fierro</a> is fairly simple: <strong>a single published site, built with Sphinx from one main repository, but from sources maintained across several repos</strong>.</p> <p><a href="https://mgaitan.github.io/en/posts/federated-documentation-with-sphinx/">Read more…</a> (7 min remaining to read)</p></div>architecturedevopsdocsgithub-actionssphinxhttps://mgaitan.github.io/en/posts/federated-documentation-with-sphinx/Tue, 28 Apr 2026 04:26:03 GMT