diff --git a/.cspell.json b/.cspell.json
index bea7fab52..249d20a08 100644
--- a/.cspell.json
+++ b/.cspell.json
@@ -11,11 +11,13 @@
     "CISA",
     "minikube",
     "srodenhuis",
+    "Traefik",
     "minio",
     "Alin",
     "APIV",
     "appgw",
     "binzx",
+    "civo",
     "drucker",
     "prope",
     "dtap",
diff --git a/docs/for-devs/console/workloads.md b/docs/for-devs/console/workloads.md
index e6ead3b08..0b7aefff3 100644
--- a/docs/for-devs/console/workloads.md
+++ b/docs/for-devs/console/workloads.md
@@ -65,9 +65,9 @@ Now click on `application` in the `Argocd` column of the workload in the list of
 ### BYO Helm chart
 
 1. Enter a name for the workload
-2. Enter the URL to the Git repo containing the Helm Chart or a Helm repository
-3. Optionally (only when using a Git repo) add the relative directory path within the Git repository. Absolute paths cause errors.
-4. Optionally (only when using a Chart registry) add the name of the Helm chart
+2. Enter the URL to the Git repo containing the Helm Chart or a Helm repository.
+3. Add the relative path to a directory within the Git repository. Use `./` when no directory is used.
+4. Optionally (only when using a Chart registry) add the name of the Helm chart.
 5. Enter the revision. In case of using a Git repo, this can be commit, tag, or branch. If omitted, will equal to HEAD. In case of using a Chart repository, this is a semver tag for the Chart's version
 6. Click `Next`
 7. Review the Values used to install the chart
diff --git a/docs/for-ops/how-to/install-with-dns.md b/docs/for-ops/how-to/install-with-dns.md
index 7815168ef..ed8eb2135 100644
--- a/docs/for-ops/how-to/install-with-dns.md
+++ b/docs/for-ops/how-to/install-with-dns.md
@@ -117,3 +117,47 @@ helm repo update
 helm install -f values.yaml otomi otomi/otomi
 ```
 
+## Civo DNS
+
+:::info
+Civo support is comming soon!
+:::
+
+Set up DNS in Civo:
+
+1. Under `Networking` in the Civo Dashboard, click `DNS` and then `Add a domain name`
+2. Fill in a domain name and then click `Add domain`
+3. Create a NS record in the zone where your domain is hosted and add the Civo name servers `ns0.civo.com` ans `ns1.civo.com`
+4. Under `Settings`, `Profile`, click on the tab `Security` and copy the `API key`
+
+Install Otomi:
+
+5. Add the DNS configuration to the `values.yaml` to install Otomi:
+
+```yaml
+cluster:
+  name: my-cluster # choose a name for your cluster
+  provider: civo
+  domainSuffix: your-domain.com # your domain name
+otomi:
+  hasExternalDNS: true # required
+dns:
+  domainFilters: 
+    - your-domain.com
+  provider:
+    civo:
+      apiToken: "<add your api token here>"
+apps:
+  cert-manager:
+    issuer: letsencrypt
+    stage: production
+    email: admin@your-domain.com
+```
+
+6. Install Otomi:
+
+```yaml
+helm repo add otomi https://otomi.io/otomi-core
+helm repo update
+helm install -f values.yaml otomi otomi/otomi
+```
\ No newline at end of file
diff --git a/docs/for-ops/how-to/switch-to-dns.md b/docs/for-ops/how-to/switch-to-dns.md
index 242d9ccf9..6b4960c92 100644
--- a/docs/for-ops/how-to/switch-to-dns.md
+++ b/docs/for-ops/how-to/switch-to-dns.md
@@ -15,8 +15,7 @@ When Otomi is installed with minimal values, a custom CA is generated and Otomi
 
 ## Step 2: Provide DNS values
 
-- In the left menu, click on `DNS` under Platform Settings. This option will only become active after External DNS is enabled in step 1
-- Provide the DNS zone name used by the Teams tom publish URLs on
+- Go back to the `Settings` and click `DNS`
 - Provide the Domain filter and optionally the Zone id filters
 - Select your Provider
 - Provide the required values
@@ -24,21 +23,21 @@ When Otomi is installed with minimal values, a custom CA is generated and Otomi
 
 ## Step 3: Set cluster domain suffix
 
-- In the left menu, click on `Cluster` under Platform Settings
+- Go back to the `Settings` and click `Cluster`
 - Provide the cluster Domain Suffix
 - Click on `Submit`
 
 
 ## Step 4 (optional): Use Let's Encrypt
 
-Let's encrypt requires a DNS zone. So if you would like to start using Let's Encrypt as a CA, now you can.
+Let's Encrypt requires a DNS zone. So if you would like to start using Let's Encrypt as a CA, now you can.
 
 - Click on `Apps` under platform
-- Click on the `CertManager` app
-- Click on `values`
+- Click on the `cert-manager` app
+- Click on the `values` tab
 - Fill in an email address with a valid domain name (required!)
 - Under `Issuer`, click on `Lets Encrypt`
-- Use `Production` or `Staging`
+- Select `Production`
 - Click on `Submit`
 
 ## Step 5: Deploy Changes
@@ -51,8 +50,7 @@ Wait for the Drone runner to finish:
 kubectl get pod -n drone-pipelines -w
 ```
 
-
-## Step 6: Adjust the web hook in Gitea
+## Step 6: Adjust the webhook in Gitea
 
 Open Gitea and follow these steps:
 
@@ -69,21 +67,24 @@ First sign in to the Otomi Console using the new domain name: `https://otomi.<yo
 - Click `Update Webhook`
 
 
-## Step 7: Restart the Drone server and agent
+## Step 7: Restart and Authorize Drone
 
-Then run the following kubectl command:
+After the webhook is adjusted, restart Drone:
 
-```
-kubectl delete pods -n team-admin -l app=drone
+```bash
+kubectl delete pod -n drone -l app=drone
 ```
 
-When both the Drone Agent and Server are back up, open the Drone app and follow these steps:
+When the pods have restarted and are in a running state:
 
+- Click on `Apps` under Platform
+- Click on the `Drone` app
 - Click on `Sign In` on the 404 page
 - Click `Continue`
 - Click on `Authorize Application`
 - Complete the Drone registration
 - Click `Submit`
-- On the Drone dashboard, click `SYNC`
+
+Now you still see the pipeline running of the DNS change is still running. You can manually cancel the pipeline by clicking on the pipeline and then click `cancel` in the top right.
 
 You're ready to go!
\ No newline at end of file
diff --git a/docs/get-started/activation.md b/docs/get-started/activation.md
index c52cc41a8..220b21b12 100644
--- a/docs/get-started/activation.md
+++ b/docs/get-started/activation.md
@@ -6,7 +6,7 @@ sidebar_label: Activation
 
 Follow the steps below to activate Otomi after initial installation.
 
-### Step 1: Get the log output of the installer job
+## Step 1: Get the log output of the installer job
 
 When the installer job (in the default namespace) has finished, copy the URL and the generated password from the bottom of the logs, sign in to the console with the provided URL, username and password.
 
@@ -16,7 +16,7 @@ Use the following command to get the logs of the installer job:
 kubectl logs jobs/otomi -n default -f
 ```
 
-### Step 2: Create an License Key for using Otomi Console and Otomi API
+## Step 2: Create an License Key for using Otomi Console and Otomi API
 
 :::info
 A Community Edition License Key is required per 17-05-2023
@@ -33,7 +33,7 @@ If you would like to use the Otomi Console (Web UI) and Otomi API (for code vali
 - Add the License key to Otomi Console
 - Click `Activate`
 
-### Step 3 (optional): Add the auto generated CA to your keychain
+## Step 3 (optional): Add the auto generated CA to your keychain
 
 Otomi by default automatically generates a CA. The generated CA is of course not trusted on your local machine. Here are some options to prevent you from clicking away lots of security warning in your browser:
 
@@ -66,15 +66,15 @@ alias chrome-insecure='/Applications/Google\ Chrome.app/Contents/MacOS/Google\ C
 3. Optional: Restart Docker (to support pushing images to Harbor)
 
 
-### Step 4 (Optional): Create a new admin user
+## Step 4 (Optional): Create a new admin user
 
 :::info ATTENTION
 We strongly advise to not use the default `otomi-admin` account after activation and to not change the password. Store it somewhere safe and only use it in case absolutely required.
 :::
 
-[Create a new user account in Keycloak](/docs/apps/keycloak#step-2-create-a-user-in-keycloak) and add the new user to the `otomi-admin` and `team-admin`.
+[Create a new user account in Keycloak](/docs/apps/keycloak#step-2-create-a-user-in-keycloak) and add the new user to the `otomi-admin` and `team-admin` group.
 
-### Step 5 (Optional): Add the URL of the Kubernetes API
+## Step 5 (Optional): Add the URL of the Kubernetes API
 
 :::info NOTE
 Adding the URL of the K8s cluster API is required by teams to be able to download the KUBECONFIG
diff --git a/docs/get-started/installation.md b/docs/get-started/installation.md
index 7e96592a4..c04c5d77b 100644
--- a/docs/get-started/installation.md
+++ b/docs/get-started/installation.md
@@ -4,9 +4,9 @@ title: Installation
 sidebar_label: Installation
 ---
 
-### Install Otomi with Helm
+## Install Otomi with Helm
 
-#### Add the Otomi repository
+### Add the Otomi repository
 
 ```bash
 helm repo add otomi https://otomi.io/otomi-core
@@ -15,7 +15,7 @@ helm repo update
 
 See [helm repo](https://helm.sh/docs/helm/helm_repo/) for command documentation.
 
-#### Minimal configuration
+### Minimal configuration
 
 :::info
 As of version [1.0.0](https://github.com/redkubes/otomi-core/releases/tag/v0.21.0) Otomi supports Kubernetes versions `1.25`,`1.26` and `1.27`.
@@ -39,7 +39,7 @@ When the chart is installed, follow the [activation steps](activation).
 license: <License Key>
 ``` -->
 
-#### Custom values
+### Custom values
 
 To view the required `values.yaml` file with detailed comments, view and download the chart's latest [values.yaml](https://github.com/redkubes/otomi-core/blob/main/chart/otomi/values.yaml). Run the following command to view _all_ the values (which might be overwhelming):
 
@@ -53,7 +53,7 @@ To test wether the input values are correct run the following command:
 helm template -f values.yaml otomi/otomi
 ```
 
-#### Install the Chart
+### Install the Chart
 
 Install the chart with the following command:
 
@@ -61,7 +61,7 @@ Install the chart with the following command:
 helm install -f values.yaml otomi otomi/otomi
 ```
 
-#### Monitoring the chart install
+### Monitoring the chart install
 
 The chart deploys a Job (`otomi`) in the `default` namespace. Monitor the chart install using `kubectl`:
 
@@ -76,11 +76,11 @@ Or view detailed info about kubernetes resources with [k9s](https://k9scli.io)
 
 When the chart is installed, follow the [activation steps](activation)
 
-### Installing from source
+## Installing from source
 
 As an alternative, you can also clone the otomi-core source code from the [Github](https://github.com/redkubes/otomi-core) and install otomi using the chart source code.
 
-#### Download source
+### Download source
 
 ```bash
 git clone https://github.com/redkubes/otomi-core.git
@@ -239,78 +239,4 @@ kms:
 #       project: ''
 #     vault:
 #       token: ''
-```
-
-## Known issues
-
-### Metrics server with untrusted Kube API certificates
-
-**Problem**
-
-Metrics server will not start when installing on a K8s cluster (like on Minikube or a cluster created with Kubeadm) with Kube API using self-signed certificates
-
-**Solution** 
-
-Add extra args to the metrics-service by using the following values when installing Otomi with Helm chart:
-
-```
-apps:
-  metrics-server:
-    enabled: true
-    _rawValues:
-      extraArgs:
-        kubelet-preferred-address-types: InternalIP
-        kubelet-insecure-tls: true
-```
-
-### Uninstalling Otomi
-
-**Problem**
-
-When uninstalling Otomi using the `helm unistall` cmd, all Otomi namespaces get stuck in a terminating state.
-
-**Solution** 
-
-The work around for now is to delete all namespaces using this cmd:
-
-```
-for ns in $(kubectl get ns --field-selector status.phase=Terminating -o jsonpath='{.items[*].metadata.name}'); do  kubectl get ns $ns -ojson | jq '.spec.finalizers = []' | kubectl replace --raw "/api/v1/namespaces/$ns/finalize" -f -; done
-```
-
-### Installing Otomi with Cloudflare DNS
-
-**Problem**
-
-When installing Otomi with `otomi.hasExternalDNS=true` and `apps.cert-manager.issuer=letsencrypt` with `apps.cert-manager.stage=staging`, activating Drone is not possible because of the following error:
-
-```
-Post "https://gitea.d3-otomi.net/login/oauth/access_token": x509: certificate signed by unknown authority
-```
-
-**Solution** 
-
-1. Install with `apps.cert-manager.stage=production`
-
-or 
-
-1. In Cloudflare, set the `A-record` for Gitea to proxy status = `DNS Only`. Also make sure your SSL/TLS encryption mode is set to `Full`
-
-### Installing Otomi with DNS fails due to failed authentication for gitea
-
-**Problem**
-
-When installing Otomi with DNS fails with the following error:
-
-```
-otomi:cmd:commit:commitAndPush:error remote: Unauthorized
-fatal: Authentication failed for 'https://gitea.otomi.example.com/otomi/values.git/'
-```
-
-**Solution**
-
-Provide a custom password:
-
-```
-otomi:
-  adminPassword: yourpassword
 ```
\ No newline at end of file
diff --git a/docs/get-started/known-issues.md b/docs/get-started/known-issues.md
new file mode 100644
index 000000000..35ba0f45e
--- /dev/null
+++ b/docs/get-started/known-issues.md
@@ -0,0 +1,99 @@
+---
+slug: known-issues
+title: Known Installation Issues
+sidebar_label: Known Installation Issues
+---
+
+
+## Metrics server does not start with untrusted Kube API certificates
+
+**Issue**
+
+Metrics server will not start when installing on a K8s cluster (like on Minikube or a cluster created with Kubeadm) with Kube API using self-signed certificates
+
+**Solution** 
+
+Add extra args to the metrics-service by using the following values when installing Otomi with Helm chart:
+
+```
+apps:
+  metrics-server:
+    enabled: true
+    _rawValues:
+      extraArgs:
+        kubelet-preferred-address-types: InternalIP
+        kubelet-insecure-tls: true
+```
+
+## Namespaces stuck in terminating state when uninstalling Otomi
+
+**Issue**
+
+When uninstalling Otomi using the `helm unistall` cmd, all Otomi namespaces get stuck in a terminating state.
+
+**Solution** 
+
+The work around for now is to delete all namespaces using this cmd:
+
+```
+for ns in $(kubectl get ns --field-selector status.phase=Terminating -o jsonpath='{.items[*].metadata.name}'); do  kubectl get ns $ns -ojson | jq '.spec.finalizers = []' | kubectl replace --raw "/api/v1/namespaces/$ns/finalize" -f -; done
+```
+
+## Drone activation fails when installing Otomi with Cloudflare DNS
+
+**Issue**
+
+When installing Otomi with `otomi.hasExternalDNS=true` and `apps.cert-manager.issuer=letsencrypt` with `apps.cert-manager.stage=staging`, activating Drone is not possible because of the following error:
+
+```
+Post "https://gitea.d3-otomi.net/login/oauth/access_token": x509: certificate signed by unknown authority
+```
+
+**Solution** 
+
+1. Install with `apps.cert-manager.stage=production`
+
+or 
+
+1. In Cloudflare, set the `A-record` for Gitea to proxy status = `DNS Only`. Also make sure your SSL/TLS encryption mode is set to `Full`
+
+
+## Installing Otomi with DNS fails due to failed authentication for Gitea
+
+**Issue**
+
+When installing Otomi with DNS fails with the following error:
+
+```
+otomi:cmd:commit:commitAndPush:error remote: Unauthorized
+fatal: Authentication failed for 'https://gitea.otomi.example.com/otomi/values.git/'
+```
+
+**Solution**
+
+Provide a custom password:
+
+```
+otomi:
+  adminPassword: yourpassword
+```
+
+## Installing Otomi on Civo fails
+
+There can be multiple issues when installing Otomi on Civo:
+
+**Issue**
+
+Some pods get stuck in a `pending` state during installation.
+
+**Solution**
+
+Otomi installs K8s applications like KeyCloak and Gitea. These apps require persistent storage. Civo has default quota set on resources, including volumes. If a pod stays in a pending state, it might be caused by a quota limit. In Civo dashboard, check the amount of volumes and remove all volumes that are not in use. Also check in the amount of volumes did not reach a quota limit and request an increase when needed.
+
+**Issue**
+
+Keycloak jobs fail during installation.
+
+**Solution**
+
+There is no solution for this at the moment. The Keycloak job will retry multiple times and eventually succeed.
\ No newline at end of file
diff --git a/docs/get-started/prerequisites.md b/docs/get-started/prerequisites.md
index d199d3ebd..34342f08a 100644
--- a/docs/get-started/prerequisites.md
+++ b/docs/get-started/prerequisites.md
@@ -4,44 +4,59 @@ title: Prerequisites
 sidebar_label: Prerequisites
 ---
 
-### Client binaries
+## Client binaries
 
 When installing Otomi using the chart, make sure the following client binaries exist:
 
 - [Kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) to access the cluster
 - [Helm](https://helm.sh/docs/intro/install/) for helm chart installation of Otomi
 
-### Supported Providers
+## Supported Providers
 
 :::info
 We have created [quickstarts](https://github.com/redkubes/quickstart) for Azure, GCP, AWS, Linode, Digital Ocean and Minikube to help you spin-up a Kubernetes cluster.
 :::
 
-#### Azure (AKS)
+### Azure (AKS)
 
 To install Otomi on a AKS cluster in Azure, use the `azure` provider. The `azure` provider includes creating optimized storage classes and optional integration with the a Application Gateway Ingress Controller add-on.
 
-#### Amazon Web Services (EKS)
+### Amazon Web Services (EKS)
 
 To install Otomi on a EKS cluster in AWS, use the `aws` provider.
 
-#### Google Cloud Platform (GKE)
+### Google Cloud Platform (GKE)
 
 To install Otomi on a GKE cluster in GCP, use the `google` provider.
 
-#### Digital Ocean
+### Digital Ocean
 
 To install Otomi on a Kubernetes cluster in Digital Ocean, use the `digitalocean` provider. Otomi is also available in the Digital Ocean [marketplace](https://marketplace.digitalocean.com/apps/otomi?refcode=476bfcac9ec9&action=deploy).
 
-#### OVHcloud
+### OVHcloud
 
 To install Otomi on a OVHcloud [Managed Kubernetes Service](https://www.ovhcloud.com/en-gb/public-cloud/kubernetes/), use the `ovh` provider.
 
-#### Vultr (VKE)
+### Vultr (VKE)
 
 To install Otomi on a [Vultr Kubernetes Engine (VKE)](https://www.vultr.com/docs/vultr-kubernetes-engine/) cluster, use the `vultr` provider.
 
-#### All others
+### Civo
+
+:::info
+Civo support is comming soon!
+:::
+
+To install Otomi on a [Civo K3s](https://www.civo.com/kubernetes) cluster, use the `civo` provider.
+
+Otomi on CIVO requires at least:
+
+* A node pool with `3` Large Standard nodes (4 CPU Cores and 8 GB RAM)
+* Kubernetes version `1.26` or `1.27`
+
+Otomi installs and configures Nginx as a default ingress controller. When launching from the marketplace, make sure to unselect the default Traefik v2 (NodePort).
+
+### All others
 
 Use the `custom` provider for all other clouds, and when running Kubernetes on your own hardware (including Minikube on your local machine). The custom provider uses the default available storage classes. The only requirement for using the custom provider is to be able to create a Kubernetes LoadBalancer Service that obtains an external accessible IP.
 
@@ -51,7 +66,7 @@ When using Minikube, only Otomi Core apps can be used! Activating more apps will
 
 :::
 
-### Kubernetes versions
+## Kubernetes versions
 
 Otomi currently supports the following Kubernetes versions:
 
@@ -59,16 +74,14 @@ Otomi currently supports the following Kubernetes versions:
 - `1.26`
 - `1.27`
 
-### Minimal compute resource requirements
+## Minimal compute resource requirements
 
-Otomi requires a node pool with at least **6 vCPU** threads and **8GiB+ RAM**. Note that this is the requirements for a minimal (default) install. When activating more apps, you'll probably need more resources.
+Otomi requires a node pool with at least **8 vCPU** and **16 GiB RAM**. Note that this is the requirements for a minimal install. When activating more apps, you'll probably need more resources.
 
 :::info ATTENTION
-
-The minimal resource requirement to run Otomi is based on running Core Apps only! The core apps provide an advanced ingress architecture based on Nginx, Istio, Keycloak, Oaut2 Proxy and Certmanager. Activating optional apps will require more compute resources. We advise to have a node pool available with 12 vCPU and 32 GiB memory.
-
+The minimal resource requirement to run Otomi is based on running Core Apps only! The core apps provide an advanced ingress architecture based on Nginx, Istio, Keycloak, Oaut2 Proxy and Certmanager. Activating optional apps will require more compute resources. We advise to have a node pool available with 16 vCPU and 24 GiB memory.
 :::
 
-### CNI
+## CNI
 
 To use the network policies feature in Otomi, make sure to install the [Calico](https://www.tigera.io/project-calico/) CNI or any other CNI that supports Kubernetes network polices.
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 3d14f6839..f3f9dd9a0 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -155,8 +155,8 @@ module.exports = {
               href: "/docs/for-devs/get-started/overview",
             },
             {
-              label: "Tutorials",
-              href: "/docs/tutorials/overview/",
+              label: "Roadmap",
+              href: "/product/roadmap",
             },
           ],
         },
diff --git a/sidebar-docs.js b/sidebar-docs.js
index f37567de0..c87cae7b8 100644
--- a/sidebar-docs.js
+++ b/sidebar-docs.js
@@ -4,6 +4,7 @@ module.exports = {
       "get-started/prerequisites",
       "get-started/installation",
       "get-started/activation",
+      "get-started/known-issues",
       "for-devs/get-started/overview",
     ],
     "For Ops": [
@@ -45,7 +46,8 @@ module.exports = {
           "for-ops/how-to/use-team-admin",
           "for-ops/how-to/core-only",
           "for-ops/how-to/install-with-dns",
-          "for-ops/how-to/create-and-restore-backups"
+          "for-ops/how-to/switch-to-dns",
+          "for-ops/how-to/create-and-restore-backups",
         ],
       },
       {