How harshgupta2125/my-portfolio works
Project type and purpose
• This is a static portfolio website built with plain HTML, CSS and JavaScript.
• Purpose: showcase the developer’s skills, projects, certificates and provide contact links.
• Deployment: hosted on Netlify with a custom domain and CDN for fast delivery.
File structure
• Top-level assets:
• index.html – entry point rendered in the browser
• style.css – global styles
• script.js – any client-side interactivity
• resume.pdf – downloadable asset
• certificates/ – folder of certificate images or PDFs
• README.md contains descriptive content and deployment info.
• No backend code or databases—purely static files served.
Key insights from the README
• Project description: personal portfolio, web-dev focus.
• Live site URL on Netlify.
• Contact via LinkedIn or email.
• No mention of dynamic forms or server-side logic.
Main components
a. Client (Web Browser)
b. DNS / Custom Domain Registrar
c. CDN / Edge Network (Netlify)
d. Origin Storage (GitHub repository → Netlify build artifacts)
e. Static Assets
• HTML, CSS, JS
• Documents (resume.pdf)
f. External Links & Services
• LinkedIn, Mailto link
Relationships & interactions
• Browser → DNS: resolve custom domain to Netlify edge.
• Browser → CDN edge: request index.html and static assets.
• CDN edge → Origin (if cache miss): fetch latest build from Netlify storage.
• Browser loads assets, renders portfolio, and clicking links redirects to external services (LinkedIn, mailto).
Important architectural patterns & principles
• Static site hosting with continuous deployment (Git push triggers Netlify build).
• CDN caching for global performance.
• Single-page or multi-page static model—no runtime server.
• Separation of assets into dedicated folders for maintainability.
Relevant technologies & frameworks
• HTML5 / CSS3 / vanilla JS
• Netlify (build, deploy, CDN)
• GitHub (source control)
• DNS provider / custom domain
• Optional: Netlify Status badge