How kunal-kushwaha/devops-bootcamp works
Project type and purpose
• This repository is not a typical codebase but an educational “DevOps-Bootcamp” content repository.
• It contains course materials (PDFs, Markdown, YAML examples) for Docker, Kubernetes, Linux/terminal commands, Networking, and YAML.
• The README points learners to YouTube playlists and a hosted course website.
File structure
• Top-level folders each represent a module:
• Docker
• Kubernetes
• Linux and Terminal commands
• Networking
• YAML
• GitHub Actions (presumably CI/CD pipeline definitions or examples)
• There is no compiled code; content consists of Markdown and PDFs.
• No explicit static-site generator configs are checked in, but GitHub Actions folder implies a CI/CD pipeline that could build and deploy the content.
README for additional insights
• README functions as an entry point, driving users to external resources (YouTube, course website).
a. Main components
1. Content Authoring Environment
– Module folders (Docker, Kubernetes, etc.) containing source files (Markdown, PDFs).
2. Version Control & Hosting
– GitHub repository (this repo).
3. CI/CD Pipeline
– GitHub Actions workflows (build, link-check, deploy).
4. Documentation Build
– Static site generator (e.g., Jekyll, Hugo, mkdocs) or a custom script that processes Markdown/PDF.
5. Hosting & Delivery
– GitHub Pages or cloud hosting (S3 + CloudFront) serving the generated site.
6. External Integrations
– YouTube channel for video lectures.
– Official course website (wemakedevs.org).
7. End Users
– Students / Learners accessing the site or PDFs.
b. Relationships and interactions
– Authors push changes → GitHub repo
– GitHub Actions triggers on push/PR → runs build jobs
– Build jobs invoke static-site generator → output HTML/CSS/JS
– Deployment step publishes → GitHub Pages (or cloud bucket + CDN)
– End users browse the site; click out to YouTube or external course links
– Module folders feed directly into the build process
c. Architectural patterns & design principles
– Modular documentation (each folder = a self-contained module)
– CI/CD for documentation (automated build & deploy)
– Static-site serving for scalability, low maintenance
– Clear separation of concerns: authoring vs. building vs. hosting
d. Relevant technologies
– Git / GitHub
– GitHub Actions (CI/CD)
– Markdown, PDF assets
– Static-site generator (e.g., Jekyll/Hugo/mkdocs)
– Hosting: GitHub Pages or cloud storage + CDN
– External services: YouTube, wemakedevs.org