How progi-hoodclassics/hoodclassics works
Main System Components
The system should be represented as a modern full-stack application with these primary components:
a) Frontend Layer (React + TypeScript):
• User Interface Components (/frontend/src/components)
• Page Components (/frontend/src/pages)
• Authentication Utilities (/frontend/src/utils/auth.ts)
b) Backend Layer (Spring Framework):
• REST Controllers (/backend/src/main/java/hoodclassics/opp/rest)
• Security Configuration (/backend/src/main/java/hoodclassics/opp/sec)
• Service Layer (/backend/src/main/java/hoodclassics/opp/service)
• Data Access Layer (/backend/src/main/java/hoodclassics/opp/dao)
• Domain Models (/backend/src/main/java/hoodclassics/opp/domain)
Key Architectural Elements
a) External Services:
• OAuth 2.0 Authentication (Google Sign-in)
• Service Integration (for interactive map functionality)
b) Security Layer:
• Authentication Handlers
• Password Encoding
• OAuth2 Configuration
• Web Security Config
[Client Layer]
[Frontend (React + TypeScript)]
[API Gateway/Load Balancer]
[Backend (Spring)]
[Data Layer]
Component Interactions
• User Authentication Flow (both OAuth and email/password)
• Data Flow (pin creation, retrieval)
• User Registration Process
• Content Management Flow
Deployment Architecture
Deployment on Render.com with:
• Frontend deployment
• Backend deployment
• Database connection
• External service connections