How shakthi-balan/evolve-fitness-feed works
Project type and purpose
• This is a front-end single-page application built with React (TypeScript) and Vite.
• It uses Tailwind CSS for styling and shadcn-ui as a component library.
• There is no custom backend in the repo; any data (auth, chatbot, calorie/sleep tracking, leaderboard) would be handled by external APIs or services.
File structure
• Root files: package.json, tsconfig.json, Vite and Tailwind configs → build and tooling configuration.
• public/ → static assets (robots.txt, index.html).
• src/
• main.tsx + index.html → application entry point.
• App.tsx + src/pages/ → page-level routing (Index, NotFound).
• src/components/ → feature components (AuthPage, ChatBot, Dashboard, CalorieTracker, SleepTracker, Leaderboard, ProgressFeed, BottomNavigation).
• src/components/ui/ → shadcn UI primitives and themed wrappers.
• src/hooks/ → custom hooks (useMobile, useToast).
• src/lib/ → shared utilities (utils.ts).
README for additional insights
• Confirms tech stack: Vite, TypeScript, React, shadcn-ui, Tailwind CSS.
• Deployment via “Lovable” static-hosting service.
• Suggests the app is meant to be edited and published as a static site.
Main components
a. Developer Environment
• Node.js + npm, Vite dev server.
b. Source Code
• React + TypeScript codebase (src/, public/, config files).
c. Build Pipeline
• Vite bundler compiles TSX, processes Tailwind CSS, outputs optimized static assets (dist/).
d. Static Hosting / CDN
• Lovable’s hosting service (or any CDN like Netlify/Vercel) serves index.html, JS/CSS, assets.
e. Client (Browser)
• Loads the SPA, hydrates React components, handles routing & UI.
f. External Services (optional)
• Auth provider (OAuth/JWT), Chat API (OpenAI or custom), Data storage or REST/GraphQL endpoints for calorie/sleep/leaderboard data.
Relationships and interactions
• Developer → (npm run dev) → Vite Dev Server → Browser (live reload).
• Developer → (npm run build) → Vite → Build Artifacts → Static Hosting → CDN.
• Browser ↔ Static Assets (JS/CSS).
• Browser ↔ External Services via HTTP(S) calls.
Architectural patterns and design principles
• Component-based architecture: feature components + UI primitives library.
• Separation of concerns: UI components (shadcn/ui), business logic (hooks/lib), pages for routing.
• Static single-page architecture with external API integration.
Essential elements
• Labels for each component and folder group
• Notes about key technologies (React, Vite, Tailwind CSS, shadcn-ui)