How ayushk-1801/universe works
Main Components
A. Frontend Layer:
• Client-Side Components
• Auth Routes (/signin, /signup)
• Professor Routes (/inbox, /post)
• Student Routes (/home, /proposal, /resources)
• Shared Components (Navbar, PostCards, Sidebar)
• UI Components Library
B. Backend Layer:
• API Routes
• Authentication System (NextAuth)
• Professor API endpoints
• Student API endpoints
• Search functionality
C. Database Layer:
• Prisma ORM
• Database Tables (visible from migrations):
• Users (Students/Professors)
• Posts
• Proposals
┌─────────────────────────────────────┐
• Client Layer │
• (Next.js Pages & Components) │
• ┘
• ↕
┌─────────────────────────────────────┐
• API Layer │
• (Next.js API Routes & Middleware) │
• ┘
• ↕
┌─────────────────────────────────────┐
• Database Layer │
• (Prisma ORM & Database) │
• ┘
Detailed Component Breakdown
A. Client Layer (Blue):
• Auth Section (/signin, /signup)
• Professor Dashboard
• Student Dashboard
• UI component library as a separate module
B. API Layer (Green):
• Related API endpoints:
• Auth API routes
• Professor-specific routes
• Student-specific routes
• Search functionality
• Middleware connections
C. Database Layer (Orange):
• Main database tables
• Prisma ORM as an intermediate layer
• Relationships between tables
Additional Elements
• Version information for major dependencies
• External service integrations
• Development vs production environments
Flow Indicators
• Authentication checks
• API request/response paths
• Demonstrate user role transitions
Remember to include:
• Environment configurations
• Authentication flow
• Database migrations
• API route grouping
• Component hierarchy
• Role-based access control
• Docker container boundaries
This will provide a clear understanding of the application's architecture while maintaining the necessary level of detail for a principal software engineer to understand the system's complete structure and flow.