How pamanaleph/dpmi-president-university works
Main Components
A. Frontend Layer:
• Client-Side Components (src/components/)
• Admin Dashboard
• User Dashboard
• Form Management
• UI Components
• Authentication Views
B. Application Routes (src/app/):
• Admin Routes ((admin))
• Auth Routes ((auth))
• Main Routes ((main))
• Dashboard
• Evaluation System
• Form Management
C. Data Layer:
• Models (src/models/)
• Services (src/service/api/)
• Utils (src/utils/)
D. External Services:
• Authentication System
• API Endpoints
• Storage System (for files)
┌─────────────────────────────────────────────┐
• Client Layer │
• (Next.js Frontend + Client-side Components)│
• ┤
• Application Layer │
• (Routes, Controllers, API Services) │
• ┤
• Data Layer │
• (Models, Services, Storage) │
• ┘
Key Relationships to Highlight
a. User Flow:
• Authentication flow between auth components and API
• Dashboard access for different user roles
• Form submission and evaluation process
b. Admin Flow:
• User management
• Evaluation management
• Setup and configuration
• Response handling
c. Data Flow:
• API service interactions
• Model relationships
• File handling
Specific Implementation Details
a. Evaluation System:
Setup → Questions → Responses → Evaluations → Reports
b. User Management:
Authentication → Role Management → Access Control → User Actions
Important Architectural Patterns
• Next.js App Router structure
• Component hierarchy
• API service pattern
• Model relationships
• Context providers (DashboardContext, AdminDashboardContext)
The API service architecture
Remember to:
• Major integration points
• Security boundaries
• Document data flow directions