How adarshkumar76/portfolio works
Project Type and Purpose
• This is a single-page portfolio website built with React.
• It’s a static front-end application (no custom backend), hosted on a CDN or GitHub Pages, showcasing your skills, projects, and GitHub stats (via third-party image APIs).
File Structure
• Top-level files: package.json (build & dependencies), public/ (static assets: index.html, resume PDF, manifest).
• src/ contains:
• App.js + index.js (root of React app)
• Component/ (reusable UI pieces: Header, Footer, AboutMain, ContactMain, etc.)
• Screens/ (page-level components tied to routes: Home, About, Projects, Services, Contact, Login/Signup, NoPage)
• setupTests.js, reportWebVitals.js, App.test.js (test & telemetry stubs)
README
• Confirms it’s a personal portfolio.
• Lists tech stack (React, JavaScript, CSS, Node for build).
• References external APIs used in the README images for GitHub stats and quotes—these endpoints are called at build time for static images or on the client to load badges.
a. Main Components
• Web Browser (Client)
• React App (SPA)
· Router Layer (react-router)
· Page Components (Screens)
· Reusable UI Components (Component/)
• Static Asset Server / CDN (serves index.html, JS bundle, CSS, Resume.pdf)
• External Image APIs (GitHub Stats, Dev Quotes, GitHub Trophies services)
b. Relationships & Data Flow
• Browser requests index.html → served by CDN
• index.html loads JS bundle → initializes React App
• React Router maps URL to Screen component → Screen renders UI Components
• Certain components embed <img> tags pointing at external APIs → browser fetches those at runtime
c. Architectural Patterns
• SPA pattern with client-side routing
• Component-based design (separation of concerns)
• Static asset hosting + CDN
d. Key Technologies
• React, React Router, Node.js (build)
• CSS modules (.css per component)
• Third-party image badge APIs