How jovination/myportfolio works
Project type and purpose
• From the file tree and README, this is a simple, static personal portfolio website.
• Purpose: showcase the developer’s work and design skills via a few HTML pages (index.html, about.html, project.html), supported by CSS, JavaScript, and images.
File structure
• Top-level files:
• README.md – personal introduction and link to the live site
• index.html, about.html, project.html – core content pages
• script.js – any interactive behavior or DOM manipulation
• Directories:
• css/ – contains project.css, resp.css, style.css for styling, layout, and responsive rules
• No server-side code or database—purely client-side static assets.
README for additional insights
• No sections on backend, data stores, or third-party services.
• A single “visit” link implies deployment over HTTPS (likely GitHub Pages, Netlify, or similar).
a. Main components
• Client (Web Browser)
• Static Hosting / CDN
• File Storage (HTML, CSS, JS, images)
• (Optional) External integrations (Analytics, Contact form service)
b. Relationships & interactions
• Browser → HTTP GET → Hosting/CDN → serves HTML
• HTML references CSS & JS → Browser fetches CSS & JS → renders pages
• HTML references images → Browser fetches images
• (If included) Browser → Analytics endpoint
c. Architectural patterns & principles
• Static-site architecture: files prebuilt, served from a CDN or static host
• Browser-based rendering: minimal JS, progressive enhancement
• Cache-first delivery from CDN for performance
d. Key technologies
• HTML5 for structure
• CSS3 for styling and responsive layouts (resp.css)
• Vanilla JavaScript (script.js) for interactivity
• Static hosting (GitHub Pages/Netlify) + optional CDN layer
• index.html, about.html, project.html
• css/ (project.css, resp.css, style.css)
• script.js
• images/
• Browser → GET index.html → CDN
• Browser parses HTML → GET CSS → CDN → apply styles
• Browser parses HTML → GET JS → CDN → execute scripts
• Browser parses HTML → GET images → CDN