How azzazeru/portfolio works
Project type and purpose
• This is a Next.js 13 “app directory” portfolio website (no separate backend service).
• Purpose: serve static and SSR React pages (Hero, Contact, System Architecture, Technical Metrics), styled with Tailwind CSS, and deployed via Vercel or similar.
File structure
• Top-level:
• .github/workflows/nextjs.yml – CI/CD pipeline config
• app/ – Next.js 13 app directory (components, layout, global CSS)
• public/ – static assets
• next.config.ts, tsconfig.json, tailwind.config.ts, postcss.config.mjs, eslint.config.mjs – build and lint configs
• package.json – dependencies (React, Next.js, Tailwind, etc.)
• No /api folder, so no custom serverless functions—site is pure frontend with SSR/SSG.
README for additional insights
• Tech stack: React, Next.js, Tailwind, TypeScript
• CI/CD interest: GitHub Actions workflow present
• Deployment target implied (Vercel or Netlify)
a. Client Browser
– Renders HTML/CSS/JS
– Hydrates React components
b. Next.js Application (Edge/Serverless)
– SSR/SSG functions at build time or per request
– App directory pages and React Components
– Tailwind CSS processed via PostCSS
c. CDN / Static Asset Hosting
– Hosts JS bundles, CSS, images under public/
d. GitHub Actions CI/CD
– Runs on push/PR via .github/workflows/nextjs.yml
– Steps: install, lint, build, deploy to Vercel
e. External Services (optional)
– Vercel (or similar) for hosting
– Analytics or badge services referenced in README
Relationships and interactions
• Browser → CDN: fetches static JS/CSS/images
• Browser → Next.js Edge/Serverless: SSR content requests
• Next.js build → generates static HTML / JSON for SSG
• CI Pipeline → triggers build → deploys to hosting
• GitHub → GitHub Actions workflow triggers on push
Architectural patterns and design principles
• JAMstack: static + serverless SSR
• Component-based UI (React)
• CSS utility-first (Tailwind)
• Infrastructure as code (GitHub Actions definitions)
• Separation of concerns:
• UI (React components in app/components/)
• Build config (Tailwind, PostCSS, ESLint)
• Deployment (CI/CD workflow)