How arihantjain04/tidlr works
Project type and purpose
• This is a single-page application (SPA) built with React, Vite, and TypeScript.
• Purpose: A frontend client for “Lovable” that renders course pages, handles authentication, and interacts with Supabase for data and auth services.
• Key indicators:
• Vite/Vite config, React/TSX files, Tailwind + shadcn-ui components.
• Supabase integration folder and config.toml.
File structure
Top-level:
• public/ – static assets (HTML template, favicon, robots.txt, sitemap).
• src/ – all application code:
– main.tsx, index.css, App.tsx – entry point and global styles.
– components/ – reusable UI pieces and shadcn-ui primitives.
– pages/ – route targets: Index, Auth, Dashboard, Course, AdminPanel, etc.
– hooks/ – custom React hooks (useAuth, useMobile, useToast).
– integrations/supabase – supabase client and types.
– lib/utils.ts – shared utilities.
• supabase/ – local supabase CLI config & temporary files.
• config files – tsconfig, vite.config.ts, tailwind.config.ts, vercel.json, urls.json.
Architectural patterns:
• Component-based UI layer (React + shadcn-ui).
• Page routing (likely React Router) with ProtectedRoute wrapper.
• Service integration layer for Supabase (client.ts).
• Tailwind CSS for styling.
• Hosted/deployed via Vercel (vercel.json) with CI via Lovable.
README for additional insights
• Tech stack: Vite, TypeScript, React, shadcn-ui, Tailwind.
• Deployment: Lovable → Share → Publish, supports custom domains.
• Development: standard npm workflow.