TrainWithShubham · LondheShubham153 · Jan 23, 2026 · Jan 23, 2026
diff --git a/.gitignore b/.gitignore
@@ -0,0 +1,41 @@
+# OS
+.DS_Store
+Thumbs.db
+
+# Logs
+*.log
+*.pid
+
+# Environment
+.env
+.env.*
+
+# Python
+__pycache__/
+*.pyc
+.venv/
+
+# Node
+node_modules/
+
+# Build
+build/
+dist/
+
+# Terraform
+.terraform/
+*.tfstate
+*.tfstate.*
+crash.log
+
+# Kubernetes
+.kube/
+
+# IDE
+.vscode/
+.idea/
+
+# Caches
+.cache/
+.pytest_cache/
+coverage/
diff --git a/2026/day-01/README.md b/2026/day-01/README.md
@@ -0,0 +1,99 @@
+# Day 01 – Introduction to DevOps and Cloud
+
+## Task
+Today’s goal is to **set the foundation for your DevOps journey**.
+
+You will create a **90-day personal DevOps learning plan** that clearly defines:
+- What is your understanding of DevOps and Cloud Engineering?
+- Why you are starting learning DevOps & Cloud?
+- Where do you want to reach?
+- How you will stay consistent every single day?
+
+This is not a generic plan.  
+This is your **career execution blueprint** for the next 90 days.
+
+---
+
+## Expected Output
+By the end of today, you should have:
+
+- A markdown file named:  
+  `learning-plan.md`
+
+or
+
+- A hand written plan for the next 90 Days (Recommended)
+
+
+The file/note should clearly reflect your intent, discipline, and seriousness toward becoming a DevOps engineer.
+
+---
+
+## Guidelines
+Follow these rules while creating your plan:
+
+- Mention your **current level**  
+  (student / fresher / working professional / non-IT background, etc.)
+- Define **3 clear goals** for the next 90 days  
+  (example: deploy a production-grade application on Kubernetes)
+- Define **3 core DevOps skills** you want to build  
+  (example: Linux troubleshooting, CI/CD pipelines, Kubernetes debugging)
+- Allocate a **weekly time budget**  
+  (example: 2–2.5 hours per day on weekdays, 4-6 hours weekends)
+- Keep the document **under 1 page**
+- Be honest and realistic; consistency matters more than perfection
+
+---
+
+## Resources
+You may refer to:
+
+- TrainWithShubham [course curriculum](https://english.trainwithshubham.com/JOSH_BATCH_10_Syllabus_v1.pdf)
+- TrainWithShubham DevOps [roadmap](https://docs.google.com/spreadsheets/d/1eE-NhZQFr545LkP4QNhTgXcZTtkMFeEPNyVXAflXia0/edit?gid=2073716385#gid=2073716385)
+- Your own past experience and career aspirations
+
+Avoid over-researching today. The focus is **clarity**, not depth.
+
+---
+
+## Why This Matters for DevOps
+DevOps engineers succeed not just because of tools, but because of:
+
+- Discipline
+- Ownership
+- Long-term thinking
+- Ability to execute consistently
+
+In real jobs, no one tells you exactly what to do every day.  
+This task trains you to **take ownership of your own growth**, just like a real DevOps engineer.
+
+A clear plan:
+- Reduces confusion
+- Prevents burnout
+- Keeps you focused during tough days
+
+---
+
+## Submission
+1. Fork this `90DaysOfDevOps` repository  
+2. Navigate to the `2026/day-01/` folder  
+3. Add your `learning-plan.md` file  
+4. Commit and push your changes to your fork  
+
+---
+
+## Learn in Public
+Share your Day 01 progress on LinkedIn:
+
+- Post 2–3 lines on why you’re starting **#90DaysOfDevOps**
+- Share one goal from your learning plan
+- Optional: screenshot of your markdown file or a professional picture
+
+Use hashtags:
+#90DaysOfDevOps
+#DevOpsKaJosh
+#TrainWithShubham
+
+
+Happy Learning  
+**TrainWithShubham**
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,125 +1,18 @@
 # Contributing Guidelines
 
-Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
-documentation, we greatly value feedback and contributions from our community.
+Thank you for contributing to #90DaysOfDevOps.
 
-Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
-information to effectively respond to your bug report or contribution.
+## Quick Start
+- Fork the repository and create a branch.
+- Complete the task in the correct `2026/day-XX` folder.
+- Commit with a clear message (example: `day-14: git fundamentals notes`).
 
-## Reporting Bugs, Features, and Enhancements
 
-We welcome you to use the GitHub issue tracker to report bugs or suggest features and enhancements.
+## Pull Request Checklist
+- Only update the day(s) you worked on.
+- Ensure filenames match the Expected Output exactly.
+- Keep content concise and practical.
+- No emojis in README files.
 
-When filing an issue, please check existing open, or recently closed, issues to make sure someone else hasn't already
-reported the issue.
-
-Please try to include as much information as you can. Details like these are incredibly useful:
-
-* A reproducible test case or series of steps.
-* Any modifications you've made relevant to the bug.
-* Anything unusual about your environment or deployment.
-
-## Contributing via Pull Requests
-
-Contributions via pull requests are appreciated. Before sending us a pull request, please ensure that:
-
-1. You [open a discussion](https://github.com/MichaelCade/90DaysOfDevOps/discussions) to discuss any significant work with the maintainer(s).
-2. You open an issue and link your pull request to the issue for context.
-3. You are working against the latest source on the `main` branch.
-4. You check existing open, and recently merged, pull requests to make sure someone else hasn't already addressed the problem.
-
-To send us a pull request, please:
-
-1. Fork the repository.
-2. Modify the source; please focus on the **specific** change you are contributing.
-3. Ensure local tests pass.
-4. Updated the documentation, if required.
-4. Commit to your fork [using a clear commit messages](http://chris.beams.io/posts/git-commit/). We ask you to please use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).
-5. Send us a pull request, answering any default questions in the pull request.
-6. Pay attention to any automated failures reported in the pull request, and stay involved in the conversation.
-
-GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
-[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
-
-### Contributor Flow
-
-This is a rough outline of what a contributor's workflow looks like:
-
-- Create a topic branch from where you want to base your work.
-- Make commits of logical units.
-- Make sure your commit messages are [in the proper format](http://chris.beams.io/posts/git-commit/).
-- Push your changes to a topic branch in your fork of the repository.
-- Submit a pull request.
-
-Example:
-
-``` shell
-git remote add upstream https://github.com/vmware-samples/packer-examples-for-vsphere.git
-git checkout -b my-new-feature main
-git commit -s -a
-git push origin my-new-feature
-```
-
-### Staying In Sync With Upstream
-
-When your branch gets out of sync with the  90DaysOfDevOps/main branch, use the following to update:
-
-``` shell
-git checkout my-new-feature
-git fetch -a
-git pull --rebase upstream main
-git push --force-with-lease origin my-new-feature
-```
-
-### Updating Pull Requests
-
-If your pull request fails to pass or needs changes based on code review, you'll most likely want to squash these changes into
-existing commits.
-
-If your pull request contains a single commit or your changes are related to the most recent commit, you can simply amend the commit.
-
-``` shell
-git add .
-git commit --amend
-git push --force-with-lease origin my-new-feature
-```
-
-If you need to squash changes into an earlier commit, you can use:
-
-``` shell
-git add .
-git commit --fixup <commit>
-git rebase -i --autosquash main
-git push --force-with-lease origin my-new-feature
-```
-
-Be sure to add a comment to the pull request indicating your new changes are ready to review, as GitHub does not generate a notification when you `git push`.
-
-### Formatting Commit Messages
-
-We follow the conventions on [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/).
-
-Be sure to include any related GitHub issue references in the commit message.
-
-See [GFM syntax](https://guides.github.com/features/mastering-markdown/#GitHub-flavored-markdown) for referencing issues and commits.
-
-## Reporting Bugs and Creating Issues
-
-When opening a new issue, try to roughly follow the commit message format conventions above.
-
-## Finding Contributions to Work On
-
-Looking at the existing issues is a great way to find something to contribute on. If you have an idea you'd like to discuss, [open a discussion](https://github.com/MichaelCade/90DaysOfDevOps/discussions).
-
-## License
-
-Shield: [![CC BY-NC-SA 4.0][cc-by-nc-sa-shield]][cc-by-nc-sa]
-
-This work is licensed under a
-[Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License][cc-by-nc-sa].
-
-[![CC BY-NC-SA 4.0][cc-by-nc-sa-image]][cc-by-nc-sa]
-
-[cc-by-nc-sa]: http://creativecommons.org/licenses/by-nc-sa/4.0/
-[cc-by-nc-sa-image]: https://licensebuttons.net/l/by-nc-sa/4.0/88x31.png
-[cc-by-nc-sa-shield]: https://img.shields.io/badge/License-CC%20BY--NC--SA%204.0-lightgrey.svg
+## Code of Conduct
+Be respectful, supportive, and helpful to others in the community.
diff --git a/LICENSE b/LICENSE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 TrainWithShubham
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/README.md b/README.md
@@ -1,66 +1,15 @@
-# #90DaysOfDevOps Challenge
+# #90DaysOfDevOps 2026
 
-## Learn, Upskill, Grow with the Community
+Welcome to TrainWithShubham's #90DaysOfDevOps challenge. This repository contains the 2026 day-by-day tasks, aligned to the live class schedule and designed for daily practice.
 
-Join our DevOps community challenge and embark on a 90-day journey to become a better DevOps practitioner. This repository serves as an open invitation to all DevOps enthusiasts who are looking to enhance their skills and knowledge. By participating in this challenge, you will have the opportunity to learn from others in the community, collaborate with like-minded individuals, and ultimately strengthen your DevOps abilities.
+## How to Participate
+- Fork the repository.
+- Complete one day at a time in `2026/day-XX`.
+- Commit your deliverable in the day folder.
+- Open a pull request with your updates.
 
-Let's come together to grow and achieve new heights in DevOps!
+## Schedule Note
+Day 01 starts on 2026-01-24 (Asia/Kolkata). Live class days contain the main challenge for the topic. Non-live days focus on practice and reinforcement.
 
-📖 **Discover More in Our Detailed Table of Contents!** Explore the richness of our content and find what you're looking for efficiently. Check out our [TOC here](./TOC.md).
-
-## Steps:
-
-- Fork[https://github.com/LondheShubham153/90DaysOfDevOps/fork] the Repo.
-- Learn Everyday and add your learnings in the day wise folders.
-- Check out what others are Learning and help/learn from them.
-- Showcase your learnings on LinkedIn
-
-## These are our community Links
-  <a href="https://discord.com/channels/824622549182185493/824622550327623692">
-    <img width="30px" src="https://www.vectorlogo.zone/logos/discordapp/discordapp-tile.svg" />
-  </a>&ensp;
-    <a href="https://t.me/trainwithshubham">
-    <img width="30px" src="https://www.vectorlogo.zone/logos/telegram/telegram-icon.svg" />
-  </a> 
-  </a>&ensp;
-
-  <a href="https://www.linkedin.com/in/shubhamlondhe1996/">
-    <img width="30px" src="https://www.vectorlogo.zone/logos/linkedin/linkedin-icon.svg" />
-  </a>&ensp;
-
- <a href="https://www.youtube.com/@TrainWithShubham">
-  <img width="30px" src="https://i.pinimg.com/originals/46/02/cb/4602cbc18967da9c1eba7452905cd99b.png" />
-  </a>&ensp;
-
-  <a href="https://chat.whatsapp.com/FvRlAAZVxUhCUSZ0Y1s7KY">
-  <img width="30px" src="https://www.vectorlogo.zone/logos/whatsapp/whatsapp-icon.svg" />
-</a>&ensp;
-
-
-<a href="https://www.trainwithshubham.com/">
-  <img width="30px" src="https://media.licdn.com/dms/image/C4D0BAQGokBZsFEUWHw/company-logo_200_200/0/1677354328695?e=1700092800&v=beta&t=3bw7W2tQEpn023Slj_PacUZflE-OyYpBU-9juiJNJVY" />
-</a>&ensp;
-
-## Events
-
-### YouTube Live Announcement:
-<a href="https://youtu.be/rO5Rllir-LM">
-  <img width="30px" src="https://i.pinimg.com/originals/46/02/cb/4602cbc18967da9c1eba7452905cd99b.png" />
-  </a>&ensp;
-
-### YouTube Playlist for DevOps:
-<a href="https://youtube.com/playlist?list=PLlfy9GnSVerRqYJgVYO0UiExj5byjrW8u
-">
-  <img width="30px" src="https://i.pinimg.com/originals/46/02/cb/4602cbc18967da9c1eba7452905cd99b.png" />
-  </a>&ensp;
-
-### DevOps Course:
-<a href="https://bit.ly/devops-batch-7">
-  <img width="30px" src="https://media.licdn.com/dms/image/C4D0BAQGokBZsFEUWHw/company-logo_200_200/0/1677354328695?e=1700092800&v=beta&t=3bw7W2tQEpn023Slj_PacUZflE-OyYpBU-9juiJNJVY" />
-</a>&ensp;
-
-## Thanks to all contributors ❤
-
- <a href = "https://github.com/LondheShubham153/90DaysOfDevOps/graphs/contributors">
-   <img src = "https://contrib.rocks/image?repo=LondheShubham153/90DaysOfDevOps"/>
- </a>
+## Start Here
+Go to `2026/day-01/README.md` and follow the task.
diff --git a/scripts/generate_days.py b/scripts/generate_days.py
@@ -0,0 +1,16 @@
+from pathlib import Path
+
+root = Path(__file__).resolve().parents[1]
+base = root / "2026"
+base.mkdir(parents=True, exist_ok=True)
+
+total_days = 90
+
+# Generate folders and ensure README.md exists without overwriting.
+for i in range(total_days):
+    day_num = i + 1
+    day_dir = base / f"day-{day_num:02d}"
+    day_dir.mkdir(parents=True, exist_ok=True)
+    readme = day_dir / "README.md"
+    if not readme.exists():
+        readme.write_text("")