How adithyak2k03/classroom-management-system-mern-stack works
Project Type and Purpose
• This is a full-stack MERN (MongoDB, Express, React, Node.js) web application called “Classroom Management System.”
• Purpose: Provide teachers (admins) with a dashboard to manage students, notes, and tasks; allow students to view/edit their profile, take notes, and manage a to-do list.
File Structure
Top-level:
• backend/ – Node.js + Express REST API
– server.js: main Express app, routes mounting
– db.js: MongoDB connection logic
– package.json/.gitignore: backend dependencies & ignores
• public/ – static assets served by React (index.html, manifest.json, robots.txt)
• src/ – React application
– components/: UI building blocks (modals, grids, header, loading screen)
– pages/: route-level pages (Home, Login, Dashboard, AdminUsers, NotesHome, TaskHome, Profile, Signup)
– services/: HTTP clients wrapping API endpoints (api.js core, NotesApi, TasksApi, AdminApi)
– context/: Context API provider for user state (UserContext)
– scripts/: populateDb.js for seeding data
– stylesheets/: CSS per page/component
– App.js, index.js: root component and bootstrap
• Dev_log.md: build-log documentation
• README.md: project overview, tech stack, deployment, features
Architectural Patterns & Configurations
– Frontend splits into Presentation (components/pages) + Data-layer (services + Context API)
– Backend: RESTful API with Express routes for users, notes, tasks; uses JWT auth middleware
– Uses concurrently (npm script “both”) to spin up frontend & backend in dev
– MongoDB as the single data store
README for Insights
• Authentication: JWT
• Hosting: Frontend on Vercel, Backend on Render
• Features summary confirms 3 main domains: Users, Notes, Tasks
• Future improvements hint at role-based access control & external integrations