ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
Pin the build environment in readthedocs.yml and map repository tags to Read the Docs versions to keep documentation reproducible and aligned with releases.
Learn how to automatically publish documentation for each Git tag using Read the Docs, see a step‑by‑step example, and understand the trade‑offs of keeping many versions active.
Learn how to use GitBook’s built‑in versioning to publish docs for each product release, with a concrete workflow, trade‑offs, and verification steps.
Goal: Prevent public access to draft versions in a GitBook space When a GitBook space is configured as public, users can publish a specific version while keeping others as drafts. The platform does not provide a built‑in option to hide those draft URLs from unauthenticated visitors, meaning anyone who knows or guesses the draft link can view the content. Thi
The goal is to allow consumers of a NuGet package to revert to a non‑breaking version after a breaking schema change without having to manually edit version constraints in their project or lock files. NuGet treats each published version as immutable, so rollback depends entirely on the consumer’s version range and any lock‑file constraints. The documented op
Our project uses semantic-release with Conventional Commits, and we need to ship a bug fix to users still on the 1.x line while main has already moved to 2.x. The documented options are a maintenance branch (e.g., 1.x ) that publishes real patch versions, or a prerelease branch (e.g., beta ) that publishes dist-tagged prereleases consumers must opt into. Dur
Our team maintains a published Figma library of components, styles, and variables that dozens of product files consume. When a maintainer publishes changes, each consuming file shows an update-available badge, and applying the update is a per-file, manual action from the library update dialog. Figma offers no built-in schedule, auto-apply, or per-file versio
readthedocs
git
gitbook
nuget