School ERP | Website, Admissions & School Operations

I built a public school website and an ERP workspace for admissions, student records, attendance, fees and administration. The website helps families explore the school, while the staff workspace keeps daily operations organized around the same student and academic-year context.

My role: Full-stack development across the interface, API, database and deployment configuration.

The school office brings attendance, collections and admissions together with an action register and office diary. Each exception leads to the relevant workspace, so the overview provides a starting point for the day.

The public website carries the school identity through admissions guidance, academic information and clear enquiry and visit actions. Families contact the school by phone or WhatsApp; staff record and manage applications inside the ERP.

The admissions board groups candidates by enquiry, visit, review and approval. Document readiness and waiting time stay visible alongside the next action. The application backend uses a transaction to create linked enrollment records when approval is completed.

The student record preview puts guardian, class, attendance and fee context together. It gives staff a focused view of the student while retaining a direct route to the collection workflow.

The finance workspace connects collection totals to student-level dues, installment dates and receipt actions. The application models fee structures, concessions, recorded payments, receipt PDFs and expenses.

Both themes use the school website's indigo, saffron, paper tones and typography. Compact controls, ledger-like summaries and restrained dividers adapt that identity for repeated administrative work.

Consistent enrollment: Admission approval creates the student, academic, document and applicable fee records in one database transaction, reducing partial enrollment states.

Explicit school context: Authentication, role, permission and school-context guards govern API access. Switching schools clears the frontend query cache so the previous school's results do not remain on screen.

Careful fee handling: Decimal database fields, integer-paise allocation, unique receipt constraints and collision retries address rounding and document-number conflicts.

Website: React, TypeScript, Vite, React Router and Tailwind CSS.

ERP interface: Next.js App Router, React, TypeScript, Tailwind CSS, shadcn/Base UI, TanStack Query, Axios and Recharts.

API and data: Node.js, NestJS, Prisma, PostgreSQL, Zod, Passport JWT, bcrypt, refresh sessions, HTTP-only cookies, S3-compatible storage and PDFKit. Deployment configuration uses Docker Compose, nginx and MinIO. The repository includes API/mobile test suites and Playwright browser tests.

The redesigned ERP remains an offline prototype. Exam workflows are unfinished, website content includes placeholders, and recorded online payments represent manual entries. Live messaging and mobile feature parity were not verified for this presentation.

Need a school platform, internal tool or operations dashboard? Send me your workflow, current stack and priorities.