Forum Discussion
Keeping SCORM package small, best practices?
Are they any documents or guides that already exist for best practices while designing in Rise to ensure you don't end up with a massive SCORM file at the end? If not, can anyone add to this list ...
This might not be feasible if you have an interconnected asset like branched learning, but we tend to break up our courses into multiple SCORMs. This is because our LMS has a hissy fit when anything gets too big (what that size is is anyone's guess) and won't save progress after a certain point.
You can think of the course as a book, with each SCORM serving as a chapter, and each Rise lesson or Storyline module acting as a section. This also helps keep your files manageable when it comes to updating.