How izuan87/portfolio works
Project type and purpose
• This is a simple, static portfolio website (“portfolia website”), composed entirely of HTML, CSS, and image assets.
• There is no backend application logic or database—just a set of pages served as static assets.
File structure
• Top-level HTML pages: index.html, certification.html, contact.html, portfolio.html, property-agent.html.
• A global stylesheet: style.css.
• A directory of media assets: /images.
• No server-side code, build scripts or configuration files—this folder structure lives as static content on a web server or CDN.
README
• Confirms that the project is a portfolio website.
• No extra details on hosting or toolchain, implying this is hand-crafted static content.
a. Main components
• Client (browser)
• Static-file hosting (e.g., web server or CDN)
• Content storage (the HTML/CSS/images in your file tree)
• (Optional) DNS service / custom domain
• (Optional) Third-party services (analytics, contact form endpoint)
b. Relationships and interactions
• Browser issues HTTP GET requests for each page (e.g., GET /index.html).
• Web server (or CDN) responds with the appropriate static files.
• Browser parses HTML, CSS and fetches image assets from /images.
c. Architectural patterns or design principles
• Single-Tier “static” architecture (no application tier).
• Separation of concerns: content (HTML), presentation (CSS), assets (images).
• Optionally, use a CDN in front of the origin server to cache and distribute assets globally.
d. Relevant technologies and frameworks
• HTML5 for markup
• CSS3 for styling
• HTTP/HTTPS for transport
• Static hosting platforms (GitHub Pages, Netlify, S3+CloudFront, etc.)
• Optional: DNS provider, SSL certificate manager, analytics endpoint
Detail
• Distinguish static-asset retrieval (CSS, images) from page HTML retrieval.