Skip to main content

Title: Export Knowbys as SCORM-Compliant Packages (SCORM 1.2 / 2004)

Feature Request

Description:

Enable admins to export one or more knowbys as SCORM-compliant ZIP packages, compatible with SCORM 1.2 and/or SCORM 2004. This would allow organisations to integrate Knowby content into legacy Learning Management Systems (LMSs) that require SCORM-format content.

Functionality:

  • Export selected knowby(s) as a SCORM ZIP package

  • Generate the required imsmanifest.xml and launchable HTML content

  • Option to track basic SCORM fields:

    • Completion status (e.g. viewed to the end)

    • Pass/fail status (e.g. optional user confirmation step)

    • Time spent in the module

Limitations (Due to SCORM Itself, Not Knowby):

  • Static content only: SCORM doesn’t support dynamic content updates — any edits to the knowby after export won’t appear unless re-exported.

  • Limited analytics: SCORM can only report basic data like completion or time — advanced Knowby metrics won’t be available.

  • No real-time collaboration or approvals: SCORM doesn’t support features like approval workflows, version history, or user interactions.

  • Translation limitations: SCORM doesn’t support dynamic language switching or translation verification.

  • Device responsiveness may vary: SCORM relies on how the LMS renders the content — some platforms may not display Knowby content optimally, especially on mobile.

Why this matters:

While SCORM is over 20 years old and no longer evolving, some organisations still rely on SCORM for LMS integration and procurement compliance. Offering a lightweight SCORM export option would help meet these needs — while still recommending deep linking or embedding for the full Knowby experience.

Status: Rejected1 comment

Log in to comment and vote

Comments1

  • Clint Collins

    Team•

    Jul 3

    Knowby is built around live, always-current guidance — not static training modules — so we've made a deliberate choice not to offer SCORM export. SCORM is a 20+ year-old standard designed for one-time e-learning content: once exported, that content is frozen, so any update you make in Knowby afterward wouldn't be reflected unless you re-exported and redistributed it all over again. It also only captures basic completion and pass/fail data, which doesn't do justice to the rich, real-world execution insight Knowby is designed to give you.

    Rather than investing in a legacy format that's no longer evolving, we're focused on modern, open integration standards like MCP (Model Context Protocol) — which lets Knowby connect directly and dynamically with the systems you already use (ERP, EAM, HRIS, and AI-driven tools), keeping your guidance content live, accurate, and actionable wherever your team accesses it. Our goal is to make sure you're always working from the most current version of a procedure, not a snapshot that can quietly go out of date.

    If SCORM compatibility is a procurement requirement on your end, we're happy to talk through options like deep linking or embedding Knowby content within your existing LMS, which keeps the experience live while still meeting your integration needs.