Opportunity
Move from individual pages to a shared system
A centralized component language reduces repeated design decisions while giving learners predictable patterns across courses.
Consistency
Common structures help learners recognize what to do next.
Maintainability
Shared assets allow system-level improvements without rebuilding every course.
Accessibility
Semantic, tested patterns provide a stronger baseline for review.
Current System
Reusable pages and components
- Course and module page patterns
- Accessible interactive and assessment components
- Responsive media and content layouts
- Standard page templates for repeatable authoring
Next Steps
Validate, govern, and scale
- Test the system inside live D2L course contexts.
- Document component ownership and release practices.
- Measure learner and authoring outcomes.