starringdaggers/boltab

Purpose and entry points

Boltab Brilliant Schools is a role-based school portal for administrators, teachers, and students. It is a Next.js App Router application that combines dashboards and HTTP APIs in one deployment. Public access begins at src/app/page.tsx and src/app/login/page.tsx; authenticated users are routed into role areas under src/app/admin, src/app/teacher, or src/app/student.

Authentication and authorization boundary

JWT authentication is issued and cleared through src/app/api/auth/login/route.ts and src/app/api/auth/logout/route.ts, using httpOnly cookies. Session, JWT, password hashing, and role checks are centralized in src/lib/session.ts, src/lib/jwt.ts, src/lib/password.ts, and src/middleware.ts. Middleware protects role-prefixed dashboard routes; API handlers must enforce their corresponding role/access rules, including admin delegation and controlled result visibility.

Role-specific application surfaces

Each role has its own layout and server/UI route tree: src/app/admin/layout.tsx, src/app/teacher/layout.tsx, and src/app/student/layout.tsx. Shared dashboard navigation and presentation live in src/components/shared/DashboardShell.tsx. Admin is the operational control plane; teacher routes support assigned teaching work; student routes expose personal academic, attendance, fee, and timetable data.

Admin school-management control plane

Admin pages and APIs manage the school’s core reference and account data: students, teachers, classes, subjects, terms, accounts/delegations, and school fee setup. Representative boundaries are src/app/admin/students/page.tsx, src/app/api/admin/students/route.ts, src/app/api/admin/teachers/route.ts, src/app/api/admin/classes/route.ts, and src/app/api/admin/terms/route.ts. Admin-specific authorization support is in src/lib/adminAccess.ts. CSV student ingestion is a dedicated mutation endpoint at src/app/api/admin/students/import/route.ts.

Academic workflows: assignments, results, and report cards

Teachers obtain their authorized classes, subjects, terms, and assignments through endpoints such as src/app/api/teacher/assignments/route.ts and src/app/api/teacher/results/route.ts, then submit academic results and report-card data. Admin manages report-card records and release/settings via src/app/api/admin/report-cards/route.ts and src/app/api/admin/report-cards/settings/route.ts. Student results are exposed through src/app/api/student/results/route.ts; visibility policy is isolated in src/lib/resultsAccess.ts. Grade computation/presentation logic is supported by src/lib/grading.ts, src/lib/reportCardFields.ts, and src/components/report-card/ReportCardView.tsx.

Operations: attendance, fees, timetables, and presence

Attendance has separate teacher recording, student viewing, and admin oversight paths: src/app/api/teacher/attendance/route.ts, src/app/api/student/attendance/route.ts, and src/app/api/admin/attendance/route.ts. Fees use admin-managed class fees and payments with student-facing balances/history: src/app/api/admin/class-fees/route.ts, src/app/api/admin/fee-payments/route.ts, and src/app/api/student/fees/route.ts. Timetables are constructed by admins using src/components/timetable/TimetableBuilder.tsx, persisted via src/app/api/admin/timetables/route.ts, and consumed through src/app/api/timetables/route.ts. Presence heartbeat/status endpoints support active-user tracking at src/app/api/presence/heartbeat/route.ts and src/app/api/presence/status/route.ts.

Data, runtime, and infrastructure

The runtime is Next.js 14 with React/TypeScript and route handlers; styling is Tailwind-based. Prisma is the persistence boundary: schema and seed data are in prisma/schema.prisma and prisma/seed.ts, accessed through src/lib/db.ts. The intended database is PostgreSQL, with Neon named in setup guidance. Manual SQL migrations under prisma/ indicate schema evolution for attendance, report cards, fees, timetables, profile pictures, and school settings. Deployment targets are Next.js-capable hosting such as Vercel or Netlify, configured with DATABASE_URL, JWT_SECRET, and token-expiry environment variables.