How tier-1-club/fe-standard works
Main Components
a. Application Layer:
• Next.js Application (Core)
• Home Module ((home) directory)
• Documentation Module (docs directory)
• Open Graph Image Generation (og directory)
b. Content Management:
• MDX Content Store (content directory)
• Documentation Content
• Blog Content
• Meta Configuration Files
c. Modular Architecture:
• AI Module (modules/ai)
• SEO Module (modules/seo)
• Teams Module (modules/teams)
• UI Module (modules/ui)
• Shared Components (shared directory)
d. Build & Deployment:
• Docker Container
• Nginx Server
• CI/CD Pipeline (GitHub Actions)
Relationships to Highlight
[Client Browser] ←→ [Nginx Server]
• ↓
[Next.js Application] ←→ [Content Layer (MDX)]
• ↓
[Module Layer]
• AI Services
• SEO Services
• UI Components
• Team Services
• ↓
[Shared Components & Utilities]
Important Architectural Patterns to Emphasize
• Module Pattern (based on the modules directory structure)
• Server Components vs Client Components
• Content Pipeline (MDX → Rendered Content)
• Performance Optimization Layer
Technical Stack Indicators
• Next.js
• Bun.sh Runtime
• Docker
• GitHub Actions
• MDX Processing
• Tailwind CSS
Specific Implementation Details
• Routing structure (app directory structure)
• Where AI search functionality integrates
• Documentation organization structure
• Performance optimization implementations