How keoswalt/hooked-on-crochet works
Project type and purpose
• This is a single-page application (SPA) front-end built with React, TypeScript, Vite and Tailwind CSS, consuming Supabase as a Backend-as-a-Service (BaaS).
• Its purpose is to let users manage “projects,” each of which can have rows, tags, images and metadata, with authentication and real-time data provided by Supabase.
File structure
• Top-level “public” and “src” directories, plus configuration for Vite, TypeScript, Tailwind and Supabase.
• src/components is organized by feature: auth, images, layout, projects, rows, tags, plus a reusable “ui” library.
• src/hooks encapsulate stateful logic and Supabase operations.
• src/integrations/supabase holds the client setup and types.
• src/pages contains the entry pages (Index, NotFound).
• Build tool: Vite (vite.config.ts), styling: Tailwind (tailwind.config.ts).
README for additional insights
• Lists tech stack: Vite, TypeScript, React, shadcn-ui, Tailwind CSS, Supabase.
• Deployment is handled by Lovable, which essentially hosts the static build and wires up DNS.
• Authentication and data storage are off-loaded to Supabase.
Detail without over-splitting
• Related components into logical clusters (e.g., all “projects” components under a “Projects Module”).
• Within each cluster, only call out the most representative components or hooks.