Services
01Webflow developmentSites your team can edit.02Shopify developmentStores built to convert.03WordPress developmentFlexible, plugin-ready sites.04Custom web app developmentDashboards, portals, AI tools.05Website migrationSwitch platforms, keep rankings.All servicesIndustries
01B2B startupsSites that keep up with the product.02Local service businessesGet found locally. Get the call.03Ecommerce companiesStores that make buying easy.All industriesCompany
Case StudiesPricingWhite LabelAboutCase study · Nonprofit / Workforce Training
A Food Safe Handling learning platform for Food Banks Alberta - company access keys, a course with a final test, and admin tools for partner organizations.
Project overview
Food Banks Alberta sells Food Safe Handling training to partner organizations. Each company gets a readable access key; when a worker registers with that key, they're automatically attached to their company in the database for later reporting, with no manual account linking required.
The challenge
A standard course platform assumes learners sign up on their own. Food Banks Alberta needed the opposite: an admin issues one key per purchasing company, any number of that company's staff can register with it, and every account has to be traceable back to the company that paid for it, without the learner ever entering a company name by hand.
What we did
We built a Next.js and Drizzle ORM app on Neon Postgres with a readable enrollment-key format (FBA-XXXX-XXXX, excluding easily-confused characters like 0/O and 1/I). Registration validates the key, checks it isn't revoked or past its use limit, and links the new account to that company in one transaction. Auth is self-built - email and password with a JWT session cookie - deliberately not Supabase Auth, so the database can be swapped without touching the login flow.
What shipped
The original scope planned a "coming soon" course card for phase one; the shipped product includes real course modules, a final test, and a post-course survey.
Admins generate and revoke access keys, set usage limits, rename companies, and manage every learner from dedicated admin screens.
UI copy runs through next-intl with English as the canonical source and bundled French and Spanish, plus an auto-translate route for additional languages when a translation API key is configured.
A dedicated import script and legacy-import report brought over existing learner records instead of starting the company's training history from zero.
The results
What launched goes well past the original phase-1 scope: a real course with assessment and survey, an admin analytics view, and a legacy-user import, on top of the original registration and company-key system. The auth and data layers stayed decoupled from any one vendor by design, so the project could move off Supabase onto Neon Postgres without a rewrite.
Talk to the foundersBring the goals, the constraints, and the messy parts. We'll turn them into a clear next move.
