Bugzilla

> I'm now considering to just build the rust doc as part of ./mach doc so that it automatically gets picked up by the current CI job instead of adding a separate archive that needs to be retrieved separately. (Leaving the needinfo for https on the staging doc page.)

Yes, this is what I was going to suggest. If you can find a Sphinx extension that can integrate rust docs into the existing Sphinx build, that's even better. After a quick search I found:
https://sphinxcontrib-rust.readthedocs.io/en/stable/

But I'm not familiar with Rust docs and am unsure if this satisfies the need you all are talking about here.

> I'm now considering to just build the rust doc as part of ./mach doc so that it automatically gets picked up by the current CI job instead of adding a separate archive that needs to be retrieved separately. (Leaving the needinfo for https on the staging doc page.)

Yes, this is what I was going to suggest. If you can find a Sphinx extension that can integrate rust docs into the existing Sphinx build, that's even better. After a quick search I found:
https://sphinxcontrib-rust.readthedocs.io/en/stable/

But I'm not familiar with Rust docs and am unsure if this satisfies the need you all are talking about here. The "Motivation" blurb certainly sounds like our use case though:

> This is primarily meant for teams and projects that are already using Sphinx as a documentation build tool, and would like to include documentation for Rust projects in it along with Python, C, and other languages.