How didoslavov/my-portfolio works
Main Components
A. Frontend Layer:
• Next.js Application (Core)
• Pages/Routes (/about, /contact, /guest-book, /projects)
• Components (UI, Layout)
• Client-side Features (Theme switching, animations)
B. Backend Services:
• Hasura GraphQL Engine
• Metadata configuration
• Database connections
• Next.js API Routes (/api/email)
C. External Services:
• GitHub API Integration (based on github-api.ts)
• Email Service (based on send-email.ts)
[Client Layer]
• ↕
[Application Layer]
• ↕
[Data Layer]
Component Relationships
• Client-Server communication via GraphQL (frontend → Hasura)
• API Routes handling (frontend → Next.js API)
• External service interactions (application → GitHub API, Email Service)
Detailed Component Breakdown
Frontend (Next.js):
[Pages] → [Components] → [UI Elements]
• ↓ ↓ ↓
[Layouts] → [Providers] → [Utils/Animations]
Backend:
[Hasura GraphQL Engine]
• ↓
[Database Connections]
• ↓
[Metadata Configuration]
Technical Stack Indicators
Technology badges for:
• Next.js
• TypeScript
• Tailwind CSS
• GraphQL
• Hasura
• GitHub API
Data Flow Representation
• Client-side data fetching
• Server-side API calls
• GraphQL mutations and queries
• Email service integration
• GitHub API interactions
Additional Elements
Include:
• Version information
• Environment configurations
• Build/Deploy pipeline indicators
• High-level architecture visibility
• Detailed component relationships
• Clear data flow patterns
• Technology stack integration
Remember to:
• Use consistent styling
• A clear hierarchy of components
• Both synchronous and asynchronous communications
• Security boundaries
• Public vs. private routes
This system design should effectively communicate the portfolio website's architecture while showing the integration of various services and features in a clear, professional manner.