How liam-prevelige/pageturner-frontend works
Main Components
Frontend Layer:
• React Single Page Application (SPA)
• Key feature modules:
• Authentication
• Book Management
• Social Features
• Search Functionality
• Profile Management
• Book Club Features
Backend Layer (to be represented although not in this repo):
• Express.js Server
• MongoDB Database
• Authentication Service (Google OAuth)
• External APIs (Amazon Books API)
Component Organization
A. Client-Side (React):
• Auth Module
• Book Management Module (BookInfo, Bookshelf)
• Social Module (Comments, ShareBox, Timeline)
• Search Module (DynamicSearch)
• Profile Module
• Book Clubs Module
B. Layout Components:
• Persistent components:
• Sidebar (Navigation)
• RightBar (Trending, WhoFollow)
• Main Content Area
C. Data Flow Layer:
• API communication layer (src/api.js)
• State management
• Authentication flow
Relationships to Highlight
• Auth flow between Google OAuth and frontend
• Data flow between components and API
• Component hierarchy and nesting
• User interaction flows
• Real-time updates for social features
Key Architectural Patterns to Emphasize
• Component-based architecture
• Container/Presenter pattern
• Route-based code splitting
• Reusable component library
[Client Browser] <-> [Frontend (React SPA)] <-> [Backend API] <-> [Database]
• [External Services]
[App.js]
• [Auth Module]
• [Layout Components]
• [Sidebar]
• [Main Content]
• [RightBar]
• [Feature Modules]
• [Book Management]
• [Social Features]
• [Search]
• [Book Clubs]