How pratikbhopi/ecommerce_project_kurtastore works
Project type and purpose
• This is a full-stack e-commerce web application named “Karma Threads,” with three primary frontends (customer client, admin panel) and a Node/Express backend that exposes REST APIs.
• Purpose: allow customers to browse and purchase kurtas, and allow admins to manage products, users, and orders.
File structure
• Top level:
• Server/ ─ Node.js + Express backend
• client/ ─ React customer-facing SPA
• admin/ ─ React admin-facing SPA
• Server side:
• controllers/ (AdminControls, Products, Users, Payments)
• services/ (mailer)
• models/ (database connection, adminDB)
• routes/ (AdminRoutes, UserRoutes)
• server.js (entry point)
• Frontends each include Vite config, Tailwind CSS, environment config, src/components, src/pages.
• Configuration: .env variables for MongoDB Atlas, JWT, Cloudinary, Razorpay, VITE_SERVER_URL.
README for additional insights
• Tech stack: React, Node.js/Express, MongoDB Atlas, Cloudinary, Razorpay.
• Features: user auth, product browsing, cart/checkout, order history, admin panel, secure payments.
Elements
• Clear labels on every block (e.g., “Express API Server,” “MongoDB Atlas,” “Cloudinary”)
• Blue for frontends
• Green for backend/application layer
• Orange for data stores
• Purple for external third-party services