refactor prerequs

aerogear · Jul 3, 2018 · d5b48fe · d5b48fe
1 parent 62e851b
commit d5b48fe
Show file tree

Hide file tree

Showing 12 changed files with 10 additions and 36 deletions.
diff --git a/modules/ROOT/pages/_partials/registering-a-mobile-app.adoc b/modules/ROOT/pages/_partials/registering-a-mobile-app.adoc
@@ -6,11 +6,6 @@ After the setup is completed, the next thing you need to do is to register a {mo
 
 A Mobile Client is a representation of the mobile app that you are developing locally. Mobile Clients allow you bind your mobile app to mobile services such as Identity Management, Push Notification, Mobile Metrics and others. This makes many of the common tasks associated with mobile development much easier and quicker to implement. For more information, please check xref:mobile-clients.adoc[Mobile Clients in OpenShift]
 
-[discrete]
-== Prerequisites:
-
-* [x] You have installed OpenShift with {product-name} as described in xref:index.adoc[Getting Started].
-
 [discrete]
 == Procedure
 

diff --git a/modules/ROOT/pages/custom/index.adoc b/modules/ROOT/pages/custom/index.adoc
@@ -10,6 +10,3 @@ include::{partialsdir}/generic-service-intros.adoc[tags=runtimeconnector-service
 
 [id='{context}_additional-resources-{context}']
 
-== Next steps
-
-xref:custom/provisioning.adoc[Provisioning] the {custom-service} Service
diff --git a/modules/ROOT/pages/custom/provisioning.adoc b/modules/ROOT/pages/custom/provisioning.adoc
@@ -19,6 +19,3 @@ When prompted, enter the following:
 
 include::{partialsdir}/generic-provisioning-end.adoc[]
 
-== Next steps
-
-xref:custom/binding.adoc[Binding] to the {service-name} Service
diff --git a/modules/ROOT/pages/digger/index.adoc b/modules/ROOT/pages/digger/index.adoc
@@ -11,6 +11,6 @@ include::{partialsdir}/generic-service-intros.adoc[tags=mobilecicd-service]
 include::./ref_terminology.adoc[leveloffset=+1]
 include::./ref_source-configuration.adoc[leveloffset=+1]
 
-== Next steps
+== Prerequisites
 
-xref:digger/provisioning.adoc[Provisioning {digger-service} Service]
+include::{partialsdir}/generic-provisioning-pre-req.adoc[]
diff --git a/modules/ROOT/pages/digger/provisioning.adoc b/modules/ROOT/pages/digger/provisioning.adoc
@@ -4,10 +4,6 @@ include::{partialsdir}/attributes.adoc[]
 
 = Provisioning {service-name} Service
 
-== Prerequisites
-
-include::{partialsdir}/generic-provisioning-pre-req.adoc[]
-
 include::{partialsdir}/generic-provisioning.adoc[]
 
 When provisioning a {digger-service} service, you are prompted to set the following:

diff --git a/modules/ROOT/pages/keycloak/index.adoc b/modules/ROOT/pages/keycloak/index.adoc
@@ -17,3 +17,7 @@ include::./ref_terminology.adoc[leveloffset=+2]
 === Additional resources
 
 See the link:https://www.keycloak.org/documentation.html[Keycloak documentation] for more info.
+
+== Prerequisites
+
+include::{partialsdir}/generic-provisioning-pre-req.adoc[]
diff --git a/modules/ROOT/pages/metrics/index.adoc b/modules/ROOT/pages/metrics/index.adoc
@@ -27,6 +27,6 @@ To collect metrics from mobile apps, you need to create a binding which is descr
 * For more information, see the link:https://prometheus.io/docs/introduction/overview/[Prometheus Documentation].
 * For more information, see the link:http://docs.grafana.org/[Grafana Documentation].
 
-== Next Steps
+== Prerequisites
 
-* xref:metrics/provisioning.adoc[Provisioning {service-name} Service]
+include::{partialsdir}/generic-provisioning-pre-req.adoc[]
diff --git a/modules/ROOT/pages/metrics/provisioning.adoc b/modules/ROOT/pages/metrics/provisioning.adoc
@@ -4,10 +4,6 @@ include::{partialsdir}/attributes.adoc[]
 
 = Provisioning {service-name} Service
 
-== Prerequisites
-
-include::{partialsdir}/generic-provisioning-pre-req.adoc[]
-
 include::{partialsdir}/generic-provisioning.adoc[]
 
 When provisioning a {service-name} Service, you are prompted to set the following:

diff --git a/modules/ROOT/pages/push/index.adoc b/modules/ROOT/pages/push/index.adoc
@@ -38,6 +38,6 @@ It can be seen as a _broker_ that distributes push messages to different 3rd par
 
 NOTE: When using the UnifiedPush Server, please keep in mind that Push notification is a signalling mechanism and that it is not suitable to be used as a data carrying system (e.g. use in a chat application).
 
-== Next Steps
+== Prerequisites
 
-* xref:push/provisioning.adoc[Provisioning the {unifiedpush-service} service]
+include::{partialsdir}/generic-provisioning-pre-req.adoc[]
diff --git a/modules/ROOT/pages/push/provisioning.adoc b/modules/ROOT/pages/push/provisioning.adoc
@@ -2,10 +2,6 @@ include::{partialsdir}/attributes.adoc[]
 
 = Provisioning {unifiedpush-service} Service
 
-== Prerequisites
-
-include::{partialsdir}/generic-provisioning-pre-req.adoc[]
-
 include::{partialsdir}/generic-provisioning.adoc[]
 
 include::{partialsdir}/generic-provisioning-end.adoc[]

diff --git a/modules/ROOT/pages/security/index.adoc b/modules/ROOT/pages/security/index.adoc
@@ -12,6 +12,3 @@ include::{partialsdir}/generic-service-intros.adoc[tags=device-security-service]
 
 //== Additional resources
 
-== Next steps
-
-xref:security/coding.adoc[Configuring your Development Environment for the Security Service]
diff --git a/modules/ROOT/pages/security/provisioning.adoc b/modules/ROOT/pages/security/provisioning.adoc
@@ -4,10 +4,6 @@ include::{partialsdir}/attributes.adoc[]
 
 = Provisioning {service-name} Service
 
-== Prerequisites
-
-include::{partialsdir}/generic-provisioning-pre-req.adoc[]
-
 include::{partialsdir}/generic-provisioning.adoc[]
 
 ///***TODO***