How mohamedmedhatnabil/simone-portofolio works
Project type and purpose
• This is a simple, static portfolio website built with HTML, CSS and images.
• The presence of GitHub Actions workflows named “jekyll-dockjer.yml” and “jekyll-gh-pages.yml” indicates that you’re using GitHub Pages (with Jekyll) as a static site generator and deployment platform.
• Purpose: Serve a personal portfolio (index.html, assets under css/ and img/) via GitHub Pages.
File structure
• Top level:
• .github/workflows/ – CI/CD definitions
• index.html – entry point
• css/ – styling
• img/ – static media assets
• README.md – project description/link
• No backend or dynamic code; it’s purely static.
• Workflows:
• jekyll-gh-pages.yml – builds with Jekyll, pushes to gh-pages branch
• jekyll-dockjer.yml – likely a Docker-based build step
• stathic.yml & static.yml – alternative static-site deploys
README for additional insights
• Only contains the published site URL.
Elements
• Code → push → Repo
• Repo → triggers → CI/CD
• CI/CD → builds → Static Artifacts
• CI/CD → deploys → GitHub Pages
• User Browser → HTTP request → GitHub Pages → static assets
• Blue for code/Repo
• Green for CI/CD and build
• Orange for hosting/CDN
• Yellow for end user
• Rectangles for processes (build, deploy)
• Clouds for external services (GitHub Pages)
Detailed but not over-engineered
• Even though it’s a modest static site, capture all seven steps (dev → push → CI → build → deploy → host → serve).