How thienguen/website works
Project Type and Purpose
• This is a full-stack, server-rendered Next.js 13 portfolio/guestbook application.
• It combines React UI (app router + server components), serverless API routes, a relational database (Prisma + PlanetScale), and third-party services (OAuth providers, Lanyard API).
Main Architectural Components
a. Client Layer
• Web browser running React/Next.js client components (hydrated UI, hooks, kbar, useSound).
b. Next.js Application (Server & Serverless)
• App Router: server components for pages under /src/app/* (render at request time or static).
• API Routes: under /src/app/api/* (e.g. /auth, /guestbooks, /delete) implemented as serverless functions.
• Middleware: authentication checks, redirects.
• NextAuth Layer: in /src/lib/nextauth – sets up session providers (GitHub, Google), JWT/cookie management.
• Prisma Client: in /src/lib/prisma.ts – ORM connecting to PlanetScale via DATABASE_URL.
c. Database Layer
• PlanetScale MySQL instance managed via Prisma schema in /prisma/schema.prisma.
• Stores user sessions, guestbook entries, any future blog content.
d. External Services
• OAuth Providers: GitHub OAuth, Google OAuth for user sign-in.
• Lanyard API: fetches real-time Discord presence.
• Vercel Platform: hosts the Next.js app with CDN, serverless functions, environment management.
Relationships and Data Flows
• Browser → Next.js App Router: requests pages (SSR/SSG) and receives HTML + JSON for hydration.
• Browser → API Routes: fetch/POST requests for guestbook entries, deletions, auth callback flows.
• Next.js Server → Prisma → PlanetScale: run queries/mutations for persistent data.
• Next.js Server → OAuth Providers & Lanyard API: perform REST calls for authentication and presence data.
• Next.js App → Public CDN: load static assets (images, CSS, sounds).
Architectural Patterns & Design Principles
• Server-Side Rendering (SSR) & Static Generation (SSG) via Next.js App Router.
• Component-driven UI: reusable React components in /src/components and /src/ui.
• Separation of concerns:
• UI layer (components + styles).
• Data access layer (Prisma in lib).
• Auth layer (NextAuth providers in lib/nextauth).
• API layer (serverless routes).
• Environment-driven configuration for secrets & URLs via .env.
• CDN + edge-network for static assets (public folder).
Elements
• Clear component labels (e.g., “Next.js App Router”, “Guestbook API Route”, “Prisma Client”).
• Notation of environment/config file for secrets (e.g., .env).