How meeki34/mywebsite works
Project type and purpose
• This is a simple, static portfolio website (“mywebsite”) consisting only of index.html and style.css.
• Purpose: serve personal portfolio content (bio, projects, contact) as static assets.
File structure
• Top-level files:
• index.html – the sole HTML entry point
• style.css – global styling sheet
• No backend code, no build scripts, no database directories.
README
• Confirms that this is “a portfolio website.”
• No further architectural details, dependencies, or runtime requirements.
Main components
a. Client (Web Browser)
– Renders HTML/CSS, displays portfolio UI.
b. Hosting Infrastructure (Web Server / Static-site host)
– Could be GitHub Pages, AWS S3 + CloudFront, Netlify, etc.
– Serves index.html and style.css over HTTP(S).
c. DNS / CDN (optional)
– Maps domain (e.g., mywebsite.com) to hosting endpoint, caches assets at edge.
d. (Optional) Third-party services
– Analytics (e.g., Google Analytics)
– Contact form backend (e.g., Formspree or serverless function)
– Social media embed APIs
Relationships and interactions
• Browser → DNS/CDN: resolve domain, retrieve cached record
• Browser ↔ CDN: fetch index.html, style.css
• CDN ↔ Origin Host: on cache miss, retrieve from S3/GitHub repo
• Browser → Third-party services: send pageview data or form submissions
Architectural patterns and design principles
• Client-server model (request static files over HTTP)
• Edge caching (CDN) to reduce latency
• Single-Page Resource: only one HTML file, no client-side routing
• Separation of concerns: structure (HTML) vs. presentation (CSS)