How mandap360/hall-harmony-finance works
Project type and purpose
• This is a full-stack web application: a React/TypeScript single-page app (SPA) built with Vite, styled with Tailwind CSS and shadcn-ui, using Supabase as a Backend-as-a-Service (database + auth).
• Purpose: financial/accounting management (accounts, transactions, bookings, vendors, reports).
File structure
• Top-level:
• src/ holds the entire frontend code (App.tsx, pages/, components/, hooks/, integrations/, lib/).
• public/ for static assets (robots.txt, index.html).
• supabase/ contains Supabase config & migrations for the Postgres schema and DB functions.
• config files (tsconfig, vite.config.ts, tailwind.config.ts).
• Patterns:
• SPA with React Router (src/pages + ProtectedRoute).
• Component-driven UI (src/components + nested feature folders).
• Custom hooks for each data domain (useAccounts, useExpenses, etc.).
• BaaS integration in src/integrations/supabase/client.ts.
README for additional insights
• Stack: Vite, TS, React, shadcn-ui, Tailwind CSS.
• Deployment via Lovable (likely automates build + hosting).
• No explicit server beyond Supabase.
Detail
• Feature domains (Accounts, Bookings, Expenses, Reports).
• Integration layer (src/integrations/supabase/client.ts).
• Migrations folder as the source of schema truth.