Make the next action clear.
Attendance, pending fees and application reviews meet in the school office action register.
Education / Full-stack development
A school day, connected.

AI-composed presentation using the public website and original ERP prototype captures. Sample records and amounts.
The project in perspective
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.
Inside the experience
Original captures. Sample records and figures.



The thinking behind the interface
Attendance, pending fees and application reviews meet in the school office action register.
Admissions, guardians, class and fee details stay connected to the task.
Installment dates, student dues, collection and receipts share a finance workspace.
Admission approval creates linked student, academic, document and applicable fee records in one database transaction.
Role, permission and school-context guards govern API access. Switching schools clears frontend query caches.
Decimal database values, integer-paise allocation and receipt constraints address rounding and document-number conflicts.
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
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