How amitsahoo7/e-learning-platform works
Project type and purpose
• This is a full-stack MERN (MongoDB, Express, React, Node.js) E-Learning Management System (e-LMS).
• Frontend: React + Tailwind CSS + Redux Toolkit + React Router + Axios.
• Backend: Node.js + Express + MongoDB/Mongoose + JWT auth + Multer file-uploads + bcrypt.
File structure
• Top-level “frontend” directory:
• A Vite-powered React SPA with src/components, src/pages, src/context (CourseContext, UserContext), App.jsx, and styling/config files.
• Uses environment variables (.env), ESLint, Tailwind and PostCSS, Vite config.
• Top-level “server” directory:
• Express app entry (index.js), environment config (.env).
• MVC pattern:
– models/: Mongoose schemas for Users, Courses, Lectures, Payments, Progress, Feedback
– controllers/: business logic per domain (user.js, course.js, admin.js, feedback.js)
– routes/: HTTP endpoints grouped by resource (/api/user, /api/course, /api/admin, /api/feedback)
– middlewares/: auth (isAuth), error handler (TryCatch), Multer file-upload config, sendMail
• Local file storage under uploads/ for lecture videos and PDFs.
• Shared root: package.json, .gitignore, webServerApiSettings.json
README for additional insights
• Role-based access control: Students, Instructors, Admin
• Core features: Auth & RBAC, Course CRUD, Video lecture upload/organization, Student enrollment & progress tracking, Admin approval workflows
• Future: Payment integration (Stripe/Razorpay), quizzes, discussion forums
1. Client (Browser/React SPA)
– Pages: Home, Courses, CourseDescription, CourseStudy, Lecture, Account, Admin Dashboard, etc.
– State management: Contexts (CourseContext/UserContext) or Redux Toolkit
– API layer: Axios calls to backend
2. API Layer (Node/Express Server)
– Router: /api/user, /api/course, /api/admin, /api/feedback
– Controllers & Middlewares: Authentication (JWT), Authorization (RBAC), Error Handling, File Upload (Multer), Email Service
3. Data Storage
– MongoDB (collections: users, courses, lectures, payments, progress, feedback)
– File System (uploads folder for videos/PDFs; could be replaced by S3/minio)
4. External Services
– Email SMTP (sendMail middleware)
– (Future) Payment Gateway (Stripe/Razorpay)
– Client → Axios HTTP(S) → Express API
– Express → Middleware chain (auth → controllers)
– Controllers ↔ Mongoose → MongoDB
– Multer middleware → File System → returns file URL/path → DB
– Express → Email service (SMTP) for verification, notifications
– (Future) Express ↔ Payment Gateway API
c. Architectural patterns & design principles:
– Client-Server separation (clear boundary)
– MVC-style on backend (Models, Controllers, Routes)
– RESTful API endpoints
– RBAC using JWT and isAuth middleware
– Context/Redux on frontend for state isolation
– Modular directory structure for scalability and maintainability
d. Key technologies & frameworks:
– Frontend: React (JSX), Tailwind CSS, Vite, Axios, React Router, Redux Toolkit (or Context API)
– Backend: Node.js, Express, Mongoose, JWT, Multer, bcrypt, dotenv