From 2f37052a701a89764104e626def2a9826a42797b Mon Sep 17 00:00:00 2001
From: Dennis van Kekem <dennis.vankekem@redkubes.com>
Date: Wed, 3 Jan 2024 15:23:42 +0100
Subject: [PATCH] fix/ added .md to internal routes and fixed broken links

---
 community/expectations.md                     |  2 +-
 community/welcome.md                          |  6 +--
 docs/apps/alertmanager.md                     |  2 +-
 docs/apps/certmanager.md                      |  2 +-
 docs/apps/grafana.md                          |  2 +-
 docs/apps/loki.md                             |  2 +-
 docs/for-devs/console/apps.md                 |  2 +-
 docs/for-devs/get-started/lab-1.md            |  2 +-
 docs/for-devs/get-started/lab-11.md           |  2 +-
 docs/for-devs/get-started/lab-22.md           |  6 +--
 docs/for-devs/get-started/lab-23.md           |  2 +-
 docs/for-devs/get-started/lab-28.md           |  4 +-
 docs/for-devs/get-started/lab-29.md           |  2 +-
 docs/for-devs/get-started/lab-30.md           |  2 +-
 docs/for-devs/get-started/lab-8.md            |  2 +-
 docs/for-devs/get-started/lab-9.md            |  2 +-
 docs/for-devs/get-started/overview.md         | 48 +++++++++----------
 docs/for-ops/cli/deploying.md                 |  4 +-
 docs/for-ops/cli/installation.md              | 40 ++++++++--------
 docs/for-ops/console/apps.md                  |  2 +-
 docs/for-ops/console/builds.md                |  2 +-
 docs/for-ops/console/clusters.md              |  2 +-
 docs/for-ops/console/overview.md              | 34 ++++++-------
 docs/for-ops/console/secrets.md               |  2 +-
 .../for-ops/console/settings/co-monitoring.md |  2 +-
 docs/for-ops/console/teams.md                 |  2 +-
 docs/for-ops/console/workloads.md             |  2 +-
 docs/for-ops/how-to/overview.md               | 12 ++---
 docs/for-ops/sre/overview.md                  |  6 +--
 docs/get-started/_post-install.md             |  4 +-
 docs/get-started/activation.md                |  2 +-
 docs/get-started/chart.md                     |  4 +-
 docs/get-started/installation/aws.md          |  2 +-
 docs/get-started/installation/azure.md        |  2 +-
 docs/get-started/installation/civo.md         |  2 +-
 docs/get-started/installation/digitalocean.md |  2 +-
 docs/get-started/installation/gcp.md          |  2 +-
 docs/get-started/installation/linode.md       |  2 +-
 docs/get-started/installation/scaleway.md     |  2 +-
 docs/get-started/installation/vultr.md        |  2 +-
 docs/get-started/overview.md                  |  2 +-
 docs/tutorials/overview.md                    |  2 +-
 42 files changed, 115 insertions(+), 115 deletions(-)

diff --git a/community/expectations.md b/community/expectations.md
index 57d4646ef..ca56034ad 100644
--- a/community/expectations.md
+++ b/community/expectations.md
@@ -25,7 +25,7 @@ Consequently, as a community we expect that all active participants in the commu
 
 ### Review comments
 
-Because reviewers are often the first points of contact between new members of the community and can significantly impact the first impression of the Otomi community, reviewers are especially important in shaping the Otomi community. Reviewers are highly encouraged to not only abide by the [code of conduct](code-of-conduct) but are strongly encouraged to go above and beyond the code of conduct to promote a collaborative, respectful Otomi community.
+Because reviewers are often the first points of contact between new members of the community and can significantly impact the first impression of the Otomi community, reviewers are especially important in shaping the Otomi community. Reviewers are highly encouraged to not only abide by the [code of conduct](code-of-conduct.md) but are strongly encouraged to go above and beyond the code of conduct to promote a collaborative, respectful Otomi community.
 
 ### Review latency
 
diff --git a/community/welcome.md b/community/welcome.md
index e09956614..9f57ababf 100644
--- a/community/welcome.md
+++ b/community/welcome.md
@@ -18,8 +18,8 @@ Before submitting code to Otomi, you should first complete the following prerequ
 
 ### Code of Conduct
 
-Please make sure to read and observe the [Code of Conduct](code-of-conduct) and
-[Community Values](community-values)
+Please make sure to read and observe the [Code of Conduct](code-of-conduct.md) and
+[Community Values](values.md)
 
 ### Developer guide
 
@@ -33,4 +33,4 @@ It is not required to set up a developer environment in order to contribute to O
 
 Otomi is a community project. Consequently, it is wholly dependent on its community to provide a productive, friendly and collaborative environment.
 
-Please read and review the [Contribution Expectations](expectations) for an understanding of code and review expectations.
+Please read and review the [Contribution Expectations](expectations.md) for an understanding of code and review expectations.
diff --git a/docs/apps/alertmanager.md b/docs/apps/alertmanager.md
index 36b7491b6..c520d3e9a 100644
--- a/docs/apps/alertmanager.md
+++ b/docs/apps/alertmanager.md
@@ -6,7 +6,7 @@ sidebar_label: Alertmanager
 
 Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of de-duplicating, grouping, and routing them to the correct receiver integration such as email, Slack, MS Teams, or OpsGenie. It also takes care of silencing and inhibition of alerts.
 
-Alertmanager is configured to use the global values found under settings' [alerts](../for-ops/console/settings/alerts) and [co-monitoring](../for-ops/console/settings/co-monitoring).
+Alertmanager is configured to use the global values found under settings' [alerts](../for-ops/console/settings/alerts.md) and [co-monitoring](../for-ops/console/settings/co-monitoring.md).
 
 A team may decide to override some or all of them, in order to have alerts sent to their own endpoints. Self-service rights to alerting must be enabled for the team (enabled by default for all teams). When running Otomi in multi-tenant mode, each team is provided a dedicated alertmanger instance.
 
diff --git a/docs/apps/certmanager.md b/docs/apps/certmanager.md
index 8a84e4a86..cad06928f 100644
--- a/docs/apps/certmanager.md
+++ b/docs/apps/certmanager.md
@@ -11,7 +11,7 @@ The wildcard certificate must be valid for the following domain `*.<cluster.doma
 :::
 
 :::info
-Setting Cert-Manager to use Letsencrypt requires DNS availability of the requesting domains, and forces Otomi to install [ExternalDNS](external-dns). Because a lot of DNS settings are used by other Otomi contexts, all DNS configuration can be found [here](../for-ops/console/settings/dns).
+Setting Cert-Manager to use Letsencrypt requires DNS availability of the requesting domains, and forces Otomi to install [ExternalDNS](external-dns.md). Because a lot of DNS settings are used by other Otomi contexts, all DNS configuration can be found [here](../for-ops/console/settings/dns.md).
 :::
 
 ## Configuration Values
diff --git a/docs/apps/grafana.md b/docs/apps/grafana.md
index 8bcb7aaae..f81d0b240 100644
--- a/docs/apps/grafana.md
+++ b/docs/apps/grafana.md
@@ -4,4 +4,4 @@ title: Grafana
 sidebar_label: Grafana
 ---
 
-Otomi uses Grafana to visualize [Prometheus](prometheus) metrics and [Loki](loki) logs. Team members are automatically given `Editor` role, while admins are also given `Admin` role. It is possible to make configuration changes directly in Grafana, but only to non-conflicting settings. Data sources are preconfigured and must not be edited as changes will be lost when Grafana is redeployed.
\ No newline at end of file
+Otomi uses Grafana to visualize [Prometheus](prometheus.md) metrics and [Loki](loki.md) logs. Team members are automatically given `Editor` role, while admins are also given `Admin` role. It is possible to make configuration changes directly in Grafana, but only to non-conflicting settings. Data sources are preconfigured and must not be edited as changes will be lost when Grafana is redeployed.
\ No newline at end of file
diff --git a/docs/apps/loki.md b/docs/apps/loki.md
index c1db3df6b..cf8c43177 100644
--- a/docs/apps/loki.md
+++ b/docs/apps/loki.md
@@ -4,7 +4,7 @@ title: Loki
 sidebar_label: Loki
 ---
 
-Loki aggregates all the container logs from the platform and stores them in a storage endpoint of choice (defaults to PVC). When Otomi is installed in multi-tenancy mode (see [here](../for-ops/console/settings/otomi) it will split logs from team namespaces and make them available only to team members. Otomi provides shortcuts to selections of logs based on interest. Otomi splits logs per team, installs a dedicated Grafana instance per team and configures authentication for Grafana to allow access for team members only.
+Loki aggregates all the container logs from the platform and stores them in a storage endpoint of choice (defaults to PVC). When Otomi is installed in multi-tenancy mode (see [here](../for-ops/console/settings/otomi.md)) it will split logs from team namespaces and make them available only to team members. Otomi provides shortcuts to selections of logs based on interest. Otomi splits logs per team, installs a dedicated Grafana instance per team and configures authentication for Grafana to allow access for team members only.
 
 ## Known issues
 
diff --git a/docs/for-devs/console/apps.md b/docs/for-devs/console/apps.md
index 4b17e2ea4..9c6578c8e 100644
--- a/docs/for-devs/console/apps.md
+++ b/docs/for-devs/console/apps.md
@@ -14,4 +14,4 @@ Here you will find more information about the app and how the app is integrated
 
 ### Shortcuts
 
-Create shortcuts to open the app at a target path. Created shortcuts will also become visable in the [Shortcuts](shortcuts) section.
+Create shortcuts to open the app at a target path. Created shortcuts will also become visable in the [Shortcuts](shortcuts.md) section.
diff --git a/docs/for-devs/get-started/lab-1.md b/docs/for-devs/get-started/lab-1.md
index dc70e494c..b3c5ff0e5 100644
--- a/docs/for-devs/get-started/lab-1.md
+++ b/docs/for-devs/get-started/lab-1.md
@@ -22,7 +22,7 @@ We assume you (or the platform administrator) have:
 - Trivy Operator
 - Gatekeeper (with option `Disable validating webhook` set to true)
 
-For the [Use OpenTelemery](lab-27) Lab, the Tempo app needs to be enabled together with tracing in the `Istio` and `Nginx Ingress` apps.
+For the [Use OpenTelemery](lab-27.md) Lab, the Tempo app needs to be enabled together with tracing in the `Istio` and `Nginx Ingress` apps.
 
 3. Created a team called `demo` with `Managed prometheus and alert manager` enabled
 4. [Created an account](/docs/apps/keycloak#create-a-user-in-keycloak) and added your user to the team group in Keycloak
diff --git a/docs/for-devs/get-started/lab-11.md b/docs/for-devs/get-started/lab-11.md
index a466f9b55..85efdda54 100644
--- a/docs/for-devs/get-started/lab-11.md
+++ b/docs/for-devs/get-started/lab-11.md
@@ -42,7 +42,7 @@ In the example above, we used the `Digest` update strategy. The `Semver` strateg
 
 ## Expose the service
 
-Now go to the [Expose services](lab-18) lab and expose the `green` service. When the service is created, go to `Services` in the left menu and click on the Url of the `green` service. What do you see?
+Now go to the [Expose services](lab-18.md) lab and expose the `green` service. When the service is created, go to `Services` in the left menu and click on the Url of the `green` service. What do you see?
 
 ## Make code change to trigger a new build
 
diff --git a/docs/for-devs/get-started/lab-22.md b/docs/for-devs/get-started/lab-22.md
index 9f06f6628..646de3b53 100644
--- a/docs/for-devs/get-started/lab-22.md
+++ b/docs/for-devs/get-started/lab-22.md
@@ -67,7 +67,7 @@ Check if the ServiveMonitor has been picked up by Prometheus:
 
 Okay, our metrics are now being scraped by the Team's Prometheus. Before we continue, let's first generate some load:
 
-1. Go to the [Expose services](lab-18) lab and expose the `custom-metrics` service
+1. Go to the [Expose services](lab-18.md) lab and expose the `custom-metrics` service
 
 2. Run the following command in your terminal:
 
@@ -96,5 +96,5 @@ To see the metrics:
 
 Prometheus is now scraping our custom metrics. You can now use these metrics to:
 
-- Create a dashboard in Grafana in the lab [Create custom dashboards](lab-30)
-- Create rules and send alerts in the lab [Create custom rules](lab-31)
\ No newline at end of file
+- Create a dashboard in Grafana in the lab [Create custom dashboards](lab-30.md)
+- Create rules and send alerts in the lab [Create custom rules](lab-31.md)
\ No newline at end of file
diff --git a/docs/for-devs/get-started/lab-23.md b/docs/for-devs/get-started/lab-23.md
index 585fcbdd7..b55df2014 100644
--- a/docs/for-devs/get-started/lab-23.md
+++ b/docs/for-devs/get-started/lab-23.md
@@ -8,7 +8,7 @@ When your application is deployed, you would of course like to get an alert when
 
 ## Monitor your application for availability
 
-- [Create a Service](lab-7) for your app in Otomi. The service can have an Exposure ingress of type `Cluster` or `Ingress`
+- [Create a Service](lab-7.md) for your app in Otomi. The service can have an Exposure ingress of type `Cluster` or `Ingress`
 
 - Open the Prometheus
 
diff --git a/docs/for-devs/get-started/lab-28.md b/docs/for-devs/get-started/lab-28.md
index c19070429..df52919ba 100644
--- a/docs/for-devs/get-started/lab-28.md
+++ b/docs/for-devs/get-started/lab-28.md
@@ -12,8 +12,8 @@ For this we are going to deploy the stable version (blue), introduce a new versi
 
 For this lab we need the 2 images (`blue` and `green`) we already created in the previous labs. If you haven't created the blue and green images, first complete these 2 labs:
 
-- [Build images](lab-6)
-- [Trigger builds](lab-26)
+- [Build images](lab-6.md)
+- [Trigger builds](lab-26.md)
 
 ## Create a workload from the developer catalog
 
diff --git a/docs/for-devs/get-started/lab-29.md b/docs/for-devs/get-started/lab-29.md
index ed39c3e29..727c25768 100644
--- a/docs/for-devs/get-started/lab-29.md
+++ b/docs/for-devs/get-started/lab-29.md
@@ -44,4 +44,4 @@ In the Info tab you'll see some information about the Chart like the version and
 
 ![catalog](../../img/catalog-3.png)
 
-From here you can create a Workload using the Catalog template by adding a name and changing the values. Go to the [next lab](lab-13) to create a workload.
\ No newline at end of file
+From here you can create a Workload using the Catalog template by adding a name and changing the values. Go to the [next lab](lab-13.md) to create a workload.
\ No newline at end of file
diff --git a/docs/for-devs/get-started/lab-30.md b/docs/for-devs/get-started/lab-30.md
index 3e6091fd2..e9fda4986 100644
--- a/docs/for-devs/get-started/lab-30.md
+++ b/docs/for-devs/get-started/lab-30.md
@@ -4,7 +4,7 @@ title: Create custom dashboards
 sidebar_label: Create custom dashboards
 ---
 
-In the lab [Using custom metrics](lab-22) we created a Workload with a ServiceMonitor so the Team's Prometheus can scrape our custom metrics. In this lab we are going to create a custom Grafana dashboard and add the dashboard to a Configmap so the Team's Grafana will automatically load the dashboard.
+In the lab [Using custom metrics](lab-22.md) we created a Workload with a ServiceMonitor so the Team's Prometheus can scrape our custom metrics. In this lab we are going to create a custom Grafana dashboard and add the dashboard to a Configmap so the Team's Grafana will automatically load the dashboard.
 
 ## Create a dashboard in Grafana
 
diff --git a/docs/for-devs/get-started/lab-8.md b/docs/for-devs/get-started/lab-8.md
index ec5427987..d04f5047c 100644
--- a/docs/for-devs/get-started/lab-8.md
+++ b/docs/for-devs/get-started/lab-8.md
@@ -67,5 +67,5 @@ The secret in Vault will now be synchronized to Kubernetes and can be used by th
 
 :::info
 
-In this part we only covered using generic secrets. See [here](../console/secrets) to see how you can create TLS and pull secrets
+In this part we only covered using generic secrets. See [here](../console/secrets.md) to see how you can create TLS and pull secrets
 :::
diff --git a/docs/for-devs/get-started/lab-9.md b/docs/for-devs/get-started/lab-9.md
index a2e7df20d..d433f0565 100644
--- a/docs/for-devs/get-started/lab-9.md
+++ b/docs/for-devs/get-started/lab-9.md
@@ -12,7 +12,7 @@ In this case we'll use a demo app called hello. If you like you can clone the re
 git clone https://github.com/redkubes/nodejs-helloworld.git
 ```
 
-And then tag and build the image as you have done in the [Push images](lab-5) lab.
+And then tag and build the image as you have done in the [Push images](lab-5.md) lab.
 
 ## Create a Deployment and Service
 
diff --git a/docs/for-devs/get-started/overview.md b/docs/for-devs/get-started/overview.md
index b57ed6f7c..769cabc16 100644
--- a/docs/for-devs/get-started/overview.md
+++ b/docs/for-devs/get-started/overview.md
@@ -12,75 +12,75 @@ Welcome to Otomi! If you are going to use Otomi, these getting started labs are
 
 **Make sure everything is ready to get started**
 
-### [Prerequisites](lab-1)
+### [Prerequisites](lab-1.md)
 
 ---
 
 **Create code repositories and build images**
 
 
-### [Create private Git repositories](lab-3)
+### [Create private Git repositories](lab-3.md)
 
-### [Create builds](lab-6)
+### [Create builds](lab-6.md)
 
-### [Trigger builds](lab-26)
+### [Trigger builds](lab-26.md)
 
 ---
 
 **Create workloads**
 
-### [Create secrets](lab-8)
+### [Create secrets](lab-8.md)
 
-### [BYO manifest to create a workload](lab-10)
+### [BYO manifest to create a workload](lab-10.md)
 
-### [Explore the Catalog](lab-29)
+### [Explore the Catalog](lab-29.md)
 
-### [Create a workload using the developer catalog](lab-13)
+### [Create a workload using the developer catalog](lab-13.md)
 
-### [Configure the auto image updater](lab-11)
+### [Configure the auto image updater](lab-11.md)
 
-### [Create a PostgreSQL database](lab-24)
+### [Create a PostgreSQL database](lab-24.md)
 
 ---
 
 **Secure workloads**
 
-### [Check policy compliance](lab-15)
+### [Check policy compliance](lab-15.md)
 
-### [Scan images for vulnerabilities](lab-7)
+### [Scan images for vulnerabilities](lab-7.md)
 
-### [Scan your running containers for vulnerabilities](lab-17)
+### [Scan your running containers for vulnerabilities](lab-17.md)
 
 ---
 
 **Expose workloads**
 
-### [Publicly expose a service](lab-18)
+### [Publicly expose a service](lab-18.md)
 
-### [Configuring network policies](lab-19)
+### [Configuring network policies](lab-19.md)
 
 ---
 
 **Monitor and debug workloads**
 
-### [View container logs](lab-20)
+### [View container logs](lab-20.md)
 
-### [View container metrics](lab-21)
+### [View container metrics](lab-21.md)
 
-### [Using custom metrics](lab-22)
+### [Using custom metrics](lab-22.md)
 
-### [Create custom dashboards](lab-30)
+### [Create custom dashboards](lab-30.md)
 
-### [Create custom rules](lab-31)
+### [Create custom rules](lab-31.md)
 
-### [Monitoring availability](lab-23)
+### [Monitoring availability](lab-23.md)
 
-### [Monitor databases](lab-25)
+### [Monitor databases](lab-25.md)
 
 ---
 
 **Advanced Labs**
 
-### [Tracing with OpenTelemetry](lab-27)
+### [Tracing with OpenTelemetry](lab-27.md)
 
-### [Canary Deployments](lab-28)
+### [Canary Deployments](lab-28.md)
diff --git a/docs/for-ops/cli/deploying.md b/docs/for-ops/cli/deploying.md
index d8cc4a354..8a81396de 100644
--- a/docs/for-ops/cli/deploying.md
+++ b/docs/for-ops/cli/deploying.md
@@ -39,7 +39,7 @@ If you don't need encryption straight away please continue to the next step
 
 :::
 
-Otomi will encrypt any `secrets.*.yaml` files with [sops](https://github.com/mozilla/sops), but only if it finds `sops:` configuration details. In order to have access to the KMS credentials to encrypt/decrypt, a `.secrets` file needs to exist and have those credentials. Please `copy .secrets.sample .secrets` and fill it in with the credentials from the [prerequisites](/docs/installation/prerequisites).
+Otomi will encrypt any `secrets.*.yaml` files with [sops](https://github.com/mozilla/sops), but only if it finds `sops:` configuration details. In order to have access to the KMS credentials to encrypt/decrypt, a `.secrets` file needs to exist and have those credentials. Please `copy .secrets.sample .secrets` and fill it in with the credentials from the [prerequisites](/docs/get-started/prerequisites.md).
 
 Then you can run `otomi bootstrap`, which will result in the encryption and decryption of the secrets files.
 
@@ -76,7 +76,7 @@ The console allows for easy configuration of many settings but not all. Assuming
 
 ## 5. Configuration
 
-Configuration can be performed much easier through the Otomi Console, so please refer to the [Otomi Console](/docs/for-ops/console/overview) documentation.
+Configuration can be performed much easier through the Otomi Console, so please refer to the [Otomi Console](/docs/for-ops/console/overview.md) documentation.
 
 However, chart configuration is not (yet) exposed through the console, so please look at the values repo's `env/charts/*` files to edit the configuration files.
 
diff --git a/docs/for-ops/cli/installation.md b/docs/for-ops/cli/installation.md
index 008a63368..bdb05a5c4 100644
--- a/docs/for-ops/cli/installation.md
+++ b/docs/for-ops/cli/installation.md
@@ -61,23 +61,23 @@ To find the options available.
 
 | Command                                          | Description                                                                                          |
 | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
-| [`otomi apply`](apply)                           | Apply all, or supplied, K8S resources                                                                |
-| [`otomi bash`](bash)                             | Run interactive bash shell in otomi-core container                                                   |
-| [`otomi bootstrap`](bootstrap)                   | Bootstrap values repo with artifacts corresponding to the cluster's stack version                    |
-| [`otomi check-policies`](check-policies)         | Check if generated manifests adhere to defined OPA policies                                          |
-| [`otomi commit`](commit)                         | Execute wrapper for generate pipelines -> git commit changed files                                   |
-| [`otomi decrypt [files..]`](decrypt)             | Decrypts file(s), given as arguments, or any file matching `secrets.*.yaml` in the values repository |
-| [`otomi destroy`](destroy)                       | Destroy all, or supplied, K8S resources                                                              |
-| [`otomi diff`](diff)                             | Diff all, or supplied, K8S resources                                                                 |
-| [`otomi encrypt [files..]`](encrypt)             | Encrypts file(s), given as arguments, or any file matching `secrets.*.yaml` in the values repository |
-| [`otomi lint`](lint)                             | Uses helmfile lint to lint the target manifests                                                      |
-| [`otomi pull`](pull)                             | Wrapper for git pull && otomi bootstrap                                                              |
-| [`otomi rotate-keys`](rotate-keys)               | Rotate keys for all the sops secrets in the values repository                                        |
-| [`otomi status`](status)                         | Show cluster status                                                                                  |
-| [`otomi sync`](sync)                             | Sync all, or supplied, K8S resources                                                                 |
-| [`otomi template [outDir]`](template)            | Export all, or supplied, K8S resources                                                               |
-| [`otomi test`](test)                             | Run tests against the target cluster                                                                 |
-| [`otomi validate-templates`](validate-templates) | Validate generated manifests against supported k8s versions/CRDs and best practices                  |
-| [`otomi validate-values`](validate-values)       | Validate values for each cluster against JSON schema (takes target options)                          |
-| [`otomi values`](values)                         | Show helmfile values for target cluster                                                              |
-| [`otomi x`](x)                                   | Execute command in container                                                                         |
+| [`otomi apply`](apply.md)                           | Apply all, or supplied, K8S resources                                                                |
+| [`otomi bash`](bash.md)                             | Run interactive bash shell in otomi-core container                                                   |
+| [`otomi bootstrap`](bootstrap.md)                   | Bootstrap values repo with artifacts corresponding to the cluster's stack version                    |
+| [`otomi check-policies`](check-policies.md)         | Check if generated manifests adhere to defined OPA policies                                          |
+| [`otomi commit`](commit.md)                         | Execute wrapper for generate pipelines -> git commit changed files                                   |
+| [`otomi decrypt [files..]`](decrypt.md)             | Decrypts file(s), given as arguments, or any file matching `secrets.*.yaml` in the values repository |
+| [`otomi destroy`](destroy.md)                       | Destroy all, or supplied, K8S resources                                                              |
+| [`otomi diff`](diff.md)                             | Diff all, or supplied, K8S resources                                                                 |
+| [`otomi encrypt [files..]`](encrypt.md)             | Encrypts file(s), given as arguments, or any file matching `secrets.*.yaml` in the values repository |
+| [`otomi lint`](lint.md)                             | Uses helmfile lint to lint the target manifests                                                      |
+| [`otomi pull`](pull.md)                             | Wrapper for git pull && otomi bootstrap                                                              |
+| [`otomi rotate-keys`](rotate-keys.md)               | Rotate keys for all the sops secrets in the values repository                                        |
+| [`otomi status`](status.md)                         | Show cluster status                                                                                  |
+| [`otomi sync`](sync.md)                             | Sync all, or supplied, K8S resources                                                                 |
+| [`otomi template [outDir]`](template.md)            | Export all, or supplied, K8S resources                                                               |
+| [`otomi test`](test.md)                             | Run tests against the target cluster                                                                 |
+| [`otomi validate-templates`](validate-templates.md) | Validate generated manifests against supported k8s versions/CRDs and best practices                  |
+| [`otomi validate-values`](validate-values.md)       | Validate values for each cluster against JSON schema (takes target options)                          |
+| [`otomi values`](values.md)                         | Show helmfile values for target cluster                                                              |
+| [`otomi x`](x.md)                                   | Execute command in container                                                                         |
diff --git a/docs/for-ops/console/apps.md b/docs/for-ops/console/apps.md
index b74fd244b..7ae960533 100644
--- a/docs/for-ops/console/apps.md
+++ b/docs/for-ops/console/apps.md
@@ -26,7 +26,7 @@ Here you will find more information about the app and how the app is integrated
 
 ### Shortcuts
 
-Create shortcuts to open the app at a target path. Created shortcuts will also become visable in the [Shortcuts](shortcuts) section
+Create shortcuts to open the app at a target path. Created shortcuts will also become visable in the [Shortcuts](shortcuts.md) section
 
 ### Values
 
diff --git a/docs/for-ops/console/builds.md b/docs/for-ops/console/builds.md
index 7636ed7bf..855708301 100644
--- a/docs/for-ops/console/builds.md
+++ b/docs/for-ops/console/builds.md
@@ -20,4 +20,4 @@ All known Builds on the platform are listed here. Builds can be sorted based on:
 | Tag           | The tag of the image                                            |
 | Team          | The name of the Team responsible for the build                  |
 
-A platform admin can also create builds. Make sure to select the correct context (team-name) in the top bar. See [here](/docs/for-devs/console/builds) for more information about creating builds.
\ No newline at end of file
+A platform admin can also create builds. Make sure to select the correct context (team-name) in the top bar. See [here](/docs/for-devs/console/builds.md) for more information about creating builds.
\ No newline at end of file
diff --git a/docs/for-ops/console/clusters.md b/docs/for-ops/console/clusters.md
index 9582345bf..fe709ad70 100644
--- a/docs/for-ops/console/clusters.md
+++ b/docs/for-ops/console/clusters.md
@@ -14,4 +14,4 @@ All known Otomi clusters are listed here. Clusters can be sorted based on:
 | Name     | The name of the cluster                                              |
 | URL      | The URL of the Otomi Console of the cluster                          |
 
-Kubernetes clusters running Otomi can be linked by adding additional clusters in the [Platform Settings / Otomi](settings/otomi). This enables to switch context between clusters by selecting `Cluster` in the top bar.
+Kubernetes clusters running Otomi can be linked by adding additional clusters in the [Platform Settings / Otomi](settings/otomi.md). This enables to switch context between clusters by selecting `Cluster` in the top bar.
diff --git a/docs/for-ops/console/overview.md b/docs/for-ops/console/overview.md
index ffa5c4dec..f2ad4b36b 100644
--- a/docs/for-ops/console/overview.md
+++ b/docs/for-ops/console/overview.md
@@ -17,28 +17,28 @@ Otomi Console has a topbar showing a cluster and team selector, the logged-in us
 The Platform section in the left menu provides access to:
 
 - Dashboard
-- [Apps](apps): All active and inactive apps. Activate apps by dragging them to the active apps section
-- [Shortcuts](shortcuts): A list off all shortcuts created on this platform
-- [Clusters](clusters): A list of all known Kubernetes clusters running Otomi 
-- [Policies](policies): A list of all available security policies and their configuration for this platform
-- [Teams](teams): A list of all Teams using this platform
-- [Builds](builds): A list of all builds created on this platform
-- [Secrets](secrets): A list of all secrets created on this platform
-- [Workloads](workloads): A list of all workloads running on this platform
-- [Services](services): A list of all services running on this platform
-- [Settings](settings/alerts): Specific configuration of the platform
+- [Apps](apps.md): All active and inactive apps. Activate apps by dragging them to the active apps section
+- [Shortcuts](shortcuts.md): A list off all shortcuts created on this platform
+- [Clusters](clusters.md): A list of all known Kubernetes clusters running Otomi 
+- [Policies](policies.md): A list of all available security policies and their configuration for this platform
+- [Teams](teams.md): A list of all Teams using this platform
+- [Builds](builds.md): A list of all builds created on this platform
+- [Secrets](secrets.md): A list of all secrets created on this platform
+- [Workloads](workloads.md): A list of all workloads running on this platform
+- [Services](services.md): A list of all services running on this platform
+- [Settings](settings/alerts.md): Specific configuration of the platform
 
 ### Team section
 
 The Team `$name` section gives access to:
 
-- [Apps](../../for-devs/console/apps): All the apps available to the team on this platform
-- [Shortcuts](../../for-devs/console/shortcuts): All shortcuts available to the team on this platform
-- [Builds](../../for-devs/console/builds): A list of all builds created by the team
-- [Secrets](../../for-devs/console/secrets): A list of all secrets created by the team
-- [Workloads](../../for-devs/console/workloads): A list of all team workloads
-- [Services](../../for-devs/console/services): A list of all team services
-- [Settings](../../for-devs/console/settings): Specific team configuration options
+- [Apps](../../for-devs/console/apps.md): All the apps available to the team on this platform
+- [Shortcuts](../../for-devs/console/shortcuts.md): All shortcuts available to the team on this platform
+- [Builds](../../for-devs/console/builds.md): A list of all builds created by the team
+- [Secrets](../../for-devs/console/secrets.md): A list of all secrets created by the team
+- [Workloads](../../for-devs/console/workloads.md): A list of all team workloads
+- [Services](../../for-devs/console/services.md): A list of all team services
+- [Settings](../../for-devs/console/settings.md): Specific team configuration options
 
 ### Cluster section
 
diff --git a/docs/for-ops/console/secrets.md b/docs/for-ops/console/secrets.md
index 92beffb00..5b0f38e60 100644
--- a/docs/for-ops/console/secrets.md
+++ b/docs/for-ops/console/secrets.md
@@ -16,4 +16,4 @@ All known Builds on the platform are listed here. Builds can be sorted based on:
 | Type          | The secret type (generic, docker-registry, TLS)        |
 | Team          | The name of the Team responsible for the secret        |
 
-A platform admin can NOT create secrets and does NOT have access to the team's secrets in Vault. In case an administrator needs access to team secrets, retrieve the `vault vault-unseal-keys` and sign in with the `token` method. See [here](/docs/apps/vault) for detailed instructions.
\ No newline at end of file
+A platform admin can NOT create secrets and does NOT have access to the team's secrets in Vault. In case an administrator needs access to team secrets, retrieve the `vault vault-unseal-keys` and sign in with the `token` method. See [here](/docs/apps/vault.md) for detailed instructions.
\ No newline at end of file
diff --git a/docs/for-ops/console/settings/co-monitoring.md b/docs/for-ops/console/settings/co-monitoring.md
index 9661b9aeb..333147b74 100644
--- a/docs/for-ops/console/settings/co-monitoring.md
+++ b/docs/for-ops/console/settings/co-monitoring.md
@@ -11,4 +11,4 @@ sidebar_label: Co-monitoring
 Co-Monitoring settings will only be active when Alertmanager is active.
 :::
 
-This section is similar to the [Alerts](alerts) section, but with a different intent: the configuration here is meant to target 3rd party alerting endpoints. Those will become active when the Remote monitoring option (in Settings/Otomi) is turned on. When used, the "Alerts" section should only contain endpoints for the 3rd party. Of course teams can still configure their own alert endpoints.
\ No newline at end of file
+This section is similar to the [Alerts](alerts.md) section, but with a different intent: the configuration here is meant to target 3rd party alerting endpoints. Those will become active when the Remote monitoring option (in Settings/Otomi) is turned on. When used, the "Alerts" section should only contain endpoints for the 3rd party. Of course teams can still configure their own alert endpoints.
\ No newline at end of file
diff --git a/docs/for-ops/console/teams.md b/docs/for-ops/console/teams.md
index b33f2e909..a972c94b5 100644
--- a/docs/for-ops/console/teams.md
+++ b/docs/for-ops/console/teams.md
@@ -15,7 +15,7 @@ sidebar_label: Teams
 
 By default, Otomi creates a team called Team Admin. Admins can use this team to expose any service in the team-admin namespace, but also in other namespaces.
 
-see [Team Services](../../for-devs/console/services) for more info about how to create Services in Otomi and how to configure ingress. The only difference here is that when creating Services in Team Admin, the admin can also select the namespace of the service.
+see [Team Services](../../for-devs/console/services.md) for more info about how to create Services in Otomi and how to configure ingress. The only difference here is that when creating Services in Team Admin, the admin can also select the namespace of the service.
 
 Another difference between the Team Admin and user created Teams is that Team Admin does not have apps and it is not possible to configure any settings for the team-admin namespace.
 
diff --git a/docs/for-ops/console/workloads.md b/docs/for-ops/console/workloads.md
index f433998ba..b90f58985 100644
--- a/docs/for-ops/console/workloads.md
+++ b/docs/for-ops/console/workloads.md
@@ -16,4 +16,4 @@ All known Workloads on the platform are listed here. Workloads can be sorted bas
 | Argocd | Link to the Argo CD application in the Argo CD UI               |
 | Team Name     | The name of the Team responsible for the workload      |
 
-A platform admin can also create Workloads. Make sure to select the correct context (team-name) in the top bar. See [here](/docs/for-devs/console/workloads) for more information about creating builds.
\ No newline at end of file
+A platform admin can also create Workloads. Make sure to select the correct context (team-name) in the top bar. See [here](/docs/for-devs/console/workloads.md) for more information about creating builds.
\ No newline at end of file
diff --git a/docs/for-ops/how-to/overview.md b/docs/for-ops/how-to/overview.md
index 65fcb5e5c..535af6795 100644
--- a/docs/for-ops/how-to/overview.md
+++ b/docs/for-ops/how-to/overview.md
@@ -8,15 +8,15 @@ sidebar_label: Overview
 
 ---
 
-### [Managing the Developer Catalog](dev-catalog)
+### [Managing the Developer Catalog](use-catalog.md)
 
-### [Managing Ingress Controllers](ingress-classes)
+### [Managing Ingress Controllers](ingress-classes.md)
 
-### [Use the team-admin](use-team-admin)
+### [Use the team-admin](use-team-admin.md)
 
-### [Using Core only](core-only)
+### [Using Core only](core-only.md)
 
-<!-- ### [Switch to DNS](switch-to-dns) -->
+<!-- ### [Switch to DNS](switch-to-dns.md) -->
 
-### [Create and restore backups](backups)
+### [Create and restore backups](backups.md)
 
diff --git a/docs/for-ops/sre/overview.md b/docs/for-ops/sre/overview.md
index 6c9b5b23a..7d9659102 100644
--- a/docs/for-ops/sre/overview.md
+++ b/docs/for-ops/sre/overview.md
@@ -51,6 +51,6 @@ Line 1-7 are configuration options supported in the Otomi values schema. Line 8-
 
 For SRE's we have created a couple of guides and checklists:
 
-- [Daily routine](daily)
-- [Troubleshooting](troubleshooting)
-- [Upgrading Otomi](upgrades)
+- [Daily routine](daily.md)
+- [Troubleshooting](troubleshooting.md)
+- [Upgrading Otomi](upgrades.md)
diff --git a/docs/get-started/_post-install.md b/docs/get-started/_post-install.md
index 50bbea749..1aff60172 100644
--- a/docs/get-started/_post-install.md
+++ b/docs/get-started/_post-install.md
@@ -36,7 +36,7 @@ kubectl logs jobs/otomi -n default -f
 
 Open the Otomi console (using the URL provided in the installer logs), and sign in with the new user.
 
-Click [here](/docs/console) to learn more about using Otomi Console.
+Click [here](/docs/console.md) to learn more about using Otomi Console.
 
 ### Step 4: Add the auto generated CA to your keychain
 
@@ -50,7 +50,7 @@ sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keyc
 
 ### Create a Team
 
-Now the final step is to create a team. See the [Teams](/docs/for-ops/console/teams) page for more information.
+Now the final step is to create a team. See the [Teams](/docs/for-ops/console/teams.md) page for more information.
 
 ## When Otomi is installed with optional configuration
 
diff --git a/docs/get-started/activation.md b/docs/get-started/activation.md
index 220b21b12..d9df4174b 100644
--- a/docs/get-started/activation.md
+++ b/docs/get-started/activation.md
@@ -27,7 +27,7 @@ If you would like to use the Otomi Console (Web UI) and Otomi API (for code vali
 - Go to [Otomi Cloud](https://portal.otomi.cloud)
 - Create an account
 - Click on `Register Cluster`
-- Agree with the [EULA](../../product/eula/v1)
+- Agree with the [EULA](/product/eula/v1)
 - Copy the License Key and click `Continue`
 - Log in to Otomi Console. You can find the link in the logs of the installer (see step 1)
 - Add the License key to Otomi Console
diff --git a/docs/get-started/chart.md b/docs/get-started/chart.md
index 00f627879..e30e2eb08 100644
--- a/docs/get-started/chart.md
+++ b/docs/get-started/chart.md
@@ -7,7 +7,7 @@ Use Helm to install Otomi.
 
 Visit the [helm documentation](https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing) page for more details on how to work with helm charts.
 
-Before you begin verify if you have met the [prerequisites](/docs/installation/prerequisites)
+Before you begin verify if you have met the [prerequisites](/docs/get-started/prerequisites.md)
 
 ## Add the Otomi repository
 
@@ -63,7 +63,7 @@ Or view detailed info about kubernetes resources with [k9s](https://k9scli.io)
 
 ### Next steps
 
-Once Otomi is installed, follow the [activation steps](activation) to get ready to use Otomi.
+Once Otomi is installed, follow the [activation steps](activation.md) to get ready to use Otomi.
 
 ## Installing from source
 
diff --git a/docs/get-started/installation/aws.md b/docs/get-started/installation/aws.md
index 89e4d6606..4d1ae5d20 100644
--- a/docs/get-started/installation/aws.md
+++ b/docs/get-started/installation/aws.md
@@ -204,5 +204,5 @@ When the installer is finished, copy the `url` and `admin-password` from the con
 Follow the activation steps [here.](https://otomi.io/docs/get-started/activation)
 
 :::tip
-Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview)
+Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview.md)
 :::
diff --git a/docs/get-started/installation/azure.md b/docs/get-started/installation/azure.md
index 439add23b..7a90e2cd8 100644
--- a/docs/get-started/installation/azure.md
+++ b/docs/get-started/installation/azure.md
@@ -169,5 +169,5 @@ When the installer is finished, copy the `url` and `admin-password` from the con
 Follow the activation steps [here.](https://otomi.io/docs/get-started/activation)
 
 :::tip
-Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview)
+Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview.md)
 :::
\ No newline at end of file
diff --git a/docs/get-started/installation/civo.md b/docs/get-started/installation/civo.md
index a8f3d5581..4c4ed382f 100644
--- a/docs/get-started/installation/civo.md
+++ b/docs/get-started/installation/civo.md
@@ -89,5 +89,5 @@ When the installer is finished, copy the `url` and `admin-password` from the con
 Follow the activation steps [here.](https://otomi.io/docs/get-started/activation)
 
 :::tip
-Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview)
+Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview.md)
 :::
\ No newline at end of file
diff --git a/docs/get-started/installation/digitalocean.md b/docs/get-started/installation/digitalocean.md
index 151a6b9a0..b27dc5a51 100644
--- a/docs/get-started/installation/digitalocean.md
+++ b/docs/get-started/installation/digitalocean.md
@@ -95,5 +95,5 @@ When the installer is finished, copy the `url` and `admin-password` from the con
 Follow the activation steps [here.](https://otomi.io/docs/get-started/activation)
 
 :::tip
-Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview)
+Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview.md)
 :::
\ No newline at end of file
diff --git a/docs/get-started/installation/gcp.md b/docs/get-started/installation/gcp.md
index c6cec4465..05169c7d8 100644
--- a/docs/get-started/installation/gcp.md
+++ b/docs/get-started/installation/gcp.md
@@ -194,5 +194,5 @@ When the installer is finished, copy the `url` and `admin-password` from the con
 Follow the activation steps [here.](https://otomi.io/docs/get-started/activation)
 
 :::tip
-Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview)
+Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview.md)
 :::
\ No newline at end of file
diff --git a/docs/get-started/installation/linode.md b/docs/get-started/installation/linode.md
index 02fb58cd1..c9ec864a6 100644
--- a/docs/get-started/installation/linode.md
+++ b/docs/get-started/installation/linode.md
@@ -94,5 +94,5 @@ When the installer is finished, copy the `url` and `admin-password` from the con
 Follow the activation steps [here.](https://otomi.io/docs/get-started/activation)
 
 :::tip
-Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview)
+Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview.md)
 :::
\ No newline at end of file
diff --git a/docs/get-started/installation/scaleway.md b/docs/get-started/installation/scaleway.md
index 21ff76393..d77196bfa 100644
--- a/docs/get-started/installation/scaleway.md
+++ b/docs/get-started/installation/scaleway.md
@@ -118,5 +118,5 @@ When the installer is finished, copy the `url` and `admin-password` from the con
 Follow the activation steps [here.](https://otomi.io/docs/get-started/activation)
 
 :::tip
-Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview)
+Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview.md)
 :::
\ No newline at end of file
diff --git a/docs/get-started/installation/vultr.md b/docs/get-started/installation/vultr.md
index 759b74191..0f7084792 100644
--- a/docs/get-started/installation/vultr.md
+++ b/docs/get-started/installation/vultr.md
@@ -99,5 +99,5 @@ When the installer is finished, copy the `url` and `admin-password` from the con
 Follow the activation steps [here.](https://otomi.io/docs/get-started/activation)
 
 :::tip
-Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview)
+Like to learn how to use Otomi? Go through the [Get Started labs](/docs/for-devs/get-started/overview.md)
 :::
\ No newline at end of file
diff --git a/docs/get-started/overview.md b/docs/get-started/overview.md
index 4f3bc5946..d91ee063e 100644
--- a/docs/get-started/overview.md
+++ b/docs/get-started/overview.md
@@ -20,5 +20,5 @@ Deploy a Kubernetes cluster in your favourite cloud or infrastructure and instal
 ### Step 3: [Activate your installation ](activation.md)
 Activate your Otomi installation on [otomi.cloud](https://portal.otomi.cloud)
 
-### Step 4: [Explore Otomi with the Get Stared Labs](/docs/for-devs/get-started/overview)
+### Step 4: [Explore Otomi with the Get Stared Labs](/docs/for-devs/get-started/overview.md)
 The get started with Otomi labs contains a set of labs to cover all the Otomi supported activities performed by developer- and/or DevOps teams.
diff --git a/docs/tutorials/overview.md b/docs/tutorials/overview.md
index 234748fa1..5e5e10e9c 100644
--- a/docs/tutorials/overview.md
+++ b/docs/tutorials/overview.md
@@ -6,7 +6,7 @@ sidebar_label: Overview
 
 This section contains tutorials for more advanced installation scenario's. 
 
-1. [Install and activate Otomi with minimal vales](tutorial-1)
+1. [Install and activate Otomi with minimal vales](tutorial-1.md)
 
 We'll soon add tutorials for: