How entur/ninkasi works
Main Components
a) Frontend Layer:
• React Application (evident from the src structure)
• Key UI Components:
• Providers Management
• Organization Management
• User Management
• Geocoder Interface
• Event Management
b) Authentication Layer:
• Keycloak Integration
• JWT Token handling
c) External Services Layer (Multiple REST APIs):
• Providers Service
• Organizations Service
• Timetable Admin Service
• Admin Service
• Geocoder Admin Service
• Events Service
Architectural Patterns to Highlight
a) Redux Pattern (visible from reducers and actions folders):
• Actions
• Reducers
• Store
• State Management Flow
b) Component-Based Architecture:
• Screens
• Modals
• Common Components
[Client Layer] → [Authentication Layer] → [Services Layer]
Specific Elements
a) Client Layer:
• Main React components
• Redux store
• Configuration management (ConfigContext)
• Routing structure
b) Authentication Layer:
• Keycloak integration
• JWT token flow
• Authentication endpoints
c) Services Layer:
• All external REST APIs
• Base URLs for each service
• Data flow directions
Important Flows to Highlight
• User authentication flow
• Data pipeline management flow
• Event monitoring flow
• Organization/User management flow
Additional Details
• Firebase hosting configuration (noted from .firebaserc)
• Environment-specific configurations (dev/prod/test)
• Micro-frontend architecture aspects (seen in MicroFrontendFetchStatus component)
Technical Stack Indicators
• React
• Redux
• Firebase
• Keycloak
• SASS (for styling)
• Node.js requirements (v18+)