How fardinkazi/healthbooker works
Project type and purpose
• HealthBooker is a full-stack healthcare booking platform.
• It provides a React-based single-page frontend for users and doctors, and an Express/Node.js REST API backend connected to MongoDB.
• Key features include user registration/login, doctor listing and applications, appointment booking and status tracking, notifications, and an admin dashboard.
File structure
• Top-level “client” folder holds the React app:
• src/components & src/pages for UI components and views
• src/redux for state management (Redux Toolkit)
• helper, middleware, images, styles
• Root contains the Node/Express API:
• server.js and .env for configuration
• routes/*.js define REST endpoints
• controllers/*.js implement business logic (MVC-style)
• models/*.js define Mongoose schemas
• middleware/auth.js for JWT auth
• db/conn.js for MongoDB connection
• Build and deployment artifacts (client/build) and package.json files confirm a standard build + serve workflow.
README for additional insights
• Technologies: React, Redux Toolkit, Node.js, Express, MongoDB
• Admin workflow requires toggling isAdmin in the database
• The app is hosted (e.g., Render), using environment variables for secrets and DB URL.
Detail
• Essential modules: frontend pages, API routes, controllers, models, and middleware
• How static assets (client/build) are served (via Express or a CDN)
• Environment configurations (.env) and where secrets live
• Don’t overthink—break the system into these components and show how data flows between them