keep only used templates

hazelcast · Oct 10, 2024 · 174b9c2 · 174b9c2
1 parent f8d023e
commit 174b9c2
Show file tree

Hide file tree

Showing 14 changed files with 6 additions and 185 deletions.
diff --git a/templates/modules/ROOT/pages/getting-started.adoc b/templates/modules/ROOT/pages/getting-started.adoc
diff --git a/templates/modules/ROOT/pages/link-to-repo.adoc b/templates/modules/ROOT/pages/link-to-repo.adoc
diff --git a/templates/modules/ROOT/pages/microservices/application-structure.adoc b/templates/modules/ROOT/pages/microservices/application-structure.adoc
@@ -1,6 +1,8 @@
 // {framework} -> The name of the microservices framework
 
+ifdef::framework[]
 The application is a basic {framework} app having 2 endpoints defined in `CommandController`:
 
 - `/put` is the page where key and values can be put on a Hazelcast distributed map. It takes `key` and `value` as query parameters and returns the entry in JSON format.
-- `/get` is the page where the values in the Hazelcast distributed map can be obtained by keys. It takes `key` as query parameter and returns the found entry in JSON format.
+- `/get` is the page where the values in the Hazelcast distributed map can be obtained by keys. It takes `key` as query parameter and returns the found entry in JSON format.
+endif::[]
diff --git a/templates/modules/ROOT/pages/microservices/running-the-application-curl.adoc b/templates/modules/ROOT/pages/microservices/running-the-application-curl.adoc
diff --git a/templates/modules/ROOT/pages/microservices/what-you-will-learn.adoc b/templates/modules/ROOT/pages/microservices/what-you-will-learn.adoc
@@ -1,5 +1,7 @@
 // {framework} -> The name of the microservices framework
 
+ifdef::framework[]
 In this guide, you will learn how to use Hazelcast IMDG within {framework} microservices.
 
-The {framework} application contains two REST controllers which helps you to put data and read it back. The application initializes a single Hazelcast IMDG member instance which is used to keep the data. When you run the application multiple times, Hazelcast IMDG instances build a cluster and share the data.
+The {framework} application contains two REST controllers which helps you to put data and read it back. The application initializes a single Hazelcast IMDG member instance which is used to keep the data. When you run the application multiple times, Hazelcast IMDG instances build a cluster and share the data.
+endif::[]
diff --git a/templates/modules/ROOT/pages/minikube-teardown.adoc b/templates/modules/ROOT/pages/minikube-teardown.adoc
diff --git a/templates/modules/ROOT/pages/prereq-caching-ms.adoc b/templates/modules/ROOT/pages/prereq-caching-ms.adoc
diff --git a/templates/modules/ROOT/pages/start-cluster.adoc b/templates/modules/ROOT/pages/start-cluster.adoc
diff --git a/templates/modules/ROOT/pages/validate-kube-env.adoc b/templates/modules/ROOT/pages/validate-kube-env.adoc
diff --git a/templates/modules/ROOT/pages/what-is-hz-cloud.adoc b/templates/modules/ROOT/pages/what-is-hz-cloud.adoc
diff --git a/templates/modules/ROOT/pages/what-is-hz.adoc b/templates/modules/ROOT/pages/what-is-hz.adoc
diff --git a/templates/modules/ROOT/pages/what-will-learn-caching-ms.adoc b/templates/modules/ROOT/pages/what-will-learn-caching-ms.adoc
diff --git a/templates/modules/ROOT/pages/youre-done-caching-ms.adoc b/templates/modules/ROOT/pages/youre-done-caching-ms.adoc
diff --git a/templates/modules/ROOT/pages/youre-done-cloud.adoc b/templates/modules/ROOT/pages/youre-done-cloud.adoc