How manu2954/buildora works
Project type and purpose
• Buildora is a full-stack MERN application: a multi-vendor e-commerce platform for construction and building materials, composed of two user-facing apps (Admin Panel and Customer Storefront) and a Node/Express backend with MongoDB.
File structure
• Top-level separation:
• backend/ – Express server implementing RESTful API, routes → controllers → services → models (Mongoose), middleware, and utils.
• frontend/ – React single-page application, using Hooks, Context API, Tailwind CSS, and services modules to call backend endpoints.
• Patterns & layers in backend:
• auth (JWT issued/verified in auth.service, auth.middleware)
• MVC style (routes → controllers → services → models)
• Admin vs. storefront routes logically separated (controllers/admin/ vs controllers/*)
• Utilities for email, token gen, error handling
• Frontend organization:
• components/ (common UI, admin UI)
• context/ (AuthContext, AdminAuthContext, CartContext, SiteContext)
• pages/ (Customer pages vs pages/admin)
• services/ (API wrappers for each domain)
Key README insights
• Two applications: Customer Interface + Admin Panel
• Tech stack: React.js, Node/Express, MongoDB/Mongoose, JWT authentication, Tailwind CSS
• Future extensions: dealer portal, payment gateway, bulk upload, notifications