How josephayo/bibliotheque-e-frontend works
Main System Components
a) Client-Side Application (Next.js)
• This as the main container
• That it supports both client-side and server-side rendering
b) Core Application Layers (show as nested containers):
Detailed Component Breakdown
a) Page Routes Structure
• Authentication routes (login, signup, verification)
• Library management routes (books, curations, genres)
• User management routes (account, manage)
• As hierarchical components
b) Component Architecture
• Layout components (AuthPageLayout, LibraryPageLayout)
• Reusable UI components (Cards, Buttons, Inputs)
• Feature-specific components (Banners, Tables)
Data Flow Patterns
a) API Integration
• Connection to external API (src/services/api)
• Query patterns for different entities (users, library, genre, curation)
b) State Management
• Redux store (src/lib/store.js)
• Slice patterns (createUserSlice)
• Context providers (GenreContextProvider)
Cross-Cutting Concerns
Overlays or side panels showing:
a) Authentication & Authorization
• AuthorizationGate
• UserAuthWrapper
• How these interact with protected routes
b) Configuration & Theming
• Chakra UI theme configuration
• Axios configuration
• As utility services
Specific Implementation Details
Technical details such as:
• Next.js API routes (/api)
• Custom hooks (useCurrentUserLoader, useUserRoles)
• Service layer organization
• Component composition patterns