RHDEVDOCS-2865: Document the changes in the Add Page and the ability to hide cards on it

Author: HarshCasper

applications/application_life_cycle_management/odc-creating-applications-using-developer-perspective.adoc

@@ -7,14 +7,37 @@ toc::[]
 
 The *Developer* perspective in the web console provides you the following options from the *+Add* view to create applications and associated services and deploy them on {product-title}:
 
-* *From Git*: Use this option to import an existing codebase in a Git repository to create, build, and deploy an application on {product-title}.
-* *Container Image*: Use existing images from an image stream or registry to deploy it on to {product-title}.
-* *From Dockerfile*: Import a dockerfile from your Git repository to build and deploy an application.
-* *YAML*: Use the editor to add YAML or JSON definitions to create and modify resources.
-* *From Catalog*: Explore the *Developer Catalog* to select the required applications, services, or source to image builders and add it to your project.
-* *Database*: See the *Developer Catalog* to select the required database service and add it to your application.
-* *Operator Backed*: Explore the *Developer Catalog* to select and deploy the required Operator-managed service.
-* *Helm Chart*: Explore the *Developer Catalog* to select the required Helm chart to simplify deployment of applications and services.
+* *Getting started resources*: Use these resources to help you get started with Developer Console. You can choose to hide the header using the *Options* menu {kebab}.
+** *Creating applications using samples*: Use existing code samples to get started with creating applications on the {product-title}.
+** *Build with guided documentation*: Follow the guided documentation to build applications and familiarize yourself with key concepts and terminologies.
+** *Explore new developer features*: Explore the new features and resources within the *Developer* perspective.
+
+* *Developer catalog*: Explore the Developer Catalog to select the required applications, services, or source to image builders, and then add it to your project.
+** *All Services*: Browse the catalog to discover services across {product-title}.
+** *Database*: Select the required database service and add it to your application.
+** *Operator Backed*: Select and deploy the required Operator-managed service.
+** *Helm chart*: Select the required Helm chart to simplify deployment of applications and services.
+** *Event Source*: Select an Event source to register interest in a class of events from a particular system.
++
+[NOTE]
+====
+The Managed services option is also available if the RHOAS Operator is installed.
+====
+
+* *Git repository*: Import an existing codebase, Devfile, or Dockerfile from your Git repository using the *From Git*, *From Devfile*, or *From Dockerfile* options respectively, to build and deploy an application on {product-title}.
+
+* *Container images*: Use existing images from an image stream or registry to deploy it on to the {product-title}.
+
+* *Pipelines*: Use Tekton pipeline to create CI/CD pipelines for your software delivery process on the {product-title}.
+
+* *Serverless*: Explore the *Serverless* options to create, build, and deploy stateless and serverless applications on the {product-title}.
+** *Channel*: Create a Knative Channel to create an event forwarding and persistence layer with in-memory and reliable implementations.
+
+* *Samples*: Explore the available sample applications to create, build, and deploy an application quickly.
+
+* *From Local Machine*: Explore the *From Local Machine* tile to import or upload files on your local machine for building and deploying applications easily.
+** *Import YAML*: Upload a YAML file to create and define resources for building and deploying applications.
+** *Upload JAR file*: Upload a JAR file to build and deploy Java applications.
 
 ifdef::openshift-enterprise,openshift-webscale[]
 Note that certain options, such as *Pipelines*, *Event Source*, and *Import Virtual Machines*, are displayed only when the xref:../../cicd/pipelines/installing-pipelines.adoc#op-installing-pipelines-operator-in-web-console_installing-pipelines[OpenShift Pipelines Operator], xref:../../serverless/admin_guide/install-serverless-operator.adoc#serverless-install-web-console_install-serverless-operator[OpenShift Serverless Operator], and xref:../../virt/install/installing-virt-web.adoc#virt-subscribing-to-the-catalog_installing-virt-web[OpenShift Virtualization Operator] are installed, respectively.

images/odc_devcatalog_mariadb.png

@@ -11,8 +11,8 @@ The following procedure explains the *Samples* option in the *Developer* perspec
 
 .Procedure
 
-. In the *+Add* view, click *Samples* to see the *Samples* page. 
-. On the *Samples* page, select one of the available sample applications to see the *Create Sample Application* form. 
+. In the *+Add* view, click on the *Samples* tile to see the *Samples* page.
+. On the *Samples* page, select one of the available sample applications to see the *Create Sample Application* form.
 . In the *Create Sample Application Form*:
 * In the *Name* field, the deployment name is displayed by default. You can modify this name as required.
 * In the *Builder Image Version*, a builder image is selected by default. You can modify this image version by using the *Builder Image Version* drop-down list.

modules/odc-creating-sample-applications.adoc

@@ -5,13 +5,13 @@
 [id="odc-deploying-java-applications_{context}"]
 = Upload JAR files for easy deployment of Java applications
 
-You can use the JAR files in the *Topology* view of the *Developer* perspective to deploy your Java applications. You can upload a JAR file using the following options: 
+You can use the JAR files in the *Topology* view of the *Developer* perspective to deploy your Java applications. You can upload a JAR file using the following options:
 
-* Navigate to the *+Add* view of the *Developer* perspective, click the *Upload JAR file* tile through the *From Local Machine* option. Browse and select your JAR file, or drag and drop a JAR file to deploy your application.
+* Navigate to the *+Add* view of the *Developer* perspective, and click *Upload JAR file* in the *From Local Machine* tile. Browse and select your JAR file, or drag and drop a JAR file to deploy your application.
 
 * Navigate to the *Topology* view and use the *Upload JAR file* option, or drag and drop a JAR file to deploy your application.
 
-* Navigate to the Context Menu in the *Topology* view and use the *Upload JAR file* option to upload your JAR file to deploy your application.
+* Use the in-context menu in the *Topology* view, and then use the *Upload JAR file* option to upload your JAR file to deploy your application.
 
 Use the following instructions to upload a JAR file in the *Topology* view to deploy a Java application:
 
@@ -25,7 +25,7 @@ Use the following instructions to upload a JAR file in the *Topology* view to de
 
 . You can further specify optional Java commands to customize your deployed application. The Runtime Icon and Builder Image is selected by default. If a Builder Image is not auto-detected, select a Builder Image. If required, you can change the version using the *Builder Image Version* drop-down list.
 
-. In the optional *Application Name* field, enter a unique name for your application for the resource labelling. 
+. In the optional *Application Name* field, enter a unique name for your application for the resource labelling.
 
 . In the *Name* field, enter a unique component name to name the associated resources.
 

modules/odc-deploying-java-applications.adoc

@@ -11,7 +11,7 @@ The following procedure walks you through the *From Git* option in the *Develope
 
 .Procedure
 
-. In the *+Add* view, click *From Git* to see the *Import from git* form.
+. In the *+Add* view, click *From Git* in the *Git Repository* tile to see the *Import from git* form.
 . In the *Git* section, enter the Git repository URL for the codebase you want to use to create an application. For example, enter the URL of this sample Node.js application `\https://github.com/sclorg/nodejs-ex`. The URL is then validated.
 . Optional: You can click *Show Advanced Git Options*  to add details such as:
 

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

@@ -9,11 +9,8 @@ You use the Developer Catalog to deploy applications and services based on Opera
 
 .Procedure
 
-. In the *Developer* perspective, navigate to the *+Add* -> *From Catalog* to view all the available services in the *Developer Catalog*.
-. Under *All Items*, select the kind of service or the component you need to add to your project. For this example, select *Databases* to list all the database services and then click *MariaDB* to see the details for the service.
-+
-.Developer Catalog
-image::odc_devcatalog_mariadb.png[]
+. In the *Developer* perspective, navigate to the *+Add* view and from the *Developer Catalog* tile, click *All Services* to view all the available services in the *Developer Catalog*.
+. Under *All Services*, select the kind of service or the component you need to add to your project. For this example, select *Databases* to list all the database services and then click *MariaDB* to see the details for the service.
 +
 . Click *Instantiate Template* to see an automatically populated template with details for the *MariaDB* service, and then click *Create* to create and view the MariaDB service in the *Topology* view.
 +