How pradumn88/lms-college-site works
Project Type & Purpose
• This is a full-stack college LMS (Learning Management System).
• Frontend: React/Vite single-page app with separate Educator and Student views.
• Backend: Node.js/Express REST API.
• Persistence & Services: MongoDB for data, Cloudinary for media, Stripe (via webhooks) for payments.
Main Components
a. User Clients (Student & Educator browsers/mobile)
b. Frontend Application
• Vite-powered React SPA
• Context layer (AppContext.jsx)
• Components directory (UI widgets)
• Pages directory (route targets)
c. Backend Application
• Express server (server/server.js)
• Routes layer (userRoutes, courseRoutes, educatorRoutes, webhook)
• Controllers (handle request logic)
• Middlewares (authMiddleware)
• Models (Mongoose schemas: User, Course, Purchase, CourseProgress)
• Configs (MongoDB, Cloudinary, multer)
d. Datastore & External Services
• MongoDB Atlas
• Cloudinary (media upload)
• Stripe (payment + webhooks)
e. Deployment / Hosting
• Vercel (Client)
• Vercel or Node host (Server)
Relationships & Data Flows
• User → Frontend: HTTP (browser loads index.html, then API calls via fetch/axios).
• Frontend → Backend: REST API over HTTPS:
– Authentication endpoints (login/signup) → authMiddleware → userController
– Course management (CRUD) → courseController
– Educator endpoints → educatorController
– Webhooks (Stripe) → webhooks.js
• Backend → MongoDB: Mongoose queries for User, Course, Purchase, Progress
• Backend → Cloudinary: media uploads via cloudinary.js + multer middleware
• Backend ↔ Stripe: webhooks for payment fulfillment
Architectural Patterns & Principles
• Separation of concerns (Presentation vs. Business Logic vs. Data Access)
• MVC-style layering in the backend (Models, Controllers, Routes)
• Component-based UI in the frontend (React)
• Context API for global state management
• Middleware for cross-cutting concerns (auth, file-upload)