How dennislwm/playboard works
Main Components
a) Client Layer:
• Mobile Device (iPhone)
• Mac Workstation
• Input Methods (Bookmarklet, Email)
b) Service Layer:
• Pinboard.in (SaaS Platform)
• GitHub Actions (Automation)
c) Storage Layer:
• Pinboard.in Database
• GitHub Repository (Primary Backup)
• Local PDF Archive
• Secondary Backup (Planned)
d) Processing Components:
• RSS Feed Generator
• Recoll Search Engine (Local)
• PDF Generation Service (Planned with wkhtmltopdf)
Component Relationships
• User input → Pinboard.in
• Pinboard.in → RSS Feeds
• GitHub Actions → Backup Process
• RSS Feeds → PDF Generation (planned)
• PDF Files → Recoll Search Engine
Specific Elements
→ Data Flow
⇢ Backup Flow
• Integration
Components:
□ User Interfaces
○ Services
▽ Storage
◇ Processing
Implementation Notes
• The distributed nature of the system (mobile, web, local)
• The automation workflow through GitHub Actions
• The separation between production (Pinboard.in) and backup systems
• The local processing capabilities (Recoll, PDF generation)
Key Workflows to Highlight
a) Bookmark Creation Flow:
User → (Bookmarklet/Email) → Pinboard.in → Tag-based Queues
b) Content Consumption Flow:
Pinboard.in → RSS Feeds → RSS Reader → User
c) Backup Flow:
Pinboard.in → GitHub Actions → Repository Storage