Hey Sam! Thanks for sharing. Is this idea the same as the note in #1.2 in this idea from you? We’re tracking these closely with our product team so we’d love to merge these ideas if you feel it’s accurately reflected there! 

Hello ​@soniamoaiery. My two posts reflect several related requests about version control. It’s a pretty big topic. Feel free to merge them into one idea or keep them separate.

The overall idea is to support versioning for courses, learning paths, and quizzes. We currently duplicate all of these things to provide versioned content to our users. Our company creates versioned desktop and server software, and our users are on a wide variety of versions. To take our training using their own install, they need to be able to choose their version.

But our current system adds a large administrative overhead for publishing and analytics, and creates a very crowded course management page. (The course families feature might help clean this up on the back-end, but not on the customer side.) We’d prefer to be able to save versions and surface those to users. For example, publish a course family to a single URL, and users can choose which version to use from a drop-down. Then we can pull analytics from the top-level course (aggregate) or sub-courses.

Versioning in this way would also address the pain point of overwriting one another’s work or accidentally saving an incorrect version of a lesson. We have encountered both of those issues multiple times, losing valuable time.

Please let me know if you have any questionsl I’m happy to talk more. Thanks!