How hamzachbit/protfilo-v1 works
Project type and purpose
• This is a Next.js front-end web application (likely a personal portfolio or marketing site) built with React, TypeScript, Tailwind CSS, and deployed to Vercel or a similar static/SSR hosting platform.
• It does not include a custom backend API or database—Next.js handles routing, rendering (static-site generation, SSR), and serving of public assets.
File structure
• Top-level “app” directory: Next.js “App Router” pages and route handlers (page.tsx for the home page, sitemap.ts, robots.ts).
• “components” directory: React UI components (Navbar, Footer, Banner, ArchiveCard, etc.).
• “context” directory: React Context providers (ThemeContext for dark/light mode, Toast notifications).
• Configuration files: next.config.js, tailwind.config.js, postcss.config.js, tsconfig.json for build, linting, and styling pipelines.
• “public” directory: static assets (PDF resume, XML proof file, manifest, images).
README for additional insights
• Confirms use of Next.js, next/font for Google Fonts, Tailwind CSS for utility-first styling, and recommended development commands.
• No mention of serverless functions or external APIs—project likely self-contained.
Detail without over-splitting
• Routing layer separately from UI components.
• React Context wrappers around the page/layout.
[Browser(Client)]
↓ HTTP Request
[Next.js Runtime @ Vercel]
├─ App Router (page.tsx, sitemap.ts, robots.ts)
├─ Layout.tsx + Context Providers (ThemeContext, Toast)
├─ React Components (Navbar, Banner, Footer, etc.)
└─ CSS Pipeline (Tailwind → PostCSS → bundle.css)
↓ (prerendered HTML + CSS + JS)
[Browser hydrates React]
↔ Fetch static assets from [Public CDN]
↔ Fetch fonts from [Google Fonts CDN]