How purelyricky/avashift_com works
Main Components
a) Frontend Layer:
• Application into 5 main user interfaces based on roles:
• Admin Portal (/app/(admin))
• Client Portal (/app/(client))
• Gatemen Portal (/app/(gatemen))
• Leaders Portal (/app/(leaders))
• Students Portal (/app/(students))
• Authentication Layer (/app/(auth))
• Shared Components (/components)
• UI Component Library (/components/ui)
b) Backend Layer:
• API Routes (/app/api)
• Action Handlers (/lib/actions)
• Email Service (/app/api/emails)
• Database Interface (indicated by databases.md)
c) External Services:
• Appwrite Integration (shown by /lib/actions/appwrite.ts)
• Email Service Provider
• Authentication Service
┌─────────────────────────────────────────────────────┐
• Client Layer │
• ┌─────────┐ ┌────────┐ ┌───────┐ ┌───────┐ ┌────┐ │
• Admin │ │ Client │ │Gatemen│ │Leaders│ │User│ │
• ┘ └────────┘ └───────┘ └───────┘ └────┘ │
• ┤
• Application Layer │
• ┌─────────────┐ ┌──────────────┐ ┌──────────────┐ │
• Next.js Pages│ │API Routes │ │Action Handlers│ │
• ┘ └──────────────┘ └──────────────┘ │
• ┤
• Service Layer │
• ┌─────────────┐ ┌──────────────┐ ┌──────────────┐ │
• Email Service│ │Auth Service │ │Appwrite │ │
• ┘ └──────────────┘ └──────────────┘ │
• ┘
Key Relationships to Highlight
• Authentication flow between auth pages and auth service
• Data flow between actions and API routes
• Demonstrate email notification system's integration
• Relationship between different user portals and shared components
• Database interactions through Appwrite
Important Details
• Role-based access control flow
• Email notification system architecture
• Project management workflow
• Attendance tracking system
• Reporting system architecture
Specific Features to Emphasize
• Dashboard systems for each user type
• Project creation and management flow
• Attendance tracking mechanism
• Shift management system
• Reporting and analytics features