Test ui-bundle.zip from antora-ui-docs that has UX improvements for i… (#154)

* Test ui-bundle.zip from antora-ui-docs that has UX improvements for interactive graphics, and related TIP edits

* Lightbox TIPs in partials

* Inc Eric's suggestion

Co-authored-by: Eric Schneider <[email protected]>

---------

Co-authored-by: Eric Schneider <[email protected]>

Author: johnsmartco

docs-src/zdm-core/modules/migrate/pages/change-read-routing.adoc

@@ -5,7 +5,7 @@ ifndef::env-github,env-browser,env-vscode[:imagesprefix: ]
 
 This topic explains how you can configure the {zdm-proxy} to route all reads to Target instead of Origin.
 
-Illustrated view of this phase:
+include::partial$lightbox-tip.adoc[]
 
 image::{imagesprefix}migration-phase4ra9.png["Phase 4 diagram shows read routing on ZDM Proxy was switched to Target."]
 

docs-src/zdm-core/modules/migrate/pages/connect-clients-to-target.adoc

@@ -15,7 +15,7 @@ At this point in our migration phases, we've completed:
 
 Now we're ready to perform Phase 5, in which we will configure our client applications to connect directly to Target. The way you do this varies based on whether your Target is Astra DB or a regular Apache Cassandra® or DataStax Enterprise cluster.
 
-Illustrated view of this phase:
+include::partial$lightbox-tip.adoc[]
 
 image::{imagesprefix}migration-phase5ra.png[Phase 5 diagram shows apps no longer using proxy and instead connected directly to Target.]
 

docs-src/zdm-core/modules/migrate/pages/enable-async-dual-reads.adoc

@@ -5,7 +5,7 @@ ifndef::env-github,env-browser,env-vscode[:imagesprefix: ]
 
 In this phase, you can optionally enable asynchronous dual reads. The idea is to test performance and verify that Target can handle your application's live request load before cutting over from Origin to Target.
 
-Illustrated view of this phase:
+include::partial$lightbox-tip.adoc[]
 
 image::{imagesprefix}migration-phase3ra.png[Phase 3 diagram shows optional step enabling async dual reads to test performance of Target.]
 

docs-src/zdm-core/modules/migrate/pages/introduction.adoc

@@ -39,20 +39,25 @@ An important migration prerequisite is that you already have the matching schema
 
 == Migration phases
 
-First, a couple of key terms used throughout the {zdm-product} documentation and software components:
+First, a couple of key terms used throughout the ZDM documentation and software components:
 
 * **Origin:** This cluster is your existing Cassandra-based environment, whether it's open-source Apache Cassandra, DSE, or {astra_db} Classic.
 
 * **Target:** This cluster is the new environment to which you want to migrate client applications and data.
 
 For additional terms, see the xref:glossary.adoc[glossary].
 
+=== Migration interactive diagram
+
+Click the *Start* button on the interactive diagram below to begin a walkthrough of the migration phases.
+Click the components to open a larger view.
+
 [.swiper]
 ====
 [.slide]
 --
 .Walk through the illustrated migration phases
-To get acquainted with the migration phases from start to finish, click the **Start** button below the diagram. Additional navigation options are available as you proceed through the illustrations and discover the key concepts, software components, and sequence of operations.
+Discover the migration concepts, software components, and sequence of operations.
 
 image:migration-introduction9.png["Introductory page prompts you to click the Start button to begin the graphical presentation."]
 --

docs-src/zdm-core/modules/migrate/pages/migrate-and-validate-data.adoc

@@ -12,7 +12,7 @@ For full details, see these topics:
 
 These tools provide sophisticated features that help you migrate your data from any Cassandra **Origin** (Apache Cassandra®, {company} Enterprise (DSE), {company} {astra_db}) to any Cassandra **Target** (Apache Cassandra, DSE, {company} {astra_db}). 
 
-Illustrated view of this phase:
+include::partial$lightbox-tip.adoc[]
 
 image::{imagesprefix}migration-phase2ra.png[Phase 2 diagram shows using tools to migrate data from Origin to Target.]
 

docs-src/zdm-core/modules/migrate/pages/phase1.adoc

@@ -11,7 +11,7 @@ This section presents the following:
 * xref:connect-clients-to-proxy.adoc[]
 * xref:manage-proxy-instances.adoc[]
 
-Illustrated view of this phase:
+include::partial$lightbox-tip.adoc[]
 
 image::{imagesprefix}migration-phase1ra.png[Phase 1 diagram shows deployed ZDM Proxy instances, client app connections to proxies, and Target is setup.]
 

docs-src/zdm-core/modules/migrate/pages/rollback.adoc

@@ -7,7 +7,7 @@ At any point during the migration process until the very last phase, if you hit
 
 The migration can be started from scratch once the issue has been addressed.
 
-Let's revisit a diagram presented earlier:
+include::partial$lightbox-tip-all-phases.adoc[]
 
 image::{imagesprefix}migration-all-phases.png[Migration phases from start to finish.]
 

docs-src/zdm-core/modules/migrate/partials/lightbox-tip-all-phases.adoc

@@ -0,0 +1,7 @@
+ 
+[TIP]
+====
+Here's an illustrated view of all the migration phases. 
+Click the components to open a larger view. 
+Click again to return to the original view. 
+====

docs-src/zdm-core/modules/migrate/partials/lightbox-tip.adoc

@@ -0,0 +1,7 @@
+ 
+[TIP]
+====
+Here's an illustrated view of this phase. 
+Click the components to open a larger view. 
+Click again to return to the original view. 
+====

playbooks/site-local-zdm.yaml

@@ -19,7 +19,9 @@ content:
 
 ui:
   bundle:
-    url: https://github.com/riptano/antora-ui-docs/releases/latest/download/ui-bundle.zip
+    url: https://github.com/riptano/antora-ui-docs/raw/test-lightbox-ux/gcx/build/ui-bundle.zip
+  # url: /Users/john.smart/github/antora-ui-docs/gcx/build/ui-bundle.zip
+  # url: https://github.com/riptano/antora-ui-docs/releases/latest/download/ui-bundle.zip
     snapshot: true
   # Uncomment the "supplemental_files" line below ONLY IF you're trying to
   # change the banner logo to something other than the default logo provided by