How solvro/web-planer works
Main Components
A. Frontend Layer (Next.js Application):
• Client-side Components
• Homepage Module
• Plans Module
• Authentication Module
• UI Components Library
• API Routes
• State Management (Atoms)
• Service Layer (USOS Integration)
B. Backend Layer (AdonisJS Application):
• Controllers Layer
• Models Layer
• Middleware Layer
• Database Layer
• USOS Integration Service
• Authentication Service
• Scheduled Tasks (Commands)
C. External Services:
• USOS System
• Database (indicated by migrations)
• Analytics Service (Umami)
Component Relationships and Data Flow
[Client Browser] ←→ [Frontend Next.js App]
• ↑↓
• [Backend API]
• ↑↓
• ┌─────────┴─────────┐
[Database] [USOS API] [Analytics]
Detailed Component Breakdown
Frontend (Next.js):
┌─ Frontend Layer ─────────────────┐
• Public Pages │
• Protected Routes (/plans) │
• API Routes │
• Authentication Flow │
• USOS Integration Services │
• ┘
Backend (AdonisJS):
┌─ Backend Layer ──────────────────┐
• Auth Controller │
• Courses Controller │
• Schedule Controller │
• Users Controller │
• Database Models │
• Middleware Stack │
• USOS Client │
• ┘
Technical Stack Indicators
Technology badges or labels:
• Next.js/React for frontend
• AdonisJS for backend
• TypeScript
• Tailwind CSS
• PostgreSQL (implied by migrations)
Additional Elements
• Deployment infrastructure (Coolify)
• Environment configurations
• CI/CD workflow connections
• Caching layers if present
• Scheduled tasks and background jobs
Remember to indicate the scalability points and potential bottlenecks in the system, especially around the USOS integration and schedule synchronization features.