How samiya-ait/portfolio works
Project type & purpose (from file tree + README)
This repository is a static portfolio website (likely a personal site) consisting of:
• index.html → the single page (or primary entry point) of the portfolio
• style.css → styling for the page
• cv.pdf + projets/*.pdf → downloadable documents (CV and project PDFs)
• No backend code, no build system, no package manager, no server-side runtime indicated.
The README contains only “portfolio”, reinforcing that this is a simple static site.
End User / Browser
• Renders HTML/CSS
• Requests assets via HTTP(S)
• Opens/Downloads PDFs
Static Hosting / Web Server
• Serves index.html, style.css, and PDF files
• Examples (not in repo, but typical): GitHub Pages, Netlify, Vercel static, S3+CloudFront, Nginx/Apache
Static Assets (the repo contents)
• index.html (UI structure + links)
• style.css (presentation)
• cv.pdf (document asset)
• projets/formation.pdf, projets/restaurant.pdf (project document assets)
(Optional but common) DNS + TLS
• DNS resolves domain to hosting
• TLS certificate for HTTPS
Initial page load
• Browser → Static Host: GET /index.html
• Host → Browser: HTML response
Loading styles
• Browser → Static Host: GET /style.css
• Host → Browser: CSS response
Opening/downloading PDFs
• Browser → Static Host: GET /cv.pdf
• Browser → Static Host: GET /projets/formation.pdf (and others)
• Host → Browser: PDF response
Architectural pattern to highlight (what this “system” is)
This is a classic static site architecture:
• Client-side rendering (HTML/CSS only; no SPA framework indicated)
• Content served as static files
• No compute layer beyond a file server/CDN
• Static origin (where files live)
• CDN/Edge cache (optional but very common)
Because the system is small, use 2 levels so it’s still “detailed”:
Focus: who uses it and what it depends on.
• Actor: “Visitor”
• System: “Portfolio Website (Static)”
• External dependencies (optional): “DNS”, “Static Hosting Provider”
Focus: runtime containers and responsibilities.
• “Browser (Client)” container
• “Static Hosting / CDN” container
• “Static Files” container (or annotate within hosting)
• index.html
• style.css
• PDFs
• HTML page
• CSS stylesheet
• Document assets (CV + project PDFs)
This is unusual for large systems, but for this repo it’s the cleanest way to “separate into as many components as possible” without inventing services.
• User (Visitor)
→ uses →
• Web Browser
→ HTTP(S) →
• Static Hosting (origin and/or CDN)
→ serves →
• index.html
→ references →
• style.css
• cv.pdf
• projets/formation.pdf
• projets/restaurant.pdf
Optionally include:
• DNS (Browser queries DNS before HTTP)
• TLS certificate (HTTPS termination at hosting/CDN)
What NOT to include (to keep it accurate)
• Backend services, APIs, databases, queues
• CI/CD pipelines unless you have evidence (no workflow files shown)
• Analytics/third-party scripts unless present in index.html (not provided here)
• Left: User + Browser
• Center: CDN/Static Host
• Right/below: the asset set (HTML/CSS/PDFs)
This will be the most accurate and sufficiently detailed representation of the system implied by the repository.