Version-aware documentation on ReadTheDocs without breaking search
Control which documentation version users see and search on ReadTheDocs using version-aware configuration and Sphinx conditionals.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Control which documentation version users see and search on ReadTheDocs using version-aware configuration and Sphinx conditionals.
A diagnostic guide to resolving Read the Docs build failures caused by missing dependencies, Python version mismatches, and Sphinx configuration errors.
Learn how to control Read the Docs builds by committing a .readthedocs.yml file that pins Python version, installs dependencies, and overrides the default Sphinx command.
Learn how to migrate to ReadTheDocs v2 config, pin build images and Python versions, add PDF/EPUB output, use conda for system dependencies, and avoid common pitfalls like legacy file conflicts and missing directory changes.
Choose the right build trigger for ReadTheDocs: webhook‑based automatic builds or manual/CI‑triggered builds. A practical guide with example config, trade‑offs, and a step‑by‑step Sphinx setup.
Use .readthedocs.yaml to pin Python, dependencies, and the Sphinx builder so Read the Docs builds match your local output.
Learn how to configure ReadTheDocs to host stable, latest, and release‑tagged documentation with a flyout menu. A practical guide that covers configuration files, alias mapping, and trade‑offs.
Read the Docs builds one documentation site per Git branch or tag, giving you stable/latest/release URLs for free. Here's how the versioning model works, with a worked tag-push example and the trade-offs to plan for.
Reviewing docs by diff hides rendering problems. Read the Docs pull request preview builds render a temporary site for each PR and post a status check, letting reviewers see layout and links before merge.