How nickisnoble/hygge_quest_public works
Main System Components
a) Client Layer
• Web Browser Interface
• Progressive Web App (PWA) Support
• Hotwire/Turbo/Stimulus Components
b) Application Layer
• Authentication System (Passwordless)
• Guest Management
• Party Management
• Guild System
• Location/Map Services
• Mailing System
• Admin (Dungeon Master) Interface
c) Storage Layer
• SQLite Database
• AWS S3 (Active Storage)
• File System Cache
Component Relationships
[Client Layer]
• ↑↓
[Application Layer]
• ↑↓
[Storage Layer]
Detailed Component Breakdown
• Rectangles (Blue): Core Features
• Guest Management
• Party Management
• Guild System
• Location Services
• Hexagons (Green): External Services
• AWS S3
• Resend Email
• Geocoding Service
• SQLite Database
• File System
• Rounded Rectangles (Purple): Frontend Components
• Turbo Frames
• Stimulus Controllers
• PWA Components
Key Workflows to Highlight
a) Guest RSVP Flow:
Browser → Passwordless Auth → Party Controller → Guest Management → Database
b) Admin (DM) Flow:
DM Interface → Cerberus Authentication → Admin Controllers → Data Management
c) Mailing System:
Mailer Controller → Resend Service → Guest Email
Technology Stack Labels
• Rails 7.1
• TailwindCSS
• Hotwire/Turbo/Stimulus
• SQLite
• AWS S3
• Resend
• Leaflet Maps
Security Layer
Security components:
• Passwordless authentication
• Cerberus admin protection
• Session management
Remember to include a clear indication of the temporary nature of the application and its specific purpose as a wedding RSVP system, as this influences architectural decisions like the use of SQLite and file-based storage.
This system design should effectively communicate both the technical architecture and the unique themed aspects of the application, making it clear how the various components work together to create this specialized wedding RSVP experience.