Hello all,This is kind of a half-baked idea that I want to throw out to the community for discussion and input. I'm sure that experienced users out there have some discipline around creating multiple versions/iterations of a course as they are developing. I'm wondering if some of these procedures could be built into Lectora. I know that Lectora currently has the "Save a copy" of a title, but I'm thinking it could go a bit further. Here's what I'm thinking:For example, when you create a new title (called Sample Course), Lectora could tack on a version number. Lectora would create a project called "Sample Course 01.00" When you go to publish to SCORM in a zip file, Lectora would create "Sample Course 01.00.zip" The next time you publish to SCORM, Lectora would create Sample Course 01.01.zip, the Sample Course 01.02.zip and so on. Same thing for HTML, EXEs and so on.When you're ready to create the next version of the project, you would "create new version" in Lectora. Lectora would copy whatever's in version 1.X and create a separate folder with a new course called "Sample Course 02.00.When you open Lectora and choose to open a title, you would open title "Sample Course." Lectora would then ask whether you wanted to open version 1 or version 2.Would you use something like this? Do you think something like this is needed? Do you have better suggestion for implementing version control within Lectora? Do you have version control practices that you can share? Interested in your opinions.
