How yiyixuu/personal-website works
• Client (Browser): Represents the end-user’s device making HTTP requests.
• CDN/Deployment Platform: Although the README emphasizes Vercel (and there is also a netlify.toml), include a “Deployment Platform” node that shows platforms like Vercel or Netlify that act as the hosting and edge network.
• Next.js Server and Routing Layer: This represents the server-side part of the app that handles SSR, static generation, and API routes (if used). Indicate that this layer uses React and the Next.js app directory routing mechanism.
• UI Layer (Components): Within the server or build process, show the “Components” node (from src/components) that builds the UI, including navigation, sections (Hero, About, Projects, etc.), and reusable UI components library.
• Business Logic/Utilities: A node for “Lib/Utils,” indicating helper functions and project-specific logic found in src/lib.
• Public Assets: A node showing the “public” directory that contains images, robots.txt, and other static files available to the client.
• Build/Deployment Process: Outline that Next.js automatically builds the app (the .next folder) and produces artifacts that are served in production. You may optionally include “Build Tools and Config” such as tsconfig.json, next.config.js, tailwind.config.ts, and scripts in package.json.
Relationships and interactions
• Within the Next.js server layer, illustrate how the “app” folder is composed of pages and nested routes (like “/projects” and “/projects/[slug]”).
• That utilities and data (lib folder) support these components and pages.
Technology stack details
• Next.js / React (UI and SSR framework)
• TypeScript (for type safety and development)
• Tailwind CSS (for styling)
• Vercel (or Netlify) as the Deployment Platform
• next/font (for optimized font loading)
• Any additional libraries like Framer Motion, Lucide React, etc., which appear in the build chunks, can be noted as part of the UI/enhancement libraries.
• Labels on each component should clearly indicate their role.
• Distinguish between build-time artifacts and runtime components to indicate the role of the .next build output.