How kalavadiyaharsh/harsh_portfolio works
Project type and purpose
• This is a single‐page front-end application built with React and Vite. It has no custom backend or database; it serves static assets and JavaScript to the browser. The main purpose is to display a personal or portfolio site (based on component names like Home, Projects, Experience, Contact).
File structure
• Top level:
• index.html: SPA shell
• public/: static assets (images, favicons)
• src/: application source
– main.jsx: React entry point
– App.jsx: root application component
– components/: visual/page components
• config files: vite.config.js, tailwind.config.js, postcss.config.js, eslint.config.js
• package.json / package-lock.json: dependencies and scripts
README for additional insights
• Confirms use of Vite for bundling, Hot Module Replacement via @vitejs/plugin-react or plugin-react-swc. ESLint is configured. Tailwind CSS is integrated (via postcss.config.js).
a. Main components:
1. Developer environment
• Source code in src/, configuration files, Node.js & npm
• Build tools: Vite bundler, PostCSS, Tailwind, ESLint
2. CI/CD or build pipeline (optional)
• “npm run build” task producing production bundle
3. Static web server / CDN
• Serves index.html, CSS, JS, public assets
4. Browser runtime
• React SPA mounted within index.html
• React Router or internal navigation (if used)
5. UI components
• Navbar, Home, Skills, Experience, Projects, Contact, Eyes/NextEyes, Marquee
b. Relationships and interactions
• Developer edits src → Vite dev server watches files → rebuilds & pushes updates via HMR → browser reloads/patches components
• Build pipeline compiles code with Babel/SWC, applies Tailwind utilities via PostCSS, outputs static files
• Browser requests index.html from server → downloads CSS & JS → React hydrates App in DOM → user navigates between components
c. Architectural patterns and principles
• Component-based UI (React)
• SPA client-side routing (if implemented)
• CSS utility framework (Tailwind)
• Dev/build separation: local Vite dev vs production static hosting
d. Technologies / frameworks
• React (JSX components)
• Vite (bundler, dev server)
• Tailwind CSS + PostCSS
• ESLint (code quality)
• Node.js/npm