Cleanup/Change template to Composer AI

content/antora.yml

@@ -1,15 +1,13 @@
 name: modules
-title: Default Title
+title: Composer AI
 version: main
 nav:
   - modules/ROOT/nav.adoc
 
 asciidoc:
   attributes:
-    lab_name: "I'm the lab_name var"
-    page-pagination: true
-    my_var: "foo"
-    guid: my-guid
-    ssh_user: devops
-    ssh_password: devops
-    ssh_command: ssh devops@bastion.{guid}.example.opentlc.com
+    openshift_api_url: https://api.cluster-guid.guid.sandbox.opentlc.com:6443
+    openshift_cluster_ingress_domain: apps.cluster-guid.guid.sandbox.opentlc.com
+    openshift_cluster_console_url: https://console-openshift-console.apps.cluster-guid.guid.sandbox.opentlc.com
+    openshift_cluster_admin_username: username
+    openshift_cluster_admin_password: password

content/modules/ROOT/nav.adoc

@@ -1,7 +1,4 @@
-* xref:module-01.adoc[1. RPM Native Container]
-** xref:module-01.adoc#repositories[Repositories]
-** xref:module-01.adoc#software[Software]
-
-* xref:module-02.adoc[2. GitHub Sourced Container]
-** xref:module-02.adoc#prerequisites[Install Prerequisites]
-** xref:module-02.adoc#container[Enable Container]
+* xref:01-setup.adoc[1. Setup]
+* xref:02-rag.adoc[2. RAG]
+* xref:03-chatbot.adoc[3. Chatbot]
+* xref:04-rhelai.adoc[4. RHEL AI]

content/modules/ROOT/pages/01-setup.adoc

@@ -0,0 +1,3 @@
+= Setup Environment
+
+This is the OpenShift apps domain: {openshift_cluster_ingress_domain}

content/modules/ROOT/pages/02-rag.adoc

@@ -0,0 +1,3 @@
+= RAG
+
+This is the OpenShift apps domain: {openshift_cluster_ingress_domain}

content/modules/ROOT/pages/03-chatbot.adoc

@@ -0,0 +1,3 @@
+= Chatbot
+
+This is the OpenShift apps domain: {openshift_cluster_ingress_domain}

content/modules/ROOT/pages/04-rhelai.adoc

@@ -0,0 +1,3 @@
+= RHEL AI
+
+This is the OpenShift apps domain: {openshift_cluster_ingress_domain}

content/modules/ROOT/pages/index.adoc

@@ -1,43 +1,3 @@
-= Welcome to Showroom
+= Composer AI and building Productivity Apps
 
-The `lab_name` var, known as an asciidoc attribute, above was set in `./content/antora.yml` and can be used to set the lab_name or title of your content.
-You are both free to change its value and if you prefer to use a different var name, you can change the value of `lab_name`, for example to `title` in `./content/antora.yml` and then reference it in your content as `\{title}`. +
-
-image::rhel-logo-black.jpg[rhel-logo-black,55%,55%]
-
-== Variables
-
-Other vars can also be set there, such as `ssh_user` and `ssh_password`, and referenced inline in the lab content by using the `\{foo}` syntax.
-
-This is another var, or asciidoc attribute, from `./content/antora.yml` {my_var}
-
-== Writing your lab
-
-Whatever type of content you are writing we'll refer to your *content* as "your lab" in this document.
-
-=== Lab structure
-
-Wether you are writing a lab
-
-* First, we will build a monolithic application already compiled as RPM packages and put it into a container. This will allow us to deploy the application, copy it between machines, and update it separately from the operating system. This process affords us a portable and easily maintained component instead of tightly coupling the application with your operating system maintenance.
-
-* In closing we will build a second container on a different operating system version that makes an application not packaged into RPMs. This will be similar to a web application deployment, positioning the correct files at the right locations. To do this, we will pull a project from GitHub and position the component files within our container image. The purpose of this is to achieve a portable application container that can deploy on several different versions of Red Hat Enterprise Linux. This also provides the benefit of decoupling your application maintenance, which would all happen by building new containers versus operating system maintenance. The container is no longer reliant on the operating system installed on the machine where the application is deployed.
-
-. Now let's examine this cluster a bit more by describing the cluster (the `$GUID` environment variable is already set for you so you can immediately describe your individual cluster):
-+
-[source,sh,role=execute]
-----
-podman ps
-----
-+
-.Sample Output
-[source,texinfo,subs="attributes"]
-----
-CONTAINER ID  IMAGE                        COMMAND           CREATED      STATUS      PORTS                 NAMES
-2dcfee9e50c4  docker.io/library/httpd:2.4  httpd-foreground  3 hours ago  Up 3 hours  0.0.0.0:8080->80/tcp  showroom-httpd
-----
-
-=== Lab Access
-
-The terminal window to your right is *already* logged into the lab environment as the `{ssh_user}` user via `ssh`. 
-All steps of this lab are to be completed as the `{ssh_user}` user.
+This is the OpenShift apps domain: {openshift_cluster_ingress_domain}

default-site.yml

@@ -13,7 +13,7 @@ ui:
     url: https://github.com/rhpds/rhdp_showroom_theme/releases/download/v0.0.1/ui-bundle.zip
 
 runtime:
-  cache_dir: ./.cache
+  cache_dir: ./.cache/antora
 
 output:
   dir: ./www