Learning Paths
These paths turn the 54-project catalog into sequenced routes. Each path is intentionally short enough to finish, but broad enough to build a portfolio story.
| Path | Best for | Outcome |
|---|---|---|
| Beginner | New students | Linux, basic cloud app delivery, first CI/CD, and a local security demo |
| Docker/Kubernetes | Container and cluster practice | Docker packaging, Kubernetes manifests, GitOps, microservices, and progressive delivery |
| Terraform/IaC | Infrastructure builders | VPCs, EKS, ECS, serverless, OpenTofu, and validation-first infrastructure work |
| CI/CD | Delivery engineers | GitHub Actions, Jenkins, GitLab CI, Azure DevOps, AWS CodePipeline, and promotion workflows |
| DevSecOps | Security-minded builders | SAST, container scanning, secrets hygiene, SBOMs, signing, and secure pipeline design |
| AWS | Cloud portfolio work | AWS networking, containers, EKS, ECS, serverless, monitoring, and cost-aware cleanup |
| Platform Engineering 2026 | Modern platform narrative | GitOps, observability, supply chain security, OpenTofu, progressive delivery, and flagship EKS |
How to Use a Path
Section titled “How to Use a Path”- Read the path goal and complete the projects in order.
- Use the project picker when you need a substitute with lower cost or different tooling.
- Run the validation command from each
project.yamlbefore deployment. - Keep a lab journal with setup notes, screenshots, failure modes, and cleanup proof.
- End each path by writing one portfolio case study from the strongest project.