How jayhyun-hwang/seeulater works
Main System Components
a. Chrome Extension Component:
• Represented by the chromeExtension directory
• Contains background scripts and browser action UI
• Has development, release, and backup versions
b. Web Application Component:
• Located in the webApp/sulClient directory
• React-based frontend application
• Contains user interface components for bookmark management
c. Backend Services (implied):
• AWS EC2 for hosting
• AWS RDS for database storage
• Authentication system
┌─────────────────────────────────────────────┐
• Client Side │
• ┐ ┌─────────────────┤
• Chrome │ │ Web App │
• Extension │ │ (React) │
• ┬───────┘ └────────┬────────┘
• ┬───────────────┘
• ┌───────────▼───────────┐
• API Gateway │
• ┬───────────┘
• ┌───────────────────────────────┐
• Backend Services │
┌───┴────┐ ┌──────────┐ ┌────┴───┐
• AWS EC2 │◄──►│ AWS RDS │ │ Auth │
• ┘ └──────────┘ │ Service │
• ┘
Component Details
For each component, include the following details:
a. Chrome Extension:
• Background Service (background.js)
• Browser Action UI (browser_action.html)
• Extension Configuration (manifest.json)
b. React Web Application:
• Components Structure:
• Header
• Login/Register
• Directories
• URL List
• Forms
• State Management (context)
• Routing System
c. Backend Services:
• Database Tables
• API Endpoints
• Authentication Flow
Data Flow Indicators
• User interactions with the Chrome extension
• Communication between extension and web app
• API calls to backend services
• Database operations
• Authentication flows
Data persistence and synchronization mechanisms
This system design should effectively communicate how the bookmark manager handles user interactions, stores data, and maintains synchronization across different platforms and interfaces.