How xcarter93/nextjs-portfolio-app works
Main Components
a) Client Layer:
• Next.js 14 App Router frontend structure
• IDE-style components (Sidebar, Tabs, Terminal)
• Interactive elements (Boot Screen, Background Effects)
• State management (Zustand store and React Context)
b) Server Layer:
• Next.js Server Components and API Routes
• Server Actions for data mutations
• Authentication system (Clerk)
c) External Services:
• PostgreSQL Database (via Prisma ORM)
• WakaTime API Integration
• GitHub API Integration
• Clerk Authentication
┌─ Client Tier ─────────────────────────┐
• ┌─ UI Components ─┐ ┌─ State ───────┐ │
• IDE Layout │ │- Zustand │ │
• Boot Screen │ │- TabsContext │ │
• Terminal │ └───────────────┘ │
• ┘ │
• ┘
• ↕ (Next.js App Router)
┌─ Server Tier ─────────────────────────┐
• ┌─ API Routes ───┐ ┌─ Server Actions┐ │
• /api/ │ │- actions.ts │ │
• middleware.ts│ └────────────────┘ │
• ┘ │
• ┘
• ↕
┌─ External Services ──────────────────┐
• ┌─ Data ────────┐ ┌─ Auth ─────────┐│
• PostgreSQL │ │- Clerk ││
• WakaTime API │ └───────────────┘││
• GitHub API │ ││
• ┘ ││
• ┘
Key Relationships to Highlight
• Real-time updates for coding stats and guest book
• Demonstrate authentication flow through Clerk
• Database interactions through Prisma
Additional Elements
• Version numbers for major dependencies
• Deployment flow to Vercel
• Error handling and loading states
This system design should be particularly detailed in showing how the IDE-like interface is achieved through the combination of client-side components and server-side functionality, while also highlighting the integration of external services for features like coding statistics and git history.