It would be very useful if Skilljar could allow us to version content, including restoring previous versions and surfacing different versions of content to learners.

We have two use cases that would greatly benefit from content versioning and might require different solutions.

1. Restoring courses or lessons
   1. It’s currently possible to, for example, accidentally delete an entire text lesson, save the lesson, and then be unable to retrieve the lost content.
   2. This can also happen when two Dashboard users edit the same lesson and overwrite each other’s changes.
   3. Support for viewing and restoring previous versions could fix this risky situation. Google Doc’s Version History interface is a good model for this.
   4. This is a more “automatic” approach to versioning.
2. Surfacing content that matches learners’ software version.
   1. Our desktop and server products use a traditional versioned release model. This fact means our courses have to correspond to a specific release. Learners ideally take the training using the exact version matching the course content so that the UI and functionality match exactly. They cannot even take the newer training if they have an older version because the provided instructions and example files will not be compatible.
   2. Therefore, we’d like to support surfacing different versions of content to users. This feature is common in software documentation. For example, click Other Versions on this page: https://pro.arcgis.com/en/pro-app/latest/arcpy/main/arcgis-pro-arcpy-reference.htm.
      1. Most solutions support this use URLs to indicate which version is being used. These names are usually branches or releases in a version control system.
      2. https://pro.arcgis.com/en/pro-app/latest/arcpy/main/arcgis-pro-arcpy-reference.htm
      3. https://pro.arcgis.com/en/pro-app/3.4/arcpy/main/arcgis-pro-arcpy-reference.htm
   3. Our current workaround uses course names, tags, and published course URLs to let users choose which training version to take. But we know learners struggle to find the right content, particularly when using an older software version.
   4. This is a more manual approach to versioning.