How noodle-run/noodle works
Main System Components
a) Client Layer:
• Next.js Frontend (src/app directory structure indicates Next.js App Router)
• Split into two main sections:
• Public Site ((site) routes)
• Dashboard Application ((dashboard) routes)
b) API Layer:
• tRPC API (src/server/routers)
• API Routes (src/app/api)
c) Data Layer:
• Database (using Drizzle ORM)
• Redis Cache
• File Storage (for static assets)
d) External Services:
• Authentication (indicated by auth routes)
• Email Service (Resend - shown in src/emails)
Component Relationships
a) Frontend to Backend:
• tRPC client connections from dashboard to API
• API routes for public endpoints
• WebSocket connections for real-time features
b) Backend to Data:
• Database connections through Drizzle ORM
• Redis cache interactions
• Static file serving paths
Specific Implementation Details
Key architectural elements:
[Client Layer]
• Public Site
• Landing Page
• Blog System
• Legal Pages
• Dashboard
• Authentication
• Module Management
• Note Taking Interface
[API Layer]
• tRPC Routers
• Early Access
• Modules
• Middleware
• API Routes
[Data Layer]
• Database Schema
• Early Access
• Modules
• Redis Cache
• Static Assets
Future Extensibility
Placeholder sections for planned features:
• Calendar integration
• Task management system
• Grade tracking module
• Flashcard system
This structure reflects Noodle's nature as a modern, full-stack web application with a focus on student productivity features, while maintaining scalability and real-time capabilities.