How firefox-d3vfr/projet-node-recette works
Project Type & Purpose
• This is a full-stack “Recipe Website” built with:
• Backend: Node.js + Express.js + MongoDB (via Mongoose)
• Frontend: React.js + SCSS + Bootstrap
• Purpose: Expose RESTful endpoints for recipes, categories, members & comments; consume these APIs in a React SPA for browsing, authentication, and user interactions.
File Structure Analysis
• Top-level
• .gitignore, README.md
• Backend/
• Frontend/mon-app-recettes/
• Backend/ follows an MVC/Layered pattern:
• app.js – Express app entrypoint
• routes/ – defines API routes
• controllers/ – handle HTTP requests, call services
• services/ – business logic, orchestrates models
• models/ – Mongoose schemas/ORM
• Frontend/mon-app-recettes/ is a standard Create React App layout:
• public/ – static HTML, manifest, images
• src/
– Pages/ – route-level React components (Categories, Recettes, Profile, etc.)
– components/ – shared UI parts (Header/Navbar, Footer, Login form…)
– App.js, index.js – SPA bootstrap
– SCSS assets for styling
Key Architectural Insights from README
• Tech stack badges confirm React on client, Express + MongoDB on server.
• Backend connects to MongoDB Atlas via .env variables.
• Frontend fetches data from backend endpoints with fetch/Axios.
• Authentication flow for login/logout managed client-side.