Removed old installation resources and fixed build (related to #640)

docs/reference/supported-environments.md

@@ -29,10 +29,7 @@ _Hint: There are more [community-maintained Camunda Platform 8 clients](./apis-c
 
 ## Camunda Platform 8 Self-Managed
 
-We highly recommend running Camunda Platform 8 Self-Managed in a Kubernetes environment. 
-We provide officially supported [Helm Charts](./self-managed/zeebe-deployment/kubernetes/helm/installing-helm.md) for this.
-
-If you cannot run in a Kubernetes environment, you may [run the distribution](https://github.com/camunda-cloud/zeebe/releases) with Java directly. 
+We highly recommend running Camunda Platform 8 Self-Managed in a Kubernetes environment. We provide officially supported [Helm Charts](./self-managed/zeebe-deployment/kubernetes-helm/) for this. Please follow the [Installation Guide](./self-managed/platform-deployment/) to learn more about installation possibilities.
 
 Requirements for the components can be seen below:
 

docs/self-managed/platform-deployment/docker.md

@@ -30,7 +30,7 @@ The following ports are exposed:
 - [`8080`](http://localhost:8080/): Operate
 - [`8081`](http://localhost:8081/): Tasklist
 
-While the Docker images itself are supported for production usage, the provided [docker-compose.yaml](https://github.com/camunda-cloud/camunda-cloud-get-started/blob/master/docker-compose.yaml) is designed to be used by developers to run an environment locally, it is not designed to be used in production. We recommend to use [Kubernetes](./kubernetes) in production, see also [Installation Overview](./).
+While the Docker images itself are supported for production usage, the provided [docker-compose.yaml](https://github.com/camunda-cloud/camunda-cloud-get-started/blob/master/docker-compose.yaml) is designed to be used by developers to run an environment locally, it is not designed to be used in production. We recommend to use [Kubernetes](../kubernetes) in production, see also [Installation Overview](./).
 
 
 ## Zeebe
@@ -101,7 +101,7 @@ operate:
 You can use the Docker image `camunda/tasklist:latest` to run Tasklist as a container.
 
 :::note
-Configure the appropriate settings described in the [Tasklist configuration](../tasklist-deployment/configuration) section.
+Configure the appropriate settings described in the [Tasklist configuration](../../tasklist-deployment/configuration) section.
 :::
 
 Like for example this `docker-compose` configuration:
@@ -123,7 +123,7 @@ tasklist:
 The `camunda/optimize:latest` Docker image can be used to run Optimize 
 
 :::note
-Configure the appropriate settings described in the [Optimize configuration](../optimize-deployment/configuration) section.
+Configure the appropriate settings described in the [Optimize configuration](../../optimize-deployment/configuration) section.
 :::
 
 Like for example this `docker-compose` configuration:

docs/self-managed/platform-deployment/index.md

@@ -27,12 +27,12 @@ For details on supported environments (e.g. Java or Elasticsearch versions), see
 You have the following options to run the above components in a self-managed fashion:
 
 - [**Kubernetes**](./kubernetes): We stronlgy recommend to use a Kubernetes to run Camunda 8 in production. Using Minikube, Kubernetes can also be an interesting evironment to run Camunda 8 locally on developer machines.
-- [**Docker**](./docker): You can run the provided Docker images of the components, also in production. For convenience, we provide a [Docker Compose](xxx) configuration to run Camunda 8 on developer machines. Note that the Docker Compose configiration is **not** optimized for production usage, but for local development.
+- [**Docker**](./docker): You can run the provided Docker images of the components, also in production. For convenience, we provide a Docker Compose configuration to run Camunda 8 on developer machines. Note that the Docker Compose configiration is **not** optimized for production usage, but for local development.
 - [**Local installation**](./local): You can simply run the Java applications on a local or virtual machine if it provides a supported Java Virtual Machine (JVM). This allows to run Camunda on virtual machines or bare metal and gives you big flexibility, however, you have to configure all nuts and bolts for the components to interact correctly yourself. We consider this a last ressort. Please note, that Windows/Mac is **NOT** supported for production usage of Zeebe.
 
 We strongly recommend
 
-* For **production**: Use Kubernetes and our [Helm charts](xxx). This setup provides you with predictable and consistent configuration, and the ability to manage deployment using automation tools.
+* For **production**: Use Kubernetes and our [Helm charts](./kubernetes-helm). This setup provides you with predictable and consistent configuration, and the ability to manage deployment using automation tools.
 * For **development**: Use SaaS. If this is not possible, use Docker Compose or Kubernetes locally. If this does not work either, consider starting a Zeebe broker via Java.
 
 ## Getting help

docs/self-managed/platform-deployment/kubernetes.md

@@ -26,7 +26,7 @@ We support [Kubernetes startup and liveness probes](../../zeebe-deployment/confi
 
 There are several alternatives to deploy applications to a Kubernetes cluster, but we recommend to use our provided Helm charts to deploy a set of components into your cluster. Helm allows you to choose exactly what chart (set of components) you want to install and how these components need to be configured.
 
-Refer to the [documentation on Camunda's Helm charts](./kubernetes-helm/) for details.
+Refer to the [documentation on Camunda's Helm charts](../kubernetes-helm/) for details.
 
 To do do, you must have the following tools installed in your local environment:
 

docs/self-managed/platform-deployment/local.md

@@ -112,11 +112,11 @@ The first screen you'll see is a sign-in page. Use the credentials `demo` / `dem
 
 After you sign in, you'll see an empty dashboard if you haven't yet deployed any processes:
 
-![operate-dash-no-processes](img/operate-dashboard-no-processes_light.png)
+![operate-dash-no-processes](assets/operate-dashboard-no-processes_light.png)
 
 If you _have_ deployed processes or created process instances, you'll see them on your dashboard:
 
-![operate-dash-with-processes](img/operate-introduction_light.png)
+![operate-dash-with-processes](assets/operate-introduction_light.png)
 
 To update Operate versions, visit the [guide to update Operate](../../components/operate/userguide/updating-operate.md).
 
@@ -150,7 +150,7 @@ The first screen you'll see is a sign-in page. Use the credentials `demo` / `dem
 
 If you've already developed user tasks in Zeebe, you can see these on the left panel on the start screen:
 
-![tasklist-start-screen](img/tasklist-start-screen_light.png)
+![tasklist-start-screen](assets/tasklist-start-screen_light.png)
 
 To update Tasklist versions, visit the [guide to update Tasklist](../../components/tasklist/userguide/updating-tasklist.md).