How bruce70345/suspendedmeal works
Project type and purpose
• Key technologies: Next.js (frontend), Node.js + Express (backend), MongoDB + Mongoose (database), Zustand (client state), Material UI, Google Maps API.
File structure
• Top level:
• backend/
– main.js (Express server entry)
– routes/ (productsRoute.js, usersRoute.js, signRoute.js)
– MongoDB/models/ (freeMealProductModel.js, freeMealUserModel.js)
– .env, package.json
• frontend/
– Next.js v13 “app” directory with pages/components (NavBar, Footer, map wrappers, signin/signup pages, about/info pages)
– src/app/hooks (custom hooks for product display & user location)
– src/app/lib (UI helpers & GoogleMap wrappers)
– providers & stores (Zustand stores for counter, login state, product data)
– .env, next.config.mjs, package.json
README for additional insights
• Features: Google Maps integration for visualizing meal availability, restaurant signup/login, CRUD meal management, passphrase-based claim.
• Dependencies confirm the tech stack above.
Key details to capture
• The three core domains: UI/UX, business logic, data persistence.
• The custom hooks and Zustand stores as the client-side state management layer.
• The endpoint structure under /products, /users, /sign.
• Google Maps integration path (script load → map initialization → marker rendering via Locations & PoiMakers).