How rissingh23/calendub-web works
Project Type & Purpose
• CalenDUB is a full-stack, single-page web application (React + Tailwind CSS) backed by a Node.js/Express API and MongoDB.
• Purpose: aggregate and display University of Washington RSO events, enable RSVPs, reminders, and RSO-specific filtering.
File Structure
Top-level directories:
• client/ → React/Vite front-end
• server/ → Node.js/Express back-end
Supporting files:
• render.yaml → deployment config
• README.md → high-level overview
Key subdirectories:
• client/src/components & client/src/routes → UI components & pages
• client/src/context/AuthContext.tsx → React Context for authentication state
• client/src/utils/*.ts → client-side services (API wrappers, AI recommendations, email utils)
• server/models/ → Mongoose schemas (User, Event, Organizer, PersonalEvent)
• server/routes/ → Express routers (userRoutes, eventRoutes, organizerRoutes)
• server/middleware/auth.js & firebase/verifyToken.js → JWT & Firebase token validation
• server/config/database.js → MongoDB connection
• server/utils/emailUtils.js → outgoing email logic
• server/seed-data/ → DB seeding scripts
Extract Architectural Insights from README
• Frontend: React + Tailwind CSS; served on localhost:3000 via Vite
• Backend: Node.js, Express, JWT & Firebase Auth, MongoDB
• Features: directory search, RSVP/reminders, RSO filters, notifications
Main System Components
a. Frontend Client (Browser)
– React SPA (Pages + Reusable Components)
– AuthContext (manages JWT/Firebase ID tokens)
– API service layer (client/src/utils/api.ts using axios or fetch)
b. Backend API Server
– Express application (server/index.js & app.js)
– Routing layer (server/routes/*)
– Middleware for auth (JWT + Firebase verify)
– Controllers/business logic (in route handlers)
– Data access via Mongoose models (server/models/*.js)
c. Database
– MongoDB cluster (connected via server/config/database.js)
d. External Services
– Firebase Authentication (client for sign-in, server verifyToken, firebase-admin)
– Email service (SMTP or SendGrid via server/utils/emailUtils.js)
e. File Storage
– Local uploads folder (server/uploads/organizers)
Component Interactions & Data Flow
1. User interacts with React UI → triggers page/component events
2. Auth flow: GoogleLoginButton → Firebase Auth SDK → receives ID token → stored in AuthContext
3. Protected API calls: AuthContext attaches JWT/Firebase token to HTTP headers → sent to Express server
4. Express middleware verifies token (JWT or firebase-admin.verify) → passes request to router
5. Router handlers call Mongoose models → read/write MongoDB
6. If needed, server/utils/emailUtils sends email reminders/RSVP confirmations
7. Server responds → frontend updates UI state
8. Optional: client utils (aiRecommendations) may call third-party AI APIs
Architectural Patterns & Principles
– Layered architecture: Presentation (UI) → API layer → Business logic → Data access → Database
– MVC-style on server: Routes (Controllers) + Models (Mongoose)
– Separation of concerns: React components vs. service utils vs. context vs. styling
– Token-based authentication: JWT + Firebase custom claims
– Progressive enhancement: seed-data for local development, file-based uploads
[ ] Frontend (React SPA)
– UI Components & Pages
– AuthContext / Token store
– API Client Layer
[ ] Backend (Express API)
– Auth & Verification Middleware
– Route Handlers (user, event, organizer)
– Business Logic / Controllers
– Mongoose Models
– Configuration (DB connection)
[ ] MongoDB (Database)
[ ] Firebase Auth (External Auth Service)
[ ] Email Service (External Notification)
[ ] File Storage (uploads directory)
[ ] Deployment Platform (Render or other)