diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json
index f59c485..6a12bd9 100644
--- a/.devcontainer/devcontainer.json
+++ b/.devcontainer/devcontainer.json
@@ -12,17 +12,24 @@
 
 	// The 'service' property is the name of the service for the container that VS Code should
 	// use. Update this value and .devcontainer/docker-compose.yml to the real service name.
-	"service": "blogs-svc",
+	"service": "tuxtechblog-mkdocs",
 
 	// The optional 'workspaceFolder' property is the path VS Code should open by default when
 	// connected. This is typically a file mount in .devcontainer/docker-compose.yml
-	"workspaceFolder": "/workspaces/${localWorkspaceFolderBasename}"
+	"workspaceFolder": "/workspaces/${localWorkspaceFolderBasename}",
+	"features": {
+		"ghcr.io/devcontainers/features/python:1": {},
+		"ghcr.io/devcontainers-contrib/features/zsh-plugins:0": {},
+		"ghcr.io/wxw-matt/devcontainer-features/command_runner:0": {},
+		"ghcr.io/schlich/devcontainer-features/powerlevel10k:1": {},
+		"ghcr.io/cirolosapio/devcontainers-features/alpine-ohmyzsh:0": {}
+	}
 
 	// Features to add to the dev container. More info: https://containers.dev/features.
 	// "features": {},
 
 	// Use 'forwardPorts' to make a list of ports inside the container available locally.
-	// "forwardPorts": [],
+	"forwardPorts": [8000]
 
 	// Uncomment the next line if you want start specific services in your Docker Compose config.
 	// "runServices": [],
diff --git a/.devcontainer/docker-compose.yml b/.devcontainer/docker-compose.yml
index 283e040..f3cb6d6 100644
--- a/.devcontainer/docker-compose.yml
+++ b/.devcontainer/docker-compose.yml
@@ -1,7 +1,7 @@
-version: '3.9'
+version: '3.8'
 services:
   # Update this to the name of the service you want to work with in your docker-compose.yml file
-  blogs-svc:
+  tuxtechblog-mkdocs:
     # Uncomment if you want to override the service's Dockerfile to one in the .devcontainer 
     # folder. Note that the path of the Dockerfile and context is relative to the *primary* 
     # docker-compose.yml file (the first in the devcontainer.json "dockerComposeFile"
diff --git a/.dockerignore b/.dockerignore
new file mode 100644
index 0000000..0690134
--- /dev/null
+++ b/.dockerignore
@@ -0,0 +1,156 @@
+.env
+.DS_Store
+.env.prod
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintainted in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
\ No newline at end of file
diff --git a/.gitignore b/.gitignore
index 90e164b..3af6d3e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,9 +1,156 @@
-# Ignore Files
-**/*.log
-**/*.pyc
-**/*.env
-
-# Folders
-__pycache__
-logs
-test
\ No newline at end of file
+.env
+.DS_Store
+.env.prod
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintainted in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
\ No newline at end of file
diff --git a/.markdownlintrc b/.markdownlintrc
deleted file mode 100644
index 38208dd..0000000
--- a/.markdownlintrc
+++ /dev/null
@@ -1,9 +0,0 @@
-{
-  "comment": "Copyright (c) 2019-2024 TuxTechLab. 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 NON-INFRINGEMENT. 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",
-  "default": true,
-  "no-trailing-punctuation": false,
-  "line-length": false,
-  "MD003": { "style": "atx"},
-  "MD007": { "indent": 4 },
-  "MD013": false
-}
diff --git a/.vscode/launch.json b/.vscode/launch.json
new file mode 100644
index 0000000..5a105f9
--- /dev/null
+++ b/.vscode/launch.json
@@ -0,0 +1,22 @@
+{
+    // Use IntelliSense to learn about possible attributes.
+    // Hover to view descriptions of existing attributes.
+    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+    "version": "0.2.0",
+    "configurations": [
+        {
+            "name": "Attach to Chrome",
+            "port": 8000,
+            "request": "attach",
+            "type": "chrome",
+            "webRoot": "${workspaceFolder}"
+        },
+        {
+            "type": "chrome",
+            "request": "launch",
+            "name": "Launch Chrome against localhost",
+            "url": "http://localhost:8080",
+            "webRoot": "${workspaceFolder}"
+        }
+    ]
+}
\ No newline at end of file
diff --git a/.vscode/settings.json b/.vscode/settings.json
index d8928ce..e7e7ea3 100644
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -1,31 +1,32 @@
-{
-    "workbench.colorCustomizations": {
-        "activityBar.activeBackground": "#feff1a",
-        "activityBar.background": "#feff1a",
-        "activityBar.foreground": "#15202b",
-        "activityBar.inactiveForeground": "#15202b99",
-        "activityBarBadge.background": "#00bebf",
-        "activityBarBadge.foreground": "#15202b",
-        "commandCenter.border": "#15202b99",
-        "sash.hoverBorder": "#feff1a",
-        "statusBar.background": "#e5e600",
-        "statusBar.foreground": "#15202b",
-        "statusBarItem.hoverBackground": "#b2b300",
-        "statusBarItem.remoteBackground": "#e5e600",
-        "statusBarItem.remoteForeground": "#15202b",
-        "titleBar.activeBackground": "#e5e600",
-        "titleBar.activeForeground": "#15202b",
-        "titleBar.inactiveBackground": "#e5e60099",
-        "titleBar.inactiveForeground": "#15202b99"
-    },
-    "peacock.color": "#e5e600",
-    "peacock.remotecolor": "#e5e600",
-    // Disable Folder Collapse in the project
-    "explorer.compactFolders": false,
-    "explorer.confirmDragAndDrop": true,
-    "explorer.enableDragAndDrop": true,
-    "explorer.enableUndo": true,
-    "explorer.confirmUndo": true,
-    "explorer.confirmDelete": true,
-    "explorer.confirmPasteNative": true,
+{
+    "peacock.color": "#e5e600",
+    "peacock.remotecolor": "#e5e600",
+    // Disable Folder Collapse in the project
+    "explorer.compactFolders": false,
+    "explorer.confirmDragAndDrop": true,
+    "explorer.enableDragAndDrop": true,
+    "explorer.enableUndo": true,
+    "explorer.confirmUndo": true,
+    "explorer.confirmDelete": true,
+    "explorer.confirmPasteNative": true,
+    "workbench.colorCustomizations": {
+        "activityBar.activeBackground": "#ffff33",
+        "activityBar.background": "#ffff33",
+        "activityBar.foreground": "#15202b",
+        "activityBar.inactiveForeground": "#15202b99",
+        "activityBarBadge.background": "#00bfbf",
+        "activityBarBadge.foreground": "#15202b",
+        "commandCenter.border": "#15202b99",
+        "sash.hoverBorder": "#ffff33",
+        "statusBar.background": "#ffff00",
+        "statusBar.foreground": "#15202b",
+        "statusBarItem.hoverBackground": "#cccc00",
+        "statusBarItem.remoteBackground": "#ffff00",
+        "statusBarItem.remoteForeground": "#15202b",
+        "titleBar.activeBackground": "#ffff00",
+        "titleBar.activeForeground": "#15202b",
+        "titleBar.inactiveBackground": "#ffff0099",
+        "titleBar.inactiveForeground": "#15202b99"
+    },
+    "peacock.remoteColor": "yellow",
 }
\ No newline at end of file
diff --git a/README.md b/README.md
index 15ea5f2..5f45c8b 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
 <div align="center">
 
-<img src='TuxTechBlogs/docs/img/favicon.ico' style="height:180px">
+<img src='TuxTechBlogs/docs/img/site.png' style="height:180px">
 
 # **TuxTechBlogs**
 
@@ -13,41 +13,83 @@
 
 <div>
 
-<h2>Tech Stack</h2>
 <!-- Badges For The Pages-->
+<div style="text-align:center">
 
-![Git](https://img.shields.io/badge/git-%23F05033.svg?style=for-the-badge&logo=git&logoColor=white) ![GitHub](https://img.shields.io/badge/github-%23121011.svg?style=for-the-badge&logo=github&logoColor=white) ![GitHub Actions](https://img.shields.io/badge/github%20actions-%232671E5.svg?style=for-the-badge&logo=githubactions&logoColor=white) ![GitHub Pages](https://img.shields.io/badge/GitHub%20Pages-121011.svg?logo=github&style=for-the-badge)
-![Alpine-Linux](https://img.shields.io/badge/Alpine_Linux-0D597F?style=for-the-badge&logo=alpine-linux&logoColor=white )
-![vs-code](https://img.shields.io/badge/Visual_Studio_Code-0078D4?style=for-the-badge&logo=visual%20studio%20code&logoColor=white)
-![Material-UI](https://img.shields.io/badge/Material--UI-0081CB?style=for-the-badge&logo=material-ui&logoColor=white)
-![Html](https://img.shields.io/badge/HTML5-E34F26?style=for-the-badge&logo=html5&logoColor=white)
-![Css](https://img.shields.io/badge/CSS3-1572B6?style=for-the-badge&logo=css3&logoColor=white)![Mark-down](https://img.shields.io/badge/Markdown-000000?style=for-the-badge&logo=markdown&logoColor=white)
-![Python](https://img.shields.io/badge/Python-3776AB?style=for-the-badge&logo=python&logoColor=white)
-![Docker](https://img.shields.io/badge/docker-%230db7ed.svg?style=for-the-badge&logo=docker&logoColor=white)
+<h2>
+🛠️ Tech Stack
+</h2>
+
+<table style="width:100%">
+  <tr>
+    <th>COMPONENT</th>
+    <th>DETAILS</th>
+  </tr>
+  <tr>
+    <td>Source Code Management</td>
+    <td><img src="https://img.shields.io/badge/git-%23F05033.svg?style=for-the-badge&logo=git&logoColor=white"><img src="https://img.shields.io/badge/github-%23121011.svg?style=for-the-badge&logo=github&logoColor=white"><img src="https://img.shields.io/badge/GitHub%20Pages-121011.svg?logo=github&style=for-the-badge"><img src="https://img.shields.io/badge/github%20actions-%232671E5.svg?style=for-the-badge&logo=githubactions&logoColor=white"></td>
+  </tr>
+  <tr>
+    <td>Operating Systems</td>
+    <td><img src="https://img.shields.io/badge/docker-%230db7ed.svg?style=for-the-badge&logo=docker&logoColor=white"><img src="https://img.shields.io/badge/Alpine_Linux-0D597F?style=for-the-badge&logo=alpine-linux&logoColor=white"><img src="https://img.shields.io/badge/Ubuntu-E95420?logo=ubuntu&style=for-the-badge&logoColor=white"><img src="https://img.shields.io/badge/Windows-0078D6?&style=for-the-badge&logo=windows&logoColor=white"><img src="https://img.shields.io/badge/macintosh%20-000000?&style=for-the-badge&logo=apple&logoColor=F0F0F0"></td>
+  </tr>
+    <tr>
+    <td>Integrated Development Environment</td>
+    <td><img src="https://img.shields.io/badge/Visual_Studio_Code-0078D4?style=for-the-badge&logo=visual%20studio%20code&logoColor=white"><img src="https://img.shields.io/badge/Material--UI-0081CB?style=for-the-badge&logo=material-ui&logoColor=white"><img src="https://img.shields.io/badge/css3-%231572B6.svg?&style=for-the-badge&logo=css3&logoColor=white"><img src="https://img.shields.io/badge/HTML5-E34F26?style=for-the-badge&logo=html5&logoColor=white"></td>
+  </tr>
+    <tr>
+    <td>Frameworks</td>
+    <td><a href="https://www.mkdocs.org"><b>Mkdocs</b></a>, <a href="https://squidfunk.github.io/mkdocs-material/"><b>Mkdocs-Material</b></a></td>
+  </tr>
+    </tr>
+    <tr>
+    <td>Programming & Scripting Languagues</td>
+    <td><img src="https://img.shields.io/badge/Markdown-000000?style=for-the-badge&logo=markdown&logoColor=white"><img src="https://img.shields.io/badge/Python-3776AB?style=for-the-badge&logo=python&logoColor=white"></td>
+  </tr>
+</table>
+</div>
 
+<div style="text-align:center">
 
-<img src='TuxTechBlogs/docs/img/site.png' style="height:180px">
+<h2>
+    <a href="https://blogs.tuxtechlab.com">💫 TuxTechBlog</a> GitHub Repo Stats
+</h2>
 
-![PRs](https://img.shields.io/badge/PRs-welcome-E87A90.svg?style=flat-square)
-[![Contributors](https://img.shields.io/github/contributors/TuxTechLab/Blogs.svg?style=flat-square)](https://github.com/i-Am-GhOsT/GhostVerse/graphs/contributors/)
-[![License](https://img.shields.io/github/license/TuxTechLab/Blogs.svg?style=flat-square)](./LICENSE)
-![Github Action Badge](https://github.com/TuxTechLab/Blogs/actions/workflows/pages/pages-build-deployment/badge.svg)
+</div>
 
-## 🌐 Connect With Me
+> `WORKFLOWS`
 
-[![Gmail](https://img.shields.io/badge/Gmail-D14836?style=for-the-badge&logo=gmail&logoColor=white)](mailto:arindamtanti123@gmail.com)
-[![LinkedId](https://img.shields.io/badge/LinkedIn-0077B5?style=for-the-badge&logo=linkedin&logoColor=white)](https://www.linkedin.com/in/arindam-tanti/)
+[![ci_cd_prod](https://github.com/TuxTechLab/Blogs/actions/workflows/ci_cd_prod.yml/badge.svg)](https://github.com/TuxTechLab/Blogs/actions/workflows/ci_cd_prod.yml)
+[![ci_cd_stage](https://github.com/TuxTechLab/Blogs/actions/workflows/ci_cd_stage.yml/badge.svg)](https://github.com/TuxTechLab/Blogs/actions/workflows/ci_cd_stage.yml)
 
-</div>
+> `REPOSITORY`
+
+[![License](https://img.shields.io/github/license/TuxTechLab/Blogs.svg?style=for-the-badge)](https://raw.githubusercontent.com/TuxTechLab/Blogs/master/LICENSE)
+[![Website Status](https://img.shields.io/website-up-down-green-red/http/shields.io.svg?style=for-the-badge)](http://blogs.tuxtechlab.com)
+[![Issues](https://img.shields.io/github/issues/TuxTechLab/Blogs?color=0088ff&style=for-the-badge&logo=github)](https://github.com/TuxTechLab/Blogs/issues)
+[![Pull Requests](https://img.shields.io/github/issues-pr/TuxTechLab/Blogs?color=0088ff&style=for-the-badge&logo=github)](https://github.com/TuxTechLab/Blogs/pulls)
+[![Contributors](https://img.shields.io/github/contributors/TuxTechLab/Blogs.svg)](https://github.com/TuxTechLab/Blogs/graphs/contributors/)
+[![Stars](https://img.shields.io/github/stars/TuxTechLab/blogs)](https://github.com/TuxTechLab/Blogs/stargazers)
 
 
 <div style="text-align:center">
 
-<h2>📊 Repo Stats </h2>
+<h2>
+✅ Code of Conduct
+</h2>
+
+Learn more from <a href="./CODE_OF_CONDUCT.md"><b>CODE OF CONDUCT</b></a> of <a href="https://blogs.tuxtechlab.com"><b>TuxTechBlogs</b></a>
+
+</div>
+
+<div style="text-align:center">
 
+<h2>
+📞 Conect Us
+</h2>
 
-![Alt](https://repobeats.axiom.co/api/embed/6e50266512168c31ef7c3b5e68a67dacda98ef22.svg "Repobeats analytics image")
+Please visit <a href="./contacts.md">Contact Us</a> of <a href="https://blogs.tuxtechlab.com"><b>TuxTechBlogs</b></a> to know more.
 
-<p>&copy; 2023<a href="https://www.linkedin.com/in/arindam-tanti"> Arindam Tanti</a> All rights reserved.</p>
+<p>&copy; 2023<a href="https://blogs.tuxtechlab.com"> TuxTechBlog </a> All rights reserved.</p>
 
 </div>
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/CHANGELOG.md b/TuxTechBlogs/docs/CHANGELOG.md
new file mode 100644
index 0000000..923fc0c
--- /dev/null
+++ b/TuxTechBlogs/docs/CHANGELOG.md
@@ -0,0 +1,73 @@
+<link rel="stylesheet" href="stylesheet/extra.css">
+
+# Changelog
+
+All notable changes to this project will be documented in this file. Dates are displayed in UTC.
+
+Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).
+
+## [Unreleased](https://github.com/TuxTechLab/Blogs/compare/1.0...HEAD)
+
+- #6 [Doc] (feat) added new docs and formattted the folders placement with names ( *.md). [`9221039`](https://github.com/TuxTechLab/Blogs/commit/92210397c731e28a4d59b8c6302385d3f58531c5)
+- #5 [Dependency] (fix) added new latest dependency in the repo. [`a5adbcf`](https://github.com/TuxTechLab/Blogs/commit/a5adbcffe913524a590f88393a2be7b0086af7d9)
+- #16 [Doc] (✨) Added DevOPs intro documents in the repo and added DevOPs topic. [`1f2613b`](https://github.com/TuxTechLab/Blogs/commit/1f2613b8002f542f70ba2ee60b5c5b876315e005)
+- #24 [Feat] Adding new scripts to manage the application via docker stack/ compose. Also adding script to check all the dependencies are installed in the system. [`a1dc190`](https://github.com/TuxTechLab/Blogs/commit/a1dc190dc014b5d704140586d82d9430f31c04b6)
+- #18 [Doc] (🔧) Fixed the devops document  reference in mkdocs.yml and DevOPs intro makrdown. [`a9642f6`](https://github.com/TuxTechLab/Blogs/commit/a9642f6a953bf1809ad44e1e05d6b299046c9c0f)
+- #17 [Doc] (🔧) Fixed the devops document  reference in mkdocs.yml and DevOPs intro makrdown. [`fbe9e0f`](https://github.com/TuxTechLab/Blogs/commit/fbe9e0f075e3d4f4c5280eab7302c16ef16d9a56)
+- #4 [Code] (feat) Modifed devcontainer setup to use dockerfile with workspace mount & port forward works. [`85b7489`](https://github.com/TuxTechLab/Blogs/commit/85b748905167cdddedc6b7df977e09103c9a432a)
+- #10 [Code] (style) Adding new logo, favicon, extra css, markdown lint, and new mkdocs config. [`51d78c8`](https://github.com/TuxTechLab/Blogs/commit/51d78c886875b659969575edaa87209f2edfa2f1)
+- #7 [Feat] (fix) Adding Markdown Linting. (.markdownlist.json) [`7744845`](https://github.com/TuxTechLab/Blogs/commit/7744845a6faffa82ba70b57f978234065468bed4)
+- #23 [Code] Added ( .gitignore, example.env ) Modified ( .makrdownlintrc, settings.json ). [`baec2f7`](https://github.com/TuxTechLab/Blogs/commit/baec2f72f37e893efa3d44c29fd01da3ce85e88b)
+- #20 [Doc] (🔧) Fixed the miscellanceous document for ports and assets. [`245969e`](https://github.com/TuxTechLab/Blogs/commit/245969e97e93b84d968017b328b0db8cb3be751d)
+- #3 [Code] (fix) Modifed dockerfile to use slim python image. [`5bc9f03`](https://github.com/TuxTechLab/Blogs/commit/5bc9f0328ca6ef7ecf524d9c37e2322569812ec7)
+- #13 [Doc] (🔧) Modified Kanban Documents and removed image assets. [`097656a`](https://github.com/TuxTechLab/Blogs/commit/097656a6bc6c6b10d304caa5d8d1f7dc7077e80c)
+- #11 [Doc] (fix) Modified SCRUM Documents and removed image assets. [`c4da16e`](https://github.com/TuxTechLab/Blogs/commit/c4da16e813900c701ebbf8690c98b7bf780602b8)
+- #9 [Doc] (fix) Modified ITSM Documents and removed image assets. [`f0f7389`](https://github.com/TuxTechLab/Blogs/commit/f0f7389e076f2cfecacaf10a1d12564e1271b394)
+- #20 [Doc] (🔧) Fixed the miscellanceous document for ports  and assets. [`95f7e79`](https://github.com/TuxTechLab/Blogs/commit/95f7e7976cd2bbc412708a3776efbdddd1a8dbb5)
+- #14 [Doc] (🔧) Modified Meeting Related Documents and removed image assets. [`8959055`](https://github.com/TuxTechLab/Blogs/commit/8959055bdf5319baec93268480eb95e26eee1252)
+- #8 [Doc] (fix) Modified Agile Documents and removed image assets. [`667ff75`](https://github.com/TuxTechLab/Blogs/commit/667ff751bcc66ea2e0ed04c5e644f5cfe9a4b80b)
+- #25 [Fix] Modified the blogs stack yml, added deployment specification for the blogs service. [`ba84bcb`](https://github.com/TuxTechLab/Blogs/commit/ba84bcb363733b24db52982034715dc7998b34ce)
+- #19 [Doc] (🔧) Fixed the miscellanceous documents reference in mkdocs.yml and assets. [`3ef7b5a`](https://github.com/TuxTechLab/Blogs/commit/3ef7b5a4c64b50bb9a2471f4948ed8c51b843591)
+- #21 [Config] (🔧) Added new site changes in the mkdocs.yml file. [`c6a8c03`](https://github.com/TuxTechLab/Blogs/commit/c6a8c035fe6e3c627eee9740f54a2a70f6c8b9e0)
+- #12 [Code] (🔧) Added mkdocs config and social media changes. [`8cd7540`](https://github.com/TuxTechLab/Blogs/commit/8cd754018e28143521f58f1cab3d47ee16335e89)
+- #25 [Doc] (✨) Modified the license. [`5a617ab`](https://github.com/TuxTechLab/Blogs/commit/5a617aba071e388a20a3317f0c1912da36782a85)
+- #22 [Feat] (✨) Added CNAME file for automatic github page deployment with custom DNS name. [`b5c4417`](https://github.com/TuxTechLab/Blogs/commit/b5c44173ae720f39c29955ed0649f2e24806696f)
+- #26 [Feat] (✨) Adding SCRUM module assets. [`ecc7f80`](https://github.com/TuxTechLab/Blogs/commit/ecc7f80681718cc9364d3c35fdfc9cb1876c7ff6)
+- #15 [Doc] (🔧) Agile related assets removed. [`dc42dc6`](https://github.com/TuxTechLab/Blogs/commit/dc42dc6d7769f9ddc9f9695316cacfb57acf3c12)
+
+## [1.0](https://github.com/TuxTechLab/Blogs/compare/v1.0.0...1.0)
+
+> 24 February 2024
+
+## v1.0.0
+
+> 15 June 2024
+
+- #1 [Code] (feat) Initial Commit. Adding All Source Code to master TuxTechLab/Blogs [`2609966`](https://github.com/TuxTechLab/Blogs/commit/2609966c5aca6278c37ea903bc511c9994044237)
+- #6 [Doc] (feat) added new docs and formattted the folders placement with names ( *.md). [`9221039`](https://github.com/TuxTechLab/Blogs/commit/92210397c731e28a4d59b8c6302385d3f58531c5)
+- #5 [Dependency] (fix) added new latest dependency in the repo. [`a5adbcf`](https://github.com/TuxTechLab/Blogs/commit/a5adbcffe913524a590f88393a2be7b0086af7d9)
+- #16 [Doc] (✨) Added DevOPs intro documents in the repo and added DevOPs topic. [`1f2613b`](https://github.com/TuxTechLab/Blogs/commit/1f2613b8002f542f70ba2ee60b5c5b876315e005)
+- #24 [Feat] Adding new scripts to manage the application via docker stack/ compose. Also adding script to check all the dependencies are installed in the system. [`a1dc190`](https://github.com/TuxTechLab/Blogs/commit/a1dc190dc014b5d704140586d82d9430f31c04b6)
+- #18 [Doc] (🔧) Fixed the devops document  reference in mkdocs.yml and DevOPs intro makrdown. [`a9642f6`](https://github.com/TuxTechLab/Blogs/commit/a9642f6a953bf1809ad44e1e05d6b299046c9c0f)
+- #17 [Doc] (🔧) Fixed the devops document  reference in mkdocs.yml and DevOPs intro makrdown. [`fbe9e0f`](https://github.com/TuxTechLab/Blogs/commit/fbe9e0f075e3d4f4c5280eab7302c16ef16d9a56)
+- #4 [Code] (feat) Modifed devcontainer setup to use dockerfile with workspace mount & port forward works. [`85b7489`](https://github.com/TuxTechLab/Blogs/commit/85b748905167cdddedc6b7df977e09103c9a432a)
+- #10 [Code] (style) Adding new logo, favicon, extra css, markdown lint, and new mkdocs config. [`51d78c8`](https://github.com/TuxTechLab/Blogs/commit/51d78c886875b659969575edaa87209f2edfa2f1)
+- #7 [Feat] (fix) Adding Markdown Linting. (.markdownlist.json) [`7744845`](https://github.com/TuxTechLab/Blogs/commit/7744845a6faffa82ba70b57f978234065468bed4)
+- #23 [Code] Added ( .gitignore, example.env ) Modified ( .makrdownlintrc, settings.json ). [`baec2f7`](https://github.com/TuxTechLab/Blogs/commit/baec2f72f37e893efa3d44c29fd01da3ce85e88b)
+- #20 [Doc] (🔧) Fixed the miscellanceous document for ports and assets. [`245969e`](https://github.com/TuxTechLab/Blogs/commit/245969e97e93b84d968017b328b0db8cb3be751d)
+- #3 [Code] (fix) Modifed dockerfile to use slim python image. [`5bc9f03`](https://github.com/TuxTechLab/Blogs/commit/5bc9f0328ca6ef7ecf524d9c37e2322569812ec7)
+- #13 [Doc] (🔧) Modified Kanban Documents and removed image assets. [`097656a`](https://github.com/TuxTechLab/Blogs/commit/097656a6bc6c6b10d304caa5d8d1f7dc7077e80c)
+- #11 [Doc] (fix) Modified SCRUM Documents and removed image assets. [`c4da16e`](https://github.com/TuxTechLab/Blogs/commit/c4da16e813900c701ebbf8690c98b7bf780602b8)
+- #9 [Doc] (fix) Modified ITSM Documents and removed image assets. [`f0f7389`](https://github.com/TuxTechLab/Blogs/commit/f0f7389e076f2cfecacaf10a1d12564e1271b394)
+- #20 [Doc] (🔧) Fixed the miscellanceous document for ports  and assets. [`95f7e79`](https://github.com/TuxTechLab/Blogs/commit/95f7e7976cd2bbc412708a3776efbdddd1a8dbb5)
+- #14 [Doc] (🔧) Modified Meeting Related Documents and removed image assets. [`8959055`](https://github.com/TuxTechLab/Blogs/commit/8959055bdf5319baec93268480eb95e26eee1252)
+- #8 [Doc] (fix) Modified Agile Documents and removed image assets. [`667ff75`](https://github.com/TuxTechLab/Blogs/commit/667ff751bcc66ea2e0ed04c5e644f5cfe9a4b80b)
+- #25 [Fix] Modified the blogs stack yml, added deployment specification for the blogs service. [`ba84bcb`](https://github.com/TuxTechLab/Blogs/commit/ba84bcb363733b24db52982034715dc7998b34ce)
+- #19 [Doc] (🔧) Fixed the miscellanceous documents reference in mkdocs.yml and assets. [`3ef7b5a`](https://github.com/TuxTechLab/Blogs/commit/3ef7b5a4c64b50bb9a2471f4948ed8c51b843591)
+- #21 [Config] (🔧) Added new site changes in the mkdocs.yml file. [`c6a8c03`](https://github.com/TuxTechLab/Blogs/commit/c6a8c035fe6e3c627eee9740f54a2a70f6c8b9e0)
+- #12 [Code] (🔧) Added mkdocs config and social media changes. [`8cd7540`](https://github.com/TuxTechLab/Blogs/commit/8cd754018e28143521f58f1cab3d47ee16335e89)
+- #2 [Code] (fix) Fixing Contributors badge in ReadMe.md file. Changed Project Path in badge. [`1e91007`](https://github.com/TuxTechLab/Blogs/commit/1e91007250f35d327ecf300b421086fe290c4036)
+- #25 [Doc] (✨) Modified the license. [`5a617ab`](https://github.com/TuxTechLab/Blogs/commit/5a617aba071e388a20a3317f0c1912da36782a85)
+- #22 [Feat] (✨) Added CNAME file for automatic github page deployment with custom DNS name. [`b5c4417`](https://github.com/TuxTechLab/Blogs/commit/b5c44173ae720f39c29955ed0649f2e24806696f)
+- #26 [Feat] (✨) Adding SCRUM module assets. [`ecc7f80`](https://github.com/TuxTechLab/Blogs/commit/ecc7f80681718cc9364d3c35fdfc9cb1876c7ff6)
+- #15 [Doc] (🔧) Agile related assets removed. [`dc42dc6`](https://github.com/TuxTechLab/Blogs/commit/dc42dc6d7769f9ddc9f9695316cacfb57acf3c12)
diff --git a/TuxTechBlogs/docs/blog/index.md b/TuxTechBlogs/docs/blog/index.md
new file mode 100644
index 0000000..c58f16c
--- /dev/null
+++ b/TuxTechBlogs/docs/blog/index.md
@@ -0,0 +1,2 @@
+# Blog
+
diff --git a/TuxTechBlogs/docs/contacts.md b/TuxTechBlogs/docs/contacts.md
index e69de29..7815a5e 100644
--- a/TuxTechBlogs/docs/contacts.md
+++ b/TuxTechBlogs/docs/contacts.md
@@ -0,0 +1,10 @@
+<div align="center">
+
+
+## 📞 Contact Us
+
+[![Gmail](https://img.shields.io/badge/Gmail-D14836?logo=gmail&logoColor=white&style=for-the-badge)](mailto:support@tuxtechlab.com) [![LinkedId](https://img.shields.io/badge/LinkedIn-0077B5?logo=linkedin&logoColor=white&style=for-the-badge)](https://inkedin.com/company/tuxtechlab)[![GitHub](https://img.shields.io/badge/github-%23121011.svg?style=for-the-badge&logo=github&logoColor=white)](https://github.com/TuxTechLab)
+
+<img src="https://discordapp.com/api/guilds/1244812127223545918/widget.png?style=banner1" alt="Discord Banner 3" style="border-radius:10px"/>
+</div>
+
diff --git a/TuxTechBlogs/docs/foundations.md b/TuxTechBlogs/docs/foundations.md
deleted file mode 100644
index e69de29..0000000
diff --git a/TuxTechBlogs/docs/img/site.png b/TuxTechBlogs/docs/img/site.png
index 42b0334..1c843b5 100644
Binary files a/TuxTechBlogs/docs/img/site.png and b/TuxTechBlogs/docs/img/site.png differ
diff --git a/TuxTechBlogs/docs/index-script.js b/TuxTechBlogs/docs/index-script.js
new file mode 100644
index 0000000..0c5fdf2
--- /dev/null
+++ b/TuxTechBlogs/docs/index-script.js
@@ -0,0 +1,652 @@
+/**
+ * Common options
+ */
+let startMusic  = true;   // auto start music (firefox only)
+let cycleColor  = false;  // cycle colors 
+let commonHue   = 0.038;  // initial color 
+let commonColor = new THREE.Color();
+commonColor.setHSL( commonHue, .8, .5 );
+
+/**
+ * Device screen info helper 
+ */
+const deviceInfo = (function(){
+ const _w = window;
+ const _s = window.screen;
+ const _b = document.body;
+ const _d = document.documentElement;
+ 
+ return {
+  screenWidth() {
+   return Math.max( 0, _w.innerWidth || _d.clientWidth || _b.clientWidth || 0 );
+  },
+  screenHeight() {
+   return Math.max( 0, _w.innerHeight || _d.clientHeight || _b.clientHeight || 0 );
+  },
+  screenRatio() {
+   return this.screenWidth() / this.screenHeight();
+  },
+  screenCenterX() {
+   return this.screenWidth() / 2;
+  },
+  screenCenterY() {
+   return this.screenHeight() / 2;
+  },
+  mouseX( e ) {
+   return Math.max( 0, e.pageX || e.clientX || 0 );
+  },
+  mouseY( e ) {
+   return Math.max( 0, e.pageY || e.clientY || 0 );
+  },
+  mouseCenterX( e ) {
+   return this.mouseX( e ) - this.screenCenterX();
+  },
+  mouseCenterY( e ) {
+   return this.mouseY( e ) - this.screenCenterY();
+  },
+ }; 
+})();
+
+
+/**
+ * Music player helper 
+ */
+const musicHelper = (function(){
+ let wrap   = document.querySelector( '#player' ); 
+ let button = wrap ? wrap.querySelector( 'button' ) : null; 
+ let audio  = new Audio( 'http://ice1.somafm.com/u80s-256-mp3' ); 
+ let step   = 0.01;
+ let active = false; 
+ let sto    = null; 
+ 
+ let fadeIn = () => {
+  audio.volume += 0.01; 
+  if ( audio.volume >= 0.2 ) { audio.volume = 0.2; return; }
+  sto = setTimeout( fadeIn, 100 ); 
+ };
+ 
+ let fadeOut = () => {
+  audio.volume -= 0.02; 
+  if ( audio.volume <= 0.01 ) { audio.volume = 0; audio.pause(); return; }
+  sto = setTimeout( fadeOut, 100 ); 
+ };
+ 
+ let play = () => {
+  if ( sto ) clearTimeout( sto ); 
+  active = true;
+  button.textContent = 'Stop Music'; 
+  audio.play(); 
+  fadeIn();
+ };
+ 
+ let stop = () => {
+  if ( sto ) clearTimeout( sto ); 
+  active = false;
+  button.textContent = 'Play Music'; 
+  fadeOut();
+ };
+ 
+ button.addEventListener( 'click', e => {
+  e.stopPropagation(); 
+  e.preventDefault(); 
+  if ( active ) { stop(); } 
+  else { play(); }
+ });
+ 
+ audio.preload = 'auto'; 
+ audio.muted   = false; 
+ audio.volume  = 0;
+ return { play, stop };
+})();
+
+
+/**
+ * Loader Helper
+ */
+const LoaderHelper = {
+ _base: 'https://raw.githubusercontent.com/rainner/codepen-assets/master/',
+ _data: {}, 
+ _loaded: 0, 
+ _cb: null,
+ 
+ // get loaded resource by name  
+ get( name ) {
+  return this._data[ name ] || null; 
+ }, 
+ 
+ // complete handler 
+ onReady( cb ) {
+  this._cb = cb; 
+ }, 
+ 
+ // common error handler 
+ onError( err ) {
+  console.error( err.message || err ); 
+ }, 
+ 
+ // when a resource is loaded 
+ onData( name, data ) {
+  this._loaded += 1;
+  this._data[ name ] = data; 
+  let total  = Object.keys( this._data ).length; 
+  let loaded = ( total && this._loaded === total ); 
+  let hascb  = ( typeof this._cb === 'function' ); 
+  if ( loaded && hascb ) this._cb( total ); 
+ }, 
+ 
+ // custom .obj file 
+ loadGeometry( name, file ) {
+  if ( !name || !file ) return;
+  this._data[ name ] = new THREE.Object3D(); 
+  const path = this._base +'/'+ file; 
+  const loader = new THREE.OBJLoader2();
+  loader.load( path, data => { this.onData( name, data ) }, null, this.onError );
+ }, 
+ 
+ // load image file 
+ loadTexture( name, file ) {
+  if ( !name || !file ) return;
+  this._data[ name ] = new THREE.Texture(); 
+  const path = this._base +'/'+ file; 
+  const loader = new THREE.TextureLoader();
+  loader.load( path, data => { this.onData( name, data ) }, null, this.onError );
+ },
+};
+
+
+/**
+ * Helper for adding easing effect 
+ */
+const addEase = ( pos, to, ease ) => {
+ pos.x += ( to.x - pos.x ) / ease;
+ pos.y += ( to.y - pos.y ) / ease;
+ pos.z += ( to.z - pos.z ) / ease;
+};
+
+/**
+ * Shooting star object 
+ */
+const shootingStar = {
+ scene: null, 
+ stars: [], 
+ spread: 1000, 
+ 
+ // create
+ create( scene ) {
+  this.scene = scene; 
+  let geometry = new THREE.CylinderGeometry( 0, 2, 120, 10 );
+  let material = new THREE.MeshBasicMaterial({
+   color: 0xffffcc,
+   opacity: .4,
+   blending: THREE.AdditiveBlending,
+   side: THREE.FrontSide,
+   transparent: false,
+   depthTest: true,
+  });
+  
+  let randx = THREE.Math.randInt( -this.spread, this.spread ); 
+  let cylinder = new THREE.Mesh( geometry, material );
+  cylinder.position.set( randx, 300, 200 );
+  cylinder.rotation.set( Math.PI / 2, 0, 0 );
+  this.stars.push( cylinder ); 
+  this.scene.add( cylinder ); 
+ },
+ 
+ // update
+ update( mouse ) {
+  for ( let i = 0; i < this.stars.length; i++ ) {
+   let cylinder = this.stars[ i ]; 
+   
+   if ( cylinder.position.z < -3000 ) {
+    this.stars.splice( i, 1 ); 
+    this.scene.remove( cylinder ); 
+    continue;
+   }
+   cylinder.position.z -= 20; 
+  }
+ },
+};
+
+
+/**
+ * Starfield object 
+ */
+const starField = {
+ group: null, 
+ total: 400, 
+ spread: 8000, 
+ zoom: 1000, 
+ ease: 12, 
+ move: { x: 0, y: 1200, z: -1000 },  
+ look: { x: 0, y:0, z: 0 }, 
+ 
+ // create 
+ create( scene ) {
+  this.group = new THREE.Object3D();
+  this.group.position.set( this.move.x, this.move.y, this.move.z );
+  this.group.rotation.set( this.look.x, this.look.y, this.look.z );
+ 
+  let geometry = new THREE.Geometry();
+  let material = new THREE.PointsMaterial({
+   size: 64,
+   color: 0xffffff,
+   opacity: 1,
+   map: LoaderHelper.get( 'starTexture' ), 
+   blending: THREE.AdditiveBlending,
+   vertexColors: false,
+   transparent: false,
+   depthTest: false,
+  });
+  
+  for ( let i = 0; i < this.total; i++ ) {
+   let angle = ( Math.random() * Math.PI * 2 );
+   let radius = THREE.Math.randInt( 0, this.spread );
+  
+   geometry.vertices.push( new THREE.Vector3(
+    Math.cos( angle ) * radius,
+    Math.sin( angle ) * radius / 10,
+    THREE.Math.randInt( -this.spread, 0 )
+   ));
+  }
+  this.group.add( new THREE.Points( geometry, material ) );
+  scene.add( this.group );
+ }, 
+ 
+ // update 
+ update( mouse ) {
+  this.move.x = -( mouse.x * 0.005 );
+  addEase( this.group.position, this.move, this.ease );
+  addEase( this.group.rotation, this.look, this.ease );
+ }, 
+}; 
+
+
+/**
+ * Mountains object
+ */
+const mountains = {
+ group: null, 
+ simplex: null,
+ geometry: null, 
+ factor: 1000, // smoothness 
+ scale: 500, // terrain size
+ speed: 0.0005, // move speed 
+ cycle: 0, 
+ ease: 18, 
+ move: { x: 0, y: 0, z: -3500 },
+ look: { x: 0, y: 0, z: 0 }, 
+ 
+ create( scene ) {
+  this.group = new THREE.Object3D();
+  this.group.position.set( this.move.x, this.move.y, this.move.z );
+  this.group.rotation.set( this.look.x, this.look.y, this.look.z );
+  
+  this.simplex  = new SimplexNoise(); 
+  this.geometry = new THREE.PlaneGeometry( 10000, 1000, 128, 32 ); 
+  
+  let texture   = LoaderHelper.get( 'mountainTexture' );
+  texture.wrapT = THREE.RepeatWrapping;
+  texture.wrapS = THREE.RepeatWrapping;
+  
+  let material  = new THREE.MeshPhongMaterial({
+   color: 0xffffff,
+   opacity: 1,
+   map: texture, 
+   blending: THREE.NoBlending,
+   side: THREE.BackSide,
+   transparent: false,
+   depthTest: false,
+  });
+  
+  let terrain = new THREE.Mesh( this.geometry, material );
+  terrain.position.set( 0, -500, -3000 );
+  terrain.rotation.x = ( Math.PI / 2 ) + 1.35;
+  
+  let light = new THREE.PointLight( 0xffffff, 8, 5500 );
+  light.position.set( 0, 1200, -3500 );
+  light.castShadow = false;
+  light.color = commonColor;
+  
+  this.movePlain();
+  this.group.add( terrain );
+  this.group.add( light );
+  scene.add( this.group );
+ }, 
+ 
+ // make new mointain plain 
+ movePlain() {
+  for ( let vertex of this.geometry.vertices ) {
+   let xoff = ( vertex.x / this.factor ); 
+   let yoff = ( vertex.y / this.factor ) + this.cycle; 
+   let rand = this.simplex.noise2D( xoff, yoff ) * this.scale;
+   vertex.z = rand;
+  }
+  this.geometry.verticesNeedUpdate = true;
+  this.cycle -= this.speed;
+ }, 
+ 
+ // update 
+ update( mouse ) {
+  this.move.x = -( mouse.x * 0.02 );
+  this.movePlain();
+  addEase( this.group.position, this.move, this.ease );
+  addEase( this.group.rotation, this.look, this.ease );
+ }, 
+};
+
+
+/**
+ * Ground object
+ */
+const groundPlain = {
+ group: null, 
+ geometry: null, 
+ material: null, 
+ plane: null,
+ simplex: null,
+ factor: 300, // smoothness 
+ scale: 30, // terrain size
+ speed: 0.015, // move speed 
+ cycle: 0, 
+ ease: 12, 
+ move: { x: 0, y: -300, z: -1000 },
+ look: { x: 29.8, y: 0, z: 0 }, 
+ 
+ // create
+ create( scene ) {
+  this.group = new THREE.Object3D();
+  this.group.position.set( this.move.x, this.move.y, this.move.z );
+  this.group.rotation.set( this.look.x, this.look.y, this.look.z );
+  
+  this.geometry = new THREE.PlaneGeometry( 4000, 2000, 128, 64 ); 
+  this.material = new THREE.MeshLambertMaterial({
+   color: 0xffffff,
+   opacity: 1,
+   blending: THREE.NoBlending,
+   side: THREE.FrontSide,
+   transparent: false,
+   depthTest: false,
+   wireframe: true, 
+  });
+ 
+  this.plane = new THREE.Mesh( this.geometry, this.material );
+  this.plane.position.set( 0, 0, 0 );
+
+  this.simplex = new SimplexNoise(); 
+  this.moveNoise();
+  
+  this.group.add( this.plane );
+  scene.add( this.group );
+ }, 
+ 
+ // change noise values over time 
+ moveNoise() {
+  for ( let vertex of this.geometry.vertices ) {
+   let xoff = ( vertex.x / this.factor ); 
+   let yoff = ( vertex.y / this.factor ) + this.cycle; 
+   let rand = this.simplex.noise2D( xoff, yoff ) * this.scale;
+   vertex.z = rand;
+  }
+  this.geometry.verticesNeedUpdate = true;
+  this.cycle += this.speed;
+ }, 
+ 
+ // update
+ update( mouse ) {
+  this.moveNoise();
+  this.move.x = -( mouse.x * 0.04 );
+  addEase( this.group.position, this.move, this.ease );
+  addEase( this.group.rotation, this.look, this.ease );
+ },
+};
+
+
+/**
+ * Ship object
+ */
+const gunShip = {
+ scene: null, 
+ group: null,
+ engineTexture: null, 
+ gunSound: 'https://raw.githubusercontent.com/rainner/codepen-assets/master/audio/effects/lazer.mp3', 
+ shots: [], 
+ ease: 12, 
+ move: { x: 0, y: 0, z: -40 },
+ look: { x: 0, y: 0, z: 0 }, 
+
+ // create
+ create( scene ) {
+  this.scene = scene; 
+  this.group = new THREE.Object3D();
+  this.group.position.set( this.move.x, this.move.y, this.move.z );
+  this.group.rotation.set( this.look.x, this.look.y, this.look.z );
+  
+  let material = new THREE.MeshPhongMaterial({
+   color: 0xffffff,
+   blending: THREE.NoBlending,
+   side: THREE.FrontSide,
+   transparent: false,
+   depthTest: true,
+   wireframe: false, 
+  });
+  
+  let light = new THREE.PointLight( 0xffffff, .4, 600 );
+  light.position.set( 0, 0, 600 );
+  
+  // let ship = LoaderHelper.get( 'shipGeometry' );
+  // ship.position.set( 0, 0, 300 );
+  // ship.rotation.set( 0, Math.PI, 0 );
+  // ship.traverse( child => {
+  //   if ( child instanceof THREE.Mesh ) {
+  //    child.material = material;
+  //   }
+  // });
+  
+  this.setupEngine();
+  this.playGunSound( false ); 
+  // this.group.add( ship ); 
+  this.group.add( light ); 
+  scene.add( this.group ); 
+ },
+ 
+ // create jet engine effect
+ setupEngine() {
+  this.engineTexture = LoaderHelper.get( 'engineTexture' );
+  this.engineTexture.wrapT = THREE.RepeatWrapping;
+  this.engineTexture.wrapS = THREE.RepeatWrapping;
+  
+  let material = new THREE.MeshBasicMaterial({
+   color: 0x0099ff,
+   opacity: 1,
+   alphaMap: this.engineTexture,
+   blending: THREE.AdditiveBlending,
+   side: THREE.FrontSide,
+   transparent: true,
+   depthTest: true,
+  });
+  
+  let cylinder = new THREE.Mesh( new THREE.CylinderGeometry( 0, .4, 8, 32, 32, true ), material );
+  cylinder.position.set( 0, .4, 307 );
+  cylinder.rotation.x = Math.PI / 2;
+  this.group.add( cylinder ); 
+ }, 
+ 
+ // update engine burn effect 
+ updateEngine() {
+  this.engineTexture.offset.y -= 0.06;
+  this.engineTexture.needsUpdate = true;
+ }, 
+ 
+ // move ship on scroll 
+ onScroll( e ) {
+  let z = this.move.z; 
+  let d = z + ( e.deltaY | 0 ); 
+  d = ( d < -130 ) ? -130 : d;
+  d = ( d > -30 ) ? -30 : d;
+  this.move.z = d;
+ }, 
+ 
+ // add gun fire on click 
+ onClick( e ) {
+  let p = this.group.position; 
+  
+  let color = new THREE.Color();
+  color.setHSL( Math.random(), 1, .5 );
+  
+  let geometry = new THREE.CylinderGeometry( .3, 0, 20, 10 );
+  let material = new THREE.MeshBasicMaterial({
+   color,
+   opacity: .8,
+   blending: THREE.AdditiveBlending,
+   side: THREE.FrontSide,
+   transparent: false,
+   depthTest: true,
+  });
+  
+  let cylinder = new THREE.Mesh( geometry, material );
+  cylinder.position.set( p.x, p.y, p.z + 290 );
+  cylinder.rotation.set( 11, 0, 0 );
+  
+  this.shots.push( cylinder ); 
+  this.scene.add( cylinder ); 
+  this.playGunSound( true ); 
+ }, 
+ 
+ // gun sound
+ playGunSound( play ) {
+  let audio = new Audio( this.gunSound );
+  if ( play ) {
+   audio.volume = 0.5;
+   audio.play();
+  }
+ }, 
+ 
+ // update gun shots 
+ updateShots() {
+  for ( let i = 0; i < this.shots.length; i++ ) {
+   let cylinder = this.shots[ i ]; 
+   
+   if ( cylinder.position.z < -300 ) {
+    this.shots.splice( i, 1 ); 
+    this.scene.remove( cylinder ); 
+    continue;
+   }
+   cylinder.position.z -= 6; 
+  }
+ }, 
+ 
+ // update
+ update( mouse ) {
+  this.move.x =  ( mouse.x * 0.05 );
+  this.move.y = -( mouse.y * 0.04 ) - 4;
+  this.look.z =  ( mouse.x * 0.0004 );
+  
+  this.updateShots();
+  this.updateEngine();
+
+  addEase( this.group.position, this.move, this.ease );
+  addEase( this.group.rotation, this.look, this.ease );
+ },
+};
+
+/**
+ * Setup scene 
+ */
+const setupScene = () => {
+ const scene = new THREE.Scene();
+
+ // track mouse movement 
+ let mouse = { 
+  x: deviceInfo.screenCenterX(), 
+  y: deviceInfo.screenCenterY(), 
+ };  
+ 
+ // setup renderer 
+ const renderer = new THREE.WebGLRenderer( { alpha: true, antialias: true, precision: 'mediump' } );
+ renderer.setSize( deviceInfo.screenWidth(), deviceInfo.screenHeight() );
+ renderer.setPixelRatio( window.devicePixelRatio );
+ renderer.setClearColor( 0x000000, 0 );
+ renderer.sortObjects = true;
+ renderer.domElement.setAttribute( 'id', 'stageElement' );
+ document.body.appendChild( renderer.domElement );
+
+ // setup camera 
+ const camera = new THREE.PerspectiveCamera( 60, deviceInfo.screenRatio(), 0.1, 20000 );
+ camera.position.set( 0, 0, 300 );
+ camera.rotation.set( 0, 0, 0 );
+ camera.lookAt( scene.position );
+ 
+ // setup light source 
+ const light = new THREE.PointLight( 0xffffff, 4, 1000 );
+ light.position.set( 0, 200, -500 );
+ light.castShadow = false;
+ light.target = scene;
+ light.color = commonColor;
+ scene.add( light ); 
+ 
+ // setup objects 
+ starField.create( scene ); 
+ mountains.create( scene ); 
+ groundPlain.create( scene ); 
+ gunShip.create( scene ); 
+ 
+ // on page resize
+ window.addEventListener( 'resize', e => {
+  camera.aspect = deviceInfo.screenRatio(); 
+  camera.updateProjectionMatrix();
+  renderer.setSize( deviceInfo.screenWidth(), deviceInfo.screenHeight() );
+ });
+ 
+ // on mouse move 
+ window.addEventListener( 'mousemove', e => {
+  mouse.x = deviceInfo.mouseCenterX( e ); 
+  mouse.y = deviceInfo.mouseCenterY( e ); 
+ });
+
+ // on mouse wheel
+ window.addEventListener( 'wheel', e => {
+  gunShip.onScroll( e ); 
+ });
+ 
+ // on mouse click
+ window.addEventListener( 'click', e => {
+  gunShip.onClick( e ); 
+ });
+ 
+ // autostart music 
+ const isff = ( typeof InstallTrigger !== 'undefined' );
+ if ( startMusic && isff ) musicHelper.play(); 
+ 
+ // animation loop 
+ const loop = () => {
+  requestAnimationFrame( loop ); 
+  
+  // add random shooting stars 
+  if ( Math.random() > 0.99 ) shootingStar.create( scene );
+  
+  // update light hue 
+  if ( cycleColor ) {
+   commonHue += 0.001; 
+   if ( commonHue >= 1 ) commonHue = 0; 
+   commonColor.setHSL( commonHue, .8, .5 );
+  }
+  // update objects 
+  shootingStar.update( mouse );
+  starField.update( mouse ); 
+  mountains.update( mouse ); 
+  groundPlain.update( mouse ); 
+  gunShip.update( mouse ); 
+  
+  // render scene 
+  renderer.render( scene, camera );
+ };
+ 
+ loop();
+};
+
+// init 
+LoaderHelper.onReady( setupScene );
+LoaderHelper.loadTexture( 'starTexture', 'images/star.png' ); 
+LoaderHelper.loadTexture( 'mountainTexture', 'images/terrain2.jpg' ); 
+LoaderHelper.loadTexture( 'engineTexture', 'images/water.jpg' ); 
+LoaderHelper.loadGeometry( 'shipGeometry', 'models/SpaceFighter03/SpaceFighter03.obj' );
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/index-style.css b/TuxTechBlogs/docs/index-style.css
new file mode 100644
index 0000000..004cc29
--- /dev/null
+++ b/TuxTechBlogs/docs/index-style.css
@@ -0,0 +1,545 @@
+*, *:before, *:after {
+  margin: 0;
+  padding: 0;
+  border: 0;
+}
+
+html, body {
+  display: block;
+  max-width: 100vw;
+  min-height: 100vh;
+}
+
+body {
+  overflow: hidden;
+  position: relative;
+  background-color: black;
+  background-image: url("https://raw.githubusercontent.com/rainner/codepen-assets/master/images/pinkish_sunset.jpg");
+  background-position: center top;
+  background-repeat: no-repeat;
+  background-size: 170vh;
+  font-family: "Denk One", Arial, sans-serif;
+  font-weight: normal;
+  font-size: 18px;
+  line-height: 1.2em;
+  color: #f0f0f0;
+}
+
+#stageElement {
+  display: block;
+  position: fixed;
+  left: 0;
+  top: 0;
+  width: 100%;
+  height: 100%;
+  z-index: -1;
+}
+
+.player,
+.instructions {
+  display: flex;
+  position: fixed;
+  flex-direction: row;
+  align-items: center;
+  justify-content: center;
+  z-index: 100;
+}
+.player > .fa,
+.instructions > .fa {
+  font-size: 320%;
+  color: inherit;
+}
+.player > .content,
+.instructions > .content {
+  margin-left: 1em;
+}
+
+.player {
+  left: 1em;
+  bottom: 1em;
+}
+.player button {
+  display: inline-block;
+  background: none;
+  border: 2px solid rgba(255, 255, 255, 0.8);
+  font: inherit;
+  font-size: 80%;
+  line-height: 1.2em;
+  color: inherit;
+  margin: 2px 0;
+  padding: 2px 6px;
+  border-radius: 4px;
+  cursor: pointer;
+}
+.player button:hover {
+  border-color: rgba(255, 255, 255, 0.6);
+}
+
+.instructions {
+  right: 1em;
+  bottom: 1em;
+}
+
+*, *:before, *:after {
+  margin: 0;
+  padding: 0;
+  border: 0;
+}
+
+html, body {
+  display: block;
+  max-width: 100vw;
+  min-height: 100vh;
+}
+
+body {
+  overflow: hidden;
+  position: relative;
+  background-color: black;
+  background-image: url("https://raw.githubusercontent.com/rainner/codepen-assets/master/images/pinkish_sunset.jpg");
+  background-position: center top;
+  background-repeat: no-repeat;
+  background-size: 170vh;
+  font-family: "Denk One", Arial, sans-serif;
+  font-weight: normal;
+  font-size: 18px;
+  line-height: 1.2em;
+  color: #f0f0f0;
+}
+
+#stageElement {
+  display: block;
+  position: fixed;
+  left: 0;
+  top: 0;
+  width: 100%;
+  height: 100%;
+  z-index: -1;
+}
+
+.player,
+.instructions {
+  display: flex;
+  position: fixed;
+  flex-direction: row;
+  align-items: right;
+  justify-content: center;
+  z-index: 100;
+}
+.player > .fa,
+.instructions > .fa {
+  font-size: 320%;
+  color: inherit;
+}
+.player > .content,
+.instructions > .content {
+  margin-left: 1em;
+}
+
+.player {
+  left: 1em;
+  bottom: 1em;
+}
+.player button {
+  display: inline-block;
+  background: none;
+  border: 2px solid rgba(255, 255, 255, 0.8);
+  font: inherit;
+  font-size: 80%;
+  line-height: 1.2em;
+  color: inherit;
+  margin: 2px 0;
+  padding: 2px 6px;
+  border-radius: 4px;
+  cursor: pointer;
+}
+.player button:hover {
+  border-color: rgba(255, 255, 255, 0.6);
+}
+
+.instructions {
+  right: 1em;
+  bottom: 1em;
+}
+
+.container {
+  position: absolute;
+  transform: translate(-50%, -50%);
+  top: 40%;
+  left: 50%;
+}
+
+.glitch, .glow {
+  color: #dfbfbf;
+  position: relative;
+  font-size: 9vw;
+  animation: glitch 5s 5s infinite;
+}
+
+.glitch::before, .glow::before {
+  content: attr(data-text);
+  position: absolute;
+  left: -2px;
+  text-shadow: -5px 0 magenta;
+  background: black;
+  overflow: hidden;
+  top: 0;
+  animation: noise-1 3s linear infinite alternate-reverse, glitch 5s 5.05s infinite;
+}
+
+.glitch::after, .glow::after {
+  content: attr(data-text);
+  position: absolute;
+  left: 2px;
+  text-shadow: -5px 0 lightgreen;
+  background: black;
+  overflow: hidden;
+  top: 0;
+  animation: noise-2 3s linear infinite alternate-reverse, glitch 5s 5s infinite;
+}
+
+@keyframes glitch {
+  1% {
+    transform: rotateX(10deg) skewX(90deg);
+  }
+  2% {
+    transform: rotateX(0deg) skewX(0deg);
+  }
+}
+@keyframes noise-1 {
+  3.3333333333% {
+    clip-path: inset(95px 0 6px 0);
+  }
+  6.6666666667% {
+    clip-path: inset(22px 0 73px 0);
+  }
+  10% {
+    clip-path: inset(10px 0 11px 0);
+  }
+  13.3333333333% {
+    clip-path: inset(95px 0 3px 0);
+  }
+  16.6666666667% {
+    clip-path: inset(15px 0 28px 0);
+  }
+  20% {
+    clip-path: inset(56px 0 34px 0);
+  }
+  23.3333333333% {
+    clip-path: inset(90px 0 5px 0);
+  }
+  26.6666666667% {
+    clip-path: inset(87px 0 4px 0);
+  }
+  30% {
+    clip-path: inset(90px 0 11px 0);
+  }
+  33.3333333333% {
+    clip-path: inset(40px 0 28px 0);
+  }
+  36.6666666667% {
+    clip-path: inset(13px 0 65px 0);
+  }
+  40% {
+    clip-path: inset(28px 0 50px 0);
+  }
+  43.3333333333% {
+    clip-path: inset(84px 0 4px 0);
+  }
+  46.6666666667% {
+    clip-path: inset(22px 0 52px 0);
+  }
+  50% {
+    clip-path: inset(53px 0 13px 0);
+  }
+  53.3333333333% {
+    clip-path: inset(53px 0 5px 0);
+  }
+  56.6666666667% {
+    clip-path: inset(43px 0 26px 0);
+  }
+  60% {
+    clip-path: inset(35px 0 12px 0);
+  }
+  63.3333333333% {
+    clip-path: inset(98px 0 3px 0);
+  }
+  66.6666666667% {
+    clip-path: inset(98px 0 3px 0);
+  }
+  70% {
+    clip-path: inset(81px 0 12px 0);
+  }
+  73.3333333333% {
+    clip-path: inset(50px 0 51px 0);
+  }
+  76.6666666667% {
+    clip-path: inset(6px 0 93px 0);
+  }
+  80% {
+    clip-path: inset(89px 0 9px 0);
+  }
+  83.3333333333% {
+    clip-path: inset(53px 0 31px 0);
+  }
+  86.6666666667% {
+    clip-path: inset(3px 0 21px 0);
+  }
+  90% {
+    clip-path: inset(73px 0 24px 0);
+  }
+  93.3333333333% {
+    clip-path: inset(60px 0 20px 0);
+  }
+  96.6666666667% {
+    clip-path: inset(98px 0 1px 0);
+  }
+  100% {
+    clip-path: inset(35px 0 16px 0);
+  }
+}
+@keyframes noise-2 {
+  0% {
+    clip-path: inset(28px 0 57px 0);
+  }
+  3.3333333333% {
+    clip-path: inset(72px 0 11px 0);
+  }
+  6.6666666667% {
+    clip-path: inset(69px 0 13px 0);
+  }
+  10% {
+    clip-path: inset(42px 0 37px 0);
+  }
+  13.3333333333% {
+    clip-path: inset(80px 0 1px 0);
+  }
+  16.6666666667% {
+    clip-path: inset(14px 0 34px 0);
+  }
+  20% {
+    clip-path: inset(66px 0 33px 0);
+  }
+  23.3333333333% {
+    clip-path: inset(86px 0 11px 0);
+  }
+  26.6666666667% {
+    clip-path: inset(35px 0 65px 0);
+  }
+  30% {
+    clip-path: inset(70px 0 21px 0);
+  }
+  33.3333333333% {
+    clip-path: inset(61px 0 19px 0);
+  }
+  36.6666666667% {
+    clip-path: inset(36px 0 27px 0);
+  }
+  40% {
+    clip-path: inset(44px 0 4px 0);
+  }
+  43.3333333333% {
+    clip-path: inset(66px 0 15px 0);
+  }
+  46.6666666667% {
+    clip-path: inset(59px 0 33px 0);
+  }
+  50% {
+    clip-path: inset(31px 0 54px 0);
+  }
+  53.3333333333% {
+    clip-path: inset(16px 0 60px 0);
+  }
+  56.6666666667% {
+    clip-path: inset(16px 0 17px 0);
+  }
+  60% {
+    clip-path: inset(64px 0 23px 0);
+  }
+  63.3333333333% {
+    clip-path: inset(78px 0 7px 0);
+  }
+  66.6666666667% {
+    clip-path: inset(40px 0 46px 0);
+  }
+  70% {
+    clip-path: inset(9px 0 9px 0);
+  }
+  73.3333333333% {
+    clip-path: inset(63px 0 6px 0);
+  }
+  76.6666666667% {
+    clip-path: inset(5px 0 7px 0);
+  }
+  80% {
+    clip-path: inset(47px 0 24px 0);
+  }
+  83.3333333333% {
+    clip-path: inset(93px 0 2px 0);
+  }
+  86.6666666667% {
+    clip-path: inset(74px 0 10px 0);
+  }
+  90% {
+    clip-path: inset(75px 0 26px 0);
+  }
+  93.3333333333% {
+    clip-path: inset(88px 0 13px 0);
+  }
+  96.6666666667% {
+    clip-path: inset(87px 0 14px 0);
+  }
+  100% {
+    clip-path: inset(10px 0 18px 0);
+  }
+}
+.scanlines {
+  overflow: hidden;
+  mix-blend-mode: difference;
+}
+
+.scanlines::before {
+  content: "";
+  position: absolute;
+  width: 100%;
+  height: 100%;
+  top: 0;
+  left: 0;
+  background: repeating-linear-gradient(to bottom, transparent 0%, rgba(255, 255, 255, 0.05) 0.5%, transparent 1%);
+  animation: fudge 7s ease-in-out alternate infinite;
+}
+
+@keyframes fudge {
+  from {
+    transform: translate(0px, 0px);
+  }
+  to {
+    transform: translate(0px, 2%);
+  }
+}
+.glow {
+  text-shadow: 0 0 1000px #dfbfbf;
+  color: transparent;
+  position: absolute;
+  top: 0;
+}
+
+@keyframes glitch-2 {
+  1% {
+    transform: rotateX(10deg) skewX(70deg);
+  }
+  2% {
+    transform: rotateX(0deg) skewX(0deg);
+  }
+}
+
+.label{
+  text-align: center; 
+  font-size: 150%;
+  margin: 10px;
+}
+
+button {
+  margin: 20px;
+}
+.custom-btn {
+  width: 130px;
+  height: 40px;
+  color: #fff;
+  border-radius: 5px;
+  padding: 10px 25px;
+  font-family: 'Lato', sans-serif;
+  font-weight: 500;
+  background: transparent;
+  cursor: pointer;
+  transition: all 0.3s ease;
+  position: relative;
+  display: inline-block;
+   box-shadow:inset 2px 2px 2px 0px rgba(255,255,255,.5),
+   7px 7px 20px 0px rgba(0,0,0,.1),
+   4px 4px 5px 0px rgba(0,0,0,.1);
+  outline: none;
+}
+
+/* 15 */
+.btn-15 {
+  background: #b621fe;
+  border: none;
+  z-index: 1;
+}
+.btn-15:after {
+  position: absolute;
+  content: "";
+  width: 0;
+  height: 100%;
+  top: 0;
+  right: 0;
+  z-index: -1;
+  background-color: #663dff;
+  border-radius: 5px;
+   box-shadow:inset 2px 2px 2px 0px rgba(255,255,255,.5),
+   7px 7px 20px 0px rgba(0,0,0,.1),
+   4px 4px 5px 0px rgba(0,0,0,.1);
+  transition: all 0.3s ease;
+}
+.btn-15:hover {
+  color: #fff;
+}
+.btn-15:hover:after {
+  left: 0;
+  width: 100%;
+}
+.btn-15:active {
+  top: 2px;
+}
+
+/* 16 */
+.btn-16 {
+  background: red;
+  border: none;
+  z-index: 1;
+}
+.btn-16:after {
+  position: absolute;
+  content: "";
+  width: 0;
+  height: 100%;
+  top: 0;
+  right: 0;
+  z-index: -1;
+  background-color: orange;
+  border-radius: 5px;
+   box-shadow:inset 2px 2px 2px 0px rgba(255,255,255,.5),
+   7px 7px 20px 0px rgba(0,0,0,.1),
+   4px 4px 5px 0px rgba(0,0,0,.1);
+  transition: all 0.3s ease;
+}
+.btn-16:hover {
+  color: #fff;
+}
+.btn-16:hover:after {
+  left: 0;
+  width: 100%;
+}
+.btn-16:active {
+  top: 2px;
+}
+
+a{
+  color: whitesmoke;
+  text-decoration: none;
+}
+
+.lrn-more-btn{
+  margin: 25% 25% 25% 25%;
+  flex: content;
+}
+
+.custom_landing_logo_clr{
+  color: #feffac;
+  opacity: 30%;
+}
+
+.readme_body{
+  max-width: 1440px;
+}
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/index.html b/TuxTechBlogs/docs/index.html
new file mode 100644
index 0000000..ea43ea9
--- /dev/null
+++ b/TuxTechBlogs/docs/index.html
@@ -0,0 +1,57 @@
+<!DOCTYPE html>
+<html lang="en">
+
+  <head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width,initial-scale=1">
+    <title>Home - TuxTechBlogs</title>
+    <link rel='stylesheet' href='https://stackpath.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css'>
+    <link rel='stylesheet' href='https://fonts.googleapis.com/css?family=Denk+One'>
+    <link rel="stylesheet" href="./index-style.css">
+    <link rel="icon" href="./img/favicon.ico">
+
+  </head>
+
+  <body class="readme_body">
+    <div class="container">
+      <div class="glitch" data-text="TuxTechBlogs">
+        <inline class="custom_landing_logo_clr">TuxTechBlogs<inline>
+      </div>
+      <div class="glow">
+      </div>
+    </div>
+
+    <div class="scanlines">
+      <p class="label">🔎Explore 📝Articles, 🎓Tutorials & 📊Insights In-Depth On 💻Technology</p>
+    </div>
+    <!-- partial:index.partial.html -->
+    <section class="player" id="player">
+      <div class="content">
+        <b>🎵Music Player</b><br />
+        <i>📍Destination: 🚀Mars<br />
+          <button class="custom-btn btn-15">
+            Play music
+          </button>
+          </div>
+    </section>
+    <section class="instructions">
+      <!-- <div class="fa fa-mouse-pointer"></div> -->
+      <div class="content">
+        🛞Steer To Move<br />
+        ⬆️Scroll To Accelerate<br />
+        🔫Left Click To Fire<br />
+        <a href="/readme">
+          <button class="custom-btn btn-16" style="font-weight: bolder;">Learn More</button>
+        </a>
+
+      </div>
+    </section>
+    <!-- partial -->
+    <script src='https://cdnjs.cloudflare.com/ajax/libs/three.js/109/three.min.js'></script>
+    <script src='https://threejsfundamentals.org/threejs/resources/threejs/r105/js/loaders/LoaderSupport.js'></script>
+    <script src='https://threejsfundamentals.org/threejs/resources/threejs/r105/js/loaders/OBJLoader2.js'></script>
+    <script src='https://cdnjs.cloudflare.com/ajax/libs/simplex-noise/2.4.0/simplex-noise.min.js'></script>
+    <script src="./index-script.js"></script>
+  </body>
+
+</html>
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/index.md b/TuxTechBlogs/docs/index.md
deleted file mode 100644
index 2ca1165..0000000
--- a/TuxTechBlogs/docs/index.md
+++ /dev/null
@@ -1,63 +0,0 @@
-🙏 Welcome To [**TuxTechBlogs**](./index.md), This website is created to share study materials & notes related to Computer Science Engineering and its' domains which are popular these days.
-
-🏹 **TuxTechBlogs** is to be a one-stop shop for programmers, both experienced and amateurs alike to brush up their programming & Computer Science skills. The repository contains well documented mini-blogs for a vast variety of programming problems.
-
-
-🔥 Programming problems from some of the best online judges [Leetcode](https://www.leetcode.com), [Codechef](https://www.codechef.com), [InterviewBit](https://https://www.interviewbit.com) etc.
-
-🎉 Each problem has an intuition section, followed by the algorithm and the pseudo-code, and finally the implementation. Additionally, the problems are embellished with explanatory images and animations to provide clarity of thought.
-
-✏️ For now, we are accepting solutions in Python,Java & C++ for the problem solving questions. Contributions are always welcome for solutions in other programming languages. Looking for **JS, Go, Kotlin** contributors.
-
----
-
-<div style="text-align:left">
-    <ul>
-        <ol>🤝 Help Others</ol>
-        <ol>📝 Maintain Documentation</ol>
-        <ol>🗣️ Share Knowledge & Experience</ol>
-    </ul>
-</div>
-
----
-
-<div align="center">
-
-<h3>A Tweet Of Different Thought</h3>
-
-<blockquote class="twitter-tweet"><p lang="en" dir="ltr">How to Get Rich (without getting lucky):</p>&mdash; Naval (@naval) <a href="https://twitter.com/naval/status/1002103360646823936?ref_src=twsrc%5Etfw">May 31, 2018</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
-
-</div>
-
----
-## 📚 CSE Foundation
-
-- ⚙️ [`DevOps Overview And Study Meterials`](devops.md)
-- 💿 [`Operating System`]()
-- 📶 [`Computer Network And Systems`]()
-- 👻 [`Hacking`]()
-- 🌐 [`Distributed Systems And Hardwares`]()
-- 📋 [`Database & Database Management Systems`]()
-
-## 📊 Data Science
-- 🔜 Work in progress
-
-## ☁️ Cloud
-- 🔜 Work in Progress
-
-## 🛸 Web3.0
-- 🔜 Work in Progress
-
-## 🦸 Interview
-- `Interview Experience`
-- `Problem Solving`
-- `System Design (HLD, LLD)`
-- `HR Discussions/ Behavioural Round`
-
-
-## 🚀 Projects layout
-    mkdocs.yml          # The configuration file.
-    docs/
-        index.md        # The documentation homepage.
-        devops.md       # Other markdown pages, images and other
-        *               # More to be added
diff --git a/TuxTechBlogs/docs/readme.md b/TuxTechBlogs/docs/readme.md
new file mode 100644
index 0000000..d4a7e0b
--- /dev/null
+++ b/TuxTechBlogs/docs/readme.md
@@ -0,0 +1,93 @@
+<div style="text-align:center">
+<img src="https://raw.githubusercontent.com/TuxTechLab/Blogs/master/TuxTechBlogs/docs/img/site.png" style="border-radius:10%" width="30%">
+<br>
+<a href="https://blogs.tuxtechlab.com">
+    <h1>
+        TuxTechLab's Blog
+    </h1>
+</a>
+
+</div>
+
+🙏 Welcome To **TuxTechBlog**'s [README.md](./readme.md). A one-stop solution for programmers and tech enthusiasts. Our goal is to talk about trending technology & strategies. For more details, please check the [Code-of-Conduct](./CODE_OF_CONDUCT.md) section.
+
+<!-- Badges For The Pages-->
+<div style="text-align:center">
+
+<h2>
+🛠️ Tech Stack
+</h2>
+
+<table style="width:100%">
+  <tr>
+    <th>COMPONENT</th>
+    <th>DETAILS</th>
+  </tr>
+  <tr>
+    <td>Source Code Management</td>
+    <td><img src="https://img.shields.io/badge/git-%23F05033.svg?style=for-the-badge&logo=git&logoColor=white"><img src="https://img.shields.io/badge/github-%23121011.svg?style=for-the-badge&logo=github&logoColor=white"><img src="https://img.shields.io/badge/GitHub%20Pages-121011.svg?logo=github&style=for-the-badge"><img src="https://img.shields.io/badge/github%20actions-%232671E5.svg?style=for-the-badge&logo=githubactions&logoColor=white"></td>
+  </tr>
+  <tr>
+    <td>Operating Systems</td>
+    <td><img src="https://img.shields.io/badge/docker-%230db7ed.svg?style=for-the-badge&logo=docker&logoColor=white"><img src="https://img.shields.io/badge/Alpine_Linux-0D597F?style=for-the-badge&logo=alpine-linux&logoColor=white"><img src="https://img.shields.io/badge/Ubuntu-E95420?logo=ubuntu&style=for-the-badge&logoColor=white"><img src="https://img.shields.io/badge/Windows-0078D6?&style=for-the-badge&logo=windows&logoColor=white"><img src="https://img.shields.io/badge/macintosh%20-000000?&style=for-the-badge&logo=apple&logoColor=F0F0F0"></td>
+  </tr>
+    <tr>
+    <td>Integrated Development Environment</td>
+    <td><img src="https://img.shields.io/badge/Visual_Studio_Code-0078D4?style=for-the-badge&logo=visual%20studio%20code&logoColor=white"><img src="https://img.shields.io/badge/Material--UI-0081CB?style=for-the-badge&logo=material-ui&logoColor=white"><img src="https://img.shields.io/badge/css3-%231572B6.svg?&style=for-the-badge&logo=css3&logoColor=white"><img src="https://img.shields.io/badge/HTML5-E34F26?style=for-the-badge&logo=html5&logoColor=white"></td>
+  </tr>
+    <tr>
+    <td>Frameworks</td>
+    <td><a href="https://www.mkdocs.org"><b>Mkdocs</b></a>, <a href="https://squidfunk.github.io/mkdocs-material/"><b>Mkdocs-Material</b></a></td>
+  </tr>
+    </tr>
+    <tr>
+    <td>Programming & Scripting Languagues</td>
+    <td><img src="https://img.shields.io/badge/Markdown-000000?style=for-the-badge&logo=markdown&logoColor=white"><img src="https://img.shields.io/badge/Python-3776AB?style=for-the-badge&logo=python&logoColor=white"></td>
+  </tr>
+</table>
+</div>
+
+<div style="text-align:center">
+
+<h2>
+    <a href="https://blogs.tuxtechlab.com">💫 TuxTechBlog</a> GitHub Repo Stats
+</h2>
+
+</div>
+
+> `WORKFLOWS`
+
+[![ci_cd_prod](https://github.com/TuxTechLab/Blogs/actions/workflows/ci_cd_prod.yml/badge.svg)](https://github.com/TuxTechLab/Blogs/actions/workflows/ci_cd_prod.yml)
+[![ci_cd_stage](https://github.com/TuxTechLab/Blogs/actions/workflows/ci_cd_stage.yml/badge.svg)](https://github.com/TuxTechLab/Blogs/actions/workflows/ci_cd_stage.yml)
+
+> `REPOSITORY`
+
+[![License](https://img.shields.io/github/license/TuxTechLab/Blogs.svg?style=for-the-badge)](https://raw.githubusercontent.com/TuxTechLab/Blogs/master/LICENSE)
+[![Website Status](https://img.shields.io/website-up-down-green-red/http/shields.io.svg?style=for-the-badge)](http://blogs.tuxtechlab.com)
+[![Issues](https://img.shields.io/github/issues/TuxTechLab/Blogs?color=0088ff&style=for-the-badge&logo=github)](https://github.com/TuxTechLab/Blogs/issues)
+[![Pull Requests](https://img.shields.io/github/issues-pr/TuxTechLab/Blogs?color=0088ff&style=for-the-badge&logo=github)](https://github.com/TuxTechLab/Blogs/pulls)
+[![Contributors](https://img.shields.io/github/contributors/TuxTechLab/Blogs.svg)](https://github.com/TuxTechLab/Blogs/graphs/contributors/)
+[![Stars](https://img.shields.io/github/stars/TuxTechLab/blogs)](https://github.com/TuxTechLab/Blogs/stargazers)
+
+
+<div style="text-align:center">
+
+<h2>
+✅ Code of Conduct
+</h2>
+
+Learn more from <a href="./CODE_OF_CONDUCT.md"><b>CODE OF CONDUCT</b></a> of <a href="https://blogs.tuxtechlab.com"><b>TuxTechBlogs</b></a>
+
+</div>
+
+<div style="text-align:center">
+
+<h2>
+📞 Conect Us
+</h2>
+
+Please visit <a href="./contacts.md">Contact Us</a> of <a href="https://blogs.tuxtechlab.com"><b>TuxTechBlogs</b></a> to know more.
+
+<p>&copy; 2023<a href="https://blogs.tuxtechlab.com"> TuxTechBlog </a> All rights reserved.</p>
+
+</div>
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/study/.markdownlint.json b/TuxTechBlogs/docs/study/.markdownlint.json
index 25e80d5..451640a 100644
--- a/TuxTechBlogs/docs/study/.markdownlint.json
+++ b/TuxTechBlogs/docs/study/.markdownlint.json
@@ -1,23 +1,23 @@
-{
-    "extends": "./.markdownlint.json",
-    "no-hard-tabs": true,
-    "rules": {
-      "markdown/allow-inline-html": true
-    },
-        "fenced-code-language": {
-        "allowed_languages": [
-          "bash",
-          "html",
-          "C++",
-          "java",
-          "javascript",
-          "json",
-          "markdown",
-          "python",
-          "text"
-        ],
-        "language_only": true
-    }
-}
-
-
+{
+    "extends": "./.markdownlint.json",
+    "no-hard-tabs": true,
+    "rules": {
+      "markdown/allow-inline-html": true
+    },
+        "fenced-code-language": {
+        "allowed_languages": [
+          "bash",
+          "html",
+          "C++",
+          "java",
+          "javascript",
+          "json",
+          "markdown",
+          "python",
+          "text"
+        ],
+        "language_only": true
+    }
+}
+
+
diff --git a/TuxTechBlogs/docs/interview.md b/TuxTechBlogs/docs/study/interview_prep/interview.md
similarity index 100%
rename from TuxTechBlogs/docs/interview.md
rename to TuxTechBlogs/docs/study/interview_prep/interview.md
diff --git a/TuxTechBlogs/docs/stylesheet/extra.css b/TuxTechBlogs/docs/stylesheet/extra.css
index e8df08d..dea8aae 100644
--- a/TuxTechBlogs/docs/stylesheet/extra.css
+++ b/TuxTechBlogs/docs/stylesheet/extra.css
@@ -1,35 +1,35 @@
-/* 
-Copyright (c) 2019-2024 Arindam Tanti <arindamtanti123@gmail.com>
-
-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 NON-INFRINGEMENT. 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
-*/
-
-/* Expanding the grid width of the website */
-
-.md-grid {
-    max-width: 1600px; 
-  }
-
-/* @import url('https://fonts.googleapis.com/css2?family=Readex+Pro:wght@300;400;500;600;700&display=swap');
-* {font-family: 'Readex Pro';} */
-
-@font-face {
-font-family: "Readex Pro";
-src: "https://fonts.googleapis.com/css2?family=Readex+Pro:wght@300;400;500;600;700&display=swap";
-}
\ No newline at end of file
+/* 
+Copyright (c) 2019-2024 TuxTechLabs <root.tuxtechlab@gmail.com>
+
+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 NON-INFRINGEMENT. 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
+*/
+
+/* Expanding the grid width of the website */
+
+.md-grid {
+    max-width: 1440px; 
+  }
+
+.h1#changelog{
+  font-size: 50rem;
+}
+
+.ul{
+  font-size: 20%;
+}
diff --git a/TuxTechBlogs/docs/topic/1.0. Agile/00. Introduction.md b/TuxTechBlogs/docs/topic/1.0. Agile/00. Introduction.md
index e3b032b..d8a7280 100644
--- a/TuxTechBlogs/docs/topic/1.0. Agile/00. Introduction.md	
+++ b/TuxTechBlogs/docs/topic/1.0. Agile/00. Introduction.md	
@@ -1,50 +1,50 @@
-- [**What comes to mind when you think of the word "agility?"**](#what-comes-to-mind-when-you-think-of-the-word-agility)
-- [**How is agile different from traditional project management?**](#how-is-agile-different-from-traditional-project-management)
-- [**Where did agile come from?**](#where-did-agile-come-from)
----
-
-## **What comes to mind when you think of the word "agility?"**
-
-- Agility is the ability to move with quick, effortless grace.
-- You can be agile in the way you work, too. Every day, you can approach your tasks with grace and efficiency.
-- Agile  is a set of ideas, frameworks, and tools to help you manage work more efficiently.
-- The agile ideas encourage you to:
-    1. **Be flexible** and ready for unpredictable change
-    2. **Communicate** often with stakeholders
-    3. **Ship work** in short increments (instead of all at once)
-    4. **Always be learning.**
-- Agile isn't just about following a process. It's about having the right **attitude** and **mindset.**
-
-Being agile allows your team to **prioritize the most critical work** and **get it done efficiently**, ultimately **delivering value to customers more quickly.**
-
-![Agile_Banner](https://media.giphy.com/media/v1.Y2lkPTc5MGI3NjExYWw4OGFxNjdjeGdxZXUyYWwwaWR1aGgwdGxvMjVqd2xpajRteWFpdCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/9hUOqSkJUe7WjmxcN4/giphy.gif)
-
----
-
-## **How is agile different from traditional project management?**
-
-A typical method of managing projects is called the  waterfall  approach. You've probably used this method in your work experience before.
-
-![Agile_vs_WaterFall](https://i.postimg.cc/J0tk19s6/agile-vs-waterfall.png)
-
-|||
-|:----|:----|
-|➡️  Waterfall is a linear approach to managing projects.|🔄  Agile is a continuous approach to managing projects.|
-| First, you define requirements thoroughly before the project begins. Then, you complete each phase of the project in sequential order. At the end, one significant deliverable is completed and shipped.|You stay flexible and respond quickly to changing requirements. You prioritize the work items that create the most value for your customers. Deliverables are completed and shipped continuously, in small increments.|
-
----
-
-## **Where did agile come from?**
-
-- Agile was created to solve a problem. In 2001, a group of tech professionals were frustrated with how software was being built. They felt the traditional waterfall approach was too slow, rigid, and inefficient.The group spent a weekend in the mountains and came up with a new approach to managing software projects. They called it _The Agile Manifesto_.
-- This short, **68-word document** provided new guidelines for building software. It suggested teams prioritize **flexibility**, **constant communication** with stakeholders, and **continuous delivery of work** in short increments.
-
-<br>
-
-> ## **See it for yourself!** Click here to go to website ➡️ **[AGILE MANIFESTO](http://agilemanifesto.org/)**
-
-<br>
-
-- Twenty years later, the ways of working suggested in _The Agile Manifesto_ continue to drive many of the world's highest-performing teams, including a majority of software developers.
-- **But, agile isn't only for software teams.** Remote work has fueled a boom in agile adoption across various teams and organizations, from law firms to marketing agencies.
+- [**What comes to mind when you think of the word "agility?"**](#what-comes-to-mind-when-you-think-of-the-word-agility)
+- [**How is agile different from traditional project management?**](#how-is-agile-different-from-traditional-project-management)
+- [**Where did agile come from?**](#where-did-agile-come-from)
+---
+
+## **What comes to mind when you think of the word "agility?"**
+
+- Agility is the ability to move with quick, effortless grace.
+- You can be agile in the way you work, too. Every day, you can approach your tasks with grace and efficiency.
+- Agile  is a set of ideas, frameworks, and tools to help you manage work more efficiently.
+- The agile ideas encourage you to:
+    1. **Be flexible** and ready for unpredictable change
+    2. **Communicate** often with stakeholders
+    3. **Ship work** in short increments (instead of all at once)
+    4. **Always be learning.**
+- Agile isn't just about following a process. It's about having the right **attitude** and **mindset.**
+
+Being agile allows your team to **prioritize the most critical work** and **get it done efficiently**, ultimately **delivering value to customers more quickly.**
+
+![Agile_Banner](https://media.giphy.com/media/v1.Y2lkPTc5MGI3NjExYWw4OGFxNjdjeGdxZXUyYWwwaWR1aGgwdGxvMjVqd2xpajRteWFpdCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/9hUOqSkJUe7WjmxcN4/giphy.gif)
+
+---
+
+## **How is agile different from traditional project management?**
+
+A typical method of managing projects is called the  waterfall  approach. You've probably used this method in your work experience before.
+
+![Agile_vs_WaterFall](https://i.postimg.cc/J0tk19s6/agile-vs-waterfall.png)
+
+|||
+|:----|:----|
+|➡️  Waterfall is a linear approach to managing projects.|🔄  Agile is a continuous approach to managing projects.|
+| First, you define requirements thoroughly before the project begins. Then, you complete each phase of the project in sequential order. At the end, one significant deliverable is completed and shipped.|You stay flexible and respond quickly to changing requirements. You prioritize the work items that create the most value for your customers. Deliverables are completed and shipped continuously, in small increments.|
+
+---
+
+## **Where did agile come from?**
+
+- Agile was created to solve a problem. In 2001, a group of tech professionals were frustrated with how software was being built. They felt the traditional waterfall approach was too slow, rigid, and inefficient.The group spent a weekend in the mountains and came up with a new approach to managing software projects. They called it _The Agile Manifesto_.
+- This short, **68-word document** provided new guidelines for building software. It suggested teams prioritize **flexibility**, **constant communication** with stakeholders, and **continuous delivery of work** in short increments.
+
+<br>
+
+> ## **See it for yourself!** Click here to go to website ➡️ **[AGILE MANIFESTO](http://agilemanifesto.org/)**
+
+<br>
+
+- Twenty years later, the ways of working suggested in _The Agile Manifesto_ continue to drive many of the world's highest-performing teams, including a majority of software developers.
+- **But, agile isn't only for software teams.** Remote work has fueled a boom in agile adoption across various teams and organizations, from law firms to marketing agencies.
 - **Agile project management can help any team be more nimble, efficient, and flexible** depending on your team structure and deliverables.
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/1.0. Agile/01. Understanding the four values of agile.md b/TuxTechBlogs/docs/topic/1.0. Agile/01. Understanding the four values of agile.md
index 3a5afbc..d7a3226 100644
--- a/TuxTechBlogs/docs/topic/1.0. Agile/01. Understanding the four values of agile.md	
+++ b/TuxTechBlogs/docs/topic/1.0. Agile/01. Understanding the four values of agile.md	
@@ -1,43 +1,43 @@
-## **Why are the values so important?**
-
-> **The four values are the foundation of agile.**
-
-- They are simple and direct guidelines that can help you navigate complex projects and deliver more value to stakeholders. 
-- Once you understand the four values, everything else you learn about agile will be easier to grasp. 
-- Knowing the values will make it easier to:
-    1. Approach your work with an **agile mindset**
-    2. Understand agile frameworks like **kanban and scrum**
-    3. Start using agile tools like **Jira Software**
-
-<br>
-
-> ## 👇 Let's take a closer look at the four values.
-
-<br>
-
-![individual-interactions](https://i.postimg.cc/BZknR8Cf/individual-interactions.png)
-
-1. Successful teams prioritize finding the **right people** and making sure they **communicate frequently**. 
-2. Good tools and processes help, but focusing on the individuals and their interactions will yield the best results.
-    
-    > **For Example:** the world's best guitar is useless to someone that doesn't know how to play it. Making a beautiful song (or product) requires **highly skilled people** that can **collaborate effectively**.
-3. Your team should do the same: **prioritize people** and **communicate often**. Frequent discussions across the team help uncover critical information to keep the work moving forward.
-
-![working_software](https://i.postimg.cc/9F9nCfv7/working-software.png)
-
-1. Successful teams prioritize **delivering a product that works, not to make it perfect.** This value applies to any work you deliver to customers, not just software.
-2. Before agile, teams would try to build against the full scope of project requirements, allowing very little flexibility.
-3. Instead, your team should look for a few critical features to deliver as a  **minimum viable product  (or MVP)**. Then, the team should prioritize building the MVP and get it in the customers' hands as quickly as possible.
-4. This practice gives customers a working product, and it allows your team to get real-time feedback to improve future iterations.
-
-![customer_collaboration](https://i.postimg.cc/x1rqNkk3/customer-collab.png)
-
-1. Successful teams prioritize **frequent collaboration with stakeholders and customers.** Think of your customers as partners, working closely to design the best solution
-2. Before agile, teams would spend a lot of time detailing a final product before the work started. The problem was that these original details rarely ended up providing much value in the end.
-3. Instead, you should **partner closely with your customer** throughout the process and **be ready to adapt to changing needs and requirements**. Gather feedback frequently to help your customers quickly solve their highest priority problems.
-
-![respond_to_change](https://i.postimg.cc/J7fBZYvX/respond-to-change.png)
-
-1. Successful teams **stay flexible and ready to adapt to unforeseen changes.** Starting with a plan is always a good idea, but don't be overly rigid in sticking to it.
-2. It's important to recognize in work (and life) that change is the only constant. Markets, teams, projects, and situations are constantly in flux. 
+## **Why are the values so important?**
+
+> **The four values are the foundation of agile.**
+
+- They are simple and direct guidelines that can help you navigate complex projects and deliver more value to stakeholders. 
+- Once you understand the four values, everything else you learn about agile will be easier to grasp. 
+- Knowing the values will make it easier to:
+    1. Approach your work with an **agile mindset**
+    2. Understand agile frameworks like **kanban and scrum**
+    3. Start using agile tools like **Jira Software**
+
+<br>
+
+> ## 👇 Let's take a closer look at the four values.
+
+<br>
+
+![individual-interactions](https://i.postimg.cc/BZknR8Cf/individual-interactions.png)
+
+1. Successful teams prioritize finding the **right people** and making sure they **communicate frequently**. 
+2. Good tools and processes help, but focusing on the individuals and their interactions will yield the best results.
+    
+    > **For Example:** the world's best guitar is useless to someone that doesn't know how to play it. Making a beautiful song (or product) requires **highly skilled people** that can **collaborate effectively**.
+3. Your team should do the same: **prioritize people** and **communicate often**. Frequent discussions across the team help uncover critical information to keep the work moving forward.
+
+![working_software](https://i.postimg.cc/9F9nCfv7/working-software.png)
+
+1. Successful teams prioritize **delivering a product that works, not to make it perfect.** This value applies to any work you deliver to customers, not just software.
+2. Before agile, teams would try to build against the full scope of project requirements, allowing very little flexibility.
+3. Instead, your team should look for a few critical features to deliver as a  **minimum viable product  (or MVP)**. Then, the team should prioritize building the MVP and get it in the customers' hands as quickly as possible.
+4. This practice gives customers a working product, and it allows your team to get real-time feedback to improve future iterations.
+
+![customer_collaboration](https://i.postimg.cc/x1rqNkk3/customer-collab.png)
+
+1. Successful teams prioritize **frequent collaboration with stakeholders and customers.** Think of your customers as partners, working closely to design the best solution
+2. Before agile, teams would spend a lot of time detailing a final product before the work started. The problem was that these original details rarely ended up providing much value in the end.
+3. Instead, you should **partner closely with your customer** throughout the process and **be ready to adapt to changing needs and requirements**. Gather feedback frequently to help your customers quickly solve their highest priority problems.
+
+![respond_to_change](https://i.postimg.cc/J7fBZYvX/respond-to-change.png)
+
+1. Successful teams **stay flexible and ready to adapt to unforeseen changes.** Starting with a plan is always a good idea, but don't be overly rigid in sticking to it.
+2. It's important to recognize in work (and life) that change is the only constant. Markets, teams, projects, and situations are constantly in flux. 
 3. You and your team will be most successful if you prepare your mind for constant changes and are ready to make intelligent pivots on a whim.
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/1.0. Agile/02. Using agile in everyday work.md b/TuxTechBlogs/docs/topic/1.0. Agile/02. Using agile in everyday work.md
index 04b45fa..81a371e 100644
--- a/TuxTechBlogs/docs/topic/1.0. Agile/02. Using agile in everyday work.md	
+++ b/TuxTechBlogs/docs/topic/1.0. Agile/02. Using agile in everyday work.md	
@@ -1,46 +1,46 @@
-> # **Your goal is to build and cultivate an  agile mindset.**
-
-## Agile mindset...what does that even mean?
-
-1. **It means you approach your day-to-day work with the agile ideas and concepts in mind.** Using agile in practice starts with the way you think. This way of thinking helps you become a more efficient, flexible, and high-performing team member. It allows your mind to be open to continuous learning and improvement.
-2. **As you start building your mindset, remember to be patient with yourself.** Establishing a new way of thinking requires forming new habits, which take time and energy.
-3. Your agile mindset is a long journey that will be developed and refined over many years. This is just the beginning.
-
-## **How do you build an agile mindset?**
-
-1. **Show respect for all the team members.**
-   - **Healthy, high-performing teams create a culture of trust and mutual respect.** That's the backbone of agility.
-   - Having an agile mindset means you embrace different ways of thinking and working, even if you don't always agree with them. Focus on keeping an open mind and seeking to understand new and unexpected ideas.
-2. **Communicate Openly and Clearly.**
-   - **Share updates. Ask questions. Be open and transparent at all times.** With each interaction, challenge yourself to communicate clearly and concisely. 
-   - Encourage your team to engage in frequent discussions. Quality discussions can reveal critical information that moves the work forward and helps the team feel more connected.
-3. **Look for ways to innovate**
-   -  **Agility is all about delivering maximum value to customers.** When a customer's needs change, you need to respond quickly with an innovative solution.
-   -  **Having an agile mindset means you're constantly looking for opportunities to innovate.** This could mean improving your team's internal processes. Or enhancing features of the product you're building.
-   -  As you complete your daily tasks, think if there are ways to improve what you're doing. Analyzing and improving your team's work will be valuable for your future career.
-4. **Actively improve your skills**
-   - Agile is all about continuous improvement. **In your daily work, always look for opportunities to learn and grow your skillset.**
-   - Pause for a minute and think about your current skills: _Which skills seem to be most valuable? Which skills mesh well with your natural tendencies?_ Use these questions as a starting point to help you plan which skills to sharpen.
-   - Prioritizing your skill development is always a good idea. Not only does it help your team, but it also improves your future career opportunities.
-5. **Your work doesn't have to be prefect.**
-   -  **Your goal is to deliver something that works: an MVP. Not to make every detail perfect.**
-   -  Shift your mindset to focus on doing "good enough" work, and then get immediate feedback to improve the next version. Try to adopt this approach for both large and small tasks.
-   -  "Good enough" is different for every team and every project. If the parameters are not clear, you may want to discuss them with your team leader.
-6. **Have a plan, but always ready to pivot.**
-   -  **An agile mindset is about being flexible and ready for any unpredictable change.** Yes, you should always have a Plan A (and B and C, if time allows). But, you'll be most successful at work if your mind is always prepared to pivot.
-   -  Change will come. It always does. Your job is to prepare your brain to stay calm and collected so that you can handle each emotional wave with ease. If everyone on the team is ready for change, you'll be able to bounce back quickly and refocus energy on solving new problems.
-
-> # **Frameworks and mindsets.**
-
-## **What's the difference?**
-
-1. Your agile mindset will help you think about your work in an agile way, regardless of how your team is structured. Most teams looking to take full advantage of agile use a specific agile framework to put the ideas into practice.
-2. An  agile framework  provides specific guidelines for how teams should be organized and structure their work. Kanban and scrum are the two most common agile frameworks.
-
-   ![scrum_vs_kanban](https://i.postimg.cc/c1XbJYbP/scrum-vs-kanban.jpg)
-
-   |||
-   |:----|:----|
-   |Kanban  is a framework that helps your team visualize work and continuously improve. Using a visual board to track work, kanban allows team members to see the status of every work item, at any time.|Scrum  is a framework that focuses on iterative and incremental deliveries. Work gets completed in short, time-boxed increments. Teams are encouraged to reflect and learn from experience, always focused on continuous improvement.|
-
+> # **Your goal is to build and cultivate an  agile mindset.**
+
+## Agile mindset...what does that even mean?
+
+1. **It means you approach your day-to-day work with the agile ideas and concepts in mind.** Using agile in practice starts with the way you think. This way of thinking helps you become a more efficient, flexible, and high-performing team member. It allows your mind to be open to continuous learning and improvement.
+2. **As you start building your mindset, remember to be patient with yourself.** Establishing a new way of thinking requires forming new habits, which take time and energy.
+3. Your agile mindset is a long journey that will be developed and refined over many years. This is just the beginning.
+
+## **How do you build an agile mindset?**
+
+1. **Show respect for all the team members.**
+   - **Healthy, high-performing teams create a culture of trust and mutual respect.** That's the backbone of agility.
+   - Having an agile mindset means you embrace different ways of thinking and working, even if you don't always agree with them. Focus on keeping an open mind and seeking to understand new and unexpected ideas.
+2. **Communicate Openly and Clearly.**
+   - **Share updates. Ask questions. Be open and transparent at all times.** With each interaction, challenge yourself to communicate clearly and concisely. 
+   - Encourage your team to engage in frequent discussions. Quality discussions can reveal critical information that moves the work forward and helps the team feel more connected.
+3. **Look for ways to innovate**
+   -  **Agility is all about delivering maximum value to customers.** When a customer's needs change, you need to respond quickly with an innovative solution.
+   -  **Having an agile mindset means you're constantly looking for opportunities to innovate.** This could mean improving your team's internal processes. Or enhancing features of the product you're building.
+   -  As you complete your daily tasks, think if there are ways to improve what you're doing. Analyzing and improving your team's work will be valuable for your future career.
+4. **Actively improve your skills**
+   - Agile is all about continuous improvement. **In your daily work, always look for opportunities to learn and grow your skillset.**
+   - Pause for a minute and think about your current skills: _Which skills seem to be most valuable? Which skills mesh well with your natural tendencies?_ Use these questions as a starting point to help you plan which skills to sharpen.
+   - Prioritizing your skill development is always a good idea. Not only does it help your team, but it also improves your future career opportunities.
+5. **Your work doesn't have to be prefect.**
+   -  **Your goal is to deliver something that works: an MVP. Not to make every detail perfect.**
+   -  Shift your mindset to focus on doing "good enough" work, and then get immediate feedback to improve the next version. Try to adopt this approach for both large and small tasks.
+   -  "Good enough" is different for every team and every project. If the parameters are not clear, you may want to discuss them with your team leader.
+6. **Have a plan, but always ready to pivot.**
+   -  **An agile mindset is about being flexible and ready for any unpredictable change.** Yes, you should always have a Plan A (and B and C, if time allows). But, you'll be most successful at work if your mind is always prepared to pivot.
+   -  Change will come. It always does. Your job is to prepare your brain to stay calm and collected so that you can handle each emotional wave with ease. If everyone on the team is ready for change, you'll be able to bounce back quickly and refocus energy on solving new problems.
+
+> # **Frameworks and mindsets.**
+
+## **What's the difference?**
+
+1. Your agile mindset will help you think about your work in an agile way, regardless of how your team is structured. Most teams looking to take full advantage of agile use a specific agile framework to put the ideas into practice.
+2. An  agile framework  provides specific guidelines for how teams should be organized and structure their work. Kanban and scrum are the two most common agile frameworks.
+
+   ![scrum_vs_kanban](https://i.postimg.cc/c1XbJYbP/scrum-vs-kanban.jpg)
+
+   |||
+   |:----|:----|
+   |Kanban  is a framework that helps your team visualize work and continuously improve. Using a visual board to track work, kanban allows team members to see the status of every work item, at any time.|Scrum  is a framework that focuses on iterative and incremental deliveries. Work gets completed in short, time-boxed increments. Teams are encouraged to reflect and learn from experience, always focused on continuous improvement.|
+
 3. **Agile itself is not a framework.** This is important to understand. Agile is a set of ideas, but it does not provide instructions on how to apply those ideas to your work. That's what agile frameworks, like kanban and scrum, are meant to accomplish.
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/11.0. Kanban/00. Introduction.md b/TuxTechBlogs/docs/topic/11.0. Kanban/00. Introduction.md
index 9a72b02..1b06b7b 100644
--- a/TuxTechBlogs/docs/topic/11.0. Kanban/00. Introduction.md	
+++ b/TuxTechBlogs/docs/topic/11.0. Kanban/00. Introduction.md	
@@ -1,109 +1,109 @@
-- [**What is kanban**](#what-is-kanban)
-- [**Kanban Principles**](#kanban-principles)
-- [**How do different teams use kanban?**](#how-do-different-teams-use-kanban)
-- [**Understanding from Examples**](#understanding-from-examples)
-- [**Getting Started with Kanban And Terminologies**](#getting-started-with-kanban-and-terminologies)
-
----
-
-## **What is kanban**
-
-> ### **Adopted by millions of teams across the world, kanban can help any team manage complex projects.**
-
-- **Kanban**  is an agile framework that helps your team visualize work and continuously improve. In Japanese, kanban roughly translates to _"visual signal."_ 
-
-- Kanban is a **more flexible** approach than scrum. It suggests you build a process starting from what you currently have.
-
----
-
-## **Kanban Principles**
-
-> ### **Kanban has four principles.**
-
-- **Visualize your workflow** using a kanban board to make work items visible to everyone. This allows team members and stakeholders to have constant insight on work progress.
-
-- **Set limits on your works in progress** (WIP), the number of work items that can be "in progress" at any given time. This helps your team reduce workloads, improve flow, and deliver in shorter increments.
-
-- **Manage the flow of work** with a system that flows freely and is as predictable as possible. Address blockers immediately, so you can reduce lead times and deliver maximum value to customers.
-
-- **Continuously improve** by reviewing and monitoring your system frequently. Prioritize small improvements that make the biggest impact on outcomes.
-
----
-
-## **How do different teams use kanban?**
-
-> ### **Any team in any industry can use kanban.**
-
-- While the framework was originally created to improve manufacturing practices, kanban has been adopted by all types of business teams, from software development to marketing.
-
----
-
-## **Understanding from Examples**
-
-> ### **Example1: Software Development Team**
-
-  - **Payton is a software developer at NotDog, LLC**. They make an iOS app where users can vote if an image is a hotdog or not a hotdog. 
-
-  - Payton is on a support team that fixes bugs submitted by customers. Tickets are submitted every few minutes, so the support team has a long backlog of bugs to fix.
-
-    ![KANBAN_sw_dev](https://i.postimg.cc/tggDdb7p/KANBAN-sw-dev.jpg)
-
-  - To keep the tickets organized, Payton's team uses a kanban board. Their workflow is: **New Request, In Progress, Code Review, Complete.**
-
-  - A customer just submitted a bug about an error message blocking the hotdog photos. When submitted, a new card is created in the **New Request** column. The work item gets assigned to Payton. He reads the details, begins the work, and moves the card to **In Progress** on the board.
-
-  - After a few hours, Payton fixes the bug! He pulls the card to **Code Review** so another team member can check the work. Once approved, the team member moves the card to **Complete**. Payton is ready to pull his next card from the backlog.
-
-> ### **Example2: Marketing team**
-
-  - Camila is a graphic designer at Rental Chickens, Inc. They supply rentable backyard chickens and coops to aspiring farmers.
-  
-  - With National Chicken Month coming in September, Camila's marketing team is launching a campaign to help boost chicken rentals.
-
-    ![KANBAN_marketing](https://i.postimg.cc/Mp5djH69/KANBAN-marketing.jpg)
-
-  - The team has tasks such as: create a social media strategy, conduct keyword research, write copy, and design the artwork. Their tasks are organized on a kanban board with the workflow: **To Do, In Progress, Waiting Approval, Complete.**
-  
-  - Camila's task is to design the artwork based on the social media strategy. As soon as she begins the work, she moves her card from **To Do** to **In Progress.**
-  
-  - She creates a set of farm-inspired art for the social media campaign and pulls the card into **Waiting Approval**. Camila pulls a new card from the backlog to keep her work flowing as she waits. Once the social media artwork is approved, Camila's task is complete! She can now focus her energy fully on her new item.
-
----
-
-## **Getting Started with Kanban And Terminologies**
-
-1. ### **Understand Kanban Basics**
-
-     - Knowing the fundamentals of the framework gives you a significant advantage as you start working on a kanban team. 
-
-     - Make sure you know **why your team uses kanban and how your team is organizing the work.** 
-
-2. ### **Know your team's workflow**
-
-     - As you saw in the examples above, every team has a different workflow. So as you get started in kanban, **make it a priority to understand your team's workflow**
-     
-     - Knowing your workflow will help you plan your daily work and understand how you fit into the bigger picture.
-
-3. ### **Don't work on too many things at once**
-
-     - One of the big ideas behind kanban is to **focus your work on just a couple of tasks at one time**.
-
-     - It's easy to slip into bad habits of multitasking. To follow the kanban framework properly, always remember to minimize the number of tasks you have in progress. It's often better to complete one task before moving on to the next.
-
-4. ### **Communicate Often**
-
-     - The benefit of a visual system is that **everyone across the team can see the work**. It's your job to update your work on the board and add relevant information for your teammates and stakeholders.
-     
-     - Always opt for over-communication, especially as you get started. Many teams schedule a daily meeting to go through their board and discuss blockers. Add comments and mention relevant people when you have questions or updates.
-
-5. ### **Know your team's working agreements**
-
-     - Every team has different processes and best practices. You'll be most successful if you **focus on understanding what your team has agreed upon**.
-     
-     - Having a firm grasp of your team's working agreements will help you better prioritize your work and collaborate more effectively with the group.
-
-6. **Use your agile mindset**
-
-     - The best way to provide long-term value to your team is to approach your work with an agile mindset.
-
+- [**What is kanban**](#what-is-kanban)
+- [**Kanban Principles**](#kanban-principles)
+- [**How do different teams use kanban?**](#how-do-different-teams-use-kanban)
+- [**Understanding from Examples**](#understanding-from-examples)
+- [**Getting Started with Kanban And Terminologies**](#getting-started-with-kanban-and-terminologies)
+
+---
+
+## **What is kanban**
+
+> ### **Adopted by millions of teams across the world, kanban can help any team manage complex projects.**
+
+- **Kanban**  is an agile framework that helps your team visualize work and continuously improve. In Japanese, kanban roughly translates to _"visual signal."_ 
+
+- Kanban is a **more flexible** approach than scrum. It suggests you build a process starting from what you currently have.
+
+---
+
+## **Kanban Principles**
+
+> ### **Kanban has four principles.**
+
+- **Visualize your workflow** using a kanban board to make work items visible to everyone. This allows team members and stakeholders to have constant insight on work progress.
+
+- **Set limits on your works in progress** (WIP), the number of work items that can be "in progress" at any given time. This helps your team reduce workloads, improve flow, and deliver in shorter increments.
+
+- **Manage the flow of work** with a system that flows freely and is as predictable as possible. Address blockers immediately, so you can reduce lead times and deliver maximum value to customers.
+
+- **Continuously improve** by reviewing and monitoring your system frequently. Prioritize small improvements that make the biggest impact on outcomes.
+
+---
+
+## **How do different teams use kanban?**
+
+> ### **Any team in any industry can use kanban.**
+
+- While the framework was originally created to improve manufacturing practices, kanban has been adopted by all types of business teams, from software development to marketing.
+
+---
+
+## **Understanding from Examples**
+
+> ### **Example1: Software Development Team**
+
+  - **Payton is a software developer at NotDog, LLC**. They make an iOS app where users can vote if an image is a hotdog or not a hotdog. 
+
+  - Payton is on a support team that fixes bugs submitted by customers. Tickets are submitted every few minutes, so the support team has a long backlog of bugs to fix.
+
+    ![KANBAN_sw_dev](https://i.postimg.cc/tggDdb7p/KANBAN-sw-dev.jpg)
+
+  - To keep the tickets organized, Payton's team uses a kanban board. Their workflow is: **New Request, In Progress, Code Review, Complete.**
+
+  - A customer just submitted a bug about an error message blocking the hotdog photos. When submitted, a new card is created in the **New Request** column. The work item gets assigned to Payton. He reads the details, begins the work, and moves the card to **In Progress** on the board.
+
+  - After a few hours, Payton fixes the bug! He pulls the card to **Code Review** so another team member can check the work. Once approved, the team member moves the card to **Complete**. Payton is ready to pull his next card from the backlog.
+
+> ### **Example2: Marketing team**
+
+  - Camila is a graphic designer at Rental Chickens, Inc. They supply rentable backyard chickens and coops to aspiring farmers.
+  
+  - With National Chicken Month coming in September, Camila's marketing team is launching a campaign to help boost chicken rentals.
+
+    ![KANBAN_marketing](https://i.postimg.cc/Mp5djH69/KANBAN-marketing.jpg)
+
+  - The team has tasks such as: create a social media strategy, conduct keyword research, write copy, and design the artwork. Their tasks are organized on a kanban board with the workflow: **To Do, In Progress, Waiting Approval, Complete.**
+  
+  - Camila's task is to design the artwork based on the social media strategy. As soon as she begins the work, she moves her card from **To Do** to **In Progress.**
+  
+  - She creates a set of farm-inspired art for the social media campaign and pulls the card into **Waiting Approval**. Camila pulls a new card from the backlog to keep her work flowing as she waits. Once the social media artwork is approved, Camila's task is complete! She can now focus her energy fully on her new item.
+
+---
+
+## **Getting Started with Kanban And Terminologies**
+
+1. ### **Understand Kanban Basics**
+
+     - Knowing the fundamentals of the framework gives you a significant advantage as you start working on a kanban team. 
+
+     - Make sure you know **why your team uses kanban and how your team is organizing the work.** 
+
+2. ### **Know your team's workflow**
+
+     - As you saw in the examples above, every team has a different workflow. So as you get started in kanban, **make it a priority to understand your team's workflow**
+     
+     - Knowing your workflow will help you plan your daily work and understand how you fit into the bigger picture.
+
+3. ### **Don't work on too many things at once**
+
+     - One of the big ideas behind kanban is to **focus your work on just a couple of tasks at one time**.
+
+     - It's easy to slip into bad habits of multitasking. To follow the kanban framework properly, always remember to minimize the number of tasks you have in progress. It's often better to complete one task before moving on to the next.
+
+4. ### **Communicate Often**
+
+     - The benefit of a visual system is that **everyone across the team can see the work**. It's your job to update your work on the board and add relevant information for your teammates and stakeholders.
+     
+     - Always opt for over-communication, especially as you get started. Many teams schedule a daily meeting to go through their board and discuss blockers. Add comments and mention relevant people when you have questions or updates.
+
+5. ### **Know your team's working agreements**
+
+     - Every team has different processes and best practices. You'll be most successful if you **focus on understanding what your team has agreed upon**.
+     
+     - Having a firm grasp of your team's working agreements will help you better prioritize your work and collaborate more effectively with the group.
+
+6. **Use your agile mindset**
+
+     - The best way to provide long-term value to your team is to approach your work with an agile mindset.
+
      - As you go through your daily work, challenge yourself to pause and consider how best to shift your mindset toward **flexibility**, **efficiency**, and **openness**. 
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/11.0. Kanban/01. Kanban Using Jira.md b/TuxTechBlogs/docs/topic/11.0. Kanban/01. Kanban Using Jira.md
index b326970..5b18021 100644
--- a/TuxTechBlogs/docs/topic/11.0. Kanban/01. Kanban Using Jira.md	
+++ b/TuxTechBlogs/docs/topic/11.0. Kanban/01. Kanban Using Jira.md	
@@ -1,93 +1,93 @@
-- [**What's a kanban board?**](#whats-a-kanban-board)
-- [**5 Components of Kanban Board**](#5-components-of-kanban-board)
-- [**How can you see your kanban board?**](#how-can-you-see-your-kanban-board)
-
----
-
-## **What's a kanban board?**
-
-> ### **why is kanban board an important part of kanban?**
-    
-- A kanban board  is a physical or virtual board that shows tasks visually moving through a workflow from beginning to end.
-
-- The board allows everyone on the team to have full transparency of the project and see how the work is organized. It also helps identify blockers and dependencies so work can continue mov
-
-- The most basic kanban board has three columns: To Do, In Progress, and Complete. Columns can be added or changed based on your team's needs. Here's an example of a simple kanban board.
-
-    ![KANBAN_simple_board](https://i.postimg.cc/sx8Rzm8Z/KANBAN-simple-board.gif)
-
-    ```shell
-    Kanban is a "pull" system. That means the team pulls new work items to the board when they have capacity. 
-
-    This is different than a "push" system, where tasks are pushed to the team at a whim. Pull systems prevent anyone from being overwhelmed with too many tasks at one time.
-    ```
-
----
-
-## **5 Components of Kanban Board**
-
-- **The board is the foundation of the kanban framework**. It's where all your work is organized and documented. You can think of the board as the source of truth for all work across your team.
-
-- _Below are the five components of Kanban:_
-  
-  1. **Cards**
-     
-     - A  card  represents an individual work item. Cards are the key "visual 
-     signals" on a kanban board. They help your team track the progress of work.
-     
-     - Each card provides additional information about the work item, such as the due date, assignee, and attachments.
-     
-     - Cards are assigned an owner responsible for the work. The owner moves the card across the board as they complete the work (To Do, In Progress, Complete, etc.). 
-     This system allows everyone to track the progress of work visually.
-
-  2. **Columns**
-
-     - **The  columns  on a board represent a workflow**. Cards move across columns on the board.
-
-     - The most basic kanban board has three columns: **To Do**, **In Progress**, and **Complete**. Your team can customize these columns based on your workflow.
-       
-       ![KANBAN_columns](https://i.postimg.cc/sxf2xTw6/KANBAN-columns.gif)
-
-  3. **Work in Progress Limits**
-     
-     - **A  work-in-progress  limit sets the maximum amount of work that can be in one column at any given time.** When a column reaches its maximum, this is a warning sign that the team has over-committed too much work.
-     
-     - For example, a team could set maximum for the **In Progress** column to two. The team determines both minimum and maximum limits based on how much work they can handle.
-     
-     - **Why have limits?** Many reasons! First, it prevents multitasking and improves focus by having the team work on a smaller set of tasks. It also makes it easier to identify blockers and inefficiencies in the workflow. 
-     
-     - It's almost always better to complete your original work item first than start dozens of new ones.
-       
-       ![KANBAN_WIP_limit](https://i.postimg.cc/mZVDJGg0/KANBAN-WIP-limit.gif)
-
-  4. **Commitment Point**
-  
-     - Kanban teams often have a backlog of work items, which they can choose to take on when they have capacity. 
-     
-     - **The  commitment point  is the moment when an item moves from the backlog to the board**. This is a big deal. You're committing to your customer that you will complete this work item.
-     
-     - Before pulling any backlog item to the board, make sure you and your team fully understand the task. For example, has the team reviewed the item in detail? Do they have all the information they need?
-     
-     - Before you cross the commitment point, make sure you understand what you're taking on.
-
-  5. **Delivery Point**
-
-     - The  delivery point  is when an item of work is complete. 
-     
-     - How do you know for sure that a task is complete? Each card has agreed-upon exit criteria, the requirements for the card to move to the next stage in the workflow. Once the requirements are met, the team can move the card to the delivery point.
-     
-     - In kanban, the team’s goal is to move cards from the commitment point to the delivery point as fast as possible. The elapsed time between the two is the lead time. This is the total time your customer is waiting for their project to be delivered.
-
----
-
-## **How can you see your kanban board?**
-
-> ### **If your team uses kanban, your kanban board will be your home base in Jira Software.**
-
-  - To view your board in Jira, navigate to the left sidebar and select **Board** or **Kanban board.**
-
-    ![KANBAN_board-nav](https://i.postimg.cc/8cyz6LY1/KANBAN-board-nav.gif)
-
-    > **💡Tip**
-    >
-    > If you don't see a Board or Kanban board option in your sidebar, you might be in a scrum board. You may need to change to a different board, or your team may not have a kanban board yet.
+- [**What's a kanban board?**](#whats-a-kanban-board)
+- [**5 Components of Kanban Board**](#5-components-of-kanban-board)
+- [**How can you see your kanban board?**](#how-can-you-see-your-kanban-board)
+
+---
+
+## **What's a kanban board?**
+
+> ### **why is kanban board an important part of kanban?**
+    
+- A kanban board  is a physical or virtual board that shows tasks visually moving through a workflow from beginning to end.
+
+- The board allows everyone on the team to have full transparency of the project and see how the work is organized. It also helps identify blockers and dependencies so work can continue mov
+
+- The most basic kanban board has three columns: To Do, In Progress, and Complete. Columns can be added or changed based on your team's needs. Here's an example of a simple kanban board.
+
+    ![KANBAN_simple_board](https://i.postimg.cc/sx8Rzm8Z/KANBAN-simple-board.gif)
+
+    ```shell
+    Kanban is a "pull" system. That means the team pulls new work items to the board when they have capacity. 
+
+    This is different than a "push" system, where tasks are pushed to the team at a whim. Pull systems prevent anyone from being overwhelmed with too many tasks at one time.
+    ```
+
+---
+
+## **5 Components of Kanban Board**
+
+- **The board is the foundation of the kanban framework**. It's where all your work is organized and documented. You can think of the board as the source of truth for all work across your team.
+
+- _Below are the five components of Kanban:_
+  
+  1. **Cards**
+     
+     - A  card  represents an individual work item. Cards are the key "visual 
+     signals" on a kanban board. They help your team track the progress of work.
+     
+     - Each card provides additional information about the work item, such as the due date, assignee, and attachments.
+     
+     - Cards are assigned an owner responsible for the work. The owner moves the card across the board as they complete the work (To Do, In Progress, Complete, etc.). 
+     This system allows everyone to track the progress of work visually.
+
+  2. **Columns**
+
+     - **The  columns  on a board represent a workflow**. Cards move across columns on the board.
+
+     - The most basic kanban board has three columns: **To Do**, **In Progress**, and **Complete**. Your team can customize these columns based on your workflow.
+       
+       ![KANBAN_columns](https://i.postimg.cc/sxf2xTw6/KANBAN-columns.gif)
+
+  3. **Work in Progress Limits**
+     
+     - **A  work-in-progress  limit sets the maximum amount of work that can be in one column at any given time.** When a column reaches its maximum, this is a warning sign that the team has over-committed too much work.
+     
+     - For example, a team could set maximum for the **In Progress** column to two. The team determines both minimum and maximum limits based on how much work they can handle.
+     
+     - **Why have limits?** Many reasons! First, it prevents multitasking and improves focus by having the team work on a smaller set of tasks. It also makes it easier to identify blockers and inefficiencies in the workflow. 
+     
+     - It's almost always better to complete your original work item first than start dozens of new ones.
+       
+       ![KANBAN_WIP_limit](https://i.postimg.cc/mZVDJGg0/KANBAN-WIP-limit.gif)
+
+  4. **Commitment Point**
+  
+     - Kanban teams often have a backlog of work items, which they can choose to take on when they have capacity. 
+     
+     - **The  commitment point  is the moment when an item moves from the backlog to the board**. This is a big deal. You're committing to your customer that you will complete this work item.
+     
+     - Before pulling any backlog item to the board, make sure you and your team fully understand the task. For example, has the team reviewed the item in detail? Do they have all the information they need?
+     
+     - Before you cross the commitment point, make sure you understand what you're taking on.
+
+  5. **Delivery Point**
+
+     - The  delivery point  is when an item of work is complete. 
+     
+     - How do you know for sure that a task is complete? Each card has agreed-upon exit criteria, the requirements for the card to move to the next stage in the workflow. Once the requirements are met, the team can move the card to the delivery point.
+     
+     - In kanban, the team’s goal is to move cards from the commitment point to the delivery point as fast as possible. The elapsed time between the two is the lead time. This is the total time your customer is waiting for their project to be delivered.
+
+---
+
+## **How can you see your kanban board?**
+
+> ### **If your team uses kanban, your kanban board will be your home base in Jira Software.**
+
+  - To view your board in Jira, navigate to the left sidebar and select **Board** or **Kanban board.**
+
+    ![KANBAN_board-nav](https://i.postimg.cc/8cyz6LY1/KANBAN-board-nav.gif)
+
+    > **💡Tip**
+    >
+    > If you don't see a Board or Kanban board option in your sidebar, you might be in a scrum board. You may need to change to a different board, or your team may not have a kanban board yet.
diff --git a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/01. Introduction.md b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/01. Introduction.md
index d5d9161..9f320b4 100644
--- a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/01. Introduction.md	
+++ b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/01. Introduction.md	
@@ -1,16 +1,16 @@
-# **Introduction**
-
-- [**Introduction**](#introduction)
-  - [**Brief**](#brief)
-
----
-
-## **Brief**
-
-1. Now, most of us have a lot of meetings on our calendar. And in some way it makes sense, right? Meetings can be a helpful tool for us all to communicate.
-
-2. But the problem that we've all experienced is that most meetings are painful expensive and really just a waste of time. So why are our meetings like this?
-
-3. Well, the truth is that running effective meetings is a skill you can build over time. It's a skill that's valuable for anyone to learn at any level in organization. Because we all have to spend time in meetings, right? So we might as well use that time to be productive, efficient, and hey, maybe even enjoy our time together.
-
-4. Well, that's what you're about to learn the best practices to make your meetings the most valuable and effective they can be. Following this chapter you'll be able to lead highly focused and efficient meetings, create clear meeting goals and agendas, keep your attendees actively involved and engaged, and use the Playbooks to improve meeting success.
+# **Introduction**
+
+- [**Introduction**](#introduction)
+  - [**Brief**](#brief)
+
+---
+
+## **Brief**
+
+1. Now, most of us have a lot of meetings on our calendar. And in some way it makes sense, right? Meetings can be a helpful tool for us all to communicate.
+
+2. But the problem that we've all experienced is that most meetings are painful expensive and really just a waste of time. So why are our meetings like this?
+
+3. Well, the truth is that running effective meetings is a skill you can build over time. It's a skill that's valuable for anyone to learn at any level in organization. Because we all have to spend time in meetings, right? So we might as well use that time to be productive, efficient, and hey, maybe even enjoy our time together.
+
+4. Well, that's what you're about to learn the best practices to make your meetings the most valuable and effective they can be. Following this chapter you'll be able to lead highly focused and efficient meetings, create clear meeting goals and agendas, keep your attendees actively involved and engaged, and use the Playbooks to improve meeting success.
diff --git a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/02. Event Determination.md b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/02. Event Determination.md
index 8443c66..673ce11 100644
--- a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/02. Event Determination.md	
+++ b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/02. Event Determination.md	
@@ -1,53 +1,53 @@
-# **Event Determination**
-
-- [**Event Determination**](#event-determination)
-  - [**Determine, do you really the meeting ?**](#determine-do-you-really-the-meeting-)
-  - [**So, how do you determine if you really need that meeting or if there's some better way to spend that time?**](#so-how-do-you-determine-if-you-really-need-that-meeting-or-if-theres-some-better-way-to-spend-that-time)
-
----
-
-## **Determine, do you really the meeting ?**
-
-1. Now, most of our calendars are packed with meetings. Sometimes being double booked or even triple booked. _But do we really need all these meetings on the calendar? Is this the most effective way to get things done?
-
-2. Meetings have become this thing where we just have a lot of them, and they don't always feel great. And so there's that question of going **does this need to be in a meeting?**
-
----
-
-## **So, how do you determine if you really need that meeting or if there's some better way to spend that time?**
-
-- When determining whether or not you need a meeting, there's **three things I like to think about:**
-
-   1. One, **what are you trying to solve, really? What's the outcome you're trying to get to? Are you trying to collaborate on a problem? Are you trying to share information with soemone else?** Really getting to kind of the crux of what it means to actually succeed in this meeting. What's the outcome we want to get to?
-
-   2. Number two, **what's the best way to achieve this?** You always default to a meeting, so you have to change that behavior. Maybe it could be an instant message. It could be Confluence page.
-
-   3. Suppose you work with a team right now that actually spends most of its time in different parts of the globe which is really hard for you to collaborate. So what you done is kind of come up with new ways to collaborate that doesn't involve a meeting.
-
-   4. You use things like Confluence to actually co-create documentation around the globe around, you know around the clock. And then use tools like Loom/ Youtube/ Diagram/ Confluence KB to allow us to kind of go and express maybe our thoughts on what's going on.
-
-   5. **What have I done in the last week or what have I done since yesterday and be able to share that back** because it's a lot easier than maybe writing something down or trying to articulate an idea. That's just too complex.
-
-   6. These Loom videos and Confluence pages to give an opportunity to kind of figure out how do you want to work the next day and then that way we have only certain touch points.
-
-   7. You need to worry about with each other versus trying to have a daily meeting to stay in sync. And finally the third thing you need to think about: **who actually needs to be at that meeting?**
-
-   8. **Are you meeting with a person or are you meeting with a group?** If you're meeting with a person, is this something that you need to have a meeting for or is it best done through an instant message or some sort of other collaboration means?
-
-   9. If it's a group, **what are you trying to share? Are you just trying to share information?** If you're just trying to share information, maybe that's also done better through sharing out something like a Confluence page and a Loom.
-
-   10. Again, when you're thinking about the meetings that you have today, don't default to just have the meeting. Think about **how could  do this a little differently?**
-
-   11. If I need help answering these questions, Atlassian has actually come up with kind of a cheeky, fun view of how we can better identify whether or not we need to have a meeting. They call it the **"why do I want to call this meeting?" decision tree.** So if you walk through it, it kind of gives you these fun areas to say maybe I'm trying to share information or maybe I want to build relationships.
-
-       ![MEETING_decision_tree](https://i.postimg.cc/c4ZRMW52/MEETING-decision-tree.jpg)
-
-   12. And it starts asking me some questions like is this a one-on-one is this just trying to push information out there and it helps you kind of determine whether or not you actually need to hold this meeting.
-
-       - For example, you probably don't need to have a meeting to let's say read through the contents of a Confluence page you just sent. Or if you just don't know any other way to collaborate. Trust me, there are other ways to collaborate that don't involve a meeting.
-
-   13. Now the thing is, is this chart is great. It's fun. It's something that Atlassian use. But based on your organizational behaviors your cultural behaviors in your organization, you may actually want to come up with your own.
-
-   14. Work with the organization or even just your own team to create a meeting decision tree of your own in order to improve your meeting culture. You can then use your decision tree as a working agreement to eliminate unnecessary meetings and promote better meeting behaviors.
-
-   15. Again, find what works best for you. I usually try to lead with if I couldn't have a meeting for this how else could I get it accomplished? Put it into a decision tree to help you kind of think through that.
+# **Event Determination**
+
+- [**Event Determination**](#event-determination)
+  - [**Determine, do you really the meeting ?**](#determine-do-you-really-the-meeting-)
+  - [**So, how do you determine if you really need that meeting or if there's some better way to spend that time?**](#so-how-do-you-determine-if-you-really-need-that-meeting-or-if-theres-some-better-way-to-spend-that-time)
+
+---
+
+## **Determine, do you really the meeting ?**
+
+1. Now, most of our calendars are packed with meetings. Sometimes being double booked or even triple booked. _But do we really need all these meetings on the calendar? Is this the most effective way to get things done?
+
+2. Meetings have become this thing where we just have a lot of them, and they don't always feel great. And so there's that question of going **does this need to be in a meeting?**
+
+---
+
+## **So, how do you determine if you really need that meeting or if there's some better way to spend that time?**
+
+- When determining whether or not you need a meeting, there's **three things I like to think about:**
+
+   1. One, **what are you trying to solve, really? What's the outcome you're trying to get to? Are you trying to collaborate on a problem? Are you trying to share information with soemone else?** Really getting to kind of the crux of what it means to actually succeed in this meeting. What's the outcome we want to get to?
+
+   2. Number two, **what's the best way to achieve this?** You always default to a meeting, so you have to change that behavior. Maybe it could be an instant message. It could be Confluence page.
+
+   3. Suppose you work with a team right now that actually spends most of its time in different parts of the globe which is really hard for you to collaborate. So what you done is kind of come up with new ways to collaborate that doesn't involve a meeting.
+
+   4. You use things like Confluence to actually co-create documentation around the globe around, you know around the clock. And then use tools like Loom/ Youtube/ Diagram/ Confluence KB to allow us to kind of go and express maybe our thoughts on what's going on.
+
+   5. **What have I done in the last week or what have I done since yesterday and be able to share that back** because it's a lot easier than maybe writing something down or trying to articulate an idea. That's just too complex.
+
+   6. These Loom videos and Confluence pages to give an opportunity to kind of figure out how do you want to work the next day and then that way we have only certain touch points.
+
+   7. You need to worry about with each other versus trying to have a daily meeting to stay in sync. And finally the third thing you need to think about: **who actually needs to be at that meeting?**
+
+   8. **Are you meeting with a person or are you meeting with a group?** If you're meeting with a person, is this something that you need to have a meeting for or is it best done through an instant message or some sort of other collaboration means?
+
+   9. If it's a group, **what are you trying to share? Are you just trying to share information?** If you're just trying to share information, maybe that's also done better through sharing out something like a Confluence page and a Loom.
+
+   10. Again, when you're thinking about the meetings that you have today, don't default to just have the meeting. Think about **how could  do this a little differently?**
+
+   11. If I need help answering these questions, Atlassian has actually come up with kind of a cheeky, fun view of how we can better identify whether or not we need to have a meeting. They call it the **"why do I want to call this meeting?" decision tree.** So if you walk through it, it kind of gives you these fun areas to say maybe I'm trying to share information or maybe I want to build relationships.
+
+       ![MEETING_decision_tree](https://i.postimg.cc/c4ZRMW52/MEETING-decision-tree.jpg)
+
+   12. And it starts asking me some questions like is this a one-on-one is this just trying to push information out there and it helps you kind of determine whether or not you actually need to hold this meeting.
+
+       - For example, you probably don't need to have a meeting to let's say read through the contents of a Confluence page you just sent. Or if you just don't know any other way to collaborate. Trust me, there are other ways to collaborate that don't involve a meeting.
+
+   13. Now the thing is, is this chart is great. It's fun. It's something that Atlassian use. But based on your organizational behaviors your cultural behaviors in your organization, you may actually want to come up with your own.
+
+   14. Work with the organization or even just your own team to create a meeting decision tree of your own in order to improve your meeting culture. You can then use your decision tree as a working agreement to eliminate unnecessary meetings and promote better meeting behaviors.
+
+   15. Again, find what works best for you. I usually try to lead with if I couldn't have a meeting for this how else could I get it accomplished? Put it into a decision tree to help you kind of think through that.
diff --git a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/03. Running Effective Meeting.md b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/03. Running Effective Meeting.md
index ba49e5c..b742632 100644
--- a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/03. Running Effective Meeting.md	
+++ b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/03. Running Effective Meeting.md	
@@ -1,80 +1,80 @@
-# **Running Effective Meeting**
-
-- [**Running Effective Meeting**](#running-effective-meeting)
-  - [**What is a Effective Meeting?**](#what-is-a-effective-meeting)
-  - [**Typical Problems with Meetings**](#typical-problems-with-meetings)
-  - [**What is an effective meeting then and what makes it effective?**](#what-is-an-effective-meeting-then-and-what-makes-it-effective)
-  - [**Four principles to an effective meeting**](#four-principles-to-an-effective-meeting)
-
----
-
-## **What is a Effective Meeting?**
-
-- I think we've all been in a meeting, probably in the last week, where you kind of came out of it thinking it wasn't the best use of my time or that wasn't that effective.
-
-- The stats today tell us that **only 50% of the time we spend in meetings is considered effective.** That means half the time we're spending a meetings, we don't feel like we're adding any value. And along those lines, at least **in the US, 37 billion dollars is spent on bad meetings**.
-
-- So, bad meetings are rampant in society today and for us there's actually ten core areas that we think bad meetings fall into. We essentially call it **"Bad Meeting Bingo."**
-
----
-
-## **Typical Problems with Meetings**
-
-- For us there's a couple of these that really resonate out there. Specifically areas like **focus;** do meetings have fluid borders. You really have no purpose coming in, you just show up. You're like, so what are we talking about today?
-
-    ![MEETING*problem*focus](https://i.postimg.cc/43rtKR98/MEETING-problem-focus.png)
-
-- Things like **loops**. Do we have like this Groundhog's Day feeling where we just kind of keep going back to the same topic over and over again, like "*Oh we talked about this last time we're gonna talk about it again?"*
-
-    ![MEETING*problem*loops](https://i.postimg.cc/sxzhcPK7/MEETING-problem-loops.png)
-
-- Even things like **readiness**. And not just on you the facilitators part, but on your participants. Are we coming into the meeting ready to have this meeting? Have we done the pre-work? Have we actually come in prepared to actually have a good conversation?
-
-    ![MEETING*problem*readiness](https://i.postimg.cc/qBcn7YML/MEETING-problem-readiness.png)
-
-- And ultimately one of the worst problems out there is **results**. Do we leave a meeting not making any decisions? Not coming to any kind of conclusion on how we want to move forward? Do we not hit an outcome?
-  
-    ![MEETING*problem*results](https://i.postimg.cc/c4XnRn3t/MEETING-problem-results.png)
-
-So for us these are some of those core areas why meetings may not be as effective, as they could be.
-
----
-
-## **What is an effective meeting then and what makes it effective?**
-
-- There's a couple things that kind of go into an effective meeting. One, they need to have a pre-established goal. **What is it that we're trying to accomplish?**
-
-- Two, they provide value to the people who are attending that meeting. There's an outcome we're going for that people feel like this was a good use of my time.
-
-- And finally all participants are engaged and they actually leave feeling like hey, I actually got value out of this. This was a good use of my time.
-
-- Think about this as a sort of a Venn diagram around business outcomes and cultural outcomes.
-
-    ![Meeeting*ven*diagram](https://i.postimg.cc/ZnzrQzY9/Meeeting-ven-diagram.png)
-
-  1. Ultimately, it comes down to the **"intent."** Effective meetings are actually created and run intently.
-
-  2. **What are the things you're trying to achieve around those spaces?** And typically meetings are built around those when we think of our business outcomes.
-
-  3. Think about things like is the intent of this meeting to impact a desired outcome. Are we actually trying to make it change happen? Maybe we want to produce actionable information. We want to go into a meeting and come out with stuff that we can make decisions on or we've actually made a decision on.
-
-  4. And **ultimately we may even want to provide visibility to leadership on how things are going.** Or maybe we want **to get visibility with leadership to showoff some of the great things we're doing.**
-
-  5. Then there's the cultural outcomes. We need to think about things like **why are we holding this meeting?** Because it's a critical touch point in an async world for our team.
-
-  6. How do we prevent things like the **Lone Wolf** syndrome where people don't feel so isolated and disengaged from their work. Is this meeting in place to help us rapidly accelerate on some sort of idea as a team.
-
-  7. Or maybe the intent of this meeting is to help us leverage the wisdom of crowds. How do we help bring about this diverse set of experience and knowledge to create something better than any one of us can do ourselves
-
-  8. Understanding the intent of an effective meeting is about balancing this business outcome with this cultural outcome. Ultimately in the end, we want to achieve both. And that allows both you and your participants to get the most out of your time together.
-
----
-
-## **Four principles to an effective meeting**
-
-  1. `Preparation`
-  2. `Facilitation`
-  3. `Participation`
-  4. `Follow-up`
-
-We will be talking about these principles in the next doc.
+# **Running Effective Meeting**
+
+- [**Running Effective Meeting**](#running-effective-meeting)
+  - [**What is a Effective Meeting?**](#what-is-a-effective-meeting)
+  - [**Typical Problems with Meetings**](#typical-problems-with-meetings)
+  - [**What is an effective meeting then and what makes it effective?**](#what-is-an-effective-meeting-then-and-what-makes-it-effective)
+  - [**Four principles to an effective meeting**](#four-principles-to-an-effective-meeting)
+
+---
+
+## **What is a Effective Meeting?**
+
+- I think we've all been in a meeting, probably in the last week, where you kind of came out of it thinking it wasn't the best use of my time or that wasn't that effective.
+
+- The stats today tell us that **only 50% of the time we spend in meetings is considered effective.** That means half the time we're spending a meetings, we don't feel like we're adding any value. And along those lines, at least **in the US, 37 billion dollars is spent on bad meetings**.
+
+- So, bad meetings are rampant in society today and for us there's actually ten core areas that we think bad meetings fall into. We essentially call it **"Bad Meeting Bingo."**
+
+---
+
+## **Typical Problems with Meetings**
+
+- For us there's a couple of these that really resonate out there. Specifically areas like **focus;** do meetings have fluid borders. You really have no purpose coming in, you just show up. You're like, so what are we talking about today?
+
+    ![MEETING*problem*focus](https://i.postimg.cc/43rtKR98/MEETING-problem-focus.png)
+
+- Things like **loops**. Do we have like this Groundhog's Day feeling where we just kind of keep going back to the same topic over and over again, like "*Oh we talked about this last time we're gonna talk about it again?"*
+
+    ![MEETING*problem*loops](https://i.postimg.cc/sxzhcPK7/MEETING-problem-loops.png)
+
+- Even things like **readiness**. And not just on you the facilitators part, but on your participants. Are we coming into the meeting ready to have this meeting? Have we done the pre-work? Have we actually come in prepared to actually have a good conversation?
+
+    ![MEETING*problem*readiness](https://i.postimg.cc/qBcn7YML/MEETING-problem-readiness.png)
+
+- And ultimately one of the worst problems out there is **results**. Do we leave a meeting not making any decisions? Not coming to any kind of conclusion on how we want to move forward? Do we not hit an outcome?
+  
+    ![MEETING*problem*results](https://i.postimg.cc/c4XnRn3t/MEETING-problem-results.png)
+
+So for us these are some of those core areas why meetings may not be as effective, as they could be.
+
+---
+
+## **What is an effective meeting then and what makes it effective?**
+
+- There's a couple things that kind of go into an effective meeting. One, they need to have a pre-established goal. **What is it that we're trying to accomplish?**
+
+- Two, they provide value to the people who are attending that meeting. There's an outcome we're going for that people feel like this was a good use of my time.
+
+- And finally all participants are engaged and they actually leave feeling like hey, I actually got value out of this. This was a good use of my time.
+
+- Think about this as a sort of a Venn diagram around business outcomes and cultural outcomes.
+
+    ![Meeeting*ven*diagram](https://i.postimg.cc/ZnzrQzY9/Meeeting-ven-diagram.png)
+
+  1. Ultimately, it comes down to the **"intent."** Effective meetings are actually created and run intently.
+
+  2. **What are the things you're trying to achieve around those spaces?** And typically meetings are built around those when we think of our business outcomes.
+
+  3. Think about things like is the intent of this meeting to impact a desired outcome. Are we actually trying to make it change happen? Maybe we want to produce actionable information. We want to go into a meeting and come out with stuff that we can make decisions on or we've actually made a decision on.
+
+  4. And **ultimately we may even want to provide visibility to leadership on how things are going.** Or maybe we want **to get visibility with leadership to showoff some of the great things we're doing.**
+
+  5. Then there's the cultural outcomes. We need to think about things like **why are we holding this meeting?** Because it's a critical touch point in an async world for our team.
+
+  6. How do we prevent things like the **Lone Wolf** syndrome where people don't feel so isolated and disengaged from their work. Is this meeting in place to help us rapidly accelerate on some sort of idea as a team.
+
+  7. Or maybe the intent of this meeting is to help us leverage the wisdom of crowds. How do we help bring about this diverse set of experience and knowledge to create something better than any one of us can do ourselves
+
+  8. Understanding the intent of an effective meeting is about balancing this business outcome with this cultural outcome. Ultimately in the end, we want to achieve both. And that allows both you and your participants to get the most out of your time together.
+
+---
+
+## **Four principles to an effective meeting**
+
+  1. `Preparation`
+  2. `Facilitation`
+  3. `Participation`
+  4. `Follow-up`
+
+We will be talking about these principles in the next doc.
diff --git a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/04. Preparation.md b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/04. Preparation.md
index 12aae2f..ac26ef5 100644
--- a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/04. Preparation.md	
+++ b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/04. Preparation.md	
@@ -1,56 +1,56 @@
-# **Phase: Preparation**
-
-- [**Phase: Preparation**](#phase-preparation)
-  - [**Preparation Principles**](#preparation-principles)
-
----
-
-## **Preparation Principles**
-
-   1. It's one of the most important stages in the entire process. This stage is all about doing the right pre-work and sharing that out with your participants before the meeting ever starts.
-  
-   2. Pre-work is essential for transforming your meetings and preventing unnecessary waste.
-
-   3. And so as we think about preparing for a meeting, there's a couple things you need to keep in mind. **When you actually say "I need this meeting," the first thing you do is not set up the meeting.**
-
-   4. The first thing you need to do before you send anything out: build an agenda. **What are the topics you want to cover in this agenda?** This goes back to that idea being very intentful with your time, thinking about the outcomes.
-
-   5. **Focus on time boxing the agendas**. Focus in on doing things like maybe setting aside 10 to 15 minute increments for each item on your agenda. Anything more than that and people might find themselves kind of drifting off or you might start wandering off topic.
-
-   6. Within your agenda, make sure you've identify what's the outcome for each one of those topics? **Yes, I want to present on something, but why am I presenting it? Again am I information sharing? Am I trying to make a decision with this group? Am I trying to gather ideas?**
-
-   7. Be very explicit and then also **identify who's going to own that topic. Who is going to help drive that conversation. Even though you may be the facilitator, someone is presenting that topic and your role is to help ensure that we hit that outcome and maintain that time box.**
-
-        ![MEETING_kickoff_agenda](https://i.postimg.cc/Hs2Q6Nqx/MEETING-kickoff-agenda.png)
-
-   8. Now this goes back down to again the intent of the meeting. **What are you trying to do? Don't blast out that invite to multiple people and just hope you get the right folks. For every person you add to the invite, make sure you ask yourself the question what's in it for this person to spend time in my meeting versus going somewhere else or doing something else.**
-
-   9. The thing is if you say well they just need to be here, that's not a good enough answer. Go through and say well, **what is their role gonna be in this meeting? Are they gonna help me make a decision? Do I need their expertise in something? Or are they part of a team that I need to share information with?**
-
-   10. Again be very explicit with **who you're bringing and why. And at that point, that's when you can invite them. That way they recognize this is the role I'm going to play versus "Hey, should I be here?"**
-
-   11. And so **once you've actually built out your agenda, you've actually figured out who needs to attend then and only then should you go ahead and send out an invite.**
-
-   12. In that invite make sure that in the description. Either **included the actual copy and paste agenda or you've included a link to something like a Confluence page.**
-
-   13. **Never ever ever send a meeting invite with that says "Agenda to come."** That is just a way to cop out of actually putting together that agenda doing that preparation.
-
-   14. As you're getting prepared for your meeting, **are there any other tools or tips to use?**
-
-   15. To me all goes back to again, w**hat do you want to try to achieve in the meeting? What's the intent of the meeting?**
-
-   16. If you're having a **one-way information sharing meeting, tools like PowerPoint and Keynote are great for that. They help convey information very well to an audience.**
-
-   17. Now if you're in a more of **a collaborative meeting, maybe you're trying to make a decision or maybe you're just trying to brainstorm things. There's other tools out there.**
-
-   18. [**Confluence**](https://www.atlassian.com/software/confluence) is really good for sharing information and allowing people to kind of review and collaborate on it. Tools like [**Mural**](https://www.mural.co/)/ [**draw.io**](https://app.diagrams.net/) are really great whiteboarding tools that **allow you to go in and actually have some rapid brainstorming.**
-
-   19. You can even use polling tools like [**Slido**](https://www.slido.com/) or [**Mentimeter**](https://www.mentimeter.com/). These are great tools that I've found in my meetings that I like to employ at certain times to kind of get the poll of the room. Especially in a large group on a certain question that I have.
-
-   20. So think creatively about how you can use tools to one engage your audience. But then also make sure when you're using those tools you're using them with intent.
-
-   21. You're not just using them because you can. And another pro tip here is if you're going to use these tools, make sure you get those tools prepped beforehand.
-
-   22. I hate going into a meeting and someone's like, "Oh look, we're gonna review this Confluence page and I don't know where it is." Be prepared. Link that in your agenda. What are we going to review, where we gonna do it?
-
-   23. At the end, sharing Minutes of Meeting (**MoM**) to the attendees helps to keep the context with target audience. Also if any to-do/ pending action to be taken by you/ someone else can be specified in follow up mail once the meeting is over.
+# **Phase: Preparation**
+
+- [**Phase: Preparation**](#phase-preparation)
+  - [**Preparation Principles**](#preparation-principles)
+
+---
+
+## **Preparation Principles**
+
+   1. It's one of the most important stages in the entire process. This stage is all about doing the right pre-work and sharing that out with your participants before the meeting ever starts.
+  
+   2. Pre-work is essential for transforming your meetings and preventing unnecessary waste.
+
+   3. And so as we think about preparing for a meeting, there's a couple things you need to keep in mind. **When you actually say "I need this meeting," the first thing you do is not set up the meeting.**
+
+   4. The first thing you need to do before you send anything out: build an agenda. **What are the topics you want to cover in this agenda?** This goes back to that idea being very intentful with your time, thinking about the outcomes.
+
+   5. **Focus on time boxing the agendas**. Focus in on doing things like maybe setting aside 10 to 15 minute increments for each item on your agenda. Anything more than that and people might find themselves kind of drifting off or you might start wandering off topic.
+
+   6. Within your agenda, make sure you've identify what's the outcome for each one of those topics? **Yes, I want to present on something, but why am I presenting it? Again am I information sharing? Am I trying to make a decision with this group? Am I trying to gather ideas?**
+
+   7. Be very explicit and then also **identify who's going to own that topic. Who is going to help drive that conversation. Even though you may be the facilitator, someone is presenting that topic and your role is to help ensure that we hit that outcome and maintain that time box.**
+
+        ![MEETING_kickoff_agenda](https://i.postimg.cc/Hs2Q6Nqx/MEETING-kickoff-agenda.png)
+
+   8. Now this goes back down to again the intent of the meeting. **What are you trying to do? Don't blast out that invite to multiple people and just hope you get the right folks. For every person you add to the invite, make sure you ask yourself the question what's in it for this person to spend time in my meeting versus going somewhere else or doing something else.**
+
+   9. The thing is if you say well they just need to be here, that's not a good enough answer. Go through and say well, **what is their role gonna be in this meeting? Are they gonna help me make a decision? Do I need their expertise in something? Or are they part of a team that I need to share information with?**
+
+   10. Again be very explicit with **who you're bringing and why. And at that point, that's when you can invite them. That way they recognize this is the role I'm going to play versus "Hey, should I be here?"**
+
+   11. And so **once you've actually built out your agenda, you've actually figured out who needs to attend then and only then should you go ahead and send out an invite.**
+
+   12. In that invite make sure that in the description. Either **included the actual copy and paste agenda or you've included a link to something like a Confluence page.**
+
+   13. **Never ever ever send a meeting invite with that says "Agenda to come."** That is just a way to cop out of actually putting together that agenda doing that preparation.
+
+   14. As you're getting prepared for your meeting, **are there any other tools or tips to use?**
+
+   15. To me all goes back to again, w**hat do you want to try to achieve in the meeting? What's the intent of the meeting?**
+
+   16. If you're having a **one-way information sharing meeting, tools like PowerPoint and Keynote are great for that. They help convey information very well to an audience.**
+
+   17. Now if you're in a more of **a collaborative meeting, maybe you're trying to make a decision or maybe you're just trying to brainstorm things. There's other tools out there.**
+
+   18. [**Confluence**](https://www.atlassian.com/software/confluence) is really good for sharing information and allowing people to kind of review and collaborate on it. Tools like [**Mural**](https://www.mural.co/)/ [**draw.io**](https://app.diagrams.net/) are really great whiteboarding tools that **allow you to go in and actually have some rapid brainstorming.**
+
+   19. You can even use polling tools like [**Slido**](https://www.slido.com/) or [**Mentimeter**](https://www.mentimeter.com/). These are great tools that I've found in my meetings that I like to employ at certain times to kind of get the poll of the room. Especially in a large group on a certain question that I have.
+
+   20. So think creatively about how you can use tools to one engage your audience. But then also make sure when you're using those tools you're using them with intent.
+
+   21. You're not just using them because you can. And another pro tip here is if you're going to use these tools, make sure you get those tools prepped beforehand.
+
+   22. I hate going into a meeting and someone's like, "Oh look, we're gonna review this Confluence page and I don't know where it is." Be prepared. Link that in your agenda. What are we going to review, where we gonna do it?
+
+   23. At the end, sharing Minutes of Meeting (**MoM**) to the attendees helps to keep the context with target audience. Also if any to-do/ pending action to be taken by you/ someone else can be specified in follow up mail once the meeting is over.
diff --git a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/05. Facilitation.md b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/05. Facilitation.md
index 296a82a..8c26e71 100644
--- a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/05. Facilitation.md	
+++ b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/05. Facilitation.md	
@@ -1,70 +1,70 @@
-# **Phase: Meeting Facilitation**
-
-- [**Phase: Meeting Facilitation**](#phase-meeting-facilitation)
-  - [**Facilitation phase**](#facilitation-phase)
-  - [**How to facilitate a meeting?**](#how-to-facilitate-a-meeting)
-  - [**Tips to keep in mind as you facilitate**](#tips-to-keep-in-mind-as-you-facilitate)
-
----
-
-## **Facilitation phase**
-  
-  1. So you made it. You're actually at your meeting. You've done all the preparation. You made sure the right people are there.
-
-  2. It is **good practise to remind the meeting facilitators when you start a meeting, always make sure you cover the ground rules, gentle reminders.** I usually like to **include this at the top of the meeting agenda page in Confluence.**
-
-  3. In the meeting you can say here are the three or four things that we agreed to follow. That we're not going to talk over each other. We're going to make sure we raise our hands if we want to say something.
-
-  4. These are little things that, again, as a quick reminder allow people to become conscious of it and realize, **"All right. This is how we act when we're together."** So again, always make sure you cover those ground rules.
-
-  5. To me each meeting needs a scribe. Honestly, it's difficult for anyone to take notes and facilitate the same time. This is also a very clever way to help bring in participation from the people in the room. **Find someone who can help you take notes.**
-
-  6. **Another clever thing to do is let's say you have one of those individuals in your meeting that really likes to kind of take the stage.** Maybe they're always kind of breaking your ground rules. A good way to get them engaged in a positive way is ask them to be the note-taker.
-
-  7. Have them being engaged and the whole flow of the meeting by being that note-taker. And it's one of the things that will help keep them focused on something that's adding value to that meeting.
-
-  8. **Be the facilitator. This means that in the conversation, make sure you're putting that facilitator hat on and not necessarily jumping into the content.**
-
-  9. **A lot of times, the facilitator can get themselves deep into a conversation** and then all of a sudden, 15, 20, 30 minutes goes by because they're so deep in the conversation that they forgot to pay attention to the clock.
-
-  10. If you find that you're in a topic that you need to engage with, actually ask your group, **"I need someone to play facilitator for the next topic because I need to engage in that."**
-
-  11. **Get someone to be that timekeeper, that person who's gonna keep you focused. It's huge because it'll also again show that you respect people's time and want to get to all the topics.**
-
-  12. **Make sure you know when to break the rules.** I say this because one of the things that you probably seen in meetings is you get a facilitator who is running a meeting by the book, when something maybe truly more pressing comes up. And says "Nope, we got to keep your schedule."
-
-  13. Knowing when to break the rules and how to ask the team permission to break the rules is key be willing to kind of sense and adapt as you go.
-
-  14. **Again use your rules as your guide, but don't be so rigid in those that all the sudden you lead people in the end to still feel like we didn't cover the right thing.**
-
-  15. Some of my best meetings have come out in the end where they said, you know what I'm glad we switch to that topic because we needed to at that point.
-
-  16. So just a few things to keep in mind as you're facilitating. It's **your responsibility to be a good listener**. **Be aware of the conversation going on** and **help advance discussion when needed**.
-
-  17. **Know how to draw your participants back in if things start to wander a bit and be mindful the topics and time** just to make sure everything stays on track.
-
-Going back to the four principles. Those are some tips for better facilitation next. Let's move to participation.
-
----
-
-## **How to facilitate a meeting?**
-
-  1. Start a meeting by covering the ground rules.
-
-  2. Have someone else be the scribe.
-
-  3. Be the facilitator.
-
-  4. Know when to break the rules.
-
----
-
-## **Tips to keep in mind as you facilitate**
-
-  1. Be a good listener. Do not talk over each other.
-
-  2. Help advance the discussion.
-
-  3. Draw participants back in.
-
-  4. Be mindguful of topics and time.
+# **Phase: Meeting Facilitation**
+
+- [**Phase: Meeting Facilitation**](#phase-meeting-facilitation)
+  - [**Facilitation phase**](#facilitation-phase)
+  - [**How to facilitate a meeting?**](#how-to-facilitate-a-meeting)
+  - [**Tips to keep in mind as you facilitate**](#tips-to-keep-in-mind-as-you-facilitate)
+
+---
+
+## **Facilitation phase**
+  
+  1. So you made it. You're actually at your meeting. You've done all the preparation. You made sure the right people are there.
+
+  2. It is **good practise to remind the meeting facilitators when you start a meeting, always make sure you cover the ground rules, gentle reminders.** I usually like to **include this at the top of the meeting agenda page in Confluence.**
+
+  3. In the meeting you can say here are the three or four things that we agreed to follow. That we're not going to talk over each other. We're going to make sure we raise our hands if we want to say something.
+
+  4. These are little things that, again, as a quick reminder allow people to become conscious of it and realize, **"All right. This is how we act when we're together."** So again, always make sure you cover those ground rules.
+
+  5. To me each meeting needs a scribe. Honestly, it's difficult for anyone to take notes and facilitate the same time. This is also a very clever way to help bring in participation from the people in the room. **Find someone who can help you take notes.**
+
+  6. **Another clever thing to do is let's say you have one of those individuals in your meeting that really likes to kind of take the stage.** Maybe they're always kind of breaking your ground rules. A good way to get them engaged in a positive way is ask them to be the note-taker.
+
+  7. Have them being engaged and the whole flow of the meeting by being that note-taker. And it's one of the things that will help keep them focused on something that's adding value to that meeting.
+
+  8. **Be the facilitator. This means that in the conversation, make sure you're putting that facilitator hat on and not necessarily jumping into the content.**
+
+  9. **A lot of times, the facilitator can get themselves deep into a conversation** and then all of a sudden, 15, 20, 30 minutes goes by because they're so deep in the conversation that they forgot to pay attention to the clock.
+
+  10. If you find that you're in a topic that you need to engage with, actually ask your group, **"I need someone to play facilitator for the next topic because I need to engage in that."**
+
+  11. **Get someone to be that timekeeper, that person who's gonna keep you focused. It's huge because it'll also again show that you respect people's time and want to get to all the topics.**
+
+  12. **Make sure you know when to break the rules.** I say this because one of the things that you probably seen in meetings is you get a facilitator who is running a meeting by the book, when something maybe truly more pressing comes up. And says "Nope, we got to keep your schedule."
+
+  13. Knowing when to break the rules and how to ask the team permission to break the rules is key be willing to kind of sense and adapt as you go.
+
+  14. **Again use your rules as your guide, but don't be so rigid in those that all the sudden you lead people in the end to still feel like we didn't cover the right thing.**
+
+  15. Some of my best meetings have come out in the end where they said, you know what I'm glad we switch to that topic because we needed to at that point.
+
+  16. So just a few things to keep in mind as you're facilitating. It's **your responsibility to be a good listener**. **Be aware of the conversation going on** and **help advance discussion when needed**.
+
+  17. **Know how to draw your participants back in if things start to wander a bit and be mindful the topics and time** just to make sure everything stays on track.
+
+Going back to the four principles. Those are some tips for better facilitation next. Let's move to participation.
+
+---
+
+## **How to facilitate a meeting?**
+
+  1. Start a meeting by covering the ground rules.
+
+  2. Have someone else be the scribe.
+
+  3. Be the facilitator.
+
+  4. Know when to break the rules.
+
+---
+
+## **Tips to keep in mind as you facilitate**
+
+  1. Be a good listener. Do not talk over each other.
+
+  2. Help advance the discussion.
+
+  3. Draw participants back in.
+
+  4. Be mindguful of topics and time.
diff --git a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/06. Participation.md b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/06. Participation.md
index a38d3d0..a92661f 100644
--- a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/06. Participation.md	
+++ b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/06. Participation.md	
@@ -1,48 +1,48 @@
-# **Phase: Participation**
-
-- [**Phase: Participation**](#phase-participation)
-  - [**How do you ensure your meetings are focused engaging and inclusive for everyone involved?**](#how-do-you-ensure-your-meetings-are-focused-engaging-and-inclusive-for-everyone-involved)
-
----
-
-## **How do you ensure your meetings are focused engaging and inclusive for everyone involved?**
-  
-A lot of times when you get into a meeting, it can feel kind of like the Wild Wild West. You know, someone's talking here things are happening there.
-
-  1. **As a facilitator, it's your job to help kind of maintain the flow of the meeting** but the same time create an environment where everyone feels like they can talk.
-
-  2. Let's take a look into [**👉  the Atlassian Team Playbook**](https://www.atlassian.com/team-playbook/plays/inclusive-meetings) play called **inclusive meetings**. And it's all about how do we set ground rules for our meetings? And these are rules in terms of like how do we want to collaborate?
-
-  3. You might have examples like **"Hey, we're gonna raise our hand when we want to speak."** Or for every topic, we're gonna hold questions until the end of that topic.
-
-  4. As a facilitator you are accountable and responsible for creating an inclusive environment in your meeting so that everyone feels like they can contribute.
-
-  5. Look for feedback afterwards to determine whether or not in that meeting everybody felt like they could get a voice. And use your intuition. **Sometimes you can see that hey, you know got a couple people that are always quiet.**
-
-  6. **Kind of look and say what can I do to change my environment help make meetings better in the future?**
-
-  7. My biggest recommendation to help **keep attendees engaged is one use time boxes in your agenda. And two, follow those sign boxes.**
-
-  8. **Keeping attendees engaged is going to come back to honoring their time saying this is our agenda.** These are what we're going to talk about and this is when we're going to talk about it.
-
-  9. This really important to help keep in participants engaged. I can't tell you how many times I get into a meeting and we have 10 minutes on a topic and I look at my watch in 20 minutes have gone by and we're still on that topic.
-
-  10. For me, I feel that facilitator isn't doing their job and I'm like, apparently the rest of these topics don't matter. Final tip for keeping people engaged on a meeting: use the power of a parking lot.
-
-  11. **Many times we get into meetings and we find ourselves derailing a topic a little bit with a new topic.** Well as a facilitator go in there and say hey, that's a great topic. Let's add it to our parking lot.
-  
-  12. If we have time maybe you've set aside time at the end of your agenda for other topics Or you need to set up a separate meeting. This allows again participants to feel that you value their time and you want them to get to the outcomes that they originally attended to get to in that meeting.
-
-  13. When it comes time to end the meeting, maybe you're in the last five minutes of it. There's nothing worse than getting to the end of the meeting where your midway through a conversation and now you're just having to leave.
-
-  14. I always want to make sure I save 5 or 10 minutes on that agenda. It kind of closes out the meeting. Honor that time box make sure that you have that 5 to 10 minutes to review a couple things.
-
-  15. Make sure you review the goal of the meeting - **did we accomplish this?** I actually like to ask my participants, **you know up or down on your with your thumbs**. **Did we hit the outcome did we get to the place?**
-
-  16. We wanted to get to also make sure you go back and look at your action items do w**e have owners assigned to them? Do we have due dates on those? Have people agreed to take those on?**
-
-  17. Make sure you take care of those so that way people leaving say, **"Cool the things that we need help with, they are going to get done."**
-
-  18. And then finally make sure you go back and look at the decisions you've made as well. Make sure you say, **"Hey in this meeting, we we made the decisions on A, B, and C."** Just as a reminder to the group that says cool, these are the things that we decided.
-
-  19. This also will help solidify for your participants that hey we actually got some value out of this meeting. We actually were able to get from A to B, which is more than maybe we've gotten to in the past.
+# **Phase: Participation**
+
+- [**Phase: Participation**](#phase-participation)
+  - [**How do you ensure your meetings are focused engaging and inclusive for everyone involved?**](#how-do-you-ensure-your-meetings-are-focused-engaging-and-inclusive-for-everyone-involved)
+
+---
+
+## **How do you ensure your meetings are focused engaging and inclusive for everyone involved?**
+  
+A lot of times when you get into a meeting, it can feel kind of like the Wild Wild West. You know, someone's talking here things are happening there.
+
+  1. **As a facilitator, it's your job to help kind of maintain the flow of the meeting** but the same time create an environment where everyone feels like they can talk.
+
+  2. Let's take a look into [**👉  the Atlassian Team Playbook**](https://www.atlassian.com/team-playbook/plays/inclusive-meetings) play called **inclusive meetings**. And it's all about how do we set ground rules for our meetings? And these are rules in terms of like how do we want to collaborate?
+
+  3. You might have examples like **"Hey, we're gonna raise our hand when we want to speak."** Or for every topic, we're gonna hold questions until the end of that topic.
+
+  4. As a facilitator you are accountable and responsible for creating an inclusive environment in your meeting so that everyone feels like they can contribute.
+
+  5. Look for feedback afterwards to determine whether or not in that meeting everybody felt like they could get a voice. And use your intuition. **Sometimes you can see that hey, you know got a couple people that are always quiet.**
+
+  6. **Kind of look and say what can I do to change my environment help make meetings better in the future?**
+
+  7. My biggest recommendation to help **keep attendees engaged is one use time boxes in your agenda. And two, follow those sign boxes.**
+
+  8. **Keeping attendees engaged is going to come back to honoring their time saying this is our agenda.** These are what we're going to talk about and this is when we're going to talk about it.
+
+  9. This really important to help keep in participants engaged. I can't tell you how many times I get into a meeting and we have 10 minutes on a topic and I look at my watch in 20 minutes have gone by and we're still on that topic.
+
+  10. For me, I feel that facilitator isn't doing their job and I'm like, apparently the rest of these topics don't matter. Final tip for keeping people engaged on a meeting: use the power of a parking lot.
+
+  11. **Many times we get into meetings and we find ourselves derailing a topic a little bit with a new topic.** Well as a facilitator go in there and say hey, that's a great topic. Let's add it to our parking lot.
+  
+  12. If we have time maybe you've set aside time at the end of your agenda for other topics Or you need to set up a separate meeting. This allows again participants to feel that you value their time and you want them to get to the outcomes that they originally attended to get to in that meeting.
+
+  13. When it comes time to end the meeting, maybe you're in the last five minutes of it. There's nothing worse than getting to the end of the meeting where your midway through a conversation and now you're just having to leave.
+
+  14. I always want to make sure I save 5 or 10 minutes on that agenda. It kind of closes out the meeting. Honor that time box make sure that you have that 5 to 10 minutes to review a couple things.
+
+  15. Make sure you review the goal of the meeting - **did we accomplish this?** I actually like to ask my participants, **you know up or down on your with your thumbs**. **Did we hit the outcome did we get to the place?**
+
+  16. We wanted to get to also make sure you go back and look at your action items do w**e have owners assigned to them? Do we have due dates on those? Have people agreed to take those on?**
+
+  17. Make sure you take care of those so that way people leaving say, **"Cool the things that we need help with, they are going to get done."**
+
+  18. And then finally make sure you go back and look at the decisions you've made as well. Make sure you say, **"Hey in this meeting, we we made the decisions on A, B, and C."** Just as a reminder to the group that says cool, these are the things that we decided.
+
+  19. This also will help solidify for your participants that hey we actually got some value out of this meeting. We actually were able to get from A to B, which is more than maybe we've gotten to in the past.
diff --git a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/07. Follow-up.md b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/07. Follow-up.md
index ed36c81..70fed5c 100644
--- a/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/07. Follow-up.md	
+++ b/TuxTechBlogs/docs/topic/13.1. Management/00. Run Effective Meetings/07. Follow-up.md	
@@ -1,45 +1,45 @@
-# **Phase: Follow Up**
-
-- Congratulations, you have made it. You completed your meeting. Now, the game's not over with yet. That's the thing. You remember that you've got preparation, facilitation, participation, and now we're in follow-up.
-
-- All about closing this out. When at the end of a meeting, you need to determine how effective that meeting was. What I like to do to determine it whether or not a meeting is effective is save a few minutes at the very end of the meeting to maybe ask the audience.
-
-- Maybe there's good psychological safety in your group and because of that you can actually ask people, "Hey, how was this meeting? Did you like it? Was it effective? Was it valuable?"
-
-- Other techniques you can use that I've used in the past. If you're in a room on the whiteboard or if you're digital, maybe you're using a Trello board,  **create a scale one to five**. One, this was not a very effective use of my time, I wish I was doing something else. And five being, this was the best use of my time possible, I'm so glad I was here.
-
-- As people leave physically in the room have a mark on that whiteboard where they're at. If they are digital have them go ahead and vote on one of those cards one to five. And again that just gives you information in terms of hey did people feel that this was an effective meeting or not?
-
-## **what's the best way to follow up with your participants?**
-
-- So once your meeting is over, let's say it was an effective meeting. Let's say you did all the right stuff. Everyone's like "Yeah, that was great."
-
-- The first thing you've got to do after that meeting is done go out there and make sure you send out those meeting notes. Share it with the participants as well as those people who maybe you just need to inform what was covered in that meeting.
-
-- Tell them what decisions were made, what actions we're taking. And most importantly, for those folks who took actions, make sure that they're aware of those especially.
-
-- If you know, they need to have some sort of tracking of those, great tools like Confluence allow you to actually mention somebody in it and actually sends them a notification that says "Hey, you got this action."
-
-- And most importantly, after let's say a few days of that meeting, follow up. Make sure things like actions are taken care of. **One of the things I like to do is if I have a regular occurring meeting, what I'll do is at the beginning of every agenda will actually have a line item to look back at prior action items.**
-
-- Have we taken care of those which ones are due which ones aren't? It leads to a lot of accountability on the people who actually took those actions and it really helps move that meeting forward.
-
-- Now if you're finding you're having an ineffective meeting so okay. Don't beat yourself up for it. It happens to all of us and the goal here is just to get better.
-
-So a couple things you can do here is one go actually ask some folks. You know have some one-on-one sessions saying, "Hey, I'd love to get better at running effective meetings. What feedback do you have for me?"
-
-Figure out what could make meetings better than the next time and experiment with that. Another thing you can do is, let's say it's a meeting that's on a regular basis.
-
-Do what we call a ritual reset here at Atlassian. If you go to our Team Playbook, you'll find the ritual reset play. It's a fantastic play that allows you to kind of take a meta view of your meetings.
-
-And saying hey if I were to reexamine all these meetings, what would I keep because I think they're super valuable? What would I maybe change because I still need that but something needs to change? And ultimately what should I get rid of? Maybe that could be more of an email. What could be async here?
-
-Actually a great story for you here is I have a customer I've been working with in telecom that actually found themselves in need of kind of fixing up some of their meetings.
-
-What ended up happening is they said you know, what? We'd love to try this ritual reset play out. And so they actually went and spent about an hour, which is all the time it takes running through that play.
-
-And the next day I actually got an email from that team that says, "Hey, I just want to say running this play kind of changed our perspective on how we meet. It allowed us to really take a look and say is this meeting worthwhile or should we change it up? Should we remove it?"
-
-And from there, they were able to kind of really change how they work together all of a sudden now, they've introduced some new ways of working. They've opened up their minds saying we can collaborate differently.
-
-So explore things like our ritual reset because it's incredibly powerful to actually look and say, "Hey, is this the best use of our time?" And maybe it is, let's get a little bit better at it.
+# **Phase: Follow Up**
+
+- Congratulations, you have made it. You completed your meeting. Now, the game's not over with yet. That's the thing. You remember that you've got preparation, facilitation, participation, and now we're in follow-up.
+
+- All about closing this out. When at the end of a meeting, you need to determine how effective that meeting was. What I like to do to determine it whether or not a meeting is effective is save a few minutes at the very end of the meeting to maybe ask the audience.
+
+- Maybe there's good psychological safety in your group and because of that you can actually ask people, "Hey, how was this meeting? Did you like it? Was it effective? Was it valuable?"
+
+- Other techniques you can use that I've used in the past. If you're in a room on the whiteboard or if you're digital, maybe you're using a Trello board,  **create a scale one to five**. One, this was not a very effective use of my time, I wish I was doing something else. And five being, this was the best use of my time possible, I'm so glad I was here.
+
+- As people leave physically in the room have a mark on that whiteboard where they're at. If they are digital have them go ahead and vote on one of those cards one to five. And again that just gives you information in terms of hey did people feel that this was an effective meeting or not?
+
+## **what's the best way to follow up with your participants?**
+
+- So once your meeting is over, let's say it was an effective meeting. Let's say you did all the right stuff. Everyone's like "Yeah, that was great."
+
+- The first thing you've got to do after that meeting is done go out there and make sure you send out those meeting notes. Share it with the participants as well as those people who maybe you just need to inform what was covered in that meeting.
+
+- Tell them what decisions were made, what actions we're taking. And most importantly, for those folks who took actions, make sure that they're aware of those especially.
+
+- If you know, they need to have some sort of tracking of those, great tools like Confluence allow you to actually mention somebody in it and actually sends them a notification that says "Hey, you got this action."
+
+- And most importantly, after let's say a few days of that meeting, follow up. Make sure things like actions are taken care of. **One of the things I like to do is if I have a regular occurring meeting, what I'll do is at the beginning of every agenda will actually have a line item to look back at prior action items.**
+
+- Have we taken care of those which ones are due which ones aren't? It leads to a lot of accountability on the people who actually took those actions and it really helps move that meeting forward.
+
+- Now if you're finding you're having an ineffective meeting so okay. Don't beat yourself up for it. It happens to all of us and the goal here is just to get better.
+
+So a couple things you can do here is one go actually ask some folks. You know have some one-on-one sessions saying, "Hey, I'd love to get better at running effective meetings. What feedback do you have for me?"
+
+Figure out what could make meetings better than the next time and experiment with that. Another thing you can do is, let's say it's a meeting that's on a regular basis.
+
+Do what we call a ritual reset here at Atlassian. If you go to our Team Playbook, you'll find the ritual reset play. It's a fantastic play that allows you to kind of take a meta view of your meetings.
+
+And saying hey if I were to reexamine all these meetings, what would I keep because I think they're super valuable? What would I maybe change because I still need that but something needs to change? And ultimately what should I get rid of? Maybe that could be more of an email. What could be async here?
+
+Actually a great story for you here is I have a customer I've been working with in telecom that actually found themselves in need of kind of fixing up some of their meetings.
+
+What ended up happening is they said you know, what? We'd love to try this ritual reset play out. And so they actually went and spent about an hour, which is all the time it takes running through that play.
+
+And the next day I actually got an email from that team that says, "Hey, I just want to say running this play kind of changed our perspective on how we meet. It allowed us to really take a look and say is this meeting worthwhile or should we change it up? Should we remove it?"
+
+And from there, they were able to kind of really change how they work together all of a sudden now, they've introduced some new ways of working. They've opened up their minds saying we can collaborate differently.
+
+So explore things like our ritual reset because it's incredibly powerful to actually look and say, "Hey, is this the best use of our time?" And maybe it is, let's get a little bit better at it.
diff --git a/TuxTechBlogs/docs/topic/13.2. Miscellaneous/acronym.md b/TuxTechBlogs/docs/topic/13.2. Miscellaneous/acronym.md
index cc853d5..347a3e2 100644
--- a/TuxTechBlogs/docs/topic/13.2. Miscellaneous/acronym.md	
+++ b/TuxTechBlogs/docs/topic/13.2. Miscellaneous/acronym.md	
@@ -1,254 +1,254 @@
-# **Acronyms**
-
-  - [**A**](#a)
-  - [**B**](#b)
-  - [**C**](#c)
-  - [**D**](#d)
-  - [**E**](#e)
-  - [**F**](#f)
-  - [**G**](#g)
-  - [**H**](#h)
-  - [**I**](#i)
-  - [**J**](#j)
-  - [**K**](#k)
-  - [**L**](#l)
-  - [**M**](#m)
-  - [**N**](#n)
-  - [**O**](#o)
-  - [**P**](#p)
-  - [**Q**](#q)
-  - [**R**](#r)
-  - [**S**](#s)
-  - [**T**](#t)
-  - [**U**](#u)
-  - [**V**](#v)
-  - [**W**](#w)
-  - [**X**](#x)
-  - [**Y**](#y)
-  - [**Z**](#z)
-
-## **A**
-
-- `AWS`     - *Amazon Web Services*
-- `Azure`   - *Azure Cloud*
-- `ABE`     - *Access Based Enumeration*
-- `AD`      - *Active Directory*
-- `ARP`     - *Address Resolution Protocol*
-- `AKS`     - *Azure K8S Service*
-
-## **B**
-
-- `Bit/ Bits`  - *Binary Digit/ Binary Digits*
-- `Byte`       - *8 bBits =1 Byte*
-- `BGP`        - *Border Gateway Protocol*
-
-## **C**
-
-- `CD`  - *Compact Disc*
-- `CSMA/CD` - *Carrier Sense Multiple Access with Collision Detection*
-- `CPU` - *Central Processing Unit*
-- `CIDR` - *Classless Inter-Domain Routing*
-- `CDN` - *Content Delivery Network*
-- `CSS` - *Cascading Styling Sheet*
-- `CI/CD` - *Continuous Delivery And Continuous Integratoion*
-
-## **D**
-
-- `DMZ` - *Demilitarized Zone*
-- `DPU` - *Data Processing Unit*
-- `DNS` - *Domain Name System*
-- `DBMS` - *Database Management System*
-- `DMA` - *Direct Memory Access*
-- `DP` - *Dynamic Programming*
-- `DVD` - *Digital Versatile Disc*
-- `DHCP` - *Dynamic Host Control Protocol*
-- `DLR` - *Distributed Logical Router*
-- `DVS` - *Distributed Virtual Switch*
-
-## **E**
-
-- `EBS` - *Elastic Block Storag*
-- `EKS` - *Elastic k8s Service*
-- `EC2` - *Elastic Cloud Compute*
-- `EOD` - *End Of the Day*
-- `ECMP` - *Equal Cost Multi Path Routing*
-
-## **F**
-
-- `fw`   - *Firewall*
-- `ftp`  - *File Transfer Protocol*
-- `fc`   - *Fiber Channel*
-- `FCOE` - *Fiber Channel Over Ethernet*
-- `FQDN` - *Fully Qualified Domain Name*
-
-## **G**
-
-- `GW`  - *Gateway*
-- `GFW` - *Gateway Firewall*
-- `GPU` - *Graphical Processing Unit*
-- `GB` - *1 GigaByte = 1024 MB*
-- `gRPC` - *Group RPC (RPC)by Google*
-- `GIT` - *Global Information Tracker*
-
-## **H**
-
-- `HDD` - *Hard Disc Drive*
-- `HTTP` - *Hypertext Transfer Protocol*
-- `HTTPS` - *Hypertext Transfer Protocol Secured*
-- `HTML` - *Hyper Text Markup Language*
-- `HLD` - *High Level Design*
-- `HDFS` - *Hadoop Distributed File System*
-
-## **I**
-
-- `IT` - *Information Technology*
-- `ITSM` - *IT Service Management*
-- `ITIL` - *Information Technology Infrastructure Library*
-- `IAM` - *Identity and Access Management*
-- `IRC` - *Internet Relay Chat*
-- `IPMI` - *Intelligent Platform Management Interface*
-- `iDRAC` - *Integrated Dell Remote Access Controller*
-- `iSCSI` - *Internet Small Computer System Interface*
-- `iQN` - *iSCSI Qualified Name*
-- `ICMP` - *Internet Control Message Protocol*
-
-## **J**
-
-- `JWT` - *JSON Web Token*
-- `JSON` - *JavaScript Object Notation*
-- `JS` - *Java Script*
-- `JIT` - *Just in Time*
-
-## **K**
-
-- `KB` - *Kilo Byte*
-- `k8s` - *Kubernetes*
-
-## **L**
-
-- `LDAP` - *Light-weight Directory Access Protocol*
-- `LLP`  - *Limited liability Partnership*
-- `LB`   - *Load Balancer*
-- `Linux` - *Lovable Intellect Not Using XP*
-- `LSB` - *Least Significant Bit*
-- `LLD` - *Low Level Design*
-- `LIDAR` - *Light Detection and Ranging*
-- `LLM` - *Large Language Model*
-- `LUN` - *Logical Unit Number*
-- `LAMP` - *Linux, Apache, MySQL, PHP/Perl/Python*
-
-## **M**
-
-- `MB` - *Mega Byte*
-- `MQ` - *Messaging Queue*
-- `MSB` - *Most Significant Bit*
-- `MTU` - *Maximum Transmission Unit*
-- `MVC` - *Model View Controller*
-- `MAC` - *Media Access Control*
-- `MVP` - *Most Viable Product*
-- `MoM` - *Minutes of Meeting*
-- `MERN` - *MongoDB, Express, React, Node*
-- `MEAN` - *MongoDB, Express, Angular, and Node*
-
-## **N**
-
-- `NTP` - *Network Time Protocol*
-- `NFS` - *Network File System*
-- `NvMe` - *Non-Volatile Memory*
-- `NoSQL` - *No Structured Quqry Language*
-- `NIC` - *Network Interface Card*
-- `NLP` - *Natual Language Processing*
-
-## **O**
-
-- `OSI` - *Open System Interconnection*
-- `OEM` - *Original Equipment Manufacturer*
-- `OS` - *Operating System*
-- `OSPF` - *Open Shortest Path First*
-
-## **P**
-
-- `PDL` - *Page Description Language*
-- `POP3` - *Post Office Protocol 3 over TLS/SSL*
-- `PB` - *1 PetaByte =  1024 TB*
-
-## **Q**
-
-- `QOS` - *Quality Of Service*
-- `OAuth` - *Open Authorization*
-
-## **R**
-
-- `RDP` - *Remote Desktop Protocol*
-- `RDBMS` - *Relational DBMS*
-- `RSYNC` - *Remote Sync*
-- `RAID` - *Redundant Array of Independent Dxisks*
-- `RMA` - *Return Merchandise Authorization*
-- `RDMA` - *Remote Direct Memory Access*
-- `RBAC` - *Role Based Access Control*
-- `RFB` - *Remote Frame Buffer*
-- `RPC` - *Remote Procedural Call*
-- `RAN` - *Radio Access Network*
-
-## **S**
-
-- `SNMP` - *Simple Network Management Protocol*
-- `SMTP` - *Simple Mail Transfer Protocol*
-- `SMB` - *Server Message Block*
-- `SMQ` - *Simple Messaging Queue*
-- `SSD` - *Solid State Drive*
-- `SDDC` - *Software Defined Datacenter*
-- `SD-WAN` - *Software Defined Wide Area Network*
-- `SSL` - *Secure Sockets Layer*
-- `SSH` - *Secure Shell*
-- `SQL` - *Structured Query Language*
-- `SFTP` - *Secure Fire Transfer Protocol*
-- `SAFe` - *Scaled Agile Framework*
-- `SCSI` - *Small Computer System Interface*
-- `SPFF` - *Small Plugable Form Factor*
-- `SATA` - *Serial Advanced Technology Attachment*
-- `SRE` - *Site Reliability Engineering*
-- `S3` - *Simple Storage Service*
-- `SSN` - *Switched Service Network*
-- `SSSD` - *System Security Services Daemon*
-- `SSSN` - *Simplified Single-Sign On Protocol*
-
-## **T**
-
-- `TCP/IP` - *Transmission Control/ Internet Protocol*
-- `TTL` - *Time to Live*
-- `TFTP` - *Trivial File Transfer Protocol*
-- `TLS` - *Transport Layer Security*
-
-## **U**
-
-- `UDP` - *User Datagram Protocol*
-- `Unix` - *UNiplexed Information Computing System*
-
-## **V**
-
-- `VLAN` - *Virtual Local Area Network*
-- `VM` - *Virtual Machine*
-- `VXLAN` - *Virtual Extended Local Area Network*
-- `VPN` - *Virtual Private Network*
-- `VNC` - *Virtual Network Compting*
-- `VQP` - *Cisco VLAN Query Protocol*
-- `VRF` - *Virtual Routing And Forwarding*
-- `VIOP` - *Voice Over Internet Protocol*
-- `VRP` - *Virtual Routing Protocol*
-
-## **W**
-
-- `WAN` - *Wide Area Network*
-- `WWW` - *World Wide*
-- `Wi-Fi` - *Wireless Fidelity*
-
-## **X**
-
-- `XML` - *Extensible Markup Language*
-
-## **Y**
-
-## **Z**
-
-- `ZFS` - Zeta Bytep File System (Developed by Sun MicroSystem.)
+# **Acronyms**
+
+  - [**A**](#a)
+  - [**B**](#b)
+  - [**C**](#c)
+  - [**D**](#d)
+  - [**E**](#e)
+  - [**F**](#f)
+  - [**G**](#g)
+  - [**H**](#h)
+  - [**I**](#i)
+  - [**J**](#j)
+  - [**K**](#k)
+  - [**L**](#l)
+  - [**M**](#m)
+  - [**N**](#n)
+  - [**O**](#o)
+  - [**P**](#p)
+  - [**Q**](#q)
+  - [**R**](#r)
+  - [**S**](#s)
+  - [**T**](#t)
+  - [**U**](#u)
+  - [**V**](#v)
+  - [**W**](#w)
+  - [**X**](#x)
+  - [**Y**](#y)
+  - [**Z**](#z)
+
+## **A**
+
+- `AWS`     - *Amazon Web Services*
+- `Azure`   - *Azure Cloud*
+- `ABE`     - *Access Based Enumeration*
+- `AD`      - *Active Directory*
+- `ARP`     - *Address Resolution Protocol*
+- `AKS`     - *Azure K8S Service*
+
+## **B**
+
+- `Bit/ Bits`  - *Binary Digit/ Binary Digits*
+- `Byte`       - *8 bBits =1 Byte*
+- `BGP`        - *Border Gateway Protocol*
+
+## **C**
+
+- `CD`  - *Compact Disc*
+- `CSMA/CD` - *Carrier Sense Multiple Access with Collision Detection*
+- `CPU` - *Central Processing Unit*
+- `CIDR` - *Classless Inter-Domain Routing*
+- `CDN` - *Content Delivery Network*
+- `CSS` - *Cascading Styling Sheet*
+- `CI/CD` - *Continuous Delivery And Continuous Integratoion*
+
+## **D**
+
+- `DMZ` - *Demilitarized Zone*
+- `DPU` - *Data Processing Unit*
+- `DNS` - *Domain Name System*
+- `DBMS` - *Database Management System*
+- `DMA` - *Direct Memory Access*
+- `DP` - *Dynamic Programming*
+- `DVD` - *Digital Versatile Disc*
+- `DHCP` - *Dynamic Host Control Protocol*
+- `DLR` - *Distributed Logical Router*
+- `DVS` - *Distributed Virtual Switch*
+
+## **E**
+
+- `EBS` - *Elastic Block Storag*
+- `EKS` - *Elastic k8s Service*
+- `EC2` - *Elastic Cloud Compute*
+- `EOD` - *End Of the Day*
+- `ECMP` - *Equal Cost Multi Path Routing*
+
+## **F**
+
+- `fw`   - *Firewall*
+- `ftp`  - *File Transfer Protocol*
+- `fc`   - *Fiber Channel*
+- `FCOE` - *Fiber Channel Over Ethernet*
+- `FQDN` - *Fully Qualified Domain Name*
+
+## **G**
+
+- `GW`  - *Gateway*
+- `GFW` - *Gateway Firewall*
+- `GPU` - *Graphical Processing Unit*
+- `GB` - *1 GigaByte = 1024 MB*
+- `gRPC` - *Group RPC (RPC)by Google*
+- `GIT` - *Global Information Tracker*
+
+## **H**
+
+- `HDD` - *Hard Disc Drive*
+- `HTTP` - *Hypertext Transfer Protocol*
+- `HTTPS` - *Hypertext Transfer Protocol Secured*
+- `HTML` - *Hyper Text Markup Language*
+- `HLD` - *High Level Design*
+- `HDFS` - *Hadoop Distributed File System*
+
+## **I**
+
+- `IT` - *Information Technology*
+- `ITSM` - *IT Service Management*
+- `ITIL` - *Information Technology Infrastructure Library*
+- `IAM` - *Identity and Access Management*
+- `IRC` - *Internet Relay Chat*
+- `IPMI` - *Intelligent Platform Management Interface*
+- `iDRAC` - *Integrated Dell Remote Access Controller*
+- `iSCSI` - *Internet Small Computer System Interface*
+- `iQN` - *iSCSI Qualified Name*
+- `ICMP` - *Internet Control Message Protocol*
+
+## **J**
+
+- `JWT` - *JSON Web Token*
+- `JSON` - *JavaScript Object Notation*
+- `JS` - *Java Script*
+- `JIT` - *Just in Time*
+
+## **K**
+
+- `KB` - *Kilo Byte*
+- `k8s` - *Kubernetes*
+
+## **L**
+
+- `LDAP` - *Light-weight Directory Access Protocol*
+- `LLP`  - *Limited liability Partnership*
+- `LB`   - *Load Balancer*
+- `Linux` - *Lovable Intellect Not Using XP*
+- `LSB` - *Least Significant Bit*
+- `LLD` - *Low Level Design*
+- `LIDAR` - *Light Detection and Ranging*
+- `LLM` - *Large Language Model*
+- `LUN` - *Logical Unit Number*
+- `LAMP` - *Linux, Apache, MySQL, PHP/Perl/Python*
+
+## **M**
+
+- `MB` - *Mega Byte*
+- `MQ` - *Messaging Queue*
+- `MSB` - *Most Significant Bit*
+- `MTU` - *Maximum Transmission Unit*
+- `MVC` - *Model View Controller*
+- `MAC` - *Media Access Control*
+- `MVP` - *Most Viable Product*
+- `MoM` - *Minutes of Meeting*
+- `MERN` - *MongoDB, Express, React, Node*
+- `MEAN` - *MongoDB, Express, Angular, and Node*
+
+## **N**
+
+- `NTP` - *Network Time Protocol*
+- `NFS` - *Network File System*
+- `NvMe` - *Non-Volatile Memory*
+- `NoSQL` - *No Structured Quqry Language*
+- `NIC` - *Network Interface Card*
+- `NLP` - *Natual Language Processing*
+
+## **O**
+
+- `OSI` - *Open System Interconnection*
+- `OEM` - *Original Equipment Manufacturer*
+- `OS` - *Operating System*
+- `OSPF` - *Open Shortest Path First*
+
+## **P**
+
+- `PDL` - *Page Description Language*
+- `POP3` - *Post Office Protocol 3 over TLS/SSL*
+- `PB` - *1 PetaByte =  1024 TB*
+
+## **Q**
+
+- `QOS` - *Quality Of Service*
+- `OAuth` - *Open Authorization*
+
+## **R**
+
+- `RDP` - *Remote Desktop Protocol*
+- `RDBMS` - *Relational DBMS*
+- `RSYNC` - *Remote Sync*
+- `RAID` - *Redundant Array of Independent Dxisks*
+- `RMA` - *Return Merchandise Authorization*
+- `RDMA` - *Remote Direct Memory Access*
+- `RBAC` - *Role Based Access Control*
+- `RFB` - *Remote Frame Buffer*
+- `RPC` - *Remote Procedural Call*
+- `RAN` - *Radio Access Network*
+
+## **S**
+
+- `SNMP` - *Simple Network Management Protocol*
+- `SMTP` - *Simple Mail Transfer Protocol*
+- `SMB` - *Server Message Block*
+- `SMQ` - *Simple Messaging Queue*
+- `SSD` - *Solid State Drive*
+- `SDDC` - *Software Defined Datacenter*
+- `SD-WAN` - *Software Defined Wide Area Network*
+- `SSL` - *Secure Sockets Layer*
+- `SSH` - *Secure Shell*
+- `SQL` - *Structured Query Language*
+- `SFTP` - *Secure Fire Transfer Protocol*
+- `SAFe` - *Scaled Agile Framework*
+- `SCSI` - *Small Computer System Interface*
+- `SPFF` - *Small Plugable Form Factor*
+- `SATA` - *Serial Advanced Technology Attachment*
+- `SRE` - *Site Reliability Engineering*
+- `S3` - *Simple Storage Service*
+- `SSN` - *Switched Service Network*
+- `SSSD` - *System Security Services Daemon*
+- `SSSN` - *Simplified Single-Sign On Protocol*
+
+## **T**
+
+- `TCP/IP` - *Transmission Control/ Internet Protocol*
+- `TTL` - *Time to Live*
+- `TFTP` - *Trivial File Transfer Protocol*
+- `TLS` - *Transport Layer Security*
+
+## **U**
+
+- `UDP` - *User Datagram Protocol*
+- `Unix` - *UNiplexed Information Computing System*
+
+## **V**
+
+- `VLAN` - *Virtual Local Area Network*
+- `VM` - *Virtual Machine*
+- `VXLAN` - *Virtual Extended Local Area Network*
+- `VPN` - *Virtual Private Network*
+- `VNC` - *Virtual Network Compting*
+- `VQP` - *Cisco VLAN Query Protocol*
+- `VRF` - *Virtual Routing And Forwarding*
+- `VIOP` - *Voice Over Internet Protocol*
+- `VRP` - *Virtual Routing Protocol*
+
+## **W**
+
+- `WAN` - *Wide Area Network*
+- `WWW` - *World Wide*
+- `Wi-Fi` - *Wireless Fidelity*
+
+## **X**
+
+- `XML` - *Extensible Markup Language*
+
+## **Y**
+
+## **Z**
+
+- `ZFS` - Zeta Bytep File System (Developed by Sun MicroSystem.)
diff --git a/TuxTechBlogs/docs/topic/13.2. Miscellaneous/ports.md b/TuxTechBlogs/docs/topic/13.2. Miscellaneous/ports.md
index e1a7021..c7e295c 100644
--- a/TuxTechBlogs/docs/topic/13.2. Miscellaneous/ports.md	
+++ b/TuxTechBlogs/docs/topic/13.2. Miscellaneous/ports.md	
@@ -1,107 +1,107 @@
-# **Ports**
-
-## **Introduction**
-
-- Port number is a 16-bit numerical value that ranges from 0 to 65535. Well-known port (0-1023), registered port (1024-49151), and dynamic port is three types of port number space. (49152-65535).
-
-- These ports can be opened and used by software applications and operating system services to send and receive data over networks (LAN or WAN) that employ certain protocols (eg TCP, UDP).
-
-- To conclude, a port is a logical form to identify system activities or various network services used to create local or network-based communications.
-
-- For example, we use 80 for HTTP-web-based plain-text surfing and 443 for HTTPS-web-based encrypted websites in our daily work.
-
----
-
-## **What are the functions of ports?**
-
-- When interacting over the Internet, TCP and UDP protocols make connections, recompile data packages after the transfer, and then deliver them to applications on the recipient’s device.
-
-- For this handover to work, the operating system must install and open the gateway for the transfer.
-
-- Each door has a unique code number. After transmission, the receiving system uses the port number to determine where the data should be sent. The port numbers of the sender and receiver are always included in the data packet.
-
-- Ports are assigned sequential numbers from 0 to 65535. Some of these codes are standardized, meaning they are assigned to certain uses. Since code numbers are universally recognized and permanently assigned, these standard ports are also known as well-known ports.
-
-- Registered ports are those that organizations or software developers have registered for their applications. Registration is handled by the Internet Assigned Numbers Authority (IANA). A diverse selection of dynamically assigned port numbers is also available. For example, when viewing websites, browsers use these ports. After that, the phone number is free again.
-
----
-
-## **Why is it important to know these ports?**
-
-- Any security researcher, bug bounty hunter, or anyone working with service configuration would benefit from this.
-
-- Knowing how to do more thorough scans such as version detection or known vulnerabilities for ancient services that are still operating in the infrastructure, especially when using tools like Nmap, is handy when getting to know these protocols and services.
-
----
-
-## **The most 50 significant ports are listed here:**
-
-The following are some of the most common service names, transport protocol names, and port numbers used to differentiate between specific services that employ TCP, UDP, DCCP, and SCTP.
-
-| **Port Number** | **Service Name** |**Protocol Name/ Transport protocol**| **Desctriptin** |
-|----:|:----|:----|:----|
-| `7` | Echo | TCP, UDP | Echo Service |
-| `20` | FTP-data | TCP, SCTP | File Transfer Protocol data transfer |
-| `21` | FTP | TCP, UDP, SCTP | File Transfer Protocol (FTP) control connection |
-| `22` | SSH-SCP | TCP, UDP, SCTP |  Secure Shell, secure logins, file transfers (scp, sftp), and port forwarding |
-| `23` | Telnet | TCP | Telnet protocol—unencrypted text communications |
-| `25` | SMTP | TCP | Simple Mail Transfer Protocol, used for email routing between mail servers |
-| `53` | DNS | TCP, UDP |  Domain Name System name resolver |
-| `69` | TFTP | UDP | Trivial File Transfer Protocol |
-| `80` | HTTP | TCP, UDP, SCTP | Hypertext Transfer Protocol (HTTP) uses TCP in versions 1.x and 2. HTTP/3 uses QUIC, a transport protocol on top of UDP |
-| `88` | Kerberos | TCP, UDP | Network Authentication System, |
-| `102` | Iso-trap | TCP | ISO Transport Service Access Point (TSAP) Class 0 protocol |
-| `110` | POP3 | TCP | Post Office Protocol, version 3 (POP3) |
-| `135` | Microsoft EMAP | TCP,UDP | Microsoft EPMAP (End Point Mapper), also known as DCE/RPC Locator service, used to remotely manage services including DHCP server, DNS server, and WINS. Also used by DCOM|
-| `137` | NetBIOS-ns | TCP, UDP | NetBIOS Name Service, used for name registration and resolution |
-| `139` | NetBIOS-ssn | TCP, UDP | NetBIOS Session Service |
-| `143` | IMAP4 | TCP, UDP | Internet Message Access Protocol (IMAP), management of electronic mail messages on a server |
-| `381` | HP Openview | TCP, UDP | HP data alarm manager |
-| `388` | HP Openview | TCP, UDP | HP data performance collector |
-| `443` | HTTP over SSL | TCP, UDP, SCTP | Hypertext Transfer Protocol Secure (HTTPS) uses TCP in versions 1.x and 2. HTTP/3 uses QUIC, a transport protocol on top of UDP. |
-| `464` | Kerberos | TCP, UDP | Kerberos Change/Set password |
-| `465` | SMTP over TLS/SSL, SSM | TCP | Authenticated SMTP over TLS/SSL (SMTPS), URL Rendezvous Directory for SSM (Cisco protocol) |
-| `587` | SMTP | TCP | Email message submission |
-| `593` | Microsoft DCOM | TCP, UDP | HTTP RPC Ep Map, Remote procedure call over Hypertext Transfer Protocol, often used by Distributed Component Object Model services and Microsoft Exchange Server |
-| `636` | LDAP over TLS/SSL | TCP, UDP | Lightweight Directory Access Protocol over TLS/SSL |
-| `691` | MS Exchange| TCP | MS Exchange Routing |
-| `902` | VMware Server | unofficial | VMware ESXi |
-|  `989` | FTP over SSL | TCP, UDP | FTPS Protocol (data), FTP over TLS/SSL |
-|  `989` | FTP over SSL | TCP, UDP | FTPS Protocol (data), FTP over TLS/SSL |
-|  `993` | IMAP4 over SSL | TCP | Internet Message Access Protocol over TLS/SSL (IMAPS) |
-| `995` | POP3 over SSL | TCP, UDP | Post Office Protocol 3 over TLS/SSL |
-| `1025` | Microsoft RPC | TCP | Microsoft operating systems tend to allocate one or more unsuspected, publicly exposed services (probably DCOM, but who knows) among the first handful of ports immediately above the end of the service port range (1024+). |
-| `1194` | OpenVPN | TCP, UDP | OpenVPN |
-| `1337` | WASTE | unofficial | WASTE Encrypted File Sharing Program |
-| `1589` | Cisco VQP | TCP, UDP | Cisco VLAN Query Protocol (VQP) |
-| `1725` | Stream | UDP | Valve Steam Client uses port 1725 |
-| `2082` | cPanel | unofficial | cPanel default |
-| `2083` | radsec, cPanel | TCP, UDP | cPanel default |
-| `2483` | Oracle DB | TCP, UDP | Oracle database listening for insecure client connections to the listener, replaces port 1521 |
-| `2484` | Oracle DB | TCP, UDP | Oracle database listening for SSL client connections to the listener |
-| `2967` | Symantec AV | TCP, UDP | Symantec System Center agent (SSC-AGENT) |
-| `3074` | XBOX Live | TCP, UDP | Xbox LIVE and Games for Windows – Live |
-| `3306` | MySQL | TCP |  MySQL database system |
-| `3724` | World of Warcraft | TCP, UDP | Blizzard games, Unofficial Club Penguin Disney online game for kids |
-| `3389` | MS wbt-server | TCP | Microsoft Remote Desktop Protocol |
-| `4664` | Google Desktop | unofficial | Google Desktop Search |
-| `5432` | Postgres SQL | TCP | PostgreSQL database system |
-| `5900` | RFB/VNC Server| TCP | virtual Network Computing (VNC) Remote Frame Buffer (RFB) protocol |
-| `6665-6669` | IRC | TCP | Internet Relat Chat |
-| `6881` | BitTorrent | unofficial | BitTorrent is part of the full range of ports used most often |
-| `6970` | Quicktime | unofficial | QuickTime Streaming Server |
-| `6999` | BitTorrent | unofficial | BitTorrent is part of the full range of ports used most often |
-| `8086` | Kaspersky AV | TCP | Kaspersky AV Control Center |
-| `8087` | Kaspersky | UDP | Kaspersky AV Control Center |
-| `8222` | VMware Server | TCP, UDP | VMware Server Management User Interface (insecure Web interface). |
-| `9100` | PDL | TCP | PDL Data Stream, used for printing to certain network printers. |
-| `10000` | BackupExec | unofficial | Webmin, Web-based Unix/Linux system administration tool (default port) |
-| `12345` | NetBus | unofficial | NetBus remote administration tool (often Trojan horse). |
-| `27374` | Sub7 | unofficial | Sub7 default |
-| `31337` | Back Orifice | unofficial | Back Orifice 2000 remote administration tools |
-
----
-
-## **Miscellaneous**
-
-- To read about VMware Port read in the website click on [**ports.esp.vmware.com**](https://ports.esp.vmware.com)
+# **Ports**
+
+## **Introduction**
+
+- Port number is a 16-bit numerical value that ranges from 0 to 65535. Well-known port (0-1023), registered port (1024-49151), and dynamic port is three types of port number space. (49152-65535).
+
+- These ports can be opened and used by software applications and operating system services to send and receive data over networks (LAN or WAN) that employ certain protocols (eg TCP, UDP).
+
+- To conclude, a port is a logical form to identify system activities or various network services used to create local or network-based communications.
+
+- For example, we use 80 for HTTP-web-based plain-text surfing and 443 for HTTPS-web-based encrypted websites in our daily work.
+
+---
+
+## **What are the functions of ports?**
+
+- When interacting over the Internet, TCP and UDP protocols make connections, recompile data packages after the transfer, and then deliver them to applications on the recipient’s device.
+
+- For this handover to work, the operating system must install and open the gateway for the transfer.
+
+- Each door has a unique code number. After transmission, the receiving system uses the port number to determine where the data should be sent. The port numbers of the sender and receiver are always included in the data packet.
+
+- Ports are assigned sequential numbers from 0 to 65535. Some of these codes are standardized, meaning they are assigned to certain uses. Since code numbers are universally recognized and permanently assigned, these standard ports are also known as well-known ports.
+
+- Registered ports are those that organizations or software developers have registered for their applications. Registration is handled by the Internet Assigned Numbers Authority (IANA). A diverse selection of dynamically assigned port numbers is also available. For example, when viewing websites, browsers use these ports. After that, the phone number is free again.
+
+---
+
+## **Why is it important to know these ports?**
+
+- Any security researcher, bug bounty hunter, or anyone working with service configuration would benefit from this.
+
+- Knowing how to do more thorough scans such as version detection or known vulnerabilities for ancient services that are still operating in the infrastructure, especially when using tools like Nmap, is handy when getting to know these protocols and services.
+
+---
+
+## **The most 50 significant ports are listed here:**
+
+The following are some of the most common service names, transport protocol names, and port numbers used to differentiate between specific services that employ TCP, UDP, DCCP, and SCTP.
+
+| **Port Number** | **Service Name** |**Protocol Name/ Transport protocol**| **Desctriptin** |
+|----:|:----|:----|:----|
+| `7` | Echo | TCP, UDP | Echo Service |
+| `20` | FTP-data | TCP, SCTP | File Transfer Protocol data transfer |
+| `21` | FTP | TCP, UDP, SCTP | File Transfer Protocol (FTP) control connection |
+| `22` | SSH-SCP | TCP, UDP, SCTP |  Secure Shell, secure logins, file transfers (scp, sftp), and port forwarding |
+| `23` | Telnet | TCP | Telnet protocol—unencrypted text communications |
+| `25` | SMTP | TCP | Simple Mail Transfer Protocol, used for email routing between mail servers |
+| `53` | DNS | TCP, UDP |  Domain Name System name resolver |
+| `69` | TFTP | UDP | Trivial File Transfer Protocol |
+| `80` | HTTP | TCP, UDP, SCTP | Hypertext Transfer Protocol (HTTP) uses TCP in versions 1.x and 2. HTTP/3 uses QUIC, a transport protocol on top of UDP |
+| `88` | Kerberos | TCP, UDP | Network Authentication System, |
+| `102` | Iso-trap | TCP | ISO Transport Service Access Point (TSAP) Class 0 protocol |
+| `110` | POP3 | TCP | Post Office Protocol, version 3 (POP3) |
+| `135` | Microsoft EMAP | TCP,UDP | Microsoft EPMAP (End Point Mapper), also known as DCE/RPC Locator service, used to remotely manage services including DHCP server, DNS server, and WINS. Also used by DCOM|
+| `137` | NetBIOS-ns | TCP, UDP | NetBIOS Name Service, used for name registration and resolution |
+| `139` | NetBIOS-ssn | TCP, UDP | NetBIOS Session Service |
+| `143` | IMAP4 | TCP, UDP | Internet Message Access Protocol (IMAP), management of electronic mail messages on a server |
+| `381` | HP Openview | TCP, UDP | HP data alarm manager |
+| `388` | HP Openview | TCP, UDP | HP data performance collector |
+| `443` | HTTP over SSL | TCP, UDP, SCTP | Hypertext Transfer Protocol Secure (HTTPS) uses TCP in versions 1.x and 2. HTTP/3 uses QUIC, a transport protocol on top of UDP. |
+| `464` | Kerberos | TCP, UDP | Kerberos Change/Set password |
+| `465` | SMTP over TLS/SSL, SSM | TCP | Authenticated SMTP over TLS/SSL (SMTPS), URL Rendezvous Directory for SSM (Cisco protocol) |
+| `587` | SMTP | TCP | Email message submission |
+| `593` | Microsoft DCOM | TCP, UDP | HTTP RPC Ep Map, Remote procedure call over Hypertext Transfer Protocol, often used by Distributed Component Object Model services and Microsoft Exchange Server |
+| `636` | LDAP over TLS/SSL | TCP, UDP | Lightweight Directory Access Protocol over TLS/SSL |
+| `691` | MS Exchange| TCP | MS Exchange Routing |
+| `902` | VMware Server | unofficial | VMware ESXi |
+|  `989` | FTP over SSL | TCP, UDP | FTPS Protocol (data), FTP over TLS/SSL |
+|  `989` | FTP over SSL | TCP, UDP | FTPS Protocol (data), FTP over TLS/SSL |
+|  `993` | IMAP4 over SSL | TCP | Internet Message Access Protocol over TLS/SSL (IMAPS) |
+| `995` | POP3 over SSL | TCP, UDP | Post Office Protocol 3 over TLS/SSL |
+| `1025` | Microsoft RPC | TCP | Microsoft operating systems tend to allocate one or more unsuspected, publicly exposed services (probably DCOM, but who knows) among the first handful of ports immediately above the end of the service port range (1024+). |
+| `1194` | OpenVPN | TCP, UDP | OpenVPN |
+| `1337` | WASTE | unofficial | WASTE Encrypted File Sharing Program |
+| `1589` | Cisco VQP | TCP, UDP | Cisco VLAN Query Protocol (VQP) |
+| `1725` | Stream | UDP | Valve Steam Client uses port 1725 |
+| `2082` | cPanel | unofficial | cPanel default |
+| `2083` | radsec, cPanel | TCP, UDP | cPanel default |
+| `2483` | Oracle DB | TCP, UDP | Oracle database listening for insecure client connections to the listener, replaces port 1521 |
+| `2484` | Oracle DB | TCP, UDP | Oracle database listening for SSL client connections to the listener |
+| `2967` | Symantec AV | TCP, UDP | Symantec System Center agent (SSC-AGENT) |
+| `3074` | XBOX Live | TCP, UDP | Xbox LIVE and Games for Windows – Live |
+| `3306` | MySQL | TCP |  MySQL database system |
+| `3724` | World of Warcraft | TCP, UDP | Blizzard games, Unofficial Club Penguin Disney online game for kids |
+| `3389` | MS wbt-server | TCP | Microsoft Remote Desktop Protocol |
+| `4664` | Google Desktop | unofficial | Google Desktop Search |
+| `5432` | Postgres SQL | TCP | PostgreSQL database system |
+| `5900` | RFB/VNC Server| TCP | virtual Network Computing (VNC) Remote Frame Buffer (RFB) protocol |
+| `6665-6669` | IRC | TCP | Internet Relat Chat |
+| `6881` | BitTorrent | unofficial | BitTorrent is part of the full range of ports used most often |
+| `6970` | Quicktime | unofficial | QuickTime Streaming Server |
+| `6999` | BitTorrent | unofficial | BitTorrent is part of the full range of ports used most often |
+| `8086` | Kaspersky AV | TCP | Kaspersky AV Control Center |
+| `8087` | Kaspersky | UDP | Kaspersky AV Control Center |
+| `8222` | VMware Server | TCP, UDP | VMware Server Management User Interface (insecure Web interface). |
+| `9100` | PDL | TCP | PDL Data Stream, used for printing to certain network printers. |
+| `10000` | BackupExec | unofficial | Webmin, Web-based Unix/Linux system administration tool (default port) |
+| `12345` | NetBus | unofficial | NetBus remote administration tool (often Trojan horse). |
+| `27374` | Sub7 | unofficial | Sub7 default |
+| `31337` | Back Orifice | unofficial | Back Orifice 2000 remote administration tools |
+
+---
+
+## **Miscellaneous**
+
+- To read about VMware Port read in the website click on [**ports.esp.vmware.com**](https://ports.esp.vmware.com)
diff --git a/TuxTechBlogs/docs/topic/13.2. Miscellaneous/status_codes.md b/TuxTechBlogs/docs/topic/13.2. Miscellaneous/status_codes.md
index 1e8e6da..9c7b116 100644
--- a/TuxTechBlogs/docs/topic/13.2. Miscellaneous/status_codes.md	
+++ b/TuxTechBlogs/docs/topic/13.2. Miscellaneous/status_codes.md	
@@ -1,307 +1,307 @@
-# **Status Code**
-
-- [**Status Code**](#status-code)
-  - [**What Are HTTP Status Codes?**](#what-are-http-status-codes)
-  - [**Status Code Details**](#status-code-details)
-    - [**1XX HTTP Status Codes**](#1xx-http-status-codes)
-    - [**2XX HTTP Status Codes**](#2xx-http-status-codes)
-    - [**3XX HTTP Status Codes**](#3xx-http-status-codes)
-    - [**4XX HTTP Status Codes**](#4xx-http-status-codes)
-    - [**5XX HTTP Status Codes**](#5xx-http-status-codes)
-  - [**How to Check the HTTP Status Code of a Page**](#how-to-check-the-http-status-code-of-a-page)
-  - [**Error status code impact for short \& longer outage?**](#error-status-code-impact-for-short--longer-outage)
-
----
-
-## **What Are HTTP Status Codes?**
-
-- An HTTP status code is a three-digit number a server generates in response to a browser’s request Like 404, for example, which you’ve likely seen before.
-- Every time you visit a website, your browser sends a request to the site’s server Then, the server responds with an HTTP code status.
-- It’s like they’re having a conversation And each code indicates whether things are working or something is wrong.
-- The first digit in each status code begins with a number between one and five, indicating the code’s category The second two digits are for specific information under the category.
-- For example, let’s use 404 again.
-
-    1 The first digit (4) indicates a client error And specifically, 404 means the server couldn’t find the requested resource.
-    2 Meanwhile, 402 also shows a client error And the second and third digits tell us the server found the page but can’t access it due to a payment being required.
-
----
-
-> ## **The Complete List of HTTP Status Codes**
-
----
-
-![different*status*codes](https://i.postimg.cc/NF3GXV0j/different-status-codes.png)
-
----
-
-|Status Code| Function|
-|----:|:----|
-| `1XX — Informational codes` | The server acknowledges and is processing the request |
-| `100` | Continue |
-| `101` | Switching Protocols |
-| `102` | Processing |
-| `103` | Early Hints |
-| `2XX — Success codes` | The server successfully received, understood, and processed the request |
-| `200` | Ok |
-| `201` | Created |
-| `202` | Accepted |
-| `203` | Non-Authoritative Information |
-| `204` | No Content |
-| `205` | Reset Content |
-| `206` | Partial Content |
-| `207` | Multi-Status |
-| `208` | Already Reported |
-| `226` | IM Used |
-| `3XX — Redirection codes` | The server received the request, but there’s a redirect to somewhere else (or, in rare cases, some additional action other than a redirect must be completed) |
-| `300` | Multiple Choices |
-| `301` | Moved Permanently |
-| `302` | Found |
-| `303` | See Other |
-| `304` | Not Modified |
-| `307` | Temporary Redirect |
-| `308` | Permanent Redirect |
-| `4XX — Client error codes` | The server couldn’t find (or reach) the page or website This is an error on the site’s side |
-| `400` | Bad Request |
-| `401` | Unauthorized |
-| `402` | Payment Required |
-| `403` | Forbidden |
-| `404` | Not Found |
-| `405` | Method Not Allowed |
-| `406` | Not Acceptable |
-| `407` | Proxy Authentication Required |
-| `408` | Request Timeout |
-| `409` | Conflict |
-| `410` | Gone |
-| `411` | Length Required |
-| `412` | Precondition Failed |
-| `413` | Content Too Large |
-| `414` | URI Too Long |
-| `415` | Unsupported Media Type |
-| `416` | Range Not Satisfiable |
-| `417` | Expectation Failed |
-| `421` | Misdirected Request |
-| `422` | Unprocessable Content |
-| `423` | Locked |
-| `424` | Failed Dependency |
-| `425` | Too Early |
-| `426` | Upgrade Required |
-| `428` | Precondition Required |
-| `429` | Too Many Requests |
-| `431` | Request Header Fields Too Large |
-| `451` | Unavailable for Legal Reasons |
-| `5XX — Server error codes` | The client made a valid request, but the server failed to complete the request |
-| `500` | Internal Server Error |
-| `501` | Not Implemented |
-| `502` | Bad Gateway |
-| `503` | Service Unavailable |
-| `504` | Gateway Timeout |
-| `505` | HTTP Version Not Supported |
-| `506` | Variant Also Negotiates |
-| `507` | Insufficient Storage |
-| `508` | Loop Detected |
-| `511` | Network Authentication Required |
-
-## **Status Code Details**
-
-### **1XX HTTP Status Codes**
-
-This category is informational, temporary, and invisible to the client It indicates the server received the request and will proceed with it.
-
-- `100 — Continue`: This interim status code means the server received the initial request, and the client should continue.
-
-- `101 — Switching protocols`: This code is a response to an Upgrade header field request and states the protocol the server will switch to.
-
-- `102 — Processing`: This response indicates the server received and is processing the request, but no response is yet available.
-
-- `103 — Early hints`: This code is used with the Link header and allows the browser to preload resources while the server prepares a response.
-
-### **2XX HTTP Status Codes**
-
-This status code category encompasses successful responses.
-
-- `200 — OK`: This is the standard response for successful HTTP requests The actual meaning of the response depends on the request method used:
-
-   ```bash
-      GET: Resource obtained and is in the message body
-      HEAD: Headers are included in the response
-      TRACE: Message body contains the request message as received by the server
-      POST or PUT: Resource describing the result of the action sent is in the message body
-   ```
-
-- `201 — Created`: The request succeeded and a new resource was created This is usually the response after POST or PUT requests.
-
-- `202 — Accepted`: The request was accepted but is still in progress It’s used for cases where another server handles the request or for batch processing.
-
-- `203 — Non-Authoritative Information`: The data returned isn’t from the origin server Instead, it’s a modified version collected from a third party.
-
-- `204 — No Content`: The request was successfully processed, but there is no content The headers may be useful.
-
-- `205 — Reset Content`: The server fulfilled the request but asked the user to reset the document.
-
-- `206 — Partial Content`: The server is delivering part of the resource This response is used when the client sends a Range header to request only part of a resource.
-
-- `207 — Multi-Status`: Provides the statuses of multiple resources, depending on how many sub-requests were made.
-
-- `208 — Already Reported`: The members of a DAV:propstat element have already been listed and won’t be included again.
-
-- `226 — IM used`: The server completed a GET request And the response indicates one or more instance-manipulation results.
-
-### **3XX HTTP Status Codes**
-
-The status codes in this category show the resource is in a different location, and the user gets redirected as a result.
-
-- `300 — Multiple Choice`: The request has more than one possible response And the user should choose one of them.
-
-- `301 — Moved Permanently`: This redirect status code indicates the requested resource has permanently moved to a new URL The browser displays the new URL.
-
-- `302 — Found`: Previously known as “Moved Temporarily,” this code indicates the requested resource has temporarily moved to a new URL.
-
-- `303 — See Other`: The server redirects the user to the requested resource with a GET request at another URL.
-
-- `304 — Not Modified`: Used for caching purposes The response hasn’t been modified, so the client can continue to use the same cached version of the requested resource.
-
-- `307 — Temporary Redirect`: The requested resource temporarily moved to a different URL The only difference vis-a-vis the 302 code is the user must not change the HTTP method used.
-
-- `308 — Permanent Redirect`: The requested resource permanently moved to a different URL The difference between this code and 301 is the user must not change the HTTP request method.
-
-### **4XX HTTP Status Codes**
-
-This category indicates the server can’t reach a page due to an error on the client side.
-
-- `400 — Bad Request`: The server can’t or won’t process the request due to a client error For example, invalid request message framing, deceptive request routing, size too large, etc.
-
-- `401 — Unauthorized`: The user doesn’t have valid authentication credentials to get the requested resource.
-
-- `402 — Payment Required`: Reserved for future use; it was initially intended for digital payment systems It’s very rarely used, and no standard convention regulates it.
-
-- `403 — Forbidden`: The client doesn’t have access rights to the content For example, it may require a password Unlike the 401 HTTP error code, the server does know the client’s identity.
-
-- `404 — Not Found`: The server can’t find the requested resource, and no redirection has been set 404 errors can harm your SEO efforts.
-
-- `405 — Method Not Allowed`: The server supports the request method, but the target resource doesn’t.
-
-- `406 — Not Acceptable`: The server doesn’t find any content that satisfies the criteria given by the user according to the Accept headers requested.
-
-- `407 — Proxy Authentication Required`: This is similar to a 401, but a proxy must authenticate the client to continue.
-
-- `408 — Request Timeout`: The server timed out waiting because the client didn’t produce a request within the allotted time.
-
-- `409 — Conflict`: The server can’t fulfill the request because there’s a conflict with the resource It’ll display information about the problem so the client can fix it and resubmit.
-
-- `410 — Gone`: The content requested has been permanently deleted from the server and will not be reinstated.
-
-- `411 — Length Required`: The server rejects the request because it requires a defined
-Content-Length header field.
-
-- `412 — Precondition Failed`: The client indicates preconditions in the header fields that the server fails to meet.
-
-- `413 — Payload Too Large`: The client’s request is larger than the server’s defined limits, and the server refuses to process it.
-
-- `414 — URI Too Long`: The URI (Uniform Resource Identifier) requested by the client is too long for the server to process.
-
-- `415 — Unsupported Media Type`: The request uses a media format the server does not support.
-
-- `416 — Range Not Satisfiable`: The server can’t fulfill the value indicated in the request’s Range header field.
-
-- `417 — Expectation Failed`: The server can’t meet the requirements indicated by the Expect request header field.
-
-- `421 — Misdirected Request`: The client sends a request to a server that can’t produce a response.
-
-- `422 — Unprocessable Entity`: The client correctly sends the request, but the server can’t process it because of semantic errors or similar issues.
-
-- `423 — Locked`: The requested method’s resource is locked and inaccessible.
-
-- `424 — Failed Dependency`: The request failed because a request the initial request depended on also failed.
-
-- `425 — Too Early`: The server is unwilling to process a request that might be replayed.
-
-- `426 — Update Required`: The server refuses to process the request using the current protocol unless the client upgrades to a different protocol.
-
-- `428 — Precondition Required`: The server needs the request to be conditional.
-
-- `429 — Too Many Requests`: The user sends too many requests in a certain amount of time.
-
-- `431 — Request Header Fields Too Large`: The server can’t process the request because the header fields are too large.
-
-- `451 — Unavailable for Legal Reasons`: The user requests a resource the server can’t legally provide.
-
-### **5XX HTTP Status Codes**
-
-This category includes errors on the server side.
-
-They can be detrimental to your SEO, as search engines can prompt crawlers to slow down with crawling and remove indexed URLs that continually return these errors.
-
-- `500 — Internal Server Error`: The server has encountered an unexpected error and cannot complete the request.
-
-- `501 — Not Implemented`: The server can’t fulfill the request or doesn’t recognize the request method.
-
-- `502 — Bad Gateway`: The server acts as a gateway and gets an invalid response from an inbound host.
-
-- `503 — Service Unavailable`: The server is unable to process the request This often occurs when a server is overloaded or down for maintenance.
-
-- `504 — Gateway Timeout`: The server was acting as a gateway or proxy and timed out, waiting for a response.
-
-- `505 — HTTP Version Not Supported`: The server doesn’t support the HTTP version in the request.
-
-- `506 — Variant Also Negotiates`: The server has an internal configuration error.
-
-- `507 — Insufficient Storage`: The server doesn’t have enough storage to process the request successfully.
-
-- `508 — Loop Detected`: The server detects an infinite loop while processing the request.
-
-- `511 — Network Authentication Required`: The client must be authenticated to access the network The error should include a link where the user can submit credentials.
-  
----
-
-## **How to Check the HTTP Status Code of a Page**
-
-   - Some status codes are visible, while others are not If you want to check a page’s HTTP status code, you can use your browser, Google Search Console, or an SEO tool.
-
-     1. Open any page with the Chrome web browser and right-click anywhere on the screen Then, click **"Inspect"**.
-        ![webpage*inspect](https://i.postimg.cc/kX2fXH8t/webpage-inspect.png)
-
-     2. Now, select **“Network”** on the top menu.
-        ![webpage*network*menu](https://i.postimg.cc/43fcnKMF/webpage-network-menu.png)
-
-     3. You should see the status codes under the **“Status”** column.
-        ![webpage*network*status](https://i.postimg.cc/C1dfH3wG/webpage-network-status.png)
-        - Each row represents a resource And each column represents information about the resource.
-        - The top resource is usually the HTML document And the last resource is whatever was requested last.
-        - You’d use this web browser method if you don’t own or manage the website you’re inspecting.
-        - If you do own the webpage, the best way to check its HTTP status code is to use Google Search Console.
-
-   - Progratically using scripts or binaries you can check the Status code of web applications.
-
-   - CLI based tools/ UI based Web Applications can also be used to check status code.
-
----
-
-## **Error status code impact for short & longer outage?**
-
-If a webpage or API is giving error status codes for short durations or longer outages, it can have several consequences for the users and the business:
-
-> **Short Duration Errors/ Outages**
-
-   1. *Inconvenience to users*: Users may experience temporary errors while accessing the webpage or API, which can be frustrating and may lead to a negative user experience.
-   2. *Loss of data*: If the error occurs during a critical transaction, such as a payment or data submission, users may lose their progress and have to start again.
-   3. *Decreased productivity*: If the error occurs frequently, users may lose time and productivity trying to resolve the issue or find workarounds.
-
-> **Longer Duration Errors/ Outages:**
-
-   1. *Loss of revenue*: If the error occurs during a critical transaction, such as a payment or sales, the business may lose revenue and customers.
-   2. *Decreased user trust*: Frequent errors can lead to a loss of trust among users, which can negatively impact the business's reputation and customer loyalty.
-   3. *Increased support requests*: Longer duration errors can lead to an increase in support requests, which can be time-consuming and costly to resolve.
-   4. *Negative impact on SEO*: If the errors are not resolved quickly, it can negatively impact the business's search engine optimization (SEO) and reputation.
-   5. *Loss of data*: If the error occurs during a critical transaction, such as a payment or data submission, the business may lose important data, which can be difficult and costly to recover.
-   6. *Legal and compliance issues*: Depending on the nature of the error, it may lead to legal and compliance issues, such as data breaches or non-compliance with regulations.
-   7. *Increased maintenance costs*: Longer duration errors can lead to increased maintenance costs, as the business may need to invest in additional resources to resolve the issue.
-   8. *Decreased employee productivity*: If the error occurs frequently, employees may spend more time trying to resolve the issue, which can decrease their productivity and morale.
-
-> **To mitigate the risks associated with error status codes, it is important to have a robust error handling process in place, which includes:**
-
-   1. *Monitoring and logging*: Implementing monitoring and logging tools to track errors and identify the root cause.
-   2. *Error handling protocols*: Establishing error handling protocols to ensure that errors are resolved quickly and effectively.
-   3. *Communication*: Communicating with users and stakeholders about the error and the steps being taken to resolve it.
-   4. *Training*: Providing training to employees on error handling and troubleshooting.
-   5. *Regular maintenance*: Regularly maintaining and updating the system to prevent errors and improve performance.
-   6. *Redundancy*: Implementing redundancy measures to ensure that the system remains available even in the event of an error.
+# **Status Code**
+
+- [**Status Code**](#status-code)
+  - [**What Are HTTP Status Codes?**](#what-are-http-status-codes)
+  - [**Status Code Details**](#status-code-details)
+    - [**1XX HTTP Status Codes**](#1xx-http-status-codes)
+    - [**2XX HTTP Status Codes**](#2xx-http-status-codes)
+    - [**3XX HTTP Status Codes**](#3xx-http-status-codes)
+    - [**4XX HTTP Status Codes**](#4xx-http-status-codes)
+    - [**5XX HTTP Status Codes**](#5xx-http-status-codes)
+  - [**How to Check the HTTP Status Code of a Page**](#how-to-check-the-http-status-code-of-a-page)
+  - [**Error status code impact for short \& longer outage?**](#error-status-code-impact-for-short--longer-outage)
+
+---
+
+## **What Are HTTP Status Codes?**
+
+- An HTTP status code is a three-digit number a server generates in response to a browser’s request Like 404, for example, which you’ve likely seen before.
+- Every time you visit a website, your browser sends a request to the site’s server Then, the server responds with an HTTP code status.
+- It’s like they’re having a conversation And each code indicates whether things are working or something is wrong.
+- The first digit in each status code begins with a number between one and five, indicating the code’s category The second two digits are for specific information under the category.
+- For example, let’s use 404 again.
+
+    1 The first digit (4) indicates a client error And specifically, 404 means the server couldn’t find the requested resource.
+    2 Meanwhile, 402 also shows a client error And the second and third digits tell us the server found the page but can’t access it due to a payment being required.
+
+---
+
+> ## **The Complete List of HTTP Status Codes**
+
+---
+
+![different*status*codes](https://i.postimg.cc/NF3GXV0j/different-status-codes.png)
+
+---
+
+|Status Code| Function|
+|----:|:----|
+| `1XX — Informational codes` | The server acknowledges and is processing the request |
+| `100` | Continue |
+| `101` | Switching Protocols |
+| `102` | Processing |
+| `103` | Early Hints |
+| `2XX — Success codes` | The server successfully received, understood, and processed the request |
+| `200` | Ok |
+| `201` | Created |
+| `202` | Accepted |
+| `203` | Non-Authoritative Information |
+| `204` | No Content |
+| `205` | Reset Content |
+| `206` | Partial Content |
+| `207` | Multi-Status |
+| `208` | Already Reported |
+| `226` | IM Used |
+| `3XX — Redirection codes` | The server received the request, but there’s a redirect to somewhere else (or, in rare cases, some additional action other than a redirect must be completed) |
+| `300` | Multiple Choices |
+| `301` | Moved Permanently |
+| `302` | Found |
+| `303` | See Other |
+| `304` | Not Modified |
+| `307` | Temporary Redirect |
+| `308` | Permanent Redirect |
+| `4XX — Client error codes` | The server couldn’t find (or reach) the page or website This is an error on the site’s side |
+| `400` | Bad Request |
+| `401` | Unauthorized |
+| `402` | Payment Required |
+| `403` | Forbidden |
+| `404` | Not Found |
+| `405` | Method Not Allowed |
+| `406` | Not Acceptable |
+| `407` | Proxy Authentication Required |
+| `408` | Request Timeout |
+| `409` | Conflict |
+| `410` | Gone |
+| `411` | Length Required |
+| `412` | Precondition Failed |
+| `413` | Content Too Large |
+| `414` | URI Too Long |
+| `415` | Unsupported Media Type |
+| `416` | Range Not Satisfiable |
+| `417` | Expectation Failed |
+| `421` | Misdirected Request |
+| `422` | Unprocessable Content |
+| `423` | Locked |
+| `424` | Failed Dependency |
+| `425` | Too Early |
+| `426` | Upgrade Required |
+| `428` | Precondition Required |
+| `429` | Too Many Requests |
+| `431` | Request Header Fields Too Large |
+| `451` | Unavailable for Legal Reasons |
+| `5XX — Server error codes` | The client made a valid request, but the server failed to complete the request |
+| `500` | Internal Server Error |
+| `501` | Not Implemented |
+| `502` | Bad Gateway |
+| `503` | Service Unavailable |
+| `504` | Gateway Timeout |
+| `505` | HTTP Version Not Supported |
+| `506` | Variant Also Negotiates |
+| `507` | Insufficient Storage |
+| `508` | Loop Detected |
+| `511` | Network Authentication Required |
+
+## **Status Code Details**
+
+### **1XX HTTP Status Codes**
+
+This category is informational, temporary, and invisible to the client It indicates the server received the request and will proceed with it.
+
+- `100 — Continue`: This interim status code means the server received the initial request, and the client should continue.
+
+- `101 — Switching protocols`: This code is a response to an Upgrade header field request and states the protocol the server will switch to.
+
+- `102 — Processing`: This response indicates the server received and is processing the request, but no response is yet available.
+
+- `103 — Early hints`: This code is used with the Link header and allows the browser to preload resources while the server prepares a response.
+
+### **2XX HTTP Status Codes**
+
+This status code category encompasses successful responses.
+
+- `200 — OK`: This is the standard response for successful HTTP requests The actual meaning of the response depends on the request method used:
+
+   ```bash
+      GET: Resource obtained and is in the message body
+      HEAD: Headers are included in the response
+      TRACE: Message body contains the request message as received by the server
+      POST or PUT: Resource describing the result of the action sent is in the message body
+   ```
+
+- `201 — Created`: The request succeeded and a new resource was created This is usually the response after POST or PUT requests.
+
+- `202 — Accepted`: The request was accepted but is still in progress It’s used for cases where another server handles the request or for batch processing.
+
+- `203 — Non-Authoritative Information`: The data returned isn’t from the origin server Instead, it’s a modified version collected from a third party.
+
+- `204 — No Content`: The request was successfully processed, but there is no content The headers may be useful.
+
+- `205 — Reset Content`: The server fulfilled the request but asked the user to reset the document.
+
+- `206 — Partial Content`: The server is delivering part of the resource This response is used when the client sends a Range header to request only part of a resource.
+
+- `207 — Multi-Status`: Provides the statuses of multiple resources, depending on how many sub-requests were made.
+
+- `208 — Already Reported`: The members of a DAV:propstat element have already been listed and won’t be included again.
+
+- `226 — IM used`: The server completed a GET request And the response indicates one or more instance-manipulation results.
+
+### **3XX HTTP Status Codes**
+
+The status codes in this category show the resource is in a different location, and the user gets redirected as a result.
+
+- `300 — Multiple Choice`: The request has more than one possible response And the user should choose one of them.
+
+- `301 — Moved Permanently`: This redirect status code indicates the requested resource has permanently moved to a new URL The browser displays the new URL.
+
+- `302 — Found`: Previously known as “Moved Temporarily,” this code indicates the requested resource has temporarily moved to a new URL.
+
+- `303 — See Other`: The server redirects the user to the requested resource with a GET request at another URL.
+
+- `304 — Not Modified`: Used for caching purposes The response hasn’t been modified, so the client can continue to use the same cached version of the requested resource.
+
+- `307 — Temporary Redirect`: The requested resource temporarily moved to a different URL The only difference vis-a-vis the 302 code is the user must not change the HTTP method used.
+
+- `308 — Permanent Redirect`: The requested resource permanently moved to a different URL The difference between this code and 301 is the user must not change the HTTP request method.
+
+### **4XX HTTP Status Codes**
+
+This category indicates the server can’t reach a page due to an error on the client side.
+
+- `400 — Bad Request`: The server can’t or won’t process the request due to a client error For example, invalid request message framing, deceptive request routing, size too large, etc.
+
+- `401 — Unauthorized`: The user doesn’t have valid authentication credentials to get the requested resource.
+
+- `402 — Payment Required`: Reserved for future use; it was initially intended for digital payment systems It’s very rarely used, and no standard convention regulates it.
+
+- `403 — Forbidden`: The client doesn’t have access rights to the content For example, it may require a password Unlike the 401 HTTP error code, the server does know the client’s identity.
+
+- `404 — Not Found`: The server can’t find the requested resource, and no redirection has been set 404 errors can harm your SEO efforts.
+
+- `405 — Method Not Allowed`: The server supports the request method, but the target resource doesn’t.
+
+- `406 — Not Acceptable`: The server doesn’t find any content that satisfies the criteria given by the user according to the Accept headers requested.
+
+- `407 — Proxy Authentication Required`: This is similar to a 401, but a proxy must authenticate the client to continue.
+
+- `408 — Request Timeout`: The server timed out waiting because the client didn’t produce a request within the allotted time.
+
+- `409 — Conflict`: The server can’t fulfill the request because there’s a conflict with the resource It’ll display information about the problem so the client can fix it and resubmit.
+
+- `410 — Gone`: The content requested has been permanently deleted from the server and will not be reinstated.
+
+- `411 — Length Required`: The server rejects the request because it requires a defined
+Content-Length header field.
+
+- `412 — Precondition Failed`: The client indicates preconditions in the header fields that the server fails to meet.
+
+- `413 — Payload Too Large`: The client’s request is larger than the server’s defined limits, and the server refuses to process it.
+
+- `414 — URI Too Long`: The URI (Uniform Resource Identifier) requested by the client is too long for the server to process.
+
+- `415 — Unsupported Media Type`: The request uses a media format the server does not support.
+
+- `416 — Range Not Satisfiable`: The server can’t fulfill the value indicated in the request’s Range header field.
+
+- `417 — Expectation Failed`: The server can’t meet the requirements indicated by the Expect request header field.
+
+- `421 — Misdirected Request`: The client sends a request to a server that can’t produce a response.
+
+- `422 — Unprocessable Entity`: The client correctly sends the request, but the server can’t process it because of semantic errors or similar issues.
+
+- `423 — Locked`: The requested method’s resource is locked and inaccessible.
+
+- `424 — Failed Dependency`: The request failed because a request the initial request depended on also failed.
+
+- `425 — Too Early`: The server is unwilling to process a request that might be replayed.
+
+- `426 — Update Required`: The server refuses to process the request using the current protocol unless the client upgrades to a different protocol.
+
+- `428 — Precondition Required`: The server needs the request to be conditional.
+
+- `429 — Too Many Requests`: The user sends too many requests in a certain amount of time.
+
+- `431 — Request Header Fields Too Large`: The server can’t process the request because the header fields are too large.
+
+- `451 — Unavailable for Legal Reasons`: The user requests a resource the server can’t legally provide.
+
+### **5XX HTTP Status Codes**
+
+This category includes errors on the server side.
+
+They can be detrimental to your SEO, as search engines can prompt crawlers to slow down with crawling and remove indexed URLs that continually return these errors.
+
+- `500 — Internal Server Error`: The server has encountered an unexpected error and cannot complete the request.
+
+- `501 — Not Implemented`: The server can’t fulfill the request or doesn’t recognize the request method.
+
+- `502 — Bad Gateway`: The server acts as a gateway and gets an invalid response from an inbound host.
+
+- `503 — Service Unavailable`: The server is unable to process the request This often occurs when a server is overloaded or down for maintenance.
+
+- `504 — Gateway Timeout`: The server was acting as a gateway or proxy and timed out, waiting for a response.
+
+- `505 — HTTP Version Not Supported`: The server doesn’t support the HTTP version in the request.
+
+- `506 — Variant Also Negotiates`: The server has an internal configuration error.
+
+- `507 — Insufficient Storage`: The server doesn’t have enough storage to process the request successfully.
+
+- `508 — Loop Detected`: The server detects an infinite loop while processing the request.
+
+- `511 — Network Authentication Required`: The client must be authenticated to access the network The error should include a link where the user can submit credentials.
+  
+---
+
+## **How to Check the HTTP Status Code of a Page**
+
+   - Some status codes are visible, while others are not If you want to check a page’s HTTP status code, you can use your browser, Google Search Console, or an SEO tool.
+
+     1. Open any page with the Chrome web browser and right-click anywhere on the screen Then, click **"Inspect"**.
+        ![webpage*inspect](https://i.postimg.cc/kX2fXH8t/webpage-inspect.png)
+
+     2. Now, select **“Network”** on the top menu.
+        ![webpage*network*menu](https://i.postimg.cc/43fcnKMF/webpage-network-menu.png)
+
+     3. You should see the status codes under the **“Status”** column.
+        ![webpage*network*status](https://i.postimg.cc/C1dfH3wG/webpage-network-status.png)
+        - Each row represents a resource And each column represents information about the resource.
+        - The top resource is usually the HTML document And the last resource is whatever was requested last.
+        - You’d use this web browser method if you don’t own or manage the website you’re inspecting.
+        - If you do own the webpage, the best way to check its HTTP status code is to use Google Search Console.
+
+   - Progratically using scripts or binaries you can check the Status code of web applications.
+
+   - CLI based tools/ UI based Web Applications can also be used to check status code.
+
+---
+
+## **Error status code impact for short & longer outage?**
+
+If a webpage or API is giving error status codes for short durations or longer outages, it can have several consequences for the users and the business:
+
+> **Short Duration Errors/ Outages**
+
+   1. *Inconvenience to users*: Users may experience temporary errors while accessing the webpage or API, which can be frustrating and may lead to a negative user experience.
+   2. *Loss of data*: If the error occurs during a critical transaction, such as a payment or data submission, users may lose their progress and have to start again.
+   3. *Decreased productivity*: If the error occurs frequently, users may lose time and productivity trying to resolve the issue or find workarounds.
+
+> **Longer Duration Errors/ Outages:**
+
+   1. *Loss of revenue*: If the error occurs during a critical transaction, such as a payment or sales, the business may lose revenue and customers.
+   2. *Decreased user trust*: Frequent errors can lead to a loss of trust among users, which can negatively impact the business's reputation and customer loyalty.
+   3. *Increased support requests*: Longer duration errors can lead to an increase in support requests, which can be time-consuming and costly to resolve.
+   4. *Negative impact on SEO*: If the errors are not resolved quickly, it can negatively impact the business's search engine optimization (SEO) and reputation.
+   5. *Loss of data*: If the error occurs during a critical transaction, such as a payment or data submission, the business may lose important data, which can be difficult and costly to recover.
+   6. *Legal and compliance issues*: Depending on the nature of the error, it may lead to legal and compliance issues, such as data breaches or non-compliance with regulations.
+   7. *Increased maintenance costs*: Longer duration errors can lead to increased maintenance costs, as the business may need to invest in additional resources to resolve the issue.
+   8. *Decreased employee productivity*: If the error occurs frequently, employees may spend more time trying to resolve the issue, which can decrease their productivity and morale.
+
+> **To mitigate the risks associated with error status codes, it is important to have a robust error handling process in place, which includes:**
+
+   1. *Monitoring and logging*: Implementing monitoring and logging tools to track errors and identify the root cause.
+   2. *Error handling protocols*: Establishing error handling protocols to ensure that errors are resolved quickly and effectively.
+   3. *Communication*: Communicating with users and stakeholders about the error and the steps being taken to resolve it.
+   4. *Training*: Providing training to employees on error handling and troubleshooting.
+   5. *Regular maintenance*: Regularly maintaining and updating the system to prevent errors and improve performance.
+   6. *Redundancy*: Implementing redundancy measures to ensure that the system remains available even in the event of an error.
diff --git a/TuxTechBlogs/docs/topic/19.0. Scrum/00. Introduction.md b/TuxTechBlogs/docs/topic/19.0. Scrum/00. Introduction.md
index 9632bfc..d96b3c2 100644
--- a/TuxTechBlogs/docs/topic/19.0. Scrum/00. Introduction.md	
+++ b/TuxTechBlogs/docs/topic/19.0. Scrum/00. Introduction.md	
@@ -1,139 +1,139 @@
-- [**What is scrum?**](#what-is-scrum)
-- [**Overview**](#overview)
-- [**What's a sprint?**](#whats-a-sprint)
-- [**What are artifacts, events, and roles?**](#what-are-artifacts-events-and-roles)
-- [**What are the scrum artifacts?**](#what-are-the-scrum-artifacts)
-- [**What are the scrum events?**](#what-are-the-scrum-events)
-- [**Who's on the scrum team?**](#whos-on-the-scrum-team)
-- [**Summarization**](#summarization)
-
----
-
-## **What is scrum?**
-
-> ### **Scrum is a popular agile framework.**
-
-**Scrum**  is **focused on following a set of rules** and **delivering in time-boxed increments**. It encourages teams to self-organize and continuously improve.
-
----
-
-## **Overview**
-
-![scrum_overview](https://i.postimg.cc/yNGNBkzR/SCRUM-overview.png)
-
----
-
-## **What's a sprint?**
-
-- The first part of the cycle to explore is sprints. In scrum, **the team delivers work incrementally in short**, **time-boxed cycles called  sprints**. A sprint duration can be between one and four weeks long, depending on the team.
-- Sprints help break down a project into **manageable**, **bite-sized tasks**. This way, the team has the flexibility to reprioritize tasks as the project changes. 
-
----
-
-## **What are artifacts, events, and roles?**
-
-> ###  **They're critical components of the scrum framework.**
-
-Compared to kanban, scrum is more **rigid** and **prescriptive**. It has specific **artifacts**, **events**, and **roles** your team must practice. These can all be customized and adapted, but many teams aim to follow the original scrum framework closely. Let's take a closer look at them.
-
----
-
-## **What are the scrum artifacts?**
-
-**Artifacts**  are items that provide key information to make the sprint cycle successful.
-
-1. `Product Backlog` is the primary list of work that needs to get done. This is usually a long list of features, requirements, and fixes. It is, essentially, the entire team’s to do list. The product backlog is used as an input to decide what to work on for the next sprint.
- 
-2. The  `sprint backlog`  is the list of items to be completed in the current sprint cycle. The highest priority items from the product backlog are pulled into the `sprint backlog`.
-   
-3. The  `completed increment`  is the releasable product delivered at the end of a sprint. Typically, this is all the work that aligns with the  sprint goal  the team set at the beginning. Sometimes the `completed increment` is shipped to customers and shared with the world. Other times, the increment is meant only for internal audiences. Once the completed increment is delivered, the team is ready to start a new sprint cycle.
-
----
-
-## **What are the scrum events?**
-
-- Scrum  `events`, also called **ceremonies**, are full-team meetings to ensure everyone is in sync. 
-
-- Each team approaches scrum events differently. Some teams find that doing all the events is too repetitive, while others find them 100% necessary. Ask your team lead or scrum master how your team approaches events.
-
-> ### Below are the different ceremonies in Scrum:
-
-1. `Sprint Planning meeting` is to plan the work to be completed in the upcoming sprint and determine a sprint goal. 
-   - Work items are pulled from the **product backlog** to the **sprint backlog** in the meeting. At the end of the session, everyone on the team must be clear on the **sprint goal** and the tasks to be completed.
-   
-    ![SCRUM_sprint_planning](https://i.postimg.cc/R0KYCDkT/SCRUM-sprint-planning.png)
-
-2. `Daily Stand-Up` The  daily stand-up  (or daily scrum) is a short meeting for team members to share progress and voice concerns about blockers. 
-   - Typically 15 minutes long, the goal is to make sure everyone is on the same page.
-
-   - Some example questions team members may answer in the daily scrum are:
-      1. _What did I complete yesterday?_
-      2. _What do I plan to complete today?_
-      3. _Are there any blockers?_
-
-   - Every team approaches stand-ups differently. Some teams prefer to meet in person every day. Others prefer to connect async in Slack or Teams.
-     
-     ![SCRUM_daily_standup](https://i.postimg.cc/mg8DXmX8/SCRUM-daily-standup.png)
-
-3. `Sprint Review` is a meeting at the end of the sprint where the team shares a demonstration of the work completed, often related to the **sprint goal**.
-
-    - This meeting is often open to a broad audience of stakeholders who review and ask questions about the work.
-
-    - It's also where ideas for the next sprint start to form.
-
-        ![SCRUM_sprint_review](https://i.postimg.cc/jSG9bbF5/SCRUM-sprint-review.png)
-
-4. The  `Retrospective`  is an internal meeting after a sprint ends for the team to reflect on what worked well and what needs to be improved in the next sprint, including the project, people, tools, and events.
-   - The goal is to create a safe space for everyone to share their honest feedback, helping drive continuous improvement with every sprint cycle.
-    
-     ![SCRUM_retrospective](https://i.postimg.cc/htfWnM4C/SCRUM-retrospective.png)
-
----
-
-## **Who's on the scrum team?**
-
-- The people on the team bring the scrum framework to life. There are specific **roles** that should be on every scrum team.
-
-- Each scrum team should have **one product owner, one scrum master, and five to seven development team members.** 
-
-> ### Below are the different roles and their responsibilities in Scrum:
-
-1. `Product owners` understand the business, customer expectations, and market trends. They set the vision for the product and ensure the development team delivers the most value to the company. Each scrum team has only one product owner.
-
-    - Their responsibilities are to:
-      1. Craft the product vision
-      2. Build, manage, and prioritize the product backlog
-      3. Provide clear guidance on which features to deliver next
-      4. Decide when to ship the product
-
-2. `Scrum masters` **ensure the team is operating efficiently and in alignment with the scrum process.** They coach teams, product owners, and the business on the scrum process, and look for ways to fine-tune their practice of it. Each scrum team has only one scrum master.
-
-    - Their responsibilities are to:
-      1. Run sprint planning meetings
-      2. Facilitate daily stand-ups
-      3. Conduct retrospective meetings
-      4. Administer the scrum board
-      5. Meet 1:1 with team members as needed
-      6. Help eliminate blockers through workflow improvements
-
-3. The `development team` **is the group that completes the hands-on tasks in a sprint**. They're the ones that get the work done. With five to seven members, teams typically have a variety of skill sets: any role that helps complete the sprint goal, from design to engineering.
-
-    - Strong scrum teams are self-organizing and approach their projects with an evident ‘we’ attitude. All team members help one another to ensure a successful sprint completion.
-    - Their responsibilities are to:
-      1. Get the work done
-      2. Drive the sprint planning and goal setting
-      3. Forecast how much work they can complete
-
----
-
-## **Summarization**
-
-- Before a **sprint** begins, the **product owner** looks at the **product backlog** and determines which work items are the highest priority. 
-
-- Then, the **scrum master** leads a team-wide **sprint planning** meeting to pull work items from the **product backlog** to the **sprint backlog**. These are the work items the team will complete in the upcoming sprint.
-
-- The two-week sprint starts, and **team members** move their work items across the **scrum board**. Then, every day, the team meets for a short 15-minute **daily stand-up** where they share progress and address any blockers. 
-
-- At the end of the two weeks, the team met their **sprint goal** by delivering a **completed product increment**. Next, they host a **sprint review** meeting to share their work with stakeholders and gather feedback. Then, they have a retrospective meeting to discuss what they learned and what can be improved for future sprints.
-
+- [**What is scrum?**](#what-is-scrum)
+- [**Overview**](#overview)
+- [**What's a sprint?**](#whats-a-sprint)
+- [**What are artifacts, events, and roles?**](#what-are-artifacts-events-and-roles)
+- [**What are the scrum artifacts?**](#what-are-the-scrum-artifacts)
+- [**What are the scrum events?**](#what-are-the-scrum-events)
+- [**Who's on the scrum team?**](#whos-on-the-scrum-team)
+- [**Summarization**](#summarization)
+
+---
+
+## **What is scrum?**
+
+> ### **Scrum is a popular agile framework.**
+
+**Scrum**  is **focused on following a set of rules** and **delivering in time-boxed increments**. It encourages teams to self-organize and continuously improve.
+
+---
+
+## **Overview**
+
+![scrum_overview](https://i.postimg.cc/yNGNBkzR/SCRUM-overview.png)
+
+---
+
+## **What's a sprint?**
+
+- The first part of the cycle to explore is sprints. In scrum, **the team delivers work incrementally in short**, **time-boxed cycles called  sprints**. A sprint duration can be between one and four weeks long, depending on the team.
+- Sprints help break down a project into **manageable**, **bite-sized tasks**. This way, the team has the flexibility to reprioritize tasks as the project changes. 
+
+---
+
+## **What are artifacts, events, and roles?**
+
+> ###  **They're critical components of the scrum framework.**
+
+Compared to kanban, scrum is more **rigid** and **prescriptive**. It has specific **artifacts**, **events**, and **roles** your team must practice. These can all be customized and adapted, but many teams aim to follow the original scrum framework closely. Let's take a closer look at them.
+
+---
+
+## **What are the scrum artifacts?**
+
+**Artifacts**  are items that provide key information to make the sprint cycle successful.
+
+1. `Product Backlog` is the primary list of work that needs to get done. This is usually a long list of features, requirements, and fixes. It is, essentially, the entire team’s to do list. The product backlog is used as an input to decide what to work on for the next sprint.
+ 
+2. The  `sprint backlog`  is the list of items to be completed in the current sprint cycle. The highest priority items from the product backlog are pulled into the `sprint backlog`.
+   
+3. The  `completed increment`  is the releasable product delivered at the end of a sprint. Typically, this is all the work that aligns with the  sprint goal  the team set at the beginning. Sometimes the `completed increment` is shipped to customers and shared with the world. Other times, the increment is meant only for internal audiences. Once the completed increment is delivered, the team is ready to start a new sprint cycle.
+
+---
+
+## **What are the scrum events?**
+
+- Scrum  `events`, also called **ceremonies**, are full-team meetings to ensure everyone is in sync. 
+
+- Each team approaches scrum events differently. Some teams find that doing all the events is too repetitive, while others find them 100% necessary. Ask your team lead or scrum master how your team approaches events.
+
+> ### Below are the different ceremonies in Scrum:
+
+1. `Sprint Planning meeting` is to plan the work to be completed in the upcoming sprint and determine a sprint goal. 
+   - Work items are pulled from the **product backlog** to the **sprint backlog** in the meeting. At the end of the session, everyone on the team must be clear on the **sprint goal** and the tasks to be completed.
+   
+    ![SCRUM_sprint_planning](https://i.postimg.cc/R0KYCDkT/SCRUM-sprint-planning.png)
+
+2. `Daily Stand-Up` The  daily stand-up  (or daily scrum) is a short meeting for team members to share progress and voice concerns about blockers. 
+   - Typically 15 minutes long, the goal is to make sure everyone is on the same page.
+
+   - Some example questions team members may answer in the daily scrum are:
+      1. _What did I complete yesterday?_
+      2. _What do I plan to complete today?_
+      3. _Are there any blockers?_
+
+   - Every team approaches stand-ups differently. Some teams prefer to meet in person every day. Others prefer to connect async in Slack or Teams.
+     
+     ![SCRUM_daily_standup](https://i.postimg.cc/mg8DXmX8/SCRUM-daily-standup.png)
+
+3. `Sprint Review` is a meeting at the end of the sprint where the team shares a demonstration of the work completed, often related to the **sprint goal**.
+
+    - This meeting is often open to a broad audience of stakeholders who review and ask questions about the work.
+
+    - It's also where ideas for the next sprint start to form.
+
+        ![SCRUM_sprint_review](https://i.postimg.cc/jSG9bbF5/SCRUM-sprint-review.png)
+
+4. The  `Retrospective`  is an internal meeting after a sprint ends for the team to reflect on what worked well and what needs to be improved in the next sprint, including the project, people, tools, and events.
+   - The goal is to create a safe space for everyone to share their honest feedback, helping drive continuous improvement with every sprint cycle.
+    
+     ![SCRUM_retrospective](https://i.postimg.cc/htfWnM4C/SCRUM-retrospective.png)
+
+---
+
+## **Who's on the scrum team?**
+
+- The people on the team bring the scrum framework to life. There are specific **roles** that should be on every scrum team.
+
+- Each scrum team should have **one product owner, one scrum master, and five to seven development team members.** 
+
+> ### Below are the different roles and their responsibilities in Scrum:
+
+1. `Product owners` understand the business, customer expectations, and market trends. They set the vision for the product and ensure the development team delivers the most value to the company. Each scrum team has only one product owner.
+
+    - Their responsibilities are to:
+      1. Craft the product vision
+      2. Build, manage, and prioritize the product backlog
+      3. Provide clear guidance on which features to deliver next
+      4. Decide when to ship the product
+
+2. `Scrum masters` **ensure the team is operating efficiently and in alignment with the scrum process.** They coach teams, product owners, and the business on the scrum process, and look for ways to fine-tune their practice of it. Each scrum team has only one scrum master.
+
+    - Their responsibilities are to:
+      1. Run sprint planning meetings
+      2. Facilitate daily stand-ups
+      3. Conduct retrospective meetings
+      4. Administer the scrum board
+      5. Meet 1:1 with team members as needed
+      6. Help eliminate blockers through workflow improvements
+
+3. The `development team` **is the group that completes the hands-on tasks in a sprint**. They're the ones that get the work done. With five to seven members, teams typically have a variety of skill sets: any role that helps complete the sprint goal, from design to engineering.
+
+    - Strong scrum teams are self-organizing and approach their projects with an evident ‘we’ attitude. All team members help one another to ensure a successful sprint completion.
+    - Their responsibilities are to:
+      1. Get the work done
+      2. Drive the sprint planning and goal setting
+      3. Forecast how much work they can complete
+
+---
+
+## **Summarization**
+
+- Before a **sprint** begins, the **product owner** looks at the **product backlog** and determines which work items are the highest priority. 
+
+- Then, the **scrum master** leads a team-wide **sprint planning** meeting to pull work items from the **product backlog** to the **sprint backlog**. These are the work items the team will complete in the upcoming sprint.
+
+- The two-week sprint starts, and **team members** move their work items across the **scrum board**. Then, every day, the team meets for a short 15-minute **daily stand-up** where they share progress and address any blockers. 
+
+- At the end of the two weeks, the team met their **sprint goal** by delivering a **completed product increment**. Next, they host a **sprint review** meeting to share their work with stakeholders and gather feedback. Then, they have a retrospective meeting to discuss what they learned and what can be improved for future sprints.
+
 - And, that's it! The team is ready to repeat the scrum cycle all over again.
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/19.0. Scrum/01. Scrum With Jira.md b/TuxTechBlogs/docs/topic/19.0. Scrum/01. Scrum With Jira.md
index 3e8b520..cf57852 100644
--- a/TuxTechBlogs/docs/topic/19.0. Scrum/01. Scrum With Jira.md	
+++ b/TuxTechBlogs/docs/topic/19.0. Scrum/01. Scrum With Jira.md	
@@ -1,95 +1,95 @@
-> # Scrum board via Jira Software
-
-## **What's a scrum board?**
-
-> **Like kanban, scrum also uses a board to manage work items.**
-
-- The difference is that a kanban board has a continuous flow of work items and a scrum board has an estimated set of work items based on a time-boxed sprint cycle.
-
-- **As a team member, it's your responsibility to update the scrum board and use it to communicate.** Make sure you stay actively engaged with your board every day so your team is aware of the progress.`
-
-- To access your scrum board in Jira Software, navigate to the left sidebar and select Active sprints.
-    ![SCRUM_active_sprints](https://i.postimg.cc/4yDt3Wkz/SCRUM-active-sprints.gif)
-
-    > If you don't see an **Active Sprints** or **Sprints** option in your sidebar, you might be in a kanban board. You may need to change to a different board, or your team may not have a scrum board yet.
-
----
-
-## **What's your workflow?**
-
-- Now that you're viewing your team's board, take a look at the columns to identify your workflow. Every team uses a custom workflow, so yours may look different than the example below.
-
-- Spend some time with your workflow and understand the criteria to move work items across each of the columns.
-
-- Examine your board columns to understand your team's workflow.
-  ![SCRUM_workflow](https://i.postimg.cc/yNGNBkzR/SCRUM-overview.png)
-
----
-
-## **When does your sprint start and end?**
-
-- **Your scrum board gives you key information about your sprints**. First, are the number of days remaining in your sprint. This helps you plan and prioritize your work.
-
-- Toward the top right of your board, the tool shows you how many days are remaining in your current sprint. Hover your cursor over the days remaining and it provides the exact start and end date of your current sprint.
-
-- _To see the sprint start and end date, hover over the days remaining._
-
-  ![SRCUM_start_to_end](https://i.postimg.cc/RZzK5pTm/SCRUM-start-to-end.gif)
-
-## **What's in your backlog?**
-
-- **Your backlog holds the work items for future sprints**. In your planning meetings, you'll rank issues based on their importance or urgency. 
-
-To access your backlog, navigate to the project sidebar and select **Backlog**. This will bring you to a list of issues. You can drag and drop issues to different sprints in the backlog, depending on their importance.
-
-- _Below is shown how to find your backlog in Jira Software._
-  
-  ![SCRUM_backlog](https://i.postimg.cc/VNkgrsH4/SCRUM-backlog.gif)
-
-
-## **Let's consider an example.**
-
-> ### **How does this software development team use scrum?**
-
-**IceStream** is an iOS app that recommends movies to watch based on your ice cream preferences. The company uses the scrum framework to manage its software development work. The scrum team has six people: 
-
-1. **Sonia:** product owner
-2. **Kimball:** scrum master
-3. **Ahmed:** UX designer
-4. **Mike:** software developer
-5. **Isabelle:** software developer
-6. **Luis:** software developer
-
-- _Below explained how this team works._
-  
-  > **Planning**
-
-  - Before the new sprint starts, Sonia, the **product owner**, looks at customer feedback. Adding a new share button seems to be the most requested feature. Sonia moves this work to the top of the **product backlog**.
-
-  - Kimball, the **scrum master**, gathers the whole team for a **sprint planning meeting**. They discuss the new share button, create the tasks, and assign the tasks to the relevant team member. The group decides the **sprint goal** should be to deliver a working version of the share button in the app.
-
-  - Then, it's time to get to work! The two-week sprint begins, and Mike, Isabelle, Luis, and Ahmed start working on their tasks.
-    
-    ![SCRUM_planning_diagram](https://i.postimg.cc/1zXzLDbP/SCRUM-planning-diagram.png)
-  
-  > **Stand-UP**
-
-  - On the fourth day of the sprint, Luis raises a problem at the **daily stand-up** a code error! He tried everything to fix it but ran out of ideas. 
-  
-  - Kimball, the **scrum master**, suggests Luis and Isabelle spend some time digging into the problem. Isabelle has more experience in this area and can probably help. 
-  
-  - Luis and Isabelle schedule a 45-minute call together. They talk through the problem and find a solution to move forward. Great job, Isabelle!
-
-    ![SCRUM_stand-up_diagram](https://i.postimg.cc/d19SrTtk/SCRUM-stand-up-diagram.png)
-
-  > **Review And Retro**
-
-  - At the end of the two weeks, the sprint is complete. The team met their **sprint goal** and delivered a working version of the share button.
-
-  - Everyone on the dev team takes turns presenting the share button at the **sprint review**. They show its functionality and the reason why this was the top priority for this sprint.
-  
-  - The final step is a **retrospective** of what the team learned and what can be improved. Ahmed suggested more communication is needed, as he didn't think he have enough information when key decisions were being made. Kimball documents this feedback and considers ways for the team to improve for the next sprint.
-  
-  - Successful sprint cycle! Now the team is ready to do it all over again. Sonia opens the **product backlog** and looks for the next high-priority items.
-
+> # Scrum board via Jira Software
+
+## **What's a scrum board?**
+
+> **Like kanban, scrum also uses a board to manage work items.**
+
+- The difference is that a kanban board has a continuous flow of work items and a scrum board has an estimated set of work items based on a time-boxed sprint cycle.
+
+- **As a team member, it's your responsibility to update the scrum board and use it to communicate.** Make sure you stay actively engaged with your board every day so your team is aware of the progress.`
+
+- To access your scrum board in Jira Software, navigate to the left sidebar and select Active sprints.
+    ![SCRUM_active_sprints](https://i.postimg.cc/4yDt3Wkz/SCRUM-active-sprints.gif)
+
+    > If you don't see an **Active Sprints** or **Sprints** option in your sidebar, you might be in a kanban board. You may need to change to a different board, or your team may not have a scrum board yet.
+
+---
+
+## **What's your workflow?**
+
+- Now that you're viewing your team's board, take a look at the columns to identify your workflow. Every team uses a custom workflow, so yours may look different than the example below.
+
+- Spend some time with your workflow and understand the criteria to move work items across each of the columns.
+
+- Examine your board columns to understand your team's workflow.
+  ![SCRUM_workflow](https://i.postimg.cc/yNGNBkzR/SCRUM-overview.png)
+
+---
+
+## **When does your sprint start and end?**
+
+- **Your scrum board gives you key information about your sprints**. First, are the number of days remaining in your sprint. This helps you plan and prioritize your work.
+
+- Toward the top right of your board, the tool shows you how many days are remaining in your current sprint. Hover your cursor over the days remaining and it provides the exact start and end date of your current sprint.
+
+- _To see the sprint start and end date, hover over the days remaining._
+
+  ![SRCUM_start_to_end](https://i.postimg.cc/RZzK5pTm/SCRUM-start-to-end.gif)
+
+## **What's in your backlog?**
+
+- **Your backlog holds the work items for future sprints**. In your planning meetings, you'll rank issues based on their importance or urgency. 
+
+To access your backlog, navigate to the project sidebar and select **Backlog**. This will bring you to a list of issues. You can drag and drop issues to different sprints in the backlog, depending on their importance.
+
+- _Below is shown how to find your backlog in Jira Software._
+  
+  ![SCRUM_backlog](https://i.postimg.cc/VNkgrsH4/SCRUM-backlog.gif)
+
+
+## **Let's consider an example.**
+
+> ### **How does this software development team use scrum?**
+
+**IceStream** is an iOS app that recommends movies to watch based on your ice cream preferences. The company uses the scrum framework to manage its software development work. The scrum team has six people: 
+
+1. **Sonia:** product owner
+2. **Kimball:** scrum master
+3. **Ahmed:** UX designer
+4. **Mike:** software developer
+5. **Isabelle:** software developer
+6. **Luis:** software developer
+
+- _Below explained how this team works._
+  
+  > **Planning**
+
+  - Before the new sprint starts, Sonia, the **product owner**, looks at customer feedback. Adding a new share button seems to be the most requested feature. Sonia moves this work to the top of the **product backlog**.
+
+  - Kimball, the **scrum master**, gathers the whole team for a **sprint planning meeting**. They discuss the new share button, create the tasks, and assign the tasks to the relevant team member. The group decides the **sprint goal** should be to deliver a working version of the share button in the app.
+
+  - Then, it's time to get to work! The two-week sprint begins, and Mike, Isabelle, Luis, and Ahmed start working on their tasks.
+    
+    ![SCRUM_planning_diagram](https://i.postimg.cc/1zXzLDbP/SCRUM-planning-diagram.png)
+  
+  > **Stand-UP**
+
+  - On the fourth day of the sprint, Luis raises a problem at the **daily stand-up** a code error! He tried everything to fix it but ran out of ideas. 
+  
+  - Kimball, the **scrum master**, suggests Luis and Isabelle spend some time digging into the problem. Isabelle has more experience in this area and can probably help. 
+  
+  - Luis and Isabelle schedule a 45-minute call together. They talk through the problem and find a solution to move forward. Great job, Isabelle!
+
+    ![SCRUM_stand-up_diagram](https://i.postimg.cc/d19SrTtk/SCRUM-stand-up-diagram.png)
+
+  > **Review And Retro**
+
+  - At the end of the two weeks, the sprint is complete. The team met their **sprint goal** and delivered a working version of the share button.
+
+  - Everyone on the dev team takes turns presenting the share button at the **sprint review**. They show its functionality and the reason why this was the top priority for this sprint.
+  
+  - The final step is a **retrospective** of what the team learned and what can be improved. Ahmed suggested more communication is needed, as he didn't think he have enough information when key decisions were being made. Kimball documents this feedback and considers ways for the team to improve for the next sprint.
+  
+  - Successful sprint cycle! Now the team is ready to do it all over again. Sonia opens the **product backlog** and looks for the next high-priority items.
+
     ![SCRUM_review_and_retro_diagram](https://i.postimg.cc/PJt9RQFQ/SCRUM-review-and-retro-diagram.png)
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/4.0. DevOps/00. Introduction.md b/TuxTechBlogs/docs/topic/4.0. DevOps/00. Introduction.md
index 5146165..c529613 100644
--- a/TuxTechBlogs/docs/topic/4.0. DevOps/00. Introduction.md	
+++ b/TuxTechBlogs/docs/topic/4.0. DevOps/00. Introduction.md	
@@ -1,221 +1,221 @@
-<center>
-  <img src="https://miro.medium.com/max/1400/0*Sb7aHQbMFEdlPY29" alt="Banner" title="DevOps Banner" style="max-width: 80%; height: auto;">
-</center>
-
-
-# **♾️DevOps**
-
-DevOps Roadmap, Resources & Study Materials
-
-- [Mindset](#mindset)
-- [Defination Of DevOps](#defination-of-devops)
-- [Branches](#branches)
-- [Prerequisite](#prerequisite)
-- [Oppportunities And Salary](#opportunities-and-salary)
-- [Resouces To Study And Learn](#resouces-to-study-and-learn)
-- [Techniques For Interview And Jobs ](#techniques-for-interview-and-jobs)
-- [Websites To Apply For Jobs](#websites-to-apply-for-jobs)
-- [FAQs](#faqs)
-
-## **🧠 Mindset**
-
->🔥 I have learnt devops from internet without spending a single penny. These below points has worked for me pretty fine.
-
->🔥 I had always interest towards troubleshooting systems, Operating system upgrade/reimage, reading tech vlogs, study and follow people from different socia media platfroms, which helped to be hungry for developing new skills.
-
-> 🔥 DevOps doamin does'nt keep you in a static technology stack,which I think is the best for your carrier growth.
-
-> 🔥 Learn something daily in the area of interest so that you can compund that knowledge over time.
-
-> 🔥 Start as a zero and learn still you are able to master it.
-
-> 🔥 Be hungry to learn, make your self a learner for life.
-
-> 🔥 Take part in open-souce conferences.
-
-## **📜 Defination of DevOps**
-
-> **💡Note**
->
-> DevOps is a set of practices that combines software development and IT operations. It aims to shorten the systems development life cycle and provide continuous delivery with high software quality.
-
-- DevOps is complementary with Agile software development.
-- Several DevOps aspects came from the **Agile methodology.**
-
-## **🌵 Branches**
-
-DevOps can be divided into two different more niche domain. And the sub-domains under devops require interest over network, hacking and securiy. 
-
-- **DevOpsSec**, i.e. DevOps With Security
-- **OpsSec**,   i.e. Oprations Security
-
-Please do your own reseach for these subdomains, if you find any of them interesting.
-
-
-## **⚗️ Prerequisite**
-
-All the mentioned list item requires basic overall knowledge
-
-1. Software Developement Life Cycle
-2. Operating System
-3. Linux Administration
-4. Networking
-5. Programming Language : C++/Java
-6. Scripting Language : Python/ Shell Scripting / Windows Batch Scripting
-7. Servers, VMs, WSL (Windows Subsystem Linux)
-8. Basics of System Design. i.e. how to scale a application from sractch.
-9. Version Control System (Git/Github, SVN )
-10. Building a code base, build tools, IDE, IaaS, IaaC
-11. Automation
-12. Cloud (GCP/ AWS/ Azure), PaaS
-13. DataBase (SQL, NoSQL)
-
-## **🎒 Oppportunities And Salary**
-
-- One thing to keep in mind, that experienced DevOps engineers are getting their cloud certification as the world is moving towards cloud. So if you want to be in a better positon, my suggestion will be to have some cloud knowledge to land in a better job.
-- Let's hear from people, who are actually done the transition to devops and happliy working on the domain:
-
-
-    [![Salary And Compensation for DevOps By Kunal Kushwaha](https://img.youtube.com/vi/r40DtAzZvcY/mqdefault.jpg)](https://www.youtube.com/watch?v=r40DtAzZvcY)
-    [![QA to DevOps](https://img.youtube.com/vi/thLVD5vtJKE/mqdefault.jpg)](https://www.youtube.com/watch?v=thLVD5vtJKE)
-    [![Highly Paid Domain](https://img.youtube.com/vi/ybAY-q4-d9Q/mqdefault.jpg)](https://www.youtube.com/watch?v=ybAY-q4-d9Q)
-    [![DevOps International Opportunities](https://img.youtube.com/vi/bTMVj6DPdnY/mqdefault.jpg)](https://www.youtube.com/watch?v=bTMVj6DPdnY)
-    [![DevOps International Opportunities](https://img.youtube.com/vi/xcxrp5sEBtI/mqdefault.jpg)](https://www.youtube.com/watch?v=xcxrp5sEBtI)
-
-
-## **👨‍💻 Resouces To Study And Learn**
-
-Most of the resources are free. But there is in anthing paid found from the links, please do a market reseach before spending a single penny.
-
-
-### **✨ Videos To Start Growing Your Interest**
-        
-#### *What is Devops ?*
-
-| `Videos` |
-|:-- |
-|[![Introduction To DevOps By SimpliLearn](https://img.youtube.com/vi/Xrgk023l4lI/mqdefault.jpg)](https://www.youtube.com/watch?v=Xrgk023l4lI)|
-|[![Introduction To DevOps by Hitesh](https://img.youtube.com/vi/_Gpe1Zn-1fE/mqdefault.jpg)](https://www.youtube.com/watch?v=_Gpe1Zn-1fE)|
-|[![Introduction To DevOps by SimpliLearn](https://img.youtube.com/vi/Me3ea4nUt0U/mqdefault.jpg)](https://www.youtube.com/watch?v=Me3ea4nUt0U)|
-
-#### *What is DevOpsSec ?*
-        
-| `Title` | `Video` |
-|:--|:--| 
-| Introduction To DevSecOps | [![Introduction To DevSecOps](https://img.youtube.com/vi/nrhxNNH5lt0/mqdefault.jpg)](https://www.youtube.com/watch?v=nrhxNNH5lt0) |
-| Define DevSecOPs | [![Introduction To DevSecOps](https://img.youtube.com/vi/iaafAnFX_0E/mqdefault.jpg)](https://www.youtube.com/watch?v=iaafAnFX_0E) |
-
-#### *What is OpsSec ?*
-
-| `Title` | `Video` |
-|:--|:--|
-| Introduction To OpsSec | [![Introduction To DevSecOps](https://img.youtube.com/vi/X59NFibpQu4/mqdefault.jpg)](https://www.youtube.com/watch?v=X59NFibpQu4) |
-| OpsSec in 1 Minute | [![Introduction To DevSecOps](https://img.youtube.com/vi/jp2o-56SzdM/mqdefault.jpg)](https://www.youtube.com/watch?v=jp2o-56SzdM) |
-
-### **YouTube Channels**
-
-- *Learning Channels*
-    - [Edureka!](https://www.youtube.com/c/edurekaIN)
-    - [SimpliLearn](https://www.youtube.com/c/SimplilearnOfficial)
-    - [DevOps Journey](https://www.youtube.com/channel/UC4Snw5yrSDMXys31I18U3gg)
-    - [FreeCodeCamp.Org](https://www.youtube.com/c/Freecodecamp)
-    - [Abhishek Viremalla](https://www.youtube.com/AbhishekVeeramalla)
-    - [Kunal Kushwaha](https://www.youtube.com/KunalKushwaha)
-    - [TechWorld With NaNa](https://www.youtube.com/TechWorldwithNana)
-
-- *DevOps Individual as YouTube Vloger*
-    - [Kunal Kushwaha](https://www.youtube.com/c/KunalKushwaha)
-    - [DevOps Directive](https://www.youtube.com/channel/UC4MdpjzjPuop_qWNAvR23JA)
-    - [TechWorldwithNana](https://www.youtube.com/c/TechWorldwithNana)
-
-- *RoadMap Video*
-    - [DevOps Roadmap 2022](https://www.youtube.com/watch?v=9pZ2xmsSDdo)
-    - [DevOps 0 to 100 Complete Guidance](https://www.youtube.com/watch?v=dhJR0YUM3Dg)
-
-- *Archive*
-    - [GFG](https://www.geeksforgeeks.org/tag/devops/)
-
-
-### **🎓 BootCamps**
-
-- [ 🔥DevOps BootCamp by **Kunal Kushwaha**](https://www.youtube.com/playlist?list=PL9gnSGHSqcnoqBXdMwUTRod4Gi3eac2Ak)
-- [ 🔥DevOps Zero to Hero by **Abhishek Viramalla**](https://youtube.com/playlist?list=PLdpzxOOAlwvIKMhk8WhzN1pYoJ1YU8Csa&si=lgC2FaV_uqCgSBtu)
-- [ 🔥 Full 11 Hours DevOps Tutorial by **Edureka!** ](https://www.youtube.com/watch?v=S_0q75eD8Yc)
-- [ 🔥 DevOps Tutorial For Beginners by **Simplilearn** ](https://youtube.com/playlist?list=PLEiEAq2VkUUJS6zkGgXeWw9l32EwRoYdR)
-- [ 🔥 DevOps Engineering Course for Beginners by **FreeCodeCamp.Org** ](https://www.youtube.com/watch?v=j5Zsa_eOXeY)
-
-### **Github Repos**
-
-- [90 Days Of DevOps by Michael Cade](https://github.com/MichaelCade/90DaysOfDevOps)
-- [DevOps Guide by Tikam2](https://github.com/Tikam02/DevOps-Guide)
-
-### **List Of Skills & Tools for DevOps Industry**
-
-[![Introduction To DevSecOps](https://img.youtube.com/vi/1pPHdvrUunY/mqdefault.jpg)](https://www.youtube.com/watch?v=1pPHdvrUunY)
-
-### **Communities**
-
-- [Community Classrooms](https://www.commclassroom.org/home)
-- [Discord DevOps Community Servers](https://disboard.org/servers/tag/devops)
-- [DevOps Community in Reddit](https://www.reddit.com/r/devops/)
-
-### **Techniques For Interview And Jobs**
-
-1. *Tips & Strategy*
-     
-    | `Title` | `Video` |
-    | :-- | :-- |
-    | FIVE things to Crack DevOps Interview | [![FIVE things to Crack DevOps Interview](https://img.youtube.com/vi/qUu7FzRo7p4/mqdefault.jpg)](https://www.youtube.com/watch?v=qUu7FzRo7p4) |
-    | How do I prepare for Cloud or DevOps Interviews?  | [![How do I prepare for Cloud or DevOps Interviews?](https://img.youtube.com/vi/JYAA2G-muZY/mqdefault.jpg)](https://www.youtube.com/watch?v=JYAA2G-muZY) |
-    | Devops Interview Questions by Simplilearn  | [![Devops Interview Questions by Simplilearn](https://img.youtube.com/vi/WxjJlYFIWtI/mqdefault.jpg)](https://www.youtube.com/watch?v=WxjJlYFIWtI) |
-    | DevOps Interview Questions by Edureka | [![DevOps Interview Questions by Edureka](https://img.youtube.com/vi/clZgb8GA6xI/mqdefault.jpg)](https://www.youtube.com/watch?v=clZgb8GA6xI) |
-    | DevOps Interview Questions by Intellipaat | [![DevOps Interview Questions by Intellipaat](https://img.youtube.com/vi/oG8I8kds8rI/mqdefault.jpg)](https://www.youtube.com/watch?v=oG8I8kds8rI) |
-
-2. *Interview Question Dumps*
-
-    - [Interviewbit DevOps Interview Questions](https://www.interviewbit.com/devops-interview-questions/)
-    - [Edureka! DevOps Interview Questions](https://www.edureka.co/blog/interview-questions/top-devops-interview-questions-2016/)
-
-
-### **Websites To Apply For Jobs** 
-
-1. Remote
-    - [Arc()](https://arc.dev/)
-    - [Turing.com](https://www.turing.com)
-    - [AngleList](https://angel.co/)
-    - [Remote](https://remote.com/)
-    - [We Work Remotely](https://weworkremotely.com/)
-    - [Twitter](https://twitter.com)
-    - [Reddit](https://www.reddit.com/r/devopsjobs/)
-2. Physical Jobs
-    - LinkedIn
-    - Referals
-    - Off Campus Hiring
-    - Naurki
-
-### **Use These Tools To Maximize Of Getting Selected :**
-
-1. *Resume ATS Tool*
-    - This tool is a exactly what companies use to filter out potential candidates from huge pile of application : [ResumeWorded.com](https://resumeworded.com/)
-2. Crome Extension
-    - AI enabled Job applying tool : [Jobseer.ai](https://jobseer.ai/)
-3. *Resume Creating Websites*
-    - Google Docs
-    - LinkedIn By default create a resume based on what you have written on your linkedin profile.
-    - [Overleaf](https://www.overleaf.com/)
-    - [FlowCV.io](https://flowcv.io/)
-4. **Check Salary Range Of Any Job of Any Company, Check :** [AmbitionBox](https://www.ambitionbox.com)
-
-
-### **FAQs**
-
-1. What is DevOps, DevOpsSec, OpsSec? 
-2. What are thre prerequisites for getting into devops? 
-3. What is the growth into devops ? And salary into DevOps ? 
-4. What are the resources to learn devops ? 
-5. How to apply for a devops engineer remote and physical jobs? 
-6. How is the community of DevOps ? 
-
-
-
-
+<center>
+  <img src="https://miro.medium.com/max/1400/0*Sb7aHQbMFEdlPY29" alt="Banner" title="DevOps Banner" style="max-width: 80%; height: auto;">
+</center>
+
+
+# **♾️DevOps**
+
+DevOps Roadmap, Resources & Study Materials
+
+- [Mindset](#mindset)
+- [Defination Of DevOps](#defination-of-devops)
+- [Branches](#branches)
+- [Prerequisite](#prerequisite)
+- [Oppportunities And Salary](#opportunities-and-salary)
+- [Resouces To Study And Learn](#resouces-to-study-and-learn)
+- [Techniques For Interview And Jobs ](#techniques-for-interview-and-jobs)
+- [Websites To Apply For Jobs](#websites-to-apply-for-jobs)
+- [FAQs](#faqs)
+
+## **🧠 Mindset**
+
+>🔥 I have learnt devops from internet without spending a single penny. These below points has worked for me pretty fine.
+
+>🔥 I had always interest towards troubleshooting systems, Operating system upgrade/reimage, reading tech vlogs, study and follow people from different socia media platfroms, which helped to be hungry for developing new skills.
+
+> 🔥 DevOps doamin does'nt keep you in a static technology stack,which I think is the best for your carrier growth.
+
+> 🔥 Learn something daily in the area of interest so that you can compund that knowledge over time.
+
+> 🔥 Start as a zero and learn still you are able to master it.
+
+> 🔥 Be hungry to learn, make your self a learner for life.
+
+> 🔥 Take part in open-souce conferences.
+
+## **📜 Defination of DevOps**
+
+> **💡Note**
+>
+> DevOps is a set of practices that combines software development and IT operations. It aims to shorten the systems development life cycle and provide continuous delivery with high software quality.
+
+- DevOps is complementary with Agile software development.
+- Several DevOps aspects came from the **Agile methodology.**
+
+## **🌵 Branches**
+
+DevOps can be divided into two different more niche domain. And the sub-domains under devops require interest over network, hacking and securiy. 
+
+- **DevOpsSec**, i.e. DevOps With Security
+- **OpsSec**,   i.e. Oprations Security
+
+Please do your own reseach for these subdomains, if you find any of them interesting.
+
+
+## **⚗️ Prerequisite**
+
+All the mentioned list item requires basic overall knowledge
+
+1. Software Developement Life Cycle
+2. Operating System
+3. Linux Administration
+4. Networking
+5. Programming Language : C++/Java
+6. Scripting Language : Python/ Shell Scripting / Windows Batch Scripting
+7. Servers, VMs, WSL (Windows Subsystem Linux)
+8. Basics of System Design. i.e. how to scale a application from sractch.
+9. Version Control System (Git/Github, SVN )
+10. Building a code base, build tools, IDE, IaaS, IaaC
+11. Automation
+12. Cloud (GCP/ AWS/ Azure), PaaS
+13. DataBase (SQL, NoSQL)
+
+## **🎒 Oppportunities And Salary**
+
+- One thing to keep in mind, that experienced DevOps engineers are getting their cloud certification as the world is moving towards cloud. So if you want to be in a better positon, my suggestion will be to have some cloud knowledge to land in a better job.
+- Let's hear from people, who are actually done the transition to devops and happliy working on the domain:
+
+
+    [![Salary And Compensation for DevOps By Kunal Kushwaha](https://img.youtube.com/vi/r40DtAzZvcY/mqdefault.jpg)](https://www.youtube.com/watch?v=r40DtAzZvcY)
+    [![QA to DevOps](https://img.youtube.com/vi/thLVD5vtJKE/mqdefault.jpg)](https://www.youtube.com/watch?v=thLVD5vtJKE)
+    [![Highly Paid Domain](https://img.youtube.com/vi/ybAY-q4-d9Q/mqdefault.jpg)](https://www.youtube.com/watch?v=ybAY-q4-d9Q)
+    [![DevOps International Opportunities](https://img.youtube.com/vi/bTMVj6DPdnY/mqdefault.jpg)](https://www.youtube.com/watch?v=bTMVj6DPdnY)
+    [![DevOps International Opportunities](https://img.youtube.com/vi/xcxrp5sEBtI/mqdefault.jpg)](https://www.youtube.com/watch?v=xcxrp5sEBtI)
+
+
+## **👨‍💻 Resouces To Study And Learn**
+
+Most of the resources are free. But there is in anthing paid found from the links, please do a market reseach before spending a single penny.
+
+
+### **✨ Videos To Start Growing Your Interest**
+        
+#### *What is Devops ?*
+
+| `Videos` |
+|:-- |
+|[![Introduction To DevOps By SimpliLearn](https://img.youtube.com/vi/Xrgk023l4lI/mqdefault.jpg)](https://www.youtube.com/watch?v=Xrgk023l4lI)|
+|[![Introduction To DevOps by Hitesh](https://img.youtube.com/vi/_Gpe1Zn-1fE/mqdefault.jpg)](https://www.youtube.com/watch?v=_Gpe1Zn-1fE)|
+|[![Introduction To DevOps by SimpliLearn](https://img.youtube.com/vi/Me3ea4nUt0U/mqdefault.jpg)](https://www.youtube.com/watch?v=Me3ea4nUt0U)|
+
+#### *What is DevOpsSec ?*
+        
+| `Title` | `Video` |
+|:--|:--| 
+| Introduction To DevSecOps | [![Introduction To DevSecOps](https://img.youtube.com/vi/nrhxNNH5lt0/mqdefault.jpg)](https://www.youtube.com/watch?v=nrhxNNH5lt0) |
+| Define DevSecOPs | [![Introduction To DevSecOps](https://img.youtube.com/vi/iaafAnFX_0E/mqdefault.jpg)](https://www.youtube.com/watch?v=iaafAnFX_0E) |
+
+#### *What is OpsSec ?*
+
+| `Title` | `Video` |
+|:--|:--|
+| Introduction To OpsSec | [![Introduction To DevSecOps](https://img.youtube.com/vi/X59NFibpQu4/mqdefault.jpg)](https://www.youtube.com/watch?v=X59NFibpQu4) |
+| OpsSec in 1 Minute | [![Introduction To DevSecOps](https://img.youtube.com/vi/jp2o-56SzdM/mqdefault.jpg)](https://www.youtube.com/watch?v=jp2o-56SzdM) |
+
+### **YouTube Channels**
+
+- *Learning Channels*
+    - [Edureka!](https://www.youtube.com/c/edurekaIN)
+    - [SimpliLearn](https://www.youtube.com/c/SimplilearnOfficial)
+    - [DevOps Journey](https://www.youtube.com/channel/UC4Snw5yrSDMXys31I18U3gg)
+    - [FreeCodeCamp.Org](https://www.youtube.com/c/Freecodecamp)
+    - [Abhishek Viremalla](https://www.youtube.com/AbhishekVeeramalla)
+    - [Kunal Kushwaha](https://www.youtube.com/KunalKushwaha)
+    - [TechWorld With NaNa](https://www.youtube.com/TechWorldwithNana)
+
+- *DevOps Individual as YouTube Vloger*
+    - [Kunal Kushwaha](https://www.youtube.com/c/KunalKushwaha)
+    - [DevOps Directive](https://www.youtube.com/channel/UC4MdpjzjPuop_qWNAvR23JA)
+    - [TechWorldwithNana](https://www.youtube.com/c/TechWorldwithNana)
+
+- *RoadMap Video*
+    - [DevOps Roadmap 2022](https://www.youtube.com/watch?v=9pZ2xmsSDdo)
+    - [DevOps 0 to 100 Complete Guidance](https://www.youtube.com/watch?v=dhJR0YUM3Dg)
+
+- *Archive*
+    - [GFG](https://www.geeksforgeeks.org/tag/devops/)
+
+
+### **🎓 BootCamps**
+
+- [ 🔥DevOps BootCamp by **Kunal Kushwaha**](https://www.youtube.com/playlist?list=PL9gnSGHSqcnoqBXdMwUTRod4Gi3eac2Ak)
+- [ 🔥DevOps Zero to Hero by **Abhishek Viramalla**](https://youtube.com/playlist?list=PLdpzxOOAlwvIKMhk8WhzN1pYoJ1YU8Csa&si=lgC2FaV_uqCgSBtu)
+- [ 🔥 Full 11 Hours DevOps Tutorial by **Edureka!** ](https://www.youtube.com/watch?v=S_0q75eD8Yc)
+- [ 🔥 DevOps Tutorial For Beginners by **Simplilearn** ](https://youtube.com/playlist?list=PLEiEAq2VkUUJS6zkGgXeWw9l32EwRoYdR)
+- [ 🔥 DevOps Engineering Course for Beginners by **FreeCodeCamp.Org** ](https://www.youtube.com/watch?v=j5Zsa_eOXeY)
+
+### **Github Repos**
+
+- [90 Days Of DevOps by Michael Cade](https://github.com/MichaelCade/90DaysOfDevOps)
+- [DevOps Guide by Tikam2](https://github.com/Tikam02/DevOps-Guide)
+
+### **List Of Skills & Tools for DevOps Industry**
+
+[![Introduction To DevSecOps](https://img.youtube.com/vi/1pPHdvrUunY/mqdefault.jpg)](https://www.youtube.com/watch?v=1pPHdvrUunY)
+
+### **Communities**
+
+- [Community Classrooms](https://www.commclassroom.org/home)
+- [Discord DevOps Community Servers](https://disboard.org/servers/tag/devops)
+- [DevOps Community in Reddit](https://www.reddit.com/r/devops/)
+
+### **Techniques For Interview And Jobs**
+
+1. *Tips & Strategy*
+     
+    | `Title` | `Video` |
+    | :-- | :-- |
+    | FIVE things to Crack DevOps Interview | [![FIVE things to Crack DevOps Interview](https://img.youtube.com/vi/qUu7FzRo7p4/mqdefault.jpg)](https://www.youtube.com/watch?v=qUu7FzRo7p4) |
+    | How do I prepare for Cloud or DevOps Interviews?  | [![How do I prepare for Cloud or DevOps Interviews?](https://img.youtube.com/vi/JYAA2G-muZY/mqdefault.jpg)](https://www.youtube.com/watch?v=JYAA2G-muZY) |
+    | Devops Interview Questions by Simplilearn  | [![Devops Interview Questions by Simplilearn](https://img.youtube.com/vi/WxjJlYFIWtI/mqdefault.jpg)](https://www.youtube.com/watch?v=WxjJlYFIWtI) |
+    | DevOps Interview Questions by Edureka | [![DevOps Interview Questions by Edureka](https://img.youtube.com/vi/clZgb8GA6xI/mqdefault.jpg)](https://www.youtube.com/watch?v=clZgb8GA6xI) |
+    | DevOps Interview Questions by Intellipaat | [![DevOps Interview Questions by Intellipaat](https://img.youtube.com/vi/oG8I8kds8rI/mqdefault.jpg)](https://www.youtube.com/watch?v=oG8I8kds8rI) |
+
+2. *Interview Question Dumps*
+
+    - [Interviewbit DevOps Interview Questions](https://www.interviewbit.com/devops-interview-questions/)
+    - [Edureka! DevOps Interview Questions](https://www.edureka.co/blog/interview-questions/top-devops-interview-questions-2016/)
+
+
+### **Websites To Apply For Jobs** 
+
+1. Remote
+    - [Arc()](https://arc.dev/)
+    - [Turing.com](https://www.turing.com)
+    - [AngleList](https://angel.co/)
+    - [Remote](https://remote.com/)
+    - [We Work Remotely](https://weworkremotely.com/)
+    - [Twitter](https://twitter.com)
+    - [Reddit](https://www.reddit.com/r/devopsjobs/)
+2. Physical Jobs
+    - LinkedIn
+    - Referals
+    - Off Campus Hiring
+    - Naurki
+
+### **Use These Tools To Maximize Of Getting Selected :**
+
+1. *Resume ATS Tool*
+    - This tool is a exactly what companies use to filter out potential candidates from huge pile of application : [ResumeWorded.com](https://resumeworded.com/)
+2. Crome Extension
+    - AI enabled Job applying tool : [Jobseer.ai](https://jobseer.ai/)
+3. *Resume Creating Websites*
+    - Google Docs
+    - LinkedIn By default create a resume based on what you have written on your linkedin profile.
+    - [Overleaf](https://www.overleaf.com/)
+    - [FlowCV.io](https://flowcv.io/)
+4. **Check Salary Range Of Any Job of Any Company, Check :** [AmbitionBox](https://www.ambitionbox.com)
+
+
+### **FAQs**
+
+1. What is DevOps, DevOpsSec, OpsSec? 
+2. What are thre prerequisites for getting into devops? 
+3. What is the growth into devops ? And salary into DevOps ? 
+4. What are the resources to learn devops ? 
+5. How to apply for a devops engineer remote and physical jobs? 
+6. How is the community of DevOps ? 
+
+
+
+
diff --git a/TuxTechBlogs/docs/topic/9.0. ITSM/00. Introduction.md b/TuxTechBlogs/docs/topic/9.0. ITSM/00. Introduction.md
index def37f9..e6a5c5c 100644
--- a/TuxTechBlogs/docs/topic/9.0. ITSM/00. Introduction.md	
+++ b/TuxTechBlogs/docs/topic/9.0. ITSM/00. Introduction.md	
@@ -1,32 +1,32 @@
-<center><img src="https://i.postimg.cc/0Qtbzcmz/ITSM-asset.png"></img></center>
-
----
-- [**Introduction**](#introduction)
-- [**What is IT Service Management (ITSM)?**](#what-is-it-service-management-itsm)
-- [**What specifically are these 'IT services' that IT teams manage?**](#what-specifically-are-these-it-services-that-it-teams-manage)
-
----
-
-## **Introduction**
-
-1. ITSM is  how IT teams manage the end-to-end delivery of IT services to their customers.
-2. It includes all the processes and activities to design, create, deliver, and support IT services.
-3. The core concept of ITSM is the belief that IT should be delivered as a service.
-4. A typical ITSM scenario could involve asking for new hardware like a laptop. You would submit your request through a portal, filling out a ticket with all relevant information, and kicking off a repeatable workflow. Then, the ticket would land in the IT team’s queue, where incoming requests are sorted and addressed according to importance.
-
----
-
-## **What is IT Service Management (ITSM)?**
-
-People often misconstrue ITSM as basic IT support. On the contrary, ITSM teams oversee all kinds of workplace technologies, ranging from laptops to servers to business-critical software applications and Cloud services.
-
----
-
-## **What specifically are these 'IT services' that IT teams manage?**
-
-Think about a service as something that IT provides and supports for the business. It can be either external or internal facing.
-
-1. _External examples_: Online banking, food delivery or streaming services.
-2. _Internal examples:_ A billing system, HR system, or cloud infrastructure.
-
+<center><img src="https://i.postimg.cc/0Qtbzcmz/ITSM-asset.png"></img></center>
+
+---
+- [**Introduction**](#introduction)
+- [**What is IT Service Management (ITSM)?**](#what-is-it-service-management-itsm)
+- [**What specifically are these 'IT services' that IT teams manage?**](#what-specifically-are-these-it-services-that-it-teams-manage)
+
+---
+
+## **Introduction**
+
+1. ITSM is  how IT teams manage the end-to-end delivery of IT services to their customers.
+2. It includes all the processes and activities to design, create, deliver, and support IT services.
+3. The core concept of ITSM is the belief that IT should be delivered as a service.
+4. A typical ITSM scenario could involve asking for new hardware like a laptop. You would submit your request through a portal, filling out a ticket with all relevant information, and kicking off a repeatable workflow. Then, the ticket would land in the IT team’s queue, where incoming requests are sorted and addressed according to importance.
+
+---
+
+## **What is IT Service Management (ITSM)?**
+
+People often misconstrue ITSM as basic IT support. On the contrary, ITSM teams oversee all kinds of workplace technologies, ranging from laptops to servers to business-critical software applications and Cloud services.
+
+---
+
+## **What specifically are these 'IT services' that IT teams manage?**
+
+Think about a service as something that IT provides and supports for the business. It can be either external or internal facing.
+
+1. _External examples_: Online banking, food delivery or streaming services.
+2. _Internal examples:_ A billing system, HR system, or cloud infrastructure.
+
 It can change based on how the business works, and how IT is structured within that organizations.
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/9.0. ITSM/01. Key Terms.md b/TuxTechBlogs/docs/topic/9.0. ITSM/01. Key Terms.md
index 6424a57..989a085 100644
--- a/TuxTechBlogs/docs/topic/9.0. ITSM/01. Key Terms.md	
+++ b/TuxTechBlogs/docs/topic/9.0. ITSM/01. Key Terms.md	
@@ -1,31 +1,31 @@
-- [**Key ITSM Terms**](#key-itsm-terms)
-- [**Industry Terms**](#industry-terms)
-- [**ITSM Terms**](#itsm-terms)
-
----
-
-## **Key ITSM Terms**
-
-You’ll come across a host of terms related to ITIL, ITSM, DevOps, and Digital Transformation. You'll need to have a working understanding of the terms below as you progress through this training.
-
----
-
-## **Industry Terms**
-| **Industry Terms** | **Definition** |
-| ---- | :----|
-| `Digital Transformation`  |**Digital Transformation** is the use of new, fast and frequently changing digital technology to solve problems. One of the examples of digital transformation is cloud computing. It reduces reliance on user owned hardware and increases reliance on subscription-based cloud services.|
-| `DevOPs` | **DevOps** emphasizes accelerated IT service delivery enabled by agile and lean practices. DevOps improves collaboration between development and IT operations teams, so organizations can build, test, and release software faster and more reliably. The promised benefits include increased trust, faster software releases, an ability to solve critical issues quickly, and better management of unplanned work.|
-| <ol><li>`Lean`</li><li>`SAFe`</li><li>`Agile`</li><li>`Scrum`</li></ol>    | <ol><li>**Lean IT** involves a methodology of value-stream mapping — diagramming and analyzing services (value streams) into their component process steps and eliminating any steps (or even entire value streams) that do not deliver value.</li><li>The **Scaled Agile Framework (SAFe)**, methodology is an agile framework for development teams built on three pillars: Team, Program, and Portfolio. It is designed not so much as a single methodology, but as a broad knowledge base of proven best practices that real teams have used to deliver successful software products.</li><li>**Agile methodology** is a practice that promotes continuous iteration of development and testing throughout the software development lifecycle of the project. Both development and testing activities are concurrent unlike the Waterfall model. Agile software development emphasizes on four core values.</li><li>**Scrum** is an agile process framework for managing complex knowledge work, with an initial emphasis on software development, although it has been used in other fields and is slowly starting to be explored for other complex work, research and advanced technologies.</li></ol> |
-| <ol><li>`AWS`</li><li>`Microsoft Azure`</li><li>`Google Cloud Platform`</li></ol>|<ol><li>**Amazon Web Services (AWS)** is a subsidiary of Amazon that provides on-demand cloud computing platforms and APIs to individuals, companies, and governments, on a metered pay-as-you-go basis.</li><li>**Microsoft Azure** is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through Microsoft-managed data centers.</li><li>**Google Cloud Platform**, offered by Google, is a suite of cloud computing services that runs on the same infrastructure that Google uses internally for its end-user products, such as Google Search, Gmail and YouTube</li></ol>|
-| `I&O ( Infrastructure & Operations )`| **Infrastructure and Operations (1&0)** manages the ITS data centers and provides around-the-clock support for ITS business computing activities. |
-
----
-
-## **ITSM Terms**
-| **ITSM Terms** | **Definition** |
-| :----: | :---- |
-|<ol><li>`Service Request`</li><li>`Incident Management`</li><li>`Problem Management`</li><li>`Knowledge and Asset Management`</li><li>`Change Enablement ( Formerly known as Change Management )`</li><li>`Configuration and Database Management ( CMDB )`</li></ol>| <ol><li>**Service Request Management** is a repeatable procedure for handling the wide variety of customer service requests, like requests for access to applications, software enhancements, and hardware updates. The service request workstream often involves recurring requests and benefits greatly from enabling customers with knowledge and automating certain tasks.</li><li>**Incident Management** is the practice of managing unplanned events that disrupt or reduce the quality of a service. It requires an emergency response from the IT team.</li><li>**Problem Management** is the practice of identifying and managing the causes of incidents on an IT service. It is a core component of ITSM frameworks.</li><li>**Knowledge Management** is the practice of creating, curating, sharing, using, and managing knowledge across an organization and even across industries. **IT Asset Management (also known as ITAM)** is the process of ensuring an organization’s assets are accounted for, deployed, maintained, upgraded, and disposed of when the time comes. Put simply, it’s making sure that the valuable items, tangible and intangible, in your organization are tracked and being used.</li><li>**Change Enablement** is an IT practice designed to minimize disruptions to IT services while making changes to critical systems and services. A change is adding, modifying, or removing anything that could have a direct or indirect effect on services.</li><li>According to ITIL 4, a **configuration management database (CMDB)** “is used to store configuration records throughout their lifecycle and maintain the relationships between them. In other words, your CMDB stores information on the configuration of items within an organization, including hardware, software, systems, facilities, and sometimes personnel. It is the purview of the IT organization to define which items should be tracked and how to do so. This configuration data can include relationships and interdependencies between items, the history of changes to each item, and class and attributes—such as type, owner, and importance—for each item.</li></ol>|
-| <ol><li>`Self-Service`</li><li>`Shift-left`</li></ol> | <ol><li>As users come to depend on self-service applications to find answers or ask for help in their daily lives, these expectations for self-service are now being applied to IT organizations. Self-service isn't a new concept, either. We see it in our everyday lives, from self-checkout lines to using an ATM. And now, finding answers is easier than ever with the power of search engines.</li><li>The ability to **"shift-left"** and deliver quality self-service is a top priority for many IT organizations today. Increasing support consist Level Three, Two, One, Zero Support. Shift left (lower cost & improved user satisfaction)</li></ol> |
-|`Always-On-Service`| A Service which is consumed/ available to consumers to be consumed anytime 24X7, 365 days. |
-| <ol><li>`ITIL`</li><li>`ITIL4`</li></ol>| <ol><li>**ITIL** is the most widely accepted approach to ITSM. ITIL focuses on practices for aligning IT services with business needs. ITIL can help organizations adapt to ongoing transformation and scale.</li><li>**ITIL4**, the recent update to ITIL standards, represents a paradigm shift for IT tears. It guides teams to a holistic, business and customer-value frame of reference, and encourages a more flexible approach based on how your team works. The ITIL 4 Guiding Principles promote collaboration, simplicity, and feedback.
+- [**Key ITSM Terms**](#key-itsm-terms)
+- [**Industry Terms**](#industry-terms)
+- [**ITSM Terms**](#itsm-terms)
+
+---
+
+## **Key ITSM Terms**
+
+You’ll come across a host of terms related to ITIL, ITSM, DevOps, and Digital Transformation. You'll need to have a working understanding of the terms below as you progress through this training.
+
+---
+
+## **Industry Terms**
+| **Industry Terms** | **Definition** |
+| ---- | :----|
+| `Digital Transformation`  |**Digital Transformation** is the use of new, fast and frequently changing digital technology to solve problems. One of the examples of digital transformation is cloud computing. It reduces reliance on user owned hardware and increases reliance on subscription-based cloud services.|
+| `DevOPs` | **DevOps** emphasizes accelerated IT service delivery enabled by agile and lean practices. DevOps improves collaboration between development and IT operations teams, so organizations can build, test, and release software faster and more reliably. The promised benefits include increased trust, faster software releases, an ability to solve critical issues quickly, and better management of unplanned work.|
+| <ol><li>`Lean`</li><li>`SAFe`</li><li>`Agile`</li><li>`Scrum`</li></ol>    | <ol><li>**Lean IT** involves a methodology of value-stream mapping — diagramming and analyzing services (value streams) into their component process steps and eliminating any steps (or even entire value streams) that do not deliver value.</li><li>The **Scaled Agile Framework (SAFe)**, methodology is an agile framework for development teams built on three pillars: Team, Program, and Portfolio. It is designed not so much as a single methodology, but as a broad knowledge base of proven best practices that real teams have used to deliver successful software products.</li><li>**Agile methodology** is a practice that promotes continuous iteration of development and testing throughout the software development lifecycle of the project. Both development and testing activities are concurrent unlike the Waterfall model. Agile software development emphasizes on four core values.</li><li>**Scrum** is an agile process framework for managing complex knowledge work, with an initial emphasis on software development, although it has been used in other fields and is slowly starting to be explored for other complex work, research and advanced technologies.</li></ol> |
+| <ol><li>`AWS`</li><li>`Microsoft Azure`</li><li>`Google Cloud Platform`</li></ol>|<ol><li>**Amazon Web Services (AWS)** is a subsidiary of Amazon that provides on-demand cloud computing platforms and APIs to individuals, companies, and governments, on a metered pay-as-you-go basis.</li><li>**Microsoft Azure** is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through Microsoft-managed data centers.</li><li>**Google Cloud Platform**, offered by Google, is a suite of cloud computing services that runs on the same infrastructure that Google uses internally for its end-user products, such as Google Search, Gmail and YouTube</li></ol>|
+| `I&O ( Infrastructure & Operations )`| **Infrastructure and Operations (1&0)** manages the ITS data centers and provides around-the-clock support for ITS business computing activities. |
+
+---
+
+## **ITSM Terms**
+| **ITSM Terms** | **Definition** |
+| :----: | :---- |
+|<ol><li>`Service Request`</li><li>`Incident Management`</li><li>`Problem Management`</li><li>`Knowledge and Asset Management`</li><li>`Change Enablement ( Formerly known as Change Management )`</li><li>`Configuration and Database Management ( CMDB )`</li></ol>| <ol><li>**Service Request Management** is a repeatable procedure for handling the wide variety of customer service requests, like requests for access to applications, software enhancements, and hardware updates. The service request workstream often involves recurring requests and benefits greatly from enabling customers with knowledge and automating certain tasks.</li><li>**Incident Management** is the practice of managing unplanned events that disrupt or reduce the quality of a service. It requires an emergency response from the IT team.</li><li>**Problem Management** is the practice of identifying and managing the causes of incidents on an IT service. It is a core component of ITSM frameworks.</li><li>**Knowledge Management** is the practice of creating, curating, sharing, using, and managing knowledge across an organization and even across industries. **IT Asset Management (also known as ITAM)** is the process of ensuring an organization’s assets are accounted for, deployed, maintained, upgraded, and disposed of when the time comes. Put simply, it’s making sure that the valuable items, tangible and intangible, in your organization are tracked and being used.</li><li>**Change Enablement** is an IT practice designed to minimize disruptions to IT services while making changes to critical systems and services. A change is adding, modifying, or removing anything that could have a direct or indirect effect on services.</li><li>According to ITIL 4, a **configuration management database (CMDB)** “is used to store configuration records throughout their lifecycle and maintain the relationships between them. In other words, your CMDB stores information on the configuration of items within an organization, including hardware, software, systems, facilities, and sometimes personnel. It is the purview of the IT organization to define which items should be tracked and how to do so. This configuration data can include relationships and interdependencies between items, the history of changes to each item, and class and attributes—such as type, owner, and importance—for each item.</li></ol>|
+| <ol><li>`Self-Service`</li><li>`Shift-left`</li></ol> | <ol><li>As users come to depend on self-service applications to find answers or ask for help in their daily lives, these expectations for self-service are now being applied to IT organizations. Self-service isn't a new concept, either. We see it in our everyday lives, from self-checkout lines to using an ATM. And now, finding answers is easier than ever with the power of search engines.</li><li>The ability to **"shift-left"** and deliver quality self-service is a top priority for many IT organizations today. Increasing support consist Level Three, Two, One, Zero Support. Shift left (lower cost & improved user satisfaction)</li></ol> |
+|`Always-On-Service`| A Service which is consumed/ available to consumers to be consumed anytime 24X7, 365 days. |
+| <ol><li>`ITIL`</li><li>`ITIL4`</li></ol>| <ol><li>**ITIL** is the most widely accepted approach to ITSM. ITIL focuses on practices for aligning IT services with business needs. ITIL can help organizations adapt to ongoing transformation and scale.</li><li>**ITIL4**, the recent update to ITIL standards, represents a paradigm shift for IT tears. It guides teams to a holistic, business and customer-value frame of reference, and encourages a more flexible approach based on how your team works. The ITIL 4 Guiding Principles promote collaboration, simplicity, and feedback.
 </li></ol>
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/9.0. ITSM/02. ITSM Library and Practices.md b/TuxTechBlogs/docs/topic/9.0. ITSM/02. ITSM Library and Practices.md
index ef67f10..ca442a9 100644
--- a/TuxTechBlogs/docs/topic/9.0. ITSM/02. ITSM Library and Practices.md	
+++ b/TuxTechBlogs/docs/topic/9.0. ITSM/02. ITSM Library and Practices.md	
@@ -1,42 +1,42 @@
-
-- [ITSM Library and Best Practices](#itsm-library-and-best-practices)
-  - [**ITIL \& ITSM**](#itil--itsm)
-  - [**How do ITIL and ITSM differ?**](#how-do-itil-and-itsm-differ)
-  - [**Read More About ITIL \& ITIL4**](#read-more-about-itil--itil4)
-
-# ITSM Library and Best Practices
-
-## **ITIL & ITSM**
-
-> **ITIL** is the acronym for *Information Technology Infrastructure Library*.
-
-A framework that helps IT teams organize and think about their workflows, ITIL is a widely accepted 'best standard' for how IT teams can aligning IT services with the needs of the business.
-
-The 'service area' categories we just introduced, like Asset Management or Service Request Management are terms that have been standardized in the industry by ITIL.
-
-## **How do ITIL and ITSM differ?**
-
-|`ITIL`|`ITSM`|
-|:----| :----|
-|ITIL provides practical and proven guidance for establishing a service management system. It provides the framework, practices, and a common glossary of terms for businesses using IT enabled services.|ITSM deals with implementing, managing, and delivering IT services to meet the needs of an organization. It ensures that the appropriate combination of people, practices, processes, and products (tools and technology) are in place to provide value.|
-
-> ## **Note**
-
-1. ITSM is the practice of delivering IT services to customers, while ITIL is the framework that can be used to implement ITSM.
-2. Many IT frameworks are only focused on specific areas like security, quality control, or service management.
-3. ITIL guides organizations and individuals on using IT as a tool to facilitate business change, transformation and growth. ITIL advocates that IT and digital services are aligned to the needs of the business and support its core objectives and goals.
-4. ITIL is an evolving framework. In previous versions, ITIL was interpreted by some practitioners as being overly-prescriptive with heavy and burdensome requirements associated with old ways of working.
-5. The latest version, ITIL 4 presents a more holistic, customer-centric frame of reference, and encourages a more flexible approach to building an effective IT organization.
-
-> ## Highlights of ITIL 4 that align with Atlassian
-
-1. Centers on `“Focus on value”` as a core principle for IT teams.
-2. Provides a `flexible and value-centric` approach.
-3. Guiding principles embrace `collaboration, simplicity, and iteration`.
-4. Shifts from processes to `practices`.
-5. Integrates best practices from `Agile`, `DevOps`, and `Lean`.
-
-## **Read More About ITIL & ITIL4**
-
-1. [ITIL 4 whitepaper](https://pages.eml.atlassian.com/rs/594-ATC-127/images/Atlassian_Axelos_ITIL4_Guide.pdf)
+
+- [ITSM Library and Best Practices](#itsm-library-and-best-practices)
+  - [**ITIL \& ITSM**](#itil--itsm)
+  - [**How do ITIL and ITSM differ?**](#how-do-itil-and-itsm-differ)
+  - [**Read More About ITIL \& ITIL4**](#read-more-about-itil--itil4)
+
+# ITSM Library and Best Practices
+
+## **ITIL & ITSM**
+
+> **ITIL** is the acronym for *Information Technology Infrastructure Library*.
+
+A framework that helps IT teams organize and think about their workflows, ITIL is a widely accepted 'best standard' for how IT teams can aligning IT services with the needs of the business.
+
+The 'service area' categories we just introduced, like Asset Management or Service Request Management are terms that have been standardized in the industry by ITIL.
+
+## **How do ITIL and ITSM differ?**
+
+|`ITIL`|`ITSM`|
+|:----| :----|
+|ITIL provides practical and proven guidance for establishing a service management system. It provides the framework, practices, and a common glossary of terms for businesses using IT enabled services.|ITSM deals with implementing, managing, and delivering IT services to meet the needs of an organization. It ensures that the appropriate combination of people, practices, processes, and products (tools and technology) are in place to provide value.|
+
+> ## **Note**
+
+1. ITSM is the practice of delivering IT services to customers, while ITIL is the framework that can be used to implement ITSM.
+2. Many IT frameworks are only focused on specific areas like security, quality control, or service management.
+3. ITIL guides organizations and individuals on using IT as a tool to facilitate business change, transformation and growth. ITIL advocates that IT and digital services are aligned to the needs of the business and support its core objectives and goals.
+4. ITIL is an evolving framework. In previous versions, ITIL was interpreted by some practitioners as being overly-prescriptive with heavy and burdensome requirements associated with old ways of working.
+5. The latest version, ITIL 4 presents a more holistic, customer-centric frame of reference, and encourages a more flexible approach to building an effective IT organization.
+
+> ## Highlights of ITIL 4 that align with Atlassian
+
+1. Centers on `“Focus on value”` as a core principle for IT teams.
+2. Provides a `flexible and value-centric` approach.
+3. Guiding principles embrace `collaboration, simplicity, and iteration`.
+4. Shifts from processes to `practices`.
+5. Integrates best practices from `Agile`, `DevOps`, and `Lean`.
+
+## **Read More About ITIL & ITIL4**
+
+1. [ITIL 4 whitepaper](https://pages.eml.atlassian.com/rs/594-ATC-127/images/Atlassian_Axelos_ITIL4_Guide.pdf)
 2. [What ITIL 4 means for you and your team](https://www.atlassian.com/blog/technology/what-the-new-itil-4-means-for-you-and-your-team)
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/9.0. ITSM/03. Core ITSM Practices.md b/TuxTechBlogs/docs/topic/9.0. ITSM/03. Core ITSM Practices.md
index 395274e..4fc02f0 100644
--- a/TuxTechBlogs/docs/topic/9.0. ITSM/03. Core ITSM Practices.md	
+++ b/TuxTechBlogs/docs/topic/9.0. ITSM/03. Core ITSM Practices.md	
@@ -1,52 +1,52 @@
-- [**Core ITSM practices**](#core-itsm-practices)
-- [**How do these IT teams manage their services?**](#how-do-these-it-teams-manage-their-services)
-- [**Examples**](#examples)
-
----
-
-## **Core ITSM practices**
-
-1. IT practices have to be standardized and managed effectively.
-2. For example, if a phone application functions as a storefront for a business and is crashing for Android users, that adds up to potentially thousands in missed sales for each minute the app is down.
-3. Without a standardized 'practice' for incident management, the team won't have an effective workflow to push a resolution.
-4. ITSM solutions help streamline these practices, helping teams work more effectively, and ultimately deliver greater dollar value to a business.
-
----
-
-## **How do these IT teams manage their services?**
-
-1. Great question. IT teams use a variety of frameworks or methodologies to name and organize the practices that manage their services.
-2. A common framework is  ITIL, which provides teams with 'practices' they can implement to deliver great service.
-
----
-
-> _Remember those ITIL practices mentioned at the beginning of the course?_
-
-1. Modern IT service teams use organizational resources and follow repeatable procedures to deliver services across various areas. The repeatable procedures are referred to in ITIL as **practices**.
-
-2. ITSM software solutions enable the implementation of these “practices."
-
----
-
-> **There are 34 practices in total, but here are the core practices that most organizations implement, and which Atlassian focuses on in our products to deliver IT services.**
-
-## **Examples**
-
-1. `Service Request Management` : Resolving a customer's service request and managing the lifecycle of all service requests.
-   - _Example:_ Newly joined Employee needs to access VPN.
-2. `Incident Management` : Resolving any kind of disruption of IT function - from issues with credit card readers to web page outages.
-   - _Example:_ IT Apps are crashing after new update was rolled out in morning. Need to Fix this asap, affecting multiple users/ team.
-3. `Problem Management` : Investigating the root cause of multiple incidents, to prevent the problem from happening again.
-   - _Example:_ Looks like crash reports are happening only only on the android devices. What can be done to improve app compatibility with android platform.
-4. `Change Enablement` : Ensuring that if IT practices need to change (migrating to a cloud based software solution for example) there are minimal disruptions to regularly scheduled business functions and services.
-   - _Example:_ Payroll database finance department is using is out-of-date completely. Now finance team needs to migrate the DB to a cloud based application if the business is keep on scaling as per current rate. Finance team is looking for advise and help to migrate to cloud based solution.
-5. `IT Asset Management` : Keeping track of all IT related assets (hardware, software, devices and subscriptions) and managing the lifecycle of those assets from procurement to disposal.
-   - _Example:_ IT Team has limited supply of the latest MacBook Pros, so they want to make sure the team that need the horsepower and whose laptops are about to go out of date, need to notify them.
-6. `Knowledge Management` : Effective management of information and knowledge like common resolutions to service requests, or instructions on how to set up a new laptop.
-   - _Example:_ A lot of FAQs were piled up on how to download and install latest internal software update. Now the customers are looking for a KB article to follow along and not resolve each query individually, instead use the FAQ KB for that.
-7. `Service Configuration Management` : Capturing the information about different parts of the IT ecosystem - called Configuration Items (CIs)- and how those items relate to one another.
-   - _Example:_ It is very difficult to deploy changes org wide/ in small scale without a map of how everything relates to one another. Thus needs more time to spent on mapping out the relationships between out critical systems and hardware so we can be more effective in the future.
-
----
-
+- [**Core ITSM practices**](#core-itsm-practices)
+- [**How do these IT teams manage their services?**](#how-do-these-it-teams-manage-their-services)
+- [**Examples**](#examples)
+
+---
+
+## **Core ITSM practices**
+
+1. IT practices have to be standardized and managed effectively.
+2. For example, if a phone application functions as a storefront for a business and is crashing for Android users, that adds up to potentially thousands in missed sales for each minute the app is down.
+3. Without a standardized 'practice' for incident management, the team won't have an effective workflow to push a resolution.
+4. ITSM solutions help streamline these practices, helping teams work more effectively, and ultimately deliver greater dollar value to a business.
+
+---
+
+## **How do these IT teams manage their services?**
+
+1. Great question. IT teams use a variety of frameworks or methodologies to name and organize the practices that manage their services.
+2. A common framework is  ITIL, which provides teams with 'practices' they can implement to deliver great service.
+
+---
+
+> _Remember those ITIL practices mentioned at the beginning of the course?_
+
+1. Modern IT service teams use organizational resources and follow repeatable procedures to deliver services across various areas. The repeatable procedures are referred to in ITIL as **practices**.
+
+2. ITSM software solutions enable the implementation of these “practices."
+
+---
+
+> **There are 34 practices in total, but here are the core practices that most organizations implement, and which Atlassian focuses on in our products to deliver IT services.**
+
+## **Examples**
+
+1. `Service Request Management` : Resolving a customer's service request and managing the lifecycle of all service requests.
+   - _Example:_ Newly joined Employee needs to access VPN.
+2. `Incident Management` : Resolving any kind of disruption of IT function - from issues with credit card readers to web page outages.
+   - _Example:_ IT Apps are crashing after new update was rolled out in morning. Need to Fix this asap, affecting multiple users/ team.
+3. `Problem Management` : Investigating the root cause of multiple incidents, to prevent the problem from happening again.
+   - _Example:_ Looks like crash reports are happening only only on the android devices. What can be done to improve app compatibility with android platform.
+4. `Change Enablement` : Ensuring that if IT practices need to change (migrating to a cloud based software solution for example) there are minimal disruptions to regularly scheduled business functions and services.
+   - _Example:_ Payroll database finance department is using is out-of-date completely. Now finance team needs to migrate the DB to a cloud based application if the business is keep on scaling as per current rate. Finance team is looking for advise and help to migrate to cloud based solution.
+5. `IT Asset Management` : Keeping track of all IT related assets (hardware, software, devices and subscriptions) and managing the lifecycle of those assets from procurement to disposal.
+   - _Example:_ IT Team has limited supply of the latest MacBook Pros, so they want to make sure the team that need the horsepower and whose laptops are about to go out of date, need to notify them.
+6. `Knowledge Management` : Effective management of information and knowledge like common resolutions to service requests, or instructions on how to set up a new laptop.
+   - _Example:_ A lot of FAQs were piled up on how to download and install latest internal software update. Now the customers are looking for a KB article to follow along and not resolve each query individually, instead use the FAQ KB for that.
+7. `Service Configuration Management` : Capturing the information about different parts of the IT ecosystem - called Configuration Items (CIs)- and how those items relate to one another.
+   - _Example:_ It is very difficult to deploy changes org wide/ in small scale without a map of how everything relates to one another. Thus needs more time to spent on mapping out the relationships between out critical systems and hardware so we can be more effective in the future.
+
+---
+
 > The practice terms like  **"Service Request Management"** can be both nouns - the name of a service area or team- and a verb and refer to the process of doing service request management.
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/9.0. ITSM/04. Maturity Matters.md b/TuxTechBlogs/docs/topic/9.0. ITSM/04. Maturity Matters.md
index 0d5ad80..6b6d4d1 100644
--- a/TuxTechBlogs/docs/topic/9.0. ITSM/04. Maturity Matters.md	
+++ b/TuxTechBlogs/docs/topic/9.0. ITSM/04. Maturity Matters.md	
@@ -1,16 +1,16 @@
-# Maturity Matters
-
-Not all businesses are ready for the complexity of a global launch. Maturity, training, documented practices, and scale play a huge role in what a team can accomplish. In the same way, not all IT organizations can offer the full breadth of IT Services covered in the previous sections.
-
-> ## **Why does maturity matter?**
-
-The maturity of an IT organization will impact the ITIL practices they're able to implement, and what they'll need from an ITSM solution. Check this diagram for ITSM maturity model:
-
-![ITSM_Maturity_model](https://i.postimg.cc/pdL9Rwhw/ITSM-Maturity-Model.png)
-
-## **ITSM Maturity Model**
-
-- The Gartner IT Maturity Model (image above ⬆️) is a useful tool to assess an IT team's current maturity. The lower maturity teams are typically more chaotic with ad hoc requests and undocumented processes. _Service Request Management_ might be a huge part of their day, but they don't have great processes in place for _Change Enablement_.
-- The more the teams mature, the more process and value-driven they get. They're able to offer _Incident Management_ and _Problem Management_. The team may begin implementing a workflow framework to shape their processes, like ITIL.
-- Every team wants to be on the complex service and value end of the scale. They must work through organizational process or technology challenges to achieve this goal.
+# Maturity Matters
+
+Not all businesses are ready for the complexity of a global launch. Maturity, training, documented practices, and scale play a huge role in what a team can accomplish. In the same way, not all IT organizations can offer the full breadth of IT Services covered in the previous sections.
+
+> ## **Why does maturity matter?**
+
+The maturity of an IT organization will impact the ITIL practices they're able to implement, and what they'll need from an ITSM solution. Check this diagram for ITSM maturity model:
+
+![ITSM_Maturity_model](https://i.postimg.cc/pdL9Rwhw/ITSM-Maturity-Model.png)
+
+## **ITSM Maturity Model**
+
+- The Gartner IT Maturity Model (image above ⬆️) is a useful tool to assess an IT team's current maturity. The lower maturity teams are typically more chaotic with ad hoc requests and undocumented processes. _Service Request Management_ might be a huge part of their day, but they don't have great processes in place for _Change Enablement_.
+- The more the teams mature, the more process and value-driven they get. They're able to offer _Incident Management_ and _Problem Management_. The team may begin implementing a workflow framework to shape their processes, like ITIL.
+- Every team wants to be on the complex service and value end of the scale. They must work through organizational process or technology challenges to achieve this goal.
 - **Effective organizations want IT delivered as a solution based service.**
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/9.0. ITSM/05. The Atlassian ITSM Solution.md b/TuxTechBlogs/docs/topic/9.0. ITSM/05. The Atlassian ITSM Solution.md
index 0d8e045..c8d5b18 100644
--- a/TuxTechBlogs/docs/topic/9.0. ITSM/05. The Atlassian ITSM Solution.md	
+++ b/TuxTechBlogs/docs/topic/9.0. ITSM/05. The Atlassian ITSM Solution.md	
@@ -1,36 +1,36 @@
-- [**The Atlassian ITSM solution**](#the-atlassian-itsm-solution)
-  - [_Unite teams on one platform_](#unite-teams-on-one-platform)
-- [**Atlassian Products**](#atlassian-products)
-- [**Build a strong culture with Atlassian Team Playbook**](#build-a-strong-culture-with-atlassian-team-playbook)
-
----
-
-## **The Atlassian ITSM solution**
-
-### _Unite teams on one platform_
-
-Atlassian provides the technology backbone with the most critical collaborative workflows—agile project planning, incident management and response, and service management and support—to help modern IT organizations plan, build, deliver, and ensure that your services are always on.
-
----
-
-![Atlassian_ITSM_Solution](https://i.postimg.cc/QtVjys9M/ITSM-Atlassian.png)
-
----
-## **Atlassian Products**
-
-| **Use Case** | **Products** | **Details** |
-| :---- | :----| :---- |
-| **High-velocity ITSM** |![jira_service_management](https://i.postimg.cc/RFbZSq5f/jira-service-management.png)|<ol><li>Jira Service Management enables IT teams, across infrastructure, operations, and workplace support, enjoy a team-centric IT support workspace that matches the way they work with flexible ITIL workflows, a self-service portal, agent queues, automation, SLAs, custom dashboards, and much more.</li><li> Outside of IT, the adoption of Jira Service Management spreads quickly to business teams, such as HR, Facilities, and Legal, who recognize the value of easily managing and tracking their flow of work.</li></ol>|
-| **Project and issue tracking** | ![jira_software](https://i.postimg.cc/bJvvfkMp/jira-software.png) | <ol><li>Jira Software is is used by software teams to plan, track, and release great software.</li><li>Use Jira software to create user stories and issues, plan sprints, distribute tasks, and track progress with complete visibility across your software team.</li><li>You can always get up-to-date information and improve team performance based on real-time, visual data that your team can put to use.</li> |
-| **Document collaboration** | ![confluence](https://i.postimg.cc/WbxqmWyr/confluence.png) | <ol><li>Confluence provides the backbone for knowledge management, providing real-time collaboration and access to support articles, troubleshooting guides, runbooks, templates and more.</li></ol>|
-| **Git code management** | ![bitbucket](https://i.postimg.cc/CMPq5LHc/bitbucket.png) | <ol><li>Bitbucket is more than just Git code management. Bitbucket gives teams one place to plan projects, collaborate on code, test, and deploy.</li><li>Strong integrations with Jira Software and Bitbucket brings development and IT teams together using a common platform to speed service requests through to changes and releases.</li></ol>|
-| **Modern incident response** | ![opsginie](https://i.postimg.cc/VkcLL3T7/opsginie.png) | <ol><li>Opsgenie provides powerful incident swarming and on-call alerting capabilities to keep services always on.</li><li>Using Opsgenie teams have modern incident management workflows to proactively respond, resolve, and learn from every incident.</li></ol>|
-| **Incident Communication**| ![statuspage](https://i.postimg.cc/G2bXLhJc/statuspage.png) | Statuspage is the easiest way to communicate incidents and scheduled maintenance to end-users to help reduce support burden and build trust with every incident. There can be possibility that Status page can be used for internal and external incident communications.|
-
----
-
-## **Build a strong culture with Atlassian Team Playbook**
-
-1. The Atlassian Team Playbook provides dozens of plays to strengthen your team’s culture and improve its overall health, from mapping out roles and responsibilities to making more effective decisions.
-2. IT teams, should start moving towards more agile approaches to ITSM that value collaboration, ease of use, and value creation.
+- [**The Atlassian ITSM solution**](#the-atlassian-itsm-solution)
+  - [_Unite teams on one platform_](#unite-teams-on-one-platform)
+- [**Atlassian Products**](#atlassian-products)
+- [**Build a strong culture with Atlassian Team Playbook**](#build-a-strong-culture-with-atlassian-team-playbook)
+
+---
+
+## **The Atlassian ITSM solution**
+
+### _Unite teams on one platform_
+
+Atlassian provides the technology backbone with the most critical collaborative workflows—agile project planning, incident management and response, and service management and support—to help modern IT organizations plan, build, deliver, and ensure that your services are always on.
+
+---
+
+![Atlassian_ITSM_Solution](https://i.postimg.cc/QtVjys9M/ITSM-Atlassian.png)
+
+---
+## **Atlassian Products**
+
+| **Use Case** | **Products** | **Details** |
+| :---- | :----| :---- |
+| **High-velocity ITSM** |![jira_service_management](https://i.postimg.cc/RFbZSq5f/jira-service-management.png)|<ol><li>Jira Service Management enables IT teams, across infrastructure, operations, and workplace support, enjoy a team-centric IT support workspace that matches the way they work with flexible ITIL workflows, a self-service portal, agent queues, automation, SLAs, custom dashboards, and much more.</li><li> Outside of IT, the adoption of Jira Service Management spreads quickly to business teams, such as HR, Facilities, and Legal, who recognize the value of easily managing and tracking their flow of work.</li></ol>|
+| **Project and issue tracking** | ![jira_software](https://i.postimg.cc/bJvvfkMp/jira-software.png) | <ol><li>Jira Software is is used by software teams to plan, track, and release great software.</li><li>Use Jira software to create user stories and issues, plan sprints, distribute tasks, and track progress with complete visibility across your software team.</li><li>You can always get up-to-date information and improve team performance based on real-time, visual data that your team can put to use.</li> |
+| **Document collaboration** | ![confluence](https://i.postimg.cc/WbxqmWyr/confluence.png) | <ol><li>Confluence provides the backbone for knowledge management, providing real-time collaboration and access to support articles, troubleshooting guides, runbooks, templates and more.</li></ol>|
+| **Git code management** | ![bitbucket](https://i.postimg.cc/CMPq5LHc/bitbucket.png) | <ol><li>Bitbucket is more than just Git code management. Bitbucket gives teams one place to plan projects, collaborate on code, test, and deploy.</li><li>Strong integrations with Jira Software and Bitbucket brings development and IT teams together using a common platform to speed service requests through to changes and releases.</li></ol>|
+| **Modern incident response** | ![opsginie](https://i.postimg.cc/VkcLL3T7/opsginie.png) | <ol><li>Opsgenie provides powerful incident swarming and on-call alerting capabilities to keep services always on.</li><li>Using Opsgenie teams have modern incident management workflows to proactively respond, resolve, and learn from every incident.</li></ol>|
+| **Incident Communication**| ![statuspage](https://i.postimg.cc/G2bXLhJc/statuspage.png) | Statuspage is the easiest way to communicate incidents and scheduled maintenance to end-users to help reduce support burden and build trust with every incident. There can be possibility that Status page can be used for internal and external incident communications.|
+
+---
+
+## **Build a strong culture with Atlassian Team Playbook**
+
+1. The Atlassian Team Playbook provides dozens of plays to strengthen your team’s culture and improve its overall health, from mapping out roles and responsibilities to making more effective decisions.
+2. IT teams, should start moving towards more agile approaches to ITSM that value collaboration, ease of use, and value creation.
 3. Checkout [Team Playbook in Atlassian](https://www.atlassian.com/team-playbook).
\ No newline at end of file
diff --git a/TuxTechBlogs/docs/topic/9.0. ITSM/06. Key Takeaways.md b/TuxTechBlogs/docs/topic/9.0. ITSM/06. Key Takeaways.md
index 5828cf9..b59cc32 100644
--- a/TuxTechBlogs/docs/topic/9.0. ITSM/06. Key Takeaways.md	
+++ b/TuxTechBlogs/docs/topic/9.0. ITSM/06. Key Takeaways.md	
@@ -1,11 +1,11 @@
-## **Key takeaways**
-
-1. IT Service Management (ITSM) is how IT teams manage the end-to-end delivery of IT services to customers.
-
-2. Information Technology Infrastructure Library (ITIL) is a set of detailed practices for IT Service Management that focuses on aligning IT services with the needs of the business. It's a framework that can be used to implement ITSM.
-
-3. The core ITSM practices include Request Management, Incident Management, Problem Management, Change Enablement,  Asset Management, Configuration Management, and Knowledge Management.
-
-4. The maturity of an IT organization will impact the ITIL practices they're able to implement, and what they'll need from an ITSM solution.
-
+## **Key takeaways**
+
+1. IT Service Management (ITSM) is how IT teams manage the end-to-end delivery of IT services to customers.
+
+2. Information Technology Infrastructure Library (ITIL) is a set of detailed practices for IT Service Management that focuses on aligning IT services with the needs of the business. It's a framework that can be used to implement ITSM.
+
+3. The core ITSM practices include Request Management, Incident Management, Problem Management, Change Enablement,  Asset Management, Configuration Management, and Knowledge Management.
+
+4. The maturity of an IT organization will impact the ITIL practices they're able to implement, and what they'll need from an ITSM solution.
+
 5. Learn about Atlassian's ITSM solutions.
\ No newline at end of file
diff --git a/TuxTechBlogs/mkdocs.yml b/TuxTechBlogs/mkdocs.yml
index 84ebfd5..79f56ee 100644
--- a/TuxTechBlogs/mkdocs.yml
+++ b/TuxTechBlogs/mkdocs.yml
@@ -1,16 +1,23 @@
 # Project information
-site_name: Blogs.TuxTechLab.com
-site_description: Documenting Everything related to Computers, Internet, Security, Software Engineering
+site_name: TuxTechBlogs
+site_description: Computer Science, Internet, Security, Software Engineering
 site_url: https://blogs.tuxtechlab.com
 site_author: Arindam Tanti
 
 # Repository
 repo_name: TuxTechLab/Blogs
-repo_url: https://github.com/TuxTechLab/Blogs
-edit_uri: 'https://blogs.tuxtechlab.com'
+repo_url: https://github.com/TuxTechLab/Blogs/
+edit_uri: edit/main/TuxTechBlogs/docs/
 
 # Copyright
-copyright: Copyright &copy; <a href="http://github.com/TuxTechLab">TuxTechLab</a> 2024 - 2025
+copyright: >
+  Maintained & Copyright &copy; <a href="http://github.com/TuxTechLab">TuxTechLab</a> 2024 - 2025
+
+# Site Configurations
+use_directory_urls: true
+strict: no
+# Enable dev_addr when working in development environment.
+#dev_addr: 0.0.0.0:{BLOGS_CTR_INTERNAL_PORT}
 
 # Configuration
 theme:
@@ -41,15 +48,34 @@ theme:
       logo: fontawesome/solid/code
       repo: fontawesome/brands/github
     features:
-      - navigation.top
-      - navigation.footer
-      - navigation.expand
-      - navigation.instant
-      - navigation.instant.preview
-      - navigation.instant.progress
-      - search.suggest
-      - search.highlight
-      - content.code.copy
+    - announce.dismiss
+    - content.action.edit
+    - content.action.view
+    - content.code.annotate
+    - content.code.copy
+    - content.code.select
+    - content.footnote.tooltips
+    - content.tabs.link
+    - content.tooltips
+    # - header.autohide
+
+    - navigation.footer
+    - navigation.instant
+    - navigation.instant.prefetch
+    - navigation.instant.progress
+    - navigation.prune
+    - navigation.tabs
+    # - navigation.sections # Read: https://jimandreas.github.io/mkdocs-material/setup/setting-up-navigation/#navigation-tabs
+    - navigation.expand # Read : https://jimandreas.github.io/mkdocs-material/setup/setting-up-navigation/#navigation-expansion
+    # - navigation.tabs.sticky # Disabled as scroll down on pages doesn't require the nav bar
+    # - navigation.indexes
+    - navigation.top
+    - navigation.tracking
+    - search.highlight
+    - search.share
+    - search.suggest
+    - toc.follow
+    - toc.integrate
     palette:
       # Light mode
       - media: '(prefers-color-scheme: light)'
@@ -68,47 +94,85 @@ theme:
           icon: material/weather-sunny
           name: Light Mode
 
+# Page Tree
 nav:
-  - Start: index.md
-  - Code Of Conduct: CODE_OF_CONDUCT.md
-  - Contribution Guide: Contribution.md
-  - Agile:
-    - Introduction To Agile: topic/1.0. Agile/00. Introduction.md
-    - Understanding the four values of agile: topic/1.0. Agile/01. Understanding the four values of agile.md
-    - Using agile in everyday work: topic/1.0. Agile/02. Using agile in everyday work.md
-  - DevOps:
-    - Introduction To DevOps: topic/4.0. DevOps/00. Introduction.md
-  - ITSM:
-    - Introduction To ITSM: topic/9.0. ITSM/00. Introduction.md
-    - Key Terms: topic/9.0. ITSM/01. Key Terms.md
-    - ITSM Library and Practices: topic/9.0. ITSM/02. ITSM Library and Practices.md
-    - Core ITSM Practices: topic/9.0. ITSM/03. Core ITSM Practices.md
-    - Maturity Matters: topic/9.0. ITSM/04. Maturity Matters.md
-    - The Atlassian ITSM Solution: topic/9.0. ITSM/05. The Atlassian ITSM Solution.md
-    - Key Takeaways: topic/9.0. ITSM/06. Key Takeaways.md
-  - Kanban:
-    - Introduction To Kanban: topic/11.0. Kanban/00. Introduction.md
-    - Kanban Using Jira: topic/11.0. Kanban/01. Kanban Using Jira.md
-  - Scrum:
-    - Introduction To Scrum: topic/19.0. Scrum/00. Introduction.md
-    - Scrum With Jira: topic/19.0. Scrum/01. Scrum With Jira.md
-  - Management:
-    - Run Effective Meetings:
-      - Planning A Productive Meeting: topic/13.1. Management/00. Run Effective Meetings/01. Introduction.md
-      - Event Determination: topic/13.1. Management/00. Run Effective Meetings/02. Event Determination.md
-      - Running Effective Meeting: topic/13.1. Management/00. Run Effective Meetings/03. Running Effective Meeting.md
-      - Preparation: topic/13.1. Management/00. Run Effective Meetings/04. Preparation.md
-      - Facilitation: topic/13.1. Management/00. Run Effective Meetings/05. Facilitation.md
-      - Participation: topic/13.1. Management/00. Run Effective Meetings/06. Participation.md
-      - Follow-up: topic/13.1. Management/00. Run Effective Meetings/07. Follow-up.md
+  - Home: index.html
+  - Getting Started:
+    - Start: readme.md
+    - Code Of Conduct: CODE_OF_CONDUCT.md
+    - How To Contribute?: contribution.md
+    - Release Note: CHANGELOG.md
+  - Foundation:
+    # - Foundation Introduction: topic/foundation.html
+    - DevOps: 
+      - Introduction to DevOps: topic/4.0. DevOps/00. Introduction.md
+    # - Core Subjects:
+    #   - Operating Systemm
+    #   - Networking
+    #   - System Design
+    #   - Object Oriented Programming
+    # - Technologies:
+    #   - Cloud
+    #   - Container
+    #   - Orchestration
+    #   - CI/CD
+    #   - Coding Tools
+    #   - Automation
+    #   - IaaC
+    #   - Virtualization
+    #   - Linux
+    #   - Windows
+    # - Stratagies:
+    #   - Site Reliability Engineering
+    #   - Command Center
+    - Management:
+      - ITSM:
+        - Introduction To ITSM: topic/9.0. ITSM/00. Introduction.md
+        - Key Terms: topic/9.0. ITSM/01. Key Terms.md
+        - ITSM Library and Practices: topic/9.0. ITSM/02. ITSM Library and Practices.md
+        - Core ITSM Practices: topic/9.0. ITSM/03. Core ITSM Practices.md
+        - Maturity Matters: topic/9.0. ITSM/04. Maturity Matters.md
+        - The Atlassian ITSM Solution: topic/9.0. ITSM/05. The Atlassian ITSM Solution.md
+        - Key Takeaways: topic/9.0. ITSM/06. Key Takeaways.md
+      - Kanban:
+        - Introduction To Kanban: topic/11.0. Kanban/00. Introduction.md
+        - Kanban Using Jira: topic/11.0. Kanban/01. Kanban Using Jira.md
+      - Scrum:
+        - Introduction To Scrum: topic/19.0. Scrum/00. Introduction.md
+        - Scrum With Jira: topic/19.0. Scrum/01. Scrum With Jira.md
+      - Agile:
+        - Introduction To Agile: topic/1.0. Agile/00. Introduction.md
+        - Understanding the four values of agile: topic/1.0. Agile/01. Understanding the four values of agile.md
+        - Using agile in everyday work: topic/1.0. Agile/02. Using agile in everyday work.md
+      - Run Effective Meetings:
+        - Planning A Productive Meeting: topic/13.1. Management/00. Run Effective Meetings/01. Introduction.md
+        - Event Determination: topic/13.1. Management/00. Run Effective Meetings/02. Event Determination.md
+        - Running Effective Meeting: topic/13.1. Management/00. Run Effective Meetings/03. Running Effective Meeting.md
+        - Preparation: topic/13.1. Management/00. Run Effective Meetings/04. Preparation.md
+        - Facilitation: topic/13.1. Management/00. Run Effective Meetings/05. Facilitation.md
+        - Participation: topic/13.1. Management/00. Run Effective Meetings/06. Participation.md
+        - Follow-up: topic/13.1. Management/00. Run Effective Meetings/07. Follow-up.md
+    - Interview Preparation: study/interview_prep/interview.md
+  - TuxTechCodes:
+      # - Python
+      # - C++
+      # - Java
+      # - Leetcode:
+      - Integration
+      - Shell
   - Miscellaneous:
     - Acronyms: topic/13.2. Miscellaneous/acronym.md
     - Ports: topic/13.2. Miscellaneous/ports.md
     - Status Codes: topic/13.2. Miscellaneous/status_codes.md
-
+  - Contact Us: contacts.md
 
 # Customization   
 extra:
+  alternate:
+    - name: English
+      link: \en\
+      lang: en
+  generator: false
   consent:
     title: Cookie consent
     description:
@@ -119,7 +183,7 @@ extra:
   social:
     - icon: fontawesome/brands/github
       link: https://github.sprcom/tuxtechlab
-    - icon: fontawesome/brands/twitter
+    - icon: fontawesome/brands/x-twitter
       link: https://twitter.com/arindam_tanti
     - icon: fontawesome/brands/linkedin
       link: https://www.linkedin.com/company/tuxtechlab
@@ -127,7 +191,7 @@ extra:
       link: https://github.com/TuxTechLab/Blogs
   analytics:
     provider: google
-    property: G-BCZ32RGHJ0
+    property: XXXXXX
 
 extra_css:
   - stylesheet/extra.css
@@ -137,29 +201,109 @@ extra_javascript:
 
 # Extensions
 markdown_extensions:
+  - abbr
+  - admonition
+  - attr_list
+  - def_list
+  - footnotes
+  - md_in_html
   - toc:
-      permalink: false
+      permalink: true
+  - pymdownx.arithmatex:
+      generic: true
+  - pymdownx.betterem:
+      smart_enable: all
+  - pymdownx.caret
+  - pymdownx.details
+  - pymdownx.emoji:
+      emoji_generator: !!python/name:material.extensions.emoji.to_svg
+      emoji_index: !!python/name:material.extensions.emoji.twemoji
   - pymdownx.highlight:
-      linenums: true
-      linenums_style: pymdownx.table
+      anchor_linenums: true
+      line_spans: __span
+      pygments_lang_class: true
+  - pymdownx.inlinehilite
+  - pymdownx.keys
+  - pymdownx.magiclink:
+      normalize_issue_symbols: true
+      repo_url_shorthand: true
+      user: squidfunk
+      repo: mkdocs-material
+  - pymdownx.mark
+  - pymdownx.smartsymbols
+  - pymdownx.snippets:
+      auto_append:
+        - includes/mkdocs.md
+  - pymdownx.superfences:
+      custom_fences:
+        - name: mermaid
+          class: mermaid
+          format: !!python/name:pymdownx.superfences.fence_code_format
+  - pymdownx.tabbed:
+      alternate_style: true
+      combine_header_slug: true
+      slugify: !!python/object/apply:pymdownx.slugs.slugify
+        kwds:
+          case: lower
   - pymdownx.tasklist:
       custom_checkbox: true
+  - pymdownx.tilde
+  - abbr
+  - admonition
+  - attr_list
+  - codehilite
+  - def_list
+  - footnotes
+  - md_in_html
+  - pymdownx.arithmatex:
+      generic: true
+  - pymdownx.betterem:
+      smart_enable: all
+  - pymdownx.caret
+  - pymdownx.details
   - pymdownx.emoji:
-      emoji_index: !!python/name:pymdownx.emoji.twemoji
-      emoji_generator: !!python/name:pymdownx.emoji.to_svg
-  - pymdownx.superfences
+      emoji_generator: !!python/name:material.extensions.emoji.to_svg
+      emoji_index: !!python/name:material.extensions.emoji.twemoji
+  - pymdownx.highlight:
+      anchor_linenums: true
+      line_spans: __span
+      pygments_lang_class: true
+  - pymdownx.inlinehilite
+  - pymdownx.keys
+  - pymdownx.magiclink:
+      normalize_issue_symbols: true
+      repo_url_shorthand: true
+      user: squidfunk
+      repo: mkdocs-material
   - pymdownx.mark
+  - pymdownx.smartsymbols
+  - pymdownx.snippets:
+      auto_append:
+        - includes/mkdocs.md
+  - pymdownx.superfences:
+      custom_fences:
+        - name: mermaid
+          class: mermaid
+          format: !!python/name:pymdownx.superfences.fence_code_format
   - pymdownx.tabbed:
       alternate_style: true
+      combine_header_slug: true
+      slugify: !!python/object/apply:pymdownx.slugs.slugify
+        kwds:
+          case: lower
+  - pymdownx.tasklist:
+      custom_checkbox: true
+  - pymdownx.tilde
 
 # Plugins
 plugins:
   - search:
       lang:
         - en
-
-spec:
-  source: 
-    git:
-      ref: Blogs by TuxTechLab
-      url: https://github.com/TuxTechLab/Blogs
+  - blog:
+      blog_dir: blog
+      blog_toc: true
+      post_date_format: full
+      post_url_date_format: yyyy/MM/dd
+  - minify:
+      minify_html: true
diff --git a/blogs.tuxtechlab.Dockerfile b/blogs.tuxtechlab.Dockerfile
new file mode 100644
index 0000000..3e5439b
--- /dev/null
+++ b/blogs.tuxtechlab.Dockerfile
@@ -0,0 +1,11 @@
+FROM squidfunk/mkdocs-material:latest
+
+LABEL maintainer="TuxTechLab <root.tuxtechlab@gamil.com>"
+
+WORKDIR /docs
+
+COPY requirements.txt .
+
+RUN pip install -r requirements.txt
+
+EXPOSE "${BLOGS_CTR_INTERNAL_PORT}"
diff --git a/demo-blogs.env b/demo-blogs.env
new file mode 100644
index 0000000..2da7952
--- /dev/null
+++ b/demo-blogs.env
@@ -0,0 +1,3 @@
+BLOGS_CTR_INTERNAL_PORT=8000
+BLOGS_CTR_EXTERNAL_PORT=8000
+VERIFY_SSL=False
\ No newline at end of file
diff --git a/docker-compose.yml b/docker-compose.yml
index a664d1c..9cf05f7 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -1,12 +1,11 @@
-version: '3.9'
-
 services:
-  blogs-svc:
+  tuxtechblog-mkdocs:
     build:
       context: .
-      dockerfile: mkdocs_blogs.Dockerfile
+      # dockerfile: mkdocs_blogs.Dockerfile
+      dockerfile: blogs.tuxtechlab.Dockerfile
     ports:
-      - "8000:8000"
+      - "${BLOGS_CTR_INTERNAL_PORT}:${BLOGS_CTR_EXTERNAL_PORT}"
     restart: "unless-stopped"
     deploy:
       resources:
@@ -15,4 +14,6 @@ services:
           memory: 50M
         reservations:
           cpus: '0.5'
-          memory: 20M
\ No newline at end of file
+          memory: 20M
+    volumes:
+      - ${PWD}/TuxTechBlogs/:/docs
\ No newline at end of file
diff --git a/env.example b/env.example
deleted file mode 100644
index e69de29..0000000
diff --git a/mkdocs_blogs.Dockerfile b/mkdocs_blogs.Dockerfile
deleted file mode 100644
index c7d3a67..0000000
--- a/mkdocs_blogs.Dockerfile
+++ /dev/null
@@ -1,26 +0,0 @@
-FROM python:3.11-slim
-
-LABEL maintainer="Arindam Tanti <arindamtanti123@gmail.com>"
-
-# Set the working directory in the container
-WORKDIR /app
-
-# Copy the requirements.txt file into the container
-COPY requirements.txt .
-
-# Install Mkdocs and any dependencies specified in requirements.txt
-RUN pip install --no-cache-dir -r requirements.txt
-
-# Copy the Mkdocs project files into the container
-COPY . .
-
-# Delete cache files and temporary files
-RUN rm -rf __pycache__ \
-    && rm -rf .pytest_cache \
-    && find . -name '*.pyc' -delete
-
-# Expose port 8000 to access the Mkdocs site
-EXPOSE 8000
-
-# Command to serve the Mkdocs site
-CMD ["mkdocs", "serve", "-a", "0.0.0.0:8000", "-w", "/app/TuxTechBlogs/", "-f", "/app/TuxTechBlogs/mkdocs.yml", "--verbose"]
diff --git a/poetry.lock b/poetry.lock
index 1d445ce..0655359 100644
--- a/poetry.lock
+++ b/poetry.lock
@@ -1,866 +1,866 @@
-# This file is automatically @generated by Poetry 1.5.1 and should not be changed by hand.
-
-[[package]]
-name = "babel"
-version = "2.14.0"
-description = "Internationalization utilities"
-optional = false
-python-versions = ">=3.7"
-files = [
-    {file = "Babel-2.14.0-py3-none-any.whl", hash = "sha256:efb1a25b7118e67ce3a259bed20545c29cb68be8ad2c784c83689981b7a57287"},
-    {file = "Babel-2.14.0.tar.gz", hash = "sha256:6919867db036398ba21eb5c7a0f6b28ab8cbc3ae7a73a44ebe34ae74a4e7d363"},
-]
-
-[package.extras]
-dev = ["freezegun (>=1.0,<2.0)", "pytest (>=6.0)", "pytest-cov"]
-
-[[package]]
-name = "black"
-version = "24.2.0"
-description = "The uncompromising code formatter."
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "black-24.2.0-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:6981eae48b3b33399c8757036c7f5d48a535b962a7c2310d19361edeef64ce29"},
-    {file = "black-24.2.0-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:d533d5e3259720fdbc1b37444491b024003e012c5173f7d06825a77508085430"},
-    {file = "black-24.2.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:61a0391772490ddfb8a693c067df1ef5227257e72b0e4108482b8d41b5aee13f"},
-    {file = "black-24.2.0-cp310-cp310-win_amd64.whl", hash = "sha256:992e451b04667116680cb88f63449267c13e1ad134f30087dec8527242e9862a"},
-    {file = "black-24.2.0-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:163baf4ef40e6897a2a9b83890e59141cc8c2a98f2dda5080dc15c00ee1e62cd"},
-    {file = "black-24.2.0-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:e37c99f89929af50ffaf912454b3e3b47fd64109659026b678c091a4cd450fb2"},
-    {file = "black-24.2.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:4f9de21bafcba9683853f6c96c2d515e364aee631b178eaa5145fc1c61a3cc92"},
-    {file = "black-24.2.0-cp311-cp311-win_amd64.whl", hash = "sha256:9db528bccb9e8e20c08e716b3b09c6bdd64da0dd129b11e160bf082d4642ac23"},
-    {file = "black-24.2.0-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:d84f29eb3ee44859052073b7636533ec995bd0f64e2fb43aeceefc70090e752b"},
-    {file = "black-24.2.0-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:1e08fb9a15c914b81dd734ddd7fb10513016e5ce7e6704bdd5e1251ceee51ac9"},
-    {file = "black-24.2.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:810d445ae6069ce64030c78ff6127cd9cd178a9ac3361435708b907d8a04c693"},
-    {file = "black-24.2.0-cp312-cp312-win_amd64.whl", hash = "sha256:ba15742a13de85e9b8f3239c8f807723991fbfae24bad92d34a2b12e81904982"},
-    {file = "black-24.2.0-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:7e53a8c630f71db01b28cd9602a1ada68c937cbf2c333e6ed041390d6968faf4"},
-    {file = "black-24.2.0-cp38-cp38-macosx_11_0_arm64.whl", hash = "sha256:93601c2deb321b4bad8f95df408e3fb3943d85012dddb6121336b8e24a0d1218"},
-    {file = "black-24.2.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:a0057f800de6acc4407fe75bb147b0c2b5cbb7c3ed110d3e5999cd01184d53b0"},
-    {file = "black-24.2.0-cp38-cp38-win_amd64.whl", hash = "sha256:faf2ee02e6612577ba0181f4347bcbcf591eb122f7841ae5ba233d12c39dcb4d"},
-    {file = "black-24.2.0-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:057c3dc602eaa6fdc451069bd027a1b2635028b575a6c3acfd63193ced20d9c8"},
-    {file = "black-24.2.0-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:08654d0797e65f2423f850fc8e16a0ce50925f9337fb4a4a176a7aa4026e63f8"},
-    {file = "black-24.2.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:ca610d29415ee1a30a3f30fab7a8f4144e9d34c89a235d81292a1edb2b55f540"},
-    {file = "black-24.2.0-cp39-cp39-win_amd64.whl", hash = "sha256:4dd76e9468d5536abd40ffbc7a247f83b2324f0c050556d9c371c2b9a9a95e31"},
-    {file = "black-24.2.0-py3-none-any.whl", hash = "sha256:e8a6ae970537e67830776488bca52000eaa37fa63b9988e8c487458d9cd5ace6"},
-    {file = "black-24.2.0.tar.gz", hash = "sha256:bce4f25c27c3435e4dace4815bcb2008b87e167e3bf4ee47ccdc5ce906eb4894"},
-]
-
-[package.dependencies]
-click = ">=8.0.0"
-mypy-extensions = ">=0.4.3"
-packaging = ">=22.0"
-pathspec = ">=0.9.0"
-platformdirs = ">=2"
-
-[package.extras]
-colorama = ["colorama (>=0.4.3)"]
-d = ["aiohttp (>=3.7.4)", "aiohttp (>=3.7.4,!=3.9.0)"]
-jupyter = ["ipython (>=7.8.0)", "tokenize-rt (>=3.2.0)"]
-uvloop = ["uvloop (>=0.15.2)"]
-
-[[package]]
-name = "certifi"
-version = "2024.2.2"
-description = "Python package for providing Mozilla's CA Bundle."
-optional = false
-python-versions = ">=3.6"
-files = [
-    {file = "certifi-2024.2.2-py3-none-any.whl", hash = "sha256:dc383c07b76109f368f6106eee2b593b04a011ea4d55f652c6ca24a754d1cdd1"},
-    {file = "certifi-2024.2.2.tar.gz", hash = "sha256:0569859f95fc761b18b45ef421b1290a0f65f147e92a1e5eb3e635f9a5e4e66f"},
-]
-
-[[package]]
-name = "charset-normalizer"
-version = "3.3.2"
-description = "The Real First Universal Charset Detector. Open, modern and actively maintained alternative to Chardet."
-optional = false
-python-versions = ">=3.7.0"
-files = [
-    {file = "charset-normalizer-3.3.2.tar.gz", hash = "sha256:f30c3cb33b24454a82faecaf01b19c18562b1e89558fb6c56de4d9118a032fd5"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-macosx_10_9_universal2.whl", hash = "sha256:25baf083bf6f6b341f4121c2f3c548875ee6f5339300e08be3f2b2ba1721cdd3"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:06435b539f889b1f6f4ac1758871aae42dc3a8c0e24ac9e60c2384973ad73027"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:9063e24fdb1e498ab71cb7419e24622516c4a04476b17a2dab57e8baa30d6e03"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:6897af51655e3691ff853668779c7bad41579facacf5fd7253b0133308cf000d"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:1d3193f4a680c64b4b6a9115943538edb896edc190f0b222e73761716519268e"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:cd70574b12bb8a4d2aaa0094515df2463cb429d8536cfb6c7ce983246983e5a6"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:8465322196c8b4d7ab6d1e049e4c5cb460d0394da4a27d23cc242fbf0034b6b5"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:a9a8e9031d613fd2009c182b69c7b2c1ef8239a0efb1df3f7c8da66d5dd3d537"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-musllinux_1_1_aarch64.whl", hash = "sha256:beb58fe5cdb101e3a055192ac291b7a21e3b7ef4f67fa1d74e331a7f2124341c"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-musllinux_1_1_i686.whl", hash = "sha256:e06ed3eb3218bc64786f7db41917d4e686cc4856944f53d5bdf83a6884432e12"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-musllinux_1_1_ppc64le.whl", hash = "sha256:2e81c7b9c8979ce92ed306c249d46894776a909505d8f5a4ba55b14206e3222f"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-musllinux_1_1_s390x.whl", hash = "sha256:572c3763a264ba47b3cf708a44ce965d98555f618ca42c926a9c1616d8f34269"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-musllinux_1_1_x86_64.whl", hash = "sha256:fd1abc0d89e30cc4e02e4064dc67fcc51bd941eb395c502aac3ec19fab46b519"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-win32.whl", hash = "sha256:3d47fa203a7bd9c5b6cee4736ee84ca03b8ef23193c0d1ca99b5089f72645c73"},
-    {file = "charset_normalizer-3.3.2-cp310-cp310-win_amd64.whl", hash = "sha256:10955842570876604d404661fbccbc9c7e684caf432c09c715ec38fbae45ae09"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:802fe99cca7457642125a8a88a084cef28ff0cf9407060f7b93dca5aa25480db"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:573f6eac48f4769d667c4442081b1794f52919e7edada77495aaed9236d13a96"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:549a3a73da901d5bc3ce8d24e0600d1fa85524c10287f6004fbab87672bf3e1e"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:f27273b60488abe721a075bcca6d7f3964f9f6f067c8c4c605743023d7d3944f"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:1ceae2f17a9c33cb48e3263960dc5fc8005351ee19db217e9b1bb15d28c02574"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:65f6f63034100ead094b8744b3b97965785388f308a64cf8d7c34f2f2e5be0c4"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:753f10e867343b4511128c6ed8c82f7bec3bd026875576dfd88483c5c73b2fd8"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:4a78b2b446bd7c934f5dcedc588903fb2f5eec172f3d29e52a9096a43722adfc"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-musllinux_1_1_aarch64.whl", hash = "sha256:e537484df0d8f426ce2afb2d0f8e1c3d0b114b83f8850e5f2fbea0e797bd82ae"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-musllinux_1_1_i686.whl", hash = "sha256:eb6904c354526e758fda7167b33005998fb68c46fbc10e013ca97f21ca5c8887"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-musllinux_1_1_ppc64le.whl", hash = "sha256:deb6be0ac38ece9ba87dea880e438f25ca3eddfac8b002a2ec3d9183a454e8ae"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-musllinux_1_1_s390x.whl", hash = "sha256:4ab2fe47fae9e0f9dee8c04187ce5d09f48eabe611be8259444906793ab7cbce"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-musllinux_1_1_x86_64.whl", hash = "sha256:80402cd6ee291dcb72644d6eac93785fe2c8b9cb30893c1af5b8fdd753b9d40f"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-win32.whl", hash = "sha256:7cd13a2e3ddeed6913a65e66e94b51d80a041145a026c27e6bb76c31a853c6ab"},
-    {file = "charset_normalizer-3.3.2-cp311-cp311-win_amd64.whl", hash = "sha256:663946639d296df6a2bb2aa51b60a2454ca1cb29835324c640dafb5ff2131a77"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-macosx_10_9_universal2.whl", hash = "sha256:0b2b64d2bb6d3fb9112bafa732def486049e63de9618b5843bcdd081d8144cd8"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:ddbb2551d7e0102e7252db79ba445cdab71b26640817ab1e3e3648dad515003b"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:55086ee1064215781fff39a1af09518bc9255b50d6333f2e4c74ca09fac6a8f6"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:8f4a014bc36d3c57402e2977dada34f9c12300af536839dc38c0beab8878f38a"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:a10af20b82360ab00827f916a6058451b723b4e65030c5a18577c8b2de5b3389"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:8d756e44e94489e49571086ef83b2bb8ce311e730092d2c34ca8f7d925cb20aa"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:90d558489962fd4918143277a773316e56c72da56ec7aa3dc3dbbe20fdfed15b"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:6ac7ffc7ad6d040517be39eb591cac5ff87416c2537df6ba3cba3bae290c0fed"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-musllinux_1_1_aarch64.whl", hash = "sha256:7ed9e526742851e8d5cc9e6cf41427dfc6068d4f5a3bb03659444b4cabf6bc26"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-musllinux_1_1_i686.whl", hash = "sha256:8bdb58ff7ba23002a4c5808d608e4e6c687175724f54a5dade5fa8c67b604e4d"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-musllinux_1_1_ppc64le.whl", hash = "sha256:6b3251890fff30ee142c44144871185dbe13b11bab478a88887a639655be1068"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-musllinux_1_1_s390x.whl", hash = "sha256:b4a23f61ce87adf89be746c8a8974fe1c823c891d8f86eb218bb957c924bb143"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:efcb3f6676480691518c177e3b465bcddf57cea040302f9f4e6e191af91174d4"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-win32.whl", hash = "sha256:d965bba47ddeec8cd560687584e88cf699fd28f192ceb452d1d7ee807c5597b7"},
-    {file = "charset_normalizer-3.3.2-cp312-cp312-win_amd64.whl", hash = "sha256:96b02a3dc4381e5494fad39be677abcb5e6634bf7b4fa83a6dd3112607547001"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-macosx_10_9_x86_64.whl", hash = "sha256:95f2a5796329323b8f0512e09dbb7a1860c46a39da62ecb2324f116fa8fdc85c"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:c002b4ffc0be611f0d9da932eb0f704fe2602a9a949d1f738e4c34c75b0863d5"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:a981a536974bbc7a512cf44ed14938cf01030a99e9b3a06dd59578882f06f985"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:3287761bc4ee9e33561a7e058c72ac0938c4f57fe49a09eae428fd88aafe7bb6"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:42cb296636fcc8b0644486d15c12376cb9fa75443e00fb25de0b8602e64c1714"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:0a55554a2fa0d408816b3b5cedf0045f4b8e1a6065aec45849de2d6f3f8e9786"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-musllinux_1_1_aarch64.whl", hash = "sha256:c083af607d2515612056a31f0a8d9e0fcb5876b7bfc0abad3ecd275bc4ebc2d5"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-musllinux_1_1_i686.whl", hash = "sha256:87d1351268731db79e0f8e745d92493ee2841c974128ef629dc518b937d9194c"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-musllinux_1_1_ppc64le.whl", hash = "sha256:bd8f7df7d12c2db9fab40bdd87a7c09b1530128315d047a086fa3ae3435cb3a8"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-musllinux_1_1_s390x.whl", hash = "sha256:c180f51afb394e165eafe4ac2936a14bee3eb10debc9d9e4db8958fe36afe711"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-musllinux_1_1_x86_64.whl", hash = "sha256:8c622a5fe39a48f78944a87d4fb8a53ee07344641b0562c540d840748571b811"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-win32.whl", hash = "sha256:db364eca23f876da6f9e16c9da0df51aa4f104a972735574842618b8c6d999d4"},
-    {file = "charset_normalizer-3.3.2-cp37-cp37m-win_amd64.whl", hash = "sha256:86216b5cee4b06df986d214f664305142d9c76df9b6512be2738aa72a2048f99"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-macosx_10_9_universal2.whl", hash = "sha256:6463effa3186ea09411d50efc7d85360b38d5f09b870c48e4600f63af490e56a"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:6c4caeef8fa63d06bd437cd4bdcf3ffefe6738fb1b25951440d80dc7df8c03ac"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-macosx_11_0_arm64.whl", hash = "sha256:37e55c8e51c236f95b033f6fb391d7d7970ba5fe7ff453dad675e88cf303377a"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:fb69256e180cb6c8a894fee62b3afebae785babc1ee98b81cdf68bbca1987f33"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:ae5f4161f18c61806f411a13b0310bea87f987c7d2ecdbdaad0e94eb2e404238"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:b2b0a0c0517616b6869869f8c581d4eb2dd83a4d79e0ebcb7d373ef9956aeb0a"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:45485e01ff4d3630ec0d9617310448a8702f70e9c01906b0d0118bdf9d124cf2"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:eb00ed941194665c332bf8e078baf037d6c35d7c4f3102ea2d4f16ca94a26dc8"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-musllinux_1_1_aarch64.whl", hash = "sha256:2127566c664442652f024c837091890cb1942c30937add288223dc895793f898"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-musllinux_1_1_i686.whl", hash = "sha256:a50aebfa173e157099939b17f18600f72f84eed3049e743b68ad15bd69b6bf99"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-musllinux_1_1_ppc64le.whl", hash = "sha256:4d0d1650369165a14e14e1e47b372cfcb31d6ab44e6e33cb2d4e57265290044d"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-musllinux_1_1_s390x.whl", hash = "sha256:923c0c831b7cfcb071580d3f46c4baf50f174be571576556269530f4bbd79d04"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-musllinux_1_1_x86_64.whl", hash = "sha256:06a81e93cd441c56a9b65d8e1d043daeb97a3d0856d177d5c90ba85acb3db087"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-win32.whl", hash = "sha256:6ef1d82a3af9d3eecdba2321dc1b3c238245d890843e040e41e470ffa64c3e25"},
-    {file = "charset_normalizer-3.3.2-cp38-cp38-win_amd64.whl", hash = "sha256:eb8821e09e916165e160797a6c17edda0679379a4be5c716c260e836e122f54b"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-macosx_10_9_universal2.whl", hash = "sha256:c235ebd9baae02f1b77bcea61bce332cb4331dc3617d254df3323aa01ab47bd4"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:5b4c145409bef602a690e7cfad0a15a55c13320ff7a3ad7ca59c13bb8ba4d45d"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:68d1f8a9e9e37c1223b656399be5d6b448dea850bed7d0f87a8311f1ff3dabb0"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:22afcb9f253dac0696b5a4be4a1c0f8762f8239e21b99680099abd9b2b1b2269"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:e27ad930a842b4c5eb8ac0016b0a54f5aebbe679340c26101df33424142c143c"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:1f79682fbe303db92bc2b1136016a38a42e835d932bab5b3b1bfcfbf0640e519"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:b261ccdec7821281dade748d088bb6e9b69e6d15b30652b74cbbac25e280b796"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:122c7fa62b130ed55f8f285bfd56d5f4b4a5b503609d181f9ad85e55c89f4185"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-musllinux_1_1_aarch64.whl", hash = "sha256:d0eccceffcb53201b5bfebb52600a5fb483a20b61da9dbc885f8b103cbe7598c"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-musllinux_1_1_i686.whl", hash = "sha256:9f96df6923e21816da7e0ad3fd47dd8f94b2a5ce594e00677c0013018b813458"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-musllinux_1_1_ppc64le.whl", hash = "sha256:7f04c839ed0b6b98b1a7501a002144b76c18fb1c1850c8b98d458ac269e26ed2"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-musllinux_1_1_s390x.whl", hash = "sha256:34d1c8da1e78d2e001f363791c98a272bb734000fcef47a491c1e3b0505657a8"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-musllinux_1_1_x86_64.whl", hash = "sha256:ff8fa367d09b717b2a17a052544193ad76cd49979c805768879cb63d9ca50561"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-win32.whl", hash = "sha256:aed38f6e4fb3f5d6bf81bfa990a07806be9d83cf7bacef998ab1a9bd660a581f"},
-    {file = "charset_normalizer-3.3.2-cp39-cp39-win_amd64.whl", hash = "sha256:b01b88d45a6fcb69667cd6d2f7a9aeb4bf53760d7fc536bf679ec94fe9f3ff3d"},
-    {file = "charset_normalizer-3.3.2-py3-none-any.whl", hash = "sha256:3e4d1f6587322d2788836a99c69062fbb091331ec940e02d12d179c1d53e25fc"},
-]
-
-[[package]]
-name = "click"
-version = "8.1.7"
-description = "Composable command line interface toolkit"
-optional = false
-python-versions = ">=3.7"
-files = [
-    {file = "click-8.1.7-py3-none-any.whl", hash = "sha256:ae74fb96c20a0277a1d615f1e4d73c8414f5a98db8b799a7931d1582f3390c28"},
-    {file = "click-8.1.7.tar.gz", hash = "sha256:ca9853ad459e787e2192211578cc907e7594e294c7ccc834310722b41b9ca6de"},
-]
-
-[package.dependencies]
-colorama = {version = "*", markers = "platform_system == \"Windows\""}
-
-[[package]]
-name = "colorama"
-version = "0.4.6"
-description = "Cross-platform colored terminal text."
-optional = false
-python-versions = "!=3.0.*,!=3.1.*,!=3.2.*,!=3.3.*,!=3.4.*,!=3.5.*,!=3.6.*,>=2.7"
-files = [
-    {file = "colorama-0.4.6-py2.py3-none-any.whl", hash = "sha256:4f1d9991f5acc0ca119f9d443620b77f9d6b33703e51011c16baf57afb285fc6"},
-    {file = "colorama-0.4.6.tar.gz", hash = "sha256:08695f5cb7ed6e0531a20572697297273c47b8cae5a63ffc6d6ed5c201be6e44"},
-]
-
-[[package]]
-name = "flake8"
-version = "7.0.0"
-description = "the modular source code checker: pep8 pyflakes and co"
-optional = false
-python-versions = ">=3.8.1"
-files = [
-    {file = "flake8-7.0.0-py2.py3-none-any.whl", hash = "sha256:a6dfbb75e03252917f2473ea9653f7cd799c3064e54d4c8140044c5c065f53c3"},
-    {file = "flake8-7.0.0.tar.gz", hash = "sha256:33f96621059e65eec474169085dc92bf26e7b2d47366b70be2f67ab80dc25132"},
-]
-
-[package.dependencies]
-mccabe = ">=0.7.0,<0.8.0"
-pycodestyle = ">=2.11.0,<2.12.0"
-pyflakes = ">=3.2.0,<3.3.0"
-
-[[package]]
-name = "ghp-import"
-version = "2.1.0"
-description = "Copy your docs directly to the gh-pages branch."
-optional = false
-python-versions = "*"
-files = [
-    {file = "ghp-import-2.1.0.tar.gz", hash = "sha256:9c535c4c61193c2df8871222567d7fd7e5014d835f97dc7b7439069e2413d343"},
-    {file = "ghp_import-2.1.0-py3-none-any.whl", hash = "sha256:8337dd7b50877f163d4c0289bc1f1c7f127550241988d568c1db512c4324a619"},
-]
-
-[package.dependencies]
-python-dateutil = ">=2.8.1"
-
-[package.extras]
-dev = ["flake8", "markdown", "twine", "wheel"]
-
-[[package]]
-name = "idna"
-version = "3.6"
-description = "Internationalized Domain Names in Applications (IDNA)"
-optional = false
-python-versions = ">=3.5"
-files = [
-    {file = "idna-3.6-py3-none-any.whl", hash = "sha256:c05567e9c24a6b9faaa835c4821bad0590fbb9d5779e7caa6e1cc4978e7eb24f"},
-    {file = "idna-3.6.tar.gz", hash = "sha256:9ecdbbd083b06798ae1e86adcbfe8ab1479cf864e4ee30fe4e46a003d12491ca"},
-]
-
-[[package]]
-name = "jinja2"
-version = "3.1.3"
-description = "A very fast and expressive template engine."
-optional = false
-python-versions = ">=3.7"
-files = [
-    {file = "Jinja2-3.1.3-py3-none-any.whl", hash = "sha256:7d6d50dd97d52cbc355597bd845fabfbac3f551e1f99619e39a35ce8c370b5fa"},
-    {file = "Jinja2-3.1.3.tar.gz", hash = "sha256:ac8bd6544d4bb2c9792bf3a159e80bba8fda7f07e81bc3aed565432d5925ba90"},
-]
-
-[package.dependencies]
-MarkupSafe = ">=2.0"
-
-[package.extras]
-i18n = ["Babel (>=2.7)"]
-
-[[package]]
-name = "markdown"
-version = "3.5.2"
-description = "Python implementation of John Gruber's Markdown."
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "Markdown-3.5.2-py3-none-any.whl", hash = "sha256:d43323865d89fc0cb9b20c75fc8ad313af307cc087e84b657d9eec768eddeadd"},
-    {file = "Markdown-3.5.2.tar.gz", hash = "sha256:e1ac7b3dc550ee80e602e71c1d168002f062e49f1b11e26a36264dafd4df2ef8"},
-]
-
-[package.extras]
-docs = ["mdx-gh-links (>=0.2)", "mkdocs (>=1.5)", "mkdocs-gen-files", "mkdocs-literate-nav", "mkdocs-nature (>=0.6)", "mkdocs-section-index", "mkdocstrings[python]"]
-testing = ["coverage", "pyyaml"]
-
-[[package]]
-name = "markupsafe"
-version = "2.1.5"
-description = "Safely add untrusted strings to HTML/XML markup."
-optional = false
-python-versions = ">=3.7"
-files = [
-    {file = "MarkupSafe-2.1.5-cp310-cp310-macosx_10_9_universal2.whl", hash = "sha256:a17a92de5231666cfbe003f0e4b9b3a7ae3afb1ec2845aadc2bacc93ff85febc"},
-    {file = "MarkupSafe-2.1.5-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:72b6be590cc35924b02c78ef34b467da4ba07e4e0f0454a2c5907f473fc50ce5"},
-    {file = "MarkupSafe-2.1.5-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:e61659ba32cf2cf1481e575d0462554625196a1f2fc06a1c777d3f48e8865d46"},
-    {file = "MarkupSafe-2.1.5-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:2174c595a0d73a3080ca3257b40096db99799265e1c27cc5a610743acd86d62f"},
-    {file = "MarkupSafe-2.1.5-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:ae2ad8ae6ebee9d2d94b17fb62763125f3f374c25618198f40cbb8b525411900"},
-    {file = "MarkupSafe-2.1.5-cp310-cp310-musllinux_1_1_aarch64.whl", hash = "sha256:075202fa5b72c86ad32dc7d0b56024ebdbcf2048c0ba09f1cde31bfdd57bcfff"},
-    {file = "MarkupSafe-2.1.5-cp310-cp310-musllinux_1_1_i686.whl", hash = "sha256:598e3276b64aff0e7b3451b72e94fa3c238d452e7ddcd893c3ab324717456bad"},
-    {file = "MarkupSafe-2.1.5-cp310-cp310-musllinux_1_1_x86_64.whl", hash = "sha256:fce659a462a1be54d2ffcacea5e3ba2d74daa74f30f5f143fe0c58636e355fdd"},
-    {file = "MarkupSafe-2.1.5-cp310-cp310-win32.whl", hash = "sha256:d9fad5155d72433c921b782e58892377c44bd6252b5af2f67f16b194987338a4"},
-    {file = "MarkupSafe-2.1.5-cp310-cp310-win_amd64.whl", hash = "sha256:bf50cd79a75d181c9181df03572cdce0fbb75cc353bc350712073108cba98de5"},
-    {file = "MarkupSafe-2.1.5-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:629ddd2ca402ae6dbedfceeba9c46d5f7b2a61d9749597d4307f943ef198fc1f"},
-    {file = "MarkupSafe-2.1.5-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:5b7b716f97b52c5a14bffdf688f971b2d5ef4029127f1ad7a513973cfd818df2"},
-    {file = "MarkupSafe-2.1.5-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:6ec585f69cec0aa07d945b20805be741395e28ac1627333b1c5b0105962ffced"},
-    {file = "MarkupSafe-2.1.5-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:b91c037585eba9095565a3556f611e3cbfaa42ca1e865f7b8015fe5c7336d5a5"},
-    {file = "MarkupSafe-2.1.5-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:7502934a33b54030eaf1194c21c692a534196063db72176b0c4028e140f8f32c"},
-    {file = "MarkupSafe-2.1.5-cp311-cp311-musllinux_1_1_aarch64.whl", hash = "sha256:0e397ac966fdf721b2c528cf028494e86172b4feba51d65f81ffd65c63798f3f"},
-    {file = "MarkupSafe-2.1.5-cp311-cp311-musllinux_1_1_i686.whl", hash = "sha256:c061bb86a71b42465156a3ee7bd58c8c2ceacdbeb95d05a99893e08b8467359a"},
-    {file = "MarkupSafe-2.1.5-cp311-cp311-musllinux_1_1_x86_64.whl", hash = "sha256:3a57fdd7ce31c7ff06cdfbf31dafa96cc533c21e443d57f5b1ecc6cdc668ec7f"},
-    {file = "MarkupSafe-2.1.5-cp311-cp311-win32.whl", hash = "sha256:397081c1a0bfb5124355710fe79478cdbeb39626492b15d399526ae53422b906"},
-    {file = "MarkupSafe-2.1.5-cp311-cp311-win_amd64.whl", hash = "sha256:2b7c57a4dfc4f16f7142221afe5ba4e093e09e728ca65c51f5620c9aaeb9a617"},
-    {file = "MarkupSafe-2.1.5-cp312-cp312-macosx_10_9_universal2.whl", hash = "sha256:8dec4936e9c3100156f8a2dc89c4b88d5c435175ff03413b443469c7c8c5f4d1"},
-    {file = "MarkupSafe-2.1.5-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:3c6b973f22eb18a789b1460b4b91bf04ae3f0c4234a0a6aa6b0a92f6f7b951d4"},
-    {file = "MarkupSafe-2.1.5-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:ac07bad82163452a6884fe8fa0963fb98c2346ba78d779ec06bd7a6262132aee"},
-    {file = "MarkupSafe-2.1.5-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:f5dfb42c4604dddc8e4305050aa6deb084540643ed5804d7455b5df8fe16f5e5"},
-    {file = "MarkupSafe-2.1.5-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:ea3d8a3d18833cf4304cd2fc9cbb1efe188ca9b5efef2bdac7adc20594a0e46b"},
-    {file = "MarkupSafe-2.1.5-cp312-cp312-musllinux_1_1_aarch64.whl", hash = "sha256:d050b3361367a06d752db6ead6e7edeb0009be66bc3bae0ee9d97fb326badc2a"},
-    {file = "MarkupSafe-2.1.5-cp312-cp312-musllinux_1_1_i686.whl", hash = "sha256:bec0a414d016ac1a18862a519e54b2fd0fc8bbfd6890376898a6c0891dd82e9f"},
-    {file = "MarkupSafe-2.1.5-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:58c98fee265677f63a4385256a6d7683ab1832f3ddd1e66fe948d5880c21a169"},
-    {file = "MarkupSafe-2.1.5-cp312-cp312-win32.whl", hash = "sha256:8590b4ae07a35970728874632fed7bd57b26b0102df2d2b233b6d9d82f6c62ad"},
-    {file = "MarkupSafe-2.1.5-cp312-cp312-win_amd64.whl", hash = "sha256:823b65d8706e32ad2df51ed89496147a42a2a6e01c13cfb6ffb8b1e92bc910bb"},
-    {file = "MarkupSafe-2.1.5-cp37-cp37m-macosx_10_9_x86_64.whl", hash = "sha256:c8b29db45f8fe46ad280a7294f5c3ec36dbac9491f2d1c17345be8e69cc5928f"},
-    {file = "MarkupSafe-2.1.5-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:ec6a563cff360b50eed26f13adc43e61bc0c04d94b8be985e6fb24b81f6dcfdf"},
-    {file = "MarkupSafe-2.1.5-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:a549b9c31bec33820e885335b451286e2969a2d9e24879f83fe904a5ce59d70a"},
-    {file = "MarkupSafe-2.1.5-cp37-cp37m-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:4f11aa001c540f62c6166c7726f71f7573b52c68c31f014c25cc7901deea0b52"},
-    {file = "MarkupSafe-2.1.5-cp37-cp37m-musllinux_1_1_aarch64.whl", hash = "sha256:7b2e5a267c855eea6b4283940daa6e88a285f5f2a67f2220203786dfa59b37e9"},
-    {file = "MarkupSafe-2.1.5-cp37-cp37m-musllinux_1_1_i686.whl", hash = "sha256:2d2d793e36e230fd32babe143b04cec8a8b3eb8a3122d2aceb4a371e6b09b8df"},
-    {file = "MarkupSafe-2.1.5-cp37-cp37m-musllinux_1_1_x86_64.whl", hash = "sha256:ce409136744f6521e39fd8e2a24c53fa18ad67aa5bc7c2cf83645cce5b5c4e50"},
-    {file = "MarkupSafe-2.1.5-cp37-cp37m-win32.whl", hash = "sha256:4096e9de5c6fdf43fb4f04c26fb114f61ef0bf2e5604b6ee3019d51b69e8c371"},
-    {file = "MarkupSafe-2.1.5-cp37-cp37m-win_amd64.whl", hash = "sha256:4275d846e41ecefa46e2015117a9f491e57a71ddd59bbead77e904dc02b1bed2"},
-    {file = "MarkupSafe-2.1.5-cp38-cp38-macosx_10_9_universal2.whl", hash = "sha256:656f7526c69fac7f600bd1f400991cc282b417d17539a1b228617081106feb4a"},
-    {file = "MarkupSafe-2.1.5-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:97cafb1f3cbcd3fd2b6fbfb99ae11cdb14deea0736fc2b0952ee177f2b813a46"},
-    {file = "MarkupSafe-2.1.5-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:1f3fbcb7ef1f16e48246f704ab79d79da8a46891e2da03f8783a5b6fa41a9532"},
-    {file = "MarkupSafe-2.1.5-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:fa9db3f79de01457b03d4f01b34cf91bc0048eb2c3846ff26f66687c2f6d16ab"},
-    {file = "MarkupSafe-2.1.5-cp38-cp38-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:ffee1f21e5ef0d712f9033568f8344d5da8cc2869dbd08d87c84656e6a2d2f68"},
-    {file = "MarkupSafe-2.1.5-cp38-cp38-musllinux_1_1_aarch64.whl", hash = "sha256:5dedb4db619ba5a2787a94d877bc8ffc0566f92a01c0ef214865e54ecc9ee5e0"},
-    {file = "MarkupSafe-2.1.5-cp38-cp38-musllinux_1_1_i686.whl", hash = "sha256:30b600cf0a7ac9234b2638fbc0fb6158ba5bdcdf46aeb631ead21248b9affbc4"},
-    {file = "MarkupSafe-2.1.5-cp38-cp38-musllinux_1_1_x86_64.whl", hash = "sha256:8dd717634f5a044f860435c1d8c16a270ddf0ef8588d4887037c5028b859b0c3"},
-    {file = "MarkupSafe-2.1.5-cp38-cp38-win32.whl", hash = "sha256:daa4ee5a243f0f20d528d939d06670a298dd39b1ad5f8a72a4275124a7819eff"},
-    {file = "MarkupSafe-2.1.5-cp38-cp38-win_amd64.whl", hash = "sha256:619bc166c4f2de5caa5a633b8b7326fbe98e0ccbfacabd87268a2b15ff73a029"},
-    {file = "MarkupSafe-2.1.5-cp39-cp39-macosx_10_9_universal2.whl", hash = "sha256:7a68b554d356a91cce1236aa7682dc01df0edba8d043fd1ce607c49dd3c1edcf"},
-    {file = "MarkupSafe-2.1.5-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:db0b55e0f3cc0be60c1f19efdde9a637c32740486004f20d1cff53c3c0ece4d2"},
-    {file = "MarkupSafe-2.1.5-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:3e53af139f8579a6d5f7b76549125f0d94d7e630761a2111bc431fd820e163b8"},
-    {file = "MarkupSafe-2.1.5-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:17b950fccb810b3293638215058e432159d2b71005c74371d784862b7e4683f3"},
-    {file = "MarkupSafe-2.1.5-cp39-cp39-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:4c31f53cdae6ecfa91a77820e8b151dba54ab528ba65dfd235c80b086d68a465"},
-    {file = "MarkupSafe-2.1.5-cp39-cp39-musllinux_1_1_aarch64.whl", hash = "sha256:bff1b4290a66b490a2f4719358c0cdcd9bafb6b8f061e45c7a2460866bf50c2e"},
-    {file = "MarkupSafe-2.1.5-cp39-cp39-musllinux_1_1_i686.whl", hash = "sha256:bc1667f8b83f48511b94671e0e441401371dfd0f0a795c7daa4a3cd1dde55bea"},
-    {file = "MarkupSafe-2.1.5-cp39-cp39-musllinux_1_1_x86_64.whl", hash = "sha256:5049256f536511ee3f7e1b3f87d1d1209d327e818e6ae1365e8653d7e3abb6a6"},
-    {file = "MarkupSafe-2.1.5-cp39-cp39-win32.whl", hash = "sha256:00e046b6dd71aa03a41079792f8473dc494d564611a8f89bbbd7cb93295ebdcf"},
-    {file = "MarkupSafe-2.1.5-cp39-cp39-win_amd64.whl", hash = "sha256:fa173ec60341d6bb97a89f5ea19c85c5643c1e7dedebc22f5181eb73573142c5"},
-    {file = "MarkupSafe-2.1.5.tar.gz", hash = "sha256:d283d37a890ba4c1ae73ffadf8046435c76e7bc2247bbb63c00bd1a709c6544b"},
-]
-
-[[package]]
-name = "mccabe"
-version = "0.7.0"
-description = "McCabe checker, plugin for flake8"
-optional = false
-python-versions = ">=3.6"
-files = [
-    {file = "mccabe-0.7.0-py2.py3-none-any.whl", hash = "sha256:6c2d30ab6be0e4a46919781807b4f0d834ebdd6c6e3dca0bda5a15f863427b6e"},
-    {file = "mccabe-0.7.0.tar.gz", hash = "sha256:348e0240c33b60bbdf4e523192ef919f28cb2c3d7d5c7794f74009290f236325"},
-]
-
-[[package]]
-name = "mergedeep"
-version = "1.3.4"
-description = "A deep merge function for 🐍."
-optional = false
-python-versions = ">=3.6"
-files = [
-    {file = "mergedeep-1.3.4-py3-none-any.whl", hash = "sha256:70775750742b25c0d8f36c55aed03d24c3384d17c951b3175d898bd778ef0307"},
-    {file = "mergedeep-1.3.4.tar.gz", hash = "sha256:0096d52e9dad9939c3d975a774666af186eda617e6ca84df4c94dec30004f2a8"},
-]
-
-[[package]]
-name = "mkdocs"
-version = "1.5.3"
-description = "Project documentation with Markdown."
-optional = false
-python-versions = ">=3.7"
-files = [
-    {file = "mkdocs-1.5.3-py3-none-any.whl", hash = "sha256:3b3a78e736b31158d64dbb2f8ba29bd46a379d0c6e324c2246c3bc3d2189cfc1"},
-    {file = "mkdocs-1.5.3.tar.gz", hash = "sha256:eb7c99214dcb945313ba30426c2451b735992c73c2e10838f76d09e39ff4d0e2"},
-]
-
-[package.dependencies]
-click = ">=7.0"
-colorama = {version = ">=0.4", markers = "platform_system == \"Windows\""}
-ghp-import = ">=1.0"
-jinja2 = ">=2.11.1"
-markdown = ">=3.2.1"
-markupsafe = ">=2.0.1"
-mergedeep = ">=1.3.4"
-packaging = ">=20.5"
-pathspec = ">=0.11.1"
-platformdirs = ">=2.2.0"
-pyyaml = ">=5.1"
-pyyaml-env-tag = ">=0.1"
-watchdog = ">=2.0"
-
-[package.extras]
-i18n = ["babel (>=2.9.0)"]
-min-versions = ["babel (==2.9.0)", "click (==7.0)", "colorama (==0.4)", "ghp-import (==1.0)", "importlib-metadata (==4.3)", "jinja2 (==2.11.1)", "markdown (==3.2.1)", "markupsafe (==2.0.1)", "mergedeep (==1.3.4)", "packaging (==20.5)", "pathspec (==0.11.1)", "platformdirs (==2.2.0)", "pyyaml (==5.1)", "pyyaml-env-tag (==0.1)", "typing-extensions (==3.10)", "watchdog (==2.0)"]
-
-[[package]]
-name = "mkdocs-material"
-version = "9.5.12"
-description = "Documentation that simply works"
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "mkdocs_material-9.5.12-py3-none-any.whl", hash = "sha256:d6f0c269f015e48c76291cdc79efb70f7b33bbbf42d649cfe475522ebee61b1f"},
-    {file = "mkdocs_material-9.5.12.tar.gz", hash = "sha256:5f69cef6a8aaa4050b812f72b1094fda3d079b9a51cf27a247244c03ec455e97"},
-]
-
-[package.dependencies]
-babel = ">=2.10,<3.0"
-colorama = ">=0.4,<1.0"
-jinja2 = ">=3.0,<4.0"
-markdown = ">=3.2,<4.0"
-mkdocs = ">=1.5.3,<1.6.0"
-mkdocs-material-extensions = ">=1.3,<2.0"
-paginate = ">=0.5,<1.0"
-pygments = ">=2.16,<3.0"
-pymdown-extensions = ">=10.2,<11.0"
-regex = ">=2022.4"
-requests = ">=2.26,<3.0"
-
-[package.extras]
-git = ["mkdocs-git-committers-plugin-2 (>=1.1,<2.0)", "mkdocs-git-revision-date-localized-plugin (>=1.2.4,<2.0)"]
-imaging = ["cairosvg (>=2.6,<3.0)", "pillow (>=10.2,<11.0)"]
-recommended = ["mkdocs-minify-plugin (>=0.7,<1.0)", "mkdocs-redirects (>=1.2,<2.0)", "mkdocs-rss-plugin (>=1.6,<2.0)"]
-
-[[package]]
-name = "mkdocs-material-extensions"
-version = "1.3.1"
-description = "Extension pack for Python Markdown and MkDocs Material."
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "mkdocs_material_extensions-1.3.1-py3-none-any.whl", hash = "sha256:adff8b62700b25cb77b53358dad940f3ef973dd6db797907c49e3c2ef3ab4e31"},
-    {file = "mkdocs_material_extensions-1.3.1.tar.gz", hash = "sha256:10c9511cea88f568257f960358a467d12b970e1f7b2c0e5fb2bb48cab1928443"},
-]
-
-[[package]]
-name = "mypy-extensions"
-version = "1.0.0"
-description = "Type system extensions for programs checked with the mypy type checker."
-optional = false
-python-versions = ">=3.5"
-files = [
-    {file = "mypy_extensions-1.0.0-py3-none-any.whl", hash = "sha256:4392f6c0eb8a5668a69e23d168ffa70f0be9ccfd32b5cc2d26a34ae5b844552d"},
-    {file = "mypy_extensions-1.0.0.tar.gz", hash = "sha256:75dbf8955dc00442a438fc4d0666508a9a97b6bd41aa2f0ffe9d2f2725af0782"},
-]
-
-[[package]]
-name = "nose"
-version = "1.3.7"
-description = "nose extends unittest to make testing easier"
-optional = false
-python-versions = "*"
-files = [
-    {file = "nose-1.3.7-py2-none-any.whl", hash = "sha256:dadcddc0aefbf99eea214e0f1232b94f2fa9bd98fa8353711dacb112bfcbbb2a"},
-    {file = "nose-1.3.7-py3-none-any.whl", hash = "sha256:9ff7c6cc443f8c51994b34a667bbcf45afd6d945be7477b52e97516fd17c53ac"},
-    {file = "nose-1.3.7.tar.gz", hash = "sha256:f1bffef9cbc82628f6e7d7b40d7e255aefaa1adb6a1b1d26c69a8b79e6208a98"},
-]
-
-[[package]]
-name = "packaging"
-version = "23.2"
-description = "Core utilities for Python packages"
-optional = false
-python-versions = ">=3.7"
-files = [
-    {file = "packaging-23.2-py3-none-any.whl", hash = "sha256:8c491190033a9af7e1d931d0b5dacc2ef47509b34dd0de67ed209b5203fc88c7"},
-    {file = "packaging-23.2.tar.gz", hash = "sha256:048fb0e9405036518eaaf48a55953c750c11e1a1b68e0dd1a9d62ed0c092cfc5"},
-]
-
-[[package]]
-name = "paginate"
-version = "0.5.6"
-description = "Divides large result sets into pages for easier browsing"
-optional = false
-python-versions = "*"
-files = [
-    {file = "paginate-0.5.6.tar.gz", hash = "sha256:5e6007b6a9398177a7e1648d04fdd9f8c9766a1a945bceac82f1929e8c78af2d"},
-]
-
-[[package]]
-name = "pathspec"
-version = "0.12.1"
-description = "Utility library for gitignore style pattern matching of file paths."
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "pathspec-0.12.1-py3-none-any.whl", hash = "sha256:a0d503e138a4c123b27490a4f7beda6a01c6f288df0e4a8b79c7eb0dc7b4cc08"},
-    {file = "pathspec-0.12.1.tar.gz", hash = "sha256:a482d51503a1ab33b1c67a6c3813a26953dbdc71c31dacaef9a838c4e29f5712"},
-]
-
-[[package]]
-name = "pip"
-version = "24.0"
-description = "The PyPA recommended tool for installing Python packages."
-optional = false
-python-versions = ">=3.7"
-files = [
-    {file = "pip-24.0-py3-none-any.whl", hash = "sha256:ba0d021a166865d2265246961bec0152ff124de910c5cc39f1156ce3fa7c69dc"},
-    {file = "pip-24.0.tar.gz", hash = "sha256:ea9bd1a847e8c5774a5777bb398c19e80bcd4e2aa16a4b301b718fe6f593aba2"},
-]
-
-[[package]]
-name = "platformdirs"
-version = "4.2.0"
-description = "A small Python package for determining appropriate platform-specific dirs, e.g. a \"user data dir\"."
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "platformdirs-4.2.0-py3-none-any.whl", hash = "sha256:0614df2a2f37e1a662acbd8e2b25b92ccf8632929bc6d43467e17fe89c75e068"},
-    {file = "platformdirs-4.2.0.tar.gz", hash = "sha256:ef0cc731df711022c174543cb70a9b5bd22e5a9337c8624ef2c2ceb8ddad8768"},
-]
-
-[package.extras]
-docs = ["furo (>=2023.9.10)", "proselint (>=0.13)", "sphinx (>=7.2.6)", "sphinx-autodoc-typehints (>=1.25.2)"]
-test = ["appdirs (==1.4.4)", "covdefaults (>=2.3)", "pytest (>=7.4.3)", "pytest-cov (>=4.1)", "pytest-mock (>=3.12)"]
-
-[[package]]
-name = "pycodestyle"
-version = "2.11.1"
-description = "Python style guide checker"
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "pycodestyle-2.11.1-py2.py3-none-any.whl", hash = "sha256:44fe31000b2d866f2e41841b18528a505fbd7fef9017b04eff4e2648a0fadc67"},
-    {file = "pycodestyle-2.11.1.tar.gz", hash = "sha256:41ba0e7afc9752dfb53ced5489e89f8186be00e599e712660695b7a75ff2663f"},
-]
-
-[[package]]
-name = "pyflakes"
-version = "3.2.0"
-description = "passive checker of Python programs"
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "pyflakes-3.2.0-py2.py3-none-any.whl", hash = "sha256:84b5be138a2dfbb40689ca07e2152deb896a65c3a3e24c251c5c62489568074a"},
-    {file = "pyflakes-3.2.0.tar.gz", hash = "sha256:1c61603ff154621fb2a9172037d84dca3500def8c8b630657d1701f026f8af3f"},
-]
-
-[[package]]
-name = "pygments"
-version = "2.17.2"
-description = "Pygments is a syntax highlighting package written in Python."
-optional = false
-python-versions = ">=3.7"
-files = [
-    {file = "pygments-2.17.2-py3-none-any.whl", hash = "sha256:b27c2826c47d0f3219f29554824c30c5e8945175d888647acd804ddd04af846c"},
-    {file = "pygments-2.17.2.tar.gz", hash = "sha256:da46cec9fd2de5be3a8a784f434e4c4ab670b4ff54d605c4c2717e9d49c4c367"},
-]
-
-[package.extras]
-plugins = ["importlib-metadata"]
-windows-terminal = ["colorama (>=0.4.6)"]
-
-[[package]]
-name = "pymdown-extensions"
-version = "10.7"
-description = "Extension pack for Python Markdown."
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "pymdown_extensions-10.7-py3-none-any.whl", hash = "sha256:6ca215bc57bc12bf32b414887a68b810637d039124ed9b2e5bd3325cbb2c050c"},
-    {file = "pymdown_extensions-10.7.tar.gz", hash = "sha256:c0d64d5cf62566f59e6b2b690a4095c931107c250a8c8e1351c1de5f6b036deb"},
-]
-
-[package.dependencies]
-markdown = ">=3.5"
-pyyaml = "*"
-
-[package.extras]
-extra = ["pygments (>=2.12)"]
-
-[[package]]
-name = "python-dateutil"
-version = "2.9.0.post0"
-description = "Extensions to the standard Python datetime module"
-optional = false
-python-versions = "!=3.0.*,!=3.1.*,!=3.2.*,>=2.7"
-files = [
-    {file = "python-dateutil-2.9.0.post0.tar.gz", hash = "sha256:37dd54208da7e1cd875388217d5e00ebd4179249f90fb72437e91a35459a0ad3"},
-    {file = "python_dateutil-2.9.0.post0-py2.py3-none-any.whl", hash = "sha256:a8b2bc7bffae282281c8140a97d3aa9c14da0b136dfe83f850eea9a5f7470427"},
-]
-
-[package.dependencies]
-six = ">=1.5"
-
-[[package]]
-name = "python-dotenv"
-version = "1.0.1"
-description = "Read key-value pairs from a .env file and set them as environment variables"
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "python-dotenv-1.0.1.tar.gz", hash = "sha256:e324ee90a023d808f1959c46bcbc04446a10ced277783dc6ee09987c37ec10ca"},
-    {file = "python_dotenv-1.0.1-py3-none-any.whl", hash = "sha256:f7b63ef50f1b690dddf550d03497b66d609393b40b564ed0d674909a68ebf16a"},
-]
-
-[package.extras]
-cli = ["click (>=5.0)"]
-
-[[package]]
-name = "pyyaml"
-version = "6.0.1"
-description = "YAML parser and emitter for Python"
-optional = false
-python-versions = ">=3.6"
-files = [
-    {file = "PyYAML-6.0.1-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:d858aa552c999bc8a8d57426ed01e40bef403cd8ccdd0fc5f6f04a00414cac2a"},
-    {file = "PyYAML-6.0.1-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:fd66fc5d0da6d9815ba2cebeb4205f95818ff4b79c3ebe268e75d961704af52f"},
-    {file = "PyYAML-6.0.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:69b023b2b4daa7548bcfbd4aa3da05b3a74b772db9e23b982788168117739938"},
-    {file = "PyYAML-6.0.1-cp310-cp310-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:81e0b275a9ecc9c0c0c07b4b90ba548307583c125f54d5b6946cfee6360c733d"},
-    {file = "PyYAML-6.0.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:ba336e390cd8e4d1739f42dfe9bb83a3cc2e80f567d8805e11b46f4a943f5515"},
-    {file = "PyYAML-6.0.1-cp310-cp310-musllinux_1_1_x86_64.whl", hash = "sha256:326c013efe8048858a6d312ddd31d56e468118ad4cdeda36c719bf5bb6192290"},
-    {file = "PyYAML-6.0.1-cp310-cp310-win32.whl", hash = "sha256:bd4af7373a854424dabd882decdc5579653d7868b8fb26dc7d0e99f823aa5924"},
-    {file = "PyYAML-6.0.1-cp310-cp310-win_amd64.whl", hash = "sha256:fd1592b3fdf65fff2ad0004b5e363300ef59ced41c2e6b3a99d4089fa8c5435d"},
-    {file = "PyYAML-6.0.1-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:6965a7bc3cf88e5a1c3bd2e0b5c22f8d677dc88a455344035f03399034eb3007"},
-    {file = "PyYAML-6.0.1-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:f003ed9ad21d6a4713f0a9b5a7a0a79e08dd0f221aff4525a2be4c346ee60aab"},
-    {file = "PyYAML-6.0.1-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:42f8152b8dbc4fe7d96729ec2b99c7097d656dc1213a3229ca5383f973a5ed6d"},
-    {file = "PyYAML-6.0.1-cp311-cp311-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:062582fca9fabdd2c8b54a3ef1c978d786e0f6b3a1510e0ac93ef59e0ddae2bc"},
-    {file = "PyYAML-6.0.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:d2b04aac4d386b172d5b9692e2d2da8de7bfb6c387fa4f801fbf6fb2e6ba4673"},
-    {file = "PyYAML-6.0.1-cp311-cp311-musllinux_1_1_x86_64.whl", hash = "sha256:e7d73685e87afe9f3b36c799222440d6cf362062f78be1013661b00c5c6f678b"},
-    {file = "PyYAML-6.0.1-cp311-cp311-win32.whl", hash = "sha256:1635fd110e8d85d55237ab316b5b011de701ea0f29d07611174a1b42f1444741"},
-    {file = "PyYAML-6.0.1-cp311-cp311-win_amd64.whl", hash = "sha256:bf07ee2fef7014951eeb99f56f39c9bb4af143d8aa3c21b1677805985307da34"},
-    {file = "PyYAML-6.0.1-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:855fb52b0dc35af121542a76b9a84f8d1cd886ea97c84703eaa6d88e37a2ad28"},
-    {file = "PyYAML-6.0.1-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:40df9b996c2b73138957fe23a16a4f0ba614f4c0efce1e9406a184b6d07fa3a9"},
-    {file = "PyYAML-6.0.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:a08c6f0fe150303c1c6b71ebcd7213c2858041a7e01975da3a99aed1e7a378ef"},
-    {file = "PyYAML-6.0.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:6c22bec3fbe2524cde73d7ada88f6566758a8f7227bfbf93a408a9d86bcc12a0"},
-    {file = "PyYAML-6.0.1-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:8d4e9c88387b0f5c7d5f281e55304de64cf7f9c0021a3525bd3b1c542da3b0e4"},
-    {file = "PyYAML-6.0.1-cp312-cp312-win32.whl", hash = "sha256:d483d2cdf104e7c9fa60c544d92981f12ad66a457afae824d146093b8c294c54"},
-    {file = "PyYAML-6.0.1-cp312-cp312-win_amd64.whl", hash = "sha256:0d3304d8c0adc42be59c5f8a4d9e3d7379e6955ad754aa9d6ab7a398b59dd1df"},
-    {file = "PyYAML-6.0.1-cp36-cp36m-macosx_10_9_x86_64.whl", hash = "sha256:50550eb667afee136e9a77d6dc71ae76a44df8b3e51e41b77f6de2932bfe0f47"},
-    {file = "PyYAML-6.0.1-cp36-cp36m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:1fe35611261b29bd1de0070f0b2f47cb6ff71fa6595c077e42bd0c419fa27b98"},
-    {file = "PyYAML-6.0.1-cp36-cp36m-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:704219a11b772aea0d8ecd7058d0082713c3562b4e271b849ad7dc4a5c90c13c"},
-    {file = "PyYAML-6.0.1-cp36-cp36m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:afd7e57eddb1a54f0f1a974bc4391af8bcce0b444685d936840f125cf046d5bd"},
-    {file = "PyYAML-6.0.1-cp36-cp36m-win32.whl", hash = "sha256:fca0e3a251908a499833aa292323f32437106001d436eca0e6e7833256674585"},
-    {file = "PyYAML-6.0.1-cp36-cp36m-win_amd64.whl", hash = "sha256:f22ac1c3cac4dbc50079e965eba2c1058622631e526bd9afd45fedd49ba781fa"},
-    {file = "PyYAML-6.0.1-cp37-cp37m-macosx_10_9_x86_64.whl", hash = "sha256:b1275ad35a5d18c62a7220633c913e1b42d44b46ee12554e5fd39c70a243d6a3"},
-    {file = "PyYAML-6.0.1-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:18aeb1bf9a78867dc38b259769503436b7c72f7a1f1f4c93ff9a17de54319b27"},
-    {file = "PyYAML-6.0.1-cp37-cp37m-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:596106435fa6ad000c2991a98fa58eeb8656ef2325d7e158344fb33864ed87e3"},
-    {file = "PyYAML-6.0.1-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:baa90d3f661d43131ca170712d903e6295d1f7a0f595074f151c0aed377c9b9c"},
-    {file = "PyYAML-6.0.1-cp37-cp37m-win32.whl", hash = "sha256:9046c58c4395dff28dd494285c82ba00b546adfc7ef001486fbf0324bc174fba"},
-    {file = "PyYAML-6.0.1-cp37-cp37m-win_amd64.whl", hash = "sha256:4fb147e7a67ef577a588a0e2c17b6db51dda102c71de36f8549b6816a96e1867"},
-    {file = "PyYAML-6.0.1-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:1d4c7e777c441b20e32f52bd377e0c409713e8bb1386e1099c2415f26e479595"},
-    {file = "PyYAML-6.0.1-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:a0cd17c15d3bb3fa06978b4e8958dcdc6e0174ccea823003a106c7d4d7899ac5"},
-    {file = "PyYAML-6.0.1-cp38-cp38-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:28c119d996beec18c05208a8bd78cbe4007878c6dd15091efb73a30e90539696"},
-    {file = "PyYAML-6.0.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:7e07cbde391ba96ab58e532ff4803f79c4129397514e1413a7dc761ccd755735"},
-    {file = "PyYAML-6.0.1-cp38-cp38-musllinux_1_1_x86_64.whl", hash = "sha256:49a183be227561de579b4a36efbb21b3eab9651dd81b1858589f796549873dd6"},
-    {file = "PyYAML-6.0.1-cp38-cp38-win32.whl", hash = "sha256:184c5108a2aca3c5b3d3bf9395d50893a7ab82a38004c8f61c258d4428e80206"},
-    {file = "PyYAML-6.0.1-cp38-cp38-win_amd64.whl", hash = "sha256:1e2722cc9fbb45d9b87631ac70924c11d3a401b2d7f410cc0e3bbf249f2dca62"},
-    {file = "PyYAML-6.0.1-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:9eb6caa9a297fc2c2fb8862bc5370d0303ddba53ba97e71f08023b6cd73d16a8"},
-    {file = "PyYAML-6.0.1-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:c8098ddcc2a85b61647b2590f825f3db38891662cfc2fc776415143f599bb859"},
-    {file = "PyYAML-6.0.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:5773183b6446b2c99bb77e77595dd486303b4faab2b086e7b17bc6bef28865f6"},
-    {file = "PyYAML-6.0.1-cp39-cp39-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:b786eecbdf8499b9ca1d697215862083bd6d2a99965554781d0d8d1ad31e13a0"},
-    {file = "PyYAML-6.0.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:bc1bf2925a1ecd43da378f4db9e4f799775d6367bdb94671027b73b393a7c42c"},
-    {file = "PyYAML-6.0.1-cp39-cp39-musllinux_1_1_x86_64.whl", hash = "sha256:04ac92ad1925b2cff1db0cfebffb6ffc43457495c9b3c39d3fcae417d7125dc5"},
-    {file = "PyYAML-6.0.1-cp39-cp39-win32.whl", hash = "sha256:faca3bdcf85b2fc05d06ff3fbc1f83e1391b3e724afa3feba7d13eeab355484c"},
-    {file = "PyYAML-6.0.1-cp39-cp39-win_amd64.whl", hash = "sha256:510c9deebc5c0225e8c96813043e62b680ba2f9c50a08d3724c7f28a747d1486"},
-    {file = "PyYAML-6.0.1.tar.gz", hash = "sha256:bfdf460b1736c775f2ba9f6a92bca30bc2095067b8a9d77876d1fad6cc3b4a43"},
-]
-
-[[package]]
-name = "pyyaml-env-tag"
-version = "0.1"
-description = "A custom YAML tag for referencing environment variables in YAML files. "
-optional = false
-python-versions = ">=3.6"
-files = [
-    {file = "pyyaml_env_tag-0.1-py3-none-any.whl", hash = "sha256:af31106dec8a4d68c60207c1886031cbf839b68aa7abccdb19868200532c2069"},
-    {file = "pyyaml_env_tag-0.1.tar.gz", hash = "sha256:70092675bda14fdec33b31ba77e7543de9ddc88f2e5b99160396572d11525bdb"},
-]
-
-[package.dependencies]
-pyyaml = "*"
-
-[[package]]
-name = "regex"
-version = "2023.12.25"
-description = "Alternative regular expression module, to replace re."
-optional = false
-python-versions = ">=3.7"
-files = [
-    {file = "regex-2023.12.25-cp310-cp310-macosx_10_9_universal2.whl", hash = "sha256:0694219a1d54336fd0445ea382d49d36882415c0134ee1e8332afd1529f0baa5"},
-    {file = "regex-2023.12.25-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:b014333bd0217ad3d54c143de9d4b9a3ca1c5a29a6d0d554952ea071cff0f1f8"},
-    {file = "regex-2023.12.25-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:d865984b3f71f6d0af64d0d88f5733521698f6c16f445bb09ce746c92c97c586"},
-    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:1e0eabac536b4cc7f57a5f3d095bfa557860ab912f25965e08fe1545e2ed8b4c"},
-    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:c25a8ad70e716f96e13a637802813f65d8a6760ef48672aa3502f4c24ea8b400"},
-    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:a9b6d73353f777630626f403b0652055ebfe8ff142a44ec2cf18ae470395766e"},
-    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:a9cc99d6946d750eb75827cb53c4371b8b0fe89c733a94b1573c9dd16ea6c9e4"},
-    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:88d1f7bef20c721359d8675f7d9f8e414ec5003d8f642fdfd8087777ff7f94b5"},
-    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl", hash = "sha256:cb3fe77aec8f1995611f966d0c656fdce398317f850d0e6e7aebdfe61f40e1cd"},
-    {file = "regex-2023.12.25-cp310-cp310-musllinux_1_1_aarch64.whl", hash = "sha256:7aa47c2e9ea33a4a2a05f40fcd3ea36d73853a2aae7b4feab6fc85f8bf2c9704"},
-    {file = "regex-2023.12.25-cp310-cp310-musllinux_1_1_i686.whl", hash = "sha256:df26481f0c7a3f8739fecb3e81bc9da3fcfae34d6c094563b9d4670b047312e1"},
-    {file = "regex-2023.12.25-cp310-cp310-musllinux_1_1_ppc64le.whl", hash = "sha256:c40281f7d70baf6e0db0c2f7472b31609f5bc2748fe7275ea65a0b4601d9b392"},
-    {file = "regex-2023.12.25-cp310-cp310-musllinux_1_1_s390x.whl", hash = "sha256:d94a1db462d5690ebf6ae86d11c5e420042b9898af5dcf278bd97d6bda065423"},
-    {file = "regex-2023.12.25-cp310-cp310-musllinux_1_1_x86_64.whl", hash = "sha256:ba1b30765a55acf15dce3f364e4928b80858fa8f979ad41f862358939bdd1f2f"},
-    {file = "regex-2023.12.25-cp310-cp310-win32.whl", hash = "sha256:150c39f5b964e4d7dba46a7962a088fbc91f06e606f023ce57bb347a3b2d4630"},
-    {file = "regex-2023.12.25-cp310-cp310-win_amd64.whl", hash = "sha256:09da66917262d9481c719599116c7dc0c321ffcec4b1f510c4f8a066f8768105"},
-    {file = "regex-2023.12.25-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:1b9d811f72210fa9306aeb88385b8f8bcef0dfbf3873410413c00aa94c56c2b6"},
-    {file = "regex-2023.12.25-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:d902a43085a308cef32c0d3aea962524b725403fd9373dea18110904003bac97"},
-    {file = "regex-2023.12.25-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:d166eafc19f4718df38887b2bbe1467a4f74a9830e8605089ea7a30dd4da8887"},
-    {file = "regex-2023.12.25-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:c7ad32824b7f02bb3c9f80306d405a1d9b7bb89362d68b3c5a9be53836caebdb"},
-    {file = "regex-2023.12.25-cp311-cp311-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:636ba0a77de609d6510235b7f0e77ec494d2657108f777e8765efc060094c98c"},
-    {file = "regex-2023.12.25-cp311-cp311-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:0fda75704357805eb953a3ee15a2b240694a9a514548cd49b3c5124b4e2ad01b"},
-    {file = "regex-2023.12.25-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:f72cbae7f6b01591f90814250e636065850c5926751af02bb48da94dfced7baa"},
-    {file = "regex-2023.12.25-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:db2a0b1857f18b11e3b0e54ddfefc96af46b0896fb678c85f63fb8c37518b3e7"},
-    {file = "regex-2023.12.25-cp311-cp311-musllinux_1_1_aarch64.whl", hash = "sha256:7502534e55c7c36c0978c91ba6f61703faf7ce733715ca48f499d3dbbd7657e0"},
-    {file = "regex-2023.12.25-cp311-cp311-musllinux_1_1_i686.whl", hash = "sha256:e8c7e08bb566de4faaf11984af13f6bcf6a08f327b13631d41d62592681d24fe"},
-    {file = "regex-2023.12.25-cp311-cp311-musllinux_1_1_ppc64le.whl", hash = "sha256:283fc8eed679758de38fe493b7d7d84a198b558942b03f017b1f94dda8efae80"},
-    {file = "regex-2023.12.25-cp311-cp311-musllinux_1_1_s390x.whl", hash = "sha256:f44dd4d68697559d007462b0a3a1d9acd61d97072b71f6d1968daef26bc744bd"},
-    {file = "regex-2023.12.25-cp311-cp311-musllinux_1_1_x86_64.whl", hash = "sha256:67d3ccfc590e5e7197750fcb3a2915b416a53e2de847a728cfa60141054123d4"},
-    {file = "regex-2023.12.25-cp311-cp311-win32.whl", hash = "sha256:68191f80a9bad283432385961d9efe09d783bcd36ed35a60fb1ff3f1ec2efe87"},
-    {file = "regex-2023.12.25-cp311-cp311-win_amd64.whl", hash = "sha256:7d2af3f6b8419661a0c421584cfe8aaec1c0e435ce7e47ee2a97e344b98f794f"},
-    {file = "regex-2023.12.25-cp312-cp312-macosx_10_9_universal2.whl", hash = "sha256:8a0ccf52bb37d1a700375a6b395bff5dd15c50acb745f7db30415bae3c2b0715"},
-    {file = "regex-2023.12.25-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:c3c4a78615b7762740531c27cf46e2f388d8d727d0c0c739e72048beb26c8a9d"},
-    {file = "regex-2023.12.25-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:ad83e7545b4ab69216cef4cc47e344d19622e28aabec61574b20257c65466d6a"},
-    {file = "regex-2023.12.25-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:b7a635871143661feccce3979e1727c4e094f2bdfd3ec4b90dfd4f16f571a87a"},
-    {file = "regex-2023.12.25-cp312-cp312-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:d498eea3f581fbe1b34b59c697512a8baef88212f92e4c7830fcc1499f5b45a5"},
-    {file = "regex-2023.12.25-cp312-cp312-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:43f7cd5754d02a56ae4ebb91b33461dc67be8e3e0153f593c509e21d219c5060"},
-    {file = "regex-2023.12.25-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:51f4b32f793812714fd5307222a7f77e739b9bc566dc94a18126aba3b92b98a3"},
-    {file = "regex-2023.12.25-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:ba99d8077424501b9616b43a2d208095746fb1284fc5ba490139651f971d39d9"},
-    {file = "regex-2023.12.25-cp312-cp312-musllinux_1_1_aarch64.whl", hash = "sha256:4bfc2b16e3ba8850e0e262467275dd4d62f0d045e0e9eda2bc65078c0110a11f"},
-    {file = "regex-2023.12.25-cp312-cp312-musllinux_1_1_i686.whl", hash = "sha256:8c2c19dae8a3eb0ea45a8448356ed561be843b13cbc34b840922ddf565498c1c"},
-    {file = "regex-2023.12.25-cp312-cp312-musllinux_1_1_ppc64le.whl", hash = "sha256:60080bb3d8617d96f0fb7e19796384cc2467447ef1c491694850ebd3670bc457"},
-    {file = "regex-2023.12.25-cp312-cp312-musllinux_1_1_s390x.whl", hash = "sha256:b77e27b79448e34c2c51c09836033056a0547aa360c45eeeb67803da7b0eedaf"},
-    {file = "regex-2023.12.25-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:518440c991f514331f4850a63560321f833979d145d7d81186dbe2f19e27ae3d"},
-    {file = "regex-2023.12.25-cp312-cp312-win32.whl", hash = "sha256:e2610e9406d3b0073636a3a2e80db05a02f0c3169b5632022b4e81c0364bcda5"},
-    {file = "regex-2023.12.25-cp312-cp312-win_amd64.whl", hash = "sha256:cc37b9aeebab425f11f27e5e9e6cf580be7206c6582a64467a14dda211abc232"},
-    {file = "regex-2023.12.25-cp37-cp37m-macosx_10_9_x86_64.whl", hash = "sha256:da695d75ac97cb1cd725adac136d25ca687da4536154cdc2815f576e4da11c69"},
-    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:d126361607b33c4eb7b36debc173bf25d7805847346dd4d99b5499e1fef52bc7"},
-    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:4719bb05094d7d8563a450cf8738d2e1061420f79cfcc1fa7f0a44744c4d8f73"},
-    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:5dd58946bce44b53b06d94aa95560d0b243eb2fe64227cba50017a8d8b3cd3e2"},
-    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:22a86d9fff2009302c440b9d799ef2fe322416d2d58fc124b926aa89365ec482"},
-    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:2aae8101919e8aa05ecfe6322b278f41ce2994c4a430303c4cd163fef746e04f"},
-    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl", hash = "sha256:e692296c4cc2873967771345a876bcfc1c547e8dd695c6b89342488b0ea55cd8"},
-    {file = "regex-2023.12.25-cp37-cp37m-musllinux_1_1_aarch64.whl", hash = "sha256:263ef5cc10979837f243950637fffb06e8daed7f1ac1e39d5910fd29929e489a"},
-    {file = "regex-2023.12.25-cp37-cp37m-musllinux_1_1_i686.whl", hash = "sha256:d6f7e255e5fa94642a0724e35406e6cb7001c09d476ab5fce002f652b36d0c39"},
-    {file = "regex-2023.12.25-cp37-cp37m-musllinux_1_1_ppc64le.whl", hash = "sha256:88ad44e220e22b63b0f8f81f007e8abbb92874d8ced66f32571ef8beb0643b2b"},
-    {file = "regex-2023.12.25-cp37-cp37m-musllinux_1_1_s390x.whl", hash = "sha256:3a17d3ede18f9cedcbe23d2daa8a2cd6f59fe2bf082c567e43083bba3fb00347"},
-    {file = "regex-2023.12.25-cp37-cp37m-musllinux_1_1_x86_64.whl", hash = "sha256:d15b274f9e15b1a0b7a45d2ac86d1f634d983ca40d6b886721626c47a400bf39"},
-    {file = "regex-2023.12.25-cp37-cp37m-win32.whl", hash = "sha256:ed19b3a05ae0c97dd8f75a5d8f21f7723a8c33bbc555da6bbe1f96c470139d3c"},
-    {file = "regex-2023.12.25-cp37-cp37m-win_amd64.whl", hash = "sha256:a6d1047952c0b8104a1d371f88f4ab62e6275567d4458c1e26e9627ad489b445"},
-    {file = "regex-2023.12.25-cp38-cp38-macosx_10_9_universal2.whl", hash = "sha256:b43523d7bc2abd757119dbfb38af91b5735eea45537ec6ec3a5ec3f9562a1c53"},
-    {file = "regex-2023.12.25-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:efb2d82f33b2212898f1659fb1c2e9ac30493ac41e4d53123da374c3b5541e64"},
-    {file = "regex-2023.12.25-cp38-cp38-macosx_11_0_arm64.whl", hash = "sha256:b7fca9205b59c1a3d5031f7e64ed627a1074730a51c2a80e97653e3e9fa0d415"},
-    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:086dd15e9435b393ae06f96ab69ab2d333f5d65cbe65ca5a3ef0ec9564dfe770"},
-    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:e81469f7d01efed9b53740aedd26085f20d49da65f9c1f41e822a33992cb1590"},
-    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:34e4af5b27232f68042aa40a91c3b9bb4da0eeb31b7632e0091afc4310afe6cb"},
-    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:9852b76ab558e45b20bf1893b59af64a28bd3820b0c2efc80e0a70a4a3ea51c1"},
-    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:ff100b203092af77d1a5a7abe085b3506b7eaaf9abf65b73b7d6905b6cb76988"},
-    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl", hash = "sha256:cc038b2d8b1470364b1888a98fd22d616fba2b6309c5b5f181ad4483e0017861"},
-    {file = "regex-2023.12.25-cp38-cp38-musllinux_1_1_aarch64.whl", hash = "sha256:094ba386bb5c01e54e14434d4caabf6583334090865b23ef58e0424a6286d3dc"},
-    {file = "regex-2023.12.25-cp38-cp38-musllinux_1_1_i686.whl", hash = "sha256:5cd05d0f57846d8ba4b71d9c00f6f37d6b97d5e5ef8b3c3840426a475c8f70f4"},
-    {file = "regex-2023.12.25-cp38-cp38-musllinux_1_1_ppc64le.whl", hash = "sha256:9aa1a67bbf0f957bbe096375887b2505f5d8ae16bf04488e8b0f334c36e31360"},
-    {file = "regex-2023.12.25-cp38-cp38-musllinux_1_1_s390x.whl", hash = "sha256:98a2636994f943b871786c9e82bfe7883ecdaba2ef5df54e1450fa9869d1f756"},
-    {file = "regex-2023.12.25-cp38-cp38-musllinux_1_1_x86_64.whl", hash = "sha256:37f8e93a81fc5e5bd8db7e10e62dc64261bcd88f8d7e6640aaebe9bc180d9ce2"},
-    {file = "regex-2023.12.25-cp38-cp38-win32.whl", hash = "sha256:d78bd484930c1da2b9679290a41cdb25cc127d783768a0369d6b449e72f88beb"},
-    {file = "regex-2023.12.25-cp38-cp38-win_amd64.whl", hash = "sha256:b521dcecebc5b978b447f0f69b5b7f3840eac454862270406a39837ffae4e697"},
-    {file = "regex-2023.12.25-cp39-cp39-macosx_10_9_universal2.whl", hash = "sha256:f7bc09bc9c29ebead055bcba136a67378f03d66bf359e87d0f7c759d6d4ffa31"},
-    {file = "regex-2023.12.25-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:e14b73607d6231f3cc4622809c196b540a6a44e903bcfad940779c80dffa7be7"},
-    {file = "regex-2023.12.25-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:9eda5f7a50141291beda3edd00abc2d4a5b16c29c92daf8d5bd76934150f3edc"},
-    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:cc6bb9aa69aacf0f6032c307da718f61a40cf970849e471254e0e91c56ffca95"},
-    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:298dc6354d414bc921581be85695d18912bea163a8b23cac9a2562bbcd5088b1"},
-    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:2f4e475a80ecbd15896a976aa0b386c5525d0ed34d5c600b6d3ebac0a67c7ddf"},
-    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:531ac6cf22b53e0696f8e1d56ce2396311254eb806111ddd3922c9d937151dae"},
-    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:22f3470f7524b6da61e2020672df2f3063676aff444db1daa283c2ea4ed259d6"},
-    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl", hash = "sha256:89723d2112697feaa320c9d351e5f5e7b841e83f8b143dba8e2d2b5f04e10923"},
-    {file = "regex-2023.12.25-cp39-cp39-musllinux_1_1_aarch64.whl", hash = "sha256:0ecf44ddf9171cd7566ef1768047f6e66975788258b1c6c6ca78098b95cf9a3d"},
-    {file = "regex-2023.12.25-cp39-cp39-musllinux_1_1_i686.whl", hash = "sha256:905466ad1702ed4acfd67a902af50b8db1feeb9781436372261808df7a2a7bca"},
-    {file = "regex-2023.12.25-cp39-cp39-musllinux_1_1_ppc64le.whl", hash = "sha256:4558410b7a5607a645e9804a3e9dd509af12fb72b9825b13791a37cd417d73a5"},
-    {file = "regex-2023.12.25-cp39-cp39-musllinux_1_1_s390x.whl", hash = "sha256:7e316026cc1095f2a3e8cc012822c99f413b702eaa2ca5408a513609488cb62f"},
-    {file = "regex-2023.12.25-cp39-cp39-musllinux_1_1_x86_64.whl", hash = "sha256:3b1de218d5375cd6ac4b5493e0b9f3df2be331e86520f23382f216c137913d20"},
-    {file = "regex-2023.12.25-cp39-cp39-win32.whl", hash = "sha256:11a963f8e25ab5c61348d090bf1b07f1953929c13bd2309a0662e9ff680763c9"},
-    {file = "regex-2023.12.25-cp39-cp39-win_amd64.whl", hash = "sha256:e693e233ac92ba83a87024e1d32b5f9ab15ca55ddd916d878146f4e3406b5c91"},
-    {file = "regex-2023.12.25.tar.gz", hash = "sha256:29171aa128da69afdf4bde412d5bedc335f2ca8fcfe4489038577d05f16181e5"},
-]
-
-[[package]]
-name = "requests"
-version = "2.31.0"
-description = "Python HTTP for Humans."
-optional = false
-python-versions = ">=3.7"
-files = [
-    {file = "requests-2.31.0-py3-none-any.whl", hash = "sha256:58cd2187c01e70e6e26505bca751777aa9f2ee0b7f4300988b709f44e013003f"},
-    {file = "requests-2.31.0.tar.gz", hash = "sha256:942c5a758f98d790eaed1a29cb6eefc7ffb0d1cf7af05c3d2791656dbd6ad1e1"},
-]
-
-[package.dependencies]
-certifi = ">=2017.4.17"
-charset-normalizer = ">=2,<4"
-idna = ">=2.5,<4"
-urllib3 = ">=1.21.1,<3"
-
-[package.extras]
-socks = ["PySocks (>=1.5.6,!=1.5.7)"]
-use-chardet-on-py3 = ["chardet (>=3.0.2,<6)"]
-
-[[package]]
-name = "six"
-version = "1.16.0"
-description = "Python 2 and 3 compatibility utilities"
-optional = false
-python-versions = ">=2.7, !=3.0.*, !=3.1.*, !=3.2.*"
-files = [
-    {file = "six-1.16.0-py2.py3-none-any.whl", hash = "sha256:8abb2f1d86890a2dfb989f9a77cfcfd3e47c2a354b01111771326f8aa26e0254"},
-    {file = "six-1.16.0.tar.gz", hash = "sha256:1e61c37477a1626458e36f7b1d82aa5c9b094fa4802892072e49de9c60c4c926"},
-]
-
-[[package]]
-name = "urllib3"
-version = "2.2.1"
-description = "HTTP library with thread-safe connection pooling, file post, and more."
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "urllib3-2.2.1-py3-none-any.whl", hash = "sha256:450b20ec296a467077128bff42b73080516e71b56ff59a60a02bef2232c4fa9d"},
-    {file = "urllib3-2.2.1.tar.gz", hash = "sha256:d0570876c61ab9e520d776c38acbbb5b05a776d3f9ff98a5c8fd5162a444cf19"},
-]
-
-[package.extras]
-brotli = ["brotli (>=1.0.9)", "brotlicffi (>=0.8.0)"]
-h2 = ["h2 (>=4,<5)"]
-socks = ["pysocks (>=1.5.6,!=1.5.7,<2.0)"]
-zstd = ["zstandard (>=0.18.0)"]
-
-[[package]]
-name = "watchdog"
-version = "4.0.0"
-description = "Filesystem events monitoring"
-optional = false
-python-versions = ">=3.8"
-files = [
-    {file = "watchdog-4.0.0-cp310-cp310-macosx_10_9_universal2.whl", hash = "sha256:39cb34b1f1afbf23e9562501673e7146777efe95da24fab5707b88f7fb11649b"},
-    {file = "watchdog-4.0.0-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:c522392acc5e962bcac3b22b9592493ffd06d1fc5d755954e6be9f4990de932b"},
-    {file = "watchdog-4.0.0-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:6c47bdd680009b11c9ac382163e05ca43baf4127954c5f6d0250e7d772d2b80c"},
-    {file = "watchdog-4.0.0-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:8350d4055505412a426b6ad8c521bc7d367d1637a762c70fdd93a3a0d595990b"},
-    {file = "watchdog-4.0.0-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:c17d98799f32e3f55f181f19dd2021d762eb38fdd381b4a748b9f5a36738e935"},
-    {file = "watchdog-4.0.0-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:4986db5e8880b0e6b7cd52ba36255d4793bf5cdc95bd6264806c233173b1ec0b"},
-    {file = "watchdog-4.0.0-cp312-cp312-macosx_10_9_universal2.whl", hash = "sha256:11e12fafb13372e18ca1bbf12d50f593e7280646687463dd47730fd4f4d5d257"},
-    {file = "watchdog-4.0.0-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:5369136a6474678e02426bd984466343924d1df8e2fd94a9b443cb7e3aa20d19"},
-    {file = "watchdog-4.0.0-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:76ad8484379695f3fe46228962017a7e1337e9acadafed67eb20aabb175df98b"},
-    {file = "watchdog-4.0.0-cp38-cp38-macosx_10_9_universal2.whl", hash = "sha256:45cc09cc4c3b43fb10b59ef4d07318d9a3ecdbff03abd2e36e77b6dd9f9a5c85"},
-    {file = "watchdog-4.0.0-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:eed82cdf79cd7f0232e2fdc1ad05b06a5e102a43e331f7d041e5f0e0a34a51c4"},
-    {file = "watchdog-4.0.0-cp38-cp38-macosx_11_0_arm64.whl", hash = "sha256:ba30a896166f0fee83183cec913298151b73164160d965af2e93a20bbd2ab605"},
-    {file = "watchdog-4.0.0-cp39-cp39-macosx_10_9_universal2.whl", hash = "sha256:d18d7f18a47de6863cd480734613502904611730f8def45fc52a5d97503e5101"},
-    {file = "watchdog-4.0.0-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:2895bf0518361a9728773083908801a376743bcc37dfa252b801af8fd281b1ca"},
-    {file = "watchdog-4.0.0-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:87e9df830022488e235dd601478c15ad73a0389628588ba0b028cb74eb72fed8"},
-    {file = "watchdog-4.0.0-pp310-pypy310_pp73-macosx_10_9_x86_64.whl", hash = "sha256:6e949a8a94186bced05b6508faa61b7adacc911115664ccb1923b9ad1f1ccf7b"},
-    {file = "watchdog-4.0.0-pp38-pypy38_pp73-macosx_10_9_x86_64.whl", hash = "sha256:6a4db54edea37d1058b08947c789a2354ee02972ed5d1e0dca9b0b820f4c7f92"},
-    {file = "watchdog-4.0.0-pp39-pypy39_pp73-macosx_10_9_x86_64.whl", hash = "sha256:d31481ccf4694a8416b681544c23bd271f5a123162ab603c7d7d2dd7dd901a07"},
-    {file = "watchdog-4.0.0-py3-none-manylinux2014_aarch64.whl", hash = "sha256:8fec441f5adcf81dd240a5fe78e3d83767999771630b5ddfc5867827a34fa3d3"},
-    {file = "watchdog-4.0.0-py3-none-manylinux2014_armv7l.whl", hash = "sha256:6a9c71a0b02985b4b0b6d14b875a6c86ddea2fdbebd0c9a720a806a8bbffc69f"},
-    {file = "watchdog-4.0.0-py3-none-manylinux2014_i686.whl", hash = "sha256:557ba04c816d23ce98a06e70af6abaa0485f6d94994ec78a42b05d1c03dcbd50"},
-    {file = "watchdog-4.0.0-py3-none-manylinux2014_ppc64.whl", hash = "sha256:d0f9bd1fd919134d459d8abf954f63886745f4660ef66480b9d753a7c9d40927"},
-    {file = "watchdog-4.0.0-py3-none-manylinux2014_ppc64le.whl", hash = "sha256:f9b2fdca47dc855516b2d66eef3c39f2672cbf7e7a42e7e67ad2cbfcd6ba107d"},
-    {file = "watchdog-4.0.0-py3-none-manylinux2014_s390x.whl", hash = "sha256:73c7a935e62033bd5e8f0da33a4dcb763da2361921a69a5a95aaf6c93aa03a87"},
-    {file = "watchdog-4.0.0-py3-none-manylinux2014_x86_64.whl", hash = "sha256:6a80d5cae8c265842c7419c560b9961561556c4361b297b4c431903f8c33b269"},
-    {file = "watchdog-4.0.0-py3-none-win32.whl", hash = "sha256:8f9a542c979df62098ae9c58b19e03ad3df1c9d8c6895d96c0d51da17b243b1c"},
-    {file = "watchdog-4.0.0-py3-none-win_amd64.whl", hash = "sha256:f970663fa4f7e80401a7b0cbeec00fa801bf0287d93d48368fc3e6fa32716245"},
-    {file = "watchdog-4.0.0-py3-none-win_ia64.whl", hash = "sha256:9a03e16e55465177d416699331b0f3564138f1807ecc5f2de9d55d8f188d08c7"},
-    {file = "watchdog-4.0.0.tar.gz", hash = "sha256:e3e7065cbdabe6183ab82199d7a4f6b3ba0a438c5a512a68559846ccb76a78ec"},
-]
-
-[package.extras]
-watchmedo = ["PyYAML (>=3.10)"]
-
-[metadata]
-lock-version = "2.0"
-python-versions = "^3.11"
-content-hash = "eb59b66f1230e1504b940568b5e30b8bd6b02c4a4cf458bf13275a3630115051"
+# This file is automatically @generated by Poetry 1.8.3 and should not be changed by hand.
+
+[[package]]
+name = "babel"
+version = "2.14.0"
+description = "Internationalization utilities"
+optional = false
+python-versions = ">=3.7"
+files = [
+    {file = "Babel-2.14.0-py3-none-any.whl", hash = "sha256:efb1a25b7118e67ce3a259bed20545c29cb68be8ad2c784c83689981b7a57287"},
+    {file = "Babel-2.14.0.tar.gz", hash = "sha256:6919867db036398ba21eb5c7a0f6b28ab8cbc3ae7a73a44ebe34ae74a4e7d363"},
+]
+
+[package.extras]
+dev = ["freezegun (>=1.0,<2.0)", "pytest (>=6.0)", "pytest-cov"]
+
+[[package]]
+name = "black"
+version = "24.2.0"
+description = "The uncompromising code formatter."
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "black-24.2.0-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:6981eae48b3b33399c8757036c7f5d48a535b962a7c2310d19361edeef64ce29"},
+    {file = "black-24.2.0-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:d533d5e3259720fdbc1b37444491b024003e012c5173f7d06825a77508085430"},
+    {file = "black-24.2.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:61a0391772490ddfb8a693c067df1ef5227257e72b0e4108482b8d41b5aee13f"},
+    {file = "black-24.2.0-cp310-cp310-win_amd64.whl", hash = "sha256:992e451b04667116680cb88f63449267c13e1ad134f30087dec8527242e9862a"},
+    {file = "black-24.2.0-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:163baf4ef40e6897a2a9b83890e59141cc8c2a98f2dda5080dc15c00ee1e62cd"},
+    {file = "black-24.2.0-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:e37c99f89929af50ffaf912454b3e3b47fd64109659026b678c091a4cd450fb2"},
+    {file = "black-24.2.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:4f9de21bafcba9683853f6c96c2d515e364aee631b178eaa5145fc1c61a3cc92"},
+    {file = "black-24.2.0-cp311-cp311-win_amd64.whl", hash = "sha256:9db528bccb9e8e20c08e716b3b09c6bdd64da0dd129b11e160bf082d4642ac23"},
+    {file = "black-24.2.0-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:d84f29eb3ee44859052073b7636533ec995bd0f64e2fb43aeceefc70090e752b"},
+    {file = "black-24.2.0-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:1e08fb9a15c914b81dd734ddd7fb10513016e5ce7e6704bdd5e1251ceee51ac9"},
+    {file = "black-24.2.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:810d445ae6069ce64030c78ff6127cd9cd178a9ac3361435708b907d8a04c693"},
+    {file = "black-24.2.0-cp312-cp312-win_amd64.whl", hash = "sha256:ba15742a13de85e9b8f3239c8f807723991fbfae24bad92d34a2b12e81904982"},
+    {file = "black-24.2.0-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:7e53a8c630f71db01b28cd9602a1ada68c937cbf2c333e6ed041390d6968faf4"},
+    {file = "black-24.2.0-cp38-cp38-macosx_11_0_arm64.whl", hash = "sha256:93601c2deb321b4bad8f95df408e3fb3943d85012dddb6121336b8e24a0d1218"},
+    {file = "black-24.2.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:a0057f800de6acc4407fe75bb147b0c2b5cbb7c3ed110d3e5999cd01184d53b0"},
+    {file = "black-24.2.0-cp38-cp38-win_amd64.whl", hash = "sha256:faf2ee02e6612577ba0181f4347bcbcf591eb122f7841ae5ba233d12c39dcb4d"},
+    {file = "black-24.2.0-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:057c3dc602eaa6fdc451069bd027a1b2635028b575a6c3acfd63193ced20d9c8"},
+    {file = "black-24.2.0-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:08654d0797e65f2423f850fc8e16a0ce50925f9337fb4a4a176a7aa4026e63f8"},
+    {file = "black-24.2.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:ca610d29415ee1a30a3f30fab7a8f4144e9d34c89a235d81292a1edb2b55f540"},
+    {file = "black-24.2.0-cp39-cp39-win_amd64.whl", hash = "sha256:4dd76e9468d5536abd40ffbc7a247f83b2324f0c050556d9c371c2b9a9a95e31"},
+    {file = "black-24.2.0-py3-none-any.whl", hash = "sha256:e8a6ae970537e67830776488bca52000eaa37fa63b9988e8c487458d9cd5ace6"},
+    {file = "black-24.2.0.tar.gz", hash = "sha256:bce4f25c27c3435e4dace4815bcb2008b87e167e3bf4ee47ccdc5ce906eb4894"},
+]
+
+[package.dependencies]
+click = ">=8.0.0"
+mypy-extensions = ">=0.4.3"
+packaging = ">=22.0"
+pathspec = ">=0.9.0"
+platformdirs = ">=2"
+
+[package.extras]
+colorama = ["colorama (>=0.4.3)"]
+d = ["aiohttp (>=3.7.4)", "aiohttp (>=3.7.4,!=3.9.0)"]
+jupyter = ["ipython (>=7.8.0)", "tokenize-rt (>=3.2.0)"]
+uvloop = ["uvloop (>=0.15.2)"]
+
+[[package]]
+name = "certifi"
+version = "2024.7.4"
+description = "Python package for providing Mozilla's CA Bundle."
+optional = false
+python-versions = ">=3.6"
+files = [
+    {file = "certifi-2024.7.4-py3-none-any.whl", hash = "sha256:c198e21b1289c2ab85ee4e67bb4b4ef3ead0892059901a8d5b622f24a1101e90"},
+    {file = "certifi-2024.7.4.tar.gz", hash = "sha256:5a1e7645bc0ec61a09e26c36f6106dd4cf40c6db3a1fb6352b0244e7fb057c7b"},
+]
+
+[[package]]
+name = "charset-normalizer"
+version = "3.3.2"
+description = "The Real First Universal Charset Detector. Open, modern and actively maintained alternative to Chardet."
+optional = false
+python-versions = ">=3.7.0"
+files = [
+    {file = "charset-normalizer-3.3.2.tar.gz", hash = "sha256:f30c3cb33b24454a82faecaf01b19c18562b1e89558fb6c56de4d9118a032fd5"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-macosx_10_9_universal2.whl", hash = "sha256:25baf083bf6f6b341f4121c2f3c548875ee6f5339300e08be3f2b2ba1721cdd3"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:06435b539f889b1f6f4ac1758871aae42dc3a8c0e24ac9e60c2384973ad73027"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:9063e24fdb1e498ab71cb7419e24622516c4a04476b17a2dab57e8baa30d6e03"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:6897af51655e3691ff853668779c7bad41579facacf5fd7253b0133308cf000d"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:1d3193f4a680c64b4b6a9115943538edb896edc190f0b222e73761716519268e"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:cd70574b12bb8a4d2aaa0094515df2463cb429d8536cfb6c7ce983246983e5a6"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:8465322196c8b4d7ab6d1e049e4c5cb460d0394da4a27d23cc242fbf0034b6b5"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:a9a8e9031d613fd2009c182b69c7b2c1ef8239a0efb1df3f7c8da66d5dd3d537"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-musllinux_1_1_aarch64.whl", hash = "sha256:beb58fe5cdb101e3a055192ac291b7a21e3b7ef4f67fa1d74e331a7f2124341c"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-musllinux_1_1_i686.whl", hash = "sha256:e06ed3eb3218bc64786f7db41917d4e686cc4856944f53d5bdf83a6884432e12"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-musllinux_1_1_ppc64le.whl", hash = "sha256:2e81c7b9c8979ce92ed306c249d46894776a909505d8f5a4ba55b14206e3222f"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-musllinux_1_1_s390x.whl", hash = "sha256:572c3763a264ba47b3cf708a44ce965d98555f618ca42c926a9c1616d8f34269"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-musllinux_1_1_x86_64.whl", hash = "sha256:fd1abc0d89e30cc4e02e4064dc67fcc51bd941eb395c502aac3ec19fab46b519"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-win32.whl", hash = "sha256:3d47fa203a7bd9c5b6cee4736ee84ca03b8ef23193c0d1ca99b5089f72645c73"},
+    {file = "charset_normalizer-3.3.2-cp310-cp310-win_amd64.whl", hash = "sha256:10955842570876604d404661fbccbc9c7e684caf432c09c715ec38fbae45ae09"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:802fe99cca7457642125a8a88a084cef28ff0cf9407060f7b93dca5aa25480db"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:573f6eac48f4769d667c4442081b1794f52919e7edada77495aaed9236d13a96"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:549a3a73da901d5bc3ce8d24e0600d1fa85524c10287f6004fbab87672bf3e1e"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:f27273b60488abe721a075bcca6d7f3964f9f6f067c8c4c605743023d7d3944f"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:1ceae2f17a9c33cb48e3263960dc5fc8005351ee19db217e9b1bb15d28c02574"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:65f6f63034100ead094b8744b3b97965785388f308a64cf8d7c34f2f2e5be0c4"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:753f10e867343b4511128c6ed8c82f7bec3bd026875576dfd88483c5c73b2fd8"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:4a78b2b446bd7c934f5dcedc588903fb2f5eec172f3d29e52a9096a43722adfc"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-musllinux_1_1_aarch64.whl", hash = "sha256:e537484df0d8f426ce2afb2d0f8e1c3d0b114b83f8850e5f2fbea0e797bd82ae"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-musllinux_1_1_i686.whl", hash = "sha256:eb6904c354526e758fda7167b33005998fb68c46fbc10e013ca97f21ca5c8887"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-musllinux_1_1_ppc64le.whl", hash = "sha256:deb6be0ac38ece9ba87dea880e438f25ca3eddfac8b002a2ec3d9183a454e8ae"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-musllinux_1_1_s390x.whl", hash = "sha256:4ab2fe47fae9e0f9dee8c04187ce5d09f48eabe611be8259444906793ab7cbce"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-musllinux_1_1_x86_64.whl", hash = "sha256:80402cd6ee291dcb72644d6eac93785fe2c8b9cb30893c1af5b8fdd753b9d40f"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-win32.whl", hash = "sha256:7cd13a2e3ddeed6913a65e66e94b51d80a041145a026c27e6bb76c31a853c6ab"},
+    {file = "charset_normalizer-3.3.2-cp311-cp311-win_amd64.whl", hash = "sha256:663946639d296df6a2bb2aa51b60a2454ca1cb29835324c640dafb5ff2131a77"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-macosx_10_9_universal2.whl", hash = "sha256:0b2b64d2bb6d3fb9112bafa732def486049e63de9618b5843bcdd081d8144cd8"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:ddbb2551d7e0102e7252db79ba445cdab71b26640817ab1e3e3648dad515003b"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:55086ee1064215781fff39a1af09518bc9255b50d6333f2e4c74ca09fac6a8f6"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:8f4a014bc36d3c57402e2977dada34f9c12300af536839dc38c0beab8878f38a"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:a10af20b82360ab00827f916a6058451b723b4e65030c5a18577c8b2de5b3389"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:8d756e44e94489e49571086ef83b2bb8ce311e730092d2c34ca8f7d925cb20aa"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:90d558489962fd4918143277a773316e56c72da56ec7aa3dc3dbbe20fdfed15b"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:6ac7ffc7ad6d040517be39eb591cac5ff87416c2537df6ba3cba3bae290c0fed"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-musllinux_1_1_aarch64.whl", hash = "sha256:7ed9e526742851e8d5cc9e6cf41427dfc6068d4f5a3bb03659444b4cabf6bc26"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-musllinux_1_1_i686.whl", hash = "sha256:8bdb58ff7ba23002a4c5808d608e4e6c687175724f54a5dade5fa8c67b604e4d"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-musllinux_1_1_ppc64le.whl", hash = "sha256:6b3251890fff30ee142c44144871185dbe13b11bab478a88887a639655be1068"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-musllinux_1_1_s390x.whl", hash = "sha256:b4a23f61ce87adf89be746c8a8974fe1c823c891d8f86eb218bb957c924bb143"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:efcb3f6676480691518c177e3b465bcddf57cea040302f9f4e6e191af91174d4"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-win32.whl", hash = "sha256:d965bba47ddeec8cd560687584e88cf699fd28f192ceb452d1d7ee807c5597b7"},
+    {file = "charset_normalizer-3.3.2-cp312-cp312-win_amd64.whl", hash = "sha256:96b02a3dc4381e5494fad39be677abcb5e6634bf7b4fa83a6dd3112607547001"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-macosx_10_9_x86_64.whl", hash = "sha256:95f2a5796329323b8f0512e09dbb7a1860c46a39da62ecb2324f116fa8fdc85c"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:c002b4ffc0be611f0d9da932eb0f704fe2602a9a949d1f738e4c34c75b0863d5"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:a981a536974bbc7a512cf44ed14938cf01030a99e9b3a06dd59578882f06f985"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:3287761bc4ee9e33561a7e058c72ac0938c4f57fe49a09eae428fd88aafe7bb6"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:42cb296636fcc8b0644486d15c12376cb9fa75443e00fb25de0b8602e64c1714"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:0a55554a2fa0d408816b3b5cedf0045f4b8e1a6065aec45849de2d6f3f8e9786"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-musllinux_1_1_aarch64.whl", hash = "sha256:c083af607d2515612056a31f0a8d9e0fcb5876b7bfc0abad3ecd275bc4ebc2d5"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-musllinux_1_1_i686.whl", hash = "sha256:87d1351268731db79e0f8e745d92493ee2841c974128ef629dc518b937d9194c"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-musllinux_1_1_ppc64le.whl", hash = "sha256:bd8f7df7d12c2db9fab40bdd87a7c09b1530128315d047a086fa3ae3435cb3a8"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-musllinux_1_1_s390x.whl", hash = "sha256:c180f51afb394e165eafe4ac2936a14bee3eb10debc9d9e4db8958fe36afe711"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-musllinux_1_1_x86_64.whl", hash = "sha256:8c622a5fe39a48f78944a87d4fb8a53ee07344641b0562c540d840748571b811"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-win32.whl", hash = "sha256:db364eca23f876da6f9e16c9da0df51aa4f104a972735574842618b8c6d999d4"},
+    {file = "charset_normalizer-3.3.2-cp37-cp37m-win_amd64.whl", hash = "sha256:86216b5cee4b06df986d214f664305142d9c76df9b6512be2738aa72a2048f99"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-macosx_10_9_universal2.whl", hash = "sha256:6463effa3186ea09411d50efc7d85360b38d5f09b870c48e4600f63af490e56a"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:6c4caeef8fa63d06bd437cd4bdcf3ffefe6738fb1b25951440d80dc7df8c03ac"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-macosx_11_0_arm64.whl", hash = "sha256:37e55c8e51c236f95b033f6fb391d7d7970ba5fe7ff453dad675e88cf303377a"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:fb69256e180cb6c8a894fee62b3afebae785babc1ee98b81cdf68bbca1987f33"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:ae5f4161f18c61806f411a13b0310bea87f987c7d2ecdbdaad0e94eb2e404238"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:b2b0a0c0517616b6869869f8c581d4eb2dd83a4d79e0ebcb7d373ef9956aeb0a"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:45485e01ff4d3630ec0d9617310448a8702f70e9c01906b0d0118bdf9d124cf2"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:eb00ed941194665c332bf8e078baf037d6c35d7c4f3102ea2d4f16ca94a26dc8"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-musllinux_1_1_aarch64.whl", hash = "sha256:2127566c664442652f024c837091890cb1942c30937add288223dc895793f898"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-musllinux_1_1_i686.whl", hash = "sha256:a50aebfa173e157099939b17f18600f72f84eed3049e743b68ad15bd69b6bf99"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-musllinux_1_1_ppc64le.whl", hash = "sha256:4d0d1650369165a14e14e1e47b372cfcb31d6ab44e6e33cb2d4e57265290044d"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-musllinux_1_1_s390x.whl", hash = "sha256:923c0c831b7cfcb071580d3f46c4baf50f174be571576556269530f4bbd79d04"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-musllinux_1_1_x86_64.whl", hash = "sha256:06a81e93cd441c56a9b65d8e1d043daeb97a3d0856d177d5c90ba85acb3db087"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-win32.whl", hash = "sha256:6ef1d82a3af9d3eecdba2321dc1b3c238245d890843e040e41e470ffa64c3e25"},
+    {file = "charset_normalizer-3.3.2-cp38-cp38-win_amd64.whl", hash = "sha256:eb8821e09e916165e160797a6c17edda0679379a4be5c716c260e836e122f54b"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-macosx_10_9_universal2.whl", hash = "sha256:c235ebd9baae02f1b77bcea61bce332cb4331dc3617d254df3323aa01ab47bd4"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:5b4c145409bef602a690e7cfad0a15a55c13320ff7a3ad7ca59c13bb8ba4d45d"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:68d1f8a9e9e37c1223b656399be5d6b448dea850bed7d0f87a8311f1ff3dabb0"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:22afcb9f253dac0696b5a4be4a1c0f8762f8239e21b99680099abd9b2b1b2269"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:e27ad930a842b4c5eb8ac0016b0a54f5aebbe679340c26101df33424142c143c"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:1f79682fbe303db92bc2b1136016a38a42e835d932bab5b3b1bfcfbf0640e519"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:b261ccdec7821281dade748d088bb6e9b69e6d15b30652b74cbbac25e280b796"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:122c7fa62b130ed55f8f285bfd56d5f4b4a5b503609d181f9ad85e55c89f4185"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-musllinux_1_1_aarch64.whl", hash = "sha256:d0eccceffcb53201b5bfebb52600a5fb483a20b61da9dbc885f8b103cbe7598c"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-musllinux_1_1_i686.whl", hash = "sha256:9f96df6923e21816da7e0ad3fd47dd8f94b2a5ce594e00677c0013018b813458"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-musllinux_1_1_ppc64le.whl", hash = "sha256:7f04c839ed0b6b98b1a7501a002144b76c18fb1c1850c8b98d458ac269e26ed2"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-musllinux_1_1_s390x.whl", hash = "sha256:34d1c8da1e78d2e001f363791c98a272bb734000fcef47a491c1e3b0505657a8"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-musllinux_1_1_x86_64.whl", hash = "sha256:ff8fa367d09b717b2a17a052544193ad76cd49979c805768879cb63d9ca50561"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-win32.whl", hash = "sha256:aed38f6e4fb3f5d6bf81bfa990a07806be9d83cf7bacef998ab1a9bd660a581f"},
+    {file = "charset_normalizer-3.3.2-cp39-cp39-win_amd64.whl", hash = "sha256:b01b88d45a6fcb69667cd6d2f7a9aeb4bf53760d7fc536bf679ec94fe9f3ff3d"},
+    {file = "charset_normalizer-3.3.2-py3-none-any.whl", hash = "sha256:3e4d1f6587322d2788836a99c69062fbb091331ec940e02d12d179c1d53e25fc"},
+]
+
+[[package]]
+name = "click"
+version = "8.1.7"
+description = "Composable command line interface toolkit"
+optional = false
+python-versions = ">=3.7"
+files = [
+    {file = "click-8.1.7-py3-none-any.whl", hash = "sha256:ae74fb96c20a0277a1d615f1e4d73c8414f5a98db8b799a7931d1582f3390c28"},
+    {file = "click-8.1.7.tar.gz", hash = "sha256:ca9853ad459e787e2192211578cc907e7594e294c7ccc834310722b41b9ca6de"},
+]
+
+[package.dependencies]
+colorama = {version = "*", markers = "platform_system == \"Windows\""}
+
+[[package]]
+name = "colorama"
+version = "0.4.6"
+description = "Cross-platform colored terminal text."
+optional = false
+python-versions = "!=3.0.*,!=3.1.*,!=3.2.*,!=3.3.*,!=3.4.*,!=3.5.*,!=3.6.*,>=2.7"
+files = [
+    {file = "colorama-0.4.6-py2.py3-none-any.whl", hash = "sha256:4f1d9991f5acc0ca119f9d443620b77f9d6b33703e51011c16baf57afb285fc6"},
+    {file = "colorama-0.4.6.tar.gz", hash = "sha256:08695f5cb7ed6e0531a20572697297273c47b8cae5a63ffc6d6ed5c201be6e44"},
+]
+
+[[package]]
+name = "flake8"
+version = "7.0.0"
+description = "the modular source code checker: pep8 pyflakes and co"
+optional = false
+python-versions = ">=3.8.1"
+files = [
+    {file = "flake8-7.0.0-py2.py3-none-any.whl", hash = "sha256:a6dfbb75e03252917f2473ea9653f7cd799c3064e54d4c8140044c5c065f53c3"},
+    {file = "flake8-7.0.0.tar.gz", hash = "sha256:33f96621059e65eec474169085dc92bf26e7b2d47366b70be2f67ab80dc25132"},
+]
+
+[package.dependencies]
+mccabe = ">=0.7.0,<0.8.0"
+pycodestyle = ">=2.11.0,<2.12.0"
+pyflakes = ">=3.2.0,<3.3.0"
+
+[[package]]
+name = "ghp-import"
+version = "2.1.0"
+description = "Copy your docs directly to the gh-pages branch."
+optional = false
+python-versions = "*"
+files = [
+    {file = "ghp-import-2.1.0.tar.gz", hash = "sha256:9c535c4c61193c2df8871222567d7fd7e5014d835f97dc7b7439069e2413d343"},
+    {file = "ghp_import-2.1.0-py3-none-any.whl", hash = "sha256:8337dd7b50877f163d4c0289bc1f1c7f127550241988d568c1db512c4324a619"},
+]
+
+[package.dependencies]
+python-dateutil = ">=2.8.1"
+
+[package.extras]
+dev = ["flake8", "markdown", "twine", "wheel"]
+
+[[package]]
+name = "idna"
+version = "3.6"
+description = "Internationalized Domain Names in Applications (IDNA)"
+optional = false
+python-versions = ">=3.5"
+files = [
+    {file = "idna-3.6-py3-none-any.whl", hash = "sha256:c05567e9c24a6b9faaa835c4821bad0590fbb9d5779e7caa6e1cc4978e7eb24f"},
+    {file = "idna-3.6.tar.gz", hash = "sha256:9ecdbbd083b06798ae1e86adcbfe8ab1479cf864e4ee30fe4e46a003d12491ca"},
+]
+
+[[package]]
+name = "jinja2"
+version = "3.1.3"
+description = "A very fast and expressive template engine."
+optional = false
+python-versions = ">=3.7"
+files = [
+    {file = "Jinja2-3.1.3-py3-none-any.whl", hash = "sha256:7d6d50dd97d52cbc355597bd845fabfbac3f551e1f99619e39a35ce8c370b5fa"},
+    {file = "Jinja2-3.1.3.tar.gz", hash = "sha256:ac8bd6544d4bb2c9792bf3a159e80bba8fda7f07e81bc3aed565432d5925ba90"},
+]
+
+[package.dependencies]
+MarkupSafe = ">=2.0"
+
+[package.extras]
+i18n = ["Babel (>=2.7)"]
+
+[[package]]
+name = "markdown"
+version = "3.5.2"
+description = "Python implementation of John Gruber's Markdown."
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "Markdown-3.5.2-py3-none-any.whl", hash = "sha256:d43323865d89fc0cb9b20c75fc8ad313af307cc087e84b657d9eec768eddeadd"},
+    {file = "Markdown-3.5.2.tar.gz", hash = "sha256:e1ac7b3dc550ee80e602e71c1d168002f062e49f1b11e26a36264dafd4df2ef8"},
+]
+
+[package.extras]
+docs = ["mdx-gh-links (>=0.2)", "mkdocs (>=1.5)", "mkdocs-gen-files", "mkdocs-literate-nav", "mkdocs-nature (>=0.6)", "mkdocs-section-index", "mkdocstrings[python]"]
+testing = ["coverage", "pyyaml"]
+
+[[package]]
+name = "markupsafe"
+version = "2.1.5"
+description = "Safely add untrusted strings to HTML/XML markup."
+optional = false
+python-versions = ">=3.7"
+files = [
+    {file = "MarkupSafe-2.1.5-cp310-cp310-macosx_10_9_universal2.whl", hash = "sha256:a17a92de5231666cfbe003f0e4b9b3a7ae3afb1ec2845aadc2bacc93ff85febc"},
+    {file = "MarkupSafe-2.1.5-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:72b6be590cc35924b02c78ef34b467da4ba07e4e0f0454a2c5907f473fc50ce5"},
+    {file = "MarkupSafe-2.1.5-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:e61659ba32cf2cf1481e575d0462554625196a1f2fc06a1c777d3f48e8865d46"},
+    {file = "MarkupSafe-2.1.5-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:2174c595a0d73a3080ca3257b40096db99799265e1c27cc5a610743acd86d62f"},
+    {file = "MarkupSafe-2.1.5-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:ae2ad8ae6ebee9d2d94b17fb62763125f3f374c25618198f40cbb8b525411900"},
+    {file = "MarkupSafe-2.1.5-cp310-cp310-musllinux_1_1_aarch64.whl", hash = "sha256:075202fa5b72c86ad32dc7d0b56024ebdbcf2048c0ba09f1cde31bfdd57bcfff"},
+    {file = "MarkupSafe-2.1.5-cp310-cp310-musllinux_1_1_i686.whl", hash = "sha256:598e3276b64aff0e7b3451b72e94fa3c238d452e7ddcd893c3ab324717456bad"},
+    {file = "MarkupSafe-2.1.5-cp310-cp310-musllinux_1_1_x86_64.whl", hash = "sha256:fce659a462a1be54d2ffcacea5e3ba2d74daa74f30f5f143fe0c58636e355fdd"},
+    {file = "MarkupSafe-2.1.5-cp310-cp310-win32.whl", hash = "sha256:d9fad5155d72433c921b782e58892377c44bd6252b5af2f67f16b194987338a4"},
+    {file = "MarkupSafe-2.1.5-cp310-cp310-win_amd64.whl", hash = "sha256:bf50cd79a75d181c9181df03572cdce0fbb75cc353bc350712073108cba98de5"},
+    {file = "MarkupSafe-2.1.5-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:629ddd2ca402ae6dbedfceeba9c46d5f7b2a61d9749597d4307f943ef198fc1f"},
+    {file = "MarkupSafe-2.1.5-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:5b7b716f97b52c5a14bffdf688f971b2d5ef4029127f1ad7a513973cfd818df2"},
+    {file = "MarkupSafe-2.1.5-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:6ec585f69cec0aa07d945b20805be741395e28ac1627333b1c5b0105962ffced"},
+    {file = "MarkupSafe-2.1.5-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:b91c037585eba9095565a3556f611e3cbfaa42ca1e865f7b8015fe5c7336d5a5"},
+    {file = "MarkupSafe-2.1.5-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:7502934a33b54030eaf1194c21c692a534196063db72176b0c4028e140f8f32c"},
+    {file = "MarkupSafe-2.1.5-cp311-cp311-musllinux_1_1_aarch64.whl", hash = "sha256:0e397ac966fdf721b2c528cf028494e86172b4feba51d65f81ffd65c63798f3f"},
+    {file = "MarkupSafe-2.1.5-cp311-cp311-musllinux_1_1_i686.whl", hash = "sha256:c061bb86a71b42465156a3ee7bd58c8c2ceacdbeb95d05a99893e08b8467359a"},
+    {file = "MarkupSafe-2.1.5-cp311-cp311-musllinux_1_1_x86_64.whl", hash = "sha256:3a57fdd7ce31c7ff06cdfbf31dafa96cc533c21e443d57f5b1ecc6cdc668ec7f"},
+    {file = "MarkupSafe-2.1.5-cp311-cp311-win32.whl", hash = "sha256:397081c1a0bfb5124355710fe79478cdbeb39626492b15d399526ae53422b906"},
+    {file = "MarkupSafe-2.1.5-cp311-cp311-win_amd64.whl", hash = "sha256:2b7c57a4dfc4f16f7142221afe5ba4e093e09e728ca65c51f5620c9aaeb9a617"},
+    {file = "MarkupSafe-2.1.5-cp312-cp312-macosx_10_9_universal2.whl", hash = "sha256:8dec4936e9c3100156f8a2dc89c4b88d5c435175ff03413b443469c7c8c5f4d1"},
+    {file = "MarkupSafe-2.1.5-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:3c6b973f22eb18a789b1460b4b91bf04ae3f0c4234a0a6aa6b0a92f6f7b951d4"},
+    {file = "MarkupSafe-2.1.5-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:ac07bad82163452a6884fe8fa0963fb98c2346ba78d779ec06bd7a6262132aee"},
+    {file = "MarkupSafe-2.1.5-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:f5dfb42c4604dddc8e4305050aa6deb084540643ed5804d7455b5df8fe16f5e5"},
+    {file = "MarkupSafe-2.1.5-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:ea3d8a3d18833cf4304cd2fc9cbb1efe188ca9b5efef2bdac7adc20594a0e46b"},
+    {file = "MarkupSafe-2.1.5-cp312-cp312-musllinux_1_1_aarch64.whl", hash = "sha256:d050b3361367a06d752db6ead6e7edeb0009be66bc3bae0ee9d97fb326badc2a"},
+    {file = "MarkupSafe-2.1.5-cp312-cp312-musllinux_1_1_i686.whl", hash = "sha256:bec0a414d016ac1a18862a519e54b2fd0fc8bbfd6890376898a6c0891dd82e9f"},
+    {file = "MarkupSafe-2.1.5-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:58c98fee265677f63a4385256a6d7683ab1832f3ddd1e66fe948d5880c21a169"},
+    {file = "MarkupSafe-2.1.5-cp312-cp312-win32.whl", hash = "sha256:8590b4ae07a35970728874632fed7bd57b26b0102df2d2b233b6d9d82f6c62ad"},
+    {file = "MarkupSafe-2.1.5-cp312-cp312-win_amd64.whl", hash = "sha256:823b65d8706e32ad2df51ed89496147a42a2a6e01c13cfb6ffb8b1e92bc910bb"},
+    {file = "MarkupSafe-2.1.5-cp37-cp37m-macosx_10_9_x86_64.whl", hash = "sha256:c8b29db45f8fe46ad280a7294f5c3ec36dbac9491f2d1c17345be8e69cc5928f"},
+    {file = "MarkupSafe-2.1.5-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:ec6a563cff360b50eed26f13adc43e61bc0c04d94b8be985e6fb24b81f6dcfdf"},
+    {file = "MarkupSafe-2.1.5-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:a549b9c31bec33820e885335b451286e2969a2d9e24879f83fe904a5ce59d70a"},
+    {file = "MarkupSafe-2.1.5-cp37-cp37m-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:4f11aa001c540f62c6166c7726f71f7573b52c68c31f014c25cc7901deea0b52"},
+    {file = "MarkupSafe-2.1.5-cp37-cp37m-musllinux_1_1_aarch64.whl", hash = "sha256:7b2e5a267c855eea6b4283940daa6e88a285f5f2a67f2220203786dfa59b37e9"},
+    {file = "MarkupSafe-2.1.5-cp37-cp37m-musllinux_1_1_i686.whl", hash = "sha256:2d2d793e36e230fd32babe143b04cec8a8b3eb8a3122d2aceb4a371e6b09b8df"},
+    {file = "MarkupSafe-2.1.5-cp37-cp37m-musllinux_1_1_x86_64.whl", hash = "sha256:ce409136744f6521e39fd8e2a24c53fa18ad67aa5bc7c2cf83645cce5b5c4e50"},
+    {file = "MarkupSafe-2.1.5-cp37-cp37m-win32.whl", hash = "sha256:4096e9de5c6fdf43fb4f04c26fb114f61ef0bf2e5604b6ee3019d51b69e8c371"},
+    {file = "MarkupSafe-2.1.5-cp37-cp37m-win_amd64.whl", hash = "sha256:4275d846e41ecefa46e2015117a9f491e57a71ddd59bbead77e904dc02b1bed2"},
+    {file = "MarkupSafe-2.1.5-cp38-cp38-macosx_10_9_universal2.whl", hash = "sha256:656f7526c69fac7f600bd1f400991cc282b417d17539a1b228617081106feb4a"},
+    {file = "MarkupSafe-2.1.5-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:97cafb1f3cbcd3fd2b6fbfb99ae11cdb14deea0736fc2b0952ee177f2b813a46"},
+    {file = "MarkupSafe-2.1.5-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:1f3fbcb7ef1f16e48246f704ab79d79da8a46891e2da03f8783a5b6fa41a9532"},
+    {file = "MarkupSafe-2.1.5-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:fa9db3f79de01457b03d4f01b34cf91bc0048eb2c3846ff26f66687c2f6d16ab"},
+    {file = "MarkupSafe-2.1.5-cp38-cp38-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:ffee1f21e5ef0d712f9033568f8344d5da8cc2869dbd08d87c84656e6a2d2f68"},
+    {file = "MarkupSafe-2.1.5-cp38-cp38-musllinux_1_1_aarch64.whl", hash = "sha256:5dedb4db619ba5a2787a94d877bc8ffc0566f92a01c0ef214865e54ecc9ee5e0"},
+    {file = "MarkupSafe-2.1.5-cp38-cp38-musllinux_1_1_i686.whl", hash = "sha256:30b600cf0a7ac9234b2638fbc0fb6158ba5bdcdf46aeb631ead21248b9affbc4"},
+    {file = "MarkupSafe-2.1.5-cp38-cp38-musllinux_1_1_x86_64.whl", hash = "sha256:8dd717634f5a044f860435c1d8c16a270ddf0ef8588d4887037c5028b859b0c3"},
+    {file = "MarkupSafe-2.1.5-cp38-cp38-win32.whl", hash = "sha256:daa4ee5a243f0f20d528d939d06670a298dd39b1ad5f8a72a4275124a7819eff"},
+    {file = "MarkupSafe-2.1.5-cp38-cp38-win_amd64.whl", hash = "sha256:619bc166c4f2de5caa5a633b8b7326fbe98e0ccbfacabd87268a2b15ff73a029"},
+    {file = "MarkupSafe-2.1.5-cp39-cp39-macosx_10_9_universal2.whl", hash = "sha256:7a68b554d356a91cce1236aa7682dc01df0edba8d043fd1ce607c49dd3c1edcf"},
+    {file = "MarkupSafe-2.1.5-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:db0b55e0f3cc0be60c1f19efdde9a637c32740486004f20d1cff53c3c0ece4d2"},
+    {file = "MarkupSafe-2.1.5-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:3e53af139f8579a6d5f7b76549125f0d94d7e630761a2111bc431fd820e163b8"},
+    {file = "MarkupSafe-2.1.5-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:17b950fccb810b3293638215058e432159d2b71005c74371d784862b7e4683f3"},
+    {file = "MarkupSafe-2.1.5-cp39-cp39-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:4c31f53cdae6ecfa91a77820e8b151dba54ab528ba65dfd235c80b086d68a465"},
+    {file = "MarkupSafe-2.1.5-cp39-cp39-musllinux_1_1_aarch64.whl", hash = "sha256:bff1b4290a66b490a2f4719358c0cdcd9bafb6b8f061e45c7a2460866bf50c2e"},
+    {file = "MarkupSafe-2.1.5-cp39-cp39-musllinux_1_1_i686.whl", hash = "sha256:bc1667f8b83f48511b94671e0e441401371dfd0f0a795c7daa4a3cd1dde55bea"},
+    {file = "MarkupSafe-2.1.5-cp39-cp39-musllinux_1_1_x86_64.whl", hash = "sha256:5049256f536511ee3f7e1b3f87d1d1209d327e818e6ae1365e8653d7e3abb6a6"},
+    {file = "MarkupSafe-2.1.5-cp39-cp39-win32.whl", hash = "sha256:00e046b6dd71aa03a41079792f8473dc494d564611a8f89bbbd7cb93295ebdcf"},
+    {file = "MarkupSafe-2.1.5-cp39-cp39-win_amd64.whl", hash = "sha256:fa173ec60341d6bb97a89f5ea19c85c5643c1e7dedebc22f5181eb73573142c5"},
+    {file = "MarkupSafe-2.1.5.tar.gz", hash = "sha256:d283d37a890ba4c1ae73ffadf8046435c76e7bc2247bbb63c00bd1a709c6544b"},
+]
+
+[[package]]
+name = "mccabe"
+version = "0.7.0"
+description = "McCabe checker, plugin for flake8"
+optional = false
+python-versions = ">=3.6"
+files = [
+    {file = "mccabe-0.7.0-py2.py3-none-any.whl", hash = "sha256:6c2d30ab6be0e4a46919781807b4f0d834ebdd6c6e3dca0bda5a15f863427b6e"},
+    {file = "mccabe-0.7.0.tar.gz", hash = "sha256:348e0240c33b60bbdf4e523192ef919f28cb2c3d7d5c7794f74009290f236325"},
+]
+
+[[package]]
+name = "mergedeep"
+version = "1.3.4"
+description = "A deep merge function for 🐍."
+optional = false
+python-versions = ">=3.6"
+files = [
+    {file = "mergedeep-1.3.4-py3-none-any.whl", hash = "sha256:70775750742b25c0d8f36c55aed03d24c3384d17c951b3175d898bd778ef0307"},
+    {file = "mergedeep-1.3.4.tar.gz", hash = "sha256:0096d52e9dad9939c3d975a774666af186eda617e6ca84df4c94dec30004f2a8"},
+]
+
+[[package]]
+name = "mkdocs"
+version = "1.5.3"
+description = "Project documentation with Markdown."
+optional = false
+python-versions = ">=3.7"
+files = [
+    {file = "mkdocs-1.5.3-py3-none-any.whl", hash = "sha256:3b3a78e736b31158d64dbb2f8ba29bd46a379d0c6e324c2246c3bc3d2189cfc1"},
+    {file = "mkdocs-1.5.3.tar.gz", hash = "sha256:eb7c99214dcb945313ba30426c2451b735992c73c2e10838f76d09e39ff4d0e2"},
+]
+
+[package.dependencies]
+click = ">=7.0"
+colorama = {version = ">=0.4", markers = "platform_system == \"Windows\""}
+ghp-import = ">=1.0"
+jinja2 = ">=2.11.1"
+markdown = ">=3.2.1"
+markupsafe = ">=2.0.1"
+mergedeep = ">=1.3.4"
+packaging = ">=20.5"
+pathspec = ">=0.11.1"
+platformdirs = ">=2.2.0"
+pyyaml = ">=5.1"
+pyyaml-env-tag = ">=0.1"
+watchdog = ">=2.0"
+
+[package.extras]
+i18n = ["babel (>=2.9.0)"]
+min-versions = ["babel (==2.9.0)", "click (==7.0)", "colorama (==0.4)", "ghp-import (==1.0)", "importlib-metadata (==4.3)", "jinja2 (==2.11.1)", "markdown (==3.2.1)", "markupsafe (==2.0.1)", "mergedeep (==1.3.4)", "packaging (==20.5)", "pathspec (==0.11.1)", "platformdirs (==2.2.0)", "pyyaml (==5.1)", "pyyaml-env-tag (==0.1)", "typing-extensions (==3.10)", "watchdog (==2.0)"]
+
+[[package]]
+name = "mkdocs-material"
+version = "9.5.12"
+description = "Documentation that simply works"
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "mkdocs_material-9.5.12-py3-none-any.whl", hash = "sha256:d6f0c269f015e48c76291cdc79efb70f7b33bbbf42d649cfe475522ebee61b1f"},
+    {file = "mkdocs_material-9.5.12.tar.gz", hash = "sha256:5f69cef6a8aaa4050b812f72b1094fda3d079b9a51cf27a247244c03ec455e97"},
+]
+
+[package.dependencies]
+babel = ">=2.10,<3.0"
+colorama = ">=0.4,<1.0"
+jinja2 = ">=3.0,<4.0"
+markdown = ">=3.2,<4.0"
+mkdocs = ">=1.5.3,<1.6.0"
+mkdocs-material-extensions = ">=1.3,<2.0"
+paginate = ">=0.5,<1.0"
+pygments = ">=2.16,<3.0"
+pymdown-extensions = ">=10.2,<11.0"
+regex = ">=2022.4"
+requests = ">=2.26,<3.0"
+
+[package.extras]
+git = ["mkdocs-git-committers-plugin-2 (>=1.1,<2.0)", "mkdocs-git-revision-date-localized-plugin (>=1.2.4,<2.0)"]
+imaging = ["cairosvg (>=2.6,<3.0)", "pillow (>=10.2,<11.0)"]
+recommended = ["mkdocs-minify-plugin (>=0.7,<1.0)", "mkdocs-redirects (>=1.2,<2.0)", "mkdocs-rss-plugin (>=1.6,<2.0)"]
+
+[[package]]
+name = "mkdocs-material-extensions"
+version = "1.3.1"
+description = "Extension pack for Python Markdown and MkDocs Material."
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "mkdocs_material_extensions-1.3.1-py3-none-any.whl", hash = "sha256:adff8b62700b25cb77b53358dad940f3ef973dd6db797907c49e3c2ef3ab4e31"},
+    {file = "mkdocs_material_extensions-1.3.1.tar.gz", hash = "sha256:10c9511cea88f568257f960358a467d12b970e1f7b2c0e5fb2bb48cab1928443"},
+]
+
+[[package]]
+name = "mypy-extensions"
+version = "1.0.0"
+description = "Type system extensions for programs checked with the mypy type checker."
+optional = false
+python-versions = ">=3.5"
+files = [
+    {file = "mypy_extensions-1.0.0-py3-none-any.whl", hash = "sha256:4392f6c0eb8a5668a69e23d168ffa70f0be9ccfd32b5cc2d26a34ae5b844552d"},
+    {file = "mypy_extensions-1.0.0.tar.gz", hash = "sha256:75dbf8955dc00442a438fc4d0666508a9a97b6bd41aa2f0ffe9d2f2725af0782"},
+]
+
+[[package]]
+name = "nose"
+version = "1.3.7"
+description = "nose extends unittest to make testing easier"
+optional = false
+python-versions = "*"
+files = [
+    {file = "nose-1.3.7-py2-none-any.whl", hash = "sha256:dadcddc0aefbf99eea214e0f1232b94f2fa9bd98fa8353711dacb112bfcbbb2a"},
+    {file = "nose-1.3.7-py3-none-any.whl", hash = "sha256:9ff7c6cc443f8c51994b34a667bbcf45afd6d945be7477b52e97516fd17c53ac"},
+    {file = "nose-1.3.7.tar.gz", hash = "sha256:f1bffef9cbc82628f6e7d7b40d7e255aefaa1adb6a1b1d26c69a8b79e6208a98"},
+]
+
+[[package]]
+name = "packaging"
+version = "23.2"
+description = "Core utilities for Python packages"
+optional = false
+python-versions = ">=3.7"
+files = [
+    {file = "packaging-23.2-py3-none-any.whl", hash = "sha256:8c491190033a9af7e1d931d0b5dacc2ef47509b34dd0de67ed209b5203fc88c7"},
+    {file = "packaging-23.2.tar.gz", hash = "sha256:048fb0e9405036518eaaf48a55953c750c11e1a1b68e0dd1a9d62ed0c092cfc5"},
+]
+
+[[package]]
+name = "paginate"
+version = "0.5.6"
+description = "Divides large result sets into pages for easier browsing"
+optional = false
+python-versions = "*"
+files = [
+    {file = "paginate-0.5.6.tar.gz", hash = "sha256:5e6007b6a9398177a7e1648d04fdd9f8c9766a1a945bceac82f1929e8c78af2d"},
+]
+
+[[package]]
+name = "pathspec"
+version = "0.12.1"
+description = "Utility library for gitignore style pattern matching of file paths."
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "pathspec-0.12.1-py3-none-any.whl", hash = "sha256:a0d503e138a4c123b27490a4f7beda6a01c6f288df0e4a8b79c7eb0dc7b4cc08"},
+    {file = "pathspec-0.12.1.tar.gz", hash = "sha256:a482d51503a1ab33b1c67a6c3813a26953dbdc71c31dacaef9a838c4e29f5712"},
+]
+
+[[package]]
+name = "pip"
+version = "24.0"
+description = "The PyPA recommended tool for installing Python packages."
+optional = false
+python-versions = ">=3.7"
+files = [
+    {file = "pip-24.0-py3-none-any.whl", hash = "sha256:ba0d021a166865d2265246961bec0152ff124de910c5cc39f1156ce3fa7c69dc"},
+    {file = "pip-24.0.tar.gz", hash = "sha256:ea9bd1a847e8c5774a5777bb398c19e80bcd4e2aa16a4b301b718fe6f593aba2"},
+]
+
+[[package]]
+name = "platformdirs"
+version = "4.2.0"
+description = "A small Python package for determining appropriate platform-specific dirs, e.g. a \"user data dir\"."
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "platformdirs-4.2.0-py3-none-any.whl", hash = "sha256:0614df2a2f37e1a662acbd8e2b25b92ccf8632929bc6d43467e17fe89c75e068"},
+    {file = "platformdirs-4.2.0.tar.gz", hash = "sha256:ef0cc731df711022c174543cb70a9b5bd22e5a9337c8624ef2c2ceb8ddad8768"},
+]
+
+[package.extras]
+docs = ["furo (>=2023.9.10)", "proselint (>=0.13)", "sphinx (>=7.2.6)", "sphinx-autodoc-typehints (>=1.25.2)"]
+test = ["appdirs (==1.4.4)", "covdefaults (>=2.3)", "pytest (>=7.4.3)", "pytest-cov (>=4.1)", "pytest-mock (>=3.12)"]
+
+[[package]]
+name = "pycodestyle"
+version = "2.11.1"
+description = "Python style guide checker"
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "pycodestyle-2.11.1-py2.py3-none-any.whl", hash = "sha256:44fe31000b2d866f2e41841b18528a505fbd7fef9017b04eff4e2648a0fadc67"},
+    {file = "pycodestyle-2.11.1.tar.gz", hash = "sha256:41ba0e7afc9752dfb53ced5489e89f8186be00e599e712660695b7a75ff2663f"},
+]
+
+[[package]]
+name = "pyflakes"
+version = "3.2.0"
+description = "passive checker of Python programs"
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "pyflakes-3.2.0-py2.py3-none-any.whl", hash = "sha256:84b5be138a2dfbb40689ca07e2152deb896a65c3a3e24c251c5c62489568074a"},
+    {file = "pyflakes-3.2.0.tar.gz", hash = "sha256:1c61603ff154621fb2a9172037d84dca3500def8c8b630657d1701f026f8af3f"},
+]
+
+[[package]]
+name = "pygments"
+version = "2.17.2"
+description = "Pygments is a syntax highlighting package written in Python."
+optional = false
+python-versions = ">=3.7"
+files = [
+    {file = "pygments-2.17.2-py3-none-any.whl", hash = "sha256:b27c2826c47d0f3219f29554824c30c5e8945175d888647acd804ddd04af846c"},
+    {file = "pygments-2.17.2.tar.gz", hash = "sha256:da46cec9fd2de5be3a8a784f434e4c4ab670b4ff54d605c4c2717e9d49c4c367"},
+]
+
+[package.extras]
+plugins = ["importlib-metadata"]
+windows-terminal = ["colorama (>=0.4.6)"]
+
+[[package]]
+name = "pymdown-extensions"
+version = "10.7"
+description = "Extension pack for Python Markdown."
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "pymdown_extensions-10.7-py3-none-any.whl", hash = "sha256:6ca215bc57bc12bf32b414887a68b810637d039124ed9b2e5bd3325cbb2c050c"},
+    {file = "pymdown_extensions-10.7.tar.gz", hash = "sha256:c0d64d5cf62566f59e6b2b690a4095c931107c250a8c8e1351c1de5f6b036deb"},
+]
+
+[package.dependencies]
+markdown = ">=3.5"
+pyyaml = "*"
+
+[package.extras]
+extra = ["pygments (>=2.12)"]
+
+[[package]]
+name = "python-dateutil"
+version = "2.9.0.post0"
+description = "Extensions to the standard Python datetime module"
+optional = false
+python-versions = "!=3.0.*,!=3.1.*,!=3.2.*,>=2.7"
+files = [
+    {file = "python-dateutil-2.9.0.post0.tar.gz", hash = "sha256:37dd54208da7e1cd875388217d5e00ebd4179249f90fb72437e91a35459a0ad3"},
+    {file = "python_dateutil-2.9.0.post0-py2.py3-none-any.whl", hash = "sha256:a8b2bc7bffae282281c8140a97d3aa9c14da0b136dfe83f850eea9a5f7470427"},
+]
+
+[package.dependencies]
+six = ">=1.5"
+
+[[package]]
+name = "python-dotenv"
+version = "1.0.1"
+description = "Read key-value pairs from a .env file and set them as environment variables"
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "python-dotenv-1.0.1.tar.gz", hash = "sha256:e324ee90a023d808f1959c46bcbc04446a10ced277783dc6ee09987c37ec10ca"},
+    {file = "python_dotenv-1.0.1-py3-none-any.whl", hash = "sha256:f7b63ef50f1b690dddf550d03497b66d609393b40b564ed0d674909a68ebf16a"},
+]
+
+[package.extras]
+cli = ["click (>=5.0)"]
+
+[[package]]
+name = "pyyaml"
+version = "6.0.1"
+description = "YAML parser and emitter for Python"
+optional = false
+python-versions = ">=3.6"
+files = [
+    {file = "PyYAML-6.0.1-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:d858aa552c999bc8a8d57426ed01e40bef403cd8ccdd0fc5f6f04a00414cac2a"},
+    {file = "PyYAML-6.0.1-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:fd66fc5d0da6d9815ba2cebeb4205f95818ff4b79c3ebe268e75d961704af52f"},
+    {file = "PyYAML-6.0.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:69b023b2b4daa7548bcfbd4aa3da05b3a74b772db9e23b982788168117739938"},
+    {file = "PyYAML-6.0.1-cp310-cp310-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:81e0b275a9ecc9c0c0c07b4b90ba548307583c125f54d5b6946cfee6360c733d"},
+    {file = "PyYAML-6.0.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:ba336e390cd8e4d1739f42dfe9bb83a3cc2e80f567d8805e11b46f4a943f5515"},
+    {file = "PyYAML-6.0.1-cp310-cp310-musllinux_1_1_x86_64.whl", hash = "sha256:326c013efe8048858a6d312ddd31d56e468118ad4cdeda36c719bf5bb6192290"},
+    {file = "PyYAML-6.0.1-cp310-cp310-win32.whl", hash = "sha256:bd4af7373a854424dabd882decdc5579653d7868b8fb26dc7d0e99f823aa5924"},
+    {file = "PyYAML-6.0.1-cp310-cp310-win_amd64.whl", hash = "sha256:fd1592b3fdf65fff2ad0004b5e363300ef59ced41c2e6b3a99d4089fa8c5435d"},
+    {file = "PyYAML-6.0.1-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:6965a7bc3cf88e5a1c3bd2e0b5c22f8d677dc88a455344035f03399034eb3007"},
+    {file = "PyYAML-6.0.1-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:f003ed9ad21d6a4713f0a9b5a7a0a79e08dd0f221aff4525a2be4c346ee60aab"},
+    {file = "PyYAML-6.0.1-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:42f8152b8dbc4fe7d96729ec2b99c7097d656dc1213a3229ca5383f973a5ed6d"},
+    {file = "PyYAML-6.0.1-cp311-cp311-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:062582fca9fabdd2c8b54a3ef1c978d786e0f6b3a1510e0ac93ef59e0ddae2bc"},
+    {file = "PyYAML-6.0.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:d2b04aac4d386b172d5b9692e2d2da8de7bfb6c387fa4f801fbf6fb2e6ba4673"},
+    {file = "PyYAML-6.0.1-cp311-cp311-musllinux_1_1_x86_64.whl", hash = "sha256:e7d73685e87afe9f3b36c799222440d6cf362062f78be1013661b00c5c6f678b"},
+    {file = "PyYAML-6.0.1-cp311-cp311-win32.whl", hash = "sha256:1635fd110e8d85d55237ab316b5b011de701ea0f29d07611174a1b42f1444741"},
+    {file = "PyYAML-6.0.1-cp311-cp311-win_amd64.whl", hash = "sha256:bf07ee2fef7014951eeb99f56f39c9bb4af143d8aa3c21b1677805985307da34"},
+    {file = "PyYAML-6.0.1-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:855fb52b0dc35af121542a76b9a84f8d1cd886ea97c84703eaa6d88e37a2ad28"},
+    {file = "PyYAML-6.0.1-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:40df9b996c2b73138957fe23a16a4f0ba614f4c0efce1e9406a184b6d07fa3a9"},
+    {file = "PyYAML-6.0.1-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:a08c6f0fe150303c1c6b71ebcd7213c2858041a7e01975da3a99aed1e7a378ef"},
+    {file = "PyYAML-6.0.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:6c22bec3fbe2524cde73d7ada88f6566758a8f7227bfbf93a408a9d86bcc12a0"},
+    {file = "PyYAML-6.0.1-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:8d4e9c88387b0f5c7d5f281e55304de64cf7f9c0021a3525bd3b1c542da3b0e4"},
+    {file = "PyYAML-6.0.1-cp312-cp312-win32.whl", hash = "sha256:d483d2cdf104e7c9fa60c544d92981f12ad66a457afae824d146093b8c294c54"},
+    {file = "PyYAML-6.0.1-cp312-cp312-win_amd64.whl", hash = "sha256:0d3304d8c0adc42be59c5f8a4d9e3d7379e6955ad754aa9d6ab7a398b59dd1df"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-macosx_10_9_x86_64.whl", hash = "sha256:50550eb667afee136e9a77d6dc71ae76a44df8b3e51e41b77f6de2932bfe0f47"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:1fe35611261b29bd1de0070f0b2f47cb6ff71fa6595c077e42bd0c419fa27b98"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:704219a11b772aea0d8ecd7058d0082713c3562b4e271b849ad7dc4a5c90c13c"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:afd7e57eddb1a54f0f1a974bc4391af8bcce0b444685d936840f125cf046d5bd"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-win32.whl", hash = "sha256:fca0e3a251908a499833aa292323f32437106001d436eca0e6e7833256674585"},
+    {file = "PyYAML-6.0.1-cp36-cp36m-win_amd64.whl", hash = "sha256:f22ac1c3cac4dbc50079e965eba2c1058622631e526bd9afd45fedd49ba781fa"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-macosx_10_9_x86_64.whl", hash = "sha256:b1275ad35a5d18c62a7220633c913e1b42d44b46ee12554e5fd39c70a243d6a3"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:18aeb1bf9a78867dc38b259769503436b7c72f7a1f1f4c93ff9a17de54319b27"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:596106435fa6ad000c2991a98fa58eeb8656ef2325d7e158344fb33864ed87e3"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:baa90d3f661d43131ca170712d903e6295d1f7a0f595074f151c0aed377c9b9c"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-win32.whl", hash = "sha256:9046c58c4395dff28dd494285c82ba00b546adfc7ef001486fbf0324bc174fba"},
+    {file = "PyYAML-6.0.1-cp37-cp37m-win_amd64.whl", hash = "sha256:4fb147e7a67ef577a588a0e2c17b6db51dda102c71de36f8549b6816a96e1867"},
+    {file = "PyYAML-6.0.1-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:1d4c7e777c441b20e32f52bd377e0c409713e8bb1386e1099c2415f26e479595"},
+    {file = "PyYAML-6.0.1-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:a0cd17c15d3bb3fa06978b4e8958dcdc6e0174ccea823003a106c7d4d7899ac5"},
+    {file = "PyYAML-6.0.1-cp38-cp38-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:28c119d996beec18c05208a8bd78cbe4007878c6dd15091efb73a30e90539696"},
+    {file = "PyYAML-6.0.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:7e07cbde391ba96ab58e532ff4803f79c4129397514e1413a7dc761ccd755735"},
+    {file = "PyYAML-6.0.1-cp38-cp38-musllinux_1_1_x86_64.whl", hash = "sha256:49a183be227561de579b4a36efbb21b3eab9651dd81b1858589f796549873dd6"},
+    {file = "PyYAML-6.0.1-cp38-cp38-win32.whl", hash = "sha256:184c5108a2aca3c5b3d3bf9395d50893a7ab82a38004c8f61c258d4428e80206"},
+    {file = "PyYAML-6.0.1-cp38-cp38-win_amd64.whl", hash = "sha256:1e2722cc9fbb45d9b87631ac70924c11d3a401b2d7f410cc0e3bbf249f2dca62"},
+    {file = "PyYAML-6.0.1-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:9eb6caa9a297fc2c2fb8862bc5370d0303ddba53ba97e71f08023b6cd73d16a8"},
+    {file = "PyYAML-6.0.1-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:c8098ddcc2a85b61647b2590f825f3db38891662cfc2fc776415143f599bb859"},
+    {file = "PyYAML-6.0.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:5773183b6446b2c99bb77e77595dd486303b4faab2b086e7b17bc6bef28865f6"},
+    {file = "PyYAML-6.0.1-cp39-cp39-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:b786eecbdf8499b9ca1d697215862083bd6d2a99965554781d0d8d1ad31e13a0"},
+    {file = "PyYAML-6.0.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:bc1bf2925a1ecd43da378f4db9e4f799775d6367bdb94671027b73b393a7c42c"},
+    {file = "PyYAML-6.0.1-cp39-cp39-musllinux_1_1_x86_64.whl", hash = "sha256:04ac92ad1925b2cff1db0cfebffb6ffc43457495c9b3c39d3fcae417d7125dc5"},
+    {file = "PyYAML-6.0.1-cp39-cp39-win32.whl", hash = "sha256:faca3bdcf85b2fc05d06ff3fbc1f83e1391b3e724afa3feba7d13eeab355484c"},
+    {file = "PyYAML-6.0.1-cp39-cp39-win_amd64.whl", hash = "sha256:510c9deebc5c0225e8c96813043e62b680ba2f9c50a08d3724c7f28a747d1486"},
+    {file = "PyYAML-6.0.1.tar.gz", hash = "sha256:bfdf460b1736c775f2ba9f6a92bca30bc2095067b8a9d77876d1fad6cc3b4a43"},
+]
+
+[[package]]
+name = "pyyaml-env-tag"
+version = "0.1"
+description = "A custom YAML tag for referencing environment variables in YAML files. "
+optional = false
+python-versions = ">=3.6"
+files = [
+    {file = "pyyaml_env_tag-0.1-py3-none-any.whl", hash = "sha256:af31106dec8a4d68c60207c1886031cbf839b68aa7abccdb19868200532c2069"},
+    {file = "pyyaml_env_tag-0.1.tar.gz", hash = "sha256:70092675bda14fdec33b31ba77e7543de9ddc88f2e5b99160396572d11525bdb"},
+]
+
+[package.dependencies]
+pyyaml = "*"
+
+[[package]]
+name = "regex"
+version = "2023.12.25"
+description = "Alternative regular expression module, to replace re."
+optional = false
+python-versions = ">=3.7"
+files = [
+    {file = "regex-2023.12.25-cp310-cp310-macosx_10_9_universal2.whl", hash = "sha256:0694219a1d54336fd0445ea382d49d36882415c0134ee1e8332afd1529f0baa5"},
+    {file = "regex-2023.12.25-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:b014333bd0217ad3d54c143de9d4b9a3ca1c5a29a6d0d554952ea071cff0f1f8"},
+    {file = "regex-2023.12.25-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:d865984b3f71f6d0af64d0d88f5733521698f6c16f445bb09ce746c92c97c586"},
+    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:1e0eabac536b4cc7f57a5f3d095bfa557860ab912f25965e08fe1545e2ed8b4c"},
+    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:c25a8ad70e716f96e13a637802813f65d8a6760ef48672aa3502f4c24ea8b400"},
+    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:a9b6d73353f777630626f403b0652055ebfe8ff142a44ec2cf18ae470395766e"},
+    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:a9cc99d6946d750eb75827cb53c4371b8b0fe89c733a94b1573c9dd16ea6c9e4"},
+    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:88d1f7bef20c721359d8675f7d9f8e414ec5003d8f642fdfd8087777ff7f94b5"},
+    {file = "regex-2023.12.25-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl", hash = "sha256:cb3fe77aec8f1995611f966d0c656fdce398317f850d0e6e7aebdfe61f40e1cd"},
+    {file = "regex-2023.12.25-cp310-cp310-musllinux_1_1_aarch64.whl", hash = "sha256:7aa47c2e9ea33a4a2a05f40fcd3ea36d73853a2aae7b4feab6fc85f8bf2c9704"},
+    {file = "regex-2023.12.25-cp310-cp310-musllinux_1_1_i686.whl", hash = "sha256:df26481f0c7a3f8739fecb3e81bc9da3fcfae34d6c094563b9d4670b047312e1"},
+    {file = "regex-2023.12.25-cp310-cp310-musllinux_1_1_ppc64le.whl", hash = "sha256:c40281f7d70baf6e0db0c2f7472b31609f5bc2748fe7275ea65a0b4601d9b392"},
+    {file = "regex-2023.12.25-cp310-cp310-musllinux_1_1_s390x.whl", hash = "sha256:d94a1db462d5690ebf6ae86d11c5e420042b9898af5dcf278bd97d6bda065423"},
+    {file = "regex-2023.12.25-cp310-cp310-musllinux_1_1_x86_64.whl", hash = "sha256:ba1b30765a55acf15dce3f364e4928b80858fa8f979ad41f862358939bdd1f2f"},
+    {file = "regex-2023.12.25-cp310-cp310-win32.whl", hash = "sha256:150c39f5b964e4d7dba46a7962a088fbc91f06e606f023ce57bb347a3b2d4630"},
+    {file = "regex-2023.12.25-cp310-cp310-win_amd64.whl", hash = "sha256:09da66917262d9481c719599116c7dc0c321ffcec4b1f510c4f8a066f8768105"},
+    {file = "regex-2023.12.25-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:1b9d811f72210fa9306aeb88385b8f8bcef0dfbf3873410413c00aa94c56c2b6"},
+    {file = "regex-2023.12.25-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:d902a43085a308cef32c0d3aea962524b725403fd9373dea18110904003bac97"},
+    {file = "regex-2023.12.25-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:d166eafc19f4718df38887b2bbe1467a4f74a9830e8605089ea7a30dd4da8887"},
+    {file = "regex-2023.12.25-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:c7ad32824b7f02bb3c9f80306d405a1d9b7bb89362d68b3c5a9be53836caebdb"},
+    {file = "regex-2023.12.25-cp311-cp311-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:636ba0a77de609d6510235b7f0e77ec494d2657108f777e8765efc060094c98c"},
+    {file = "regex-2023.12.25-cp311-cp311-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:0fda75704357805eb953a3ee15a2b240694a9a514548cd49b3c5124b4e2ad01b"},
+    {file = "regex-2023.12.25-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:f72cbae7f6b01591f90814250e636065850c5926751af02bb48da94dfced7baa"},
+    {file = "regex-2023.12.25-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:db2a0b1857f18b11e3b0e54ddfefc96af46b0896fb678c85f63fb8c37518b3e7"},
+    {file = "regex-2023.12.25-cp311-cp311-musllinux_1_1_aarch64.whl", hash = "sha256:7502534e55c7c36c0978c91ba6f61703faf7ce733715ca48f499d3dbbd7657e0"},
+    {file = "regex-2023.12.25-cp311-cp311-musllinux_1_1_i686.whl", hash = "sha256:e8c7e08bb566de4faaf11984af13f6bcf6a08f327b13631d41d62592681d24fe"},
+    {file = "regex-2023.12.25-cp311-cp311-musllinux_1_1_ppc64le.whl", hash = "sha256:283fc8eed679758de38fe493b7d7d84a198b558942b03f017b1f94dda8efae80"},
+    {file = "regex-2023.12.25-cp311-cp311-musllinux_1_1_s390x.whl", hash = "sha256:f44dd4d68697559d007462b0a3a1d9acd61d97072b71f6d1968daef26bc744bd"},
+    {file = "regex-2023.12.25-cp311-cp311-musllinux_1_1_x86_64.whl", hash = "sha256:67d3ccfc590e5e7197750fcb3a2915b416a53e2de847a728cfa60141054123d4"},
+    {file = "regex-2023.12.25-cp311-cp311-win32.whl", hash = "sha256:68191f80a9bad283432385961d9efe09d783bcd36ed35a60fb1ff3f1ec2efe87"},
+    {file = "regex-2023.12.25-cp311-cp311-win_amd64.whl", hash = "sha256:7d2af3f6b8419661a0c421584cfe8aaec1c0e435ce7e47ee2a97e344b98f794f"},
+    {file = "regex-2023.12.25-cp312-cp312-macosx_10_9_universal2.whl", hash = "sha256:8a0ccf52bb37d1a700375a6b395bff5dd15c50acb745f7db30415bae3c2b0715"},
+    {file = "regex-2023.12.25-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:c3c4a78615b7762740531c27cf46e2f388d8d727d0c0c739e72048beb26c8a9d"},
+    {file = "regex-2023.12.25-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:ad83e7545b4ab69216cef4cc47e344d19622e28aabec61574b20257c65466d6a"},
+    {file = "regex-2023.12.25-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:b7a635871143661feccce3979e1727c4e094f2bdfd3ec4b90dfd4f16f571a87a"},
+    {file = "regex-2023.12.25-cp312-cp312-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:d498eea3f581fbe1b34b59c697512a8baef88212f92e4c7830fcc1499f5b45a5"},
+    {file = "regex-2023.12.25-cp312-cp312-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:43f7cd5754d02a56ae4ebb91b33461dc67be8e3e0153f593c509e21d219c5060"},
+    {file = "regex-2023.12.25-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:51f4b32f793812714fd5307222a7f77e739b9bc566dc94a18126aba3b92b98a3"},
+    {file = "regex-2023.12.25-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:ba99d8077424501b9616b43a2d208095746fb1284fc5ba490139651f971d39d9"},
+    {file = "regex-2023.12.25-cp312-cp312-musllinux_1_1_aarch64.whl", hash = "sha256:4bfc2b16e3ba8850e0e262467275dd4d62f0d045e0e9eda2bc65078c0110a11f"},
+    {file = "regex-2023.12.25-cp312-cp312-musllinux_1_1_i686.whl", hash = "sha256:8c2c19dae8a3eb0ea45a8448356ed561be843b13cbc34b840922ddf565498c1c"},
+    {file = "regex-2023.12.25-cp312-cp312-musllinux_1_1_ppc64le.whl", hash = "sha256:60080bb3d8617d96f0fb7e19796384cc2467447ef1c491694850ebd3670bc457"},
+    {file = "regex-2023.12.25-cp312-cp312-musllinux_1_1_s390x.whl", hash = "sha256:b77e27b79448e34c2c51c09836033056a0547aa360c45eeeb67803da7b0eedaf"},
+    {file = "regex-2023.12.25-cp312-cp312-musllinux_1_1_x86_64.whl", hash = "sha256:518440c991f514331f4850a63560321f833979d145d7d81186dbe2f19e27ae3d"},
+    {file = "regex-2023.12.25-cp312-cp312-win32.whl", hash = "sha256:e2610e9406d3b0073636a3a2e80db05a02f0c3169b5632022b4e81c0364bcda5"},
+    {file = "regex-2023.12.25-cp312-cp312-win_amd64.whl", hash = "sha256:cc37b9aeebab425f11f27e5e9e6cf580be7206c6582a64467a14dda211abc232"},
+    {file = "regex-2023.12.25-cp37-cp37m-macosx_10_9_x86_64.whl", hash = "sha256:da695d75ac97cb1cd725adac136d25ca687da4536154cdc2815f576e4da11c69"},
+    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:d126361607b33c4eb7b36debc173bf25d7805847346dd4d99b5499e1fef52bc7"},
+    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:4719bb05094d7d8563a450cf8738d2e1061420f79cfcc1fa7f0a44744c4d8f73"},
+    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:5dd58946bce44b53b06d94aa95560d0b243eb2fe64227cba50017a8d8b3cd3e2"},
+    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:22a86d9fff2009302c440b9d799ef2fe322416d2d58fc124b926aa89365ec482"},
+    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:2aae8101919e8aa05ecfe6322b278f41ce2994c4a430303c4cd163fef746e04f"},
+    {file = "regex-2023.12.25-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl", hash = "sha256:e692296c4cc2873967771345a876bcfc1c547e8dd695c6b89342488b0ea55cd8"},
+    {file = "regex-2023.12.25-cp37-cp37m-musllinux_1_1_aarch64.whl", hash = "sha256:263ef5cc10979837f243950637fffb06e8daed7f1ac1e39d5910fd29929e489a"},
+    {file = "regex-2023.12.25-cp37-cp37m-musllinux_1_1_i686.whl", hash = "sha256:d6f7e255e5fa94642a0724e35406e6cb7001c09d476ab5fce002f652b36d0c39"},
+    {file = "regex-2023.12.25-cp37-cp37m-musllinux_1_1_ppc64le.whl", hash = "sha256:88ad44e220e22b63b0f8f81f007e8abbb92874d8ced66f32571ef8beb0643b2b"},
+    {file = "regex-2023.12.25-cp37-cp37m-musllinux_1_1_s390x.whl", hash = "sha256:3a17d3ede18f9cedcbe23d2daa8a2cd6f59fe2bf082c567e43083bba3fb00347"},
+    {file = "regex-2023.12.25-cp37-cp37m-musllinux_1_1_x86_64.whl", hash = "sha256:d15b274f9e15b1a0b7a45d2ac86d1f634d983ca40d6b886721626c47a400bf39"},
+    {file = "regex-2023.12.25-cp37-cp37m-win32.whl", hash = "sha256:ed19b3a05ae0c97dd8f75a5d8f21f7723a8c33bbc555da6bbe1f96c470139d3c"},
+    {file = "regex-2023.12.25-cp37-cp37m-win_amd64.whl", hash = "sha256:a6d1047952c0b8104a1d371f88f4ab62e6275567d4458c1e26e9627ad489b445"},
+    {file = "regex-2023.12.25-cp38-cp38-macosx_10_9_universal2.whl", hash = "sha256:b43523d7bc2abd757119dbfb38af91b5735eea45537ec6ec3a5ec3f9562a1c53"},
+    {file = "regex-2023.12.25-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:efb2d82f33b2212898f1659fb1c2e9ac30493ac41e4d53123da374c3b5541e64"},
+    {file = "regex-2023.12.25-cp38-cp38-macosx_11_0_arm64.whl", hash = "sha256:b7fca9205b59c1a3d5031f7e64ed627a1074730a51c2a80e97653e3e9fa0d415"},
+    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:086dd15e9435b393ae06f96ab69ab2d333f5d65cbe65ca5a3ef0ec9564dfe770"},
+    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:e81469f7d01efed9b53740aedd26085f20d49da65f9c1f41e822a33992cb1590"},
+    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:34e4af5b27232f68042aa40a91c3b9bb4da0eeb31b7632e0091afc4310afe6cb"},
+    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:9852b76ab558e45b20bf1893b59af64a28bd3820b0c2efc80e0a70a4a3ea51c1"},
+    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:ff100b203092af77d1a5a7abe085b3506b7eaaf9abf65b73b7d6905b6cb76988"},
+    {file = "regex-2023.12.25-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl", hash = "sha256:cc038b2d8b1470364b1888a98fd22d616fba2b6309c5b5f181ad4483e0017861"},
+    {file = "regex-2023.12.25-cp38-cp38-musllinux_1_1_aarch64.whl", hash = "sha256:094ba386bb5c01e54e14434d4caabf6583334090865b23ef58e0424a6286d3dc"},
+    {file = "regex-2023.12.25-cp38-cp38-musllinux_1_1_i686.whl", hash = "sha256:5cd05d0f57846d8ba4b71d9c00f6f37d6b97d5e5ef8b3c3840426a475c8f70f4"},
+    {file = "regex-2023.12.25-cp38-cp38-musllinux_1_1_ppc64le.whl", hash = "sha256:9aa1a67bbf0f957bbe096375887b2505f5d8ae16bf04488e8b0f334c36e31360"},
+    {file = "regex-2023.12.25-cp38-cp38-musllinux_1_1_s390x.whl", hash = "sha256:98a2636994f943b871786c9e82bfe7883ecdaba2ef5df54e1450fa9869d1f756"},
+    {file = "regex-2023.12.25-cp38-cp38-musllinux_1_1_x86_64.whl", hash = "sha256:37f8e93a81fc5e5bd8db7e10e62dc64261bcd88f8d7e6640aaebe9bc180d9ce2"},
+    {file = "regex-2023.12.25-cp38-cp38-win32.whl", hash = "sha256:d78bd484930c1da2b9679290a41cdb25cc127d783768a0369d6b449e72f88beb"},
+    {file = "regex-2023.12.25-cp38-cp38-win_amd64.whl", hash = "sha256:b521dcecebc5b978b447f0f69b5b7f3840eac454862270406a39837ffae4e697"},
+    {file = "regex-2023.12.25-cp39-cp39-macosx_10_9_universal2.whl", hash = "sha256:f7bc09bc9c29ebead055bcba136a67378f03d66bf359e87d0f7c759d6d4ffa31"},
+    {file = "regex-2023.12.25-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:e14b73607d6231f3cc4622809c196b540a6a44e903bcfad940779c80dffa7be7"},
+    {file = "regex-2023.12.25-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:9eda5f7a50141291beda3edd00abc2d4a5b16c29c92daf8d5bd76934150f3edc"},
+    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl", hash = "sha256:cc6bb9aa69aacf0f6032c307da718f61a40cf970849e471254e0e91c56ffca95"},
+    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl", hash = "sha256:298dc6354d414bc921581be85695d18912bea163a8b23cac9a2562bbcd5088b1"},
+    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_17_s390x.manylinux2014_s390x.whl", hash = "sha256:2f4e475a80ecbd15896a976aa0b386c5525d0ed34d5c600b6d3ebac0a67c7ddf"},
+    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl", hash = "sha256:531ac6cf22b53e0696f8e1d56ce2396311254eb806111ddd3922c9d937151dae"},
+    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl", hash = "sha256:22f3470f7524b6da61e2020672df2f3063676aff444db1daa283c2ea4ed259d6"},
+    {file = "regex-2023.12.25-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl", hash = "sha256:89723d2112697feaa320c9d351e5f5e7b841e83f8b143dba8e2d2b5f04e10923"},
+    {file = "regex-2023.12.25-cp39-cp39-musllinux_1_1_aarch64.whl", hash = "sha256:0ecf44ddf9171cd7566ef1768047f6e66975788258b1c6c6ca78098b95cf9a3d"},
+    {file = "regex-2023.12.25-cp39-cp39-musllinux_1_1_i686.whl", hash = "sha256:905466ad1702ed4acfd67a902af50b8db1feeb9781436372261808df7a2a7bca"},
+    {file = "regex-2023.12.25-cp39-cp39-musllinux_1_1_ppc64le.whl", hash = "sha256:4558410b7a5607a645e9804a3e9dd509af12fb72b9825b13791a37cd417d73a5"},
+    {file = "regex-2023.12.25-cp39-cp39-musllinux_1_1_s390x.whl", hash = "sha256:7e316026cc1095f2a3e8cc012822c99f413b702eaa2ca5408a513609488cb62f"},
+    {file = "regex-2023.12.25-cp39-cp39-musllinux_1_1_x86_64.whl", hash = "sha256:3b1de218d5375cd6ac4b5493e0b9f3df2be331e86520f23382f216c137913d20"},
+    {file = "regex-2023.12.25-cp39-cp39-win32.whl", hash = "sha256:11a963f8e25ab5c61348d090bf1b07f1953929c13bd2309a0662e9ff680763c9"},
+    {file = "regex-2023.12.25-cp39-cp39-win_amd64.whl", hash = "sha256:e693e233ac92ba83a87024e1d32b5f9ab15ca55ddd916d878146f4e3406b5c91"},
+    {file = "regex-2023.12.25.tar.gz", hash = "sha256:29171aa128da69afdf4bde412d5bedc335f2ca8fcfe4489038577d05f16181e5"},
+]
+
+[[package]]
+name = "requests"
+version = "2.31.0"
+description = "Python HTTP for Humans."
+optional = false
+python-versions = ">=3.7"
+files = [
+    {file = "requests-2.31.0-py3-none-any.whl", hash = "sha256:58cd2187c01e70e6e26505bca751777aa9f2ee0b7f4300988b709f44e013003f"},
+    {file = "requests-2.31.0.tar.gz", hash = "sha256:942c5a758f98d790eaed1a29cb6eefc7ffb0d1cf7af05c3d2791656dbd6ad1e1"},
+]
+
+[package.dependencies]
+certifi = ">=2017.4.17"
+charset-normalizer = ">=2,<4"
+idna = ">=2.5,<4"
+urllib3 = ">=1.21.1,<3"
+
+[package.extras]
+socks = ["PySocks (>=1.5.6,!=1.5.7)"]
+use-chardet-on-py3 = ["chardet (>=3.0.2,<6)"]
+
+[[package]]
+name = "six"
+version = "1.16.0"
+description = "Python 2 and 3 compatibility utilities"
+optional = false
+python-versions = ">=2.7, !=3.0.*, !=3.1.*, !=3.2.*"
+files = [
+    {file = "six-1.16.0-py2.py3-none-any.whl", hash = "sha256:8abb2f1d86890a2dfb989f9a77cfcfd3e47c2a354b01111771326f8aa26e0254"},
+    {file = "six-1.16.0.tar.gz", hash = "sha256:1e61c37477a1626458e36f7b1d82aa5c9b094fa4802892072e49de9c60c4c926"},
+]
+
+[[package]]
+name = "urllib3"
+version = "2.2.1"
+description = "HTTP library with thread-safe connection pooling, file post, and more."
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "urllib3-2.2.1-py3-none-any.whl", hash = "sha256:450b20ec296a467077128bff42b73080516e71b56ff59a60a02bef2232c4fa9d"},
+    {file = "urllib3-2.2.1.tar.gz", hash = "sha256:d0570876c61ab9e520d776c38acbbb5b05a776d3f9ff98a5c8fd5162a444cf19"},
+]
+
+[package.extras]
+brotli = ["brotli (>=1.0.9)", "brotlicffi (>=0.8.0)"]
+h2 = ["h2 (>=4,<5)"]
+socks = ["pysocks (>=1.5.6,!=1.5.7,<2.0)"]
+zstd = ["zstandard (>=0.18.0)"]
+
+[[package]]
+name = "watchdog"
+version = "4.0.0"
+description = "Filesystem events monitoring"
+optional = false
+python-versions = ">=3.8"
+files = [
+    {file = "watchdog-4.0.0-cp310-cp310-macosx_10_9_universal2.whl", hash = "sha256:39cb34b1f1afbf23e9562501673e7146777efe95da24fab5707b88f7fb11649b"},
+    {file = "watchdog-4.0.0-cp310-cp310-macosx_10_9_x86_64.whl", hash = "sha256:c522392acc5e962bcac3b22b9592493ffd06d1fc5d755954e6be9f4990de932b"},
+    {file = "watchdog-4.0.0-cp310-cp310-macosx_11_0_arm64.whl", hash = "sha256:6c47bdd680009b11c9ac382163e05ca43baf4127954c5f6d0250e7d772d2b80c"},
+    {file = "watchdog-4.0.0-cp311-cp311-macosx_10_9_universal2.whl", hash = "sha256:8350d4055505412a426b6ad8c521bc7d367d1637a762c70fdd93a3a0d595990b"},
+    {file = "watchdog-4.0.0-cp311-cp311-macosx_10_9_x86_64.whl", hash = "sha256:c17d98799f32e3f55f181f19dd2021d762eb38fdd381b4a748b9f5a36738e935"},
+    {file = "watchdog-4.0.0-cp311-cp311-macosx_11_0_arm64.whl", hash = "sha256:4986db5e8880b0e6b7cd52ba36255d4793bf5cdc95bd6264806c233173b1ec0b"},
+    {file = "watchdog-4.0.0-cp312-cp312-macosx_10_9_universal2.whl", hash = "sha256:11e12fafb13372e18ca1bbf12d50f593e7280646687463dd47730fd4f4d5d257"},
+    {file = "watchdog-4.0.0-cp312-cp312-macosx_10_9_x86_64.whl", hash = "sha256:5369136a6474678e02426bd984466343924d1df8e2fd94a9b443cb7e3aa20d19"},
+    {file = "watchdog-4.0.0-cp312-cp312-macosx_11_0_arm64.whl", hash = "sha256:76ad8484379695f3fe46228962017a7e1337e9acadafed67eb20aabb175df98b"},
+    {file = "watchdog-4.0.0-cp38-cp38-macosx_10_9_universal2.whl", hash = "sha256:45cc09cc4c3b43fb10b59ef4d07318d9a3ecdbff03abd2e36e77b6dd9f9a5c85"},
+    {file = "watchdog-4.0.0-cp38-cp38-macosx_10_9_x86_64.whl", hash = "sha256:eed82cdf79cd7f0232e2fdc1ad05b06a5e102a43e331f7d041e5f0e0a34a51c4"},
+    {file = "watchdog-4.0.0-cp38-cp38-macosx_11_0_arm64.whl", hash = "sha256:ba30a896166f0fee83183cec913298151b73164160d965af2e93a20bbd2ab605"},
+    {file = "watchdog-4.0.0-cp39-cp39-macosx_10_9_universal2.whl", hash = "sha256:d18d7f18a47de6863cd480734613502904611730f8def45fc52a5d97503e5101"},
+    {file = "watchdog-4.0.0-cp39-cp39-macosx_10_9_x86_64.whl", hash = "sha256:2895bf0518361a9728773083908801a376743bcc37dfa252b801af8fd281b1ca"},
+    {file = "watchdog-4.0.0-cp39-cp39-macosx_11_0_arm64.whl", hash = "sha256:87e9df830022488e235dd601478c15ad73a0389628588ba0b028cb74eb72fed8"},
+    {file = "watchdog-4.0.0-pp310-pypy310_pp73-macosx_10_9_x86_64.whl", hash = "sha256:6e949a8a94186bced05b6508faa61b7adacc911115664ccb1923b9ad1f1ccf7b"},
+    {file = "watchdog-4.0.0-pp38-pypy38_pp73-macosx_10_9_x86_64.whl", hash = "sha256:6a4db54edea37d1058b08947c789a2354ee02972ed5d1e0dca9b0b820f4c7f92"},
+    {file = "watchdog-4.0.0-pp39-pypy39_pp73-macosx_10_9_x86_64.whl", hash = "sha256:d31481ccf4694a8416b681544c23bd271f5a123162ab603c7d7d2dd7dd901a07"},
+    {file = "watchdog-4.0.0-py3-none-manylinux2014_aarch64.whl", hash = "sha256:8fec441f5adcf81dd240a5fe78e3d83767999771630b5ddfc5867827a34fa3d3"},
+    {file = "watchdog-4.0.0-py3-none-manylinux2014_armv7l.whl", hash = "sha256:6a9c71a0b02985b4b0b6d14b875a6c86ddea2fdbebd0c9a720a806a8bbffc69f"},
+    {file = "watchdog-4.0.0-py3-none-manylinux2014_i686.whl", hash = "sha256:557ba04c816d23ce98a06e70af6abaa0485f6d94994ec78a42b05d1c03dcbd50"},
+    {file = "watchdog-4.0.0-py3-none-manylinux2014_ppc64.whl", hash = "sha256:d0f9bd1fd919134d459d8abf954f63886745f4660ef66480b9d753a7c9d40927"},
+    {file = "watchdog-4.0.0-py3-none-manylinux2014_ppc64le.whl", hash = "sha256:f9b2fdca47dc855516b2d66eef3c39f2672cbf7e7a42e7e67ad2cbfcd6ba107d"},
+    {file = "watchdog-4.0.0-py3-none-manylinux2014_s390x.whl", hash = "sha256:73c7a935e62033bd5e8f0da33a4dcb763da2361921a69a5a95aaf6c93aa03a87"},
+    {file = "watchdog-4.0.0-py3-none-manylinux2014_x86_64.whl", hash = "sha256:6a80d5cae8c265842c7419c560b9961561556c4361b297b4c431903f8c33b269"},
+    {file = "watchdog-4.0.0-py3-none-win32.whl", hash = "sha256:8f9a542c979df62098ae9c58b19e03ad3df1c9d8c6895d96c0d51da17b243b1c"},
+    {file = "watchdog-4.0.0-py3-none-win_amd64.whl", hash = "sha256:f970663fa4f7e80401a7b0cbeec00fa801bf0287d93d48368fc3e6fa32716245"},
+    {file = "watchdog-4.0.0-py3-none-win_ia64.whl", hash = "sha256:9a03e16e55465177d416699331b0f3564138f1807ecc5f2de9d55d8f188d08c7"},
+    {file = "watchdog-4.0.0.tar.gz", hash = "sha256:e3e7065cbdabe6183ab82199d7a4f6b3ba0a438c5a512a68559846ccb76a78ec"},
+]
+
+[package.extras]
+watchmedo = ["PyYAML (>=3.10)"]
+
+[metadata]
+lock-version = "2.0"
+python-versions = "^3.11"
+content-hash = "eb59b66f1230e1504b940568b5e30b8bd6b02c4a4cf458bf13275a3630115051"
diff --git a/requirements.txt b/requirements.txt
index ad88686..0e10074 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,36 +1,34 @@
-Babel==2.14.0
-black==24.2.0
-certifi==2024.2.2
-charset-normalizer==3.3.2
-click==8.1.7
-colorama==0.4.6
-flake8==7.0.0
-ghp-import==2.1.0
-idna==3.6
-Jinja2==3.1.3
-Markdown==3.5.2
-MarkupSafe==2.1.5
-mccabe==0.7.0
-mergedeep==1.3.4
-mkdocs==1.5.3
-mkdocs-material==9.5.12
-mkdocs-material-extensions==1.3.1
-mypy-extensions==1.0.0
-nose==1.3.7
-packaging==23.2
-paginate==0.5.6
-pathspec==0.12.1
-platformdirs==4.2.0
-pycodestyle==2.11.1
-pyflakes==3.2.0
-Pygments==2.17.2
-pymdown-extensions==10.7
-python-dateutil==2.9.0.post0
-python-dotenv==1.0.1
-PyYAML==6.0.1
-pyyaml_env_tag==0.1
-regex==2023.12.25
-requests==2.31.0
-six==1.16.0
-urllib3==2.2.1
-watchdog==4.0.0
+# Copyright (c) 2024-2025 TuxTechLabs <root.tuxtechlabs@gmail.com>
+
+# 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 NON-INFRINGEMENT. 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.
+
+# Requirements for core
+jinja2~=3.0
+markdown~=3.2
+mkdocs~=1.6
+mkdocs-material-extensions~=1.3
+pygments~=2.16
+pymdown-extensions~=10.2
+
+# Requirements for plugins
+babel~=2.10
+colorama~=0.4
+paginate~=0.5
+regex>=2022.4
+requests~=2.26
\ No newline at end of file
diff --git a/scripts/check_dependencies.sh b/scripts/check_dependencies.sh
index 35aa108..4912f24 100644
--- a/scripts/check_dependencies.sh
+++ b/scripts/check_dependencies.sh
@@ -3,8 +3,8 @@
 
 #################################################################
 #                                                               #
-#      Author        :  Arindam Tanti                           #
-#      Email Address :  arindamtanti123@gmail.com               #
+#      Author        :  TuxTechLab.com                          #
+#      Email Address :  root.tuxtechlab@gmail.com               #
 #                                                               #
 #      Description   :  This script validates the environment   #
 #                       for Docker Swarm, Python3, Poetry,      #
diff --git a/scripts/manage_compose.sh b/scripts/manage_compose.sh
index 0224aeb..929e6a4 100644
--- a/scripts/manage_compose.sh
+++ b/scripts/manage_compose.sh
@@ -2,8 +2,8 @@
 
 ##############################################################
 #                                                            #
-#      Author        :  Arindam Tanti                        #
-#      Email Address :  iamarindamtanti@gmail.com            #
+#      Author        :  TuxTechLab.com                       #
+#      Email Address :  root.tuxtechlab@gmail.com            #
 #                                                            #
 #      Description   :  This script helps you to start,      #
 #                       stop, update, and scale the blogs    #
@@ -18,7 +18,7 @@
 # set -e # Disabled Exit on Error to capture errors.
 set -o pipefail # Checks for any pipe failures
 
-logfile="../logs/blog-compose-$(date +'%d-%m-%Y').log"
+logfile="../logs/blog-stack-$(date +'%d-%m-%Y-%H:%M').log"
 
 # Help function to display usage instructions
 help(){
diff --git a/scripts/manage_stack.sh b/scripts/manage_stack.sh
index e47703a..1a0a941 100644
--- a/scripts/manage_stack.sh
+++ b/scripts/manage_stack.sh
@@ -2,8 +2,8 @@
 
 ##############################################################
 #                                                            #
-#      Author        :  Arindam Tanti                        #
-#      Email Address :  iamarindamtanti@gmail.com             #
+#      Author        :  TuxTechLab.com                       #
+#      Email Address :  root.tuxtechlab@gmail.com            #
 #                                                            #
 #      Description   :  This script helps you to start,      #
 #                       stop, update, scale the blogs stack  #
@@ -17,7 +17,7 @@
 # set -e # Disabled Exit on Error to capture errors.
 set -o pipefail # Checks for any pipefails
 
-logfile="../logs/blog-stack-$(date +'%d-%m-%Y').log"
+logfile="../logs/blog-stack-$(date +'%d-%m-%Y-%H:%M').log"
 
 # Help function to display usage instructions
 help(){
@@ -39,34 +39,38 @@ help(){
     exit 1
 }
 
+logger(){
+    echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] | $1" | tee -a $logfile
+}
+
 # Function to deploy a stack
 stack_deploy(){
     local stack_name=$1
     img_spec="blogs:$(date +%Y%m%d-%H-%M-%S)"
     # Setting Up the logfile
-    echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (INFO) | Starting Blogs Stack Deploy." | tee -a $logfile
+    logger "(INFO) | Starting Blogs Stack Deploy."
 
     # Check if Docker is running in Swarm mode
     if docker info | grep -q "Swarm: active"; then
-        echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (INFO) | Docker is running in Swarm mode." | tee -a $logfile
-        echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (INFO) | Proceeding to Building Container and Deploying Application Stack..." | tee -a $logfile
+        logger "(INFO) | Docker is running in Swarm mode."
+        logger "(INFO) | Proceeding to Building Container and Deploying Application Stack..."
         
         # Build a new Docker image with the Dockerfile and tag it
-        echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (INFO) | Building Container Image [ $img_spec ]" | tee -a $logfile
-        cp ../mkdocs_blogs.Dockerfile ../Dockerfile | tee -a $logfile
-        docker build -t $img_spec ".." --no-cache | tee -a $logfile
+        logger "(INFO) | Building Container Image [ $img_spec ]"
+        cp ../mkdocs_blogs.Dockerfile ../Dockerfile
+        docker build -t $img_spec ".." --no-cache
         rm ../Dockerfile
-        docker image ls $img_spec | tee -a $logfile
+        docker image ls $img_spec
 
         # Run Docker stack deploy with the specified service file
-        echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (INFO) | Deploying Docker Stack: [ $stack_name ]" | tee -a $logfile
-        docker stack deploy -c "../blogs-stack.yml" "$stack_name" | tee -a $logfile
-        sleep 10 | tee -a $logfile
-        docker service ls | grep "blogs:" | tee -a $logfile
+        logger "(INFO) | Deploying Docker Stack: [ $stack_name ]"
+        docker stack deploy -c "../blogs-stack.yml" "$stack_name"
+        sleep 10
+        docker service ls | grep "blogs:"
 
-        echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (INFO) | Docker Stack [ $stack_name ] Started Successfully." | tee -a $logfile
+        logger "(INFO) | Docker Stack [ $stack_name ] Started Successfully."
     else
-        echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (ERROR) | Error: Docker is not running in Swarm mode. Please enable Swarm mode to deploy Blogs stacks." | tee -a $logfile
+        logger "(ERROR) | Error: Docker is not running in Swarm mode. Please enable Swarm mode to deploy Blogs stacks."
         exit 1
     fi
 }
@@ -76,14 +80,14 @@ stop_stack(){
     local stack_name=$1
     
     # Stop the Docker stack
-    echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (INFO) | Stopping Docker Stack: $stack_name" | tee -a $logfile
-    docker stack rm "$stack_name" | tee -a $logfile
+    logger "(INFO) | Stopping Docker Stack: $stack_name"
+    docker stack rm "$stack_name"
 }
 
 # Function to restart a stack
 restart_stack(){
     local stack_name=$1
-    echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (INFO) | Restaring Docker Stack: $stack_name" | tee -a $logfile
+    logger "(INFO) | Restaring Docker Stack: $stack_name"
     stop_stack $stack_name 
     sleep 5
     stack_deploy $stack_name
@@ -97,8 +101,8 @@ update_stack(){
     local stack_name=$1
     
     # Update the Docker stack
-    echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (INFO) | Updating Docker Stack: $stack_name" | tee -a $logfile
-    docker stack deploy -c "../blogs-stack.yml" "$stack_name" | tee -a $logfile
+    logger "(INFO) | Updating Docker Stack: $stack_name"
+    docker stack deploy -c "../blogs-stack.yml" "$stack_name"
 }
 
 # Function to scale a stack
@@ -108,14 +112,14 @@ scale_stack(){
     local replicas=$3
     
     # Scale the specified service in the Docker stack
-    echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (INFO) | Scaling Service: $service_name in Stack: $stack_name to $replicas replicas" | tee -a $logfile
-    docker service scale "$stack_name"_"$service_name"="$replicas" | tee -a $logfile
+    logger "(INFO) | Scaling Service: $service_name in Stack: $stack_name to $replicas replicas"
+    docker service scale "$stack_name"_"$service_name"="$replicas"
 }
 
 # Function to list running stacks
 list_stacks(){
-    echo "[ $(date +'%d-%m-%Y %H:%M:%S') ] (INFO) | Listing All running Docker Stacks:" | tee -a $logfile
-    docker ps --format 'table {{.Names}}\t{{.Status}}\t{{.Ports}}' | tee -a $logfile
+    logger "(INFO) | Listing All running Docker Stacks:"
+    docker ps --format 'table {{.Names}}\t{{.Status}}\t{{.Ports}}'
 }
 
 # Main function to parse command-line arguments and execute corresponding functions
diff --git a/sweep.yaml b/sweep.yaml
index e2c3de3..f1652d9 100644
--- a/sweep.yaml
+++ b/sweep.yaml
@@ -1,43 +1,43 @@
-# Sweep AI turns bugs & feature requests into code changes (https://sweep.dev)
-# For details on our config file, check out our docs at https://docs.sweep.dev/usage/config
-
-# This setting contains a list of rules that Sweep will check for. If any of these rules are broken in a new commit, Sweep will create an pull request to fix the broken rule.
-rules:
-- "All new business logic should have corresponding unit tests."
-- "Refactor large functions to be more modular."
-- "Add docstrings to all functions and file headers."
-
-# This is the branch that Sweep will develop from and make pull requests to. Most people use 'main' or 'master' but some users also use 'dev' or 'staging'.
-branch: 'main'
-
-# By default Sweep will read the logs and outputs from your existing Github Actions. To disable this, set this to false.
-gha_enabled: True
-
-# This is the description of your project. It will be used by sweep when creating PRs. You can tell Sweep what's unique about your project, what frameworks you use, or anything else you want.
-#
-# Example:
-#
-# description: sweepai/sweep is a python project. The main api endpoints are in sweepai/api.py. Write code that adheres to PEP8.
-description: ''
-
-# This sets whether to create pull requests as drafts. If this is set to True, then all pull requests will be created as drafts and GitHub Actions will not be triggered.
-draft: False
-
-# This is a list of directories that Sweep will not be able to edit.
-blocked_dirs: []
-
-# This is a list of documentation links that Sweep will use to help it understand your code. You can add links to documentation for any packages you use here.
-#
-# Example:
-#
-# docs:
-#   - PyGitHub: ["https://pygithub.readthedocs.io/en/latest/", "We use pygithub to interact with the GitHub API"]
-docs: []
-
-# Sandbox executes commands in a sandboxed environment to validate code changes after every edit to guarantee pristine code. For more details, see the [Sandbox](./sandbox) page.
-sandbox:
-  install:
-    - trunk init
-  check:
-    - trunk fmt {file_path} || return 0
-    - trunk check --fix --print-failures {file_path}
+# Sweep AI turns bugs & feature requests into code changes (https://sweep.dev)
+# For details on our config file, check out our docs at https://docs.sweep.dev/usage/config
+
+# This setting contains a list of rules that Sweep will check for. If any of these rules are broken in a new commit, Sweep will create an pull request to fix the broken rule.
+rules:
+- "All new business logic should have corresponding unit tests."
+- "Refactor large functions to be more modular."
+- "Add docstrings to all functions and file headers."
+
+# This is the branch that Sweep will develop from and make pull requests to. Most people use 'main' or 'master' but some users also use 'dev' or 'staging'.
+branch: 'main'
+
+# By default Sweep will read the logs and outputs from your existing Github Actions. To disable this, set this to false.
+gha_enabled: True
+
+# This is the description of your project. It will be used by sweep when creating PRs. You can tell Sweep what's unique about your project, what frameworks you use, or anything else you want.
+#
+# Example:
+#
+# description: sweepai/sweep is a python project. The main api endpoints are in sweepai/api.py. Write code that adheres to PEP8.
+description: ''
+
+# This sets whether to create pull requests as drafts. If this is set to True, then all pull requests will be created as drafts and GitHub Actions will not be triggered.
+draft: False
+
+# This is a list of directories that Sweep will not be able to edit.
+blocked_dirs: []
+
+# This is a list of documentation links that Sweep will use to help it understand your code. You can add links to documentation for any packages you use here.
+#
+# Example:
+#
+# docs:
+#   - PyGitHub: ["https://pygithub.readthedocs.io/en/latest/", "We use pygithub to interact with the GitHub API"]
+docs: []
+
+# Sandbox executes commands in a sandboxed environment to validate code changes after every edit to guarantee pristine code. For more details, see the [Sandbox](./sandbox) page.
+sandbox:
+  install:
+    - trunk init
+  check:
+    - trunk fmt {file_path} || return 0
+    - trunk check --fix --print-failures {file_path}