How raghavxkatta/raghavkatta works
Project type and purpose
• This is a front-end–only, single-page portfolio application.
• It uses React (SPA framework), Tailwind CSS, Framer Motion, Lenis, and is deployed as static assets via Vercel.
• Purpose: showcase the developer’s work, skills, contact info, and animated experience.
File structure
• Top level:
• package.json / package-lock.json, Vite/Tailwind/Vercel config files, README.md
• public/: index.html + static images/assets served at root
• src/:
– assets/: images/media
– components/: UI sections (Hero, About, Projects, Skills, etc.)
– context/: ThemeContext for global state
– App.jsx & main.jsx: React entry points
– index.css / App.css: Tailwind & global styles
• Build/config: vite.config.js, tailwind.config.js, eslint.config.js
• Deployment: Vercel integration (.vercel/ not shown in file tree but noted in README)
README for additional insights
• CI/CD: GitHub → Vercel
• Live URL: served over CDN
Components
a. Developer & Source Control
• Developer’s local environment (IDE, npm scripts: dev, build, preview, lint)
• GitHub repo
b. CI/CD / Build Pipeline
• Vercel build step invoking Vite → produces /dist (static bundle: index.html, app.js, CSS)
c. Hosting & Delivery
• Vercel (CDN edge nodes) serving index.html and static assets
d. Client-side runtime (Browser)
• Loads index.html → main.jsx mounts <App/> at root
• App.jsx wraps everything in ThemeContext
• Components hierarchy: Header, Hero, About, Skills, Projects, ContactTerminal, Footer, etc.
• Styling: Tailwind CSS classes, global CSS
• Animations & interactions: Framer Motion, Lenis for smooth scrolling, React Toast for notifications
• Assets fetched from /assets folder on CDN
e. External integrations (if any)
• GitHub Stats component may fetch GitHub APIs
• ContactTerminal may send email or integrate with form backend (if configured)
Relationships and data flows
• Developer → (push) → GitHub → (webhook) → Vercel
• Vercel → (run) → Vite build → outputs dist → deploy to CDN
• Browser → (GET) → CDN → index.html + JS/CSS → Browser executes React app
• React app → (renders) → components → (use) → assets, contexts, animations libraries
• Any API calls: e.g. GithubStats component → GitHub REST API
Architectural patterns & principles
• SPA served as static assets (no server-side logic)
• Component-based UI (React)
• Global state via React Context (ThemeContext)
• Utility-first styling (Tailwind)
• Animation layer abstracted (Framer Motion + Lenis)
• CI/CD for zero-downtime static deployments