How codebyunique/unique-portfolio works
Project type and purpose
• This is a static, single-page (plus a few sub-pages) personal portfolio website.
• Purpose: showcase skills, education, certificates, projects, and provide a contact form for visitors.
File structure
• Top‐level:
• index.html – landing page
• src/pages/… – additional HTML pages (skills, education, certificates, projects, contact)
• src/style/style.css – global stylesheet
• src/script/script.js – client-side behavior (e.g. mobile menu, form submission)
• assets/… – static assets (images, favicons, PDF resume)
• README.md, LICENSE, netlify configuration implied by deploy on Netlify
• No server-side code: it’s purely frontend hosted as static files.
• The contact form is integrated with Formspree (an external API).
Points from README
• Fully responsive, minimal UI.
• Tech stack: HTML5, CSS3, Boxicons/FontAwesome, Netlify for hosting.
• Contact form uses Formspree.
Main components
a. User’s Browser (Client)
b. Static-File Hosting (Netlify CDN)
c. Static Assets Repository (images, CSS, JS, HTML)
d. External Services
– Formspree API (form submissions)
Relationships and data flows
• User → HTTP GET → Netlify CDN → serves HTML/CSS/JS/assets → Browser renders pages.
• Browser → CSS/JS → CDN fetch static assets.
• Browser (JS) → HTTPS POST → Formspree endpoint → external service processes/submits email.
Architectural patterns & design principles
• “Jamstack” style: JavaScript, APIs, and Markup pre‐built.
• Decoupled frontend; no backend code in repo.
• CDN for performance; external APIs for dynamic features (form).
Diagramming recommendations
• Rectangle labeled “User’s Browser”
• Hosting/CDN in another,
• External services in a third.
• Related elements in shaded containers:
• “Static Layer” (Netlify + Assets)
Additional details
• If desired, show how the resume PDF is served (direct link from assets).