How andreean26/adam_web works
This repo is a single Next.js 15 (App Router) portfolio website: a mostly static/content-driven frontend with client-side interactions (theme toggle, scroll reveal, animated background) and static data sources (TypeScript data files) plus public assets (images, CV PDF). There is no evident custom backend (no src/app/api/*, no server folder, no DB layer).
• Delivery/runtime of a Next.js app (Vercel/Node runtime + CDN/static assets)
• UI composition (App Router → page → sections → UI components)
• Data/asset flow (static TS data + public images/documents)
• Build/deploy pipeline (Next build output, Vercel deployment)
Runtime entrypoints / routing
• src/app/layout.tsx — global shell (fonts, theme provider patterns if present, header/footer inclusion)
• src/app/page.tsx — the home route composing all sections
• src/app/globals.css — global styling layer
“Data layer” (static, build-time bundled)
• src/assets/data/projects.ts
• src/assets/data/services.ts
These are the primary “content sources” powering Portfolio/Services UI.
Static assets served via Next/public
• public/images/** — hero + project images
• public/assets/documents/** — CV PDF
These are delivered as static files (typically CDN-cached in production).
Cross-cutting config/tooling
• next.config.ts — Next runtime/build configuration
• postcss.config.mjs, Tailwind usage (implied by README)
• tsconfig.json, package.json — TypeScript + dependency graph
Next.js App (Next 15 App Router)
• Responsibilities: routing (/), rendering, bundling, serving HTML/JS/CSS
Static Asset Store / CDN
• Source: public/ folder
• Assets: images, PDF CV
• Delivered to browser independently of page HTML (still under same domain typically)
Build Pipeline (CI/CD)
• npm run build → Next build output
• Deploy to Vercel on git push
Key relationships
• Next.js App uses Tailwind/PostCSS to produce CSS
• Next.js App bundles TypeScript content from src/assets/data/* into build artifacts
• Next.js App references public/* assets by URL path
• Edge/CDN (static + caching)
• Serverless/Node runtime (rendering, if SSR is used)
This is where you “separate into as many components as possible” while staying true to the repo.
App Shell
• src/app/layout.tsx
• contains/uses: Header, Footer, global styles (globals.css), fonts (Geist per README)
Route
• src/app/page.tsx
• composes sections in order:
• HeroSection
• AboutSection
• SkillsSection
• ServicesSection
• PortfolioSection
• ContactSection
Section internals
• ServicesSection → consumes src/assets/data/services.ts → renders Card/Button (or equivalents)
• PortfolioSection → consumes src/assets/data/projects.ts → renders project cards, images from public/images/data/...
• HeroSection → likely references hero image (public/images/hero/...) and CV link (public/assets/documents/...)
Interaction/UI primitives (cross-cutting)
• ThemeToggle → affects global theme state (often via class on <html>/<body> or context); may persist in localStorage/cookies (if implemented)
• ScrollReveal + useScrollReveal → intersection observer / scroll-trigger animation behavior used by sections
• ScrollProgress, BackToTop → window scroll listeners
• AnimatedBackground, NatureDecorations → visual layer used across hero/page
• Composition: page.tsx → sections → UI components
• Data dependency: sections → assets/data/*.ts
• Asset dependency: sections/components → public/images/* and public/assets/documents/*
• Hook dependency: ScrollReveal → useScrollReveal
Labels on nodes (don’t keep them implicit):
• “Next.js 15 App Router” (container)
• “Tailwind CSS (PostCSS)” (build-time styling)
• “Static content (TS modules): projects.ts, services.ts”
• “Static assets (public/): images, CV PDF”
• “Client-side interactions: theme toggle, scroll listeners, intersection observer”
Notable architectural patterns to highlight
• App Router composition: layout.tsx as shell + page.tsx composing sections
• Component taxonomy: layout/ vs sections/ vs ui/ (clean separation)
• Static data-driven rendering: services/projects are code-defined datasets (no CMS/DB)
• Cross-cutting UI behavior via hooks: useScrollReveal consumed by UI component(s)
Concrete diagramming rules (make it readable and unambiguous)
Use consistent visual grammar:
• “HTML (RSC/SSR/SSG)”
• “JS bundle”
• “CSS”
• “/public/images/*”
• “projects.ts (import)”
• “Repo / Source” boundary (src/, public/)
• “Build Output (.next)” boundary (conceptual)
• “Hosting (Vercel)” boundary (prod runtime)
Context: Visitor ↔ Portfolio Site (Vercel) ↔ External links (GitHub/LinkedIn/Email)
2. Container: Browser → CDN/static assets + Next.js rendering runtime; plus CI/CD from Git → Vercel
3. Component: layout.tsx + page.tsx + sections + UI + hooks + static data + public assets
That combination will be both accurate to the repo and detailed enough to communicate architecture, composition, and operational flow.