How sourceguidehq/main works
Main Components
A. Frontend Layer
• Next.js Application Structure
• Pages (app directory structure)
• Components (UI and Custom)
• Client-Side Features
• Static Assets
• Styling (Tailwind CSS)
B. Data Layer
• Static JSON Files
• organizations.json
• programs.json
C. Integration Layer
• Analytics Integration (Google Analytics)
• External Links (Discord, GitHub)
┌─────────────────────────────────────┐
• Client Layer │
• ┘
• ↕
┌─────────────────────────────────────┐
• Application Layer │
• ┘
• ↕
┌─────────────────────────────────────┐
• Data Layer │
• ┘
Detailed Component Breakdown
A. Client Layer (Top)
• Navigation Menu
• Pages (Home, About, Issues, Programs, etc.)
• UI Components (Cards, Buttons, Dialogs)
• Pages (rectangles)
• Components (rounded rectangles)
B. Application Layer (Middle)
• Next.js Router
• Page Components
• Utility Functions (lib/utils.ts)
• Component Library
C. Data Layer (Bottom)
• JSON Data Store
• External Integrations
Important Elements to Highlight
A. Routing Structure
• Dynamic routes ([org])
• Static routes (about, programs, etc.)
B. Component Organization
• UI components (/components/ui)
• Custom components (/comps)
C. Data Flow
• How data flows from JSON files to components
• Integration points with external services
Technical Stack Indicators
Technology badges or labels for:
• Next.js
• TypeScript
• Tailwind CSS
• React
• Google Analytics
Remember to indicate the app's primary features:
• Issue discovery
• Program browsing
• User engagement points
• Static content delivery
This will create a comprehensive yet clear visualization of SourceGuide's architecture that effectively communicates the system's design to other engineers and stakeholders.