How hancheo/mobilog works
Main System Components
a) Client-Side (Frontend):
• Next.js Application Layer
• Component Library
• Theme/Style System
• Client-side Providers (Analytics, Theme)
b) Server-Side:
• API Routes Layer
• Core Services Layer
• Data Sources Layer
• Repository Layer
c) External Services:
• Notion API Integration
• Google Analytics Integration
• Comment System
Architectural Patterns to Highlight
The project follows these patterns that should be represented:
• Clean Architecture (visible in the server/services/useCases structure)
• Repository Pattern (server/services/repository)
• Provider Pattern (client/providers)
• Component-based Architecture (client/components)
[Client Layer]
• ↕
[Next.js API Routes]
• ↕
[Service Layer]
• ↕
[Repository Layer]
• ↕
[External Services]
Detailed Component Breakdown
Frontend Section:
• Main components (PostList, Comments, VisitorCounter)
• Core components and layouts
• Providers (ThemeProvider, GoogleAnalyticsProvider)
Backend Section:
• API routes (/api/blog, /api/posts, /api/tags)
• Service layer with use cases
• Repository pattern implementation
• Data sources (Notion, Google Analytics)
Key Interactions to Highlight
• Notion Integration Flow
• Visitor Counter System
• Comment System Flow
• Dynamic OG Image Generation
• Search Functionality
Technical Details
• Next.js as the framework
• TypeScript implementation
• Tailwind CSS for styling
• API Routes structure
• Clean Architecture implementation
Remember to:
• Use clear, consistent symbols
• Data flow directions
• Separation between client and server components
• Demonstrate the integration points with external services
This will provide a clear understanding of how Mobilog transforms Notion content into a full-featured blog platform with additional capabilities like visitor counting and dynamic image generation.