How santiagoqp23/restaurant-web-app works
Project type and purpose
• This is a single-page application (SPA) implemented in React + TypeScript, built with Vite, and deployed as static assets (Netlify).
• Purpose: a full-featured restaurant management system (order taking, kitchen display, billing, menu management, reports, user & table management) that communicates with an external backend via REST and WebSockets.
File structure
• Top-level:
• public/: static assets (images, index.html)
• src/: all React code
• src/api/: Axios REST client + React Query setup
• src/context/, src/hooks/: cross-cutting concerns (SocketContext, MenuContext, custom hooks)
• src/redux/: Redux slices for auth, menu, orders, tables, users
• src/pages/: feature folders (Public/Auth/Shop, Private/Dashboard, Orders, Menu, Bills, Balance, Reports, etc.)
• src/components/ui: shared UI primitives
• src/theme, src/styles: theming & global styles
• config: .env, netlify.toml, tsconfig, vite.config.ts
README for additional insights
• It confirms core features: Dashboard, Orders, Kitchen view, Menu management, Tables, Users, Clients, Cash register, Reports.
• It does not ship its own backend—relies on a REST API (“restauranteApi.ts”) and WebSocket events for real-time updates.