How sunny8080/study-notion-mern-frontend works
Project Type and Purpose
• This is the frontend of a full-stack MERN Edtech application (“StudyNotion”) where:
– Instructors upload and manage courses.
– Students browse, purchase, and view course content.
• Key technologies (from README): React, Redux, Tailwind CSS, JavaScript, HTML.
• Frontend hosts as a SPA on Netlify (or similar), communicating with a Node/Express API backend.
File Structure
• Top-level:
– public/ – static HTML and manifest for the SPA
– src/
· components/ – organized into common UI widgets and “core” feature modules (Auth, Dashboard, Course, etc.)
· pages/ – React Router pages (Home, CategoryCourses, CourseDetails, Dashboard, etc.)
· redux/ – store configuration, rootReducer, feature slices (auth, cart, profile, viewCourse, addCourse)
· services/ – API connector, endpoint definitions, and per‐feature service operations (authServices, courseServices, paymentServices, etc.)
· hooks/, utils/, data/ – shared logic, constants, assets
• Config files:
– example.env → .env (environment variables, API base URL)
– netlify.toml (deployment settings)
– tailwind.config.js
README for Additional Insights
• Confirms SPA on port 3000 (dev) / Netlify in prod
• Backend lives separately on port 4000 / hosted API
• Usage flow: user → React UI → REST API → MongoDB
Diagramming Conventions
• Clear labels on every component (e.g., “React Router”, “AuthSlice”, “CourseServices”)
– UI → Redux → Services → Backend API → Database
– Payment flow: Backend → Stripe
– Blue rectangles for frontend modules
– Green rectangles for backend modules