How jeeyan28/the-riverview works
Riverview appears to be a venue reservation and operations system: customers browse facilities, reserve and pay for sessions, while staff manage bookings, room sessions, and administration. The graph covers the routed web experience and the principal backend domains, including payments, reporting, settings, and notifications. Backend route-to-model and helper links follow the SOURCE INDEX; frontend-to-backend transport is not shown in the excerpts, so that boundary is left unconnected. Several capabilities are represented by their exact route or page directories because their implementation was not sampled.
Main entry points: server.js API server · bookingRoutes.js Booking workflow · monitoringRoutes.js Room sessions · App.jsx Web routes
Components 24
Web experience
- Web routes
FrontEnd/src/App.jsx - Customer pages
FrontEnd/src/pages - Admin pages
FrontEnd/src/pages/Admin - API client
FrontEnd/src/services/api.js - API server
BackEnd/server.js
Identity and access
- Authentication
BackEnd/routes/auth.js - User accounts
BackEnd/routes/userRoutes.js - Access control
BackEnd/middleware/adminAuth.js
Reservations and payments
- Booking workflow
BackEnd/routes/bookingRoutes.js - Booking rules
BackEnd/utils/bookingHelper.js - Booking records
BackEnd/model/booking.js - Payment processing
BackEnd/routes/paymongoRoutes.js - Payment gateways
BackEnd/utils/paymongo.js
Venue operations
- Facility catalog
BackEnd/routes/roomRoutes.js - Room sessions
BackEnd/routes/monitoringRoutes.js - Monitor records
BackEnd/model/monitoring.js - Venue settings
BackEnd/routes/settingsRoutes.js - Settings records
BackEnd/model/settings.js
Administration and insight
- Reports and forecasts
BackEnd/routes/forecastRoutes.js - Admin reporting
BackEnd/routes/dashboardRoutes.js - Audit history
BackEnd/utils/auditLog.js - Reservation notices
BackEnd/utils/reservationNotifications.js
Other components
- Customer
- Venue staff
Connections 30
- Customer → Web routes: uses
- Venue staff → Web routes: uses
- Web routes → Customer pages: routes to
FrontEnd/src/App.jsx - Web routes → Admin pages: routes to
FrontEnd/src/App.jsx - Web routes → API client: requests data
- API server → Authentication: mounts
BackEnd/server.js - API server → Facility catalog: mounts
BackEnd/server.js - API server → Room sessions: mounts
BackEnd/server.js - API server → Booking workflow: mounts
BackEnd/server.js - API server → User accounts: mounts
BackEnd/server.js - API server → Venue settings: mounts
BackEnd/server.js - API server → Payment processing: mounts
BackEnd/server.js - API server → Reports and forecasts: mounts
BackEnd/server.js - API server → Admin reporting: mounts
BackEnd/server.js - Booking workflow → Booking records: reads and writes
BackEnd/routes/bookingRoutes.js - Booking workflow → Booking rules: delegates to
BackEnd/routes/bookingRoutes.js - Payment processing → Booking records: reads and writes
BackEnd/routes/paymongoRoutes.js - Payment processing → Booking rules: prices bookings
BackEnd/routes/paymongoRoutes.js - Payment processing → Payment gateways: creates intents
BackEnd/routes/paymongoRoutes.js - Room sessions → Monitor records: reads and writes
BackEnd/routes/monitoringRoutes.js - Room sessions → Booking records: reads bookings
BackEnd/routes/monitoringRoutes.js - Room sessions → Facility catalog: reads catalog
BackEnd/routes/monitoringRoutes.js - Venue settings → Settings records: reads and writes
BackEnd/routes/settingsRoutes.js - Venue settings → Audit history: records changes
BackEnd/routes/settingsRoutes.js - Booking workflow → Access control: guards actions
BackEnd/routes/bookingRoutes.js - Room sessions → Access control: guards actions
BackEnd/routes/monitoringRoutes.js - User accounts → Access control: guards actions
BackEnd/routes/userRoutes.js - Reports and forecasts → Access control: guards access
BackEnd/routes/forecastRoutes.js - Booking workflow → Reservation notices: sends notices
BackEnd/routes/bookingRoutes.js - Booking workflow → Audit history: records actions
BackEnd/routes/bookingRoutes.js