How ewanbrinkman/do-you-know-there works
Main Components
a. Frontend Layer:
• Next.js Application (Core)
• Game Components
• GameContainer
• GameLocationImage
• GameMap
• ResultsContainer
• Common Components
• Button
• Container
• LocationImage
• Map
• Layout Components
• Navbar
b. Data Layer:
• Assets and Configuration
• Area Data (locations.json, map.json, info.json)
• Game Configuration
• Theme Configuration
• Image Storage
• Location Images
• Processed/Optimized Images
c. Build/Processing Layer:
• Image Processing Pipeline
• Static Site Generation
Component Relationships
[Client Browser] ←→ [Next.js Frontend]
• ↓
[Frontend Components] → [Game Logic] → [Data Layer]
• ↓
[Static Assets] ← [Build Pipeline] ← [Raw Assets]
Specific Implementation Details
• Blue rectangles for React components
• Yellow diamonds for processing pipelines
• Gray rectangles for configuration files
• Purple hexagons for build/optimization processes
Key Architectural Patterns to Highlight
a. Component Architecture:
• Hierarchy of components (Features > Game > specific components)
• Shared Common components
b. Data Flow:
• How location data flows from static files to game components
• Image processing pipeline
c. Build Process:
• Demonstrate image optimization flow
• Static site generation process
Important Elements
• Version/environment information
• External dependencies (if any)
• Entry points and user interaction flows
Specific Implementation Notes
• Annotations for key configuration points
• Notes about image processing requirements
The component hierarchy and reuse patterns
Remember to include a note about the single-area current limitation and future multi-area support plans.
This architecture should be represented in a clean, professional manner that clearly shows the modern Next.js application structure while highlighting the game-specific components and data flow.