How kartik-katkar/organease works
Project type and purpose
• From the README and file tree, this is a full-stack MERN (MongoDB, Express, React, Node.js) web application called “OrganEase.”
• Purpose: to replace a manual organ-requesting workflow with a unified portal where procurement/transplant centres list available organs and hospitals request compatible organs (with payment integration).
File structure
• Top‐level directories:
• client/ – React single‐page application (SPA)
• server/ – Node.js + Express REST API
• Screenshots, README.md, LICENSE, Data Privacy.pdf, vercel.json
• client/:
• public/ – static HTML/CSS
• src/ – React code, organized into components for admin and shop (hospital) sides, each with their own contexts, modals, protected routes, partials.
• serviceWorker.js, index.js – startup
• server/:
• config/ – DB connection, environment keys, upload folder script
• controller/ – business logic per resource (auth, products, orders, categories, users, braintree, customize)
• models/ – Mongoose schemas
• routes/ – Express route definitions
• middleware/ – auth guard
• server.js – application entry point
• Key patterns: client–server separation, React Context for state, MVC on the server, RESTful JSON APIs, token-based auth, Braintree payment integration.
Extract additional insights from the README
• Requires Node.js/NPM, MongoDB connection string via environment variable.
• Two processes: npm start in client and npm start:dev in server.
• URL: http://localhost:3000/
• Images of the UI illustrate an admin dashboard for managing organs/products/categories/orders and a hospital (“shop”) portal for browsing, checkout, and order history.