DevOps MOC (Map of Content) organization¶
A DevOps Map of Content (MOC) serves as a central entry point or index that aggregates various technical notes, resources, and tools into a structured hierarchy^[400-devops-000-moc-devops.md]. This organizational method allows for the navigation of complex topics ranging from operating system basics to CI/CD pipelines and containerization.
Structure¶
The DevOps MOC is typically organized by categorizing knowledge into specific domains or tiers, such as:
- OS and Linux Basics: Foundational knowledge including networking tools like ngrok and domain management^[400-devops-000-moc-devops.md].
- Containerization: Resources covering container technologies and alternatives, such as vscode-devcontainer for environment setup and podman as a Docker alternative^[400-devops-000-moc-devops.md].
- CI/CD Pipelines: Sections dedicated to automation workflows, including [[GitHub]] and cloud-based development environments like gitpod^[400-devops-000-moc-devops.md].
Usage¶
The MOC acts as a high-level roadmap, often visualized as a "DevOps Engineer" roadmap or "DevOps Bootcamp" structure^[400-devops-000-moc-devops.md]. It provides links to external resources, such as PDF roadmaps and video tutorials on learning technologies, as well as internal links to specific implementation notes^[400-devops-000-moc-devops.md].
Related Concepts¶
- [[Map of Content]]
- [[Hub pages]]
- Link pages and hub pages
Sources¶
- 400-devops-000-moc-devops.md