Sphinx documentation importer and aggregator for Antora sites
Built for API documentation teams using Sphinx and Antora.
“Jul 19, 2022 — It would be great if we could use Antora to create a main documentation that combines (includes, imports, whatever the correct term is) ... Read …”
The receipts — real demand
“Jul 19, 2022 — It would be great if we could use Antora to create a main documentation that combines (includes, imports, whatever the correct term is) ... Read more”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
API documentation teams using both Sphinx and Antora who need unified docs sites. No search volume given; demand appears niche and tied to specific tool adoption rather than broad market pull.
Competition & the opening
Antora already ships native multi-component aggregation (built-in), sphinx-to-asciidoc handles conversion, and Read the Docs hosts both separately. The gap is narrow: teams want Sphinx content *inside* Antora without manual conversion or iframe workarounds, but Antora's native feature and free conversion tools already address the core need. Market is moderately crowded (4/10).
What's hard to build
Sphinx and Antora use different source formats (reStructuredText vs AsciiDoc) and metadata models. Reliable conversion requires handling custom Sphinx extensions, cross-references, and theme-specific directives—complexity that existing tools (Pandoc, sphinx-to-asciidoc) struggle with. Integration into Antora's component model adds another layer of build-system coupling.
Why now
Antora users with large inherited Sphinx docs want aggregation without manual conversion or iframe hacks, but native solutions remain incomplete and community-driven.
How you'd monetize
One-time $99–199 conversion tool or $9/mo SaaS for ongoing Sphinx sync; position