Practical writing on SCORM and xAPI
Independent, opinionated, no vendor pitches. Notes from someone who builds SCORM packages and is tired of the marketing version of the answer.
Why authoring tools hide the SCORM API from you, and what you can do about it
An honest look at the gap between what SCORM 1.2 actually offers and what authoring tools let you reach.
Read post →How to test a SCORM package before sending it to a client
A practical testing routine for SCORM packages. Catches the failure that would otherwise have embarrassed you.
Read post →The tool wrote the code. Who owns the course?
When an AI writes your HTML course, who owns it? The answer is more complicated than your vendor's terms of service suggests.
Read post →The minimum viable SCORM manifest, explained line by line
The smallest valid SCORM 1.2 imsmanifest, explained without the historical detours.
Read post →Why your SCORM package works in SCORM Cloud but not in your client's LMS
A practical debugging guide for the most universal frustration in instructional design.
Read post →Is Storyline dead? Short answer no, longer answer it depends what you are paying for
No, Storyline is not dead. But that is not really the question being asked, and the real one is more interesting.
Read post →xAPI versus SCORM 1.2 in 2026, an honest comparison
xAPI was supposed to replace SCORM years ago. SCORM 1.2 is still what every LMS actually runs on. Here is the honest version of why.
Read post →What SCORM actually tracks
A short, practical guide for anyone who has ever sworn at an LMS upload screen.
Read post →Want to try the tool the blog is from?
Private beta. Drop in an HTML file or folder, get back a SCORM 1.2 zip in seconds.
Request access