How erazor48/ethan-portfolio works
To accurately represent the “Ethan Orain Portfolio – AI Chatbot” system, follow these steps:
Project Type and Purpose
• This is a full-stack Next.js web application (React + server-side API) that serves a personal portfolio with:
• A static/dynamic frontend (app pages + React components)
• A backend API (Next.js API routes) providing AI‐driven chat and GitHub‐synchronized data
• External integrations (OpenAI via LangChain, GitHub API)
File Structure
• Top-level:
• app/… – Next.js 13 “app router” pages (UI routes and server components)
• app/api/… – serverless API routes: POST/GET /chat, GET/POST /projects
• components/… – React UI components and custom hooks
• lib/… – core data and service layer:
– lib/data/personal-data.ts (in-code database)
– lib/services/*.ts (ChatbotService, GitHubSyncService, ProjectAutomationService, DataService)
– lib/ai (LangChain integrations and tools)
• public/, styles/ – static assets and Tailwind CSS
• next.config.ts, tsconfig.json, package.json – build & tooling
Extract Architectural Insights from README
• Four main backend services abstracted in lib/services
• Data flows: GitHub → cache/DataService → frontend & chatbot
• Chatbot uses LangChain (ChatbotService) calling OpenAI
• Project automation auto-manages and caches projects
• Frontend UI components consume data via built-in fetch to API routes
Main Components and Their Interactions
a. Frontend Layer
– Next.js React pages (app/…) render UI components (components/)
– ThemeToggle, Navbar, Hero, ProjectCard, ExpandableChatDemo, etc.
– Invokes client-side hooks (useChat) and browser fetch to API
b. API Layer (Backend)
– /api/chat → ChatController → ChatbotService (uses LangChain → OpenAI API) & DataService
– /api/projects → ProjectController → GitHubSyncService & ProjectAutomationService & DataService
c. Service Layer
– DataService: central facade for lib/data and cached GitHub data
– GitHubSyncService: fetches repos via GitHub API → caches in DataService
– ProjectAutomationService: processes, enriches project data
– ChatbotService: builds prompts, invokes LangChain, returns responses
d. Data Layer
– personal-data.ts: static definitions (experience, skills, about)
– GitHub‐fetched data: projects, languages, stats
– Cache mechanism (in-memory or file/cache store) managed by services
e. External Systems
– OpenAI API (via LangChain)
– GitHub REST API
Architectural Patterns & Design Principles
• Separation of Concerns: UI, API/controllers, services, data
• Facade Pattern: DataService unifies data access
• Adapter Pattern: lib/ai/tools wrap external calls (GitHubTool, ProjectTool, SkillTool)
• Serverless API Routes in Next.js (scalable, on-demand)
• React Server Components vs Client Components (app/ vs components/ui)
• Clear, consistent labels for each node