Websites

Online learning platform: what it's made of

Courses, lessons, student progress, assignment review, video and certificates. The parts a learning platform consists of and how it differs from a site with video recordings.

A learning platform is often pictured as a website with paid video lessons. While there's one course and a dozen students, that really is enough. Then it turns out the main difficulty isn't showing video but making sure the system knows where each person stopped, what they've submitted and what to unlock for them next. Here's what a learning platform consists of and in what order to build it.

How an LMS differs from a site with videos

The difference is in who tracks the state of learning. On a video site, the student keeps that state in their head: they remember which lesson they watched last and decide what's next. A platform takes this on itself.

Almost everything else follows from this. If the system knows the progress, it can:

  • unlock the next lesson only after the previous one;
  • show in the dashboard where the student stopped and resume the video from the same minute;
  • remind people who haven't logged in for a week;
  • withhold the certificate until required assignments are submitted;
  • show the teacher who's falling behind before the person drops out.

None of these is possible without tracking progress. So progress isn't an extra feature but the foundation: the data structure everything else is built around.

The practical takeaway: if you have one introductory course with no assignments or feedback, you don't need a platform — a private section with videos is enough. If there are several courses, assignments and teachers, the lack of a proper system very quickly turns into manual tracking in spreadsheets.

Structure: course, module, lesson

Almost any programme breaks down into three levels: course — module — lesson. It seems obvious, but the details of the structure determine what the platform will be able to do later.

Key decisions:

  1. What a lesson consists of. Usually not just video: text, attachments, an assignment, a quiz, a discussion. It's better to design a lesson from the start as a set of blocks of different types, not as "video plus description". Otherwise the first lesson without a video will break the model.
  2. The order of progression. Free (everything open at once) or sequential (the next lesson after completing the previous one). Sequential builds discipline but annoys those who need a specific topic. A mixed approach is often sensible: modules in sequence, lessons within a module in any order.
  3. What counts as completing a lesson. Watching the video to the end, a manual checkmark, a submitted assignment or a passed quiz. This determines how well progress reflects reality.
  4. Course versions. The programme gets updated while students go through it at different times. Decide in advance: do those who have already started see the old version or the new one? Without this decision, a course update breaks the progress of some students.

Progress, assignments and review

Progress is a record of what each student has done with each element of the course. Technically simple, but it's exactly what the platform's value rests on.

Automatic grading

Multiple-choice quizzes, short answers with an exact match, tasks with a verifiable result — all of these are graded without a person. Details matter here that usually surface after launch:

  • how many attempts are allowed and what happens when they run out;
  • whether to show the correct answers after submission, and immediately or after access closes;
  • whether to shuffle questions and options;
  • whether there's a time limit.

These rules should be set per quiz, not platform-wide: an entry test and a final exam live by different rules.

Human review

Homework, essays and projects are reviewed by a teacher. This needs a proper workflow, not just a file upload:

  1. The student submits the work and sees its status and review deadline.
  2. The work lands in the teacher's queue with filters by course and cohort.
  3. The teacher leaves a grade and comment and, if needed, sends it back for revision.
  4. The student gets a notification, sees the comment and can reply.
  5. The history of all versions of the work and all comments is kept.

A platform where assignment review isn't thought through quite quickly turns into teachers and students messaging each other in a chat app, and the site itself into a video archive.

The teacher's workload is planned separately. If review takes a lot of time, comment templates, grading criteria right in the review interface and the ability to hand work to another reviewer all help.

Video and hosting

Video is the heaviest part of the platform, both in volume and in running costs.

The main choice: host and deliver it yourself or use a specialised video service. Self-hosting gives full control and independence but means handling transcoding into several qualities, adaptive streaming for connection speed, CDN delivery and protection against direct downloads. An external service removes these tasks but adds an ongoing subscription fee and dependence on someone else's platform. For most learning projects an external service is more sensible at the start — moving to your own hosting later is easier than building it straight away.

What matters regardless of the choice:

  • Remembering the playback position. The student returns to where they stopped. Without this, long lessons are watched once and never revisited.
  • Playback speed and subtitles. They significantly broaden the material's accessibility and are cheap to implement.
  • A realistic attitude to protection. Video can't be fully protected from screen recording. A watermark with the student's name and private links with a limited lifetime cut off mass distribution — don't expect more, and don't invest disproportionately in it.

Groups, cohorts and certificates

When there are many students, learning stops being individual.

Cohorts are the same programme launched on different dates, with their own deadlines and teachers. A student is tied to a cohort, and deadlines count from the cohort's start date, not the purchase date. Without the concept of a cohort, dates have to be managed by hand.

Groups are needed for corporate training: a company buys access for its employees, and its representative sees their group's progress but not anyone else's. It's a separate role with its own dashboard and reports.

Certificates are issued when predefined conditions are met: required lessons completed, assignments submitted, a minimum score reached. Three things matter technically: the issuing conditions are configurable, not hard-coded; the certificate has a permanent URL for verifying authenticity; it carries a number and a date. A certificate that can't be verified by a link is worthless to an employer.

Order of work: what comes first

When building a platform from scratch, a sensible sequence looks like this:

  1. The course, module and lesson structure with blocks of different types.
  2. The student dashboard and progress tracking.
  3. Video playback that remembers the position.
  4. Quizzes with automatic grading.
  5. Assignments with teacher review and feedback.
  6. Cohorts and deadlines.
  7. Certificates.
  8. Groups and corporate dashboards.
  9. Completion reports and analytics.

The first three points give you a working product for one course. The next ones turn it into a platform. The last ones are needed when learning becomes a regular business, and building them in advance is usually premature.

It's easiest to start working through a specific programme by breaking the course down into lessons and assignment types — almost all the technical work that follows depends on it. More about our approach is on the education platforms page; you can discuss your task via the form.