How yogndrr/mern-school-management-system works
Main components
• Frontend Client – A React.js application with various pages for Admin, Teacher, and Student roles, built using Material UI and Redux.
• Backend Server – A Node.js/Express.js API that exposes endpoints for operations like class management, user handling, attendance, and more.
• Database – A MongoDB instance that stores data related to users, classes, attendances, notices, subjects, and other school-related information.
• External Services – Though not explicitly highlighted, you may also include GitHub repositories, deployment services (Render for backend, Netlify for frontend), and any third-party libraries that enable environment-specific configurations (like the .env files).
Architectural patterns or design principles
• Separation of concerns for a full-stack application—the frontend (client-side) is completely decoupled from the backend (server-side) via RESTful APIs.
• Document the use of MVC-like patterns in the backend (controllers, models, routes) and client-side state management via Redux in the frontend.
• Properties such as environment configuration (.env usage) and service endpoints to signal good deployment practices.
Technologies and libraries
• For Frontend: React.js, Material UI, Redux.
• For Backend: Node.js, Express.js.
• For Database: MongoDB (can mention either local or Atlas configuration).
• Deployment: Render (server side) and Netlify (client side).