How sahilgiri49/fire-free-arena-hub works
Project type and purpose
• This is a full-stack single-page web application. The front end is a React + TypeScript SPA built with Vite, Tailwind CSS and shadcn-ui. The back end is provided as a Backend-as-a-Service via Supabase (authentication, database, real-time, storage).
• The app delivers tournament, team, news and live-stream features, plus an admin dashboard for managing those resources.
File structure
• Top-level:
• package.json, vite.config.ts, tsconfig.*.json, tailwind.config.ts – front-end build and config.
• public/ – static assets (HTML shell, robots.txt).
• supabase/ – Supabase config.toml and SQL migrations (defines your database schema).
• src/:
• main.tsx – SPA entry point.
• App.tsx / App.css – root component.
• components/ – reusable UI and domain-specific components (hero, leaderboard, tournament cards…).
• components/ui/ – shadcn-ui primitives (buttons, dialogs, tables, etc.).
• context/AuthContext.tsx – React context for auth state.
• hooks/ – custom hooks (mobile detection, toast).
• integrations/supabase/ – Supabase client setup and types.
• pages/ – route components (Index, News, Teams, Tournaments, Profile, plus admin sub-folder).
• lib/utils.ts – utility functions.
README for additional insights
• Confirms tech stack: Vite, TypeScript, React, shadcn-ui, Tailwind CSS.
• Mentions deployment and domain setup via Lovable (the hosting platform).
Elements
• Clear labels for each component or group.
– Asset requests (Browser → CDN)
– API calls & real-time subscriptions (SPA ↔ Supabase)
– Migration deployment (DevOps → Supabase DB)
– Another for external systems (e.g., gray)
• Separate user flows for normal users vs. admin users.
Detailed but not over-engineered
• Supabase features distinctly (Auth vs. DB vs. Real-time).
• Build/deploy step (Vite → static assets → Lovable CDN).