Renamed RHTAP to RHADS (redhat-developer#1233)

RHIDP-7599: Update Template editor (redhat-developer#1218)

* Added content

* Incorporated Lindsey's comments and Jai's comments from test day

* Added Jai's and Shiran's suggestion

Move links in Prerequisites to Additional resources

Move links in Prerequisites to Additional resources

Move links in Prerequisites to Additional resources

Move links in Prerequisites to Additional resources

Move links in Prerequisites to Additional resources

Author: gtrivedi88

artifacts/attributes.adoc

@@ -52,9 +52,9 @@
 :rhbk: RHBK
 :keycloak-version: 26.0
 
-// RHTAP information
-:rhtap-brand-name: Red Hat Trusted Application Pipeline
-:rhtap-very-short: RHTAP
+// RHADS information
+:rhads-brand-name: Red Hat Advanced Developer Suite - secure supply chain
+:rhads-very-short: RHADS - ssc
 
 // TAS information
 :rhtas-brand-name: Red Hat Trusted Artifact Signer

modules/about/con-integrations-in-rhdh.adoc

@@ -12,17 +12,17 @@
 * Access to advanced OpenShift capabilities such as service mesh, serverless functions, GitOps, and distributed tracing.
 * Pipelines and GitOps plugins for streamlined cloud-native workflows.
 
-== Integration with {rhtap-brand-name}
-{rhtap-brand-name} ({rhtap-very-short}) enhances {product} by providing secure CI/CD capabilities that integrate security measures into every stage of the development process.
+== Integration with {rhads-brand-name}
+{rhads-brand-name} ({rhads-very-short}) enhances {product} by providing secure CI/CD capabilities that integrate security measures into every stage of the development process.
 
-While {product} focuses on the inner loop (code, build, and test), {rhtap-very-short} manages the outer loop, automating:
+While {product} focuses on the inner loop (code, build, and test), {rhads-very-short} manages the outer loop, automating:
 
 * Code scanning
 * Image building
 * Vulnerability detection
 * Deployment
 
-{rhtap-very-short} includes tools like {rhtas-brand-name} ({rhtas-very-short}) for code integrity, {rhtpa-brand-name} ({rhtpa-very-short}) for automated Software build of Materials (SBOM) creation, and {rhacs-brand-name} ({rhacs-very-short}) for vulnerability scanning. 
+{rhads-very-short} includes tools like {rhtas-brand-name} ({rhtas-very-short}) for code integrity, {rhtpa-brand-name} ({rhtpa-very-short}) for automated Software build of Materials (SBOM) creation, and {rhacs-brand-name} ({rhacs-very-short}) for vulnerability scanning. 
 
 == Extending Backstage with {product}
 {product} which is a fully supported, enterprise-grade productized version of upstream Backstage extends the upstream project by adding:

modules/customizing-templates/proc-creating-templates.adoc

@@ -6,7 +6,7 @@
 [id="proc-creating-templates_{context}"]
 = Creating a Software Template by using the Template Editor
 
-You can create a Software Template by using the Template Editor.
+Use the {product} Template Editor to create a Software Template.
 
 Alternately, you can use the Template Editor to do any of the following actions:
 
@@ -20,8 +20,8 @@ Alternately, you can use the Template Editor to do any of the following actions:
 
 To create a Software Template by using the Template Editor templates, complete the following steps:
 
-. In your {product} navigation menu, click *Catalog > Self-service*.
-. Click the overview menu and select *Manage Templates*.
+. In your {product} navigation menu, click *Catalog > Self-service*. Alternatively, to go to *Self-service* page, in your header menu, click the (+) icon.
+. Click the Kebab menu and select *Manage Templates*.
 +
 image::rhdh/template-editor.png[Template Editor]
 +
@@ -37,17 +37,20 @@ image::rhdh/template-editor.png[Template Editor]
 * *Load Template Directory*: Use to load an existing `templates.yaml` file
 ** In your local file manager, navigate to the folder where your `templates.yaml` file is stored and click *Select*.
 * *Create New Template*: Use to create a `templates.yaml` file
-** In your local file manager, navigate to the folder where you want the Template Editor to create a `templates.yaml` file and click *Select*.
+.. In your local file manager, navigate to the folder where you want the Template Editor to create a `templates.yaml` file and click *Select*.
 .. On the *Template Editor* page, select the `templates.yaml` file.
 .. (Optional) You can preview and test your template specifications.
 ... On the *Fill in some steps* tab, enter text into the required fields and click *Next*.
 ... On the *Repository Location* tab, enter text into the required fields and click *Review*.
 ... Modify the YAML definition for the parameters of your template. For more information about these parameters, see <<Creating a Software Template as a YAML file>>.
 ... Review the information for accuracy, then click *Create*.
-.. When the Software Template is created, xref:proc-adding-templates_{context}[import your Software Template in your {product-very-short} instance].
+.. After the Software Template is created, xref:proc-adding-templates_{context}[import your Software Template in your {product-very-short} instance].
 
 .Verification
 
 . Click the *Catalog* tab in the navigation panel.
 . In the *Kind* drop-down menu, select *Template*.
 . Confirm that your template is shown in the list of existing templates.
+
+.Next step
+* xref:proc-adding-templates_{context}[Import your Software Template in your {product-very-short} instance].

modules/installation/proc-deploy-rhdh-instance-eks.adoc

@@ -8,12 +8,12 @@
 .Prerequisites
 
 * A cluster administrator has installed the {product} Operator.
-* You have an {eks-short} cluster with {aws-short} Application Load Balancer (ALB) add-on installed. For more information, see https://docs.aws.amazon.com/eks/latest/userguide/alb-ingress.html[Application load balancing on {eks-brand-name}] and https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html[Installing the AWS Load Balancer Controller add-on].
-* You have configured a domain name for your {product-short} instance. The domain name can be a hosted zone entry on Route 53 or managed outside of AWS. For more information, see https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-configuring.html[Configuring Amazon Route 53 as your DNS service] documentation.
+* You have an {eks-short} cluster with {aws-short} Application Load Balancer (ALB) add-on installed.
+* You have configured a domain name for your {product-short} instance. The domain name can be a hosted zone entry on Route 53 or managed outside of AWS.
 * You have an entry in the {aws-short} Certificate Manager (ACM) for your preferred domain name. Make sure to keep a record of your Certificate ARN.
-* You have subscribed to `registry.redhat.io`. For more information, see https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
-* You have set the context to the {eks-short} cluster in your current `kubeconfig`. For more information, see https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html[Creating or updating a kubeconfig file for an Amazon {eks-short} cluster].
-* You have installed `kubectl`. For more information, see https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html[Installing or updating kubectl].
+* You have subscribed to `registry.redhat.io`.
+* You have set the context to the {eks-short} cluster in your current `kubeconfig`.
+* You have installed `kubectl`.
 
 .Procedure
 
@@ -158,3 +158,13 @@ In the previous template, replace ` <rhdh_dns_name>` with your {product-short} d
 .Verification
 
 Wait until the DNS name is responsive, indicating that your {product-short} instance is ready for use.
+
+[role="_additional-resources"]
+.Additional resources
+
+* link:https://docs.aws.amazon.com/eks/latest/userguide/alb-ingress.html[Application load balancing on {eks-brand-name}]
+* link:https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html[Installing the AWS Load Balancer Controller add-on]
+* link:https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-configuring.html[Configuring Amazon Route 53 as your DNS service documentation]
+* link:https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication]
+* link:https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html[Creating or updating a kubeconfig file for an Amazon {eks-short} cluster]
+* link:https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html[Installing or updating kubectl]

modules/installation/proc-deploy-rhdh-instance-gke.adoc

@@ -4,11 +4,10 @@ You can deploy your {product-short} instance in {gke-short} using the Operator.
 
 .Prerequisites
 * A cluster administrator has installed the {product} Operator.
-* You have subscribed to `registry.redhat.io`. For more information, see https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
-* You have installed `kubectl`. For more information, see https://kubernetes.io/docs/tasks/tools/#kubectl[Install kubetl].
-
+* You have subscribed to `registry.redhat.io`.
+* You have installed `kubectl`.
 * You have configured a domain name for your {product-short} instance.
-* You have reserved a static external Premium IPv4 Global IP address that is not attached to any virtual machine (VM). For more information see https://cloud.google.com/vpc/docs/reserve-static-external-ip-address#reserve_new_static[Reserve a new static external IP address]
+* You have reserved a static external Premium IPv4 Global IP address that is not attached to any virtual machine (VM).
 * You have configured the DNS records for your domain name to point to the IP address that has been reserved.
 +
 [NOTE]
@@ -191,5 +190,19 @@ spec:
 
 // Wait until the DNS name is responsive, indicating that your {product-short} instance is ready for use.
 
+[role="_additional-resources"]
+.Additional resources
+
+* link:https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication]
+* link:https://kubernetes.io/docs/tasks/tools/#kubectl[Installing `kubetl]`
+* link:https://cloud.google.com/vpc/docs/reserve-static-external-ip-address#reserve_new_static[Reserving a new static external IP address]
+
 .Additional information
 For more information on setting up {gke-short} using Ingress with TLS, see https://github.com/GoogleCloudPlatform/gke-networking-recipes/tree/main/ingress/single-cluster/ingress-https[Secure GKE Ingress].
+
+[role="_additional-resources"]
+.Additional resources
+
+* link:https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication]
+* link:https://kubernetes.io/docs/tasks/tools/#kubectl[Installing kubetl]
+* link:https://cloud.google.com/vpc/docs/reserve-static-external-ip-address#reserve_new_static[Reserving a new static external IP address]

modules/installation/proc-enable-signin.adoc

@@ -63,7 +63,6 @@ The {product} supports the following authentication providers:
 .Prerequisites
 
 * You have installed the {product-short}.
-For more information about installation, see xref:{installing-on-ocp-book-url}#assembly-install-rhdh-ocp-helm[{installing-on-ocp-book-title} with the Helm chart].
 
 .Procedure
 
@@ -87,3 +86,8 @@ auth:
 `signInPage: oidc`
 
 . Start your {product-short} application and sign in.
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:{installing-on-ocp-book-url}#assembly-install-rhdh-ocp-helm[{installing-on-ocp-book-title} with the Helm chart]

modules/installation/proc-install-operator.adoc

@@ -14,7 +14,7 @@ Containers are available for the following CPU architectures:
 .Prerequisites
 
 * You are logged in as an administrator on the {ocp-short} web console.
-* You have configured the appropriate roles and permissions within your project to create or access an application. For more information, see the link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/building_applications/index#building-applications-overview[{ocp-brand-name} documentation on Building applications].
+* You have configured the appropriate roles and permissions within your project to create or access an application.
 * You have installed {ocp-brand-name} 4.17 or later.
 
 .Procedure
@@ -81,5 +81,6 @@ If you selected an *Automatic* approval strategy, the upgrade status should reso
 [role="_additional-resources"]
 .Additional resources
 
-* xref:proc-install-rhdh-ocp-operator_{context}[Deploying {product} on {ocp-short} with the Operator]
+* xref:proc-install-rhdh-ocp-operator_{context}[Deploying {product} on {ocp-short} with Operator]
 * link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/operators/index#olm-installing-from-operatorhub-using-web-console_olm-adding-operators-to-a-cluster[Installing from OperatorHub by using the web console]
+* link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/building_applications/index#building-applications-overview[{ocp-brand-name} documentation on Building applications]

modules/installation/proc-install-rhdh-airgapped-partial-k8s-helm.adoc

@@ -5,7 +5,7 @@ In a partially disconnected environment, the cluster cannot access external regi
 
 .Prerequisites
 
-* You have set up your workstation.
+* You have set up your workstation
 ** You have installed Skopeo 1.17 or later
 ** You have installed Yq 4.4 or later
 ** You have installed Helm 3.13 or later

modules/installation/proc-install-rhdh-helm-airgapped-full.adoc

@@ -9,11 +9,11 @@ If your network has access to the registry through a bastion host, you can use t
 ** You have access to the registry.redhat.io.
 ** You have access to the charts.openshift.io Helm chart repository.
 ** You have installed the {openshift-cli} on your workstation.
-** You have installed the oc-mirror {openshift-cli} plugin, for more information see https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[Installing the oc-mirror OpenShift CLI plugin].
+** You have installed the oc-mirror {openshift-cli} plugin.
 ** You have an account in https://developers.redhat.com/[{rhdeveloper-name}] portal.
 * You have set up your intermediary host.
-** Your host has access to the disconnected cluster and to the target mirror registry, for example, the {ocp-brand-name} image registry. For more information about exposing the {ocp-short} image registry, see https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/registry/index#securing-exposing-registry[Exposing the registry].
-** You have installed the oc-mirror {openshift-cli} plugin, for more information see https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[Installing the oc-mirror OpenShift CLI plugin].
+** Your host has access to the disconnected cluster and to the target mirror registry, for example, the {ocp-brand-name} image registry.
+** You have installed the oc-mirror {openshift-cli} plugin.
 ** You have installed {ocp-brand-name} {ocp-version-min} or later.
 ** You have installed the {openshift-cli} on your workstation.
 
@@ -146,4 +146,10 @@ where:
 `<archive_file>` :: Specifies the name of the archive file containing the resources that you want to mirror, for example, `redhat-developer-hub-1.4.1.tgz`.
 
 `<your_namespace>` :: Specifies the namespace that you want to deploy the Helm chart to, for example, `{my-product-namespace}`.
---
+--
+
+[role="_additional-resources"]
+.Additional resources
+
+* link:https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[Installing the oc-mirror OpenShift CLI plugin]
+* link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/registry/index#securing-exposing-registry[Exposing the {ocp-short} image registry]

modules/installation/proc-install-rhdh-helm-airgapped-partial.adoc

@@ -8,10 +8,10 @@ If your network has access to the `registry.redhat.io` registry and the `charts.
 * You have installed {ocp-brand-name} {ocp-version-min} or later.
 * You have access to the `charts.openshift.io` Helm chart repository.
 * You have access to the `registry.redhat.io`.
-* You have access to a mirror registry that can be reached from the disconnected cluster, for example, the {ocp-short} image registry. For more information about exposing the {ocp-short} image registry, see https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/registry/index#securing-exposing-registry[Exposing the registry].
-* You are logged in to your target mirror registry and have permissions to push images to it. For more information, see link:https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-adding-registry-pull-secret_installing-mirroring-disconnected[Configuring credentials that allow images to be mirrored].
+* You have access to a mirror registry that can be reached from the disconnected cluster, for example, the {ocp-short} image registry.
+* You are logged in to your target mirror registry and have permissions to push images to it.
 * You have installed the {openshift-cli} on your workstation.
-* You have installed the oc-mirror {openshift-cli} plugin, for more information see https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[Installing the oc-mirror OpenShift CLI plugin].
+* You have installed the oc-mirror {openshift-cli} plugin.
 * You have an account in https://developers.redhat.com/[{rhdeveloper-name}] portal.
 
 .Procedure
@@ -33,11 +33,11 @@ kind: ImageSetConfiguration
 mirror:
   helm:
     repositories:
-      - name: _<repository_name>_ (1)
-        url: _<repository_url>_ (2)
+      - name: _<repository_name>_ # <1>
+        url: _<repository_url>_ # <2>
         charts:
-          - name: _<chart_name>_ (3)
-            version: "_<rhdh_version>_" (4)
+          - name: _<chart_name>_ # <3>
+            version: "_<rhdh_version>_" # <4>
 ----
 <1> The name of the repository containing the Helm chart that you want to mirror, for example, `openshift-charts`.
 <2> The URL for the repository containing the Helm chart that you want to mirror, for example, `https://charts.openshift.io`.
@@ -122,4 +122,10 @@ where:
 `<archive_file>` :: Specifies the name of the archive file containing the resources that you want to mirror, for example, `redhat-developer-hub-1.4.1.tgz`.
 
 `<your_namespace>` :: Specifies the namespace that you want to deploy the Helm chart to, for example, `{my-product-namespace}`.
---
+--
++
+[role="_additional-resources"]
+.Additional resources
+* link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/registry/index#securing-exposing-registry[Exposing the {ocp-short} image registry]
+* link:https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-adding-registry-pull-secret_installing-mirroring-disconnected[Configuring credentials that allow images to be mirrored]
+* link:https://docs.openshift.com/container-platform/4.17/disconnected/mirroring/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[Installing the oc-mirror OpenShift CLI plugin]