How mo7yw4ng/dashcam-share works
Main Application Structure
a. Frontend Architecture (Primary Focus)
• Implement a clear component hierarchy using Atomic Design pattern, as evidenced by the structure:
• Atoms (Base components)
• Molecules (Composite components)
• Organisms (Complex components)
• Views (Page components)
b. State Management Layer
• Pinia stores (found in src/stores):
• form store
• googleMaps store
• user store
Key Components to Highlight
a. Core Features
• Integration System (DashCamMapView, SecurityCamMapView)
• Video Management System (VideoDetailsPage, VideoReport)
• Monitoring System (MonitorDetailsPage, MonitorExpandView)
• Form Management System (Various form components and views)
b. Data Flow Layer
• API Integration (indicated by mock data in public/mock)
• Composables for data handling (useConnectionMessage, useHandleConnectionData)
┌─ User Interface Layer ─────────────────────┐
• Views -> Organisms -> Molecules -> Atoms │
• State Management Layer ───────────────────┤
• Pinia Stores (form, googleMaps, user) │
• Business Logic Layer ───────────────────┤
• Composables, Utils, Services │
• External Services Layer ─────────────────┤
• Google Maps, API Services │
• ┘
Important Connections
• Component composition flow
• State management interactions
• API data flow
• Router navigation paths
Technical Stack Indicators
Technology badges for:
• Vue 3
• TypeScript
• Vite
• Pinia
• Tailwind CSS
• Google Maps Integration