How rohangoyal37/portfolio_website works
Project Type and Purpose
• This is a frontend-only SPA (built with Create-React-App) showcasing a personal portfolio: Home, About, Skills, Experience, Education, Projects, and Contact sections.
• It’s deployed as a static site but integrates with third-party services for email and maps.
File Structure
• Top-level files: package.json, babel.config.js, tailwind.config.js → build and styling configuration.
• public/: static assets (HTML template, PDF resumes, certificates, manifest).
• src/: React app source—entry point (index.js), global CSS, and component tree (App.js → <Section/> → /components/...).
• JSON data under src/components/*/*.json for Certifications, Projects, Skills.
Key Architectural Insights from README
• Tech stack: React, Tailwind CSS, Framer Motion, React-Spring, Recharts, EmailJS, Google Maps API, Vercel hosting.
• Features: Non-scroll navigation, glassmorphism, animations, theme switcher, responsive design.
Main Components & Relationships
a. User Client (Browser)
• Loads index.html + JS/CSS bundle from Vercel CDN
• Renders React SPA
b. React Application
• Component hierarchy:
– <App>
· <Navbar> (anchors for each section)
· <ParticleBackground> (animation + ThemeContext)
· <Section> (one‐per‐page view)
· Section modules: Home, About, Skills (with Recharts), Experience, Education, Projects, Contact (with EmailJS & Google Maps), Footer
• Static JSON data imported at build time for Projects, Skills, Certifications
• CSS/Tailwind modules for styling; CSS files per component
c. Build Pipeline & Hosting
• GitHub repo (push triggers Vercel)
• Vercel build: npm install → Babel/Webpack compile + Tailwind processing → npm run build → produce static build/
• Vercel CDN serves assets worldwide
d. External Services
• EmailJS REST API for sending contact form emails
• Google Maps JavaScript API for interactive map in Contact section
Architectural Patterns & Design Principles
• Component-based SPA: clear separation of UI concerns into reusable components
• Data-driven views: JSON files drive Certifications, Projects, Skills
• Static hosting + client integration: no custom backend—third-party APIs only
• Theming & State: React Context (ThemeContext) for light/dark mode
Essential Elements
• Clear component boundaries (e.g., root <App> vs. child sections)
• Build & deploy flow (GitHub → Vercel CI → CDN)
• External integrations with EmailJS and Google Maps
• Data sources: local JSON vs. third-party APIs