Back to workSELECTED WORK / A CLOSER LOOK

Education / Full-stack development

School ERP

A school day, connected.

Project lead & role
Somveer Kumar / Full-stack development
Scope
Application + separate ERP design prototype
Presentation
Original prototype captures / Sample data
School ERP / Portfolio presentation
AI-composed presentation using the public website and original ERP prototype captures. Sample records and amounts.
DESIGN, WITH CONTEXT

AI-composed presentation using the public website and original ERP prototype captures. Sample records and amounts.

The project in perspective

A school day, connected.

A public school website and an ERP application for admissions, students, attendance, fees and administration. One project, serving families and school staff.

Work by Somveer Kumar. Prototype screens and application engineering are described separately.

Decorative studio sculpture. The product images are shown separately.

The thinking behind the interface

Design.
And the build.

01 / EXPERIENCE

Make the next action clear.

Attendance, pending fees and application reviews meet in the school office action register.

02 / EXPERIENCE

Keep student context close.

Admissions, guardians, class and fee details stay connected to the task.

03 / EXPERIENCE

Review dues clearly.

Installment dates, student dues, collection and receipts share a finance workspace.

01 / CRAFT

Consistent enrollment

Admission approval creates linked student, academic, document and applicable fee records in one database transaction.

02 / CRAFT

Explicit school context

Role, permission and school-context guards govern API access. Switching schools clears frontend query caches.

03 / CRAFT

Careful fee handling

Decimal database values, integer-paise allocation and receipt constraints address rounding and document-number conflicts.

Tools behind the work

Website: React, TypeScript, Vite and Tailwind CSS. ERP: Next.js, React, TypeScript, TanStack Query and Recharts. API and data: NestJS, Prisma and PostgreSQL.

An honest view of the work

The scope.
Made clear.

Screens are a separate offline HTML/CSS/JavaScript prototype with fictional records. Engineering describes the School ERP application codebase. The public site has some placeholders. Exams are unfinished; live messaging, payment gateways and mobile feature parity are not demonstrated.

View the public Contra presentation