How octavian-regatun/planitly-web works
Main Components
Frontend Layer:
• Client-Side Application (Next.js)
• Authentication Layer
• Route Groups ((authenticated-app) structure)
• Component Layer
• State Management (store directory)
• UI Components (shadcn components)
Backend Integration:
• API Services Layer
• Authentication Service
• External Services Integration
Component Relationships
a) Top Level (Client Architecture):
┌─ Next.js Application
• Public Routes
• Protected Routes (authenticated-app)
• Dashboard
• Calendar
• Events
• Friends
• Groups
• Settings
• Users
b) Feature Modules:
• Events Management
• User Management
• Management
• Calendar System
• Friendship System
c) Service Layer:
• Authentication Service (auth.ts)
• API Services (events.ts, users.ts, groups.ts, etc.)
• Axios Instance (utilities/axios.ts)
Data Flow Visualization
• User authentication flow
• API requests flow
• State management flow (store → components)
• Component hierarchy
Architectural Patterns to Highlight
• Next.js App Router Structure
• Protected Routes Pattern
• Service Layer Pattern
• Custom Hooks Pattern
• Component Composition
Implementation Details
• Clear separation between authenticated and public areas
• Integration of UI components with business logic
• Hook-based data fetching pattern
• State management flow
Additional Notes
• Relationship between hooks and services
• Where global state is used
• Authentication boundaries
• Integration points with external services
Remember to:
• Use consistent styling
• Related components
• Clear boundaries between different parts of the application
• Important configuration aspects