In the last lesson in this SCORM for Developers series, we dipped our toes in the water and created the most barebones SCORM course possible. In this lesson, we’ll wade a little deeper, adding sophistication to the course via a smattering of JavaScript and HTML. We’ll use cmi.
Let’s roll up our sleeves and create a minimalist SCORM 1.2 course! This will be a fast and loose example, containing only the bare minimum of SCORM code and not much else. I will be moving quickly, but don’t worry if you don’t grasp all of
SCORM has been around for 20+ years, and the ecosystem has matured to the point where we can make certain assumptions about vendor support. Commercial course creation tools like Adobe Captivate, Articulate Rise, and iSpring are hyper-focused on broad compatibility with as many LMSs as possible. Acknowledging they couldn’t
For the purposes of course development, you will need to learn how to work with three components: the SCORM API, the CMI data model, and the course manifest (imsmanifest.xml). Here’s a quick overview of each component. I will provide real-world examples later in this series. The SCORM API
The Shared Content Object Reference Model (SCORM) is a system for standardizing how e-learning courses interact with a learning management system (LMS). In the mid-1990s, the Internet — still spelled with a capital “I” — was booming, and new learning management systems were popping up left and right. The LMS ecosystem was