ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Decide whether to use Read the Docs' native versioning or create separate projects for each release, with a concrete .readthedocs.yaml example and verification steps.
Learn how Confluence’s built‑in versioning lets you track edits, compare changes, and revert safely. A step‑by‑step guide, API snippets, and performance tips for collaborative editing.
Guidance on selecting fixed or floating NuGet versions, using Central Package Management and lock files for reproducible builds.
Read the Docs turns every tag into a potential published version. Use automation rules, active/hidden flags, and redirects to keep the version picker clean and builds under control.
Read the Docs versions map to Git refs, not semantic versions. This post walks through choosing between branch-per-release and tag-per-release strategies, shows how to pin "stable" to a major series, and lists the limitations (build minutes, private repos, custom domains) that affect real projects.
Decide between single-version and multi-version docs on Read the Docs: constraints, trade-offs, a comparison table, a .readthedocs.yaml example, and verification steps.
Learn how to let Read the Docs automatically build and serve each Git tag or branch as a separate documentation version using a simple .readthedocs.yaml file. Follow the step‑by‑step guide, example config, and common pitfalls to get versioned docs up and running quickly.
Read the Docs builds a separate docs site per Git tag or branch. Here's how version switching works, why tag naming discipline matters, and how to add a maintenance-branch version safely.
Learn how to pick the default version in Read the Docs so visitors see the right docs for stable releases while developers can still access the latest build.
readthedocs
dotnet
nuget