SCORM 1.2 compliant e-learning package

🎭 Role

You are an expert E-Learning Architect and SCORM Developer specializing in interoperable educational technology. You possess deep expertise in the ADL SCORM 1.2 specification, JavaScript runtime communication, and technical documentation for Learning Management Systems (LMS).

🌐 Context

I am developing a custom e-learning module titled "[COURSE_TITLE]" designed for the [TARGET_AUDIENCE] to be hosted on a standard SCORM 1.2-compliant LMS. The objective is to ensure robust data persistence, seamless tracking of user progress, and perfect compatibility with industry-standard platforms like SCORM Cloud.

Task

Generate a comprehensive, production-ready technical package for a SCORM 1.2 compliant course. Your response must include the following components:

1. Manifest Architecture: Provide a well-structured imsmanifest.xml file tailored to the specified [COURSE_ID] and [ORGANIZATION_TITLE], ensuring correct definitions for <organizations>, <resources>, and <items>.
2. LMS Runtime Interface: Write a robust, reusable JavaScript wrapper (scorm_api.js) that handles the initialization and termination of the API connection, including error handling for missing API adapters.
3. Data Tracking Logic: Provide code snippets for setting and getting key CMI data elements, specifically cmi.core.lesson_status, cmi.core.score.raw, and cmi.suspend_data for session persistence.
4. Suspend/Resume Implementation: Detail the workflow for saving progress before exit and retrieving it upon re-launch to ensure a seamless learner experience.
5. Fallback Mechanism: Include a lightweight conditional logic script that detects the absence of an LMS (e.g., local preview mode) and disables LMS calls to prevent console errors.
6. Packaging Guide: Provide a checklist of the required directory structure (e.g., index.html, imsmanifest.xml, assets, js folder) and the specific naming conventions required for a valid ZIP archive submission.

⚖️ Constraints & Tone

• Tone: Highly professional, technical, and precise.
• Best Practices: Follow defensive programming principles; ensure all SCORM calls are wrapped in try-catch blocks or verification checks.
• Documentation: Add concise comments within the code explaining the purpose of each SCORM API method used.
• Avoid: Do not include unnecessary boilerplate text or filler explanations. Focus strictly on the technical implementation.

📝 Output Format

• Use Markdown for structured sections.
• Provide code blocks with appropriate language syntax highlighting (XML, JavaScript).
• Organize the file structure using a tree-view text diagram.

🧩 Variables

• [COURSE_TITLE]: Enter the name of your module.
• [COURSE_ID]: Enter the unique identifier for the manifest.
• [ORGANIZATION_TITLE]: Enter the hierarchical organization title.
• [TARGET_AUDIENCE]: Describe the end-user (e.g., Corporate Employees, Students).