How ozgurozalp/my-website works
Project type and purpose
• This is a Jamstack‑style, Next.js (v13+) website built with the App Router, MDX blog posts, Tailwind CSS, and TypeScript.
• Its purpose is to serve a personal/professional website with static and dynamic pages (home, about, blog listing, blog detail, custom pages).
File structure
• Top‑level config: next.config.ts, tsconfig.json, tailwind.config.ts, postcss.config.mjs, .eslintrc.json, .prettierrc. These indicate a modern React/Next.js toolchain with linting, formatting, and CSS-in-JS.
• public/: Static assets (images, PDF resume) and metadata (robots.txt, manifest.json, sitemap.ts).
• src/app/: The Next.js App Router directory driving routing and page layouts. Contains server and client components (page.tsx, layout.tsx) for each route (/, /about, /ben-kimim, /blog, /blog/[slug], /blog/category/[slug]).
• src/components/: Shared UI components (typography, buttons, dropdowns) and page‑specific components (BlogList, BlogCard).
• src/posts/: MDX files for blog content.
• src/lib/ and src/utils/: Helper functions and constants.
• src/actions/: Potential server actions or API handlers.
Detailed breakdown of components
• Build Server
• Tailwind/PostCSS module
• MDX parser
• Next.js SSG/SSR engine
• pnpm install/build scripts
• CDN/Edge
• Caches static HTML, CSS, JS
• Runs SSR via serverless/Edge Functions when cache misses
• File System
• src/app (routes & layouts)
• src/components (UI library)
• src/posts (content)
• public (images, PDF, robots.txt, manifest.json)
• Client Browser
• Hydrates server-rendered pages
• Executes client components (e.g., page.client.tsx)
• Interacts with UI (dropdowns, tooltips)