How mbta/screens works
Main System Components
a) Client Layer
• Multiple screen types (Bus E-Ink, Green Line E-Ink, Bus LCD, Multimodal LCD, Pre-fare LCD, DUP LCD)
• Frontend applications (React/TypeScript based on the assets structure)
• Screen-specific widgets and components
b) Application Layer
• Phoenix web server (screens_web)
• Widget framework
• Screen data processing
• Real-time information handlers
• Authentication/Authorization system
c) Data Processing Layer
• Candidate generators
• Template builders
• Alert processors
• Departure processors
• Screen configuration handlers
d) External Services Integration
• MBTA API integration
• S3 configuration storage
• Cache systems
• Real-time data feeds
Key Relationships to Highlight
• Data flow from external services to the application
• Request/response patterns between layers
• Widget rendering pipeline
• Screen-specific content generation flows
Specific Implementation Details
a) Widget Framework
• How widgets are generated and managed
• Template system
• Candidate generation process
b) Screen Types
• Demonstrate how different screen types are handled
• Screen-specific processing paths
• Content adaptation for different display types
c) Real-time Processing
• How real-time data flows through the system
• Caching mechanisms
• Update/refresh patterns
Important Architectural Patterns
Emphasize:
• Phoenix/Elixir supervision tree structure
• Widget-based component architecture
• Cache management system
• Screen configuration management
• Authentication/authorization flow
Additional Elements
Include:
• Version information
• Key technology stack components
• Main data flow paths
• Critical system boundaries
Remember to include notes about:
• Scaling considerations
• Error handling paths
• Configuration management
• Screen type-specific processing
• Real-time data flow optimizations