Adding categories

docs/artifact-storage/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Artifact Storage",
+    "position": 10,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/artifact-storage/introduction.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is an Artifact?
+
+An artifact is a deployable component of your application. It can be a compiled binary, a library, a Docker image, or any other file that is part of your application. Artifacts are stored in an artifact repository, which is a collection of all the artifacts that are part of your application.

docs/chaos-engineering/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Chaos Engineering",
+    "position": 21,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/chaos-engineering/introduction.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is Chaos Engineering?
+
+Chaos engineering is the practice of intentionally introducing failure into a system in order to test its resilience and reliability. It is a way to proactively identify and address weaknesses in a system, and it is used to ensure that a system can continue to function in the face of unexpected events and conditions.

docs/ci-cd/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "CI/CD",
+    "position": 9,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/ci-cd/continuous-integration.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# Continuous Integration
+
+Continuous Integration (CI) is a software development practice where developers regularly merge their code changes into a central repository, after which automated builds and tests are run. The key goals of CI are to find and address bugs quicker, improve software quality, and reduce the time it takes to validate and release new software updates.

docs/cloud/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Cloud",
+    "position": 7,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/cloud/cloud-patterns.md

@@ -0,0 +1,5 @@
+---
+sidebar_position: 3
+---
+
+# Cloud Patterns

docs/cloud/cloud-providers.md

@@ -0,0 +1,5 @@
+---
+sidebar_position: 2
+---
+
+# Cloud Providers

docs/cloud/what-is-cloud.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is Cloud?
+
+The cloud is a network of servers that are hosted on the internet. These servers store and manage data, run applications, and deliver content or services such as streaming videos, webmail, office productivity software, and social media.

docs/code-analysis/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Code Analysis",
+    "position": 15,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/code-analysis/introduction.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is Code Analysis?
+
+Code analysis is the process of analyzing source code to find bugs, security vulnerabilities, and other issues. It is an essential part of the software development process, as it helps to ensure that the code is of high quality and free from defects. Code analysis tools can be used to automate the process of finding and fixing issues in the code, which can help to improve the overall quality of the software.

docs/container-orchestrator/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Container Orchestrator",
+    "position": 11,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/container-orchestrator/introduction.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is Container Orchestration?
+
+Container orchestration is the process of managing the lifecycle of containers, especially in large, dynamic environments. It involves automating the deployment, scaling, and management of containerized applications. Container orchestration tools provide a platform for defining, deploying, and managing a set of interconnected containers.

docs/containers/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Containers",
+    "position": 5,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/containers/container.md

@@ -0,0 +1,5 @@
+---
+sidebar_position: 1
+---
+
+# What is a Container?

docs/containers/image.md

@@ -0,0 +1,5 @@
+---
+sidebar_position: 2
+---
+
+# What is an Image?

docs/disaster-recovery/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Disaster Recovery",
+    "position": 13,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/disaster-recovery/backups.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 2
+---
+
+# What is a Backup?
+
+A backup is a copy of data that is stored separately from the original data. Backups are used to restore data to its original state after data loss or corruption. Backups are essential for disaster recovery and data protection. They are used to recover data in case of hardware failure, software failure, data corruption, accidental deletion, or other data loss events.

docs/disaster-recovery/introduction.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is Disaster Recovery?
+
+Disaster recovery is the process of recovering data and resuming business operations after a disaster.

docs/environments-definition/_category_.json

@@ -0,0 +1,7 @@
+{
+  "label": "Environments Definition",
+  "position": 6,
+  "link": {
+    "type": "generated-index"
+  }
+}

docs/environments-definition/environment.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is an Environment?
+
+An environment is a collection of resources that are used to run an application. These resources include the infrastructure, configuration, and services that are required to run the application. An environment can be a development, testing, staging, or production environment.

docs/feature-flags/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Feature Flags",
+    "position": 20,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/feature-flags/introduction.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is Feature Flags?
+
+Feature flags are a way to manage the lifecycle of a feature in a software application. They are a way to control the visibility and behavior of a feature, and they are used to enable or disable a feature at runtime. Feature flags are a way to manage the release of new features, and they are used to control the rollout of new functionality to different groups of users.

docs/finops/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "FinOps",
+    "position": 18,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/finops/cloud-finops.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 2
+---
+
+# What is Cloud FinOps?
+
+Cloud FinOps is a set of practices and techniques that enable teams to manage and optimize their cloud costs. It is a way to align the goals of the finance, engineering, and business teams, and to ensure that cloud resources are being used efficiently and effectively. FinOps is a way to manage cloud costs in a more incremental and iterative manner, allowing teams to monitor and optimize their cloud spending in real time.

docs/finops/greenops.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 3
+---
+
+# What is GreenOps?
+
+GreenOps is a set of practices and techniques that enable teams to build and operate sustainable and environmentally friendly software. It is a way to deliver software in a more sustainable and responsible manner, allowing teams to reduce the environmental impact of their applications and infrastructure.

docs/finops/introduction.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is FinOps?
+
+FinOps is a set of practices and techniques that enable teams to manage and optimize their cloud costs. It is a way to align the goals of the finance, engineering, and business teams, and to ensure that cloud resources are being used efficiently and effectively. FinOps is a way to manage cloud costs in a more incremental and iterative manner, allowing teams to monitor and optimize their cloud spending in real time.

docs/gitops/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "GitOps",
+    "position": 12,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/gitops/introduction.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is GitOps?
+
+GitOps is a way to do Kubernetes cluster management and application delivery. It works by using Git as a single source of truth for declarative infrastructure and applications. With Git at the center of your delivery pipelines, developers can make pull requests to accelerate and simplify application deployments and operations tasks to Kubernetes.

docs/infrastructure-as-code/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Infrastructure as Code",
+    "position": 8,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/infrastructure-as-code/alternatives.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 4
+---
+
+# Alternative IaC Tools
+
+Infrastructure as Code (IaC) is the process of managing and provisioning computing infrastructure through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. IaC is a key DevOps practice and is used to manage and provision infrastructure in a safe, repeatable, and efficient manner.

docs/infrastructure-as-code/infrastucture-as-code.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is IaC?
+
+Infrastructure as Code (IaC) is the process of managing and provisioning computing infrastructure (processes, storage, networks, and other resources) through machine-readable files, rather than physical hardware configuration or interactive configuration tools.

docs/infrastructure-as-code/opentofu.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 3
+---
+
+# OpenToFu
+
+OpenToFu is a set of tools and best practices for managing infrastructure as code (IaC) and cloud resources. It is designed to help you manage your infrastructure in a way that is consistent, repeatable, and scalable.

docs/infrastructure-as-code/terraform.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 2
+---
+
+# Terraform
+
+Terraform is an open-source infrastructure as code software tool created by HashiCorp. It enables users to define and provision a datacenter infrastructure using a high-level configuration language known as Hashicorp Configuration Language (HCL), or optionally JSON.

docs/microservices-architecture/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Microservices Architecture",
+    "position": 4,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/microservices-architecture/microservice-vs-monolith.md

@@ -0,0 +1,9 @@
+---
+sidebar_position: 2
+---
+
+# Microservice vs Monolith
+
+## What is a Monolith?
+
+A monolith is a software application that is built as a single, indivisible unit. It is a single-tiered software application in which different components are combined into a single program from a single platform. The monolithic architecture is the traditional architecture for building software applications.

docs/microservices-architecture/microservice.md

@@ -0,0 +1,5 @@
+---
+sidebar_position: 1
+---
+
+# What is a Microservice?

docs/observability/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Observability",
+    "position": 14,
+    "link": {
+      "type": "generated-index"
+    }
+  }
+

docs/observability/introduction.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 1
+---
+
+# What is Observability?
+
+Observability is a measure of how well internal states of a system can be inferred from knowledge of its external outputs. It helps to understand the behavior of a system by analyzing its outputs. Observability is a key concept in the field of control theory, which is the study of how to control systems. It is also a key concept in the field of systems engineering, which is the study of how to design and manage systems.

docs/observability/logging.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 3
+---
+
+# Logging
+
+Logging is the process of recording events that occur in a system. It is a critical part of observability, as it provides a record of what has happened in a system. This record can be used to understand the state of the system, diagnose problems, and monitor performance.

docs/observability/monitoring.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 2
+---
+
+# Monitoring
+
+Monitoring is the process of observing and tracking the performance of a system. It is a critical part of maintaining the health and reliability of a system. Monitoring can be used to detect and diagnose problems, and to ensure that a system is performing as expected.

docs/observability/profiling.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 5
+---
+
+# Profiling
+
+Profiling is the process of analyzing the performance of a system to identify bottlenecks and areas for optimization. Profiling can be used to identify performance issues, such as slow response times, high CPU usage, and memory leaks. Profiling tools can be used to collect data about the performance of a system, and to analyze that data to identify performance issues.

docs/observability/tracing.md

@@ -0,0 +1,5 @@
+---
+sidebar_position: 4
+---
+
+# Tracing