How ablamalki/shoppy works
Project Type & Purpose
• A frontend-only React Single-Page Admin Dashboard (“Shoppy”) using React.js, TailwindCSS and Syncfusion EJ2 for charts, tables, calendar and Kanban.
Main Components
• Public Layer:
– index.html, manifest and static assets served by a web server.
• React App:
– Entry: src/index.js → ContextProvider → App.js.
– Layout: Sidebar, Navbar, Header, ThemeSettings, UserProfile, Chat, Notifications.
– Pages: Dashboard, Orders, Customers, Kanban, Calendar, Team, Charts (Area, Bar, Line, Pie, Stacked).
– UI Widgets: Button, Charts (LineChart, PieChart, Stacked), ChartsHeader.
– Data: src/assets/data.js (static JSON).
• Styling: Tailwind config + global/index.css + component CSS.
Relationships & Data Flow
• Browser → index.html → bundles → React entry.
• ContextProvider manages theme & shared state → consumed by components/pages.
• Pages import UI widgets & data → render charts and tables.
• User actions → Context updates → re-render downstream components.
Architectural Patterns & Tech
• SPA with Context API for state management.
• Component-based hierarchy: Layout → Pages → Reusable UI components.
• TailwindCSS utility classes; Syncfusion EJ2 chart/calendar modules.
• Purely client-side; no external API in code (can be extended).