RHIDP-8565 fixed the Vale alert: AsciiDocDITA.RelatedLinks:Content other than links cannot be mapped to DITA related-links. (#1368)

themr0c · web-flow · commit 1bd4f491fb0f · 2025-09-10T14:52:25.000+02:00
diff --git a/assemblies/assembly-install-rhdh-airgapped-environment-ocp-helm.adoc b/assemblies/assembly-install-rhdh-airgapped-environment-ocp-helm.adoc
@@ -3,10 +3,10 @@
 
 You can install {product} in a fully disconnected or partially disconnected environment using the {product} Helm chart.
 
-[role="_additional-resources"]
-.Additional resources
-* For more information about registry authentication, see link:https://access.redhat.com/articles/RegistryAuthentication[{company-name} Container Registry Authentication].
-
 include::modules/installation/proc-install-rhdh-helm-airgapped-full.adoc[leveloffset=+1]
 
 include::modules/installation/proc-install-rhdh-helm-airgapped-partial.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* link:https://access.redhat.com/articles/RegistryAuthentication[{company-name} Container Registry Authentication]
diff --git a/assemblies/assembly-install-rhdh-eks-operator.adoc b/assemblies/assembly-install-rhdh-eks-operator.adoc
@@ -4,7 +4,8 @@
 
 The {product} Operator installation requires the Operator Lifecycle Manager (OLM) framework.
 
+include::modules/installation/proc-rhdh-deploy-eks-operator.adoc[leveloffset=+1]
+
 .Additional resources
-* For information about the OLM, see link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)] documentation.
+* link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)]
 
-include::modules/installation/proc-rhdh-deploy-eks-operator.adoc[leveloffset=+1]
diff --git a/modules/about/con-benefits-of-rhdh.adoc b/modules/about/con-benefits-of-rhdh.adoc
@@ -26,10 +26,12 @@ For organizations::
 == Key features
 
 Centralized Dashboard::
-Provides a single interface for accessing developer tools, CI/CD pipelines, APIs, monitoring tools, and documentation. Integrated with systems like Git, OpenShift, Kubernetes, and JIRA.
+Provides a single interface for accessing developer tools, CI/CD pipelines, APIs, monitoring tools, and documentation.
+Integrated with systems like Git, OpenShift, Kubernetes, and JIRA.
 
 Dynamic Plugins::
-Add, update, or remove plugins dynamically without downtime. Popular plugins like Tekton, GitOps, Nexus Repository, and JFrog Artifactory are supported and verified by Red Hat.
+Add, update, or remove plugins dynamically without downtime.
+Popular plugins like Tekton, GitOps, Nexus Repository, and JFrog Artifactory are supported and verified by Red Hat.
 
 Software Templates::
 Simplify development processes by automating tasks such as repository setup, variable insertion, and production pipeline creation.
@@ -45,4 +47,4 @@ Centralized repositories ensure synchronized updates, improving version control
 
 [role="_additional-resources"]
 .Additional resources
-  * For more information about the different features of {product} and how to extend it, see link:https://developers.redhat.com/rhdh/overview[{product} overview].
+* link:https://developers.redhat.com/rhdh/overview[{product} overview]
diff --git a/modules/configuring-deployment/proc-configuring-deployment-by-using-the-operator.adoc b/modules/configuring-deployment/proc-configuring-deployment-by-using-the-operator.adoc
@@ -1,15 +1,16 @@
 [id="configuring-the-deployment"]
 = Configuring {product} deployment when using the Operator
 
-The {product} Operator exposes a `rhdh.redhat.com/v1alpha3` API Version of its custom resource (CR). This CR exposes a generic `spec.deployment.patch` field, which gives you full control over the {product-short} Deployment resource. This field can be a fragment of the standard `apps.Deployment` Kubernetes object.
+The {product} Operator exposes a `rhdh.redhat.com/v1alpha3` API Version of its custom resource (CR).
+This CR exposes a generic `spec.deployment.patch` field, which gives you full control over the {product-short} Deployment resource.
+This field can be a fragment of the standard `apps.Deployment` Kubernetes object.
 
 .Procedure
-
 . Create a `{product-custom-resource-type}` CR with the following fields:
 
 --
 .Example
-[source, yaml]
+[source,yaml]
 ----
 apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
@@ -26,7 +27,7 @@ spec:
 Add labels to the {product-short} pod.
 +
 .Example adding the label `my=true`
-[source, yaml]
+[source,yaml]
 ----
 apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
@@ -45,10 +46,11 @@ spec:
 `volumes`::
 +
 --
+
 Add an additional volume named `my-volume` and mount it under `/my/path` in the {product-short} application container.
 
 .Example additional volume
-[source, yaml]
+[source,yaml]
 ----
 apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
@@ -73,10 +75,11 @@ spec:
                 name: my-volume
 ----
 
-Replace the default `dynamic-plugins-root` volume with a persistent volume claim (PVC) named `dynamic-plugins-root`. Note the `$patch: replace` directive, otherwise a new volume will be added.
+Replace the default `dynamic-plugins-root` volume with a persistent volume claim (PVC) named `dynamic-plugins-root`.
+Note the `$patch: replace` directive, otherwise a new volume will be added.
 
 .Example `dynamic-plugins-root` volume replacement
-[source, yaml]
+[source,yaml]
 ----
 apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
@@ -94,14 +97,15 @@ spec:
                 persistentVolumeClaim:
                   claimName: dynamic-plugins-root
 ----
+
 --
 
 `cpu` request::
 
 Set the CPU request for the {product-short} application container to 250m.
 +
 .Example CPU request
-[source, yaml]
+[source,yaml]
 ----
 apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
@@ -125,7 +129,7 @@ spec:
 Add a new `my-sidecar` sidecar container into the {product-short} Pod.
 +
 .Example side car container
-[source, yaml]
+[source,yaml]
 ----
 apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
@@ -146,5 +150,4 @@ spec:
 
 [role="_additional-resources"]
 .Additional resources
-
-* To learn more about merging, see link:https://github.com/kubernetes/community/blob/master/contributors/devel/sig-api-machinery/strategic-merge-patch.md#basic-patch-format[Strategic Merge Patch].
+* link:https://github.com/kubernetes/community/blob/master/contributors/devel/sig-api-machinery/strategic-merge-patch.md#basic-patch-format[Strategic Merge Patch]
diff --git a/modules/customizing-the-learning-paths/proc-customizing-the-learning-paths-by-using-hosted-json-files.adoc b/modules/customizing-the-learning-paths/proc-customizing-the-learning-paths-by-using-hosted-json-files.adoc
@@ -4,7 +4,8 @@
 For ease of use and simplicity, you can configure the Learning Paths by using a hosted JSON file.
 
 .Procedure
-. Publish the JSON file containing your Learning Paths data to a web server, such as GitHub or Gitlab. You can find an example at link:https://raw.githubusercontent.com/redhat-developer/rhdh/release-{product-version}/packages/app/public/learning-paths/data.json[].
+. Publish the JSON file containing your Learning Paths data to a web server, such as GitHub or Gitlab.
+You can find an example at link:https://raw.githubusercontent.com/redhat-developer/rhdh/release-{product-version}/packages/app/public/learning-paths/data.json[].
 
 . Configure the {product-short} proxy to access the Learning Paths data from the hosted JSON file, by adding the following to the `{my-app-config-file}` file:
 +
@@ -22,8 +23,7 @@ proxy:
 
 `_<target>_`:: Enter the hosted JSON file base URL, such as `pass:[https://raw.githubusercontent.com]`.
 
-`_<learning_path.json>_`:: Enter the hosted JSON file path without the base URL, such as
-`'/redhat-developer/rhdh/main/packages/app/public/learning-paths/data.json'`
+`_<learning_path.json>_`:: Enter the hosted JSON file path without the base URL, such as `'/redhat-developer/rhdh/main/packages/app/public/learning-paths/data.json'`
 +
 [TIP]
 ====
@@ -46,4 +46,4 @@ proxy:
 ====
 
 .Additional resources
-* xref:customizing-the-home-page[Customizing the Home page in {product}].
+* xref:customizing-the-home-page[Customizing the Home page in {product}]
diff --git a/modules/dynamic-plugins/proc-enabling-argo-cd-rollouts.adoc b/modules/dynamic-plugins/proc-enabling-argo-cd-rollouts.adoc
@@ -2,11 +2,11 @@
 [id="enabling-argo-cd-rollouts_{context}"]
 = Enabling Argo CD Rollouts
 
-The optional Argo CD Rollouts feature enhances Kubernetes by providing advanced deployment strategies, such as blue-green and canary deployments, for your applications. When integrated into the backstage Kubernetes plugin, it allows developers and operations teams to visualize and manage Argo CD Rollouts seamlessly within the {product-custom-resource-type} interface.
+The optional Argo CD Rollouts feature enhances Kubernetes by providing advanced deployment strategies, such as blue-green and canary deployments, for your applications.
+When integrated into the backstage Kubernetes plugin, it allows developers and operations teams to visualize and manage Argo CD Rollouts seamlessly within the {product-custom-resource-type} interface.
 
 .Prerequisites
-
-* The Backstage Kubernetes plugin (`@backstage/plugin-kubernetes`) is installed and configured. 
+* The Backstage Kubernetes plugin (`@backstage/plugin-kubernetes`) is installed and configured.
 
 ** To install and configure Kubernetes plugin in Backstage, see link:https://backstage.io/docs/features/kubernetes/installation/[Installaltion] and link:https://backstage.io/docs/features/kubernetes/configuration/[Configuration] guide.
 
@@ -15,7 +15,6 @@ The optional Argo CD Rollouts feature enhances Kubernetes by providing advanced
 * The Kubernetes cluster has the `argoproj.io` group resources (for example, Rollouts and AnalysisRuns) installed.
 
 .Procedure
-
 . In the `{my-app-config-file}` file in your {product-custom-resource-type} instance, add the following `customResources` component under the `kubernetes` configuration to enable Argo Rollouts and AnalysisRuns:
 
 +
@@ -103,7 +102,8 @@ annotations:
 +
 [NOTE]
 ====
-Ensure you specify the labels declared in `backstage.io/kubernetes-label-selector` on your Kubernetes resources. This annotation overrides entity-based or namespace-based identification annotations, such as `backstage.io/kubernetes-id` and `backstage.io/kubernetes-namespace`.
+Ensure you specify the labels declared in `backstage.io/kubernetes-label-selector` on your Kubernetes resources.
+This annotation overrides entity-based or namespace-based identification annotations, such as `backstage.io/kubernetes-id` and `backstage.io/kubernetes-namespace`.
 ====
 
 . Add label to Kubernetes resources to enable Backstage to find the appropriate Kubernetes resources.
@@ -129,16 +129,17 @@ labels:
 +
 [NOTE]
 ====
-If using the label selector annotation (backstage.io/kubernetes-label-selector), ensure the specified labels are present on the resources. The label selector will override other annotations like kubernetes-id or kubernetes-namespace.
+If using the label selector annotation (backstage.io/kubernetes-label-selector), ensure the specified labels are present on the resources.
+The label selector will override other annotations like kubernetes-id or kubernetes-namespace.
 ====
 
 .Verification
-
 . Push the updated configuration to your GitOps repository to trigger a rollout.
 
 . Open {product} interface and navigate to the entity you configured.
 
-. Select the *CD* tab and then select the *GitOps application*. The side panel opens. 
+. Select the *CD* tab and then select the *GitOps application*.
+The side panel opens.
 
 . In the *Resources* table of the side panel, verify that the following resources are displayed:
 
@@ -155,7 +156,4 @@ If using the label selector annotation (backstage.io/kubernetes-label-selector),
 
 [role="_additional-resources"]
 .Additional resources
-
-* The package path, scope, and name of the {company-name} ArgoCD plugin has changed since 1.2. For more information, see link:{release-notes-book-url}#removed-functionality-rhidp-4293[Breaking Changes] in the _{release-notes-book-title}_.
-
-* For more information on installing dynamic plugins, see link:{installing-and-viewing-plugins-book-url}[{installing-and-viewing-plugins-book-title}].
+* link:{installing-and-viewing-plugins-book-url}[{installing-and-viewing-plugins-book-title}]
diff --git a/modules/dynamic-plugins/proc-using-argo-cd.adoc b/modules/dynamic-plugins/proc-using-argo-cd.adoc
@@ -1,16 +1,15 @@
 = Using the Argo CD plugin
 
-You can use the Argo CD plugin to visualize the Continuous Delivery (CD) workflows in OpenShift GitOps. This plugin provides a visual overview of the application’s status, deployment details, commit message, author of the commit, container image promoted to environment and deployment history.
+You can use the Argo CD plugin to visualize the Continuous Delivery (CD) workflows in OpenShift GitOps.
+This plugin provides a visual overview of the application’s status, deployment details, commit message, author of the commit, container image promoted to environment and deployment history.
 
 .Prerequisites
-
 * You have enabled the Argo CD plugin in {product} {product-very-short}.
 
 .Procedure
-
 . Select the *Catalog* tab and choose the component that you want to use.
 
-. Select the *CD* tab to view insights into deployments managed by Argo CD. 
+. Select the *CD* tab to view insights into deployments managed by Argo CD.
 
 +
 image::rhdh-plugins-reference/argocd.png[CD tab Argo CD]
@@ -22,13 +21,13 @@ image::rhdh-plugins-reference/sidebar.png[Sidebar]
 
 .. Click the link icon (image:rhdh-plugins-reference/link.png[Link icon]) to open the deployment details in Argo CD.
 
-. Select the *Overview* tab and navigate to the Deployment summary section to review the summary of your application's deployment across namespaces. Additionally, select an appropriate Argo CD app to open the deployment details in Argo CD, or select a commit ID from the Revision column to review the changes in GitLab or GitHub.
+. Select the *Overview* tab and navigate to the Deployment summary section to review the summary of your application's deployment across namespaces.
+Additionally, select an appropriate Argo CD app to open the deployment details in Argo CD, or select a commit ID from the Revision column to review the changes in GitLab or GitHub.
 
 +
 image::rhdh-plugins-reference/deployment_summary.png[Deployment summary]
 
 
 [role="_additional-resources"]
 .Additional resources
-
-* For more information on installing dynamic plugins, see link:{installing-and-viewing-plugins-book-url}[{installing-and-viewing-plugins-book-title}].
+* link:{installing-and-viewing-plugins-book-url}[{installing-and-viewing-plugins-book-title}]
