RHIDP-7849 Added existing modules to the _Getting started with RHDH on OCP_ title

themr0c · themr0c · commit a02ea4ca2c4a · 2025-08-06T11:08:20.000+02:00
Fixed existing content to build while reused.

Signed-off-by: Fabrice Flore-Thébault &lt;ffloreth@redhat.com&gt;
diff --git a/modules/authentication/proc-enabling-user-authentication-with-rhbk.adoc b/modules/authentication/proc-enabling-user-authentication-with-rhbk.adoc
@@ -157,7 +157,6 @@ catalog:
         schedule:
           initialDelay: { seconds: 15}
 ----
---
 
 . To set up the {rhbk} authentication provider in your {product-short} custom configuration, edit your custom {product-short} ConfigMap such as `app-config-rhdh`, and add the following lines to the `{my-app-config-file}` content:
 
diff --git a/modules/configuring/proc-configuring-an-rhdh-instance-with-tls-in-kubernetes.adoc b/modules/configuring/proc-configuring-an-rhdh-instance-with-tls-in-kubernetes.adoc
@@ -1,4 +1,4 @@
-[id="proc-configuring-an-rhdh-instance-with-tls-in-kubernetes_{context}"]
+[id="configuring-an-rhdh-instance-with-tls-in-kubernetes"]
 = Configuring an {product-very-short} instance with a TLS connection in Kubernetes
 
 You can configure a {product-very-short} instance with a Transport Layer Security (TLS) connection in a Kubernetes cluster, such as an Azure Red Hat OpenShift (ARO) cluster, any cluster from a supported cloud provider, or your own cluster with proper configuration. Transport Layer Security (TLS) ensures a secure connection for the {product-very-short} instance with other entities, such as third-party applications, or external databases. However, you must use a public Certificate Authority (CA)-signed certificate to configure your Kubernetes cluster.
diff --git a/modules/configuring/proc-provisioning-your-custom-configuration.adoc b/modules/configuring/proc-provisioning-your-custom-configuration.adoc
@@ -55,7 +55,7 @@ backend:
 *** link:{authentication-book-url}[{authentication-book-title}].
 *** link:{authorization-book-url}[{authorization-book-title}].
 *** link:{customizing-book-url}[Customization].
-*** xref:proc-configuring-an-rhdh-instance-with-tls-in-kubernetes_running-behind-a-proxy[Configure your {ocp-short} integration].
+*** xref:configuring-an-rhdh-instance-with-tls-in-kubernetes[Configure your {ocp-short} integration].
 
 . Provision your custom configuration files to your {ocp-short} cluster.
 
diff --git a/modules/installation/proc-install-operator.adoc b/modules/installation/proc-install-operator.adoc
@@ -78,8 +78,3 @@ If you selected an *Automatic* approval strategy, the upgrade status should reso
  *** From the list of installed Operators, locate the {product} Operator name and details.
  *** Click *{product} Operator* to open the *Operator details* page for the {product} Operator.
 
-[role="_additional-resources"]
-.Additional resources
-
-* xref:proc-install-rhdh-ocp-operator_{context}[Deploying {product} on {ocp-short} with the 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]
diff --git a/modules/integrating-with-github/proc-enabling-github-repository-discovery.adoc b/modules/integrating-with-github/proc-enabling-github-repository-discovery.adoc
@@ -25,7 +25,7 @@ Authorization callback URL::
 Enter your {product-short} authentication backend URL: `pass:c,a,q[{my-product-url}/api/auth/github/handler/frame]`.
 
 Webhook::
-Clear "Active", as this is not needed for authentication and catalog providers. 
+Clear "Active", as this is not needed for authentication and catalog providers.
 
 App permissions::
 Select permissions to define the level of access for the app.
@@ -117,7 +117,7 @@ It provides an automated alternative to manually registering components via `cat
 When a repository contains a `catalog-info.yaml` file, the entity is ingested into the catalog as a component.
 +
 .`dynamic-plugins.yaml` file fragment
-[code,yaml]
+[source,yaml]
 ----
 plugins:
   - package: './dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github'
diff --git a/titles/configuring/master.adoc b/titles/configuring/master.adoc
@@ -27,7 +27,7 @@ include::assemblies/assembly-configuring-high-availability.adoc[leveloffset=+1]
 include::assemblies/assembly-configuring-a-proxy.adoc[leveloffset=+1]
 
 
-include::modules/installation/proc-configuring-an-rhdh-instance-with-tls-in-kubernetes.adoc[leveloffset=+1]
+include::modules/configuring/proc-configuring-an-rhdh-instance-with-tls-in-kubernetes.adoc[leveloffset=+1]
 
 
 include::assemblies/dynamic-plugins/assembly-using-the-dynamic-plugins-cache.adoc[ leveloffset=+1]
@@ -36,4 +36,4 @@ include::assemblies/dynamic-plugins/assembly-using-the-dynamic-plugins-cache.ado
 include::assemblies/assembly-configuring-default-secret-pvc-mounts.adoc[leveloffset=+1]
 
 
-include::modules/configuring/proc-enabling-the-rhdh-plugin-assets-cache.adoc[leveloffset=+1]
+include::modules/configuring/proc-enabling-the-rhdh-plugin-assets-cache.adoc[leveloffset=+1]
diff --git a/titles/getting-started-with-rhdh-on-ocp-for-the-platform-engineer/master.adoc b/titles/getting-started-with-rhdh-on-ocp-for-the-platform-engineer/master.adoc
@@ -8,3 +8,52 @@ include::artifacts/attributes.adoc[]
 
 {abstract}
 
+// Install the operator
+include::modules/installation/proc-install-operator.adoc[leveloffset=+1]
+
+
+// Provision your custom configuration
+include::modules/configuring/proc-provisioning-your-custom-configuration.adoc[leveloffset=+1]
+
+// Understand plugins
+include::modules/con-rhdh-plugins.adoc[leveloffset=+1]
+
+
+// Select and enable your plugins
+include::modules/dynamic-plugins/proc-config-dynamic-plugins-rhdh-operator.adoc[leveloffset=+1]
+
+// TODO: Understand the software catalog
+
+// Enable plugin caching
+include::modules/configuring/proc-enabling-the-rhdh-plugin-assets-cache.adoc[leveloffset=+1]
+
+// Configure high availability (replicas)
+include::assemblies/assembly-configuring-high-availability.adoc[leveloffset=+1]
+
+// Optional: If your environment requires it: run behind a proxy
+include::modules/configuring-a-proxy/proc-configuring-proxy-in-operator-deployment.adoc[leveloffset=+1]
+
+// Authentication: simplified
+// FIXME: see https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/1266
+
+// Git provider
+include::modules/integrating-with-github/proc-enabling-github-repository-discovery.adoc[leveloffset=+1]
+
+// Importing manually a Git repository
+//Missing?
+
+// Run a CI pipeline: GitHub; CF + Tekton
+
+// Configure Software Templates
+
+// Changing the title, logo, and color scheme
+== Customizing the appearance of your {product-very-short} instance
+
+include::modules/customizing/proc-customizing-your-product-title.adoc[leveloffset=+2]
+
+
+include::modules/customizing-the-appearance/proc-customize-rhdh-branding-logo.adoc[leveloffset=+2]
+
+
+include::modules/customizing-the-appearance/proc-customize-rhdh-theme-mode.adoc[leveloffset=+2]
+

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-[id="proc-configuring-an-rhdh-instance-with-tls-in-kubernetes_{context}"]`
	`1`	`+[id="configuring-an-rhdh-instance-with-tls-in-kubernetes"]`
`2`	`2`	`= Configuring an {product-very-short} instance with a TLS connection in Kubernetes`
`3`	`3`
`4`	`4`	You can configure a {product-very-short} instance with a Transport Layer Security (TLS) connection in a Kubernetes cluster, such as an Azure Red Hat OpenShift (ARO) cluster, any cluster from a supported cloud provider, or your own cluster with proper configuration. Transport Layer Security (TLS) ensures a secure connection for the {product-very-short} instance with other entities, such as third-party applications, or external databases. However, you must use a public Certificate Authority (CA)-signed certificate to configure your Kubernetes cluster.