How kevin-2810/personal-portfolio works
Project type and purpose
• This is a static, single-page personal portfolio website built purely with frontend technologies (HTML, CSS, JavaScript, Bootstrap, AOS).
• Purpose: showcase skills, projects, contact info; hosted on GitHub Pages or any static host.
File structure
• Top-level files:
• index.html – entry point
• style.css – custom styles
• script.js – custom behavior
• Kevin.Gandhi Resume.pdf – downloadable asset
• assets folder:
• images/ – pictures used on the page
• No backend code or server-side logic; everything is client-side static content.
Key technologies from README
• HTML5 structure
• CSS + Bootstrap (via CDN)
• JavaScript + AOS library (via CDN)
• Google Fonts (via Google’s CDN)
• Deployed on GitHub Pages (static hosting)
Main components
a. Client Browser
b. Static Hosting Platform (GitHub Pages or equivalent)
c. Static Assets:
• index.html
• CSS (style.css + Bootstrap CSS)
• JavaScript (script.js + AOS JS + Bootstrap JS)
• Images
• Resume PDF
d. External CDNs / Third-party Services:
• Bootstrap CDN
• AOS CDN
• Google Fonts CDN
Relationships and data flows
• User’s Browser → requests → Static Host → serves → index.html
• index.html → references → CSS & JS assets (local + CDN) → Browser loads & renders
• index.html → references → images & PDF → fetched from static host
• JS (script.js) & AOS animate elements on scroll
Architectural patterns & principles
• Single-page static website (no client-server state beyond asset fetch)
• Separation of concerns:
• Markup (HTML)
• Styling (CSS/Bootstrap)
• Behavior (JavaScript + AOS)
• CDN usage for performance and caching
• Hosted on a global static hosting (GitHub Pages) for high availability
Detail without overcomplication
• If desired, annotate that GitHub Actions or CI/CD could automatically publish on push (optional extension)