How kimbylr/inemit works
Main System Components
A. Client Layer (Frontend)
• Next.js Application
• Learn Module (src/app/(learn))
• Lists Management Module (src/app/lists)
• UI Components (src/components, src/elements)
• State Management (src/hooks)
B. Server Layer (Backend)
• Next.js API Routes (src/app/api)
• Authentication System (Auth0 integration)
• Database Layer (MongoDB)
C. External Services
• Unsplash API (for images)
• Deepl API (mentioned in env vars)
Component Relationships
a) User Flow:
• User → Auth0 → Application
• Authenticated User → Lists Management/Learn Module
• Lists Management → Database Operations
• Image Selection → Unsplash API
b) Data Flow:
• Client Components → API Routes → Database
• Learning Session → Spaced Repetition Algorithm → Progress Updates
Specific Architectural Elements
Key architectural patterns:
a) Next.js App Router Structure:
• Route groups: (learn), lists, about
• Dynamic routes: [slug]
• API routes structure
b) Component Architecture:
• Base Elements (src/elements)
• Composed Components (src/components)
• Complex Compositions (src/compositions)
• Page Layouts
Technical Details
Create sections for:
a) Frontend:
• PWA Capabilities (manifest.webmanifest)
• CSS Framework (Tailwind)
• Client-side Hooks and Helpers
b) Backend:
• Database Models (src/db/models.ts)
• Database Actions (src/db/actions.ts)
• Authentication Middleware
Special Features to Highlight
Create dedicated sections for:
• Spaced Repetition System
• Learning Progress Tracking
• Management Features
• Image Integration
• Import/Export Functionality