[Examples] Renamed some example groups for better extensibility (#2641)

- [x] Renamed `Distributed training` to `Clusters`
- [x] Renamed `Deployment` to `Inference`
- [x] Renamed `Monitoring` to `Metrics`.
- [x] Added redirects

Author: peterschmidt85

docs/assets/stylesheets/extra.css

@@ -790,6 +790,7 @@ body {
         display: flex;
     }
 
+    /* Comment to siwtch to sections in sidebar */
     .md-sidebar__inner > .md-nav--primary > .md-nav__list:not(.md-post__meta) > .md-nav__item > .md-nav > .md-nav__list > .md-nav__item:not(.md-nav__item--section) {
         display: none;
     }
@@ -861,7 +862,7 @@ body {
 }
 
 .md-sidebar--primary .md-nav__link, .md-sidebar--post .md-nav__link {
-    padding: 5px 15px 5px;
+    padding: 5px 15px 4px;
     margin-top: 0;
 }
 

docs/blog/posts/amd-on-runpod.md

@@ -42,7 +42,7 @@ you can now specify an AMD GPU under `resources`. Below are a few examples.
     Here's an example of a [service](../../docs/concepts/services.md) that deploys
     Llama 3.1 70B in FP16 using [TGI :material-arrow-top-right-thin:{ .external }](https://huggingface.co/docs/text-generation-inference/en/installation_amd){:target="_blank"}.
 
-    <div editor-title="examples/deployment/tgi/amd/service.dstack.yml"> 
+    <div editor-title="examples/inference/tgi/amd/service.dstack.yml"> 
 
     ```yaml
     type: service

docs/blog/posts/beyond-kubernetes-2024-recap-and-whats-ahead.md

@@ -110,7 +110,7 @@ efficient manner.
 
 ### NVIDIA
 
-NVIDIA remains the top accelerator supported by `dstack`. Recently, we introduced a [NIM example](../../examples/deployment/nim/index.md) 
+NVIDIA remains the top accelerator supported by `dstack`. Recently, we introduced a [NIM example](../../examples/inference/nim/index.md) 
 for model deployment, and we continue to enhance support for the rest of NVIDIA's ecosystem.
 
 ### AMD

docs/blog/posts/dstack-metrics.md

@@ -7,7 +7,7 @@ image: https://dstack.ai/static-assets/static-assets/images/dstack-stats-v2.png
 categories:
   - AMD
   - NVIDIA
-  - Monitoring
+  - Metrics
 ---
 
 # Monitoring essential GPU metrics via CLI

docs/blog/posts/metrics-ui.md

@@ -5,7 +5,7 @@ description: "TBA"
 slug: metrics-ui
 image: https://dstack.ai/static-assets/static-assets/images/dstack-metrics-ui-v3-min.png
 categories:
-  - Monitoring
+  - Metrics
   - AMD
   - NVIDIA
 ---
@@ -55,6 +55,6 @@ For persistent storage and long-term access to metrics, we still recommend setti
 metrics from `dstack`.
 
 !!! info "What's next?"
-    1. See [Monitoring](../../docs/guides/monitoring.md)
+    1. See [Metrics](../../docs/guides/metrics.md)
     2. Check [dev environments](../../docs/concepts/dev-environments.md), [tasks](../../docs/concepts/tasks.md), [services](../../docs/concepts/services.md), and [fleets](../../docs/concepts/fleets.md)
     3. Join [Discord :material-arrow-top-right-thin:{ .external }](https://discord.gg/u8SmfwPpMd){:target="_blank"}

docs/blog/posts/mpi.md

@@ -101,5 +101,5 @@ as well as use MPI for other tasks.
 
 !!! info "What's next?"
     1. Learn more about [dev environments](../../docs/concepts/dev-environments.md), [tasks](../../docs/concepts/tasks.md), [services](../../docs/concepts/services.md), and [fleets](../../docs/concepts/fleets.md)
-    2. Check the [NCCL tests](../../examples/distributed-training/nccl-tests/index.md) example
+    2. Check the [NCCL tests](../../examples/clusters/nccl-tests/index.md) example
     2. Join [Discord :material-arrow-top-right-thin:{ .external }](https://discord.gg/u8SmfwPpMd){:target="_blank"}

docs/blog/posts/prometheus.md

@@ -5,7 +5,7 @@ description: "TBA"
 slug: prometheus
 image: https://dstack.ai/static-assets/static-assets/images/dstack-prometheus-v3.png
 categories:
-  - Monitoring
+  - Metrics
   - NVIDIA
 ---
 
@@ -46,7 +46,7 @@ Overall, `dstack` collects three groups of metrics:
 | **Runs**   | Run metrics include run counters for each user in each project.                                                                                                   |
 | **Jobs**   | A run consists of one or more jobs, each mapped to a container. Job metrics offer insights into execution time, cost, GPU model, NVIDIA DCGM telemetry, and more. |
 
-For a full list of available metrics and labels, check out [Monitoring](../../docs/guides/monitoring.md).
+For a full list of available metrics and labels, check out [Metrics](../../docs/guides/metrics.md).
 
 ??? info "NVIDIA"
     NVIDIA DCGM metrics are automatically collected for `aws`, `azure`, `gcp`, and `oci` backends,
@@ -60,7 +60,7 @@ For a full list of available metrics and labels, check out [Monitoring](../../do
     only accessible through the UI and the [`dstack metrics`](dstack-metrics.md) CLI.
 
 !!! info "What's next?"
-    1. See [Metrics](../../docs/guides/monitoring.md)
+    1. See [Metrics](../../docs/guides/metrics.md)
     1. Check [dev environments](../../docs/concepts/dev-environments.md),
        [tasks](../../docs/concepts/tasks.md), [services](../../docs/concepts/services.md),
        and [fleets](../../docs/concepts/fleets.md)

docs/blog/posts/tpu-on-gcp.md

@@ -50,7 +50,7 @@ and [vLLM :material-arrow-top-right-thin:{ .external }](https://github.com/vllm-
 
 === "Optimum TPU"
 
-    <div editor-title="examples/deployment/optimum-tpu/service.dstack.yml"> 
+    <div editor-title="examples/inference/optimum-tpu/service.dstack.yml"> 
 
     ```yaml
     type: service
@@ -83,7 +83,7 @@ and [vLLM :material-arrow-top-right-thin:{ .external }](https://github.com/vllm-
     the official Docker image can be used instead of `dstackai/optimum-tpu:llama31`.
 
 === "vLLM"
-    <div editor-title="examples/deployment/vllm/service-tpu.dstack.yml"> 
+    <div editor-title="examples/inference/vllm/service-tpu.dstack.yml"> 
 
     ```yaml
     type: service

docs/changelog/index.md

@@ -71,7 +71,7 @@ To delete a gateway, pass the gateway configuration to [`dstack delete`](../refe
 <div class="termy">
 
 ```shell
-$ dstack delete -f examples/deployment/gateway.dstack.yml
+$ dstack delete -f examples/inference/gateway.dstack.yml
 ```
 
 </div>