What is the eLearning Design System?
A reusable system of learning principles, visual foundations, experience patterns, components, platform standards and governance for coherent digital learning experiences.
Purpose
- Create a coherent learner experience across platforms and course types.
- Reduce reinvention through documented patterns, components and shared production standards.
- Improve delivery speed, accessibility, maintainability and readiness for future brand change.
Audiences
| Audience | What the system provides |
|---|---|
| Executives & sponsors | Strategic direction, scope, governance model and investment rationale. |
| Designers & developers | Learning patterns, components, implementation standards, versioning and technical references. |
| Subject matter experts | A clearer explanation of how content is structured and why particular patterns are used. |
| Platform administrators | A consistent model for applying the system within Moodle, Rise and future tools. |
System architecture
| Layer | What it governs | What it does not contain |
|---|---|---|
| Core system | Learning intent, foundation roles, patterns, component contracts and governance. | Organisation-specific branding or platform code. |
| Implementation | Theme values, technical namespace, platform behaviour and production assets. | Course-specific approved copy or scenarios. |
| Course application | Source-controlled content, sequence, scenarios, media and release evidence. | Unreviewed changes to the reusable system. |
Implementations
The core is deliberately neutral. Organisation and platform decisions live in named implementation layers so they can evolve without redefining the system. The implementation directory records the available themes, platforms and current production evidence.
Maturity and roadmap
The system has moved from course-by-course discovery to formal consolidation. Its first implementation was proven through a substantial child-protection course family. This site represents Roadmap Phase 5 — Document and demonstrate — reached ahead of the completed audit and accessibility gate, so several entries are marked accordingly. See Governance for the full lifecycle model and current open decisions.
How to use this site
Executives and sponsors: read this Overview and Governance. Designers: start with Learning design and Learning patterns. Developers: use Components, then enter the relevant Implementation for production detail. Reviewers: use the accessibility fields on each component page and the checklists under Resources.