How zikompo/website_v2 works
Project type and purpose
• This is a Next.js-based personal website (portfolio/blog) using the App Router (app/ directory) and MDX for writing posts. It delivers static and semi-dynamic content (SSG/ISR) and lives entirely in the frontend layer—there is no custom backend or microservice.
File structure
• Top-level “my-website” folder holds all source.
• app/ contains the Next.js App Router: page.tsx files for each route, layout.tsx for shared wrappers, global CSS.
• app/components + components/ui/ houses reusable React components (cards, dialogs, buttons).
• app/writing and writings/ store MDX content. lib/ contains utility functions (MDX serialization, theme helpers).
• hooks/ for React hooks (e.g., useTheme).
• public/ holds static assets (PDF, images).
• Configuration files: next.config.js/ts, tsconfig.json, postcss.config.mjs, package.json.
Elements
• Clear labels for: Browser, CDN/Hosting, Next.js Build, App Router, MDX Compiler, React Components, CSS Processor, Public Assets.
• Build phase data flows: MDX files → MDX Compiler → Static HTML + JS bundles
• Runtime flows: Browser ↔ JS bundles via React hydration; Browser → public assets
• Runtime components (Router, React, Hooks) in another
• Static assets and external hosting as a third