Student Dashboard + Course Player
The learner runtime connects enrollment, access, course hub, one lesson at a time, notes, bookmarks, watch history, progress, completion diagnostics, AI study coach, certificates, discussions, and payments.
Workflow
- Student lands on /student/dashboard and sees continue learning, study plan, reminders, live lessons, and certificate strip.
- Course hub at /student/courses/{course}/hub shows overview, outcomes, curriculum, resources, instructor, and certificate checklist.
- Lesson player at /student/courses/{course}/lessons/{lesson} supports theatre, reading, and review modes.
- Autosave records watch/read position, active seconds, resource events, notes, bookmarks, and completion attempts.
- Completion service validates server-side rules and explains blocked states like drip, prerequisite, watched percent, resource download, PDF view, or live attendance.
Important Screens
| Screen | Route | What students see |
|---|---|---|
| Learner home | /student/dashboard | Active courses, filters, study plan, reminders, bookmarked lessons, certificates. |
| Course hub | /student/courses/{course}/hub | Course overview, outcomes, instructor, progress by section, resources, study coach. |
| Lesson player | /student/courses/{course}/lessons/{lesson} | Lesson content, resources, completion CTA, diagnostics, notes, bookmarks, tutor. |
| Payments | /student/payments | Invoices, receipts, bundles, failed payment retry, payment history. |
Access Protection
Only active or completed enrollments get full lesson content. Public and non-enrolled users receive preview-safe excerpts, preview media, and locked sales curriculum only.
Demo Checklist
- Open learner dashboard and verify Continue Learning.
- Open course hub and inspect progress map.
- Open player and verify completion diagnostics.
- Create a note/bookmark and confirm ownership scoping.
- Try a locked/dripped lesson and confirm clear reason.
Demo And Developer Notes
Buyer exampleRun the Student guided demo, resume the seeded course, add a note/bookmark, and confirm the completion CTA explains blocked states.
Developer noteImportant anchors are
student-dashboard-workspace, course-hub-workspace, and student-player-workspace. Student data must stay scoped to the signed-in learner.