How mhitza/subscriptions-digest works
Main Components
a. External Services Layer:
• GitHub Actions (Scheduler/Trigger)
• Email Service Providers (SES, Gmail, Mandrill, etc.)
• GitHub API (for tracking last run)
• RSS Feed Sources
• Gist (for configuration storage)
b. Application Core:
• Configuration Manager
• Feed Processor
• Digest Generator
• Email Formatter
• Mailer Service
Component Relationships
• Configuration flow from Gist to the application
• Feed processing pipeline
• Demonstrate email generation and delivery flow
Specific Implementation Details
• Blue rectangles for external services
• Green rectangles for core application components
• Yellow diamonds for decision points
• Red rectangles for critical configuration elements
Data Flow Representation
• Configuration loading (Gist → Application)
• Feed fetching (RSS Sources → Feed Processor)
• Email generation (Digest Generator → Email Service)
• State management (GitHub API interactions)
Key Technical Elements
Specific components:
• Symfony Mailer integration
• Twig templating system (template.html.twig)
• YAML configuration handling
• Command line interface (RunCommand.php)
[Triggers Layer]
• GitHub Actions (Scheduled Tasks)
• ↓
[Configuration Layer]
• Gist Config → YAML Parser
• ↓
[Processing Layer]
• Feed Fetcher → Content Processor → Digest Generator
• ↓
[Template Layer]
• Twig Template Engine
• ↓
[Delivery Layer]
• Symfony Mailer → Email Service Provider
Automation aspect by clearly showing the GitHub Actions workflows
• scheduled-digest.yml (daily runs)
• scheduled-sync.yml (weekly updates)
2. A state management section showing how the system tracks the last run using GitHub API