redhat-developer · themr0c · Nov 19, 2024
diff --git a/artifacts/attributes.adoc b/artifacts/attributes.adoc
@@ -1,5 +1,5 @@
 :red-hat-developers-documentation:
-:imagesdir:
+:imagesdir: images
 :idseparator: -
 
 // Company names

diff --git a/artifacts/docinfo.xml b/artifacts/docinfo.xml
@@ -0,0 +1,11 @@
+<title>{title}</title>
+<productname>{product}</productname>
+<productnumber>{product-version}</productnumber>
+<subtitle>{subtitle}</subtitle>
+<abstract>
+<para>{abstract}</para>
+</abstract>
+<authorgroup>
+<orgname>{company-name} Customer Content Services</orgname>
+</authorgroup>
+<xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
diff --git a/assemblies/assembly-add-custom-app-file-openshift.adoc b/assemblies/assembly-add-custom-app-file-openshift.adoc
diff --git a/assemblies/assembly-adding-custom-configuration-files.adoc b/assemblies/assembly-adding-custom-configuration-files.adoc
@@ -0,0 +1,12 @@
+:_mod-docs-content-type: ASSEMBLY
+:context: adding-custom-configuration-files
+[id="{context}"]
+= Adding custom configuration files to {product}
+
+To configure {product}, add custom configuration files to {ocp-brand-name} and register them in {product-short}.
+
+include::modules/adding-custom-configuration-files/proc-adding-custom-configuration-files-by-using-the-operator.adoc[leveloffset=+1]
+
+
+include::modules/adding-custom-configuration-files/proc-adding-custom-configuration-files-by-using-helm.adoc[leveloffset=+1]
+
diff --git a/assemblies/assembly-configuring-external-postgresql-databases.adoc b/assemblies/assembly-configuring-external-postgresql-databases.adoc
@@ -1,4 +1,6 @@
-[id="assembly-configuring-external-postgresql-databases"]
+:_mod-docs-content-type: ASSEMBLY
+:context: configuring-external-postgresql-databases
+[id="{context}"]
 = Configuring external PostgreSQL databases
 
 As an administrator, you can configure and use external PostgreSQL databases in {product}. You can use a PostgreSQL certificate file to configure an external PostgreSQL instance using the Operator or Helm Chart.
@@ -11,9 +13,11 @@ By default, the {product} operator or Helm Chart creates a local PostgreSQL data
 ====
 
 
-include::modules/admin/proc-configuring-postgresql-instance-using-operator.adoc[leveloffset=+1]
+include::modules/external-databases/proc-configuring-postgresql-instance-using-the-operator.adoc[leveloffset=+1]
 
-include::modules/admin/proc-configuring-postgresql-instance-using-helm.adoc[leveloffset=+1]
 
-include::modules/admin/proc-migrating-databases-to-an-external-server.adoc[leveloffset=+1]
+include::modules/external-databases/proc-configuring-postgresql-instance-using-helm.adoc[leveloffset=+1]
+
+
+include::modules/external-databases/proc-migrating-databases-to-an-external-server.adoc[leveloffset=+1]
 
diff --git a/assemblies/assembly-techdocs-plugin.adoc → ...mblies/assembly-configuring-techdocs.adoc b/assemblies/assembly-techdocs-plugin.adoc → ...mblies/assembly-configuring-techdocs.adoc
@@ -1,8 +1,11 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="assembly-techdocs-plugin_{context}"]
-= Configuring the TechDocs plugin in {product}
+:context: configuring-techdocs
+[id="{context}"]
+= Configuring TechDocs
 
-The {product} TechDocs plugin helps your organization create, find, and use documentation in a central location and in a standardized way. For example:
+Configure the {product} TechDocs plugin to create, find,
+and use documentation in a central location and in a standardized way.
+For example:
 
 Docs-like-code approach::
 Write your technical documentation in Markdown files that are stored inside your project repository along with your code.

diff --git a/assemblies/assembly-admin-templates.adoc → ...blies/assembly-configuring-templates.adoc b/assemblies/assembly-admin-templates.adoc → ...blies/assembly-configuring-templates.adoc
@@ -1,14 +1,12 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="assembly-admin-templates"]
-= Managing templates
-:context: assembly-admin-templates
+:context: configuring-templates
+[id="{context}"]
+= Configuring templates
 
-toc::[]
+Configure templates to create software components, and publish these components to different locations, such as the {product} software catalog, or Git repositories.
 
 A template is a form composed of different UI fields that is defined in a YAML file. Templates include _actions_, which are steps that are executed in sequential order and can be executed conditionally.
 
-You can use templates to easily create {product} components, and then publish these components to different locations, such as the {product} software catalog, or repositories in GitHub or GitLab.
-
 include::modules/templates/proc-creating-templates.adoc[leveloffset=+1]
 include::modules/templates/ref-creating-templates.adoc[leveloffset=+1]
 

diff --git a/...mblies/assembly-customize-rhdh-theme.adoc → ...assembly-customizing-rhdh-appearance.adoc b/...mblies/assembly-customize-rhdh-theme.adoc → ...assembly-customizing-rhdh-appearance.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="assembly-customize-rhdh-theme"]
-= Customizing the appearance of your {product} instance
-:context: assembly-customize-rhdh-theme
+:context: customizing-appearance
+[id="{context}"]
+= Customizing {product} appearance
 
 The following default theme configurations are available for {product}:
 

diff --git a/assemblies/assembly-customizing-the-quick-access-card-in-rhdh.adoc b/assemblies/assembly-customizing-the-quick-access-card-in-rhdh.adoc
@@ -1,15 +1,15 @@
 :_mod-docs-content-type: ASSEMBLY
-
-[id="customizing-the-quick-access-card-in-rhdh"]
-= Customizing the Quick access card in {product}
+:context: customizing-quick-access-card
+[id="{context}"]
+= Customizing {product} Quick access card
 
 To access the Home page in {product}, the base URL must include the `/developer-hub` proxy. You can configure the Home page by passing the data into the `app-config.yaml` file as a proxy. You can provide data to the Home page from the following sources:
 
 * JSON files hosted on GitHub or GitLab.
 * A dedicated service that provides the Home page data in JSON format using an API.
 
 include::modules/getting-started/proc-using-hosted-json-files-to-provide-data-to-the-quick-access-card.adoc[leveloffset=+1]
-include::modules/getting-started/proc-using-a-dedicated-service-to-provide-data-to-the-quick-access-card.adoc[leveloffset=+1]
 
 
+include::modules/getting-started/proc-using-a-dedicated-service-to-provide-data-to-the-quick-access-card.adoc[leveloffset=+1]
 
diff --git a/assemblies/assembly-customizing-the-rhdh-homepage.adoc b/assemblies/assembly-customizing-the-rhdh-homepage.adoc
@@ -1,4 +1,4 @@
-[id='proc-customize-rhdh-homepage_{context}']
+[id='proc-customize-rhdh-homepage']
 = Customizing the Home page in {product}
 
 When using the `app-config`, you can do the following:
@@ -16,4 +16,4 @@ When using the `app-config`, you can do the following:
 ** Featured docs
 
 include::modules/getting-started/proc-customizing-the-home-page-cards.adoc[leveloffset=+1]
-include::modules/getting-started/proc-defining-the-layout-of-the-product-home-page.adoc[leveloffset=+1]
+include::modules/getting-started/proc-defining-the-layout-of-the-product-home-page.adoc[leveloffset=+1]
diff --git a/assemblies/assembly-rhdh-integration-aws.adoc b/assemblies/assembly-rhdh-integration-aws.adoc
diff --git a/...assembly-running-rhdh-behind-a-proxy.adoc → ...lies/assembly-running-behind-a-proxy.adoc b/...assembly-running-rhdh-behind-a-proxy.adoc → ...lies/assembly-running-behind-a-proxy.adoc
@@ -1,5 +1,9 @@
-[id="assembly-running-rhdh-behind-a-proxy"]
-= Running the {product-very-short} application behind a corporate proxy
+:_mod-docs-content-type: ASSEMBLY
+:context: running-behind-a-proxy
+[id="{context}"]
+= Running {product} behind a corporate proxy
+
+In a network restricted environment, configure {product} to use your proxy to access remote network resources.
 
 You can run the {product-very-short} application behind a corporate proxy by setting any of the following environment variables before starting the application:
 
@@ -8,6 +12,8 @@ You can run the {product-very-short} application behind a corporate proxy by set
 
 Additionally, you can set the `NO_PROXY` environment variable to exclude certain domains from proxying. The variable value is a comma-separated list of hostnames that do not require a proxy to get reached, even if one is specified.
 
+include::modules/proxy/proc-configuring-proxy-in-operator-deployment.adoc[leveloffset=+1]
+
+
+include::modules/proxy/proc-configuring-proxy-in-helm-deployment.adoc[leveloffset=+1]
 
-include::modules/admin/proc-configuring-proxy-in-helm-deployment.adoc[leveloffset=+1]
-include::modules/admin/proc-configuring-proxy-in-operator-deployment.adoc[leveloffset=+1]
diff --git a/...c-add-custom-app-file-openshift-helm.adoc → ...om-configuration-files-by-using-helm.adoc b/...c-add-custom-app-file-openshift-helm.adoc → ...om-configuration-files-by-using-helm.adoc
@@ -1,5 +1,5 @@
 [id='proc-add-custom-app-file-openshift-helm_{context}']
-= Adding a custom application configuration file to {ocp-short} using the Helm chart
+= Adding custom {product} configuration files by using the Helm chart
 
 You can use the {product} Helm chart to add a custom application configuration file to your {ocp-short} instance.
 

diff --git a/...-custom-app-config-file-ocp-operator.adoc → ...guration-files-by-using-the-operator.adoc b/...-custom-app-config-file-ocp-operator.adoc → ...guration-files-by-using-the-operator.adoc
@@ -1,5 +1,5 @@
 [id="proc-add-custom-app-config-file-ocp-operator_{context}"]
-= Adding a custom application configuration file to {ocp-short} using the Operator
+= Adding custom {product} configuration files by using the operator
 
 A custom application configuration file is a `ConfigMap` object that you can use to change the configuration of your {product} instance. If you are deploying your {product-short} instance on {ocp-brand-name}, you can use the {product} Operator to add a custom application configuration file to your {ocp-short} instance by creating the `ConfigMap` object and referencing it in the {product-short} custom resource (CR).
 

diff --git a/...es/admin/proc-rhdh-deployment-config.adoc → ...ing-deployment-by-using-the-operator.adoc b/...es/admin/proc-rhdh-deployment-config.adoc → ...ing-deployment-by-using-the-operator.adoc
@@ -1,8 +1,5 @@
-// Module included in:
-// title-admin.adoc
-
 [id="proc-rhdh-deployment-config_{context}"]
-= Configuring {product} deployment
+= Configuring {product} deployment by using the operator
 
 The {product} operator exposes a `rhdh.redhat.com/v1alpha2` API Version of its Custom Resource Definition (CRD). This CRD 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.
 
@@ -147,4 +144,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].
+* 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].
diff --git a/modules/customization/proc-customize-rhdh-branding-logo.adoc b/modules/customization/proc-customize-rhdh-branding-logo.adoc
@@ -1,5 +1,5 @@
 // Module included in the following assemblies:
-// assembly-customize-rhdh-theme.adoc 
+// assembly-customizing-rhdh-appearance.adoc
 //restored module as per slack thread: https://redhat-internal.slack.com/archives/C04CUSD4JSG/p1726856912238529
 
 [id="proc-customize-rhdh-branding-logo_{context}"]

diff --git a/modules/customization/proc-customize-rhdh-font.adoc b/modules/customization/proc-customize-rhdh-font.adoc
@@ -1,5 +1,5 @@
 // Module included in the following assemblies:
-// assembly-customize-rhdh-theme.adoc
+// assembly-customizing-rhdh-appearance.adoc
 
 [id="proc-customize-rhdh-font_{context}"]
 = Customizing the font for your {product-short} instance

diff --git a/modules/customization/proc-customize-rhdh-page-theme.adoc b/modules/customization/proc-customize-rhdh-page-theme.adoc
@@ -1,5 +1,5 @@
 // Module included in the following assemblies:
-// assembly-customize-rhdh-theme.adoc
+// assembly-customizing-rhdh-appearance.adoc
 
 [id="proc-customize-rhdh-page-theme_{context}"]
 = Customizing the page theme header for your {product-short} instance

diff --git a/modules/customization/proc-customize-rhdh-palette.adoc b/modules/customization/proc-customize-rhdh-palette.adoc
@@ -1,5 +1,5 @@
 // Module included in the following assemblies:
-// assembly-customize-rhdh-theme.adoc
+// assembly-customizing-rhdh-appearance.adoc
 
 [id="proc-customize-rhdh-branding_{context}"]
 = Customizing the theme mode color palettes for your {product-short} instance

diff --git a/modules/customization/proc-customize-rhdh-tab-tooltip.adoc b/modules/customization/proc-customize-rhdh-tab-tooltip.adoc
@@ -1,5 +1,5 @@
 // Module included in the following assemblies:
-// assembly-customize-rhdh-theme.adoc
+// assembly-customizing-rhdh-appearance.adoc
 
 [id="proc-customizing-rhdh-tab-tooltip_{context}"]
 = Customizing the application title for your {product-short} instance

diff --git a/modules/customization/proc-customize-rhdh-theme-mode.adoc b/modules/customization/proc-customize-rhdh-theme-mode.adoc
@@ -1,5 +1,5 @@
 // Module included in the following assemblies:
-// assembly-customize-rhdh-theme.adoc
+// assembly-customizing-rhdh-appearance.adoc
 
 [id="proc-customizing-rhdh-theme-mode_{context}"]
 = Customizing the theme mode for your {product-short} instance

diff --git a/modules/customization/ref-customize-rhdh-custom-components.adoc b/modules/customization/ref-customize-rhdh-custom-components.adoc
@@ -1,5 +1,5 @@
 // Module included in the following assemblies:
-// assembly-customize-rhdh-theme.adoc
+// assembly-customizing-rhdh-appearance.adoc
 
 [id="ref-customize-rhdh-custom-components_{context}"]
 = Custom component options for your {product-short} instance

diff --git a/modules/customization/ref-customize-rhdh-default-backstage.adoc b/modules/customization/ref-customize-rhdh-default-backstage.adoc
@@ -1,5 +1,5 @@
 // Module included in the following assemblies:
-// assembly-customize-rhdh-theme.adoc
+// assembly-customizing-rhdh-appearance.adoc
 
 [id="ref-customize-rhdh-default-backstage_{context}"]
 = Default Backstage theme

diff --git a/modules/customization/ref-customize-rhdh-default-rhdh.adoc b/modules/customization/ref-customize-rhdh-default-rhdh.adoc
@@ -1,5 +1,5 @@
 // Module included in the following assemblies:
-// assembly-customize-rhdh-theme.adoc
+// assembly-customizing-rhdh-appearance.adoc
 
 [id="ref-customize-rhdh-default-rhdh_{context}"]
 = Default {product} theme

diff --git a/...uring-postgresql-instance-using-helm.adoc → ...uring-postgresql-instance-using-helm.adoc b/...uring-postgresql-instance-using-helm.adoc → ...uring-postgresql-instance-using-helm.adoc
diff --git a/...g-postgresql-instance-using-operator.adoc → ...stgresql-instance-using-the-operator.adoc b/...g-postgresql-instance-using-operator.adoc → ...stgresql-instance-using-the-operator.adoc
diff --git a/...ting-databases-to-an-external-server.adoc → ...ting-databases-to-an-external-server.adoc b/...ting-databases-to-an-external-server.adoc → ...ting-databases-to-an-external-server.adoc
diff --git a/modules/getting-started/proc-customize-rhdh-learning-paths.adoc b/modules/getting-started/proc-customize-rhdh-learning-paths.adoc
@@ -7,7 +7,7 @@ In {product}, you can configure Learning Paths by passing the data into the `app
 ====
 Due to the use of overlapping `pathRewrites` for both the `learning-path` and `homepage` quick access proxies, you must create the `learning-paths` configuration (`^api/proxy/developer-hub/learning-paths`) before you create the `homepage` configuration (`^/api/proxy/developer-hub`).
 
-For more information about customizing the Home page in {product}, see xref:proc-customize-rhdh-homepage_rhdh-getting-started[Customizing the Home page in {product}].
+For more information about customizing the Home page in {product}, see xref:proc-customize-rhdh-homepage[Customizing the Home page in {product}].
 ====
 
 You can provide data to the Learning Path from the following sources:

diff --git a/modules/getting-started/proc-customize-rhdh-tech-radar-page.adoc b/modules/getting-started/proc-customize-rhdh-tech-radar-page.adoc
@@ -9,7 +9,7 @@ In {product}, you can configure Learning Paths by passing the data into the `app
 ====
 Due to the use of overlapping `pathRewrites` for both the `tech-radar` and `homepage` quick access proxies, you must create the `tech-radar` configuration (`^api/proxy/developer-hub/tech-radar`) before you create the `homepage` configuration (`^/api/proxy/developer-hub`).
 
-For more information about customizing the Home page in {product}, see xref:proc-customize-rhdh-homepage_rhdh-getting-started[Customizing the Home page in {product}].
+For more information about customizing the Home page in {product}, see xref:proc-customize-rhdh-homepage[Customizing the Home page in {product}].
 ====
 
 You can provide data to the Tech Radar page from the following sources:

diff --git a/...configuring-proxy-in-helm-deployment.adoc → ...configuring-proxy-in-helm-deployment.adoc b/...configuring-proxy-in-helm-deployment.adoc → ...configuring-proxy-in-helm-deployment.adoc
diff --git a/...iguring-proxy-in-operator-deployment.adoc → ...iguring-proxy-in-operator-deployment.adoc b/...iguring-proxy-in-operator-deployment.adoc → ...iguring-proxy-in-operator-deployment.adoc
diff --git a/modules/templates/proc-adding-templates.adoc b/modules/templates/proc-adding-templates.adoc
@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * assemblies/assembly-admin-templates.adoc
+// * assemblies/assembly-configuring-templates.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="proc-adding-templates_{context}"]

diff --git a/modules/templates/proc-creating-templates.adoc b/modules/templates/proc-creating-templates.adoc
@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * assemblies/assembly-admin-templates.adoc
+// * assemblies/assembly-configuring-templates.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="proc-creating-templates_{context}"]

diff --git a/modules/templates/ref-creating-templates.adoc b/modules/templates/ref-creating-templates.adoc
@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * assemblies/assembly-admin-templates.adoc
+// * assemblies/assembly-configuring-templates.adoc
 
 :_mod-docs-content-type: REFERENCE
 [id="ref-creating-templates_{context}"]

diff --git a/titles/admin-rhdh/docinfo.xml b/titles/admin-rhdh/docinfo.xml
diff --git a/titles/admin-rhdh/master.adoc b/titles/admin-rhdh/master.adoc
diff --git a/titles/admin-rhdh/title-admin.adoc b/titles/admin-rhdh/title-admin.adoc