Wagtail LMS
A Learning Management System extension for Wagtail CMS with SCORM 1.2/2004 and H5P support.
⚠️ Alpha Release
This package is in early development. That said, it is actively used in production at thinkelearn.com.
Supported versions:
- Python: 3.11, 3.12, 3.13, 3.14
- Django: 4.2 (LTS), 5.0, 5.1, 5.2 (LTS), 6.0, 6.1
- Wagtail: 6.0, 6.2, 6.3, 7.1, 7.2, 7.4 (LTS), 8.0
Selected combinations are tested in CI. See our compatibility matrix for specific version combinations.
Features
- 📚 Course Management - Integrate courses into Wagtail's page system
- 📦 SCORM Support - Full SCORM 1.2 and 2004 package compatibility
- 🎯 H5P Support - Embed interactive H5P activities in long-scroll lesson pages
- 👥 Enrollment Tracking - Automatic student enrollment and progress monitoring
- 📊 SCORM API - Complete runtime API implementation for content interactivity
- 📡 xAPI Tracking - Record H5P learner interactions as xAPI statements
- 🔒 Secure Delivery - Path-validated content serving with iframe support
- 💾 Progress Persistence - CMI data model storage with suspend/resume capability
- 🔄 Concurrency Handling - Retry logic for SQLite database lock scenarios
- 🎨 Framework Agnostic - Minimal default styling, easy to customize with any CSS framework
Installation
pip install wagtail-lms
Quick Start
-
Add to
INSTALLED_APPSin your Django settings:INSTALLED_APPS = [ # ... "wagtail_lms", # ... ]
-
Add wagtail-lms URLs to your
urls.py:from django.urls import path, include urlpatterns = [ # ... path("lms/", include("wagtail_lms.urls")), # ... ]
-
Run migrations:
python manage.py migrate wagtail_lms
-
Collect static files:
python manage.py collectstatic
Configuration
Optional settings in your Django settings:
WAGTAIL_LMS_AUTO_ENROLL = False # Auto-enroll on course visit
# SCORM
WAGTAIL_LMS_SCORM_UPLOAD_PATH = "scorm_packages/" # Upload directory
WAGTAIL_LMS_SCORM_CONTENT_PATH = "scorm_content/" # Extracted content
# H5P
WAGTAIL_LMS_H5P_UPLOAD_PATH = "h5p_packages/" # Upload directory
WAGTAIL_LMS_H5P_CONTENT_PATH = "h5p_content/" # Extracted content
# Cache-Control rules for served assets (exact MIME, wildcard, and default)
WAGTAIL_LMS_CACHE_CONTROL = {
"text/html": "no-cache",
"text/css": "max-age=86400",
"application/javascript": "max-age=86400",
"text/javascript": "max-age=86400",
"image/*": "max-age=604800",
"font/*": "max-age=604800",
"default": "max-age=86400",
}
# Redirect audio/video assets to storage URLs (useful for S3 backends)
WAGTAIL_LMS_REDIRECT_MEDIA = False
# Use custom Wagtail admin viewsets for upload flows
WAGTAIL_LMS_SCORM_PACKAGE_VIEWSET_CLASS = "wagtail_lms.viewsets.SCORMPackageViewSet"
WAGTAIL_LMS_H5P_ACTIVITY_VIEWSET_CLASS = "wagtail_lms.viewsets.H5PActivityViewSet"
WAGTAIL_LMS_H5P_SNIPPET_VIEWSET_CLASS = "wagtail_lms.viewsets.H5PActivitySnippetViewSet"
# Lesson access hook (dotted-path callable)
WAGTAIL_LMS_CHECK_LESSON_ACCESS = "wagtail_lms.access.default_lesson_access_check"
# Django admin registration controls
WAGTAIL_LMS_REGISTER_DJANGO_ADMIN = True
WAGTAIL_LMS_SCORM_ADMIN_CLASS = "wagtail_lms.admin.SCORMPackageAdmin"
WAGTAIL_LMS_H5P_ADMIN_CLASS = "wagtail_lms.admin.H5PActivityAdmin"
Usage
SCORM Courses
- Log into Wagtail admin
- Create a new Course Page under Pages
- Upload a SCORM package via LMS → SCORM Packages in the Wagtail admin
- Add a SCORM Lesson Page as a child of the Course Page and assign the SCORM package to it
- Publish — enrolled learners can access the lesson from the course page
SCORM package requirements:
- Valid SCORM 1.2 or 2004 ZIP file
- Must contain
imsmanifest.xmlat the root - Launch file must be specified in the manifest
H5P Lessons
H5P activities are composed into long-scroll H5P Lesson Pages alongside rich text. A lesson is always a child of a Course Page; enrollment in the course is required to access its lessons.
- Upload an H5P Activity snippet via LMS → H5P Activities in the Wagtail admin
- Create a Course Page (no SCORM package required for H5P-only courses)
- Add an H5P Lesson Page as a child of the Course Page
- In the lesson body, add H5P Activity blocks (and/or rich text blocks) to compose the lesson
- Publish — enrolled learners can access the lesson; xAPI statements are recorded automatically
H5P package requirements:
-
Valid
.h5pfile (ZIP with an.h5pextension) containingh5p.jsonat the root -
Must include library JavaScript files — h5p-standalone renders content using library JS bundled inside the package (e.g.
H5P.InteractiveVideo-1.27/). A warning is logged and "Could not load activity." is shown if files are missing.- ✅ Lumi desktop editor (free, open-source) — recommended
- ✅ Moodle / WordPress / Drupal H5P plugin export
- ✅ Lumi Cloud (free tier available at lumi.education)
- ❌ H5P.org "Reuse" download — content-only, no library files included
- ❌ H5P.org does not offer a download-with-libraries option for any content
Customizing Templates
The package includes minimal, functional styling that works out of the box. To match your project's design:
- Quick: Override the CSS classes in your own stylesheet
- Full control: Override the templates in your project (standard Django approach)
- Examples: See Template Customization for Bootstrap, Tailwind CSS, and Bulma examples
For API-first projects, the templates are optional and can be ignored entirely.
Development
An example project is available in example_project/ for local development and testing. See its README for setup instructions.
Running Tests
uv sync --extra testing
PYTHONPATH=. uv run pytest
PYTHONPATH=. uv run pytest --cov=src/wagtail_lms --cov-report=term-missing
See the Testing Guide for full details, including writing new tests and CI configuration.
Database
SQLite works for development (the package includes retry logic for concurrent SCORM operations). PostgreSQL is recommended for production. See the example project README for configuration examples.
Acknowledgments
- Built with Django and Wagtail CMS
- SCORM implementation based on ADL specifications
- H5P support powered by H5P and h5p-standalone
- Lumi — recommended free, open-source H5P editor for creating self-contained packages
- Inspired by open-source LMS solutions like Moodle and Open edX
License
This project is licensed under the MIT License. See the LICENSE file for details.
Metadata
Release files for wagtail-lms 0.11.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| wagtail_lms-0.11.1.tar.gz | 622.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wagtail_lms-0.11.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 MB
Release files / wagtail_lms-0.11.1.tar.gz
| Download URL | wagtail_lms-0.11.1.tar.gz |
|---|---|
| Size | 622.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1cb9b5e92451a65eda551efa3bb493b0ecabf1a08dd11f066bbb1eef07d9dcb
|
|
BLAKE2b-256 checksum How to use checksums |
8afc9116c75719e7c4db9554f42bbd8dcae1ef50eeb4fdfd57e7e3e81e77306b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.
Transparency logRelease files / wagtail_lms-0.11.1-py3-none-any.whl
| Download URL | wagtail_lms-0.11.1-py3-none-any.whl |
|---|---|
| Size | 659.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8cee7f8c5f3677dde0554f30ceb6b18f4a3b0b27a0e1a66ceb60e0e0034f33e4
|
|
BLAKE2b-256 checksum How to use checksums |
81e148239d94ee436f85ad09129d851512265652fcea692a4764c7ec2cc04e19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.
Transparency logSecurity for wagtail-lms 0.11.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for wagtail_lms-0.11.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.