Content qa (#1247)

* Updates after review

* Updates

* Update gitops-apps-dashboard.md

* Update installation-options.md

* Update monitor-applications.md

* Update monitor-applications.md

* Added conditions for user tokens

* Update manage-pats.md

* Add symlink to values validation

* Update gitops-runtime.md

Removed hosted section

* Update gitops-runtime.md

* Update ingress arch diagram

* Update gitops.md

* Update paths for inline images with conditions

* Updates

* Fix endif tags

* Updates after self-review

* Updates

* Update monitor-applications.md

* Update monitor-applications.md

Author: NimRegev

_data/argohub-nav.yml

@@ -208,9 +208,9 @@
 - title: Products
   url: "/products"
   pages:
-    - title: About Products
+    - title: About products
       url: "/about-products"
-    - title: Create Products
+    - title: Create products
       url: "/create-product"
     - title: Configure Product Settings
       url: "/configure-product-settings"
@@ -220,7 +220,7 @@
       url: "/promotion-version-properties"
     - title: Selecting Promotion Flows
       url: "/promotion-flow-triggers"
-    - title: Tracking Releases for Products
+    - title: Tracking Releases for products
       url: "/releases-in-products"
 
 - title: Applications

_docs/administration/single-sign-on/oidc/oidc-okta.md

@@ -136,7 +136,7 @@ max-width="60%"
 ### How to 
 
 1. In the Codefresh UI, from the toolbar click the **Settings** icon.
-1. In the sidebar, from Access & Collaboration, select [Single Sign-On](https://g.codefresh.io/2.0/account-settings/single-sign-on){:target="\_blank"}.
+1. In the sidebar, from Access & Collaboration, select **Single Sign-On**.
 1. Select **+ Add Single Sign-On**, select **Okta** and then click **Next**.
 
 {% include image.html 
@@ -167,7 +167,7 @@ max-width="30%"
     Though you can assign an Okta application to both groups and individual users, Codefresh _only syncs users who are part of teams_.<br>   
     New users in Okta, _not_ assigned to a team, are **NOT** synced with Codefresh. You should first assign the user to a team for the sync to work.
 1. Optional. To also remove individual users who have been deactivated in Okta from their Codefresh accounts during sync, select **Remove deactivated users during sync**.  
-  When selected, deactivated users are removed from the current account, _and_ from all the accounts defined in **Additional accounts to sync**, if any. Their names are removed from both the Users list and from the Teams to which they belong in [Users and Teams](https://g.codefresh.io/account-admin/collaborators/users){:target="\_blank"}).  
+  When selected, deactivated users are removed from the current account, _and_ from all the accounts defined in **Additional accounts to sync**, if any. Their names are removed from both the Users list and from the Teams to which they belong in Users and Teams.  
   If not selected, the deactivated users are automatically removed from the Team or Teams to which they belong, but still displayed in the Users list.
 1. Select **+Add**.  
   Codefresh automatically generates the **Client Name** to which to identify the SSO configuration.

_docs/administration/user-self-management.md

@@ -4,13 +4,9 @@ description: "Learn how to manage personal settings"
 group: administration
 toc: true
 ---
-{% if page.collection != site.gitops_collection %}
-You can change your email notifications and API keys through [settings]({{site.baseurl}}/docs/administration/user-self-management/user-settings/).
 
-For GitOps integrations you can also manage [your own Git tokens]({{site.baseurl}}/docs/administration/user-self-management/manage-pats/).
-{% endif %}
+As a user, you can change your email notifications and API keys through [settings]({{site.baseurl}}/docs/administration/user-self-management/user-settings/).
+
+You can also manage [your own Git tokens]({{site.baseurl}}/docs/administration/user-self-management/manage-pats/).
 
-{% if page.collection == site.gitops_collection %}
-For GitOps integrations you can also manage [your own Git tokens]({{site.baseurl}}/docs/administration/user-self-management/manage-pats/).
-{% endif %}
 

_docs/deployments/gitops/application-configuration-settings.md

@@ -156,5 +156,4 @@ For example applications, go to the [Argo CD example applications repo](https://
 [Promotions]({{site.baseurl}}/docs/promotions/promotions-overview/)  
 [Manage products and applications in environments]({{site.baseurl}}/docs/environments/manage-apps-in-environments/)  
 [Product Dashboard]({{site.baseurl}}/docs/dashboards/gitops-products/)  
-[Home dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard/)  
 {% if page.collection != site.gitops_collection %}[DORA metrics]({{site.baseurl}}/docs/dashboards/dora-metrics/){% endif %}  

_docs/deployments/gitops/create-application.md

@@ -133,8 +133,7 @@ spec:
 ## Related articles
 [Monitoring Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/monitor-applications/)  
 [Managing Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/manage-application/)  
+[Trigger promotions for applications]({{site.baseurl}}/docs/promotions/trigger-promotions/)  
 [Environments]({{site.baseurl}}/docs/environments/environments-overview/)      
 [Products]({{site.baseurl}}/docs/products/about-products/)  
-[Trigger promotions for applications]({{site.baseurl}}/docs/promotions/trigger-promotions/)  
-[Home dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard/)  
 {% if page.collection != site.gitops_collection %}[DORA metrics]({{site.baseurl}}/docs/dashboards/dora-metrics/){% endif %}  

_docs/deployments/gitops/gitops-app-groups.md

@@ -97,7 +97,7 @@ max-width="60%"
 
 You can: 
 * Filter by one or more applications to find the Groups they belong to.
-* Star one or more Application Groups as favorites for single-click access to them.{::nomarkdown}<br>Click <img src="../../../../images/icons/icon-mark-favorite.png?display=inline-block"> to star a Group, and click <img src="../../../../images/icons/icon-fav-starred.png?display=inline-block"> to view starred Groups.{:}.
+* Star one or more Application Groups as favorites for single-click access to them.{::nomarkdown}<br>Click {% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/icon-mark-favorite.png?display=inline-block">{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/icon-mark-favorite.png?display=inline-block">{% endif %} to star a Group, and click {% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/icon-fav-starred.png?display=inline-block">{% endif %} {% if page.collection == site.gitops_collection %}<img src="../../../../images/icons/icon-fav-starred.png?display=inline-block">{% endif %} to view starred Groups.{:/}.
 * Select a Group to view the Timelines of the applications in it. 
 * Navigate to the Card views of its applications by clicking Applications. 
 

_docs/deployments/gitops/manage-application.md

@@ -65,7 +65,7 @@ There are two aspects to managing Argo CD applications in Codefresh GitOps:
   To delete specific resources within an application, see [Delete application resources]({{site.baseurl}}/docs/deployments/gitops/monitor-applications/#delete-application-resources).
 
 
-## GitOps environments & Argo CD applications
+## Environments & Argo CD applications
 Tracking and managing deployments at scale requires clear visibility into applications at every stage. Codefresh GitOps provides this visibility through environments.  
 When you define an environment by specifying one or more cluster-namespace pairs, Codefresh automatically detects and displays the applications deployed to those locations.
 
@@ -798,7 +798,6 @@ metadata:
 [GitOps Apps dashboard]({{site.baseurl}}/docs/dashboards/gitops-apps-dashboard/)    
 [Environments dashboard]({{site.baseurl}}/docs/dashboards/gitops-environments/)    
 [Products dashboard]({{site.baseurl}}/docs/dashboards/gitops-products/)   
-[Home dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard/)  
 {% if page.collection != site.gitops_collection %}[DORA metrics]({{site.baseurl}}/docs/dashboards/dora-metrics/){% endif %}  
 
 

_docs/deployments/gitops/monitor-applications.md

@@ -355,12 +355,12 @@ The table describes the possible health statuses for an application resource in
 {: .table .table-bordered .table-hover}
 |  Health icon    | Health status | Description  | 
 | --------------  | ------------| ------------------|  
-| {::nomarkdown}<img src="../../../../images/icons/current-state-healthy.png" display=inline-block">{:/}       | **Healthy**     | Resource is functioning as required.  | 
-| {::nomarkdown}<img src="../../../../images/icons/current-state-progressing.png" display=inline-block">{:/}   | **Progressing** | Resource is not healthy but can become healthy before the timeout occurs. | 
-| {::nomarkdown}<img src="../../../../images/icons/current-state-suspended.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-missing.png" display=inline-block">{:/}        | **Missing**     | Resource is not present on the cluster.  |                        
-| {::nomarkdown}<img src="../../../../images/icons/current-state-degraded.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-unknown.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}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/current-state-healthy.png" display=inline-block">{% endif %}{:/} {% if page.collection == site.gitops_collection %}<img src="../../../images/icons/current-state-healthy.png" display=inline-block">{% endif %}{:/}      | **Healthy**     | Resource is functioning as required.  | 
+| {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/current-state-progressing.png" display=inline-block">{:/} {% endif %} {% if page.collection == site.gitops_collection %}<img src="../../../images/icons/current-state-progressing.png" display=inline-block">{:/} {% endif %}   | **Progressing** | Resource is not healthy but can become healthy before the timeout occurs. | 
+| {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/current-state-suspended.png" display=inline-block">{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/current-state-suspended.png" display=inline-block">{% endif %}{:/}     |  **Suspended**   | Resource is not functioning, and is either suspended or paused. For example, Cron job or a canary rollout.|
+|{::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/current-state-missing.png" display=inline-block">{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/current-state-missing.png" display=inline-block">{% endif %}{:/}        | **Missing**     | Resource is not present on the cluster.  |                        
+| {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/current-state-degraded.png" display=inline-block/>{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/current-state-degraded.png" display=inline-block/>{% endif %}{:/}      | **Degraded**    | Resource is not healthy, or a timeout occurred before it could reach a healthy status. |
+| {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/current-state-unknown.png" display=inline-block/>{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/current-state-unknown.png" display=inline-block/>{% endif %}{:/}      | **Unknown**   | Resource does not have a health status, or the health status is not tracked in Argo CD. For example, `ConfigMaps` resource types.   |
 
 
 See also [Argo CD's set of health checks](https://argo-cd.readthedocs.io/en/stable/operator-manual/health/){:target="\_blank"}.
@@ -377,9 +377,9 @@ The table describes the possible sync states for an application resource in the
 {: .table .table-bordered .table-hover}
 | Sync icon      | Sync state   |Description  |  
 | -------------- | ----------    | ----------     |  
-| {::nomarkdown}<img src="../../../../images/icons/current-state-synced.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-syncing.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-out-of-sync.png" display=inline-block">{:/}| **Out-of-Sync**  | The live state is not identical to the desired state.<br>To sync a resource, select the **Sync** option from the resource's context menu in Tree view.  |  
+| {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/current-state-synced.png" display=inline-block">{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/current-state-synced.png" display=inline-block">{% endif %}{:/} | **Synced**  | The live state of the resource on the cluster is identical to the desired state in Git.|                            
+| {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/current-state-syncing.png" display=inline-block/>{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/current-state-syncing.png" display=inline-block/>{% endif %}{:/}| **Syncing**  | The live state of the resource was not identical to the desired state, and is currently being synced. |  
+| {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/current-state-out-of-sync.png" display=inline-block">{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/current-state-out-of-sync.png" display=inline-block">{% endif %}{:/}| **Out-of-Sync**  | The live state is not identical to the desired state.<br>To sync a resource, select the **Sync** option from the resource's context menu in Tree view.  |  
 | No icon | **Unknown**      | The sync status could not be determined.  |  
 
 
@@ -426,7 +426,7 @@ max-width="50%"
 
 
 ### Tree view: Access external links
-Resources with annotations for external links, display {::nomarkdown}<img src="../../../../images/icons/external-link-resources.png" display=inline-block">{:/} below their context menu. Ingress resources automatically display external links. Clicking the icon lists available links.  
+Resources with annotations for external links, display {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/external-link-resources.png" display=inline-block">{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/external-link-resources.png" display=inline-block">{% endif %}{:/} below their context menu. Ingress resources automatically display external links. Clicking the icon lists available links.  
 For more details on this feature, see [Argo CD's documentation on Adding external URLs](https://argo-cd.readthedocs.io/en/stable/user-guide/external-url/){:target="\_blank"}.
 
 >**NOTE**  
@@ -449,7 +449,7 @@ caption="External links for deployment resource in Current State Tree view"
 max-width="50%"
 %}
 
- Clicking {::nomarkdown}<img src="../../../../images/icons/external-link-resources.png" display=inline-block">{:/} displays the links configured. 
+ Clicking {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/external-link-resources.png" display=inline-block">{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/external-link-resources.png" display=inline-block">{% endif %}{:/} displays the links configured. 
 
 
 
@@ -631,10 +631,10 @@ The table lists the controls in the Rollout Player to manage an ongoing rollout.
 {: .table .table-bordered .table-hover}
 |Rollback player icon | Option   | Description |  
 | --------------  | ------------| 
-| {::nomarkdown}<img src="../../../../images/icons/rollout-rollback.png" display=inline-block"> {:/}  | **Rollback**  | Rollback rollout to the selec.  | 
-| {::nomarkdown}<img src="../../../../images/icons/rollout-resume.png" display=inline-block"> {:/}    |**Resume**     | Resume a step that has been paused indefinitely. | 
-| {::nomarkdown}<img src="../../../../images/icons/rollout-skip-step.png" display=inline-block"> {:/} | **Skip step** | Skip execution of current step. Such steps are marked as Skipped in the rollout visualization. | 
-| {::nomarkdown}<img src="../../../../images/icons/rollout-promote-full.png" display=inline-block"> {:/}| **Promote full rollout**    | Skip remaining pause, traffic routing, and analysis steps, and deploy the current release. |                        
+| {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/rollout-rollback.png" display=inline-block">{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/rollout-rollback.png" display=inline-block">{% endif %}  {:/}  | **Rollback**  | Rollback rollout to the selec.  | 
+| {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/rollout-resume.png" display=inline-block">{% endif %} {% if page.collection == site.gitops_collection %}<img src="../../../images/icons/rollout-resume.png" display=inline-block">{% endif %}{:/}    |**Resume**     | Resume a step that has been paused indefinitely. | 
+| {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/rollout-skip-step.png" display=inline-block">{% endif %} {% if page.collection == site.gitops_collection %}<img src="../../../images/icons/rollout-skip-step.png" display=inline-block">{% endif %}{:/} | **Skip step** | Skip execution of current step. Such steps are marked as Skipped in the rollout visualization. | 
+| {::nomarkdown}{% if page.collection != site.gitops_collection %}<img src="../../../../images/icons/rollout-promote-full.png" display=inline-block">{% endif %}{% if page.collection == site.gitops_collection %}<img src="../../../images/icons/rollout-promote-full.png" display=inline-block">{% endif %} {:/}| **Promote full rollout**    | Skip remaining pause, traffic routing, and analysis steps, and deploy the current release. |                        
 
 
 
@@ -695,7 +695,6 @@ max-width="50%"
 [Troubleshooting Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/troubleshooting-gitops-apps/)  
 [Environments dashboard]({{site.baseurl}}/docs/dashboards/gitops-environments/)    
 [Products dashboard]({{site.baseurl}}/docs/dashboards/gitops-products/)  
-[Home dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard/)  
 {% if page.collection != site.gitops_collection %}[DORA metrics]({{site.baseurl}}/docs/dashboards/dora-metrics/){% endif %}  
 
 

_docs/environments/manage-apps-in-environments.md

@@ -19,7 +19,7 @@ Use the Environments dashboard to:
 ## Filter applications in environments by health status
 Quickly filter applications within an Environment by health status. For health status descriptions, see [Health status for application resources]({{site.baseurl}}/docs/deployments/gitops/monitor-applications/#health-status-for-application-resources).
 
-1. In the Codefresh UI, from the sidebar, select [**Environments**](https://g.codefresh.io/2.0/environments?view=compact){:target="\_blank"}.
+1. In the Codefresh UI, from the sidebar, select **Environments**.
 1. For any Environment, click the Health status or statuses by which to filter.  
   The Environment displays those applications that match the selected status. 
 
@@ -38,7 +38,7 @@ Quickly filter applications within an Environment by health status. For health s
 Promote a product or application from the Environments dashboard using one of two methods:
 * **Drag-and-drop promotion**  
   Manually move a product or application from one environment to another, and define the Promotion Settings. Use this method to quickly test changes, such as promoting an application from development to testing.
-* **Promote action**
+* **Promote action**  
   Instead of drag-and-drop, select the target environment to promote to, or trigger a predefined Promotion Flow configured with promotion settings, including the action, and Pre-Action and Post-Action Workflows. This method is best for structured promotions that follow defined policies.