-
Notifications
You must be signed in to change notification settings - Fork 560
📝 [Docs]: Add Missing “Project Setup Flow Diagram” in README #1649
Copy link
Copy link
Open
Labels
GSSoC '26backendIssues related to server-side, database logic or APIsIssues related to server-side, database logic or APIsdocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestfeatureImprove existing feature or add newImprove existing feature or add newfrontendIssues related to UI/UXIssues related to UI/UXgood first issueGood for newcomersGood for newcomers
Description
Metadata
Metadata
Assignees
Labels
GSSoC '26backendIssues related to server-side, database logic or APIsIssues related to server-side, database logic or APIsdocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestfeatureImprove existing feature or add newImprove existing feature or add newfrontendIssues related to UI/UXIssues related to UI/UXgood first issueGood for newcomersGood for newcomers
The current README is very detailed and well-structured, but it is missing a visual or step-by-step flow representation of how the system works end-to-end.
New contributors often struggle to quickly understand how the frontend, backend, and database interact during key actions like task creation or routine scheduling.
Suggested Improvement
Add a new section in README.md:
🔄 System Flow Overview
Include a simple flow explanation like:
User Action (Frontend)
User creates a task or drags it into a routine grid
React UI captures input using components in frontend/src/components
API Request
Axios sends request to backend:
/api/tasks
/api/routines
Backend Processing
Express route handles request
Controller processes logic (taskController.js, routineController.js)
Mongoose schema validates and stores data
Database Layer
MongoDB stores tasks, routines, and user data
Data is returned to backend after update
Response to Frontend
Backend returns JSON response
React updates UI state via Context API / hooks
💡 Why this is needed
Helps new contributors understand full-stack flow faster
Improves onboarding experience for GSSoC participants
Bridges gap between backend structure and frontend components
Reduces confusion when debugging API calls
🏷 Suggested Labels
documentation
enhancement
good first issue
🚀 Impact
Better contributor onboarding
Easier debugging and development understanding
Improved README clarity for MERN architecture