codemonk-io/campussync

Purpose and entry points

This is a full-stack event-management application: users authenticate, create and browse events, register for them, comment, view personal dashboards, and optionally integrate calendars/reminders. The backend HTTP entry point is backend/index.js; the React/Vite client starts at frontend/src/main.jsx and composes application routing/UI in frontend/src/App.jsx.

Frontend application boundary

The browser client is a React single-page application with a centralized API layer and authentication context. frontend/src/api.js is the frontend/backend transport boundary; frontend/src/context/AuthContext.jsx owns client authentication state. Route protection is enforced in frontend/src/components/layout/ProtectedRoute.jsx, while key user workflows are implemented by pages such as frontend/src/pages/EventsPage.jsx, frontend/src/pages/EventDetailPage.jsx, and frontend/src/pages/user/DashboardPage.jsx.

Backend HTTP and request pipeline

The Node backend is organized as route → controller → service → model. Route modules expose domain endpoints, including backend/routes/auth.js, backend/routes/events.js, and backend/routes/registrations.js. Controllers adapt HTTP requests/responses and delegate business work, e.g. backend/controllers/eventController.js, backend/controllers/calendarController.js, and backend/controllers/dashboardController.js. Authentication and centralized error handling form cross-cutting request boundaries in backend/middleware/auth.js and backend/middleware/errorHandler.js.

Core event and participation domain

Events are the central aggregate, represented by backend/models/Event.js and managed through backend/services/eventService.js. Registration is a separate relationship/domain workflow, with backend/models/Registration.js and backend/services/registrationService.js; this separation supports event capacity/attendance logic independently of event authoring. Event discussion is similarly isolated through backend/models/Comment.js and backend/services/commentService.js.

Identity and authorization

Users are persisted in backend/models/User.js. Authentication behavior is concentrated in backend/services/authService.js and exposed through backend/controllers/authController.js; protected backend operations pass through backend/middleware/auth.js. The repository also includes Google auth configuration at backend/config/googleAuth.js, indicating an external identity-provider integration alongside the application’s own auth flow.

Calendar, notifications, and asynchronous work

Calendar integration is handled as an external-service boundary by backend/services/googleCalendarService.js, invoked through backend/controllers/calendarController.js. Email delivery is encapsulated in backend/services/emailService.js. Reminder processing is separated from request handling: backend/cron/reminderCron.js schedules work, while backend/services/reminderService.js determines and sends reminder actions. Time-offset parsing resides in backend/utils/parseOffset.js, supporting reminder scheduling inputs.

Dashboard and data composition

Dashboard data is assembled server-side rather than directly in the client from individual models, through backend/services/dashboardService.js and backend/controllers/dashboardController.js. The resulting user-facing view is rendered by frontend/src/pages/user/DashboardPage.jsx; organizer-specific presentation is represented by frontend/src/components/events/OrganizerDashboardModal.jsx. This creates a clear composition boundary for derived, multi-domain event and registration data.