Skip to main content

Tracks, progress & certificates

This page walks through what you'll actually see as a learner: how a track is laid out, what "My Learning" shows you, how quizzes and completion work, and what your manager can see.

What a track looks like​

A track (like the ADW Track) is a linear, gated sequence of modules — you generally move through them in order, and each one ends with a knowledge check before you move to the next. The sidebar on the left always shows you where you are in the current track and what's left.

Enrollment​

Opening a track's first module effectively enrolls you in it — there's no separate signup step. If you're signed in, that enrollment is recorded server-side; if not, it's implicit in your local progress.

Lesson progress​

Each lesson tracks whether you've started or completed it:

  • Opening a lesson marks it started.
  • A "Mark this lesson complete" control at the end of a lesson marks it completed once you've actually gone through the content (and, where the module has one, done the hands-on lab).

Completed lessons show a checkmark in the sidebar, so you (and later, "My Learning") can see progress through the whole track at a glance.

Knowledge checks​

Modules that include a knowledge check gate on it: you need a passing score (70% by default) to have that module count as complete. If you don't pass, you can review the material and retry — a knowledge check is a checkpoint, not a one-shot exam. Each attempt is recorded (score, pass/fail, which answers you gave), which is also what powers the reporting rollups described below.

My Learning​

My Learning (linked from the top nav) is your personal dashboard across every track you've touched:

  • Which tracks you're enrolled in and how far through each one you are.
  • Per-module status (not started / in progress / complete).
  • Quiz scores and pass/fail history.
  • Certificates you've earned.

Certificates​

Complete every module in a track and a certificate is issued for that track, tied to your identity and completion date. It's the answer to "prove you finished this," both for you and for anyone who needs to confirm it.

Manager visibility (cohort reporting)​

Completion isn't just for the learner. When you're signed in, your progress and quiz results also feed a reporting view that lets managers see cohort-level completion — who on the team has finished a track, module completion funnels, and quiz pass rates — without exposing your individual day-to-day activity beyond what's needed for that rollup. This is what turns "we did the training" from an assumption into something an org can actually verify.

MVP vs. full: being honest about what's real today​

The Academy is built to be useful before every layer is finished, and to upgrade quietly once it is:

  • MVP (content-only): all of the above — lesson progress, quizzes, completion — works entirely in your browser via localStorage. No sign-in, no cross-device sync, no manager view. This is enough to actually learn from and to self-track your own progress, and it's what ships first.
  • Full (with the backend): once the LMS backend (a small FastAPI service on its own Postgres schema, sitting behind company SSO) is deployed, the same UI transparently starts writing through to it — you get cross-device progress, durable certificates independent of your browser, and the manager cohort-reporting view described above.

Nothing about the learner experience changes when the backend arrives; the site simply stops being local-only and starts being reportable. If the backend is ever unreachable, the site falls back to localStorage rather than breaking, so the Academy is never blocked on the sidecar being up.

Where this is implemented

This split — localStorage-only progress on a static host vs. a full server-side progress/quiz/completion API — is a deliberate architecture decision, not a shortcut. It's why the Academy is deployed on Container Apps rather than a plain static host: the platform is built for the full version from day one, even while running in MVP mode.