Everything we know about Cornerstone on Demand and Storyline!

We publish as HTML5 with Flash backup primarily because of the industry-wide assumption that Flash is being phased out and in part because Google Chrome is making running Flash a gradually worse and worse user experience (e.g. showing a puzzle piece and making the user indicate they want to run Flash), and also in part because of the conventional wisdom that Flash is a major security risk. Also, our IT dept has enabled font downloads so we no longer have  issues with fonts not downloading in HTML5 content, at least for our users on our company computers.

Having said that, it seems like Google likes to change their rules for rendering HTML5 in Chrome so often that I've began to wonder if it is really is a step up from Flash. For example, Google has decided to stop HTML5 from being able to autoplay audio in some, but not all cases (making it essentially untestable), which Articulate helpfully reacted to by adding a play button to the landing page of newly published content, but which means our old already published HTML5 content now has to be updated to avoid muted audio on initial slides. And it seems like over the last couple years things that once worked in HTML5 gradually stop working as HTML5 seems to constantly evolve (did it ever really come out of beta?). And yet we soldier on publishing in HTML5 because it still seems to be the lesser of two evils.

Regarding updating a course... we don't inactivate courses we are updating but instead use the new Course Uploader to either create a new version of a course or modify a course. If we can get away with using Modify we always pick it as it is much less work.