You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ability to serve multiple versions of docs to users from a single doc source.
Users select which doc version to view from the same URL. For example, on the front end, https://developer.rackspace.com/docs/ links to different versions of the same docs. On the back end, different versions are generated from the same source.
Why are multiple versions needed?
Users need clear, unambiguous support for their product version.
The Repose dev team states that their largest source of 1-to-1 support contacts is user confusion over versioned instructions presented side-by-side in dev docs.
Versioned docs can reduce 1-to-1 support contacts.
The Repose team is small; consequently, the team fills its support roster by rotating developers out of production and development.
The need for versioned docs will grow.
The Repose use case is not unique. As more Rackspace product teams migrate content to Nexus, the number of use cases for versioned docs will likely increase.
How might we support versioned docs?
Maybe by configuring automated build tools to support GitHub tags?
The text was updated successfully, but these errors were encountered:
What is needed?
The ability to serve multiple versions of docs to users from a single doc source.
Users select which doc version to view from the same URL. For example, on the front end,
https://developer.rackspace.com/docs/
links to different versions of the same docs. On the back end, different versions are generated from the same source.Why are multiple versions needed?
The Repose dev team states that their largest source of 1-to-1 support contacts is user confusion over versioned instructions presented side-by-side in dev docs.
The Repose team is small; consequently, the team fills its support roster by rotating developers out of production and development.
The Repose use case is not unique. As more Rackspace product teams migrate content to Nexus, the number of use cases for versioned docs will likely increase.
How might we support versioned docs?
Maybe by configuring automated build tools to support GitHub tags?
The text was updated successfully, but these errors were encountered: