diff --git a/_data/home-content.yml b/_data/home-content.yml
index 3a6183ff..fce2a45e 100644
--- a/_data/home-content.yml
+++ b/_data/home-content.yml
@@ -1,7 +1,26 @@
 
 
 
-
+- title: Deployments
+  icon: images/home-icons/deployment.svg
+  url: ''
+  links:
+    - title: Deployment options for Kubernetes
+      localurl: /docs/deployments/kubernetes/deployment-options-to-kubernetes/
+    - title: Managing Kubernetes clusters
+      localurl: /docs/deployments/kubernetes/manage-kubernetes/
+    - title: Using Helm in Codefresh pipelines
+      localurl: /docs/deployments/helm/using-helm-in-codefresh-pipeline/
+    - title: Managing Helm releases
+      localurl: /docs/deployments/helm/helm-releases-management/
+    - title: Promoting Helm environments
+      localurl: /docs/deployments/helm/helm-environment-promotion/
+    - title: Creating GitOps applications
+      localurl: /docs/deployment/gitops/create-application/
+    - title: Monitoring applications
+      localurl: /docs/deployment/gitops/applications-dashboard/
+    - title: Managing applications
+      localurl: /docs/deployment/gitops/manage-application/
 
 - title: Pipelines
   icon: images/home-icons/pipeline.svg
diff --git a/_data/nav.yml b/_data/nav.yml
index 8c1c9346..eeb18f1c 100644
--- a/_data/nav.yml
+++ b/_data/nav.yml
@@ -1,4 +1,46 @@
 
+- title: Deployments
+  url: "/deployments"
+  pages:
+    - title: Kubernetes
+      url: "/kubernetes"
+      sub-pages:  
+        - title: Deployment options for Kubernetes
+          url: "/deployment-options-to-kubernetes"
+        - title: Managing Kubernetes clusters
+          url: "/manage-kubernetes"
+        - title: Custom kubectl commands
+          url: "/custom-kubectl-commands"
+    - title: Helm
+      url: "/helm"
+      sub-pages:
+        - title: Using Helm in a Codefresh pipeline
+          url: "/using-helm-in-codefresh-pipeline"
+        - title: Managing Helm Releases
+          url: "/helm-releases-management"
+        - title: Using managed Helm repos
+          url: "/managed-helm-repository"
+        - title: Helm Charts and repositories
+          url: "/helm-charts-and-repositories"
+        - title: Custom Helm uploads
+          url: "/custom-helm-uploads"
+        - title: Promoting Helm environments
+          url: "/helm-environment-promotion"
+    - title: GitOps
+      url: "/gitops"
+      sub-pages:
+        - title: Creating GitOps applications 
+          url: "/create-application"
+        - title: Monitoring GitOps applications
+          url: "/applications-dashboard"
+        - title: Managing GitOps applications
+          url: "/manage-application"
+        - title: Progressive delivery with GitOps
+          url: "/install-argo-rollouts"
+        - title: Images for GitOps
+          url: "/images"
+
+
 - title: CI pipelines
   url: "/pipelines"
   pages:
diff --git a/_docs/deployments/gitops/applications-dashboard.md b/_docs/deployments/gitops/applications-dashboard.md
index 3273113d..51907f81 100644
--- a/_docs/deployments/gitops/applications-dashboard.md
+++ b/_docs/deployments/gitops/applications-dashboard.md
@@ -70,7 +70,7 @@ Here's a description of the information and actions in the Applications dashboar
 | Item                     | Description            |  
 | --------------         | --------------           |  
 |Application filters       | Filter by a range of attributes to customize the information in the dashboard to bring you what you need. {::nomarkdown}  <ul><li>Application state<br>A snapshot that displays a breakdown of the deployed applications by their health status.<br>Click a status to filter by applications that match it.<br>Codefresh tracks Argo CD's set of health statuses. See the official documentation on <a href="https://argo-cd.readthedocs.io/en/stable/operator-manual/health" target=”_blank”>Health sets. </a>.</li><li>Application attributes<br>Attribute filters support multi-selection, and results are based on an OR relationship within the same filter with multiple options, and an AND relationship between filters.<br>Clicking <b>More Filters</b> gives you options to filter by Health status, Cluster names, Namespace, and Type. <br><ul><li>Application Type: Can be any of the following<ul><li>Applications: Standalone applications. See the official documentation on <a href="https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#applications" target=”_blank”>Applications</a>.</li><li>ApplicationSet: Applications created using the ApplicationSet Custom Resource (CR) template. An ApplicationSet can generate single or multiple applications. See the official documentation on <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/application-set" target=”_blank”>Generating Applications with ApplicationSet</a>.</li><li>Git Source: Applications created by Codefresh that includes other applications and CI resources. See <a href="https://codefresh.io/csdp-docs/docs/runtime/git-sources">Git Sources</a>.</li></ul></li></li><li>Labels:The K8s labels defined for the applications. The list displays labels of <i>all</i> the applications, even if you have applied filters.<br>To see the available labels, select <b>Add</b>, and then select the required label and one or more values. <br>To filter by the labels, select <b>Add</b> and then <b>Apply</b>.<br> See the official documentation on <a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/labels" target=”_blank”>Labels and selectors</a>.</li></ul></ul>{:/}|
-|{::nomarkdown}<img src="../../../images/icons/icon-mark-favorite.png?display=inline-block">{:/}| Star applications as favorites and view only the starred applications.{::nomarkdown}<br>Select the <img src="../../../images/icons/icon-mark-favorite.png?display=inline-block"> to star the application as a favorite.<br><br>To filter by favorite applications, on the filters bar, select <img src="../../../images/icons/icon-fav-starred.png?display=inline-block">.<br>{:/} TIP: If you star applications as favorites in the Applications dashboard, you can filter by the same applications in the [DORA metrics dashboard]({{site.baseurl}}/docs/reporting/dora-metrics/#metrics-for-favorite-applications).  |
+|{::nomarkdown}<img src="../../../../images/icons/icon-mark-favorite.png?display=inline-block">{:/}| Star applications as favorites and view only the starred applications.{::nomarkdown}<br>Select the <img src="../../../../images/icons/icon-mark-favorite.png?display=inline-block"> to star the application as a favorite.<br><br>To filter by favorite applications, on the filters bar, select <img src="../../../../images/icons/icon-fav-starred.png?display=inline-block">.<br>{:/} TIP: If you star applications as favorites in the Applications dashboard, you can filter by the same applications in the [DORA metrics dashboard]({{site.baseurl}}/docs/reporting/dora-metrics/#metrics-for-favorite-applications).  |
 |Application actions| Options to monitor/manage applications through the application's context menu. {::nomarkdown}<ul><li>Quick view<br>A comprehensive read-only view of the deployment and definition information for the application.</li>{:/}See [Application Quick View](#view-deployment-and-configuration-info-for-selected-application) in this article.{::nomarkdown}<li>Synchronize/Sync<br>Manually synchronize the application.</li>{:/}See [Manually sync applications]({{site.baseurl}}/docs/deployments/gitops/manage-application/#manually-synchronize-an-application).{::nomarkdown}<li>Edit<br>Modify application definitions.</li>{:/}See [Edit application definitions]({{site.baseurl}}/docs/deployments/gitops/manage-application/#edit-application-definitions).{::nomarkdown}<li>Refresh and Hard Refresh: Available in Card view only. In List view, you must first select the application. <ul><li>Refresh: Retrieve desired (Git) state, compare with the live (cluster) state, and refresh the application to sync with the desired state.</li><li>Hard Refresh: Refresh the application to sync with the Git state, while removing the cache.</li></ul>{:/} |
 
 
@@ -166,7 +166,8 @@ max-width="50%"
 
 
 
-#### Quick View: Summary
+### Quick View: Summary
+
 Displays health, sync status, and source and destination definitions.
 
 {% include
@@ -179,7 +180,9 @@ caption="Application Quick View: Summary"
 max-width="30%"
 %}
 
-#### Quick View: Metadata
+
+### Quick View: Metadata
+
 Displays labels and annotations for the application.
 
 {% include
@@ -192,7 +195,9 @@ caption="Application Quick View: Metadata"
 max-width="30%"
 %}
 
-#### Quick View: Parameters
+
+### Quick View: Parameters
+
 Displays parameters configured for the application, based on the tool used to create the application's manifests.  
 The parameters displayed differ according to the tool:  `directory` (as in the screenshot below), `Helm` charts, or `Kustomize` manifests, or the specific plugin.  
 
@@ -206,7 +211,8 @@ caption="Application Quick View: Parameters"
 max-width="30%"
 %}
 
-#### Quick View: Sync Options
+### Quick View: Sync Options
+
 Displays sync options enabled for the application.
 
 {% include
@@ -219,7 +225,8 @@ caption="Application Quick View: Parameters"
 max-width="30%"
 %}
 
-#### Quick View: Manifest 
+### Quick View: Manifest 
+
 Displays the YAML version of the application manifest.
 
 {% include
@@ -232,7 +239,8 @@ caption="Application Quick View: Manifest"
 max-width="30%"
 %}
 
-#### Quick View: Events
+### Quick View: Events
+
 Displays status and sync events for the application.
 
 {% include
@@ -303,7 +311,7 @@ You can view application resources in [List or Tree views](#view-modes-for-appli
 
 > To quickly see which resources have been added, modified, or removed for the current or for a specific deployment, switch to the Timeline tab and expand the deployment record to show Updated Resources. See [Monitor resource updates for deployments](#monitor-resource-updates-for-deployments).
 
-#### View modes for application resources
+### View modes for application resources
 
 The Current State tab supports Tree and List view formats. 
 * Tree view (default): A hierarchical, interactive visualization of the application and its resources. Useful for complex deployments with multiple clusters and large numbers of resources. See also [Working with resources in Tree view](#working-with-resources-in-tree-view).  
@@ -459,12 +467,14 @@ Identify the health of an application resource through the color-coded border an
 {: .table .table-bordered .table-hover}
 | Health status   | Description | Display in Tree view  | 
 | --------------  | ------------| ------------------|  
-| **Healthy**     | Resource is functioning as required. | {::nomarkdown}<img src="../../../images/icons/current-state-healthy.png" display=inline-block">{:/} | 
-| **Progressing** | Resource is not healthy but can become healthy before the timeout occurs.| {::nomarkdown}<img src="../../../images/icons/current-state-progressing.png" display=inline-block">{:/} | 
-| **Suspended**   | Resource is not functioning, and is either suspended or paused. For example, Cron job or a canary rollout.| {::nomarkdown}<img src="../../../images/icons/current-state-suspended.png" display=inline-block">{:/} | 
+
+| **Healthy**     | Resource is functioning as required. | {::nomarkdown}<img src="../../../../images/icons/current-state-healthy.png" display=inline-block">{:/} | 
+| **Progressing** | Resource is not healthy but can become healthy before the timeout occurs.| {::nomarkdown}<img src="../../../../images/icons/current-state-progressing.png" display=inline-block">{:/} | 
+| **Suspended**   | Resource is not functioning, and is either suspended or paused. For example, Cron job or a canary rollout.| {::nomarkdown}<img src="../../../../images/icons/current-state-suspended.png" display=inline-block">{:/} | 
 | **Missing**     | Resource is not present on the cluster. |{::nomarkdown}<img src="../../../images/icons/current-state-missing.png" display=inline-block">{:/} |                        
-| **Degraded**    | Resource is not healthy, or a timeout occurred before it could reach a healthy status.| {::nomarkdown}<img src="../../../images/icons/current-state-degraded.png" display=inline-block/>{:/} |
-| **Unknown**   | Resource does not have a health status, or the health status is not tracked in Argo CD. For example,`ConfigMaps` resource types.   | {::nomarkdown}<img src="../../../images/icons/current-state-unknown.png" display=inline-block">{:/} | 
+| **Degraded**    | Resource is not healthy, or a timeout occurred before it could reach a healthy status.| {::nomarkdown}<img src="../../../../images/icons/current-state-degraded.png" display=inline-block/>{:/} |
+| **Unknown**   | Resource does not have a health status, or the health status is not tracked in Argo CD. For example,`ConfigMaps` resource types.   | {::nomarkdown}<img src="../../../../images/icons/current-state-unknown.png" display=inline-block">{:/} | 
+
 
 See also [Argo CD's set of health checks](https://argo-cd.readthedocs.io/en/stable/operator-manual/health/){:target="\_blank"}.
 
@@ -480,10 +490,12 @@ The table describes the possible sync statuses for an application resource, and
 {: .table .table-bordered .table-hover}
 | Sync state     | Description |Display in Tree view  |  
 | -------------- | ----------    | ----------     |  
-| **Synced**       | The live state of the resource on the cluster is identical to the desired state in Git.| {::nomarkdown}<img src="../../../images/icons/current-state-synced.png" display=inline-block">{:/} |                            
-| **Syncing**      | The live state of the resource was not identical to the desired state, and is currently being synced.| {::nomarkdown}<img src="../../../images/icons/current-state-syncing.png" display=inline-block/>{:/} |  
-| **Out-of-Sync**  | {::nomarkdown}The live state is not identical to the desired state.<br>To sync a resource, select the <b>Sync</b> option from the resource's context menu in Tree view. {:/}| {::nomarkdown}<img src="../../../images/icons/current-state-out-of-sync.png" display=inline-block">{:/} |  
-| **Unknown**      | The sync status could not be determined. | {::nomarkdown}<img src="../../../images/icons/current-state-sync-unknown.png" display=inline-block">{:/} |  
+
+| **Synced**       | The live state of the resource on the cluster is identical to the desired state in Git.| {::nomarkdown}<img src="../../../../images/icons/current-state-synced.png" display=inline-block">{:/} |                            
+| **Syncing**      | The live state of the resource was not identical to the desired state, and is currently being synced.| {::nomarkdown}<img src="../../../../images/icons/current-state-syncing.png" display=inline-block/>{:/} |  
+| **Out-of-Sync**  | {::nomarkdown}The live state is not identical to the desired state.<br>To sync a resource, select the <b>Sync</b> option from the resource's context menu in Tree view. {:/}| {::nomarkdown}<img src="../../../../images/icons/current-state-out-of-sync.png" display=inline-block">{:/} |  
+| **Unknown**      | The sync status could not be determined. | {::nomarkdown}<img src="../../../../images/icons/current-state-sync-unknown.png" display=inline-block">{:/} |  
+
 
 > The application header displays the statuses of the current and previous sync operations. Clicking **More** opens the Sync panels with Sync Info, Sync Result and Commit Info.
   The Application Warnings/Errors panel surfaces sync errors on exceeding the maximum number of retries and when a sync operation extends beyond 30 minutes.
@@ -767,8 +779,9 @@ max-width="50%"
 %}
 
 ## Related articles
-[Creating GitOps applications]({{site.baseurl}})/docs/deployments/gitops/create-application)  
-[Managing GitOps applications]({{site.baseurl}})/docs/deployments/gitops/manage-applications)  
+
+[Creating GitOps applications]({{site.baseurl}}/docs/deployments/gitops/create-application)  
+[Managing GitOps applications]({{site.baseurl}}/docs/deployments/gitops/manage-applications)  
 [Home dashboard]({{site.baseurl}}/docs/reporting/home-dashboard)  
 [DORA metrics]({{site.baseurl}}/docs/reporting/dora-metrics/)  
 
diff --git a/_docs/deployments/gitops/images.md b/_docs/deployments/gitops/images.md
index eb46e3d9..80984226 100644
--- a/_docs/deployments/gitops/images.md
+++ b/_docs/deployments/gitops/images.md
@@ -114,7 +114,8 @@ Selecting **more details** for an image tag.
 | **5**             | The log information for the build image step in the relevant workflow. Select to view Logs panel. |
 
 ## Related articles
-[Creating GitOps applications]({{site.baseurl}})/docs/deployments/gitops/create-application)  
-[Managing GitOps applications]({{site.baseurl}})/docs/deployments/gitops/manage-applications)  
+
+[Creating GitOps applications]({{site.baseurl}}/docs/deployments/gitops/create-application)  
+[Managing GitOps applications]({{site.baseurl}}/docs/deployments/gitops/manage-applications)  
 [Image enrichment with integrations]({{site.baseurl}}/integrations/image-enrichment-overview)  
 [Home dashboard]({{site.baseurl}}/docs/reporting/home-dashboard)  
diff --git a/_docs/deployments/helm/helm-charts-and-repositories.md b/_docs/deployments/helm/helm-charts-and-repositories.md
index 1fd079d3..8edfe049 100644
--- a/_docs/deployments/helm/helm-charts-and-repositories.md
+++ b/_docs/deployments/helm/helm-charts-and-repositories.md
@@ -3,10 +3,6 @@ title: "Using external Helml repos in Codefresh pipelines"
 description: "Use external Helm Charts and repositories in Codefresh pipelines"
 group: deployments
 sub_group: helm
-permalink: /:collection/deployments/helm/add-helm-repository/
-redirect_from:
-  - /docs/deployments/helm/
-  - /docs/add-helm-repository/
 toc: true
 ---
 Codefresh allows you to integrate with external Helm repositories and Helm charts in the Helm Charts page.  
@@ -26,8 +22,8 @@ By default, we show charts from the [official Helm repository](https://github.co
 
 {% include image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/quick-helm-integration.png" 
-url="/images/kubernetes-helm/quick-helm-integration.png" 
+file="/images/deployments/helm/quick-helm-integration.png" 
+url="/images/deployments/helm/quick-helm-integration.png" 
 alt="Adding a Helm repository"
 caption="Adding a Helm repository" 
 max-width="70%" 
@@ -50,8 +46,8 @@ Once connected, inject any Helm repository context into Codefresh pipelines.
 
 {% include image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/connect-helm-repo.png" 
-url="/images/kubernetes-helm/connect-helm-repo.png" 
+file="/images/deployments/helm/connect-helm-repo.png" 
+url="/images/deployments/helm/connect-helm-repo.png" 
 alt="Connecting a Helm repository in the pipeline"
 caption="Connecting a Helm repository in the pipeline" 
 max-width="70%" 
diff --git a/_docs/deployments/helm/helm-environment-promotion.md b/_docs/deployments/helm/helm-environment-promotion.md
index 2b526b14..21466e5d 100644
--- a/_docs/deployments/helm/helm-environment-promotion.md
+++ b/_docs/deployments/helm/helm-environment-promotion.md
@@ -1,5 +1,6 @@
 ---
-title: "Helm Environment Promotion"
+
+title: "Promoting Helm Environments"
 description: "Manage your Helm Environments with the Codefresh UI"
 group: deployments
 sub_group: helm
@@ -14,8 +15,8 @@ Here is an example board:
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/promotion/board.png" 
-url="/images/kubernetes-helm/promotion/board.png"
+file="/images/deployments/helm/promotion/board.png" 
+url="/images/deployments/helm/promotion/board.png"
 alt="Helm Environment Dashboard" 
 caption="Helm Environment Dashboard" 
 max-width="80%"
@@ -37,8 +38,8 @@ For each board, you define how many columns it will contain, where each column i
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/promotion/helm-environments.png" 
-url="/images/kubernetes-helm/promotion/helm-environments.png"
+file="/images/deployments/helm/promotion/helm-environments.png" 
+url="/images/deployments/helm/promotion/helm-environments.png"
 alt="Helm environments column structure" 
 caption="Helm environments column structure" 
 max-width="80%"
@@ -63,8 +64,8 @@ Create your own Helm board with a single or multiple Helm applications. You can
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/promotion/board-selection.png" 
-url="/images/kubernetes-helm/promotion/board-selection.png"
+file="/images/deployments/helm/promotion/board-selection.png" 
+url="/images/deployments/helm/promotion/board-selection.png"
 alt="Helm board selection" 
 caption="Helm board selection" 
 max-width="80%"
@@ -89,8 +90,8 @@ Once you create your Helm environment board, you are ready to define its columns
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/promotion/edit-helm-environment.png" 
-url="/images/kubernetes-helm/promotion/edit-helm-environment.png"
+file="/images/deployments/helm/promotion/edit-helm-environment.png" 
+url="/images/deployments/helm/promotion/edit-helm-environment.png"
 alt="Edit Helm environment" 
 caption="Edit Helm environment" 
 max-width="50%"
@@ -122,8 +123,8 @@ For each Helm release, you will get some basic details such as the chart version
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/promotion/expand.png" 
-url="/images/kubernetes-helm/promotion/expand.png"
+file="/images/deployments/helm/promotion/expand.png" 
+url="/images/deployments/helm/promotion/expand.png"
 alt="Helm release details" 
 caption="Helm release details" 
 max-width="50%"
@@ -145,8 +146,8 @@ You can also use the board as an action tool in order to promote/demote a Helm r
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/promotion/shift-right.png" 
-url="/images/kubernetes-helm/promotion/shift-right.png"
+file="/images/deployments/helm/promotion/shift-right.png" 
+url="/images/deployments/helm/promotion/shift-right.png"
 alt="Promoting a Helm release" 
 caption="Promoting a Helm release" 
 max-width="80%"
@@ -157,8 +158,8 @@ Once you drop the release you will also see the promotion dialog.
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/promotion/promote-settings.png" 
-url="/images/kubernetes-helm/promotion/promote-settings.png"
+file="/images/deployments/helm/promotion/promote-settings.png" 
+url="/images/deployments/helm/promotion/promote-settings.png"
 alt="Promotion Settings" 
 caption="Promotion Settings" 
 max-width="40%"
@@ -171,8 +172,8 @@ By clicking the *Variables* button you can override the chart values, import a s
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/promotion/value-options.png" 
-url="/images/kubernetes-helm/promotion/value-options.png"
+file="/images/deployments/helm/promotion/value-options.png" 
+url="/images/deployments/helm/promotion/value-options.png"
 alt="Changing deployment values" 
 caption="Changing deployment values" 
 max-width="40%"
@@ -249,8 +250,8 @@ For any existing Helm board, you have the following options:
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/promotion/board-management.png" 
-url="/images/kubernetes-helm/promotion/board-management.png"
+file="/images/deployments/helm/promotion/board-management.png" 
+url="/images/deployments/helm/promotion/board-management.png"
 alt="Editing a Helm environment" 
 caption="Editing a Helm environment" 
 max-width="80%"
@@ -273,8 +274,8 @@ The filtering options allow you to further constrain the Helm release shown for
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/promotion/filter.png" 
-url="/images/kubernetes-helm/promotion/filter.png"
+file="/images/deployments/helm/promotion/filter.png" 
+url="/images/deployments/helm/promotion/filter.png"
 alt="Filtering options" 
 caption="Filtering options" 
 max-width="50%"
diff --git a/_docs/deployments/helm/helm-releases-management.md b/_docs/deployments/helm/helm-releases-management.md
index aeffd4b6..991701f7 100644
--- a/_docs/deployments/helm/helm-releases-management.md
+++ b/_docs/deployments/helm/helm-releases-management.md
@@ -25,8 +25,8 @@ View all the Helm releases in your cluster, and drill down into a specific relea
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/dashboard/helm-release-dashboard.png" 
-url="/images/kubernetes-helm/dashboard/helm-release-dashboard.png"
+file="/images/deployments/helm/dashboard/helm-release-dashboard.png" 
+url="/images/deployments/helm/dashboard/helm-release-dashboard.png"
 alt="Helm Releases" 
 caption="Helm Releases" 
 max-width="90%"
@@ -55,8 +55,8 @@ For Helm 2 releases, Codefresh will try to find the server component (Tiller) in
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/dashboard/services.png" 
-url="/images/kubernetes-helm/dashboard/services.png"
+file="/images/deployments/helm/dashboard/services.png" 
+url="/images/deployments/helm/dashboard/services.png"
 alt="Kubernetes Services" 
 caption="Kubernetes Services" 
 max-width="70%"
@@ -67,8 +67,8 @@ The History tab shows all previous releases.
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/dashboard/history.png" 
-url="/images/kubernetes-helm/dashboard/history.png"
+file="/images/deployments/helm/dashboard/history.png" 
+url="/images/deployments/helm/dashboard/history.png"
 alt="Helm History" 
 caption="Helm History"
 max-width="60%"
@@ -79,8 +79,8 @@ You can further expand a release revision to see exactly what files were changed
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/dashboard/diff.png" 
-url="/images/kubernetes-helm/dashboard/diff.png"
+file="/images/deployments/helm/dashboard/diff.png" 
+url="/images/deployments/helm/dashboard/diff.png"
 alt="Helm diff" 
 caption="Helm diff" 
 max-width="60%"
@@ -91,8 +91,8 @@ There are other tabs that show you the chart used, the values as well as the fin
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/dashboard/manifests.png" 
-url="/images/kubernetes-helm/dashboard/manifests.png"
+file="/images/deployments/helm/dashboard/manifests.png" 
+url="/images/deployments/helm/dashboard/manifests.png"
 alt="Final rendered manifests" 
 caption="Final rendered manifests" 
 max-width="50%"
@@ -134,8 +134,8 @@ can help show the main reason behind each release, or any other message that is
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/dashboard/helm-commit-message.png" 
-url="/images/kubernetes-helm/dashboard/helm-commit-message.png"
+file="/images/deployments/helm/dashboard/helm-commit-message.png" 
+url="/images/deployments/helm/dashboard/helm-commit-message.png"
 alt="Helm release message" 
 caption="Helm release message" 
 max-width="70%"
@@ -158,8 +158,8 @@ You can rollback to a previous revision of a release in the History tab.
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/dashboard/rollback.png" 
-url="/images/kubernetes-helm/dashboard/rollback.png"
+file="/images/deployments/helm/dashboard/rollback.png" 
+url="/images/deployments/helm/dashboard/rollback.png"
 alt="Rolling back to a previous release" 
 caption="Rolling back to a previous release" 
 max-width="50%"
@@ -186,8 +186,8 @@ Similar to a [build badge]({{site.baseurl}}/docs/pipelines/build-status/#using-t
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/dashboard/helm-badge.png" 
-url="/images/kubernetes-helm/dashboard/helm-badge.png"
+file="/images/deployments/helm/dashboard/helm-badge.png" 
+url="/images/deployments/helm/dashboard/helm-badge.png"
 alt="Helm Deployment badge" 
 caption="Helm Deployment badge" 
 max-width="60%"
@@ -216,8 +216,8 @@ You can override these actions for a specific Helm release by defining custom pi
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/dashboard/override-helm-actions.png" 
-url="/images/kubernetes-helm/dashboard/override-helm-actions.png"
+file="/images/deployments/helm/dashboard/override-helm-actions.png" 
+url="/images/deployments/helm/dashboard/override-helm-actions.png"
 alt="Changing default Helm actions" 
 caption="Changing default Helm actions" 
 max-width="50%"
diff --git a/_docs/deployments/helm/managed-helm-repository.md b/_docs/deployments/helm/managed-helm-repository.md
index b06a0e5d..5dcd43b5 100644
--- a/_docs/deployments/helm/managed-helm-repository.md
+++ b/_docs/deployments/helm/managed-helm-repository.md
@@ -27,8 +27,8 @@ The Codefresh-managed Helm repo is displayed with other Helm repositories you ha
 {% include 
 image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/private-helm-repo/managed-helm-repo.png" 
-url="/images/kubernetes-helm/private-helm-repo/managed-helm-repo.png"
+file="/images/deployments/helm/private-helm-repo/managed-helm-repo.png"
+url="/images/deployments/helm/private-helm-repo/managed-helm-repo.png"
 alt="Codefresh built-in Helm repository" 
 caption="Codefresh built-in Helm repository" 
 max-width="50%" 
diff --git a/_docs/deployments/helm/using-helm-in-codefresh-pipeline.md b/_docs/deployments/helm/using-helm-in-codefresh-pipeline.md
index 6e3a66a6..f96ddd4f 100644
--- a/_docs/deployments/helm/using-helm-in-codefresh-pipeline.md
+++ b/_docs/deployments/helm/using-helm-in-codefresh-pipeline.md
@@ -54,8 +54,8 @@ The Helm pipeline step requires the configuration of a `kube_context` variable t
 
 {% include image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/k8s-name.png" 
-url="/images/kubernetes-helm/k8s-name.png" 
+file="/images/deployments/helm/k8s-name.png" 
+url="/images/deployments/helm/k8s-name.png" 
 alt="Name of Kubernetes cluster"
 caption="Name of Kubernetes cluster" 
 max-width="70%" 
@@ -87,8 +87,8 @@ Once you have a connected to a Helm repository, attach it to the pipeline.
 
 {% include image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/import-helm-configuration.png" 
-url="/images/kubernetes-helm/import-helm-configuration.png" 
+file="/images/deployments/helm/import-helm-configuration.png" 
+url="/images/deployments/helm/import-helm-configuration.png" 
 alt="Connecting a Helm repository in the pipeline"
 caption="Connecting a Helm repository in the pipeline" 
 max-width="50%" 
@@ -266,8 +266,8 @@ The pipeline in this example builds a docker image, runs unit tests, stores the
 
 {% include image.html 
 lightbox="true" 
-file="/images/kubernetes-helm/full-helm-pipeline.png" 
-url="/images/kubernetes-helm/full-helm-pipeline.png" 
+file="/images/deployments/helm/full-helm-pipeline.png" 
+url="/images/deployments/helm/full-helm-pipeline.png" 
 alt="Helm pipeline"
 caption="Helm pipeline" 
 max-width="90%" 
diff --git a/_docs/deployments/kubernetes/custom-kubectl-commands.md b/_docs/deployments/kubernetes/custom-kubectl-commands.md
index 7c22b13b..77bc7411 100644
--- a/_docs/deployments/kubernetes/custom-kubectl-commands.md
+++ b/_docs/deployments/kubernetes/custom-kubectl-commands.md
@@ -1,5 +1,5 @@
 ---
-title: "Running custom kubectl commands"
+title: "Custom kubectl commands"
 description: "Use kubectl in your Codefresh pipelines"
 group: deployments
 sub_group: kubernetes
@@ -45,8 +45,8 @@ your [kubeconfig files](https://kubernetes.io/docs/concepts/configuration/organi
 
 {% include image.html 
 lightbox="true" 
-file="/images/kubernetes/custom-kubectl/kube-context.png" 
-url="/images/kubernetes/custom-kubectl/kube-context.png"
+file="/images/deployments/kubernetes/kube-context.png" 
+url="/images/deployments/kubernetes/kube-context.png"
 alt="Codefresh cluster names"
 caption="Codefresh cluster names"
 max-width="50%"
@@ -104,8 +104,8 @@ Here is the pipeline:
 
 {% include image.html 
 lightbox="true" 
-file="/images/kubernetes/custom-kubectl/parallel-kubectl.png" 
-url="/images/kubernetes/custom-kubectl/parallel-kubectl.png"
+file="/images/deployments/kubernetes/parallel-kubectl.png" 
+url="/images/deployments/kubernetes/parallel-kubectl.png"
 alt="Parallel kubectl deployment"
 caption="Parallel kubectl deployment"
 max-width="100%"
diff --git a/_docs/deployments/kubernetes/deployment-options-to-kubernetes.md b/_docs/deployments/kubernetes/deployment-options-to-kubernetes.md
index c79d25a4..ed56a0b1 100644
--- a/_docs/deployments/kubernetes/deployment-options-to-kubernetes.md
+++ b/_docs/deployments/kubernetes/deployment-options-to-kubernetes.md
@@ -76,9 +76,10 @@ Wait until the deployment is completed, and you can open the deployed applicatio
 
 {% include image.html 
 lightbox="true" 
-file="/images/3f36367-Screenshot_from_2018-02-16_17-09-54.png" 
-url="/images/3f36367-Screenshot_from_2018-02-16_17-09-54.png" 
-alt="Screenshot from 2018-02-16 17-09-54.png" 
+file="/images/deployments/kubernetes/describe-k8s-deployment.png" 
+url="/images/deployments/kubernetes/describe-k8s-deployment.png" 
+alt="Describe Kubernetes deployment" 
+caption="Describe Kubernetes deployment" 
 max-width="60%" 
 %}
 
diff --git a/_docs/deployments/kubernetes/manage-kubernetes.md b/_docs/deployments/kubernetes/manage-kubernetes.md
index 6990c6d0..986fb08d 100644
--- a/_docs/deployments/kubernetes/manage-kubernetes.md
+++ b/_docs/deployments/kubernetes/manage-kubernetes.md
@@ -1,5 +1,5 @@
 ---
-title: "Manage your Kubernetes cluster"
+title: "Managing Kubernetes clusters"
 description: "Use the graphical Kubernetes dashboard in Codefresh"
 group: deployments
 sub_group: kubernetes
@@ -17,8 +17,8 @@ After [adding a cluster]({{site.baseurl}}/docs/integrations/kubernetes/#connect-
 
 {% include image.html
 lightbox="true"
-file="/images/kubernetes/dashboard/kubernetes-dashboard.png"
-url="/images/kubernetes/dashboard/kubernetes-dashboard.png"
+file="/images/deployments/kubernetes/kubernetes-dashboard.png"
+url="/images/deployments/kubernetes/kubernetes-dashboard.png"
 alt="Codefresh Kubernetes Dashboard"
 caption="Codefresh Kubernetes Dashboard"
 max-width="80%"
diff --git a/images/deployments/helm/add-helm-repository.png b/images/deployments/helm/add-helm-repository.png
new file mode 100644
index 00000000..f9227b25
Binary files /dev/null and b/images/deployments/helm/add-helm-repository.png differ
diff --git a/images/deployments/helm/connect-helm-repo.png b/images/deployments/helm/connect-helm-repo.png
new file mode 100644
index 00000000..57631986
Binary files /dev/null and b/images/deployments/helm/connect-helm-repo.png differ
diff --git a/images/deployments/helm/diff.png b/images/deployments/helm/diff.png
new file mode 100644
index 00000000..56888435
Binary files /dev/null and b/images/deployments/helm/diff.png differ
diff --git a/images/deployments/helm/full-helm-pipeline.png b/images/deployments/helm/full-helm-pipeline.png
new file mode 100644
index 00000000..429cbe4c
Binary files /dev/null and b/images/deployments/helm/full-helm-pipeline.png differ
diff --git a/images/deployments/helm/helm-badge.png b/images/deployments/helm/helm-badge.png
new file mode 100644
index 00000000..ff284dcd
Binary files /dev/null and b/images/deployments/helm/helm-badge.png differ
diff --git a/images/deployments/helm/helm-commit-message.png b/images/deployments/helm/helm-commit-message.png
new file mode 100644
index 00000000..b9433254
Binary files /dev/null and b/images/deployments/helm/helm-commit-message.png differ
diff --git a/images/deployments/helm/helm-release-dashboard.png b/images/deployments/helm/helm-release-dashboard.png
new file mode 100644
index 00000000..c7078f88
Binary files /dev/null and b/images/deployments/helm/helm-release-dashboard.png differ
diff --git a/images/deployments/helm/history.png b/images/deployments/helm/history.png
new file mode 100644
index 00000000..c00e3e5a
Binary files /dev/null and b/images/deployments/helm/history.png differ
diff --git a/images/deployments/helm/import-helm-configuration.png b/images/deployments/helm/import-helm-configuration.png
new file mode 100644
index 00000000..17fbbf3c
Binary files /dev/null and b/images/deployments/helm/import-helm-configuration.png differ
diff --git a/images/deployments/helm/k8s-name.png b/images/deployments/helm/k8s-name.png
new file mode 100644
index 00000000..24197bb2
Binary files /dev/null and b/images/deployments/helm/k8s-name.png differ
diff --git a/images/deployments/helm/managed-helm-repo.png b/images/deployments/helm/managed-helm-repo.png
new file mode 100644
index 00000000..0a9d0c5b
Binary files /dev/null and b/images/deployments/helm/managed-helm-repo.png differ
diff --git a/images/deployments/helm/manifests.png b/images/deployments/helm/manifests.png
new file mode 100644
index 00000000..67e4ad30
Binary files /dev/null and b/images/deployments/helm/manifests.png differ
diff --git a/images/deployments/helm/override-helm-actions.png b/images/deployments/helm/override-helm-actions.png
new file mode 100644
index 00000000..db9a39df
Binary files /dev/null and b/images/deployments/helm/override-helm-actions.png differ
diff --git a/images/deployments/helm/promotion/board-management.png b/images/deployments/helm/promotion/board-management.png
new file mode 100644
index 00000000..8b99e0a8
Binary files /dev/null and b/images/deployments/helm/promotion/board-management.png differ
diff --git a/images/deployments/helm/promotion/board-selection.png b/images/deployments/helm/promotion/board-selection.png
new file mode 100644
index 00000000..01922b53
Binary files /dev/null and b/images/deployments/helm/promotion/board-selection.png differ
diff --git a/images/deployments/helm/promotion/board.png b/images/deployments/helm/promotion/board.png
new file mode 100644
index 00000000..bbd35458
Binary files /dev/null and b/images/deployments/helm/promotion/board.png differ
diff --git a/images/deployments/helm/promotion/edit-helm-environment.png b/images/deployments/helm/promotion/edit-helm-environment.png
new file mode 100644
index 00000000..7e06aa85
Binary files /dev/null and b/images/deployments/helm/promotion/edit-helm-environment.png differ
diff --git a/images/deployments/helm/promotion/edit-value.png b/images/deployments/helm/promotion/edit-value.png
new file mode 100644
index 00000000..b28abfb2
Binary files /dev/null and b/images/deployments/helm/promotion/edit-value.png differ
diff --git a/images/deployments/helm/promotion/expand.png b/images/deployments/helm/promotion/expand.png
new file mode 100644
index 00000000..9e4d063f
Binary files /dev/null and b/images/deployments/helm/promotion/expand.png differ
diff --git a/images/deployments/helm/promotion/filter.png b/images/deployments/helm/promotion/filter.png
new file mode 100644
index 00000000..a429fd40
Binary files /dev/null and b/images/deployments/helm/promotion/filter.png differ
diff --git a/images/deployments/helm/promotion/helm-environments.png b/images/deployments/helm/promotion/helm-environments.png
new file mode 100644
index 00000000..4b584979
Binary files /dev/null and b/images/deployments/helm/promotion/helm-environments.png differ
diff --git a/images/deployments/helm/promotion/promote-settings.png b/images/deployments/helm/promotion/promote-settings.png
new file mode 100644
index 00000000..4d965ac5
Binary files /dev/null and b/images/deployments/helm/promotion/promote-settings.png differ
diff --git a/images/deployments/helm/promotion/promote.png b/images/deployments/helm/promotion/promote.png
new file mode 100644
index 00000000..94bd01a8
Binary files /dev/null and b/images/deployments/helm/promotion/promote.png differ
diff --git a/images/deployments/helm/promotion/shift-left.png b/images/deployments/helm/promotion/shift-left.png
new file mode 100644
index 00000000..cce3c937
Binary files /dev/null and b/images/deployments/helm/promotion/shift-left.png differ
diff --git a/images/deployments/helm/promotion/shift-right.png b/images/deployments/helm/promotion/shift-right.png
new file mode 100644
index 00000000..54d1a2ff
Binary files /dev/null and b/images/deployments/helm/promotion/shift-right.png differ
diff --git a/images/deployments/helm/promotion/value-options.png b/images/deployments/helm/promotion/value-options.png
new file mode 100644
index 00000000..5ce6820f
Binary files /dev/null and b/images/deployments/helm/promotion/value-options.png differ
diff --git a/images/deployments/helm/quick-helm-integration.png b/images/deployments/helm/quick-helm-integration.png
new file mode 100644
index 00000000..d6e7ced4
Binary files /dev/null and b/images/deployments/helm/quick-helm-integration.png differ
diff --git a/images/deployments/helm/rollback.png b/images/deployments/helm/rollback.png
new file mode 100644
index 00000000..5ff38aae
Binary files /dev/null and b/images/deployments/helm/rollback.png differ
diff --git a/images/deployments/helm/services.png b/images/deployments/helm/services.png
new file mode 100644
index 00000000..e9e00b23
Binary files /dev/null and b/images/deployments/helm/services.png differ
diff --git a/images/deployments/kubernetes/describe-k8s-deployment.png b/images/deployments/kubernetes/describe-k8s-deployment.png
new file mode 100644
index 00000000..68be6815
Binary files /dev/null and b/images/deployments/kubernetes/describe-k8s-deployment.png differ
diff --git a/images/deployments/kubernetes/grid-view.png b/images/deployments/kubernetes/grid-view.png
new file mode 100644
index 00000000..d05e9e55
Binary files /dev/null and b/images/deployments/kubernetes/grid-view.png differ
diff --git a/images/deployments/kubernetes/kube-context.png b/images/deployments/kubernetes/kube-context.png
new file mode 100644
index 00000000..c94744a6
Binary files /dev/null and b/images/deployments/kubernetes/kube-context.png differ
diff --git a/images/deployments/kubernetes/kubernetes-dashboard.png b/images/deployments/kubernetes/kubernetes-dashboard.png
new file mode 100644
index 00000000..1a78c079
Binary files /dev/null and b/images/deployments/kubernetes/kubernetes-dashboard.png differ
diff --git a/images/deployments/kubernetes/parallel-kubectl.png b/images/deployments/kubernetes/parallel-kubectl.png
new file mode 100644
index 00000000..9945bfe6
Binary files /dev/null and b/images/deployments/kubernetes/parallel-kubectl.png differ