You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are new and increasing demands on the documentation, the main two being localization (i.e., translations) and release-specific docs (#5308). With these new demands, it has become increasingly difficult for the current system to meet our needs.
Back before we tried to address these kinds of needs, our documentation setup was simpler and served us well. The backend was smaller, easier to understand, and easier to maintain, since it didn't need to do much. There was only a single, canonical version of every documentation page.
However, times change. As our project has matured, we've decided it was time to acknowledge and take seriously the reality that not everyone reads English and not everyone uses the same version of Qubes OS at the same time. We have users and contributors from around the world, and we have multiple versions of Qubes.
There are times when an older Qubes release is supported concurrently with a newer release to give users time to upgrade. Even when there's only one currently-supported release, there's usually a new one in development and testing that folks want to start documenting. This means that we have to support a separate version of each appropriate documentation page for every translated language and for every supported and in-development Qubes version, not to mention historical documentation for EOL releases.
This is just a summary. In order to fully understand the context and background of this issue, please read the following mailing list threads:
Built-in support for downloading/exporting docs in multiple formats for offline reading. Direct access to human-readable source files in Git repos should also continue to be possible.
Includes search functionality.
Widespread use among open-source projects. Established history.
Can be self-hosted.
[Subjective] Some people think RTD looks better.
These will benefit those who produce and consume Qubes documentation.
Completion criteria checklist:
Complete conversion to Sphinx / RST
Freeze docs
Make testing announcement
Wait for testing period to complete (2025-08-12)
Incorporate any errors found, rerun conversion, and post final RTD version
Create an RST guide for documentation contributors
Full list of documentation pages to be reviewed during testing period
For each documentation page in the list below:
new denotes a link to the new documentation page (generated from reStructuredText and hosted by Read the Docs) that needs to be reviewed.
old denotes a link to the old documentation page (generated from Markdown and hosted by GitHub Pages) so that you can compare the new page to the old one.
source denotes a link to the reStructuredText source code for the new page, which is provided in case you want to open a pull request.