How mikoyzskie/sgc-app works
Main Components
A. Client-Side Components:
• Browser/User Interface
• Client-side Runtime (Next.js Client)
• Static Assets (in /public directory)
B. Server-Side Components:
• Next.js Server Runtime
• App Router (new Next.js 13+ architecture)
• Server Components
• Static Generation Pipeline
C. Build-time Components:
• Next.js Build System
• Asset Optimization Pipeline
• TypeScript Compilation Layer
D. Development Tools:
• ESLint Configuration
• Tailwind CSS Processing
• Husky Git Hooks
Rectangle: Core components
Hexagon: Build processes
Rounded Rectangle: Runtime environments
Blue: Client-side components
Green: Server-side components
Orange: Build-time processes
Grey: External services/tools
Key Relationships to Highlight
A. Request Flow:
• Browser → Next.js Server → Server Components → Client Components
• Static Asset Delivery Path
• API Routes (if added later)
B. Build-time Flow:
• Source Files → Next.js Build → Optimized Output
• TypeScript Compilation
• CSS/Tailwind Processing
Important Architectural Elements
A. App Router Structure:
• Root Layout (src/app/layout.tsx)
• Page Components (src/app/page.tsx)
• Global Styles (src/app/globals.css)
B. Static Optimization:
• Font Optimization (next/font)
• Asset Optimization
• Static Generation Paths
Deployment Architecture
• Vercel Platform Integration
• Edge Network Distribution
• Build Output Optimization
Specific Implementation Details
Top Layer: Client Interface
Middle Layer: Next.js Runtime (Server + Client)
Bottom Layer: Build & Optimization Systems
Specific elements:
• CircleCI Integration (.circleci/config.yml)
• TypeScript Configuration (tsconfig.json)
• Tailwind CSS Processing Pipeline
• Next.js Configuration (next.config.ts)