How desai1611/xs-hair-beauty works
XS Hair & Beauty is a salon website with a public service/product/review experience, enquiry booking, and a JWT-protected admin dashboard. Visitors browse database-backed content and submit an enquiry; the backend persists it and attempts email notifications. Admins manage bookings and salon content through the dashboard. The graph combines sampled routing, booking, and content-fetch code with capabilities explicitly documented in the README; unsampled implementation details are not inferred beyond those documented relationships.
Main entry points: app.js HTTP application · client.js API client · routes Content routes · bookingRoutes.js Booking routes
Components 22
Public website
- Public pages
frontend/src/pages - Booking form
frontend/src/pages/Contact.jsx - Content fetching
frontend/src/hooks/useFetch.js - API client
frontend/src/api/client.js
Admin dashboard
- Admin screens
frontend/src/pages/admin - Resource manager
frontend/src/components/admin/ResourceManager.jsx - Admin authentication
frontend/src/context/AuthContext.jsx
REST API
- HTTP application
backend/src/app.js - Authentication routes
backend/src/routes/authRoutes.js - Booking routes
backend/src/routes/bookingRoutes.js - Content routes
backend/src/routes - Upload routes
backend/src/routes/uploadRoutes.js - Booking handling
backend/src/controllers/bookingController.js - Review handling
backend/src/controllers/reviewController.js - Content controllers
backend/src/controllers - JWT protection
backend/src/middleware/auth.js - Image upload
backend/src/middleware/upload.js
Persistence and messaging
- MongoDB records
backend/src/models - Email notifications
backend/src/utils/mailer.js
Other components
- Visitor
- Admin user
- Email service
Connections 26
- Visitor → Public pages: browses
- Visitor → Booking form: submits enquiry
README.md - Public pages → Content fetching: loads content
frontend/src/pages/BeautyServices.jsx - Content fetching → API client: requests data
frontend/src/hooks/useFetch.js - Booking form → API client: sends enquiry
README.md - Admin user → Admin screens: manages salon
- Admin screens → Resource manager: uses CRUD UI
frontend/src/pages/admin/ReviewsPanel.jsx - Resource manager → API client: sends CRUD requests
frontend/src/components/admin/ResourceManager.jsx - Admin authentication → API client: uses API
frontend/src/context/AuthContext.jsx - API client → HTTP application: calls REST API
README.md - HTTP application → Authentication routes: mounts
backend/src/app.js - HTTP application → Booking routes: mounts
backend/src/app.js - HTTP application → Content routes: mounts
backend/src/app.js - HTTP application → Upload routes: mounts
backend/src/app.js - Booking routes → Booking handling: routes requests
backend/src/routes/bookingRoutes.js - Content routes → Content controllers: routes content requests
backend/src/routes/reviewRoutes.js - Content routes → Review handling: routes review requests
backend/src/routes/reviewRoutes.js - Booking routes → JWT protection: protects admin routes
backend/src/routes/bookingRoutes.js - Content routes → JWT protection: protects admin routes
backend/src/routes/reviewRoutes.js - Upload routes → JWT protection: protects uploads
backend/src/routes/uploadRoutes.js - Upload routes → Image upload: handles files
backend/src/routes/uploadRoutes.js - Booking handling → MongoDB records: stores bookings
backend/src/controllers/bookingController.js - Booking handling → Email notifications: requests notifications
backend/src/controllers/bookingController.js - Email notifications → Email service: sends email
README.md - Review handling → MongoDB records: reads and writes reviews
backend/src/controllers/reviewController.js - Content controllers → MongoDB records: reads and writes content
backend/src/controllers/reviewController.js