How suhasbangale/portfolio2 works
Project Type and Purpose
• This is a simple static portfolio website.
• There is no dynamic backend or database—everything is served as static assets.
Main Components
a. Client (Web Browser)
b. Web Server or CDN (serving static files)
c. Static Assets:
• index.html (entry point)
• CSS directory (css/buttons.css, css/common.css)
• Docs directory (docs/Resume_Suhas_Bangale.pdf)
Relationships and Data Flow
• Browser sends an HTTP GET for index.html.
• Server responds with index.html.
• Server (or CDN) returns each static asset.
Architectural Patterns and Design Principles
• Single‐Page Static Site Architecture
• Asset Organization by type (CSS, images, docs)
• Leveraging browser caching for static assets
• (Optional) Edge CDN layer for high availability and low latency
Technologies and Frameworks
• HTML5 (index.html)
• CSS3 (buttons.css, common.css)
• Static file server (e.g., Nginx, GitHub Pages) or CDN
• PDF viewer in-browser for the resume document
Detail
• Even in a simple static site, capturing each asset request path helps diagnose performance or 404 issues.
• Grouping of CSS vs. image vs. document assets to clarify folder structure.