Customer-facing (B2C)Summer Course Registration Platform
Summer registration on paper and in Excel, replaced by back-office course listing and online registration for parents
New courses no longer need to be outsourced; registrations and payments are checked in the same system, and class-cancellation notices and pre-class reminders go out over LINE.
- Outcome
- New courses listed from the back office, with no more waiting on outside custom development
- Role
- Built from requirements: from requirements through launch and maintenance
- Period
- Launched 2026.02
- Tech
- PostgreSQL · Drizzle ORM
Problem Registration on paper and in Excel; every new course waited on an outside vendor
Registration records were kept on paper and in Excel, and every new course had to wait for custom development by an outside vendor before it could be listed.
Approach and impact Courses listed from the back office
In-house registration system, built from requirements through launch and maintenance. Courses are listed from the back office with no outsourced development, and can be maintained and changed internally at any time; registrations and payments are checked in the same system.
User flow Listing in the back office, public registration, checking in one system
- Internal staff maintain and list courses in the back office.
- Courses are open for public registration.
- Registrations and payments are checked in the same system.
LINE integration Class-cancellation notices, pre-class reminders and make-up sign-ups
When a session is cancelled, the parents of that session are notified over LINE; a LINE reminder goes out before class; for typhoon make-up classes, parents open the sign-up page from the LINE notice.
Scale 324 API routes, 75 test cases
Counted from the GitHub main branch: 324 API routes, 81 database tables, 75 test cases. Source code is in a private repo and is not public.