How pranshuverma601/pranshu.portfolio works
Project type and purpose
• This is a frontend-focused web application built with Next.js (React framework)
• It serves a multi-page site (About, Projects, Contact, Resume) with static assets (PDF resume, fonts)
• No custom backend or database is present—content is pre-rendered at build time or served server-side
File structure
• src/app – Next.js App Router directory containing route folders (about, contact, projects, resume) and root layouts
• src/components – Reusable UI pieces (Navbar, Footer)
• public – Static assets (resume.pdf, any images or favicon)
• Configuration files (next.config.ts, tsconfig.json, ESLint, PostCSS) define build, lint, and styling pipelines
README insights
• Uses Next.js 13+ App Router and next/font for optimized font loading
• Built with Create-Next-App, deployed via Vercel (SSG/SSR, CDN)
Main components
• User’s Browser
• Next.js Server/Edge Functions (Vercel Edge Runtime)
• File-based Router (src/app → route handlers & layouts)
• React Components (Navbar, Footer, Page Templates)
• next/font Optimization Service
• Build Pipeline (npm script → Next.js compiler → pre-rendering)
• CDN / Vercel Hosting
Relationships and interactions
• Browser → HTTP GET → Vercel CDN edge
• Edge Function (SSR) or CDN cache (SSG) serves pre-rendered HTML
• React hydration on the client uses src/components
• Font optimization: next/font fetches Geist font from Vercel CDN
• Static assets (resume.pdf) delivered directly from public bucket
Architectural patterns & design principles
• File-based routing (App Router)
• Hybrid Rendering:
– Static Site Generation (SSG) for truly static pages (resume, projects list)
– Server-Side Rendering (SSR) or Incremental Static Regeneration where dynamic content is needed
• Component-driven UI (atomic design)
• Edge-first deployment (Vercel edge functions + global CDN)