How definiteiymaybe/dostoevsky-website works
Main Components Identification
The system should be represented with these key components:
a) Frontend Layer:
• Gatsby Static Site Generator
• React Components (src/components)
• UI Kit Components
• Templates Layer
• Routing System
b) Data Layer:
• Content Management (content/)
• Static Files (static/)
• JSON Data Sources (content/*.json)
• Markdown/MDX Files (content/posts/)
c) Build & Deployment:
• GitHub Actions Pipeline
• Netlify/Vercel Deployment
• Crowdin Translation System Integration
[Client Browser] ←→ [CDN/Static Hosting]
• ↑ ↑
[Static Assets] ←── [Build Output]
• ↑
• [Gatsby Build]
• ↑
• ┌────────────────┴─────────────────┐
• ↓ ↓ ↓
[React Components] [Templates] [Data Sources]
• ↓ ↓ ↓
[UI Kit] [Page Templates] [Content (MD/JSON/Static)]
• ↓
• [Translation System]
Key Relationships to Highlight
a) Component Architecture:
• Hierarchy between UI Kit → Components → Templates → Pages
• Data flow from content sources through Gatsby's build process
• Demonstrate the translation system's integration
b) Build Process:
• How content flows through the Gatsby build pipeline
• Where translations are injected
• Deployment paths to different environments (production/beta)
Technical Details
• TypeScript integration
• Testing infrastructure
• Style management (CSS modules)
• State management
• Route handling
Remember to highlight the project's unique features like:
• Multi-language support
• Feature flag system
• Analytics integration
• Content management workflow
• Component library organization
This will provide a clear understanding of how the various parts of the system interact while maintaining a focus on the project's specific requirements and architecture.