How gedam12/portfolio works
Project type and purpose
• This is a simple, single‐page static website (no backend code, frameworks, or build scripts).
• Key files: index.html (entry point), stylesheet.css (styles), main.js (client‐side behavior), img/ (static images).
File structure
• Top‐level assets live alongside your HTML:
– index.html: main document
– main.js: all JavaScript logic (event handlers, DOM updates, any AJAX)
– stylesheet.css: all styling rules
– img/: contains images referenced by HTML or CSS
README
• It’s empty, so no additional architectural hints. We’ll focus on a generic static‐site deployment pattern.
Main components
a. Client (User’s browser)
– Renders index.html, applies stylesheet.css, executes main.js
– May request images from img/
b. Static Asset Server / Hosting Environment
– Serves HTML, CSS, JS, image files over HTTP(S)
– Could be GitHub Pages, Netlify, Amazon S3 + CloudFront, or any simple web server
c. (Optional) External Dependencies
– If main.js loads any 3rd‐party scripts or APIs at runtime, represent those as external services.
Relationships and interactions
• Browser → HTTP GET → Asset Server: requests index.html
• Browser parses HTML → issues HTTP GETs for stylesheet.css, main.js, and any images
• main.js runs in browser → manipulates DOM, may call external APIs over AJAX/Fetch
Architectural patterns & design principles
• Client‐side rendering: all logic runs in the browser.
• Static file hosting: no dynamic backend, no database.
• Separation of concerns: HTML for structure, CSS for presentation, JS for behavior.
Putting it all together
– index.html
– stylesheet.css
– main.js
– img/*
• Protocols (HTTP(S)), caching layers (CDN), or hosting provider.
Detail without overcomplicating
• Every moving part (HTML, CSS, JS, images, hosting, optional APIs).
• Keep it simple: static‐site architecture has only client, server, and optional third‐party services.