System blueprint

Frontend, backend, payment, and admin modules

This is the implementation map behind the mockup: the first version can stay lean for one teacher, while the database avoids hard-coding the business into a corner.

Frontend

Public + student portal

  • Landing page and course catalog
  • Course detail with preview lessons
  • Login, enrolment, progress dashboard
  • Lesson video, PDF, quiz, practice upload

Backend API

Core entities

  • users, students, teachers
  • courses, modules, lessons, assets
  • enrolments, progress, submissions, comments
  • orders, payments, subscriptions, coupons

Admin

Teacher operations

  • Course builder and publishing controls
  • Manual enrolment and student access expiry
  • Payment setting per course
  • Practice review and student messaging

Payments

Flexible access

  • Manual payment proof approval for early launch
  • One-time course purchase
  • Optional recurring subscription
  • Admin can disable checkout and invite students only