How ksoliven/mywebsite works
Project Type and Purpose
• This is a static, front-end portfolio website built with HTML5, CSS3 (Sass/Bootstrap), JavaScript and jQuery.
• It’s intended to showcase work and load client-side assets only—no custom backend.
Main Components (to include)
A. Developer & Build
• Version Control (e.g. GitHub repo)
• Local Build Tool (Sass compiler, bundler/minifier)
• CI/CD or Manual Deploy Step
B. Hosting Environment
• Static File Host (e.g. GitHub Pages, Netlify or similar)
• CDN Layer (optional, for CSS/JS/Images)
C. Browser Runtime
• Browser Engine loading:
– index.html
– Compiled CSS (Bootstrap + custom styles)
– Bundled JavaScript
• Client-side UI rendering & user interactions
• Google Map embed & other dynamic widgets
D. External Services
• Google Maps API
• (If used) Analytics or Form-submission endpoint (e.g. Formspree, Google Analytics)
Relationships & Data Flow
1. Developer & Build → Hosting Environment
• Push code to repo
• Build tool compiles Sass → CSS, bundles/minifies JS → static assets
• CI/CD or manual deploy publishes assets to static host
2. Browser Runtime ← Hosting Environment
• User’s browser requests index.html and assets (CSS/JS/images/fonts) from the host or CDN
3. Browser Runtime ↔ External Services
• JavaScript makes API calls (e.g. loads Google Maps scripts/data)
• Assets such as map tiles or analytics events flow between browser and external endpoints
Architectural Patterns & Principles
• Single-Page or Multi-Page Static Site: separation of concerns between markup, styles, and scripts
• Build-time asset pipeline: compile-and-deploy model rather than runtime server logic
• CDN or caching layer for static content delivery