How banaanas/cyrilo-mots works
┌─ Client Layer ─────────────────────┐
• Next.js Frontend │
• React Components │
• Zustand State Management │
• ┬────────────────┘
• ↕
┌─ API Layer ──────┴────────────────┐
• Next.js API Routes │
• Authentication Handlers │
• ┬────────────────┘
• ↕
┌─ External Services ────────────────┐
• Supabase (Auth & Database) │
• Wiktionary API │
• ┘
Component Details
Frontend (Client Layer):
• Layout Components (Header, Layout)
• Word Management (WordSearch, WordsList, WordDefinitions)
• Authentication Components (LoginPage, LoginForm, LoginGithub)
• Common Components (Loader, MaxWidthWrapper)
State Management:
• A Zustand store section showing the four stores:
• useMaxRangeStore
• useWordsAccordionStore
• useWordsSearchStore
• useWordsStore
API Integration:
• Create sections for:
• Supabase API calls (all-words, search-word, word operations)
• Wiktionary API integration (definitions retrieval)
Data Flow Indicators
• User authentication flow (Login → Supabase Auth)
• Word search and retrieval (Search → Supabase → Wiktionary API)
• State updates (Components → Zustand Store)
Technical Stack Indicators
Technology badges for:
• Next.js
• React
• TypeScript
• Supabase
• Emotion
• Zustand
• Radix UI
Notes
Annotations for:
• Authentication methods supported
• Word definition retrieval process
• Pagination implementation
• State management strategy
• SEO optimization approach
Component hierarchy and interaction
Remember to emphasize the application's key features:
• Two different word lists (All Words/Unread Words)
• Search functionality
• Authentication system
• Word definition retrieval
• Pagination
• Responsive design considerations