How editm07/academo-track works
Project type and purpose
• This is a Single-Page Application (SPA) built with Vite, TypeScript, React, Tailwind CSS and the shadcn-ui component library.
• It uses Supabase as a Backend-as-a-Service (BaaS) for authentication, database and migrations.
• From the pages (Attendance, Grades, Reports, Students, Subjects, Dashboard, Auth) it appears to be a school-management dashboard.
File structure
• Top-level:
• config files for Vite, Tailwind, TypeScript, ESLint
• supabase/ (config.toml + SQL migrations)
• public/ (static assets, robots.txt)
• src/:
• App.tsx + main.tsx entrypoints
• pages/ (route components)
• components/ (AppSidebar, ProtectedRoute, plus a full shadcn-ui UI library under components/ui/)
• hooks/ (custom React hooks like use-mobile, use-toast)
• integrations/supabase (client setup, type definitions)
• lib/utils.ts (shared helpers)
• No custom backend code—Supabase handles auth, DB and migrations.
README for additional insights
• Confirms stack: Vite, TS, React, shadcn-ui, Tailwind.
• Deployment managed by Lovable (a platform which automatically builds & publishes the Vite app).
• Supabase migrations live in the repo, so infra is versioned alongside the frontend.
Main components & interactions
a. Components:
1. Developer Environment (IDE, Git CLI)
2. Source Code Repository (GitHub or Lovable’s Git)
3. CI/CD / Build & Deploy (Lovable Platform)
4. Static Hosting CDN (Lovable’s hosting or equivalent)
5. Browser / Client Device
6. React SPA (bundles loaded into browser)
– Presentation Layer: shadcn-ui + Tailwind CSS
– Routing Layer: React Router or ProtectedRoute
– View Layer: pages/* components
– Shared Components & Hooks: src/components, src/hooks
7. Supabase BaaS:
– Auth service
– Postgres database
– Migrations (from supabase/migrations)
– API endpoints (REST / Realtime / GraphQL)
b. Data flows & relationships:
• Developer → commits → Repo
• Repo → triggers → Lovable CI/CD → builds → publishes static assets to CDN
• Browser → GET index.html & JS/CSS bundles from CDN
• React SPA → internal routing → renders pages & UI components
• React SPA → Supabase client → Auth API (login, tokens)
• React SPA → Supabase client → Database queries (CRUD for attendance, grades, etc.)
• Supabase → responses → React SPA
c. Architectural patterns / design principles:
– SPA architecture with client-side routing
– Component-based design (shadcn-ui library + custom UI components)
– Hooks for cross-cutting concerns (mobile detection, toast notifications)
– BaaS integration (no custom backend code)
– Versioned database migrations alongside front-end code
d. Key technologies / frameworks:
– Vite (build & dev server)
– React + React Router
– TypeScript
– Tailwind CSS + shadcn-ui
– Supabase (Auth, Postgres, Migrations)
– Lovable platform (CI/CD, hosting)
Essential architectural elements
• Pipeline from code→deploy to runtime.
• That all backend interactions go through Supabase’s client SDK.