How solvro/web-eventownik works
Main Components
A. Frontend Layer:
• Next.js Application (Client-Side)
• Landing Page Components (/src/components/landing/*)
• UI Components (/src/components/ui/*)
• Event Management Views (/src/pages/event/*)
• Registration System (/src/pages/rejestracja/*)
B. Backend Layer:
• Next.js API Routes (Server-Side)
• Supabase Integration (/src/lib/supabase.ts)
• Authentication
• Real-time Database
• API Layer
C. Data Layer:
• Supabase Database
• User Management
• Event Data
• Reservations
• Blocks (Rooms/Tables)
Key Interactions to Highlight
• Client-Server Communication
• Real-time Updates Flow
• Authentication Flow
• Data Management Flow
Architectural Patterns to Emphasize
• Next.js Pages Router Architecture
• Client-Side State Management (using atoms - /src/atoms/)
• Component Hierarchy
• API Integration Pattern
Specific Implementation Details
a) Core Features:
• Event Management
• Registration System
• Block Management (Rooms/Tables)
• User Management
b) Technical Implementation:
• TypeScript Integration
• Tailwind CSS Styling
• Supabase Real-time Features
• Form Handling (useZodForm)
┌─ Client Layer ─────────────────────┐
• Landing Page │
• Event Management UI │
• Registration System │
• UI Components │
• Application Layer ────────────────┤
• Next.js Routes │
• State Management │
• Form Handling │
• Integration Layer ────────────────┤
• Supabase Client │
• API Services │
• Real-time Subscriptions │
• Data Layer ──────────────────────┤
• Supabase Database │
• Authentication │
• Storage │
• ┘