How sohamwalam11/soham-portfolio works
Project type and purpose
• This is a single-page portfolio website built with React and TypeScript.
• It’s deployed as a static site (via Vercel), showcasing projects, skills, achievements, and a contact form.
File structure
• Top-level files: package.json, tsconfig.json, vite.config.ts, postcss.config.js, tailwind.config.ts. → build & tooling config.
• public/ → static assets (resume, images, projects data folders).
• src/
• pages/Index.tsx, NotFound.tsx → route targets (SPA routing).
• App.tsx, main.tsx → application root and bootstrapping.
• components/ui/… → reusable UI primitives (shadcn/ui wrappers).
• hooks/ → custom React hooks (e.g., useMobile, useToast).
• lib/ → helper modules (data loaders: achieve.ts, certs.ts, utilities).
• README describes tech stack: React, TypeScript, TailwindCSS, shadcn/ui, Framer Motion, Vercel.
README for additional insights
• No backend/API; all data is static or loaded at build time.
• Animations via Framer Motion; UI styling via Tailwind + shadcn/ui.
• Deployment on Vercel implies a CI/CD pipeline that runs the Vite build and serves the dist folder.
Main components & relationships
a. Components:
1. Developer Workstation
• Source code (Git), VS Code, local dev server (Vite).
2. Build System (Vite)
• Transpilation (TSX → JS), bundling, PostCSS (Tailwind) → production assets.
3. CI/CD (Vercel)
• Git integration triggers build & deploy.
4. CDN/Static Hosting
• Serves index.html, JS/CSS bundles, public assets.
5. Client Browser
• Loads SPA, executes React + hooks, renders UI.
6. External Services (optional)
• Contact form submission (e.g., formspree, email API).
b. Relationships & data flow:
• Developer pushes code → Vercel CI → Vite build → generated static files → deployed to CDN.
• End user browser → requests index.html & assets → receives JS bundle → React app bootstraps (main.tsx → App.tsx) → client-side routing (pages/Index, NotFound) → loads static data from lib/ modules → renders UI components from components/ui.
• If contact form is used, client makes an HTTP POST to an external API/service.
c. Architectural patterns & design principles:
• SPA architecture: client-side routing + component-driven UI.
• Atomic UI components (shadcn/ui library wrappers).
• Utility-first CSS (Tailwind) with design system tokens.
• Build-time data loading (lib/achieve.ts, lib/certs.ts).
• CI/CD with “deploy on push” model.
d. Key technologies & frameworks:
• React 18, TypeScript, Vite (bundler), TailwindCSS + PostCSS, shadcn/ui, Framer Motion, Vercel.
Detailed capture of essential elements
• Break out UI sub-systems:
• Layout & pages (Index, NotFound)
• UI primitives (accordion, button, modal, etc.)
• Animation layer (Framer Motion)
• Config files as part of the build node.
• That “public/” content is directly served off CDN.