Software Development
Docs Versioning Strategy
Decides how developer docs track several product, library or API versions - whether to version docs at all, which versions keep docs and in what state (next, current, maintained, frozen, archived), latest-only vs version switcher vs per-major archives, banners, retiring a docs version. Use whenever someone mentions versioned docs, a docs version switcher, archiving old docs, or readers on the wrong docs version - even without saying strategy. Do NOT use for old docs outranking current in search - use samber/developer-relations-skills@docs-seo; nor support windows - use samber/developer-relations-skills@oss-release-policy; nor upgrade guides - use samber/developer-relations-skills@version-migration-guide; nor API version schemes - use samber/developer-platform-skills@api-versioning-policy.
- Publisher / source
- samber/developer-relations-skills (found on skills.sh)
- Upstream record
- samber/developer-relations-skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication
- Content fingerprint
70c6b07687e5f7501b77860305a38edbc591669c955cd277026be4d85cbf453a