How pujo-atlas-kolkata/pujoatlaskol-web works
Main Components
A. Frontend Layer
• Astro-based frontend architecture with two main layouts:
• Landing Page Layout
• Web App Layout
• Features:
• Pandal Map View
• Search Functionality
• Carousel Components
• Multilingual Support (English/Bengali)
B. State Management Layer
• Stores structure:
• Active Store
• Pujo Store
• Query Store
• Search Store
C. API Integration Layer
• Request handling system
• Hooks structure:
• Location hooks
• Pandal hooks
• Search hooks
• Query hooks (mutations and queries)
D. External Services
• Netlify (Hosting)
• Cloudflare (CDN/DNS)
• Sentry (Error Tracking)
• Google Maps Integration
┌─────────────────────────────────────────────────────────┐
• Client Layer │
• ┬────────────────┬───────────┬──────────────┤
• Landing │ Web App │ Shared │ Multilingual │
• Components │ Components │ Components│ Routes │
• ┴────────────────┴───────────┴──────────────┘
• ↕ ↕
┌─────────────────────────────────────────────────────────┐
• State Management │
• ┬────────────────┬───────────┬──────────────┤
• Active │ Pujo │ Query │ Search │
• Store │ Store │ Store │ Store │
• ┴────────────────┴───────────┴──────────────┘
• ↕ ↕
┌─────────────────────────────────────────────────────────┐
• Custom Hooks │
• ┬────────────────┬───────────┬──────────────┤
• Location │ Pandal │ Search │ Query │
• Hooks │ Hooks │ Hooks │ Hooks │
• ┴────────────────┴───────────┴──────────────┘
• ↕ ↕
┌─────────────────────────────────────────────────────────┐
• External Services │
• ┬────────────────┬───────────┬──────────────┤
• Netlify │ Cloudflare │ Sentry │ Google Maps │
• ┴────────────────┴───────────┴──────────────┘
Special Features to Highlight
• Search and debounce mechanism
• Map clustering system
• Multilingual routing structure
Important Details
• Data flow direction indicators
• Separation between server and client-side code
• Build and deployment pipeline
Notes for Implementation
• Keep the abstraction level high enough to be understandable but detailed enough to show the application's complexity
• Use standardized symbols for different types of components
• Notes about the key architectural decisions