Move quarkus items from cloud to advanced use cases, fix links

serverlessworkflow/modules/ROOT/pages/cloud/quarkus/deploying-on-kubernetes.adoc → serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/deployments/deploying-on-kubernetes.adoc

@@ -1,4 +1,4 @@
-= Deploying your Serverless Workflow application on Kubernetes
+= Deploying your {product_name} application on Kubernetes
 :compat-mode!:
 // Metadata:
 :description: Deploying Serverless Application on Kubernetes
@@ -31,7 +31,7 @@
 This document describes how to deploy a {product_name} application using a Kubernetes cluster, along with a procedure to run the Knative platform.
 
 // shared pre req
-include::../common/_prerequisites.adoc[subs=quotes+]
+include::./common/_prerequisites.adoc[subs=quotes+]
 
 
 Before proceeding further, make sure that you have access to the Kubernetes cluster with Knative available.
@@ -67,7 +67,7 @@ Once Knative is ready, you can initiate the process of deploying your {product_n
 
 
 // shared app req
-include::../common/_deploy_workflow_application_requisites.adoc[]
+include::./common/_deploy_workflow_application_requisites.adoc[]
 
 [IMPORTANT]
 ====
@@ -79,11 +79,10 @@ If the registry requires authentication you need to create a Pull Secret with th
 .Procedure
 . Create `serverless-workflow-greeting-quarkus` namespace using the following command:
 +
-include::../common/_create_namespace_and_deploy_info.adoc[]
+include::./common/_create_namespace_and_deploy_info.adoc[]
 
 In the following procedures, you can find different approaches to deploy your workflow application, such as:
 
-* <<proc-deploy-sw-application-knative-cli,Using Knative CLI (kn)>>
 * <<proc-deploy-sw-application-kubectl,Using kubectl command-line tool>>
 * <<proc-deploy-sw-application-quarkus-cli,Using Quarkus CLI>>
 
@@ -94,13 +93,10 @@ For this tutorial, we use the `default-domain` provided by Knative that configur
 the Magic DNS for naming resolution, for more details please check the Knative link:{knative_domain_dns_url}[documentation].
 ====
 
-// deploy with kn-cli
-include::../common/_proc_deploy_sw_kn_cli.adoc[]
-
 // deploy with kubectl
-include::../common/_proc_deploy_sw_kubectl.adoc[]
+include::./common/_proc_deploy_sw_kubectl.adoc[]
 
 // deploy with quarkus-cli
-include::../common/_proc_deploy_sw_quarkus_cli.adoc[]
+include::./common/_proc_deploy_sw_quarkus_cli.adoc[]
 
-include::../../../pages/_common-content/report-issue.adoc[]
+include::../../../../pages/_common-content/report-issue.adoc[]

serverlessworkflow/modules/ROOT/pages/cloud/quarkus/deploying-on-minikube.adoc → serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/deployments/deploying-on-minikube.adoc

@@ -30,7 +30,7 @@ This document describes how to deploy your workflow application using a local Ku
 For more information about Minikube and related system requirements, see link:{minikube_url}/docs/start/[Getting started with Minikube] documentation.
 
 // shared pre req
-include::../common/_prerequisites.adoc[]
+include::./common/_prerequisites.adoc[]
 
 To deploy your workflow application on Minikube, you need to install Knative on Minikube. However, first you need to ensure that Minikube is installed correctly.
 
@@ -128,7 +128,7 @@ To follow the manual process of installing Knative on Minikube, see link:{knativ
 Once you install Knative on Minikube, you can initiate the process of deploying your workflow application on Minikube.
 
 // shared app req
-include::../common/_deploy_workflow_application_requisites.adoc[]
+include::./common/_deploy_workflow_application_requisites.adoc[]
 
 
 .Procedure
@@ -203,7 +203,7 @@ Status:
 
 . After starting the Minikube tunnel, create `serverless-workflow-greeting-quarkus` namespace using the following command:
 +
-include::../common/_create_namespace_and_deploy_info.adoc[]
+include::./common/_create_namespace_and_deploy_info.adoc[]
 
 In the following procedures, you can find different approaches to deploy your workflow application, such as:
 
@@ -213,16 +213,16 @@ In the following procedures, you can find different approaches to deploy your wo
 
 
 // deploy with kn-cli
-include::../common/_proc_deploy_sw_kn_cli.adoc[]
+include::./common/_proc_deploy_sw_kn_cli.adoc[]
 
 // deploy with kubectl
-include::../common/_proc_deploy_sw_kubectl.adoc[]
+include::./common/_proc_deploy_sw_kubectl.adoc[]
 
 // deploy with quarkus-cli
-include::../common/_proc_deploy_sw_quarkus_cli.adoc[]
+include::./common/_proc_deploy_sw_quarkus_cli.adoc[]
 
 
 // verify deployed swf
-include::../common/_verify_if_swf_is_deployed.adoc[]
+include::./common/_verify_if_swf_is_deployed.adoc[]
 
-include::../../../pages/_common-content/report-issue.adoc[]
+include::../../../../pages/_common-content/report-issue.adoc[]

serverlessworkflow/modules/ROOT/pages/cloud/quarkus/deploying-on-openshift.adoc → serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/deployments/deploying-on-openshift.adoc

@@ -69,7 +69,7 @@ If you get error messages related to `Istio`, this link:{knative_istio_issue_url
 Once `Knative Serving` is ready, you can initiate the process of deploying your {product_name} application on OpenShift.
 
 // shared app req
-include::../common/_deploy_workflow_application_requisites.adoc[]
+include::./common/_deploy_workflow_application_requisites.adoc[]
 
 After checking the prerequisites, prepare the project that will be used to deploy your application:
 
@@ -168,12 +168,12 @@ In the next steps you will notice the value **{k8s_registry}** being used. It is
 * <<proc-deploy-sw-application-quarkus-cli,Using Quarkus CLI>>
 
 // deploy with kn-cli
-include::../common/_proc_deploy_sw_kn_cli.adoc[]
+include::./common/_proc_deploy_sw_kn_cli.adoc[]
 
 // deploy with kubectl
-include::../common/_proc_deploy_sw_oc.adoc[]
+include::./common/_proc_deploy_sw_oc.adoc[]
 
 // deploy with quarkus-cli
-include::../common/_proc_deploy_sw_quarkus_cli.adoc[]
+include::./common/_proc_deploy_sw_quarkus_cli.adoc[]
 
-include::../../../pages/_common-content/report-issue.adoc[]
+include::../../../../pages/_common-content/report-issue.adoc[]

serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/getting-started/build-serverless-workflow-quarkus-examples.adoc

@@ -1,4 +1,4 @@
-= Building images of serverless workflow example applications using Quarkus CLI
+= Building image of {product_name} example application using Quarkus CLI
 :compat-mode!:
 // Metadata:
 :description: Build Serverless Application with Quarkus CLI

serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/getting-started/build-workflow-image-with-quarkus-cli.adoc

@@ -225,4 +225,4 @@ Example response::
 * xref:cloud/quarkus/deploying-on-kubernetes.adoc[Deploying your {product_name} application on Kubernetes]
 * xref:cloud/quarkus/deploying-on-openshift.adoc[Deploying your {product_name} application on OpenShift]
 
-include::../../../pages/_common-content/report-issue.adoc[]
+include::../../../../pages/_common-content/report-issue.adoc[]

serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/integrations/serverless-dashboard-with-runtime-data.adoc

@@ -254,7 +254,7 @@ For more information about creating a workflow, see xref:getting-started/create-
 The following is an example of GraphQL query that lists all the workflows:
 
 .Example GraphQL query to retrieve all workflows
-[source,grahpql]
+[source,json]
 ----
 {
   ProcessInstances {

serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/testing/basic-integration-tests-with-restassured.adoc

@@ -32,7 +32,7 @@ The following procedure describes how to test a workflow application that expose
 ----
 
 .Prerequisites
-include::../../pages/_common-content/getting-started-requirement.adoc[]
+include::../../../../pages/_common-content/getting-started-requirement.adoc[]
 
 [NOTE]
 ====
@@ -162,4 +162,4 @@ If you see a similar output, this means your test is executed successfully.
 * link:https://quarkus.io/guides/getting-started-testing[Testing a Quarkus application]
 * link:https://rest-assured.io/#docs[REST Assured Documentation]
 
-include::../../pages/_common-content/report-issue.adoc[]
+include::../../../../pages/_common-content/report-issue.adoc[]