shipped
live, in production
Online parenting workshops + sensory toy shop, purchase unlocks portal access.
Visit
Live site02 · Outcomes
Numbers, not adjectives. The stats below are pulled from production. Anything still live, still measured.
shipped
live, in production
purchase unlocks portal
video + text material
sensory development
age-appropriate by design
front · back · admin
shop + workshops + portal
03 · Overview
Online workshops for parents combined with a shop for educational toys designed for preschool-age sensory development. Buying a toy or workshop unlocks the user portal — paired video and text material that turns a toy from object into curriculum. Full admin manages workshops, shop catalogue, user accounts, and the content library from a single console.
04 · Gallery
Secondary mockups, detail crops, mobile and desktop variants. Click any shot to open it full-size.
05 · Process
Four phases. Each one with a deliverable the client could see, not a slide deck of intent.
The product wasn't 'a course' or 'a toyshop' — it was both. Parent buys a sensory toy for the preschool kid, and the toy comes paired with the workshop video plus a text curriculum on what the toy is teaching. Brief was: keep the buying experience light, but make sure the educational content is in the parent's account the moment they hit pay.
React + Redux Toolkit front. Node + Express + MySQL back. Entitlement layer between purchases and content access — unlocks gated by product purchases, audited per user. Single admin handling shop, workshops, accounts, and content library.
Shop + checkout first — that's the entry point. Workshop catalogue + content library second. Entitlement layer last but fully tested, since this is where a missed unlock turns into a support ticket.
Live since 2026. Parents buy a toy or a workshop, the content is in their account immediately. Operator runs catalogue + workshop publishing + user accounts + content library from a single admin.
06 · Decisions
Tech is downstream of decisions. These are the calls made early enough to compound the right way. The ones a code review six months later still agrees with.
Purchase grants the parent the content paired with that toy. One product, one entitlement, no separate course SKU — cleaner conversion, cleaner ledger, less explaining at the support inbox.
Same user accounts, same payments, same admin. Parent buys a workshop and a toy in one flow without bouncing between systems — and the content library serves both.
Purchases → unlocks must be airtight. SQL for the relational integrity (user × product × access window), simple to audit when a parent reports missing content from their portal.
06 · Let’s build
I take 4–5 freelance projects a year. Cold pitches welcome. I reply within 24 hours on weekdays.