How sinaremanav/kalpana-multispeciality-dental-hospital works
Kalpana Dental Clinic is a patient-facing dental clinic website paired with an admin and doctor management portal. Patients browse clinic information, submit appointments or inquiries, and contact the clinic; staff authenticate, review bookings and messages, and manage clinic content. The frontend uses modular data services and Supabase, while the Express backend exposes API and authentication routes. The README documents capabilities whose source was not sampled; those are represented at subsystem level where exact implementation paths are unavailable.
Main entry points: App.jsx Route Application · supabaseClient.js Supabase Client · src/pages Clinic Pages · admin/pages Content Managers
Components 24
Patient Portal
- Route Application
frontend/src/App.jsx - Clinic Pages
frontend/src/pages - Appointment Booking
frontend/src/pages/Appointment.jsx - Contact Inquiry
frontend/src/pages/Contact.jsx - Public Components
frontend/src/components
Admin Portal
- Session and Roles
frontend/src/admin/context/AuthContext.jsx - Admin Routes
frontend/src/App.jsx - Content Managers
frontend/src/admin/pages - Admin Dashboard
frontend/src/admin/pages/Dashboard.jsx - Admin UI Components
frontend/src/admin/components
Data Services
- Appointment Service
frontend/src/services/appointmentService.js - Contact Service
frontend/src/services/contactService.js - Content Services
frontend/src/services - Authentication Service
frontend/src/services/authService.js - Image Storage Service
frontend/src/services/storageService.js - Supabase Client
frontend/src/lib/supabaseClient.js
Backend API
- Express Server
backend/server.js - API Routes
backend/routes/api.js - Backend Auth Routes
backend/routes/auth.js - Backend Supabase Client
backend/lib/supabase.js - Fallback Data
backend/data/index.js
Other components
- Patients
- Clinic Staff
- Supabase
Connections 27
- Patients → Route Application: opens site
README.md - Clinic Staff → Route Application: opens portal
README.md - Route Application → Clinic Pages: routes to
frontend/src/App.jsx - Route Application → Admin Routes: routes to
frontend/src/App.jsx - Clinic Pages → Appointment Booking: books through
README.md - Clinic Pages → Contact Inquiry: sends inquiries
README.md - Route Application → Public Components: renders shared UI
frontend/src/App.jsx - Appointment Booking → Appointment Service: submits booking
README.md - Contact Inquiry → Contact Service: submits inquiry
README.md - Appointment Service → Supabase Client: uses client
frontend/src/services/appointmentService.js - Contact Service → Supabase Client: uses client
README.md - Supabase Client → Supabase: connects to
README.md - Admin Routes → Content Managers: routes to
frontend/src/App.jsx - Admin Routes → Admin Dashboard: routes to
frontend/src/App.jsx - Admin Routes → Session and Roles: provides auth
frontend/src/App.jsx - Session and Roles → Authentication Service: uses service
frontend/src/admin/context/AuthContext.jsx - Authentication Service → Supabase Client: uses client
frontend/src/services/authService.js - Content Managers → Content Services: manages clinic data
README.md - Content Managers → Admin UI Components: uses management UI
frontend/src/admin/pages/DoctorsManager.jsx - Admin UI Components → Image Storage Service: uploads images
frontend/src/admin/components/ImageUploader.jsx - Image Storage Service → Supabase Client: uses client
frontend/src/services/storageService.js - Express Server → API Routes: registers routes
backend/server.js - Express Server → Backend Auth Routes: registers routes
backend/server.js - API Routes → Backend Supabase Client: uses client
backend/routes/api.js - API Routes → Fallback Data: loads fallback data
backend/routes/api.js - Backend Auth Routes → Backend Supabase Client: uses client
backend/routes/auth.js - Backend Supabase Client → Supabase: connects to
README.md