01 / flagship product
Make a large syllabus feel like a next step.
Status
Live product
Category
Flagship product
Video walkthrough
Deborah — Education SaaS in motion.
A student signs in with a supported provider, completes a profile, reviews notes, practices by topic or weak area, starts a timed exam, receives a server-scored result, reviews mistakes, and uses progress signals to choose the next study action.
A visual tour of the primary product flow
Context
Deborah is an Ethiopian Grade 12 learning and exam-preparation platform. The public product explains a connected loop: assess, learn, practice, test, reflect, and improve.
The problem
Students need more than a content library. They need focused practice, a repeatable exam workflow, and a way to understand where effort should go next.
My contribution
I worked across the product boundary: the Next.js experience, Hono API layers, shared validation and types, learning services, server-authoritative exam rules, authentication surfaces, admin workflows, and the release evidence that makes the boundaries explicit.
Real workflow
A student signs in with a supported provider, completes a profile, reviews notes, practices by topic or weak area, starts a timed exam, receives a server-scored result, reviews mistakes, and uses progress signals to choose the next study action.
Architecture
The repository is a Bun workspace with a Next.js App Router web app, a Bun + Hono REST API, shared Zod validation and types, a Drizzle/PostgreSQL data layer, and pure core logic for scoring, recommendations, readiness, and entitlements.
Integrations
Provider-based sign-in, server-side AI access, manual payment and receipt verification through a provider abstraction, same-origin API proxying, and deployment-friendly environment boundaries are documented in the repository.
What works in the described product
- Student onboarding and provider sign-in
- Notes, search, bookmarks, and review-later flow
- Practice by topic, weak area, previous mistakes, or random selection
- Server-timed exams with autosave, recovery, scoring, results, and review
- Progress charts, recommendations, achievements, and an AI study assistant
- Admin curriculum, question bank, exam, payment, and contact workflows
Verification and boundaries
The checked-in release-readiness report records 151 Bun tests, 15 Chromium smoke tests, TypeScript checks, a production build, and the remaining staging/provider/device gaps. I link the evidence instead of presenting local QA as a production sign-off.
Next: Before calling it fully production-ready, I would run the live staging browser pass, provider sandbox flows, managed Postgres checks, and the device/accessibility review already called out in the repository.