A course platform.
Built and tested in WordPress.
A small learning brand with a real course, a working learner account and a complete test journey from order to course completion. Built with a custom theme, Tutor LMS and WooCommerce.
The custom homepage uses imagery from our own fictional lamp concept. Open any screenshot to view it at full size.
From an order
to a place in the course.
A fictional £59 virtual product is linked to the Tutor course. The test uses manual approval: the pending order keeps lessons locked, and marking it completed in WooCommerce automatically grants enrollment.
WooCommerce's order transition triggered access through Tutor's integration.
No funds were transferred. A payment-provider integration was not part of this test.
The worksheet download checks enrollment and refuses a logged-out request.
Progress that stays.
A quiz that grades.
Each lesson uses Tutor's own completion control. Progress survived a reload. The native quiz recorded a failed 0/3 attempt and a passed 3/3 attempt; strict course completion refused the failed result.
A fictional lamp launch illustrates outcomes, deliverables and acceptance checks.
A six-second video reference and a plain-text worksheet support the lessons.
The completed course remained in the learner panel after a browser reload.
Built to be edited.
The real Course Builder contains the module, three lessons and three quiz questions. An administrator edit was saved through the native interface and verified on the course page.
A calmer page.
A usable learner panel.
The homepage and learner course card were checked at an actual 390px browser width. Both stayed within the screen without outer horizontal scrolling.
- Custom homepage and course presentation
- Student sign-in and persisted progress
- Manual test order to automatic enrollment
- Failed and passed native quiz attempts
- Editable course content in the admin builder
Clear about what this proves.
A tested local foundation.
This demonstration verifies the workflows described above. It is not a commercial client case, a production deployment or evidence of a live payment integration. Public registration is disabled; the test learner was created during setup.
Certificates, staged content release, assignments, webinar integrations, automatic invoices and advanced reports are outside the verified demonstration. They require a separate implementation with the appropriate components and licenses. The video is an ordinary reference asset; protected streaming and DRM were not tested.
Technical verification notes
Testing used a loopback-only PHP installation with SQLite, blocked outbound email and fictional account data. It does not replace production MySQL/MariaDB, payment-provider or hosting validation. The worksheet is stored outside the web root and served after an enrollment check. A 100% curriculum-visit counter after a failed quiz did not mean course completion: the native completion action refused it until the quiz was passed. Verification completed on 17 October 2026.
For a complete course platform, the next step is agreeing the course structure, integrations, license ownership and acceptance checks before implementation.
Back to portfolio ↗