How nijika21/portfolio-web works
Project type and purpose
• This is a static, front-end portfolio website built with plain HTML, CSS, and JavaScript and hosted on GitHub Pages. Its purpose is to showcase the developer’s profile, projects, and contact information, including a small gallery of 3D models.
File structure
• Top-level files:
• README.md – project description and usage
• index.html – entry point
• style.css, style.js – styling and behavior
• assets/ directory:
• 3D model files (GLB) and preview image(s)
• No backend code or server framework—pure static content.
README for additional insights
• Confirms responsive design for desktop/mobile
• Describes sections: profile, project gallery, contact
• Technology stack: HTML5, CSS3, JavaScript, GitHub Pages hosting
Diagramming the architecture
a. Main components
• Client (Browser)
• Static Hosting Service (GitHub Pages CDN)
• Static assets:
• index.html
• style.css
• style.js
• 3D models (GLB) and images
b. Relationships and interactions
• Browser sends HTTP GET to GitHub Pages URL
• Hosting service responds with HTML, CSS, JS, and asset files
• Browser renders HTML, applies CSS, runs JS, fetches 3D models and images dynamically
c. Architectural patterns / design principles
• Single-Page (or multi-section) static site
• Separation of concerns: markup, styling, scripting, and media assets in distinct files/directories
d. Key technologies
• HTML5 for structure
• CSS3 for responsive layout
• Vanilla JavaScript for dynamic behavior (e.g., loading 3D models)
• GitHub Pages as the static site host / CDN
Elements
• Clear rectangular nodes for: Browser, GitHub Pages CDN, and “Assets Storage”
• Blue for code files (HTML/CSS/JS)
• Green for media assets (GLB, images)
• Orange for hosting/infrastructure
Detailed breakdown to capture essential elements
• Responsive design step (CSS media query block) to show mobile vs. desktop styling