How daehyeoni/holidays-kr works
Main Components
a. Data Source Layer:
• Public Data Portal (한국천문연구원) API
• As an external system component
b. Data Processing Layer:
• GitHub Actions Workflows
• Data Update Pipeline
• JSON Storage
c. Service Layer:
• ICS File Generator
• Web Server/Hosting
d. Client Layer:
• Google Calendar (as consumer)
• Other Calendar Applications
Component Relationships
• Public Data Portal → GitHub Actions
• GitHub Actions → JSON Files
• JSON Files → ICS Generator
• ICS File → Calendar Clients
• GitHub Actions Schedule → Update Pipeline
Specific Implementation Details
• GitHub Actions Workflows (highlight two workflows):
• update-holidays.yml
• deploy.yml
• Data Storage:
• JSON files (2023.json through 2026.json)
• Output:
• holidays.ics
Additional Elements
Supporting details:
• Automation Schedule
• Data Format Transformations
• Hosting Environment
[External Data Source]
• ↓
[Automation Layer]
• ↓
[Data Storage]
• ↓
[Service Layer]
• ↓
[Client Layer]
Key Considerations:
Automation
• Automated nature of the system
• Clear separation between update and deployment processes
Data Flow
• Demonstrate how data moves from source to final ICS format
• Where transformations occur
Integration Points
• Webcal:// endpoint
• How calendar clients can consume the service
Infrastructure
• Hosting/deployment environment
• Where the ICS file is served from
Remember to:
• Use consistent symbols throughout
• Version or last update information
• Error handling paths where relevant