DevOps rollout

Pipeline in motion

Progressing through each release checkpoint

Initialize Cloud Infra

Spinning VPCs, subnets, and base services

Running

Prime Delivery Pipeline

CI runners warm, caches hydrated

Queued

Secure Artifacts

Images signed, SBOMs verified

Queued

Deploy Portfolio

Rolling out containers with health gates

Queued

Stabilize Observability

Dashboards green, alerts quiet

Queued
0% complete
Back to projects

DevOps Portfolio Website

Personal portfolio showcasing DevOps and backend engineering projects.

Problem

  • I needed a single place to present real DevOps/backend work without it getting buried in random repos and notes.
  • Most portfolios over-index on frontend polish and under-explain engineering decisions.

Solution

  • Built a portfolio that reads like a case-study library: projects, decisions, and outcomes.
  • Focused the content on CI/CD, infrastructure automation, and backend systems.

Deployment

  • Shipped as a containerized app and deployed on my personal NAS.

Decisions & tradeoffs

  • Prioritized clarity and technical storytelling over flashy UI.
  • Kept the structure reusable so new projects can be added without redesigning pages.

Project Info

Type: Portfolio WebsiteRole: SoftwareStatus: Personal

Key Outcomes

Next.js + TypeScript
Recruiter-first layout
Containerized deploy
Self-hosted on NAS

Tech Stack

Next.jsTypeScriptReact
GitHubLinkedin
© 2026 Maad Mustafa

Running systems, not just code.