Travel Hub CRM is an interactive product prototype for managing the operational lifecycle of a travel order. It brings sales, booking services, passengers, suppliers, finance, documents, notifications, and team communication into one role-aware workspace.
The repository focuses on product flows and interface behavior. It uses realistic demo data so stakeholders can validate navigation, information hierarchy, and operational scenarios before backend integration.
- Role-specific manager dashboard and KPI views
- Orders with status chain, passenger details, services, and activity context
- Air, rail, hotel, transfer, bus, and tour service workflows
- Clients, companies, suppliers, and commercial offers
- Finance operations, payments, debt, commissions, and returns
- Document center, receipts, and fulfillment workflow
- Route-receipt import and reconciliation experience
- Global notifications center
- Contextual team chat and order-linked discussions
- Role-based access and protected sections
- Responsive drawers, tables, filters, and action menus
The prototype is split into focused page and system modules instead of one monolithic file:
index.html # application shell, tokens, and global styles
js/app.jsx # authentication, routing, roles, shared state
js/page_*.jsx # domain pages and workflows
js/components*.jsx # shared UI building blocks
js/data*.js # realistic demonstration data
| Area | Technology |
|---|---|
| Interface | React and JSX |
| Styling | Custom responsive CSS and reusable design tokens |
| State | React state with shared in-memory demo data |
| Product model | Role-aware routes and domain-specific modules |
| Delivery | Static deployment suitable for rapid stakeholder review |
No application secrets or backend services are required for the prototype.
python3 -m http.server 8000Open http://localhost:8000.
This repository is a high-fidelity frontend prototype. The following are simulated for product validation:
- Authentication
- Service search results
- Document processing
- Payments and finance actions
- Notifications and chat data
- Role switching
A production implementation would connect the existing flows to authenticated APIs, persistent storage, provider integrations, audit logging, and organization-level access control.
The CRM is designed to reduce context switching between messengers, spreadsheets, reservation tools, documents, and financial records. Its main principle is to keep every operational action connected to the correct order and customer.