Open course authoring
A practical way to build SCORM courses with AI and real project files
A lot of SCORM work still ends with a ZIP file and very little visibility into how the course is put together. That can be fine for small edits. It gets frustrating when a team wants AI help, reviewable changes, reusable patterns, or a reliable way to check what changed before an LMS upload.
CourseCode takes a different approach: keep the course in regular project files, let AI tools work against the real preview and source, and package it for SCORM, cmi5, or LTI only when the course is ready to deliver.
The problem with course files you cannot review
Course production often comes down to basic questions: what changed, why did the layout break, which interaction reports completion, and can this pattern be reused in another course?
Course teams should be able to review a change before it ships, compare versions, run checks, and understand how their content becomes a SCORM, cmi5, or LTI package.
AI needs real course context
Better course checks come from working against the same thing a learner will use. An AI assistant should be able to inspect files, open the preview, capture screenshots, check interactions, and report problems before a package goes to the LMS.
CourseCode Framework stores a course as local project files and includes MCP tooling for preview inspection, screenshots, navigation, interaction tests, and AI-assisted authoring checks during development.
SCORM should be an output, not the authoring model
SCORM still matters because many organizations and LMS platforms depend on it. But SCORM is a delivery format, not a good mental model for course creation. Teams should author once and package for the LMS format they need: SCORM 1.2, SCORM 2004, cmi5, or LTI.
That is the CourseCode model: build in regular project files, preview locally with LMS simulation, then export or deploy in the format your environment requires.
What changes for a course team
When course source is file-based, instructional designers, developers, reviewers, automation, and AI assistants can work from the same project. A developer can automate checks. An instructional designer can use CourseCode Desktop for a visual editing path. A team can use CourseCode Cloud when it needs hosted previews, licensing, analytics, or LMS package downloads.
The framework remains the course engine. Desktop and Cloud are optional ways to work with the same course format.
Where to start
If you are evaluating CourseCode because you want more control over course source, start with the open course authoring guide.
If your immediate goal is LMS output, start with SCORM course authoring. If you want a GUI, use CourseCode Desktop. If you need hosted delivery, use CourseCode Cloud.
You can see a live CourseCode course here: View the CourseCode demo course.
Related reading
The best starting point depends on whether you want to install the framework, build a SCORM package, or try the desktop app.