How harshaltupe12/portfolio works
Project type and purpose
• This is a Next.js–based personal/portfolio website that uses React for UI, Tailwind CSS for styling, and Next.js’s App Router for file-based routing and SSR/SSG capabilities. There is no separate “backend” folder—Next.js itself handles server-side rendering, static export, and API routes (none defined here).
File structure
• Top level:
• app/ — Next.js App Router directory containing page routes (page.jsx files), shared layout (layout.tsx), global CSS, and nested sub-routes (about, contact, etc.).
• components/ — reusable React UI components, further subdivided into:
– magicui/ — custom “theme” or “design system” primitives (aura-button, aurora-text).
– ui/ — generic, animated, 3D, or theme-provider components.
– SchemaMarkup.tsx for SEO/schema.
• lib/ — application-level utilities (utils.ts).
• utils/ — small helper scripts (cn.ts for classnames, skill-image.js, skills.js).
• public/ — static assets served directly (SVGs, robots.txt, sitemap, manifest).
• config files — next.config.mjs, tailwind.config.ts, postcss.config.js(mjs), tsconfig.json, package.json.
README for additional insights
• It’s a stock Next.js “create-next-app” scaffold.
• No mention of API routes or database—so it’s purely frontend with SSR/SSG.
• Deployed on Vercel (implied), serves static pages and assets, optimized fonts via next/font.
Elements
• Clear labels: Browser, CDN/Edge, Next.js Server, Page Renderer, Component Library, Styling Pipeline, Static Assets, Utilities, External Services
– Request flow (Client → CDN → Server → Client)
– Data/style flow (Tailwind config → CSS bundle → Client)
– Asset fetch (Client → CDN → public/)
– Purple for external services (Google Fonts, Analytics)
Final advice
1. Routing & SSR Engine (reads app/ tree, invokes React render)
• “layout” layer separately to show persistent UI
• Don’t forget to show the build step (+ Tailwind/PostCSS) as part of the CI/CD process if needed