How plon/illinispots works
Frontend Layer
• Interactive Map Component (MapLibre GL JS)
• Building Status Components
• Library Room Components
• UI Components (shadcn/ui)
API Layer
• Buildings Availability Endpoint
• Libraries Availability Endpoint
• Connection to both frontend and database layers
Database Layer
• Core Tables (from schema/tables.sql)
• Custom Functions (get_current_building_status)
• Data models for buildings, rooms, schedules
Data Pipeline System
• Scrapers (Course Explorer, LibCal, Tableau)
• Data Processors
• Building Data Enrichment
• Scheduled tasks (cron jobs)
External Data Sources
• Course Explorer
• Facility Scheduling
• Library Reservation System
• Tableau Daily Events
Key Relationships to Highlight:
• External Sources → Data Pipeline
• Data Pipeline → PostgreSQL Database
• Database → API Routes
• API Routes → Frontend Components
Real-time Updates
• Periodic data refresh cycles
• Websocket connections if applicable
• Blue: Frontend components
• Green: API layer
• Yellow: Database components
• Orange: Data pipeline
• Grey: External systems
Special Considerations:
Core Algorithm Visualization
• State Detection
• Gap Analysis
• Duration Calculation
Library System Pipeline
• Three-stage pipeline:
• Room Data Extraction
• Reservation Status Collection
• Availability Processing
Important Elements to Include:
Technology Labels
• Next.js/React
• TypeScript
• PostgreSQL
• MapLibre GL JS
• Python (for data pipeline)
Data Flow Timing
• Real-time API calls
• Scheduled data updates
• Cron job frequencies
Security Layer
• Supabase authentication
• API route protection
• Environment variables
Scalability Points
• Database optimization
• Caching strategies
• Load balancing considerations
• Component types (Frontend, Backend, Database, External)
• Status indicators (Available/Occupied)
Level of Detail:
• High-level: Show main system components and their interactions
• Mid-level: Include key subcomponents and data flows
• Low-level: Add specific implementation details for critical features
Remember to include version information and any relevant deployment architecture details if applicable.