Fixes

NimRegev · NimRegev · commit c1a1b66db309 · 2023-01-11T10:35:44.000+02:00
diff --git a/_data/nav.yml b/_data/nav.yml
@@ -395,6 +395,8 @@
 - title: Single Sign-On
   url: /single-sign-on
   pages:
+    - title: Common configuration
+      url: /team-sync
     - title: OpenID Connect
       url: /oidc
       sub-pages:
@@ -409,7 +411,7 @@
         - title: OneLogin
           url: /oidc-onelogin
     - title: SAML
-      url: /saml
+      url: /saml-setup
       sub-pages:
         - title: JumpCloud
           url: /saml-jumpcloud
@@ -421,8 +423,7 @@
           url: /saml-pingid
     - title: LDAP
       url: /ldap
-    - title: Common configuration
-      url: /team-sync
+
 
 
 - title: Reference
diff --git a/_docs/administration/account-user-management/access-control.md b/_docs/administration/account-user-management/access-control.md
@@ -114,7 +114,7 @@ You can assign multiple tags to each cluster, making it easy to define multiple
 
 >By default, all clusters, with and without tags, are displayed and can be edited by all users (but not deleted). As soon as you add at least one tag to a cluster, the cluster is only accessible to users with the required policy rules (explained in the next sections).
 
-### Configure CI pipelines with policy attributes <!---TITLE: add tags to pipelines-->
+### Configure pipelines with policy attributes <!---TITLE: add tags to pipelines-->
 
 Similar to Kubernetes clusters, you can also add tags to specific pipelines. 
 
diff --git a/_docs/deployments/helm/custom-helm-uploads.md b/_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 CI 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/getting-started/helm-quick-start-guide/) 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.
diff --git a/_docs/installation/installation-options.md b/_docs/installation/installation-options.md
@@ -9,7 +9,7 @@ To be changed and updated for ProjectOne
 The Codefresh platform supports two different installation environments, each with different installation options.
 
 * CI/CD installation environment  
-  The CI/CD installation environment is optimized for Continuous Integration/Delivery with Codefresh pipelines. CI pipelines created in Codefresh fetch code from your Git repository, packages/compiles the code, and deploys the final artifact to a target environment.
+  The CI/CD installation environment is optimized for Continuous Integration/Delivery with Codefresh pipelines. Pipelines created in Codefresh fetch code from your Git repository, packages/compiles the code, and deploys the final artifact to a target environment.
 
   The CI/CD installation environment supports these installation options:  
   * Hybrid, where the Codefresh CI/CD UI runs in the Codefresh cloud, and the builds run on customer premises
diff --git a/_docs/pipelines/advanced-workflows.md b/_docs/pipelines/advanced-workflows.md
@@ -1,7 +1,7 @@
 ---
 title: "Advanced workflows with parallel steps"
 description: "Create complex workflows in Codefresh with step dependencies"
-group: codefresh-yaml
+group: pipelines
 toc: true
 ---
 
diff --git a/_docs/pipelines/annotations.md b/_docs/pipelines/annotations.md
@@ -1,7 +1,7 @@
 ---
 title: "Annotations in CI pipelines"
 description: "Mark your builds and projects with extra annotations"
-group: codefresh-yaml
+group: pipelines
 toc: true
 ---
 
diff --git a/_docs/pipelines/condition-expression-syntax.md b/_docs/pipelines/condition-expression-syntax.md
@@ -1,7 +1,7 @@
 ---
 title: "Condition Expression Syntax"
 description: "Condition expressions can be included in each step in your codefresh.yml, and must be satisfied for the step to execute."
-group: codefresh-yaml
+group: pipelines
 redirect_from:
   - /docs/condition-expression-syntax/
   - /docs/codefresh-yaml/expression-condition-syntax/
diff --git a/_docs/pipelines/conditional-execution-of-steps.md b/_docs/pipelines/conditional-execution-of-steps.md
@@ -2,6 +2,7 @@
 title: "Conditional execution of steps"
 description: "Skip specific pipeline steps according to one or more conditions"
 group: pipelines
+sub_group: steps
 redirect_from:
   - /docs/conditional-execution-of-steps/
 toc: true
diff --git a/_docs/pipelines/configuration/build-status.md b/_docs/pipelines/configuration/build-status.md
@@ -2,6 +2,7 @@
 title: "Public logs and status badges"
 description: "Embedding Status Images and viewing public logs"
 group: pipelines
+sub_group: configuration
 toc: true
 redirect_from:
   - /docs/build-status
diff --git a/_docs/pipelines/configuration/pipeline-settings.md b/_docs/pipelines/configuration/pipeline-settings.md
@@ -1,7 +1,8 @@
 ---
-title: "Global settings for CI pipelines"
+title: "Global settings for pipelines"
 description: "Define global options for pipeline templates, yaml sources and approval behavior"
 group: pipelines
+sub_group: configuration
 toc: true
 ---
 
diff --git a/_docs/pipelines/configuration/secrets-store.md b/_docs/pipelines/configuration/secrets-store.md
@@ -1,7 +1,8 @@
 ---
-title: "Secrets in CI pipelines"
+title: "Secrets in pipelines"
 description: "Use Kubernetes secrets in Codefresh"
 group: pipelines
+sub_group: configuration
 toc: true
 ---
 
diff --git a/_docs/pipelines/configuration/shared-configuration.md b/_docs/pipelines/configuration/shared-configuration.md
@@ -1,7 +1,8 @@
 ---
-title: "Shared configuration for CI pipelines"
+title: "Shared configuration for pipelines"
 description: "How to keep your pipelines DRY"
 group: pipelines
+sub_group: configuration
 toc: true
 ---
   
diff --git a/_docs/pipelines/debugging-pipelines.md b/_docs/pipelines/debugging-pipelines.md
@@ -1,5 +1,5 @@
 ---
-title: "Debugging CI pipelines"
+title: "Debugging pipelines"
 description: "Pause and inspect pipelines"
 group: pipelines
 toc: true
diff --git a/_docs/pipelines/docker-image-metadata.md b/_docs/pipelines/docker-image-metadata.md
@@ -147,15 +147,15 @@ You can view an image's metadata annotation by:
 {% 
   include image.html 
   lightbox="true" 
-  file="/images/codefresh-yaml/docker-image-metadata/annotations.png" 
-  url="/images/codefresh-yaml/docker-image-metadata/annotations.png" 
+  file="/images/pipeline/codefresh-yaml/docker-image-metadata/annotations.png" 
+  url="/images/pipeline/codefresh-yaml/docker-image-metadata/annotations.png" 
   alt="Image annotations" 
   max-width="65%" 
 %}
 
 In addition, you can add selected annotations to the images table on images page. To display an annotation in the image table, click on the gear icon at the top right corner of image page and then select all annotations you want to display.
 
-{% include image.html lightbox="true" file="/images/aec92e8-Screen_Shot_2017-10-17_at_3.01.26_PM.png" url="/images/aec92e8-Screen_Shot_2017-10-17_at_3.01.26_PM.png" alt="Screen Shot 2017-10-08 at 8.28.35 AM.png" max-width="40%" %}
+{% include image.html lightbox="true" file="/images/pipeline/codefresh-yaml/docker-image-metadata/annotations-image-table.png" url="images/pipeline/codefresh-yaml/docker-image-metadata/annotations-image-table.png" alt="Annotations in image table" caption="Annotations in image table"max-width="40%" %}
 
 
 ## Annotating images programmatically
diff --git a/_docs/pipelines/hooks.md b/_docs/pipelines/hooks.md
@@ -1,5 +1,5 @@
 ---
-title: "Hooks in CI pipelines"
+title: "Hooks in pipelines"
 description: "Execute commands before/after each pipeline or step"
 group: pipelines
 toc: true
diff --git a/_docs/pipelines/introduction-to-codefresh-pipelines.md b/_docs/pipelines/introduction-to-codefresh-pipelines.md
@@ -23,8 +23,8 @@ Use CI pipelines to:
 {% include 
 image.html 
 lightbox="true" 
-file="/images/pipelines/codefresh-yaml/stages/complex-pipeline.png" 
-url="/images/pipelines/codefresh-yaml/stages/complex-pipeline.png"
+file="/images/pipeline/codefresh-yaml/stages/complex-pipeline.png" 
+url="/images/pipeline/codefresh-yaml/stages/complex-pipeline.png"
 alt="Codefresh CI pipelines" 
 caption="Codefresh CI pipelines"
 max-width="90%"
diff --git a/_docs/pipelines/monitoring-pipelines.md b/_docs/pipelines/monitoring-pipelines.md
@@ -1,5 +1,5 @@
 ---
-title: "Monitoring CI pipelines"
+title: "Monitoring pipelines"
 description: "Viewing your builds and logs"
 group: pipelines
 toc: true
diff --git a/_docs/pipelines/pipeline-caching.md b/_docs/pipelines/pipeline-caching.md
@@ -1,5 +1,5 @@
 ---
-title: "Caching in CI pipelines"
+title: "Caching in pipelines"
 description: "Faster builds with Codefresh caching"
 group: pipelines
 toc: true
diff --git a/_docs/pipelines/pipelines.md b/_docs/pipelines/pipelines.md
@@ -1,6 +1,6 @@
 ---
-title: "Creating CI pipelines"
-description: "Define CI pipelines in Codefresh"
+title: "Creating pipelines"
+description: "Define pipelines in Codefresh"
 group: pipelines
 redirect_from:
   - /docs/pipeline
diff --git a/_docs/pipelines/post-step-operations.md b/_docs/pipelines/post-step-operations.md
@@ -1,7 +1,8 @@
 ---
-title: "Post-Step Operations"
+title: "Post-step operations"
 description: "Annotate your builds and run extra steps"
-group: codefresh-yaml
+group: pipelines
+sub_group: steps
 redirect_from:
   - /docs/post-step-operations/
 toc: true
diff --git a/_docs/pipelines/stages.md b/_docs/pipelines/stages.md
@@ -1,5 +1,5 @@
 ---
-title: "Grouping steps in CI pipelines"
+title: "Grouping steps in pipelines"
 description: "Group steps into stages for better visualization"
 group: pipelines
 toc: true
diff --git a/_docs/pipelines/steps/approval.md b/_docs/pipelines/steps/approval.md
@@ -66,8 +66,8 @@ In the Codefresh UI you will see the *Approve/Reject* buttons.
 {% include 
 image.html 
 lightbox="true" 
-file="/images/codefresh-yaml/approval/build-waiting.png" 
-url="/images/codefresh-yaml/approval/build-waiting.png"
+file="/images/pipeline/codefresh-yaml/approval/build-waiting.png" 
+url="/images/pipeline/codefresh-yaml/approval/build-waiting.png"
 alt="Build waiting for input" 
 caption="Build waiting for input"
 max-width="80%"
@@ -107,8 +107,8 @@ This is a two-step process. First you need to tag your pipeline with one or more
 {% include 
 image.html 
 lightbox="true" 
-file="/images/codefresh-yaml/approval/pipeline-tag.png" 
-url="/images/codefresh-yaml/approval/pipeline-tag.png"
+file="/images/pipeline/codefresh-yaml/approval/pipeline-tag.png" 
+url="/images/pipeline/codefresh-yaml/approval/pipeline-tag.png"
 alt="Marking a pipeline with tags" 
 caption="Marking a pipeline with tags"
 max-width="40%"
@@ -119,8 +119,8 @@ Once you have tagged your pipelines you can create one or more access rules that
 {% include 
 image.html 
 lightbox="true" 
-file="/images/codefresh-yaml/approval/approval-rule.png" 
-url="/images/codefresh-yaml/approval/approval-rule.png"
+file="/images/pipeline/codefresh-yaml/approval/approval-rule.png" 
+url="/images/pipeline/codefresh-yaml/approval/approval-rule.png"
 alt="Rules for approvals" 
 caption="Rules for approvals"
 max-width="80%"
@@ -280,8 +280,8 @@ Here is the pipeline state after a rejection:
 {% include 
 image.html 
 lightbox="true" 
-file="/images/codefresh-yaml/approval/pipeline-rejected.png" 
-url="/images/codefresh-yaml/approval/pipeline-rejected.png"
+file="/images/pipeline/codefresh-yaml/approval/pipeline-rejected.png" 
+url="/images/pipeline/codefresh-yaml/approval/pipeline-rejected.png"
 alt="Rejecting a pipeline" 
 caption="Rejecting a pipeline"
 max-width="80%"
@@ -315,8 +315,8 @@ via a Slack channel
 {% include 
 image.html 
 lightbox="true" 
-file="/images/codefresh-yaml/approval/slack-approval.png" 
-url="/images/codefresh-yaml/approval/slack-approval.png"
+file="/images/pipeline/codefresh-yaml/approval/slack-approval.png" 
+url="/images/pipeline/codefresh-yaml/approval/slack-approval.png"
 alt="Approval step in a slack channel" 
 caption="Approval step in a slack channel"
 max-width="80%"
@@ -327,8 +327,8 @@ To enable this behavior, you need to activate it in the Slack settings page:
 {% include 
 image.html 
 lightbox="true" 
-file="/images/codefresh-yaml/approval/slack-settings.png" 
-url="/images/codefresh-yaml/approval/slack-settings.png"
+file="/images/pipeline/codefresh-yaml/approval/slack-settings.png" 
+url="/images/pipeline/codefresh-yaml/approval/slack-settings.png"
 alt="Slack settings" 
 caption="Slack settings"
 max-width="50%"
diff --git a/_docs/pipelines/triggers.md b/_docs/pipelines/triggers.md
@@ -1,5 +1,5 @@
 ---
-title: "Triggers in CI pipelines"
+title: "Triggers in pipelines"
 description: "Choose when your pipelines should run"
 group: pipelines
 redirect_from:
diff --git a/_docs/pipelines/variables.md b/_docs/pipelines/variables.md
@@ -1,5 +1,5 @@
 ---
-title: "Variables in CI pipelines"
+title: "Variables in pipelines"
 description: ""
 group: pipelines
 redirect_from:
diff --git a/images/pipeline/codefresh-yaml/docker-image-metadata/annotations-image-table.png b/images/pipeline/codefresh-yaml/docker-image-metadata/annotations-image-table.png
