vishwa374/revenue_audits

Purpose

This repository implements a hotel-performance and conversion-analysis dashboard. Its visible product surface combines data-entry/audit views with KPI, chart, performance-table, and conversion-blocker reporting. The README provides no operational guidance, so the component names and entry files define the available architecture evidence.

Application Entry Points

• Frontend bootstraps from frontend/src/index.js and mounts the root application in frontend/src/App.js.

• The backend service entry point is backend/server.py.

• The frontend is configured as a JavaScript single-page application, with static host deployment metadata in frontend/vercel.json and the document shell at frontend/public/index.html.

Frontend Composition Layer

frontend/src/App.js is the likely composition and state-boundary point for the dashboard. Product-level views are separated into focused components:

• Hotel input/audit workflow: frontend/src/components/HotelAudit.jsx, frontend/src/components/FormSection.jsx

• Summary and reporting: frontend/src/components/ResultsDashboard.jsx, frontend/src/components/KPIDashboard.jsx

• Analytical detail: frontend/src/components/EnhancedCharts.jsx, frontend/src/components/PerformanceTable.jsx, frontend/src/components/ConversionBlockers.jsx

This separation suggests a flow from hotel/audit inputs to synthesized results, then to KPI, chart, table, and issue-oriented presentations.

Primary Data and Control Flow

The probable client flow is:

1. Users provide or review hotel/audit data through HotelAudit and FormSection.

2. The root application coordinates submitted state and any request to the backend.

3. Returned or derived analysis is presented by ResultsDashboard.

4. Specialized result projections render KPIs, trends/comparisons, tabular performance, and identified conversion blockers.

The frontend/backend boundary is between the React application under frontend/src/ and the server process at backend/server.py. No database, queue, authentication provider, or external analytics API is identifiable from the supplied tree.

UI System and Presentation Boundary

The dashboard uses a reusable local UI component layer under frontend/src/components/ui/, including inputs, forms, cards, tables, tabs, dialogs, and toast notifications. Product components should consume this layer rather than encode shared interaction primitives independently. Styling is centered in frontend/src/App.css, frontend/src/index.css, and Tailwind configuration at frontend/tailwind.config.js.

Runtime and Deployment

• Frontend: Node-based React build/runtime configuration, indicated by frontend/package.json, frontend/craco.config.js, and frontend/src/index.js.

• Backend: Python service dependencies are declared in backend/requirements.txt, with execution logic in backend/server.py.

• Hosting: frontend/vercel.json indicates Vercel-oriented frontend deployment; backend deployment topology is not specified.