How pranshuverma601/my-protfolio works
Project type and purpose
• This is a front-end single-page application (SPA) built with React and Vite.
• It’s a minimal template/portfolio-style site: static HTML/CSS/JS delivered to the browser, no backend or API layer.
File structure
• Top level:
• package.json, vite.config.js — npm scripts & Vite build/dev config
• index.html, public/ — static entry point & public assets
• src/ — application source
• src:
• main.jsx + index.css — React entrypoint + global styles
• App.jsx + App.css — root component
• Components/ — feature components (Navbar, Hero, About, Services, MyWork, Contact, Footer), each with its own .jsx + .css
• assets/ — local data modules (mywork_data.js, services_data.js)
• No server or database directories ⇒ purely client-side.
Insights from the README
• Uses Vite for dev server and bundling.
• Supports Fast Refresh via @vitejs/plugin-react (Babel) or plugin-react-swc.
• ESLint rules in eslint.config.js.
a. Main components:
• Developer Workstation
• Source Code (src/, public/, config files)
• Vite Dev Server (with HMR plugin)
• Build Process (Vite bundler → dist/)
• Static Hosting / CDN
• Browser Client
b. Relationships & interactions:
• Developer edits source → Vite Dev Server picks up changes → HMR pushes updates to Browser
• On production build: Vite bundles & outputs to dist/ → static assets are deployed to Hosting/CDN → Browser fetches HTML/CSS/JS
• Components inside React interact locally (Navbar dispatches events, Hero loads asset data, etc.), but these are internal to the Browser runtime.
c. Architectural patterns & design principles:
• Component-based UI (React)
• Modular CSS per component
• Single entry point (index.html → main.jsx)
• Development vs. production workflows separated by Vite
d. Technologies & frameworks:
• React (UI library)
• Vite (dev server + bundler)
• @vitejs/plugin-react or plugin-react-swc (Fast Refresh)
• ESLint for linting
• npm/Yarn for dependency management