How rbsuhail/zomatoapp works
Project type and purpose
• ZomatoClone is a modern, full-stack restaurant discovery platform.
• Frontend built in React + TypeScript + Tailwind. Backend in Node.js + Express + MongoDB.
• Key features: text/location/image search, filters, ratings, responsive UI.
File structure
• Top-level:
• ZomatoApp/src → React app (components, pages, context, utils, types)
• ZomatoApp/server → Express API (models, routes, server.js)
• ZomatoApp/scripts → data-import script
• Config files (ESLint, PostCSS, Tailwind, Vite, tsconfig)
• Patterns:
• Frontend: component-driven, context for global state, service wrapper for Axios
• Backend: MVC-style (Models in /models, Controllers implicitly in /routes), single Node monolith
• Deployment:
• Vite dev server (port 5173) + Express dev server (port 5000)
• .env for MongoDB URI, port
Extract additional insights from README
• REST API endpoints under /api/restaurants and /api/search
• Image upload (Multer) for food-image search
• Scripts to import seed data into MongoDB
• Tech stack confirms React ↔ Axios ↔ Express ↔ MongoDB flow
Elements
• Clear labels: “Browser / React Frontend”, “Express API Server”, “MongoDB”
• From React to each REST endpoint
• From Express to MongoDB
• From Browser geolocation API to React
• File upload flow from React → Express (Multer)
• Blue rectangles for frontend components
• Orange rectangle for backend services