School ERP

Future Gate High School, 2023 – now

5: modules shipped
400+: users
20+: REST APIs integrated

ERP home screen: greeting, attendance, teaching schedule, foundation announcements, quick actions and the module launcher — Home screen, where every user role starts.

The same ERP home screen on a phone — The same home screen on a phone.

Admissions dashboard with a to-do list for registrations, applicant status breakdown and the active intake wave — Admissions dashboard with the registrations that need action today.

Learning dashboard with class progress bars, latest materials and the module roadmap — Learning: class progress against the semester plan.

The problem

The school needed one system for admissions, academics, HR, finance and inventory, with screens suited to each department.

My role

I lead the frontend: architecture, the screens for each department, and integration with the backend team's APIs.

Outcome

Every department works in one system, with screens built for its own job.
400+ users, from new-student enrollment through payroll.
Fewer UI bugs after introducing internal testing and documentation.

Architecture

Five connected modules (Academic, Admissions, HR, Finance, Inventory) in one React + TypeScript frontend.
Redux and Zustand hold the state, so data stays in sync across modules.
Role-specific views for each type of user.

Decisions

Role-based views over shared data

Each role gets its own screens, built on the same records, so the modules stay in sync with each other.

Testing and documentation

Unit tests with Jest and React Testing Library, plus internal testing and written technical docs, reduced UI bugs.

Stack

React, TypeScript, Redux, Zustand, REST, Jest, React Testing Library

Client work, no public source. Screens show only data that is safe to share.