How akiffazal/my-portfolio-website works
Project type and purpose
• This is a static portfolio website, built purely with HTML, CSS, and JavaScript.
• No dynamic backend or database; assets include a PDF resume and site styling/behavior files.
• CI/CD pipeline via GitHub Actions (static.yml) likely deploys to a static-hosting service (e.g., GitHub Pages, Netlify).
File structure
• Top-level:
• .github/workflows/static.yml → continuous integration/deployment config
• index.html → entry point
• CSS files (style.css, hamburger.css, mobile-menu.css, profile-adjust.css) → styling concerns
• JS files (script.js, mobile-menu.js, profile-adjust.js) → interactive behavior
• assets/ → static assets (resume PDF)
• No server or API directories—this is purely front-end.
README
• Very brief: just the project title. No additional architecture notes, so we infer common static-site CI/CD.
Required elements
• Clear labels: e.g., “User Browser,” “Static Host,” “GitHub Repo,” “CI/CD.”
– Code push → CI/CD
– CI/CD → Deploy to Host
– Browser → Host → fetch files
– Another for hosting infrastructure
– A third for the client