How yasinakbulut25/dyt-deniz works
Project Type and Purpose
• This is a full-stack Next.js web application (portfolio/blog) that:
• Renders static and dynamic pages (SSR/SSG) for public content (home, about, services, blog posts, comments).
• Exposes serverless API routes to send email and handle image uploads.
File Structure
• Top-level configs: next.config.mjs, tailwind.config.mjs, ESLint, PostCSS, JSConfig.
• src/app/: Next.js “app router” pages and layout (layout.jsx, page.jsx) plus API routes under src/app/api/send-email/route.js and src/app/api/upload/route.js.
• src/hooks/, src/lib/: custom hooks and utilities.
• src/api: client-side API wrapper (fetchRequest.js, endpoints).
README
• Confirms Next.js, client can run dev server, uses next/font for custom fonts, deploys on Vercel.
• No external database—uses serverless functions for email and file uploads.
Main Components
a. Client (Browser)
b. CDN / Edge Cache (serving static /public assets and pre-rendered pages)
c. Next.js Application Server (SSR/SSG rendering, routing)
d. API Route Handlers (Serverless Functions)
• send-email → SMTP or 3rd-party email service
• upload → file storage (local disk or cloud bucket)
e. Data Store (if any)—in this project the file system under /public/uploads
f. Optional External Services
• Email provider (e.g., SendGrid, Mailgun)
• Cloud storage (e.g., AWS S3) if extended
Relationships & Data Flows
• Browser → (1) HTTP GET → CDN/Edge → Next.js server → page HTML/JSON → Browser.
• Browser → (2) API POST → /api/send-email → Email service → SMTP.
• Browser → (3) API POST → /api/upload → File storage → return URL → Browser.
• Next.js build pipeline reads src/app, src/components, tailwind/Next config → outputs static assets + serverless functions.
Architectural Patterns & Design Principles
• Serverless Functions: encapsulated in /src/app/api/*/route.js.
• App Router (Next.js): file-system based routing under src/app.
• Component-Driven UI: isolation of reusable UI in src/components.
• CDN-First: static assets and prerendered pages served globally.
Technologies & Frameworks to Annotate
• Next.js 13+ App Router
• React & JSX
• Tailwind CSS + PostCSS
• Vercel (deployment & CDN)
• Node.js runtime for Serverless routes
• Optional: SMTP / Cloud Storage SDK
• Break out:
• Frontend: React pages/components, styling, routing.
• Backend: Next.js SSR/SSG engine, API functions.
• External Dependencies: Email provider, optional storage.
• Both build-time (Next.js build, Tailwind compile) and run-time flows (HTTP requests, serverless executions).
• Keep it detailed but uncluttered, grouping related pieces logically.