The Domain Map
Demand • Design • Product • Governance • Runtime • Guidance
The Domain Map covers six domains across the digital learning lifecycle. Their English names are used consistently across the platform, documentation and software.
|
Domain |
Description |
|---|---|
|
Demand — What need should the learning experience address? |
Defines the need behind a learning experience: its audience, capability requirements, skill gaps, learning objectives, subject-matter sources, evidence and learning strategy. For example, compliance training should do more than convey information; it should improve specific decisions at work. Demand defines those decisions and how success will be measured. |
|
Design — What will make an effective learning journey? |
Turns the subject-matter basis into a learning architecture, outline, storyboard, activities and blueprint. Learning objectives become chapters, tasks, reflection points, interactions and a coherent journey. |
|
Product — What will be produced? |
Covers the learning content itself: modules, pages, assets, content blocks, interactive activities, simulations and other components. A storyboard becomes a usable digital module with interactions, media and delivery formats. |
|
Governance — What is reviewed and approved? |
Provides controlled review, comments, approval, versioning and traceability. Subject-matter experts review the content, legal reviewers provide guidance, editors make corrections and the final release is documented. |
|
Runtime — What happens during use? |
Captures and evaluates learning activity, including sessions, progress, interactions and analytics. It shows where learners drop out, take longer than expected or repeatedly revisit content. |
|
Guidance — How should we respond? |
Uses learner behaviour and context to provide support, recommendations or interventions. The learning companion can recognise difficulty with a topic and suggest a focused explanation or review activity. |
- Domain
Demand — What need should the learning experience address?
- Description
Defines the need behind a learning experience: its audience, capability requirements, skill gaps, learning objectives, subject-matter sources, evidence and learning strategy. For example, compliance training should do more than convey information; it should improve specific decisions at work. Demand defines those decisions and how success will be measured.
- Domain
Design — What will make an effective learning journey?
- Description
Turns the subject-matter basis into a learning architecture, outline, storyboard, activities and blueprint. Learning objectives become chapters, tasks, reflection points, interactions and a coherent journey.
- Domain
Product — What will be produced?
- Description
Covers the learning content itself: modules, pages, assets, content blocks, interactive activities, simulations and other components. A storyboard becomes a usable digital module with interactions, media and delivery formats.
- Domain
Governance — What is reviewed and approved?
- Description
Provides controlled review, comments, approval, versioning and traceability. Subject-matter experts review the content, legal reviewers provide guidance, editors make corrections and the final release is documented.
- Domain
Runtime — What happens during use?
- Description
Captures and evaluates learning activity, including sessions, progress, interactions and analytics. It shows where learners drop out, take longer than expected or repeatedly revisit content.
- Domain
Guidance — How should we respond?
- Description
Uses learner behaviour and context to provide support, recommendations or interventions. The learning companion can recognise difficulty with a topic and suggest a focused explanation or review activity.
Cross-functional capabilities
Four cross-functional capabilities span the six domains.
|
Cross-functional capability |
Description |
|---|---|
|
Supports research, learning design, storyboarding, review, translation, analysis and guidance. AI remains connected to learning objectives, subject-matter context, review rules and usage data rather than operating in isolation. |
|
|
Localisation |
Begins before the text is final and covers audiences, terminology, examples, media, variants and review processes. Language versions remain connected to the same content, structure, status, approval and release. |
|
Legacy Content Operations |
Manages existing SCORM content as a coherent body of legacy content. Its value lies not simply in import, but in inventory, controlled delivery, patching, translation, review and versioning—and in deciding which content to retain, modernise, migrate or replace. |
|
Delivery |
Connects production, content management and delivery. It covers output formats, LMS/LTI integration, hosted launches, versions and variants, and links usage data to the precise version delivered. |
- Cross-functional capability
AI
- Description
Supports research, learning design, storyboarding, review, translation, analysis and guidance. AI remains connected to learning objectives, subject-matter context, review rules and usage data rather than operating in isolation.
- Cross-functional capability
Localisation
- Description
Begins before the text is final and covers audiences, terminology, examples, media, variants and review processes. Language versions remain connected to the same content, structure, status, approval and release.
- Cross-functional capability
Legacy Content Operations
- Description
Manages existing SCORM content as a coherent body of legacy content. Its value lies not simply in import, but in inventory, controlled delivery, patching, translation, review and versioning—and in deciding which content to retain, modernise, migrate or replace.
- Cross-functional capability
Delivery
- Description
Connects production, content management and delivery. It covers output formats, LMS/LTI integration, hosted launches, versions and variants, and links usage data to the precise version delivered.
The platform
Learning experience management
Much digital learning content is still delivered as SCORM packages through an LMS. Learners may not notice a problem, but every content update adds complexity for the L&D team.
Even a small change can mean reopening the source file, editing the content, exporting it again, uploading it to the LMS, testing it, approving it and replacing the correct course version. The same process applies to subject-matter corrections, new media, additional languages and regulatory updates.
This content remains valuable. It may include mandatory and compliance training, product training, onboarding modules or highly produced learning programmes. The challenge is to maintain, review and improve it efficiently while it remains in use.
The BLX Learning Experience Management System (LXMS) helps L&D teams manage both existing and new learning content centrally. It makes versions traceable, coordinates translations and reviews, and controls delivery. SCORM packages can remain in use without turning every update into a bespoke manual process.
The BLX solution is built on TYPO3, a proven content-management platform. Editorial workflows, roles and permissions, versioning, multilingual content, responsive delivery and a flexible extension architecture all support the day-to-day management of digital learning content.
Organisations retain long-term control of their learning content. They reduce dependence on individual tools, continue to use existing web, learning and identity systems, and modernise their content in manageable stages.
From CMS to LXMS
Combining structured content, xAPI/cmi5, an LRS and LTI turns TYPO3 into more than a content management system. It becomes a platform for producing and delivering interactive, adaptive and measurable learning content.
Editorial teams work across fewer disconnected systems and gain greater control of their legacy content. They can create new content in the LXMS and manage existing material within the same lifecycle. Changes, translations, media replacements, reviews and re-releases become versioned updates rather than isolated file operations.
This open architecture complements an organisation’s existing LMS landscape while providing greater control over content, versions and data. Moving from CMS to LXMS is not simply a technology upgrade; it changes how digital learning content is managed—from one-off export packages to version-controlled, deliverable and measurable assets.
Why use a CMS as the foundation?
Choosing the foundation for a Learning Experience Management System is both a technical and a strategic decision. For a long-term learning platform, maintainability, extensibility, digital sovereignty and integration are essential.
TYPO3 provides a reliable foundation. This open-source content management system is designed for scalable, long-lived web platforms and maintained through Long Term Support (LTS) releases. That matters to organisations with demanding requirements for stability, governance and sustainable architecture.
TYPO3 integrates flexibly with existing infrastructure and runs on established open-source components including MariaDB, MySQL, PostgreSQL, Apache, Nginx, PHP and JavaScript. Its interfaces and extension points support REST APIs, single sign-on, translation services, media sources and AI services.
This openness is central to Legacy Content Operations. Existing packages, media, language versions, metadata, review states and delivery channels do not have to disappear into a proprietary authoring tool. The LXMS can manage them as objects, files, releases or references, supported by TYPO3’s file management, permissions, workflows, multilingual capabilities, versioning and integration with existing identity and LMS systems.
TYPO3 also has a broad ecosystem of specialist agencies and developers, supported by both free and commercial extensions. Organisations can expand the platform gradually without replacing the underlying architecture or committing to a proprietary end-to-end system.
TYPO3 also has an established role in the public sector. Germany’s Government Site Builder uses TYPO3 and supports requirements including responsive design, GDPR compliance and accessibility under BITV 2.0. The LXMS therefore shares the open, interoperable and sustainable foundation used by modern public information and service platforms.
Interactive content in the LXMS
The LXMS supports a wide range of interactive formats, including interactive video, quizzes, drag-and-drop activities, branching scenarios, dialogue cards and learning journals.
Interactive content is managed within the page and module structure rather than as a disconnected add-on. Central styles control fonts, colours, spacing and layouts so that every activity fits the organisation’s visual identity and the wider learning experience.
This goes beyond appearance. TYPO3 brings activities, video, text, navigation, progress and feedback together as one coherent learning experience rather than a collection of separate embedded tools.
From interactive activities to managed learning experiences
Interactive activities become more valuable when they retain their context. The LXMS connects them with persistent progress, evaluation, learning pathways and efficient translation workflows.
|
Interactive capability |
What the LXMS adds |
|---|---|
|
Interactive tasks and videos |
Embedded within the module structure, navigation and learning context |
|
Feedback on individual tasks |
Extensible feedback logic and context-sensitive guidance |
|
xAPI learning events |
Storage and analysis in the LRS, with dashboard reporting |
|
Saved progress within activities |
Support for resuming across sessions |
|
Individual activity types |
Learning paths, variants, test scenarios and reflection activities |
|
Standardised presentation |
Central styling through TYPO3, aligned with brand and accessibility requirements |
|
Multilingual content |
AI-assisted translation with change tracking, subject-matter review and approval for each language variant |
- Interactive capability
Interactive tasks and videos
- What the LXMS adds
Embedded within the module structure, navigation and learning context
- Interactive capability
Feedback on individual tasks
- What the LXMS adds
Extensible feedback logic and context-sensitive guidance
- Interactive capability
xAPI learning events
- What the LXMS adds
Storage and analysis in the LRS, with dashboard reporting
- Interactive capability
Saved progress within activities
- What the LXMS adds
Support for resuming across sessions
- Interactive capability
Individual activity types
- What the LXMS adds
Learning paths, variants, test scenarios and reflection activities
- Interactive capability
Standardised presentation
- What the LXMS adds
Central styling through TYPO3, aligned with brand and accessibility requirements
- Interactive capability
Multilingual content
- What the LXMS adds
AI-assisted translation with change tracking, subject-matter review and approval for each language variant
Persistent progress is particularly valuable. If learners leave an activity, they can resume from their previous state. This makes longer modules easier to fit around everyday work and provides continuity between sessions.
The LXMS also provides greater control over assessment scenarios. Activities can be combined into pools, variants and differentiated tests, while the platform manages complex randomisation and cross-module logic.
The same principle applies to existing content. Packages and media remain connected to learning journeys, releases, language versions and operational decisions, creating one lifecycle context for both new and legacy content.
Learning pathways, reflection and reuse
The LXMS is particularly valuable when a learning experience extends beyond individual pages or activities. Modular content can be reused and assembled differently for each audience, reducing maintenance and simplifying future updates.
This also opens up new learning-design options. A learning journal can retain entries across modules; notes can collect selected passages for later reflection; and response comparisons can show learners how their assessment relates to those of others.
Adaptive pathways are also possible. Learners who demonstrate confidence can move to more challenging content or skip basic material, while those who struggle receive further explanations, revision or alternative activities. Individual activities provide the interaction; the LXMS connects them into a coherent journey.
xAPI, cmi5, LRS and LTI 1.3
Much of the LXMS’s value sits below the surface. xAPI and cmi5 record learning activities as measurable events, including answers, video interactions, time on task, repeated attempts, exit points, scores, progress, notes and PDF annotations.
A Learning Record Store (LRS) holds this data for analysis, dashboards and reporting. It shows how learners engage with content: which activities they repeat, where they stop watching a video, which sections take unusually long and which interactive elements they use.
The integrated LRS and LTI 1.3 connector extend these capabilities. Native LXMS content can run within an existing LMS without being shipped as a fixed package. Existing SCORM content can remain operational while new delivery and tracking models are introduced gradually.
This is not an either-or architecture. The LMS remains the organisational system for courses, participants and certificates. The LXMS manages the learning content itself—its structure, storyboards, variants, reviews, delivery and detailed usage data.
Data protection and data minimisation
Detailed learning-history data brings greater responsibility for personal information. Before xAPI statements are stored in the LRS, organisations should define what data is needed, for which purpose, how long it will be retained and whether it must be pseudonymised or anonymised.
Tracking should be proportionate to the use case. Aggregated usage data may be sufficient for some courses and learning programmes, while others need more detailed progress patterns for formative support, evaluation or evidence requirements.
The entire data chain—LMS, LXMS, LRS, authentication, reporting and deletion—must be considered together. Data protection is part of the system architecture, not a compliance check added at the end.