Choose between cmi5 and SCORM packaging and model a course using cmi5's Assignable Unit / block course structure

Steps

1. Understand that unlike a SCORM package, which bundles the actual content files with its manifest, a cmi5 package's cmi5.xml course structure file only describes and references Assignable Units (AUs) — the content itself can be hosted anywhere, not just on the LMS.
2. Model the course as nested block container elements holding one or more au (Assignable Unit) elements in cmi5.xml, rather than SCORM's flat organizations/items manifest tree.
3. Set a moveOn criterion (e.g. completed, passed, completedAndPassed) on each AU instead of relying on SCORM-style sequencing rules — cmi5 deliberately excludes sequencing/navigation rules from the course structure itself.
4. Package the cmi5.xml plus any local assets as a zip archive, using Zip64 packaging if the archive is large enough to exceed standard Zip32 limits.
5. At runtime, launch each AU with xAPI launch parameters (endpoint, auth token, registration, activityId) rather than the SCORM RTE JavaScript API — progress tracking flows through xAPI statements, not LMSSetValue/LMSCommit calls.