How baibhab-adhikari/developer-portfolio works
Project type and purpose
• This is a simple, static portfolio website.
• The README (“My portfolio Website”) and the presence of only HTML, CSS, JS, and static assets indicate there is no backend or database—everything is delivered as static files.
File structure
• Top-level files:
• index.html – entry point and page markup
• style.css – styling for the HTML
• script.js – client-side behavior and interactivity
• assets/ – static assets (Baibhab_Adhikari_Resume.pdf)
• .gitignore – source control exclusions
• README.md – project description
• No server-side code or build scripts are present, confirming it’s a pure front-end project.
README for additional insights
• The README is minimal but confirms the site’s role as a personal portfolio.
• No special build, deployment, or external service integrations are documented.
• Client (Web Browser)
• Web Server / Static Hosting (e.g., GitHub Pages, Netlify, S3+CloudFront)
• Static Files:
– index.html
– style.css
– script.js
– assets/Baibhab_Adhikari_Resume.pdf
b. Relationships and interactions:
• Browser sends HTTP(S) GET requests to the Hosting service
• Hosting service returns static files
• Browser renders HTML, applies CSS, executes JS, enables user interaction (e.g., download resume)
c. Architectural patterns / principles:
• “Jamstack”-style: pre-built static pages + client-side JS
• Separation of concerns:
– Markup (HTML),
– Styling (CSS),
– Behavior (JS),
– Assets (PDF, images)
d. Key technologies:
• HTML5
• CSS3
• Vanilla JavaScript
• Static hosting platform or CDN
Elements
• Clear labels for each component (e.g., “Browser,” “Static File Host,” “index.html,” etc.)
• Browser → Host (requests)
• Host → Browser (responses with .html, .css, .js, assets)
• Rectangles for services (Hosting)