How gakuto06250177/morningwinner works
Project type and purpose
• Full-stack (front-heavy) web application built on Next.js (App Router)
• Purpose: Track attendance/late penalties for four members, persisting data in either LocalStorage or Supabase
File structure
• Top-level:
– next.config.ts, vercel.json → Vercel deploy
– package.json, tsconfig.json, ESLint, PostCSS, Tailwind configs
• src/app → Entry points (layout.tsx, page.tsx) using Next.js App Router
• src/components → UI building blocks (SunriseLoading animations, attendance controls, summary table)
• src/hooks → Data access abstraction: useLocalStorageData.ts, useSupabaseData.ts
• src/lib → Low-level API clients: database.ts for LocalStorage, supabase.ts for Supabase
• supabase-schema.sql → DB schema for Supabase
README for architecture insights
• Dual persistence strategy (LocalStorage vs. Supabase) selectable via environment variables
• Client-side rendering with occasional SSR/SSG by Next.js
• Tailwind CSS for styling
• Vercel for hosting
Main components and their interactions
a. Browser / Client
– Next.js pages and React components render UI
– Custom hooks decide storage target
– LocalStorage API or Supabase JS client invoked on user actions
b. Next.js hosting (Vercel)
– Serves static assets and server-side rendered pages
– Environment variables configure Supabase connectivity
c. Supabase (optional backend)
– Hosted PostgreSQL + auto-generated REST / GraphQL endpoints
– Auth & real-time features (not in use but available)
d. LocalStorage (fallback storage)
– Browser’s key/value store; no network calls
e. Shared types and utilities
– src/types define data models
– src/lib contains client abstractions
Architectural patterns and design principles
• Layered architecture:
– Presentation (React pages/components in src/app, src/components)
– Data Access (hooks in src/hooks)
– Infrastructure Adapters (src/lib)
• Strategy Pattern:
– StorageStrategy = LocalStorage or Supabase, injected via hooks
• Separation of concerns:
– UI vs. business logic vs. persistence