When to version, when to skip
When to maintain a named documentation version alongside current docs.
Keep a named documentation version when customers still use an older product release with different instructions. For a continuously updated product, current docs plus a changelog are often simpler.
The case for versioning
Use separate editions when an API, SDK or product release changes setup or behavior and customers cannot all move immediately. Each edition should explain the product version it supports.
The case against
Every tagged version is another copy to maintain. A correction to current docs does not automatically update older editions. Avoid creating a separate edition for every small typo or routine product update.
When to skip, what to do instead
Update current docs and describe changes in a dated changelog. Mark deprecated behavior where readers encounter it and link to the replacement. Use publication history for recovery rather than exposing every saved state as a reader-facing version.
Setting it up in Docsio
Use Tag Doc Version in the editor toolbar and give the edition a clear, unique name. Publish to make it available. Current sites use /docs/versions/NAME for archived editions alongside current docs.
Keep versions useful
Check links and search inside each edition. Tell readers when they are viewing an older release and link to the current instructions. Keep only editions you can maintain, and make a deliberate plan before removing public version URLs.