How bpevs/favioli works
Main Components Identification
The system should be represented as a browser extension architecture with these key components:
a) Extension UI Layer:
• Popup Interface (source/popup.tsx)
• Options Page (source/options.tsx)
• Components (source/components/*)
b) Core Extension Components:
• Background Script (source/background.ts)
• Content Script (source/content_script.ts)
c) Business Logic Layer:
• Models (source/models/*)
• Utilities (source/utilities/*)
┌─ Browser Extension Environment ─────────────────────┐
• ┌─ UI Layer ─────────────┐ │
• Popup ─┼─┐ │
• Options Page ─┼─┤ │ Components │
• Emoji Selector ─┼─┘ │ - Checkbox │
• ┘ │ - List │
• Switch │
• ┌─ Core Extension ──────────┘ │
• Background Script ◄────► Content Script │
• ┬───────────────────────────────┘ │
• ┌─ Business Logic ────────────────────────────┐ │
• Models: Utilities: │ │
• Emoji - Favicon Selector │ │
• Favicon - Image Helpers │ │
• Settings - Permissions │ │
• ┘ │
• ┘
Key Relationships to Highlight
• Data flow from UI components to Business Logic layer
• Storage interactions with Browser API
• Favicon manipulation pipeline
Important Technical Details
• Built with Deno and Bext
• Cross-browser compatibility (Chrome/Firefox)
• Storage mechanisms for settings
• Favicon manipulation utilities
Implementation Notes
• The separation between UI, core extension logic, and business logic
• How the favicon override system integrates with web pages
• The role of various utilities in favicon manipulation
• Storage and state management flow