[enterprise-4.10] RHDEVDOCS-3623: Update Pipeline section in add flow and pipeline docs

cicd/pipelines/working-with-pipelines-using-the-developer-perspective.adoc

@@ -7,9 +7,9 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 You can use the *Developer* perspective of the {product-title} web console to create CI/CD pipelines for your software delivery process.
 
-
 In the *Developer* perspective:
 
 * Use the *Add* -> *Pipeline* -> *Pipeline Builder* option to create customized pipelines for your application.
@@ -28,9 +28,13 @@ After you create the pipelines for your application, you can view and visually i
 
 include::modules/op-constructing-pipelines-using-pipeline-builder.adoc[leveloffset=+1]
 
-== Creating applications with OpenShift Pipelines
+== Creating OpenShift Pipelines along with applications
+
+To create pipelines along with applications, use the *From Git* option in the *Add+* view of the *Developer* perspective. You can view all of your available pipelines and select the pipelines you want to use to create applications while importing your code or deploying an image. 
+
+The Tekton Hub Integration is enabled by default and you can see tasks from the Tekton Hub that are supported by your cluster. Administrators can opt out of the Tekton Hub Integration and the Tekton Hub tasks will no longer be displayed. You can also check whether a webhook URL exists for a generated pipeline. Default webhooks are added for the pipelines that are created using the *+Add* flow and the URL is visible in the side panel of the selected resources in the Topology view.
 
-To create pipelines along with applications, use the *From Git* option in the *Add* view of the *Developer* perspective. For more information, see xref:../../applications/creating_applications/odc-creating-applications-using-developer-perspective.adoc#odc-importing-codebase-from-git-to-create-application_odc-creating-applications-using-developer-perspective[Creating applications using the Developer perspective].
+For more information, see xref:../../applications/creating_applications/odc-creating-applications-using-developer-perspective.adoc#odc-importing-codebase-from-git-to-create-application_odc-creating-applications-using-developer-perspective[Creating applications using the Developer perspective].
 
 include::modules/op-interacting-with-pipelines-using-the-developer-perspective.adoc[leveloffset=+1]
 

modules/odc-importing-codebase-from-git-to-create-application.adoc

@@ -6,6 +6,7 @@
 [id="odc-importing-codebase-from-git-to-create-application_{context}"]
 = Importing a codebase from Git to create an application
 
+[role="_abstract"]
 You can use the *Developer* perspective to create, build, and deploy an application on {product-title} using an existing codebase in GitHub.
 
 The following procedure walks you through the *From Git* option in the *Developer* perspective to create an application.
@@ -50,7 +51,7 @@ The resource name must be unique in a namespace. Modify the resource name if you
 The *Serverless Deployment* option is displayed in the *Import from git* form only if the {ServerlessOperatorName} is installed in your cluster. For further details, refer to the {ServerlessProductName} documentation.
 ====
 
-. In the *Pipelines* section, select *Add Pipeline*, and then click *Show Pipeline Visualization* to see the pipeline for the application.
+. In the *Pipelines* section, select *Add Pipeline*, and then click *Show Pipeline Visualization* to see the pipeline for the application. A default pipeline is selected, but you can choose the pipeline you want from the list of available pipelines for the application.
 
 . Optional: In the *Advanced Options* section, the *Target port* and the *Create a route to the application* is selected by default so that you can access your application using a publicly available URL.
 +

modules/op-constructing-pipelines-using-pipeline-builder.adoc

@@ -6,6 +6,7 @@
 [id="op-constructing-pipelines-using-pipeline-builder_{context}"]
 = Constructing Pipelines using the Pipeline Builder
 
+[role="_abstract"]
 In the *Developer* perspective of the console, you can use the *+Add* -> *Pipeline* -> *Pipeline builder* option to:
 
 * Configure pipelines using either the *Pipeline builder* or the *YAML view*.

modules/op-interacting-with-pipelines-using-the-developer-perspective.adoc

@@ -6,6 +6,7 @@
 [id="op-interacting-with-pipelines-using-the-developer-perspective_{context}"]
 = Interacting with pipelines using the Developer perspective
 
+[role="_abstract"]
 The *Pipelines* view in the *Developer* perspective lists all the pipelines in a project, along with the following details:
 
 * The namespace in which the pipeline was created
@@ -37,7 +38,7 @@ You can use this information to improve the pipeline workflow and eliminate issu
 +
 The *Pipeline Runs* tab provides details about the pipeline run, the status of the task, and a link to debug failed pipeline runs. Use the Options menu {kebab} to stop a running pipeline, to rerun a pipeline using the same parameters and resources as that of the previous pipeline execution, or to delete a pipeline run.
 +
-* Click the required pipeline run to see the *Pipeline Run details* page. By default, the *Details* tab displays a visual representation of all the serial tasks, parallel tasks, `finally` tasks, and when expressions in the pipeline run. The results for successful runs are displayed under the *Pipeline Run results* pane at the bottom of the page.
+* Click the required pipeline run to see the *Pipeline Run details* page. By default, the *Details* tab displays a visual representation of all the serial tasks, parallel tasks, `finally` tasks, and when expressions in the pipeline run. The results for successful runs are displayed under the *Pipeline Run results* pane at the bottom of the page. Additionally, you would only be able to see tasks from Tekton Hub which are supported by the cluster. While looking at a task, you can click the link beside it to jump to the task documentation.
 +
 [NOTE]
 ====