How omwairagade/campus360 works
Campus360 is a campus-management application for students, faculty, and administrators. Users enter through role-specific web pages, which make authenticated API requests; the backend routes those requests to academic, attendance, fee, and administrative operations backed by PostgreSQL through Prisma. The graph groups related screens and handlers to show the main workflow and major capabilities without enumerating every route. Source evidence is strongest for server mounting, enrollment, attendance, and database access; some broader capability links are therefore left out rather than inferred.
Main entry points: routes API routes · prisma.js Prisma client · main.jsx Role-based app · api.js API client
Components 19
Web application
- Role-based app
frontend/src/main.jsx - Student pages
frontend/src/pages - Faculty pages
frontend/src/pages - Admin pages
frontend/src/pages
API and access
- API client
frontend/src/api.js - HTTP server
backend/src/server.js - Authentication
backend/src/middleware/authMiddleware.js - Role checks
backend/src/middleware/roleMiddleware.js - API routes
backend/src/routes
Academic operations
- Course enrollment
backend/src/controllers/enrollmentController.js - Admin enrollment
backend/src/controllers/adminEnrollmentController.js - Attendance
backend/src/controllers/attendanceController.js - Assignments
backend/src/controllers/assignmentController.js
Campus services
- Student administration
backend/src/controllers/adminStudentController.js - Timetable administration
backend/src/controllers/adminTimetableController.js - Campus controllers
backend/src/controllers
Persistence
- Prisma client
backend/src/lib/prisma.js - PostgreSQL
Other components
- Students and staff
Connections 25
- Students and staff → Role-based app: use
- Role-based app → Student pages: routes to
frontend/src/main.jsx - Role-based app → Faculty pages: routes to
frontend/src/main.jsx - Role-based app → Admin pages: routes to
frontend/src/main.jsx - Student pages → API client: request data
frontend/src/pages/AdminEnrollments.jsx - Faculty pages → API client: request data
frontend/src/pages/FacultyCourseDetails.jsx - Admin pages → API client: request data
frontend/src/pages/AdminEnrollments.jsx - API client → HTTP server: HTTP requests
frontend/src/api.js - HTTP server → API routes: mounts
backend/src/server.js - API routes → Authentication: checks token
backend/src/routes/enrollmentRoutes.js - API routes → Role checks: checks role
backend/src/routes/adminEnrollmentRoutes.js - API routes → Course enrollment: dispatches
backend/src/routes/enrollmentRoutes.js - API routes → Admin enrollment: dispatches
backend/src/routes/adminEnrollmentRoutes.js - API routes → Attendance: dispatches
backend/src/routes/attendanceRoutes.js - API routes → Assignments: dispatches
backend/src/routes/assignmentRoutes.js - API routes → Student administration: dispatches
- API routes → Timetable administration: dispatches
backend/src/routes/adminTimetableRoutes.js - HTTP server → Campus controllers: mounts routes
- Course enrollment → Prisma client: queries
backend/src/controllers/enrollmentController.js - Admin enrollment → Prisma client: queries
backend/src/controllers/adminEnrollmentController.js - Attendance → Prisma client: queries
backend/src/controllers/attendanceController.js - Assignments → Prisma client: queries
backend/src/controllers/assignmentController.js - Student administration → Prisma client: queries
backend/src/controllers/adminStudentController.js - Timetable administration → Prisma client: queries
backend/src/controllers/adminTimetableController.js - Prisma client → PostgreSQL: connects
backend/src/lib/prisma.js