openshift · jseseCCS · Aug 3, 2026
diff --git a/modules/odc-customizing-a-perspective-using-YAML-view.adoc b/modules/odc-customizing-a-perspective-using-YAML-view.adoc
@@ -6,6 +6,9 @@
 [id="odc-customizing-a-perspective-using-YAML-view_{context}"]
 = Customizing a perspective using YAML view
 
+[role="_abstract"]
+You can customize a perspective by editing the YAML content of the *Console (operator.openshift.io)* resource.
+
 .Prerequisites
 * You must have administrator privileges.
 

diff --git a/modules/odc-customizing-a-perspective-using-form-view.adoc b/modules/odc-customizing-a-perspective-using-form-view.adoc
@@ -6,6 +6,9 @@
 [id="odc-customizing-a-perspective-using-form-view_{context}"]
 = Customizing a perspective using form view
 
+[role="_abstract"]
+You can customize a perspective by using the form view of the *Console (operator.openshift.io)* resource.
+
 .Prerequisites
 * You must have administrator privileges.
 
@@ -21,7 +24,7 @@
 +
 A notification opens to confirm that your changes are saved.
 +
-image::customizing-user-perspective.png[]
+image::customizing-user-perspective.png[Notification confirming that perspective customization changes are saved]
 +
 [NOTE]
 ====

diff --git a/modules/odc-customizing-user-perspectives.adoc b/modules/odc-customizing-user-perspectives.adoc
@@ -6,6 +6,7 @@
 [id="odc-customizing-user-perspectives_{context}"]
 = Customizing user perspectives
 
+[role="_abstract"]
 The {product-title} web console provides two perspectives by default, *Administrator* and *Developer*. You might have more perspectives available depending on installed console plugins. As a cluster administrator, you can show or hide a perspective for all users or for a specific user role. Customizing  perspectives ensures that users can view only the perspectives that are applicable to their role and tasks. For example, you can hide the *Administrator* perspective from unprivileged users so that they cannot manage cluster resources, users, and projects. Similarly, you can show the *Developer* perspective to users with the developer role so that they can create, deploy, and monitor applications.
 
 You can also customize the perspective visibility for users based on role-based access control (RBAC). For example, if you customize a perspective for monitoring purposes, which requires specific permissions, you can define that the perspective is visible only to users with required permissions.

diff --git a/modules/odc_con_customizing-a-developer-catalog-or-its-sub-catalogs.adoc b/modules/odc_con_customizing-a-developer-catalog-or-its-sub-catalogs.adoc
@@ -7,6 +7,7 @@
 [id="odc_con_customizing-a-developer-catalog-or-its-sub-catalogs_{context}"]
 = Developer catalog and sub-catalog customization
 
+[role="_abstract"]
 As a cluster administrator, you have the ability to organize and manage the Developer catalog or its sub-catalogs. You can enable or disable the sub-catalog types or disable the entire developer catalog.
 
 The `developerCatalog.types` object includes the following parameters that you must define in a snippet to use them in the YAML view:

diff --git a/modules/odc_con_example-yaml-file-changes.adoc b/modules/odc_con_example-yaml-file-changes.adoc
@@ -7,6 +7,7 @@
 [id="con_example-yaml-file-changes_{context}"]
 = Example YAML file changes
 
+[role="_abstract"]
 You can dynamically add the following snippets in the YAML editor for customizing a developer catalog.
 
 Use the following snippet to display all the sub-catalogs by setting the _state_ type to *Enabled*.

diff --git a/...dc_customizing-a-developer-catalog-or-its-sub-catalogs-using-the-form-view.adoc b/...dc_customizing-a-developer-catalog-or-its-sub-catalogs-using-the-form-view.adoc
@@ -6,6 +6,7 @@
 [id="odc_customizing-a-developer-catalog-or-its-sub-catalogs-using-the-form-view_{context}"]
 = Customizing a developer catalog or its sub-catalogs using the form view
 
+[role="_abstract"]
 You can customize a developer catalog by using the form view in the Web Console.
 
 .Prerequisites
@@ -23,7 +24,7 @@ You can customize a developer catalog by using the form view in the Web Console.
 .Verification
 After you have customized the developer catalog, your changes are automatically saved in the system and take effect in the browser after a refresh.
 +
-image::odc_customizing_developer_catalog.png[]
+image::odc_customizing_developer_catalog.png[Developer catalog customization options in the form view]
 
 [NOTE]
 ====

diff --git a/...dc_customizing-a-developer-catalog-or-its-sub-catalogs-using-the-yaml-view.adoc b/...dc_customizing-a-developer-catalog-or-its-sub-catalogs-using-the-yaml-view.adoc
@@ -7,6 +7,7 @@
 [id="odc_customizing-a-developer-catalog-or-its-sub-catalogs-using-the-yaml-view_{context}"]
 = Customizing a developer catalog or its sub-catalogs using the YAML view
 
+[role="_abstract"]
 You can customize a developer catalog by editing the YAML content in the YAML view.
 
 .Prerequisites
@@ -42,7 +43,7 @@ spec:
 ----
 
 . Click *Save*.
-
++
 [NOTE]
 ====
 By default, the developer catalog types are enabled in the Administrator view of the Web Console.