How forestcrazy/myportfoliowebsite works
Project type and purpose
• This is a simple, static “personal portfolio” website.
• It consists entirely of HTML pages (index.html, about.html, contact.html, skills.html), a CSS/SCSS stylesheet, an image folder, and no server-side code or database.
File structure
• Top-level HTML files represent separate pages.
• index.scss is the source for index.css (build step: SCSS → CSS).
• img/ holds static assets.
• No “src/” or “backend/” directories—this is a purely frontend, static-site architecture.
Extract insights from the README
• “Lightweight, customizable personal portfolio website.”
• No mention of dynamic content, authentication, or API integrations.
Main components
a. Developer Workstation
• SCSS compiler (e.g., node-sass, dart-sass) or build tool (optional).
b. Build Pipeline (optional)
• SCSS → CSS step.
c. Version Control
• Git repository.
d. Static Hosting / CDN
• e.g., GitHub Pages, Netlify, Vercel, S3 + CloudFront.
e. Browser (end user)
Relationships and data flows
• Developer writes HTML/SCSS → commits to Git.
• Build step transforms index.scss → index.css.
• Hosting provider pulls from Git → serves files to CDN or origin.
• Browser requests HTML, CSS, images → hosting/CDN responds with static files.
Architectural patterns and design principles
• Static site architecture (no backend).
• Build-time preprocessing (SCSS compilation).
• CDN for global content distribution and caching.
• Separation of concerns:
• Content (HTML)
• Presentation (CSS)
• Media (img/)
Technologies/frameworks in use
• HTML5
• SCSS → CSS compiler (e.g., node-sass)
• Static hosting/CDN (e.g., GitHub Pages, Netlify)