Update x-refs

Author: NimRegev

_docs/ci-cd-guides/helm-best-practices.md

@@ -63,7 +63,7 @@ Here is a list of important Helm points that are often controversial between tea
 
 ### Helm repositories are optional
 
-Using Helm repositories is a recommended practice, but completely optional. You can deploy a Helm chart to a Kubernetes cluster directly from the filesystem. The [quick start guide]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/) describes this scenario.
+Using Helm repositories is a recommended practice, but completely optional. You can deploy a Helm chart to a Kubernetes cluster directly from the filesystem. The [quick start guide]({{site.baseurl}}/docs/quick-start/deploy-with-helm/) describes this scenario.
 
 Helm can install a chart either in the package (`.tgz`) or unpackaged (tree of files) to a Kubernetes cluster right away. Thus, the most minimal Helm pipeline has only two steps:
 
@@ -360,7 +360,7 @@ There are different pipelines for:
 While this workflow is very flexible, it adds complexity on the number of Helm charts available (since they exist in multiple Helm repositories). You also need to set up the parameters between the different pipelines so that Helm charts to be deployed can be indeed found in the expected Helm repository.
 
 ## Related articles
-[Helm quick start guide]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/)  
+[Helm quick start guide]({{site.baseurl}}/docs/quick-start/deploy-with-helm/)  
 [Using Helm in a Codefresh pipeline]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/)  
 [Helm Dashboard]({{site.baseurl}}/docs/deployments/helm/helm-releases-management)  
 [Helm Promotion boards]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion)  

_docs/ci-cd-guides/kubernetes-templating.md

@@ -15,7 +15,7 @@ Once you start working with Kubernetes you will see the need for using templates
 
 Kubernetes does not provide any templating mechanism on its own. Deployed manifests are expected to be static yaml files. An external solution is needed if you want to pass parameters in your manifests.
 
-The proper way to handle templates is within [Helm]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/). Helm is the package manager for Kubernetes and also includes templating capabilities.
+The proper way to handle templates is within [Helm]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-with-helm/) . Helm is the package manager for Kubernetes and also includes templating capabilities.
 
 To use templates without using Helm, there are several templating solutions available including [Kustomize](https://github.com/kubernetes-sigs/kustomize){:target="\_blank"} from Google. 
 

_docs/deployments/helm/custom-helm-uploads.md

@@ -12,7 +12,7 @@ Helm packages are just TAR files. Helm repositories are simple file hierarchies
 You can run custom commands and manually upload indexes and packages to a Helm repo.
 
 >This articles shows some non-standard Helm examples.  
-  For the basic use cases, or if you are just getting started with Helm, see our [Helm quick start guide]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/) and [Using Helm in pipelines]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/).
+  For the basic use cases, or if you are just getting started with Helm, see our [Helm quick start guide]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-with-helm/)  and [Using Helm in pipelines]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/).
 
 ## Package a Helm chart
 Below is an example of a freestyle step in a Codefresh pipeline that packages the Helm chart and then extracts the chart name from the command output. It also saves that package name in an environment variable for later use.

_docs/deployments/helm/using-helm-in-codefresh-pipeline.md

@@ -14,7 +14,7 @@ We created a [special Helm step](https://codefresh.io/steps/step/helm){:target="
 > If you have a special use case that is not covered by the Codefresh Helm step, you can always use the regular `helm` cli in a freestyle step.  
   In this case, you can use the simpler container `codefresh/kube-helm` which includes only Kubectl and helm tools. `kube-helm` is available on DockerHub: [https://hub.docker.com/r/codefresh/kube-helm/](https://hub.docker.com/r/codefresh/kube-helm/){:target="\_blank"}.
 
-If you are just starting with Helm, refer to our [Helm quick start guide]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/). And, if you prefer to work directly with code, see our [full Helm example]({{site.baseurl}}/docs/example-catalog/cd-examples/helm/).
+If you are just starting with Helm, refer to our [Helm quick start guide]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-with-helm/) . And, if you prefer to work directly with code, see our [full Helm example]({{site.baseurl}}/docs/example-catalog/cd-examples/helm/).
 
 ## Helm setup
 

_docs/deployments/kubernetes/deployment-options-to-kubernetes.md

@@ -24,7 +24,7 @@ Codefresh offers several options when it comes to Kubernetes deployments:
 1. Using a [freestyle]({{site.baseurl}}/docs/codefresh-yaml/steps/freestyle/) step with your own `kubectl` commands  
   This deployment option gives you great flexibility, but assumes that you know how to work with `kubectl`. See [Custom kubectl commands]({{site.baseurl}}/docs/deployments/kubernetes/custom-kubectl-commands/).
 1. Using Helm as a package manager  
-  See our [Helm quick start guide]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/).
+  See our [Helm quick start guide]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-with-helm/) .
 
 ## Prerequisites
 

_docs/integrations/helm.md

@@ -16,7 +16,7 @@ Native support for Helm in Codefresh includes:
  * A dashboard for [Helm environments]({{site.baseurl}}/docs/deployments/kubernetes/environment-dashboard/)
 
 The built-in Helm repository is production ready. You can start using Helm right away with your Codefresh account,
-even if you don't have an external Helm repository. See our [quick start guide for Helm]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/) or the [complete Helm example]({{site.baseurl}}/docs/example-catalog/cd-examples/helm/).  
+even if you don't have an external Helm repository. See our [quick start guide for Helm]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-with-helm/)  or the [complete Helm example]({{site.baseurl}}/docs/example-catalog/cd-examples/helm/).  
 
 For each Helm integration, you can toggle the level of access by [non-admin users]({{site.baseurl}}/docs/administration/access-control/#users-and-administrators). 
 

_docs/pipelines/running-pipelines-locally.md

@@ -1,7 +1,7 @@
 ---
 title: "Running pipelines locally"
 description: "How to run Codefresh pipelines on your workstation"
-group: configure-ci-cd-pipeline
+group: pipelines
 toc: true
 redirect_from:
   - /docs/troubleshooting/common-issues/debugging-codefresh-builds-locally/

_docs/pipelines/service-containers.md

@@ -1,5 +1,5 @@
 ---
-title: "Service containers in CI pipelines"
+title: "Service containers in pipelines"
 description: "How to use sidecar services in your pipelines"
 group: pipelines
 toc: true

_docs/pipelines/steps/deploy.md

@@ -17,7 +17,7 @@ It has two modes:
 automatically update the service/deployment with the new docker image.
 1. Using the `file_path` option. In this case you provide your own Kubernetes manifest and Codefresh deploys it as-is. It is **your
 own responsibility** to do [custom replacements]({{site.baseurl}}/docs/deploy-to-kubernetes/kubernetes-templating/) here (for example using [awk](https://en.wikipedia.org/wiki/AWK), [sed](https://www.gnu.org/software/sed/manual/sed.html) or [yq](http://mikefarah.github.io/yq/)). The deploy step is also using the [Codefresh templating mechanism]({{site.baseurl}}/docs/deploy-to-kubernetes/kubernetes-templating/#using-the-codefresh-deploy-image) behind the scenes if you want to take advantage of it. For a full templating solution we also
-suggest you look at [Helm]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/).
+suggest you look at [Helm]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-with-helm/) .
 
 You need to define either one of these fields in the deploy step. If you define `service` you also can select the exact Docker image
 with the `candidate` field (otherwise Codefresh will just reuse the docker image defined in the existing deployment)
@@ -174,7 +174,7 @@ If you find the deploy step limited, feel free to look at the other deployment o
 
 * [The cf-deploy-kubernetes step]({{site.baseurl}}/docs/deploy-to-kubernetes/kubernetes-templating/) 
 * [Custom kubectl commands]({{site.baseurl}}/docs/deploy-to-kubernetes/custom-kubectl-commands/) 
-* [Helm]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/) 
+* [Helm]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-with-helm/)  
 
 ## Related articles
 [Kubernetes Quick start guide]({{site.baseurl}}/docs/getting-started/deployment-to-kubernetes-quick-start-guide/)