How sumitkushwahji/portfolio works
Project Type and Purpose
• This is a front‐end only, single‐page React.js portfolio website. It has no custom backend or database; it simply hosts static assets (HTML, JS, CSS, PDFs) and is built & deployed via a CI/CD pipeline (GitHub Actions → GitHub Pages or a similar static-hosting service).
File Structure
• Top‐level
• .github/workflows/jekyll-gh-pages.yml → CI/CD definition
• public/ → Static HTML (index.html), manifest, robots.txt
• src/ → React source code & assets
• Images/ → Documentation screenshots
• package.json & package-lock.json → Build/dependency config
• src/components/
• Navbar.js, Particle.js, Pre.js, ScrollToTop.js → Generic UI components
• Home/ → Home.js, Home2.js, Type.js → Hero section with typewriter effect
• About/ → Bio cards, GitHub widget, tech/tool stacks
• Projects/ → ProjectCards & Projects listing
• Resume/ → ResumeNew component
• Footer.js
• Static PDFs in src/Assets/Projects
Extract Insights from the README
• Built with React.js, Node.js (for build), Express.js (mentioned but not used in code), React-Bootstrap, pure CSS
• Hosted as a static site (deploy via CI to Vercel or GitHub Pages)
• Responsive, multi-page layout simulated via client-side routing or anchored sections
Main Components
a. Developer Environment
– IDE & local Node.js/NPM → npm install & npm start
b. Source Code Repository
– GitHub repo holding .github/, public/, src/, package.json, README.md
c. CI/CD Pipeline
– GitHub Actions workflow (jekyll-gh-pages.yml):
• Checkout → npm ci → npm run build → deploy to GitHub Pages
d. Hosting Service
– GitHub Pages (or Vercel) serving the built static site via a CDN
e. End User Browser
– Issues an HTTP GET to the site URL → receives index.html, JS/CSS bundles, assets
f. React App Runtime
– App.js as root → renders Navbar, Particle effect, Preloader, ScrollToTop, Home, About, Projects, Resume, Footer
Relationships & Data Flow
• Developer → pushes code → GitHub Repo
• GitHub Repo → triggers GitHub Actions
• GitHub Actions → runs build → publishes output to Hosting Service
• End User Browser → fetches static site from Hosting Service
• React App (in Browser) → dynamically loads components, assets, PDFs, and renders UI
Architectural Patterns & Technologies
• Component-Based Architecture (React): each UI section is a self-contained component
• Static Site Deployment: Build once, serve static bundles (no runtime server)
• Continuous Deployment: GitHub Actions → automatic publish on push to main
• Asset Hosting: PDFs and images are served alongside JS/CSS bundles
Detail Level
• Top‐Level: Developer, GitHub, CI/CD, Hosting, Browser
• Mid‐Level: Build process steps, static asset storage
• Low‐Level (optional): React component tree