Content qa (codefresh-io#1238)

* Updates after review * Updates * Update gitops-apps-dashboard.md * Update installation-options.md
NOUIY · pull · Feb 10, 2025 · Feb 10, 2025 · Feb 10, 2025 · Feb 11, 2025
commit 1bf478aecc5c9bd10b35b54913469de948e909dd
diff --git a/_docs/dashboards/gitops-apps-dashboard.md b/_docs/dashboards/gitops-apps-dashboard.md
@@ -116,14 +116,14 @@ Here's a description of the information and actions in the GitOps Apps dashboard
 {: .table .table-bordered .table-hover}
 | Item                     | Description            |  
 | --------------         | --------------           |  
-|**Application filters**       | Filter by a range of attributes to customize what you see in the dashboard. {::nomarkdown}  <ul><li>Application health<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 <a href="https://codefresh.io/docs/docs/deployments/gitops/monitor-applications/#health-status-for-application-resources">Health status</a> in this article, and Argo CD's 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/docs/docs/installation/gitops/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 to filter them later.{::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>{:/} {% if page.collection != site.gitops_collection %}TIP: You can filter starred (favorite) applications also in the [DORA metrics dashboard]({{site.baseurl}}/docs/dashboards/dora-metrics/#metrics-for-favorite-applications).{% endif %}  |
-|**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 [Monitor deployments for selected Argo CD application](#monitoring-deployments-for-selected-argo-cd-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-argo-cd-application).{::nomarkdown}<li>Edit<br>Modify application definitions.</li>{:/}See [Edit application definitions]({{site.baseurl}}/docs/deployments/gitops/manage-application/#edit-argo-cd-application-definitions).{::nomarkdown}<li>Refresh and Hard Refresh: Always available in the application's toolbar. <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>See <a href="https://codefresh.io/docs/docs/deployments/gitops/manage-application/#refreshhard-refresh-argo-cd-applications/">Refresh/hard refresh GitOps applications</a>.{:/} |
+|**Application filters**       | Filter by a range of attributes to customize what you see in the dashboard. {::nomarkdown}  <ul><li>Application health<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 <a href="https://codefresh.io/docs/docs/deployments/gitops/monitor-applications/#health-status-for-application-resources">Health status</a>, and Argo CD's 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/docs/docs/installation/gitops/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 to filter them later.{::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>{:/} {% if page.collection != site.gitops_collection %}TIP: You can filter starred (favorite) applications also in the [DORA metrics dashboard]({{site.baseurl}}/docs/dashboards/dora-metrics/#metrics-for-favorite-applications).{% endif %}  |
+|**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 [Monitor deployments for selected Argo CD application]({{site.baseurl}}/docs/deployments/gitops/monitor-applications/#monitoring-application-deployments).{::nomarkdown}<li>Synchronize/Sync: Manually synchronize the application.</li>{:/}See [Manually sync applications]({{site.baseurl}}/docs/deployments/gitops/manage-application/#manually-sync-an-argo-cd-application).{::nomarkdown}<li>Edit: Modify application definitions.</li>{:/}See [Edit application definitions]({{site.baseurl}}/docs/deployments/gitops/manage-application/#edit-argo-cd-application-definitions).{::nomarkdown}<li>Refresh and Hard Refresh: Always available in the application's toolbar. <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>{:/}See [Refresh/hard refresh GitOps applications]({{site.baseurl}}/docs/deployments/gitops/manage-application/#refreshhard-refresh-argo-cd-applications). |
 
 ## Related articles
 [Monitoring Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/monitor-applications/)  
 [Managing Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/manage-application/)  
 [Environments dashboard]({{site.baseurl}}/docs/dashboards/gitops-environments/)    
 [Products dashboard]({{site.baseurl}}/docs/dashboards/gitops-products/)  
-[Home Dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard/)  
+[Home dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard/)  
 {% if page.collection != site.gitops_collection %}[DORA metrics]({{site.baseurl}}/docs/dashboards/dora-metrics/){% endif %}  
diff --git a/_docs/dashboards/gitops-environments.md b/_docs/dashboards/gitops-environments.md
@@ -9,11 +9,9 @@ toc: true
 ## Environments dashboard
 The **Environments** dashboard introduces a new dimension to the developer and deployment experience with Argo CD applications in Codefresh.
 
-Within Codefresh's suite of dashboards, such as the GitOps Overview and GitOps Apps, you gain valuable insights into application deployments and configurations. These views focus on individual applications, lacking the broader context of their interconnections, if any.
+The Environments dashboard provides a comprehensive view of applications across their software development and deployment lifecycles in Codefresh. Unlike the GitOps Overview and GitOps Apps dashboards, which focus on individual applications, the Environments dashboard highlights their relationships within products and promotions.
 
-The Environments dashboard fills this gap by providing a holistic perspective on applications based on their software development and deployment lifecycles. It offers a centralized view of products and their applications as they progress through various promotions, placing them within the broader context of their development journey.
-
-The Environments dashboard in Codefresh gives you a real-time view of your applications across all environments. It provides insights into deployment status, promotions, and version history—helping teams track changes and make informed decisions. With built-in filtering and detailed environment data, you can quickly assess the state of your applications and streamline troubleshooting.
+It offers real-time insights into deployment status, promotions, and version history, helping teams track changes and make informed decisions. With built-in filtering and detailed environment data, you can quickly assess application health and streamline troubleshooting.
 
 
 {% include 

diff --git a/_docs/dashboards/home-dashboard.md b/_docs/dashboards/home-dashboard.md
@@ -375,11 +375,12 @@ You can then filter by the specific pipeline or pipelines and analyze success ra
 
 ## Related articles
 [Environments]({{site.baseurl}}/docs/dashboards/gitops-environments/)  
-{% if page.collection != site.gitops_collection %}[DORA metrics]({{site.baseurl}}/docs/dashboards/dora-metrics/){% endif %}  
 [Monitoring applications]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/)  
+[Images]({{site.baseurl}}/docs/dashboards/images/)  
 {% if page.collection != site.gitops_collection %}
 [Monitoring pipelines]({{site.baseurl}}/docs/pipelines/monitoring-pipelines/)  
+[DORA metrics]({{site.baseurl}}/docs/dashboards/dora-metrics/)  
 {% endif %}  
-[Images]({{site.baseurl}}/docs/dashboards/images/)  
+
 
 
diff --git a/_docs/gitops-quick-start/create-app-ui.md b/_docs/gitops-quick-start/create-app-ui.md
@@ -18,7 +18,7 @@ We'll do the following:
 * Create a product for the applications
 * Explore the Product Dashboard
 
-For detailed information, see [About Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/create-application/).
+For detailed information, see [Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/about-apps/).
 
 
 ## Products in GitOps
@@ -351,7 +351,7 @@ The Product Dashboard provides a centralized view of your product's applications
 * **Release versions**: Quickly identify which version of an application is deployed in each environment to maintain consistency or troubleshoot issues. For detailed information, see [Configuring app version for promotions]({{site.baseurl}}/docs/products/promotion-version-properties/#configuring-versions-for-promoted-applications).
 * **Dependency insights**: Compare dependency versions across environments to detect inconsistencies or verify production readiness.
 * **Integrated application insights**: Use Git commit history, Kubernetes data, and feature mappings to evaluate changes, troubleshoot, and plan promotions.  
-  Requirement: Integrate CI platforms/tools  
+
   For the Git and Features tabs to work seamlessly, ensure your CI/CD systems are integrated.  
   If you have CI platforms/tools already in place, be it Codefresh pipelines, GitHub Actions, or Jenkins, you can integrate them with Codefresh GitOps. The same applies to issue-tracking tools like Jira.  
   For setup instructions, see [Image enrichments with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/).

diff --git a/_docs/gitops-quick-start/create-codefresh-account.md b/_docs/gitops-quick-start/create-codefresh-account.md
@@ -23,10 +23,11 @@ Codefresh currently supports the following IdPs:
 
 If your preferred IdP is not listed, please [contact us](https://codefresh.io/contact-us/){:target="\_blank"} with the details.
 
-
+{% if page.collection != site.gitops_collection %}
 >**NOTE**     
 For Git repositories, the login method is less important, as you can access Git repositories through [Git integrations]({{site.baseurl}}/docs/integrations/git-providers/), regardless of your sign-up process. <br><br>
 If you have multiple sign-up methods, as long as you use the same email address in all the sign-ups, Codefresh automatically redirects you to the account dashboard.
+{% endif %}
 
 ## Create Codefresh account
 1. Go to the [Codefresh Sign Up page](https://g.codefresh.io/signup).  <!---need to change the URL and the screenshot-->
@@ -101,7 +102,7 @@ Congratulations! Your new Codefresh account is now ready and you are directed to
 ## What's next
 You are now ready to install the GitOps Runtime, the foundation for GitOps operations. 
 
-[Quick start: Installing the GitOps Runtime]({{site.baseurl}}/docs/gitops-quick-start/quick-start-install-runtime/)
+[Quick start: Installing a GitOps Runtime]({{site.baseurl}}/docs/gitops-quick-start/quick-start-install-runtime/)
 
 
 

diff --git a/_docs/gitops-quick-start/dependency-multi-env-promotion.md b/_docs/gitops-quick-start/dependency-multi-env-promotion.md
@@ -185,8 +185,8 @@ These foundational steps empower you to manage complex promotions confidently an
 
 ## Related articles
 Now that you’ve covered simple and advanced promotion scenarios, learn more on customizing promotion settings for products: 
-* [Configuring version and promotable properties for Products]({{site.baseurl}}/docs/products/promotion-version-properties/)  
-* [Configuring Promotion Flows and triggers for Products]({{site.baseurl}}/docs/products/promotion-flow-triggers/)   
+* [Configuring version and promotable properties for products]({{site.baseurl}}/docs/products/promotion-version-properties/)  
+* [Selecting Promotion Flows and triggers for products]({{site.baseurl}}/docs/products/promotion-flow-triggers/)   
 
 
 

diff --git a/_docs/gitops-quick-start/multi-env-sequential-flow.md b/_docs/gitops-quick-start/multi-env-sequential-flow.md
@@ -99,7 +99,7 @@ max-width="60%"
 
 {:start="6"}
 1. Select the target environments in the promotion sequence to which to promote changes. For example, `qa` and `prod`.
-    1. Mouse over the right of the environment node to which to add the new environment (`dev` for example), and click {::nomarkdown}<img src="../../../../images/icons/plus-icon.png" display=inline-block>{:/}.
+    1. Mouse over the right of the environment node to which to add the new environment (`dev` for example), and click {::nomarkdown}<img src="../../../images/icons/plus-icon.png" display=inline-block>{:/}.
     1. From the list, select the first target environment in the flow, `qa` for this quick start.
     1. Repeat the action on the newly added environment node (for example, `qa`) to add the next target environment. 
       For the quick start, we'll add `prod` as the final target environment in the flow. 

diff --git a/_docs/gitops-quick-start/quick-start-configure-runtime.md b/_docs/gitops-quick-start/quick-start-configure-runtime.md
@@ -15,7 +15,7 @@ Configure the Runtime immediately after installation using the Configuration and
 
 Configuration includes:
 * [Configuring Git credentials](#configure-git-credentials-for-runtime)
-* [Configuring the Runtime as an Argo CD Application](#configure-runtime-as-argo-application)
+* [Configuring the Runtime as an Argo CD Application](#configure-runtime-as-argo-cd-application)
 * [Adding a Git source](#add-git-source-to-runtime)
 
 For detailed information, see [Configuring the GitOps Runtime]({{site.baseurl}}/docs/installation/gitops/runtime-configuration/).
@@ -57,6 +57,6 @@ Leave all other settings as is.
 ## What's next
 Now that the GitOps Runtime is installed and configured, you are ready to create applications.
 
-[Quick start: Creating Products and applications]({{site.baseurl}}/docs/gitops-quick-start/create-app-ui/)
+[Quick start: Creating products and applications]({{site.baseurl}}/docs/gitops-quick-start/create-app-ui/)
 
 
diff --git a/_docs/gitops-quick-start/quick-start-gitops-environments.md b/_docs/gitops-quick-start/quick-start-gitops-environments.md
@@ -1,5 +1,5 @@
 ---
-title: "Quick start: Creating Environments"
+title: "Quick start: Creating environments"
 description: "Explore how environments empower application promotion and deployment"
 group: gitops-quick-start
 toc: true
@@ -38,7 +38,7 @@ Environments help you:
 * **Mirror your SDLC**: Align applications with their development stages, providing clarity and structure.
 * **Simplify promotions**: Easily move applications through stages, ensuring consistency.
 
-For detailed information, see [Environments]({{site.baseurl}}/docs/dashboards/gitops-environments/).
+For detailed information, see [Environments]({{site.baseurl}}/docs/environments/environments-overview/).
 
 
 ## Requirements

diff --git a/_docs/gitops-quick-start/quick-start-install-runtime.md b/_docs/gitops-quick-start/quick-start-install-runtime.md
@@ -26,10 +26,10 @@ Choose from two installation options based on your existing Argo CD setup:
 
 * **Install with a new Argo CD instance**
   If Argo CD is not installed, Codefresh can deploy and configure it along with the GitOps Runtime.  
-  .
+
 
 The key difference is whether Argo CD instance is either external to the Runtime or installed as part of it.
-For an architectural overview, see [Runtime installation modes and architecture](#runtime-installation-modes-and-architecture). 
+For an architectural overview, see [Runtime installation modes and architecture]({{site.baseurl}}/docs/gitops-runtimes/runtime-architecture/#runtime-installation-modes-and-architecture). 
 
 
 

diff --git a/_docs/gitops-quick-start/quick-start-promotion-workflow.md b/_docs/gitops-quick-start/quick-start-promotion-workflow.md
@@ -1,5 +1,5 @@
 ---
-title: "Quick start: Create Promotion Workflows"
+title: "Quick start: Creating Promotion Workflows"
 description: "Create a workflow template to use as pre- or post-action"
 group: gitops-quick-start
 toc: true
@@ -9,6 +9,7 @@ toc: true
 This quick start will guide you through creating a Promotion Workflow in Codefresh.  
 
 Promotion Workflows are Argo Workflow Templates that automate tasks such as notifications, validations, and additional deployments before or after a promotion. They can be used in Promotion Flows to automate tasks before or after promotion.
+
 For detailed information, see [Configure Promotion Workflows]({{site.baseurl}}/docs/promotions/promotion-workflow/).
 
 This quick start includes examples of two Promotion Workflows: