Skip to content
Part of ELO — Embedded Logic Operations · Volunteer teacher → platform lead ↗

Handed over 2021 · platform still live

SPDA Education

Volunteer-taught learning platform built during COVID — students, volunteers and teachers register, pick courses and run them. Django modernised with Vue as a drop-in SPA layer (no npm build step), shipped on Docker.

Role
Volunteer teacher → platform lead (via ELO)
Period
2020 — 2021 · maintained, then handed over
Stack
Django · Vue · PostgreSQL · Docker · and 2 more
Place
Canada (Remote)
SPDA Education — the students / volunteers / teachers split that drives registration and course selection.

SPDA Education — the students / volunteers / teachers split that drives registration and course selection.

3 rolesStudents · volunteers · teachers

Schools closed and two problems collided: students had no classes, and volunteers had credit hours to earn with nowhere to earn them. SPDA's answer was to make the volunteers the faculty — anyone with a skill could open a course, and any student could take it for free.

01 / 03

Why it existed

That only works with real software behind it.

Someone has to register three different kinds of user, keep courses and enrolments straight, and let a volunteer actually run a session. I taught on the platform and helped build it, which is the fastest way to find out what a platform is missing.

02 / 03

Vue over Django, deliberately

  • Modernise, don't rewrite. The client had a working Django application. Replacing it would have cost the whole engagement; the goal was for it to feel like a modern app, not to be a different one.
  • Vue as a progressive layer. Vue could be dropped into existing Django templates and take over the interactive parts incrementally — no build pipeline, no npm install in the deployment path, no toolchain for the next maintainer to inherit.
  • Server-rendered where it belonged. Registration, course listings and admin stayed Django; the interactive surfaces became SPA-like. The seams were chosen, not accidental.
03 / 03

Dockerised so the handover would stick

The engagement was always going to end — a volunteer-run organisation cannot keep a studio on retainer.

So the deploy story mattered more than usual: the whole stack was containerised so that bringing the platform up was one command, not a runbook.

That is what made the 2021 handover clean rather than a slow decay. The platform is still live today, which is the only real test of a handover.

Decisions and why

  1. Vue sprinkled into Django rather than a separate SPA

    WhyA separate front end would have meant a build step, a second deployment, and a toolchain the client could not maintain after handover. Vue's script-tag path gave the modern feel at none of that cost.

  2. Containerise before handing over

    WhyThe people inheriting the platform were volunteers, not an ops team. A dockerised stack made "run it" a single command and removed the environment drift that usually kills handed-over projects.

Impact

  • Gave a volunteer teaching programme working LMS infrastructure during school closures.
  • Handed over cleanly in 2021 — the platform is still live and in use years later.
  • Grew an engineer who worked alongside me on it into a career that is now in Norway.
Outcomes

By the numbers.

Django + Vue
SPA layer, no npm step
Docker
One-command deploy
2021
Clean handover
Visit project

See it in the wild.

This case study covers how SPDA Education was built — these links open what ships today: the live product, repo, demos, and supporting material.

↗ Next case study

Optimo

Optimo is the all-in-one service-automation testing framework ELO built for Hyundai HATA in California, still used there to test the online architecture behind their connected-cars ecosystem. One platform covers three surfaces that normally need three separate test stacks — IoT devices, the web portal, and the mobile app — including human-to-device voice conversations against Alexa and Google Home. Fauzul was active in the early scope definition, wrote test cases, designed the test workflows, defined the APIs, and managed the development team delivering it.