How himavincent/my-portfolio works
Project type and purpose
• This is a simple, static portfolio website built with HTML, SCSS/CSS and minimal JavaScript.
• Its primary purpose is to serve personal branding content (resume PDF, work samples) to visitors.
File structure
• Top-level files:
• README.md – project description
• index.html – single entry-point HTML file
• style.css + style.css.map – compiled stylesheet and source-map
• Directories:
• assets/ – static assets (e.g., PDF resume)
• scss/ – Sass partials and main .scss (global, mixins, variables, normalize, media-queries)
• No backend, serverless/design: all files are served statically.
README for additional insights
• Confirms it is a “starter project” showcasing core frontend skills.
• No build tool or JS framework noted, so assume a simple Sass compilation step (e.g. sass scss:./).
Main components
a. Client (Browser)
b. Static Hosting Server / CDN
c. Build Process (Sass compiler) – development step only
d. Static Assets – HTML, CSS, source maps, resume PDF, images (if any)
Relationships and interactions
• Developer runs Sass compiler → outputs style.css + style.css.map
• Deployment: upload index.html, style.css, assets to static host (GitHub Pages, Netlify, etc.)
• Browser requests index.html → then fetches style.css and assets as linked resources
Architectural patterns / design principles
• No dynamic logic – purely static, lean front end
• SCSS partialization (variables, mixins, normalize) for maintainability and DRY styles
• Source maps for debugging in development
Technologies / frameworks
• HTML5
• Sass/SCSS
• (Optional) Static hosting service (GitHub Pages, Netlify, Vercel)
• (Optional) Sass CLI or Node-based build tool (e.g. npm scripts)
Additional detail to capture
• If using a specific hosting platform, note that’s where HTTPS, caching, and CDN live