How manthann07/msu-footprint works
Project type and purpose
• This is a full-stack “Meal Planner Platform” composed of a React/Tailwind frontend and a Node/Express backend.
• Purpose: provide personalized meal plans, BMI calculation, and an AI assistant (via Gemini API) to suggest meals and nutritional information.
File structure
• Top level splits into two directories:
• nutrition-planner-frontend (Vite + React, Tailwind, context providers, pages/components)
• nutrition-planner-backend (Express API, MongoDB config, auth middleware, routes, User model)
• Key config files: .env files, vite.config.js (frontend), config/db.js, server.js (backend).
• Patterns:
• Frontend uses Context API (AuthContext, MealPlanContext), routing (ProtectedRoute.jsx).
• Backend follows a simple MVC style: routes ↔ controllers (in routes/), models/ (User.js), middleware/auth for JWT validation.
README insights
• Architecture overview: React frontend ↔ Node/Express REST API ↔ MongoDB database, plus external AI (Gemini API).
• Auth with JWT.
• Environment variables orchestrate API endpoints and secrets.
Elements
• Clear labels: “React Client,” “Express API,” “MongoDB,” “Gemini AI Service”
• UI → API (requests)
• API → DB (CRUD)
• API → AI (HTTP call)
• API → UI (responses)
• Backend components in another (e.g., green)