The wild west of polyglot docs sites

7 min read Original article ↗

2026 Oct 08

Given a project that provides libraries in N different programming languages, the docs site for that project often needs to interact with N or N+1 different documentation generators. This is because each programming language has its own API reference generator. While the libraries themselves may be loosely coupled or decoupled from each other, the docs site often needs tighter coupling in various ways: all pages should use the same fonts and colors, the in-site search UX should be consistent and comprehensive, etc.

There doesn’t seem to be an established term for this kind of docs site, where you’re attempting to wrangle the outputs from disparate docs generators into one cohesive whole. Let’s call it a polyglot docs site for now. Maybe someone will come up with a better name in the future.

Short story long, polyglot docs sites feel like a sparsely explored frontier of technical writing, full of rattlesnakes and tumbleweeds. And perhaps a little gold, too.

Strategies#

In terms of top-down strategy I can only think of 2 ways to structure a polyglot docs site. I think both strategies are valid and viable but they both currently have a lot of major issues.

Transformation#

The first strategy is to parse each API reference generator’s output and transform it into markup that plays nicely with your main docs generator. For example, in my first job I ingested Doxygen HTML as input, used XSLT (!!) to transform it into simpler HTML fragments, and then used the raw directive to pull the HTML fragments into my Sphinx site.

The main drawback of the transformation approach boils down to losing out on the expertise of the API reference generators:

  • Tools like Doxygen, rustdoc, javadoc, etc. understand the details of their respective languages much better than I do. With a custom transformation that “simplifies” the output, there’s a risk that I’m stripping out information that users actually need. I.e. Chesterton’s fence.

  • These tools have put a lot of thought into the UX of API references. For example, given a structured search query like vec -> usize, rustdoc’s search engine will only return functions that take in a vec as an arg and returns usize.

Another drawback of transformation is that it goes against the grain of the ecosystem. Rust programmers are familiar with the rustdoc UI. Even if I could theoretically create an API reference that’s superior in every way, I’m still asking my users to figure out a new and different UI that they won’t encounter anywhere else.

Case study: Breathe#

Another example of the transformation approach is Breathe. You first run a Doxygen XML build, and then make that available as an input to the Sphinx build. In your reStructuredText you insert a directive like .. doxygenclass:: pw::Foo to indicate the place where the API reference for pw::Foo should go. Breathe parses the info from the Doxygen XML and transforms it into API reference content that Sphinx understands. This was the foundation of C/C++ API reference content on pigweed.dev from 2022 to 2024. We moved to the approach described in the next section for a few reasons:

  • One issue was slowness. I don’t remember the exact numbers but Breathe was a significant bottleneck in our docs build. We went from something like 90 seconds with Breathe to 60 seconds without it.

  • Another issue was too much glue code leading to silent failures. In addition to marking up your headers with Doxygen comments, you have to remember to pull the content into Sphinx via a directive like .. doxygenclass:: pw::Foo. On quite a few occasions I saw SWEs make an honest effort to document their code, but the documentation never actually got published, because they had forgotten the doxygenclass step.

  • The last issue was too much flexibility. Some docs contributors would order their doxygenclass directives alphabetically on a single page. Others would take a thematic approach. E.g. in the middle of a guide on how to foo the bar, they would insert the API reference for pw::Foo.

I respect and appreciate the work of the Breathe maintainers and don’t like singling them out. Breathe just happens to be in the unfortunate position of being the transformation tool that I have a lot of firsthand experience with and clearly demonstrates general issues of the transformation approach that any transformation tool will need to reckon with.

Turducken#

The second strategy is to defer to the expertise of the API reference generators and publish their output as-is. This is what pigweed.dev does. Under-the-hood, pigweed.dev is 3 separate docs sites cobbled together. We generate our C/C++ API reference with Doxygen, our Rust API reference with rustdoc, and everything else with Sphinx.

Architecture-wise, it’s a turducken. A chicken stuffed into a duck stuffed into a turkey. Well, in the case of pigweed.dev it’s more like a chicken (Doxygen) and a duck (rustdoc) stuffed side-by-side into a turkey (Sphinx).

The obvious problem is that the subsites all look different from each other:

../../../../_images/d1.png

A Doxygen-generated page#

../../../../_images/r1.png

A rustdoc-generated page#

../../../../_images/s1.png

A Sphinx-generated page#

With an obscene amount of !important flags I can make them look more similar to each other. And I plan on doing that. But no amount of CSS hacking can solve the following more insidious problems:

  • It’s hard to navigate from one subsite to another. E.g. from a rustdoc-generated page there is no way to get back to the pigweed.dev homepage.

  • The search UX is fragmented and incomplete. E.g. when using the in-site search on a page generated by Sphinx, the search results do not include any content from rustdoc-generated pages.

  • It’s hard to link from one subsite to another. You end up relying on hardcoded manual relative paths, which are brittle.

So, we’ve got 3 completely separate subsites that have no awareness of each other’s existence, and we somehow need to make them feel more connected. On pigweed.dev we made some progress on this front by introducing a universal header and comprehensive search.

Manual#

OK, I lied. There’s a 3rd approach. For a small, slowly changing API surface, it’s feasible to write all the docs manually. Especially in this age of agents. I’ve done it. It can work fine.

Future avenues of exploration#

My main motivation for this post was simply to start discussion among the maintainers of docs sites, docs generators like Doxygen, and libraries like Pagefind. Here are some ways that we might better wrangle and tame polyglot docs sites in the future.

--fragment mode#

I had to hack and override a lot of Doxygen and rustdoc CSS to make the pigweed.dev turducken functional. The only HTML output they provide assumes that you want a complete site, whereas what I really need is just the main content. It might help a lot to provide a --fragment mode that outputs content-only HTML fragments rather than a complete site with headers, search, navbars, etc.

Linking#

There is a wonderful little library, Doxylink, that makes linking from Sphinx to Doxygen bulletproof. If you link to a symbol that doesn’t exist, the docs build breaks. I need something similar in all directions: from rustdoc to Sphinx, from Doxygen to rustdoc, etc.