How idiltugba/idiltech works
Project Type & Purpose
• This is a Next.js v13 frontend project (no custom backend) built with TypeScript and Tailwind CSS.
• It serves as a personal website (“idiltech”) plus an embedded pin‑pong game and a dynamic “project” page.
Key Architectural Components
a. Client Browser
b. Next.js Server (or Vercel/Lambda deployment)
c. Application Router (app/ folder & dynamic routes)
d. React Components (components/ folder)
e. Static Assets (public/ folder)
f. Build Pipeline (Babel, Webpack, PostCSS, Tailwind)
g. Data Sources (oldprojects.json, works.json, social.json)
Component Relationships & Data Flow
• On a browser request, the Next.js Server uses the app/ router and page.tsx files to perform SSR or SSG.
• Layout.tsx provides the global page shell (header, footer, menus).
• Dynamic routes under app/[project]/page.tsx fetch project metadata from JSON or public/projects.
• React components under components/ render UI widgets (face‑animation, pinpongame, menu sections).
• Tailwind/PostCSS processes CSS (globals.css + tailwind.config.js) at build time.
• Static assets (images, fonts, scripts) in public/ are served directly by the CDN.
Architectural Patterns & Design Principles
• Component‑based UI: atomic React components in components/.
• App Router (Next.js 13) for declarative routing and nested layouts.
• SSG/SSR hybrid: static generation for pages without dynamic data; server rendering on demand for dynamic routes.
• Separation of concerns: styling (Tailwind) vs logic (TypeScript) vs assets (public).
• Notes on where SSR vs SSG vs client hydration occurs