diff --git a/.env.sample b/.env.sample
index f21de7484..79dd000ed 100644
--- a/.env.sample
+++ b/.env.sample
@@ -3,3 +3,5 @@ GATSBY_ALGOLIA_SEARCH_KEY=
 ALGOLIA_ADMIN_KEY=
 GATSBY_CLOUDFLARE_URL=
 BUILD_ENV=LOCAL
+
+
diff --git a/modules/ROOT/pages/api-user-management.adoc b/modules/ROOT/pages/api-user-management.adoc
index 3c41e7065..d327af112 100644
--- a/modules/ROOT/pages/api-user-management.adoc
+++ b/modules/ROOT/pages/api-user-management.adoc
@@ -121,7 +121,6 @@ To create a user:
 * +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Fusers%2Fcreate-user">POST /api/rest/2.0/users/create</a>+++ (Rest API v2)
 * xref:user-api.adoc#create-user[POST /tspublic/v1/user] (Rest API v1)
 
-
 To update user details:
 
 * +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Fusers%2Fupdate-user">POST /api/rest/2.0/users/{user_identifier}/update</a>+++ (Rest API v2)
@@ -135,18 +134,20 @@ If you rename an SSO user through the REST API and that user then logs in throug
 
 * If Just-in-Time (JIT) provisioning is enabled, ThoughtSpot creates a new duplicate account. The duplicate account does not inherit the original user's content, groups, or permissions.
 * If JIT provisioning is disabled, the user cannot log in.
+====
 
-To safely update the username of an SSO user:
+To update the username of an SSO user:
 
 . Update the username in your IdP.
 . Before the user logs in again, update the username in ThoughtSpot to match the new value using the REST API or Admin UI.
 
 Both updates must be complete before the user's next SSO login.
-The order of the two steps can be reversed — you may update ThoughtSpot first and the IdP second — provided the user does not log in during the interval between the two changes.
+The order of the two steps can be reversed. You may update ThoughtSpot first and the IdP second, provided the user does not log in during the interval between the two changes.
 
 For SSO users, ThoughtSpot derives email address and display name directly from the IdP. Update these attributes in your IdP only.
 ThoughtSpot automatically reflects the new values when the user next logs in through SSO.
 Do not use the REST API or the Admin UI to update the email address or display name of an SSO user.
+====
 
 For users who authenticate directly with ThoughtSpot (not through an external IdP), you can update username, email address, and display name using the REST API or Admin UI.
 No IdP coordination is required for local users.
diff --git a/modules/ROOT/pages/common/nav-embedding.adoc b/modules/ROOT/pages/common/nav-embedding.adoc
index 347aa02bb..c65bdd872 100644
--- a/modules/ROOT/pages/common/nav-embedding.adoc
+++ b/modules/ROOT/pages/common/nav-embedding.adoc
@@ -124,6 +124,8 @@ Customize and integrate
 Embedding tutorials
 
 * link:{{navprefix}}/tutorials/tutorials-overview[Embedding tutorials]
+
+////
 * link:{{navprefix}}/tutorials/tse-fundamentals/intro[Embedding Fundamentals]
 ** link:{{navprefix}}/tutorials/tse-fundamentals/lesson-01[01 - Overview]
 ** link:{{navprefix}}/tutorials/tse-fundamentals/lesson-02[02 - Set up for course]
@@ -142,8 +144,16 @@ Embedding tutorials
 ** link:{{navprefix}}/tutorials/react-components/lesson-02[02 - ThoughtSpot component pages]
 ** link:{{navprefix}}/tutorials/react-components/lesson-03[03 - Menus and navigation elements]
 ** link:{{navprefix}}/tutorials/react-components/lesson-04[04 - Event handling]
-* link:{{navprefix}}/tutorials/spotter/integrate-into-chatbot[Integrate Spotter into your Chatbot]
+//* link:{{navprefix}}/tutorials/spotter/integrate-into-chatbot[Integrate Spotter into your Chatbot]
+
+* link:{{navprefix}}/tutorials/react-components/intro[Introduction]
+** link:{{navprefix}}/tutorials/react-components/lesson-01[Initializing ThoughtSpot Embed SDK]
+** link:{{navprefix}}/tutorials/react-components/lesson-02[ThoughtSpot component pages]
+** link:{{navprefix}}/tutorials/react-components/lesson-03[Menus and other navigation elements]
+** link:{{navprefix}}/tutorials/react-components/lesson-04[Event handling]
 
+* link:{{navprefix}}/tutorials/spotter/integrate-into-chatbot[Integrate Spotter into your chatbot]
+////
 
 [.sidebar-title]
 Reference guides and changelog
diff --git a/modules/ROOT/pages/common/nav-release-notes.adoc b/modules/ROOT/pages/common/nav-release-notes.adoc
new file mode 100644
index 000000000..061b9ec4d
--- /dev/null
+++ b/modules/ROOT/pages/common/nav-release-notes.adoc
@@ -0,0 +1,17 @@
+
+:page-pageid: nav-release-notes
+:page-description: Release notes and changelogs
+
+[navSection]
+
+[.sidebar-title]
+Release notes and changelogs
+
+* link:{{navprefix}}/whats-new[What's new]
+* Changelog
+** link:{{navprefix}}/embed-sdk-changelog[Visual Embed SDK changelog]
+** link:{{navprefix}}/mobile-sdk-changelog[Mobile Embed SDK changelog]
+** link:{{navprefix}}/rest-v2-changelog[REST API v2 changelog]
+** link:{{navprefix}}/mcp-server-changelog[Spotter MCP Server changelog]
+* link:{{navprefix}}/deprecated-features[Deprecation announcements]
+
diff --git a/modules/ROOT/pages/common/nav-rest-api.adoc b/modules/ROOT/pages/common/nav-rest-api.adoc
index a0ebf26aa..88e4749eb 100644
--- a/modules/ROOT/pages/common/nav-rest-api.adoc
+++ b/modules/ROOT/pages/common/nav-rest-api.adoc
@@ -38,8 +38,6 @@ REST APIs
 ** link:{{navprefix}}/webhooks-rest-api[Webhook APIs]
 
 
-
-
 [.sidebar-title]
 REST API SDK
 
@@ -50,14 +48,19 @@ REST API SDK
 * link:{{navprefix}}/rest-api-sdk-csharp[C# SDK]
 * link:{{navprefix}}/rest-apiv2-js[REST API v2.0 in JavaScript]
 
+
 [.sidebar-title]
 REST API Tutorials
 
 * link:{{navprefix}}/tutorials/rest-api/intro[REST API Tutorials]
+
+////
 * link:{{navprefix}}/tutorials/rest-api/lesson-01[01 - REST API overview]
 * link:{{navprefix}}/tutorials/rest-api/lesson-02[02 - Simple Python implementation]
 * link:{{navprefix}}/tutorials/rest-api/lesson-03[03 - Complex REST API workflows]
 
+////
+
 [.sidebar-title]
 REST API v1 (DEPRECATED)
 
diff --git a/modules/ROOT/pages/common/nav-tutorials.adoc b/modules/ROOT/pages/common/nav-tutorials.adoc
new file mode 100644
index 000000000..5ebf5d5b7
--- /dev/null
+++ b/modules/ROOT/pages/common/nav-tutorials.adoc
@@ -0,0 +1,51 @@
+
+:page-pageid: nav-tutorials
+:page-description: Tutorials navigation
+
+[navSection]
+
+[.sidebar-title]
+Embedding fundamentals
+
+* link:{{navprefix}}/tutorials/tse-fundamentals/intro[Introduction]
+* link:{{navprefix}}/tutorials/tse-fundamentals/lesson-01[Overview of ThoughtSpot Embedded]
+* link:{{navprefix}}/tutorials/tse-fundamentals/lesson-02[Setting up for the course]
+* link:{{navprefix}}/tutorials/tse-fundamentals/lesson-03[Security Setting]
+* link:{{navprefix}}/tutorials/tse-fundamentals/lesson-04[Start Coding]
+* link:{{navprefix}}/tutorials/tse-fundamentals/lesson-05[Embed Search]
+* link:{{navprefix}}/tutorials/tse-fundamentals/lesson-06[Embed Natural Language Search]
+* link:{{navprefix}}/tutorials/tse-fundamentals/lesson-07[Embed Liveboard]
+* link:{{navprefix}}/tutorials/tse-fundamentals/lesson-08[Embed Liveboard Visualization]
+* link:{{navprefix}}/tutorials/tse-fundamentals/lesson-09[Embed Application]
+* link:{{navprefix}}/tutorials/tse-fundamentals/lesson-10[Styling ThoughtSpot]
+* link:{{navprefix}}/tutorials/tse-fundamentals/lesson-11[Summary and Next Steps]
+
+[.sidebar-title]
+UI elements and style customization
+
+* link:{{navprefix}}/tutorials/style-customization/intro[Introduction]
+* link:{{navprefix}}/tutorials/style-customization/step-01[Getting started]
+* link:{{navprefix}}/tutorials/style-customization/step-02[Large component elements]
+* link:{{navprefix}}/tutorials/style-customization/step-03[CSS styles]
+* link:{{navprefix}}/tutorials/style-customization/step-04[Text strings and icon replacement]
+* link:{{navprefix}}/tutorials/style-customization/step-05[Menu items]
+* link:{{navprefix}}/tutorials/style-customization/step-06[Conclusion]
+
+[.sidebar-title]
+REST API tutorials
+
+** link:{{navprefix}}/tutorials/rest-api/intro[Introduction]
+** link:{{navprefix}}/tutorials/rest-api/lesson-01[REST API overview]
+** link:{{navprefix}}/tutorials/rest-api/lesson-02[Simple Python implementation]
+** link:{{navprefix}}/tutorials/rest-api/lesson-03[Complex REST API workflows]
+** link:{{navprefix}}/tutorials/rest-api/lesson-04[Browser JavaScript REST API implementation]
+
+[.sidebar-title]
+React Components Tutorial
+
+* link:{{navprefix}}/tutorials/react-components/intro[Introduction]
+* link:{{navprefix}}/tutorials/react-components/lesson-01[Initializing ThoughtSpot Embed SDK]
+* link:{{navprefix}}/tutorials/react-components/lesson-02[ThoughtSpot component pages]
+* link:{{navprefix}}/tutorials/react-components/lesson-03[Menus and other navigation elements]
+* link:{{navprefix}}/tutorials/react-components/lesson-04[Event handling]
+//* link:{{navprefix}}/tutorials/spotter/integrate-into-chatbot[Integrate Spotter into your chatbot]
diff --git a/modules/ROOT/pages/common/nav-walkthroughs.adoc b/modules/ROOT/pages/common/nav-walkthroughs.adoc
new file mode 100644
index 000000000..53846edb8
--- /dev/null
+++ b/modules/ROOT/pages/common/nav-walkthroughs.adoc
@@ -0,0 +1,50 @@
+
+:page-pageid: nav-walkthroughs
+:page-description: Guided Walkthroughs navigation
+
+//
+// HOW TO ADD A NEW WALKTHROUGH/TUTORIAL GROUP
+// ---------------------------------------------------------------------
+// Each tutorial below MUST be a two-level list:
+//   * Tutorial group name (no link — this line is just the heading)
+//   ** link:...[Step 1]
+//   ** link:...[Step 2]
+//   ...
+//
+// Do NOT flatten this to a single level (all "*", no "**"). The nesting
+// is load-bearing, not cosmetic — the left nav (LeftSidebar/index.scss,
+// ".tutorialsNavWrapper" rules) relies on exactly this two-level shape to:
+//   1. Number each step with a circular badge (counter-reset/increment
+//      on the nested <ul>, restarting at 1 per tutorial).
+//   2. Auto-collapse every OTHER tutorial (and this one's own heading)
+//      once you're inside a tutorial's pages, so only the active
+//      tutorial's numbered steps show (see the ":has()" drill-down rules
+//      in the same file, and LeftSidebar/helper.tsx's expand/collapse
+//      logic, which both require a nested <li> containing a nested <ul>).
+//
+// Flattening this file (even by mistake, e.g. during a merge) silently
+// removes BOTH behaviors with no build error — the nav just renders as
+// a plain unnumbered, ungrouped list of links. If that ever happens,
+// restore the "*" / "**" nesting shown below rather than changing the CSS.
+//
+
+[.sidebar-title]
+Get started
+
+* Build a data-driven app with ThoughtSpot Embedded
+** link:{{navprefix}}/tutorials/embed-data-driven-app/intro[Build a data-driven app with ThoughtSpot Embedded]
+** link:{{navprefix}}/tutorials/embed-data-driven-app/into-developer-portal[Get into the Developer Portal]
+** link:{{navprefix}}/tutorials/embed-data-driven-app/base-liveboard-rendering[Get the base Liveboard rendering]
+** link:{{navprefix}}/tutorials/embed-data-driven-app/make-it-conversational[Make it conversational]
+** link:{{navprefix}}/tutorials/embed-data-driven-app/style-to-match-portal[Style it to match the portal]
+** link:{{navprefix}}/tutorials/embed-data-driven-app/wire-custom-action[Wire in a custom action]
+** link:{{navprefix}}/tutorials/embed-data-driven-app/troubleshooting[When it doesn't just work]
+** link:{{navprefix}}/tutorials/embed-data-driven-app/summary[Where to go from here]
+
+* Build it faster
+** link:{{navprefix}}/tutorials/spottercode-embed/intro[Embed ThoughtSpot with SpotterCode]
+** link:{{navprefix}}/tutorials/spottercode-embed/set-up-spottercode[Set up SpotterCode]
+** link:{{navprefix}}/tutorials/spottercode-embed/embed-liveboard-view[Embed the Liveboard view]
+** link:{{navprefix}}/tutorials/spottercode-embed/embed-spotter[Embed Spotter]
+** link:{{navprefix}}/tutorials/spottercode-embed/troubleshooting[Troubleshooting]
+** link:{{navprefix}}/tutorials/spottercode-embed/summary[Summary]
diff --git a/modules/ROOT/pages/common/nav.adoc b/modules/ROOT/pages/common/nav.adoc
index 688e73792..817197cc7 100644
--- a/modules/ROOT/pages/common/nav.adoc
+++ b/modules/ROOT/pages/common/nav.adoc
@@ -5,15 +5,18 @@
 [navSection]
 
 [.sidebar-title]
-Release notes and changelogs
+Quickstart Guides
 
-* link:{{navprefix}}/whats-new[What's new]
-* Changelog
-** link:{{navprefix}}/embed-sdk-changelog[Visual Embed SDK changelog]
-** link:{{navprefix}}/mobile-sdk-changelog[Mobile Embed SDK changelog]
-** link:{{navprefix}}/rest-v2-changelog[REST API v2 changelog]
-** link:{{navprefix}}/mcp-server-changelog[Spotter MCP Server changelog]
-* link:{{navprefix}}/deprecated-features[Deprecation announcements]
+* link:{{navprefix}}/tutorials/walkthroughs[Walkthroughs]
+
+[.sidebar-title]
+Get started
+
+* link:{{navprefix}}/getting-started[Embed ThoughtSpot]
+* link:{{navprefix}}/SpotterCode[SpotterCode]
+* link:{{navprefix}}/rest-apis[REST APIs]
+* link:{{navprefix}}/ai-analytics-integration[AI analytics integration]
+* link:{{navprefix}}/mcp-integration[MCP Server integration]
 
 [.sidebar-title]
 Live Playgrounds
@@ -27,69 +30,61 @@ Live Playgrounds
 * +++<a href="https://try-everywhere.thoughtspot.cloud/v2/#/everywhere/playground/theme-builder" target="_blank">Theme Builder</a>+++
 ** link:{{navprefix}}/theme-builder-doc[How to use]
 
-
 [.sidebar-title]
-Get started
+Reference Guides
 
-* link:{{navprefix}}/getting-started[Embed ThoughtSpot]
-* link:{{navprefix}}/SpotterCode[SpotterCode]
-* link:{{navprefix}}/rest-apis[REST APIs]
-* link:{{navprefix}}/ai-analytics-integration[AI analytics integration]
-* link:{{navprefix}}/mcp-integration[MCP Server integration]
-//** link:{{navprefix}}/tutorials/tutorials-overview[Tutorials]
 * link:{{navprefix}}/VisualEmbedSdk[SDK and API reference]
-** link:{{navprefix}}/VisualEmbedSdk[Visual Embed SDK]
-** link:{{navprefix}}/rest-apiv2-reference[REST API]
-** link:{{navprefix}}/mcp-tool-reference[MCP tools]
+* link:{{navprefix}}/rest-apiv2-reference[REST API]
+* link:{{navprefix}}/mcp-tool-reference[MCP tools]
+
+[.sidebar-title]
+Integration Guides
 
+* link:{{navprefix}}/webhooks-overview[Overview]
+** link:{{navprefix}}/webhooks-ui[Webhooks UI]
+** link:{{navprefix}}/webhooks-comm-channel[Webhook communication channels]
+** link:{{navprefix}}/webhooks-lb-schedule[Webhook connection for Liveboard scheduled events]
+** link:{{navprefix}}/webhooks-s3-integration[AWS S3 storage integration for webhook delivery]
+** link:{{navprefix}}/webhooks-gcs-storage[GCS storage integration for webhook delivery]
+** link:{{navprefix}}/webhooks-lb-payload[Webhook response payload]
+** link:{{navprefix}}/webhooks-kpi[Webhook connection for KPI alerts]
+
+* link:{{navprefix}}/external-tool-script-integration[External tools and scripts]
+* link:{{navprefix}}/pendo-integration[Pendo integration with embed]
+* link:{{navprefix}}/sf-integration[Integration with Salesforce]
+* link:{{navprefix}}/vercel-integration[Vercel integration]
 
 [.sidebar-title]
-Build and deploy
+Deployment guides
 
-** link:{{navprefix}}/thoughtspot-objects[ThoughtSpot objects]
-** link:{{navprefix}}/timezone-aware-filtering[Timezone-aware keywords and filters]
-** link:{{navprefix}}/variables[Variables]
-** link:{{navprefix}}/parameterize-metadata[Parameterize metadata]
+* link:{{navprefix}}/thoughtspot-objects[ThoughtSpot objects]
+* link:{{navprefix}}/timezone-aware-filtering[Timezone-aware keywords and filters]
+* link:{{navprefix}}/variables[Variables]
+* link:{{navprefix}}/parameterize-metadata[Parameterize metadata]
 * link:{{navprefix}}/development-and-deployment[Development and deployment]
-** link:{{navprefix}}/deploy-with-tml-apis[Deploy with TML APIs]
-*** link:{{navprefix}}/git-provider-integration[Git provider integration]
-*** link:{{navprefix}}/modify-tml[TML modification]
+* link:{{navprefix}}/deploy-with-tml-apis[Deploy with TML APIs]
+** link:{{navprefix}}/git-provider-integration[Git provider integration]
+** link:{{navprefix}}/modify-tml[TML modification]
 * link:{{navprefix}}/publish-data-overview[Publish content to Orgs]
 ** link:{{navprefix}}/publish-to-orgs[Publish objects to Orgs]
 * link:{{navprefix}}/git-integration[Deploy with GitHub APIs (legacy)]
 ** link:{{navprefix}}/git-configuration[Configure GitHub integration]
 ** link:{{navprefix}}/git-api[GitHub REST APIs]
 ** link:{{navprefix}}/guid-mapping[GUID mapping]
-
-[.sidebar-title]
-Multi-tenancy
-
 * link:{{navprefix}}/multi-tenancy[Overview]
-* link:{{navprefix}}/orgs[Multi-tenancy with Orgs]
+** link:{{navprefix}}/orgs[Multi-tenancy with Orgs]
 ** link:{{navprefix}}/orgs-api-op[Org administration]
 ** link:{{navprefix}}/multitenancy-within-an-org[Multi-tenancy within an Org]
 ** link:{{navprefix}}/single-tenant-data-models[Single-tenant data models with Orgs]
 * link:{{navprefix}}/tse-cluster[Cluster maintenance and upgrade]
 
 [.sidebar-title]
-Webhooks
+Tutorials
 
-* link:{{navprefix}}/webhooks-overview[Overview]
-* link:{{navprefix}}/webhooks-ui[Webhooks UI]
-* link:{{navprefix}}/webhooks-comm-channel[Webhook communication channels]
-* link:{{navprefix}}/webhooks-lb-schedule[Webhook connection for Liveboard scheduled events]
-* link:{{navprefix}}/webhooks-s3-integration[AWS S3 storage integration for webhook delivery]
-* link:{{navprefix}}/webhooks-gcs-storage[GCS storage integration for webhook delivery]
-* link:{{navprefix}}/webhooks-lb-payload[Webhook response payload]
-* link:{{navprefix}}/webhooks-kpi[Webhook connection for KPI alerts]
+* link:{{navprefix}}/tutorials/tutorials-overview[Embedding tutorials]
+* link:{{navprefix}}/tutorials/rest-api/intro[REST API Tutorials]
 
-[.sidebar-title]
-Integration with external tools
 
-** link:{{navprefix}}/external-tool-script-integration[External tools and scripts]
-** link:{{navprefix}}/pendo-integration[Pendo integration with embed]
-** link:{{navprefix}}/sf-integration[Integration with Salesforce]
-** link:{{navprefix}}/vercel-integration[Vercel integration]
 
 [.sidebar-title]
 Additional resources
diff --git a/modules/ROOT/pages/developer-playground.adoc b/modules/ROOT/pages/developer-playground.adoc
index 7d80036f4..a4525ba0c 100644
--- a/modules/ROOT/pages/developer-playground.adoc
+++ b/modules/ROOT/pages/developer-playground.adoc
@@ -136,7 +136,7 @@ To explore the features available for embedding Natural Language Search:
 
 . Go to *Playground* > *Natural Language Search*.
 . Select a data source.
-. +++<a href="{{previewPrefix}}/playground/sage" id="preview-in-playground" target="_blank">Try out</a>+++ the following customization settings and click *Run* to preview the result.
+. +++<a href="{{previewPrefix}}/playground/sage" target="_blank">Try out</a>+++ the following customization settings and click *Run* to preview the result.
 
 [width="100%"]
 |====
@@ -194,7 +194,7 @@ To explore the Spotter embedding features:
 
 . Go to *Playground* > *Spotter*.
 . Select a data source.
-. +++<a href="{{previewPrefix}}/playground/sage" id="preview-in-playground" target="_blank">Try out</a>+++ the following customization settings and click *Run* to preview the result.
+. +++<a href="{{previewPrefix}}/playground/sage" target="_blank">Try out</a>+++ the following customization settings and click *Run* to preview the result.
 
 [width="100%"]
 |====
diff --git a/modules/ROOT/pages/home.adoc b/modules/ROOT/pages/home.adoc
index 59849dca6..f0f150e82 100644
--- a/modules/ROOT/pages/home.adoc
+++ b/modules/ROOT/pages/home.adoc
@@ -8,6 +8,17 @@
 ++++
 <div class="container">
 <div class="header-banner">
+    <div class="radiance-bg">
+        <div class="blob blob-pink"></div>
+        <div class="blob blob-purple"></div>
+        <div class="blob blob-blue"></div>
+        <div class="blob blob-orange"></div>
+        <div class="blob blob-yellow"></div>
+        <div class="blob blob-purple-r"></div>
+        <div class="blob blob-teal"></div>
+        <div class="blob blob-wash-pink"></div>
+        <div class="blob blob-wash-blue"></div>
+    </div>
     <div class="header-banner-text">
       <h1>ThoughtSpot Embedded Documentation</h1>
       <p>Learn how to use developer tools, APIs, and SDKs to embed ThoughtSpot content in your app.</p>
@@ -27,7 +38,6 @@
 [.non-link]
 ++++
 <div class="document-body-wrapper">
-<div class="cardHeading"> Get started with embedding</div>
 <div class="row flex pb-10">
 	<div class="col-md-4 flex">
 <div class="boxDiv"><div>
@@ -117,7 +127,6 @@
 [.non-link]
 ++++
 <div class="document-body-wrapper">
-<div class="cardHeading">Integrate tools and workflows</div>
 <div class="row flex pb-10">
 	<div class="col-md-4 flex">
 <div class="boxDiv"><div>
diff --git a/modules/ROOT/pages/onboarding-guide.adoc b/modules/ROOT/pages/onboarding-guide.adoc
index 42510ac4f..73d3fa9b9 100644
--- a/modules/ROOT/pages/onboarding-guide.adoc
+++ b/modules/ROOT/pages/onboarding-guide.adoc
@@ -1,4 +1,4 @@
-= Quickstart Guide
+= Get started with embedding
 :toc: true
 :linkattrs:
 :sectanchors:
@@ -32,7 +32,7 @@ If you’re using the Free Trial instance, note that it is already connected to
 
 To learn more about data connections, data models and objects, and how to search data and create Liveboards, see link:https://docs.thoughtspot.com/cloud/latest/ts-cloud-getting-started[ThoughtSpot product documentation, window=_blank].
 
-== Get started with embedding
+== Embed ThoughtSpotcontent
 This section provides a set of steps to quickly embed a xref:faqs.adoc#lbDef[Liveboard] from the link:https://www.thoughtspot.com/trial?tsiref=web-devsite[Free Trial, window=_blank] or your own ThoughtSpot application instance.
 The following figure shows a sample Liveboard with charts and a table:
 
diff --git a/modules/ROOT/pages/rest-api-v2-reference.adoc b/modules/ROOT/pages/rest-api-v2-reference.adoc
index 799c77ed2..e34dae733 100644
--- a/modules/ROOT/pages/rest-api-v2-reference.adoc
+++ b/modules/ROOT/pages/rest-api-v2-reference.adoc
@@ -16,7 +16,7 @@ Access to ThoughtSpot data is controlled based on xref:api-user-management.adoc#
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -123,7 +123,7 @@ ThoughtSpot Software: __Not available__  a| +++<a href="{{navprefix}}/restV2-pla
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -191,7 +191,7 @@ a| +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoint
 == Collections
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -230,7 +230,7 @@ ThoughtSpot Software: __Not available__ + a| +++<a href="{{navprefix}}/restV2-pl
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -303,7 +303,7 @@ a| +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoint
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -343,7 +343,7 @@ ThoughtSpot Software: __26.3.0.sw or later__ + a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -383,7 +383,7 @@ ThoughtSpot Software: __9.8.0.sw or later__   a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -420,7 +420,7 @@ a|+++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -452,7 +452,7 @@ ThoughtSpot Software: __9.0.1.sw or later__  a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -503,7 +503,7 @@ ThoughtSpot Software: __10.0.0.sw or later__  a| +++<a href="{{navprefix}}/restV
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -551,7 +551,7 @@ ThoughtSpot Software: __Not available__   a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -598,7 +598,7 @@ ThoughtSpot Software: __9.0.1.sw or later__  a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -614,7 +614,7 @@ ThoughtSpot Software: __Not available__
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -667,7 +667,7 @@ ThoughtSpot Software: __Not available__  a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -780,7 +780,7 @@ a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -817,7 +817,7 @@ ThoughtSpot Software: __Not Applicable__ a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -841,7 +841,7 @@ ThoughtSpot Software: __9.0.1.sw or later__ a| +++<a href="{{navprefix}}/restV2-
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -883,7 +883,7 @@ ThoughtSpot Software: __Not applicable__   a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -925,7 +925,7 @@ ThoughtSpot Software: __9.5.0.sw or later__ a| +++<a href="{{navprefix}}/restV2-
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -999,7 +999,7 @@ Adds or updates column security rules applied on the Table specified in the API
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -1053,7 +1053,7 @@ a| +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoint
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version| Playground link
@@ -1115,7 +1115,7 @@ ThoughtSpot Software: __26.3.0.sw or later__ a| +++<a href="{{navprefix}}/restV2
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -1168,7 +1168,7 @@ ThoughtSpot Software: __9.0.1.sw or later__  a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -1244,7 +1244,7 @@ ThoughtSpot Software: __9.8.0.sw or later__ a| +++<a href="{{navprefix}}/restV2-
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -1322,7 +1322,7 @@ ThoughtSpot Software: __9.5.0.sw or later__  a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
@@ -1376,7 +1376,7 @@ a|ThoughtSpot Cloud: __10.9.0.cl or later__ a|
 
 [div boxAuto]
 --
-[width="100%" cols="8,5,3"]
+[width="100%" cols="6,6,3"]
 [options='header']
 |=====
 |API endpoint| Release version | Playground link
diff --git a/modules/ROOT/pages/spotter-agent-instructions.adoc b/modules/ROOT/pages/spotter-agent-instructions.adoc
index 4a6f9008d..530177958 100644
--- a/modules/ROOT/pages/spotter-agent-instructions.adoc
+++ b/modules/ROOT/pages/spotter-agent-instructions.adoc
@@ -14,11 +14,11 @@ Unlike xref:spotter-nl-instructions.adoc[data model instructions], which operate
 
 [width="100%", cols="1"]
 |=====
-a|`PUT /api/rest/2.0/ai/agent/instructions/set` [.version-badge.new]#New# +
+a|`PUT /api/rest/2.0/ai/agent/instructions/set`  +
 xref:spotter-agent-instructions.adoc#_set_agent_instructions[Sets behavioral instructions] for the Spotter agent. +
 __Available on ThoughtSpot Cloud instances from 26.7.0.cl onwards.__
 
-a|`GET /api/rest/2.0/ai/agent/instructions/get` [.version-badge.new]#New# +
+a|`GET /api/rest/2.0/ai/agent/instructions/get`  +
 xref:spotter-agent-instructions.adoc#_get_agent_instructions[Retrieves the behavioral instructions] currently configured for the Spotter agent. +
 __Available on ThoughtSpot Cloud instances from 26.7.0.cl onwards.__
 |=====
@@ -128,5 +128,5 @@ If no instructions are configured, ThoughtSpot returns an empty value for the `i
 
 * For information about adding instructions at the data model level, see xref:spotter-nl-instructions.adoc[Data model instruction APIs].
 * For information about Spotter agent conversation workflows, see xref:spotter-agent-apis.adoc[AI APIs (Spotter Agent and Spotter 3)].
-* Visit the +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Fai%2Fset-agent-instructions" id="preview-in-playground">REST API v2.0 Playground</a>+++ to test the set agent instructions endpoint.
-* Visit the +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Fai%2Fget-agent-instructions" id="preview-in-playground">REST API v2.0 Playground</a>+++ to test the get agent instructions endpoint.
+* Visit the +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Fai%2Fset-agent-instructions">REST API v2.0 Playground</a>+++ to test the set agent instructions endpoint.
+* Visit the +++<a href="{{navprefix}}/restV2-playground?apiResourceId=http%2Fapi-endpoints%2Fai%2Fget-agent-instructions">REST API v2.0 Playground</a>+++ to test the get agent instructions endpoint.
diff --git a/modules/ROOT/pages/style-customization.adoc b/modules/ROOT/pages/style-customization.adoc
index 6fd53a71e..4b3288c8b 100644
--- a/modules/ROOT/pages/style-customization.adoc
+++ b/modules/ROOT/pages/style-customization.adoc
@@ -29,7 +29,7 @@ Custom CSS allows developers to override the default styles and UI element speci
 +
 To customize themes and variables in the CSS file, developers must know the basics of HTML and CSS framework and how to build custom themes. For more information, see xref:css-customization.adoc[Advanced customization with custom CSS]. 
 
-A xref:style-customization_tutorial.adoc[hands-on tutorial] is also available to learn how to test style customization capabilities using Visual Embed Playground.
+A xref:style-customization_tutorial-intro.adoc[hands-on tutorial] is also available to learn how to test style customization capabilities using Visual Embed Playground.
 
 == Scope of customization
 
diff --git a/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-intro.adoc b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-intro.adoc
new file mode 100644
index 000000000..c185b6e00
--- /dev/null
+++ b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-intro.adoc
@@ -0,0 +1,62 @@
+= Build a data-driven app with ThoughtSpot Embedded
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Build a Data-Driven App with ThoughtSpot Embedded
+:page-pageid: embed-data-driven-app__intro
+:page-description: A hands-on guide to embedding a ThoughtSpot Liveboard and Spotter in a host application, built around one real embedding project.
+
+A hands-on guide, built around one real embedding project.
+
+== The scenario
+
+Imagine you're a full-stack developer at SpotStay, a short-term rental company.
+Your team runs an internal portal that hosts use every day to check bookings, occupancy, and maintenance status across their listings.
+Right now, if a host wants to know why occupancy dropped for a listing, they file a ticket and wait for the data team to pull a report.
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/frame-video.mp4[width=100%,options="autoplay,loop"]
+--
+
+*Your mandate*: give hosts a self-serve view inside the portal they already use.
+
+* Embed a Liveboard so hosts see booking volume, occupancy rate, and average daily rate at a glance.
+* Embed Spotter so hosts can ask follow-up questions in plain language, such as "why did occupancy drop for our Austin listings this week?". Spotter answers without you building a custom query interface for every possible question.
+* Style and lock it down so it feels like part of the portal, not a third-party iframe bolted on the side.
+
+[NOTE]
+====
+Liveboard is an AI-augmented dashboard within ThoughtSpot.
+====
+
+This guide covers the build end to end, the same path you would take for your own app. It matches the SpotStay example on GitHub if you want to work through it in code.
+== Before you start
+
+* Confirm access to a ThoughtSpot instance (trial or org instance) with Developer or Admin privilege.
+* Add your app domain to the CSP and CORS allowlist (*Develop* > *Customizations* > *Security Settings*).
+* Confirm you have content to embed: a connected data warehouse, a data model, and a Liveboard.
+* Confirm Spotter is enabled on your instance. This is on by default for most Cloud instances. If you don't see it, ask your ThoughtSpot administrator to enable it.
+
+[NOTE]
+====
+Trial users: sample data is pre-connected. No data setup is required.
+====
+
+== Steps in this tutorial
+
+* xref:build-data-driven-app-with-tse-step-00.adoc[Get into the Developer Portal]
+//* xref:build-data-driven-app-with-tse-step-01.adoc[Set up the project]
+* xref:build-data-driven-app-with-tse-step-02.adoc[Get the base Liveboard rendering]
+* xref:build-data-driven-app-with-tse-step-03.adoc[Make it conversational]
+* xref:build-data-driven-app-with-tse-step-04.adoc[Style it to match the portal]
+* xref:build-data-driven-app-with-tse-step-05.adoc[Wire in a custom action]
+//* xref:build-data-driven-app-with-tse-step-06.adoc[Lock it down]
+* xref:build-data-driven-app-with-tse-troubleshooting.adoc[When it doesn't just work]
+* xref:build-data-driven-app-with-tse-summary.adoc[Where to go from here]
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/embed-data-driven-app/into-developer-portal">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-00.adoc b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-00.adoc
new file mode 100644
index 000000000..7e8adb7d4
--- /dev/null
+++ b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-00.adoc
@@ -0,0 +1,191 @@
+= Get into the Developer Portal
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Get into the Developer Portal
+:page-pageid: embed-data-driven-app__into-developer-portal
+:page-description: Find the Developer Playground, AI Theme Builder, SpotterCode, and Security Settings inside the ThoughtSpot Developer Portal.
+
+== Developer Portal
+Start in the Developer Portal, where every ID and configuration option you need lives.
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/dev-section.mp4[width=100%,options="autoplay,loop"]
+--
+
+. Log in to ThoughtSpot.
+. Click the *Develop* tab.
++
+[NOTE]
+====
+The *Develop* tab is visible only to users with Developer or Admin privilege.
+If you don't see it, ask your administrator to add you to a group with the *Has Developer privilege* permission.
+====
+
+From the Developer Portal you have access to:
+
+Developer Playground::
+An interactive sandbox where you configure the component you want to embed, see it render live, and copy out the exact SDK code.
+This is where every step starts.
+
+AI Theme Builder::
+The same live-render-and-copy pattern, but for styling.
+
+SpotterCode::
+An AI coding assistant built into the Playground and IDE that can generate and refine embed code from a plain-language prompt, and help theme it too.
+
+Security Settings::
+Where you allowlist your portal domain for CSP and CORS.
+Nothing renders without this.
+
+Customizations::
+Connectors, security settings, and webhooks for the broader ThoughtSpot instance.
+
+[IMPORTANT]
+====
+*Why this step matters:* skipping the Playground and hand-writing IDs from old tickets or Slack messages is the single most common source of "why is my embed blank" bugs.
+Grab every ID from the Playground, not from memory, and keep the terminology aligned with the ThoughtSpot objects you are embedding.
+====
+
+== Project setup
+
+Before you write a single line of embed code, four things need to be settled: the portal's domain needs to be allowlisted, you need the actual cluster hostname, you need to know which auth type you're building against, and you need the project files scaffolded.
+Skipping them is the fastest way to spend an afternoon debugging a CORS error and blaming the code.
+
+=== 1. Allowlist the portal domain
+
+In the ThoughtSpot UI, an admin or developer-privileged user goes to *Develop* > *Customizations* > *Security Settings* and adds your portal's domain (for example, `+https://spotstay.com+`) to the CSP and CORS allowlists.
+Without this, the browser blocks the embed regardless of how correct the code is.
+
+This is a one-time, admin-side setup step: it is not something the SDK or any tooling generates for you.
+Do this first so you are not debugging a CORS error later and assuming it is your code.
+
+=== 2. Get the cluster hostname
+
+Your ThoughtSpot instance lives at a specific hostname.
+For a Cloud instance, it looks like `spotstay.thoughtspot.cloud`.
+It's visible in the browser URL bar whenever you're logged into the ThoughtSpot UI. It is also listed under *Develop* > *REST API Playground*, which shows the fully qualified host that any API call must target.
+This is the value that goes into `thoughtSpotHost`. If you get it wrong, every embed on the page renders blank.
+
+=== 3. Choose an auth type
+
+The tutorial-friendly option is `AuthType.None`.
+It prompts for a ThoughtSpot login at runtime and is fine for local development.
+It is not what ships to hosts in production.
+
+The production-recommended pattern is Trusted Authentication: your own backend exchanges credentials for a token server-side, and hosts are signed in to the embed silently. No ThoughtSpot login screen, no separate ThoughtSpot license per user.
+Setting this up means standing up a small token-issuing endpoint on your side. It's a separate build from the embed code itself, and worth planning for before this goes past a demo.
+
+See xref:embed-authentication.adoc[Authentication] for the full option set, `AuthType.None`, `AuthType.Basic`, `AuthType.TrustedAuthToken`, `AuthType.TrustedAuthTokenCookieless`, and SSO-based flows, and which fits your setup.
+
+=== 4. Create the project structure
+
+With the domain allowed, the hostname in hand, and an auth type picked, create a small project folder.
+This matches the structure in the SpotStay example repo on GitHub:
+
+[source]
+----
+spotstay-embed/
+├── index.html   # Page shell + wrapper app navigation
+├── app.js       # All embedding code (SpotterEmbed, LiveboardEmbed, custom actions)
+└── styles.css   # Host app styling
+----
+
+Install the SDK:
+
+[source,shell]
+----
+npm install @thoughtspot/visual-embed-sdk
+----
+
+In `app.js`, import the components you'll use:
+
+[source,javascript]
+----
+import {
+  SpotterEmbed,
+  LiveboardEmbed,
+  AuthType,
+  init,
+  EmbedEvent,
+  HostEvent,
+  CustomActionTarget,
+  CustomActionPosition,
+} from '@thoughtspot/visual-embed-sdk';
+----
+
+[NOTE]
+====
+For a throwaway prototype, a CDN import works as well: keep <script type="module" src="app.js"> and import the SDK from the jsDelivr build instead of the npm package.
+Use npm if this is going into a real app.
+====
+
+`index.html` owns the page chrome, nav bar, container `div`, and nothing else.
+ThoughtSpot doesn't need to know anything about the rest of the portal:
+
+[source,html]
+----
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8" />
+  <title>SpotStay Portal</title>
+  <link rel="stylesheet" href="styles.css" />
+</head>
+<body>
+  <nav class="app-nav">
+    <span class="brand">SpotStay</span>
+    <button data-view="liveboard" class="nav-btn active">Dashboard</button>
+    <button data-view="spotter" class="nav-btn">Ask a question</button>
+  </nav>
+
+  <main>
+    <div id="ts-embed"></div>
+    <div id="detail-panel" class="hidden"></div>
+  </main>
+
+  <script type="module" src="app.js"></script>
+</body>
+</html>
+----
+
+`app.js` initializes the SDK once, near the top of the file.
+Always call `init()` before calling `render()` on any embed component:
+
+[source,javascript]
+----
+const tsURL = 'https://spotstay.thoughtspot.cloud';
+
+init({
+  thoughtSpotHost: tsURL,
+  authType: AuthType.None, // <1>
+});
+----
+<1> `AuthType.None` is fine while you're iterating locally: you get a one-time login popup and the session holds until it expires.
+Before this touches production, swap in a token-based `AuthType` such as `AuthType.TrustedAuthTokenCookieless`, so hosts are authenticated silently through your own backend, not a ThoughtSpot login popup.
+
+Then add tab-switching logic so the nav bar swaps embeds:
+
+[source,javascript]
+----
+const container = document.getElementById('ts-embed');
+
+document.querySelectorAll('.nav-btn').forEach((btn) => {
+  btn.addEventListener('click', () => {
+    document.querySelectorAll('.nav-btn').forEach((b) => b.classList.remove('active'));
+    btn.classList.add('active');
+    container.innerHTML = '';
+    btn.dataset.view === 'spotter' ? renderSpotter() : renderLiveboard();
+  });
+});
+
+renderLiveboard(); // default view on load
+----
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/embed-data-driven-app/intro">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/embed-data-driven-app/base-liveboard-rendering">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-01.adoc b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-01.adoc
new file mode 100644
index 000000000..7f41b78b8
--- /dev/null
+++ b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-01.adoc
@@ -0,0 +1,145 @@
+= Step 1: Set up the project
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Step 1: Set up the project
+:page-pageid: embed-data-driven-app__step-01
+:page-description: Allowlist your portal domain, get the cluster hostname, choose an auth type, and scaffold the project files.
+
+Before you write a single line of embed code, four things need to be settled: the portal's domain needs to be allowlisted, you need the actual cluster hostname, you need to know which auth type you're building against, and you need the project files scaffolded.
+Skipping them is the fastest way to spend an afternoon debugging a CORS error and blaming the code.
+
+== 1. Allowlist the portal domain
+
+In the ThoughtSpot UI, an admin or developer-privileged user goes to *Develop* > *Customizations* > *Security Settings* and adds your portal's domain (for example, `+https://spotstay.com+`) to the CSP and CORS allowlists.
+Without this, the browser blocks the embed regardless of how correct the code is.
+
+This is a one-time, admin-side setup step: not something the SDK or any tooling generates for you.
+Do this first, so you aren't debugging a CORS error later and assuming it's your code.
+
+== 2. Get the cluster hostname
+
+Your ThoughtSpot instance lives at a specific hostname.
+For a Cloud instance, it looks like `spotstay.thoughtspot.cloud`.
+It's visible in the browser URL bar whenever you're logged into the ThoughtSpot UI, and it's also listed under *Develop* > *REST API Playground*, which shows the fully qualified host any API call needs to target.
+This is the value that goes into `thoughtSpotHost`. If you get it wrong, every embed on the page renders blank.
+
+== 3. Choose an auth type
+
+The tutorial-friendly option is `AuthType.None`.
+It prompts for a ThoughtSpot login at runtime and is fine for local development.
+It is not what ships to hosts in production.
+
+The production-recommended pattern is Trusted Authentication: your own backend exchanges credentials for a token server-side, and hosts are signed in to the embed silently. No ThoughtSpot login screen, no separate ThoughtSpot license per user.
+Setting this up means standing up a small token-issuing endpoint on your side. It's a separate build from the embed code itself, and worth planning for before this goes past a demo.
+
+See xref:embed-authentication.adoc[Authentication] for the full option set, `AuthType.None`, `AuthType.Basic`, `AuthType.TrustedAuthToken`, `AuthType.TrustedAuthTokenCookieless`, and SSO-based flows, and which fits your setup.
+
+== 4. Create the project structure
+
+With the domain allowed, the hostname in hand, and an auth type picked, create a small project folder.
+This matches the structure in the SpotStay example repo on GitHub:
+
+[source]
+----
+spotstay-embed/
+├── index.html   # Page shell + wrapper app navigation
+├── app.js       # All embedding code (SpotterEmbed, LiveboardEmbed, custom actions)
+└── styles.css   # Host app styling
+----
+
+Install the SDK:
+
+[source,shell]
+----
+npm install @thoughtspot/visual-embed-sdk
+----
+
+In `app.js`, import the components you'll use:
+
+[source,javascript]
+----
+import {
+  SpotterEmbed,
+  LiveboardEmbed,
+  AuthType,
+  init,
+  EmbedEvent,
+  HostEvent,
+} from '@thoughtspot/visual-embed-sdk';
+----
+
+[NOTE]
+====
+For a throwaway prototype, the CDN import works just as well: swap the package import for a `<script type="module" src="app.js">` pointed at the jsDelivr build.
+Use npm if this is going into a real app.
+====
+
+`index.html` owns the page chrome, nav bar, container `div`, and nothing else.
+ThoughtSpot doesn't need to know anything about the rest of the portal:
+
+[source,html]
+----
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8" />
+  <title>SpotStay Portal</title>
+  <link rel="stylesheet" href="styles.css" />
+</head>
+<body>
+  <nav class="app-nav">
+    <span class="brand">SpotStay</span>
+    <button data-view="liveboard" class="nav-btn active">Dashboard</button>
+    <button data-view="spotter" class="nav-btn">Ask a question</button>
+  </nav>
+
+  <main>
+    <div id="ts-embed"></div>
+    <div id="detail-panel" class="hidden"></div>
+  </main>
+
+  <script type="module" src="app.js"></script>
+</body>
+</html>
+----
+
+`app.js` initializes the SDK once, near the top of the file.
+Always call `init()` before calling `render()` on any embed component:
+
+[source,javascript]
+----
+const tsURL = 'https://spotstay.thoughtspot.cloud';
+
+init({
+  thoughtSpotHost: tsURL,
+  authType: AuthType.None, // <1>
+});
+----
+<1> `AuthType.None` is fine while you're iterating locally: you get a one-time login popup and the session holds until it expires.
+Before this touches production, swap in a token-based `AuthType` such as `AuthType.TrustedAuthTokenCookieless`, so hosts are authenticated silently through your own backend, not a ThoughtSpot login popup.
+
+Then add tab-switching logic so the nav bar swaps embeds:
+
+[source,javascript]
+----
+const container = document.getElementById('ts-embed');
+
+document.querySelectorAll('.nav-btn').forEach((btn) => {
+  btn.addEventListener('click', () => {
+    document.querySelectorAll('.nav-btn').forEach((b) => b.classList.remove('active'));
+    btn.classList.add('active');
+    container.innerHTML = '';
+    btn.dataset.view === 'spotter' ? renderSpotter() : renderLiveboard();
+  });
+});
+
+renderLiveboard(); // default view on load
+----
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/embed-data-driven-app/step-00">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/embed-data-driven-app/step-02">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-02.adoc b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-02.adoc
new file mode 100644
index 000000000..c0d11dcaa
--- /dev/null
+++ b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-02.adoc
@@ -0,0 +1,62 @@
+= Get the base Liveboard rendering
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Get the base Liveboard rendering
+:page-pageid: embed-data-driven-app__base-liveboard-rendering
+:page-description: Embed the bookings Liveboard, and optionally a single visualization from it, using the Liveboard ID from the Developer Playground.
+
+
+Your first real milestone is getting the bookings Liveboard to render inside the portal. Grab the Liveboard ID from the Developer Playground and drop it straight in.
+
+[#import-liveboard-embed]
+== Step 1: Import the LiveboardEmbed component
+
+Find the file you want to embed the Liveboard in and import the `LiveboardEmbed` component:
+
+[source,javascript]
+----
+import { LiveboardEmbed } from '@thoughtspot/visual-embed-sdk/react';
+----
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/liveboard.mp4[width=100%,options="autoplay,loop"]
+--
+
+[#render-liveboard]
+== Step 2: Render the Liveboard
+
+First, decide which Liveboard you want to embed:
+
+. In the ThoughtSpot UI, go to *Develop* > *Visual Embed SDK Playground*.
+. Select *Liveboard Embed*, then select the Liveboard you want to embed.
+. The *Code snippet* section updates with the generated code. Copy it directly into your file, or extract only the Liveboard ID.
+
+[source,javascript]
+----
+function renderLiveboard() {
+    const liveboardEmbed = new LiveboardEmbed(container, {
+        frameParams: { width: '100%', height: '100%' },
+        liveboardId: '<%=liveboardGUID%>', // from the Playground
+    });
+
+    liveboardEmbed.on(EmbedEvent.LiveboardRendered, () => {
+        console.log('Liveboard rendered');
+    });
+
+    liveboardEmbed.render();
+}
+----
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/analytics.mp4[width=100%,options="autoplay,loop"]
+--
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/embed-data-driven-app/into-developer-portal">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/embed-data-driven-app/make-it-conversational">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-03.adoc b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-03.adoc
new file mode 100644
index 000000000..dfa93a9cb
--- /dev/null
+++ b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-03.adoc
@@ -0,0 +1,63 @@
+= Make it conversational
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Make it conversational
+:page-pageid: embed-data-driven-app__make-it-conversational
+:page-description: Embed Spotter below the Liveboard so hosts can ask follow-up questions in plain language.
+
+The Liveboard is up.
+Now for the second half of the ask: hosts can ask follow-up questions in their own words instead of hunting through Liveboard filters for "why."
+
+Find the file in which you want to embed Spotter and import the `SpotterEmbed` component:
+
+[source,javascript]
+----
+import { SpotterEmbed } from '@thoughtspot/visual-embed-sdk/react';
+----
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/spotter-embed-playground.mp4[width=100%,options="autoplay,loop"]
+--
+
+[#render-spotter]
+== Step 2: Render Spotter
+
+First, decide which data model hosts will query. Then:
+
+. In the ThoughtSpot UI, go to *Develop* > *Visual Embed SDK Playground*.
+. Select *Spotter Embed*, then select the data model you want.
+. The *Code snippet* section updates with the generated code. Copy it directly into your file, or extract just the Model ID.
+
+[source,javascript]
+----
+function renderSpotter() {
+    const spotterEmbed = new SpotterEmbed(container, {
+        frameParams: { width: '100%', height: '100%' },
+        worksheetId: '<your-model-guid>', // or 'auto_mode', see the following note
+    });
+
+    spotterEmbed.on(EmbedEvent.Init, () => console.log('Spotter initializing…'));
+    spotterEmbed.on(EmbedEvent.Load, () => console.log('Spotter loaded'));
+
+    spotterEmbed.render();
+}
+----
+
+[NOTE]
+====
+If your instance has Auto mode enabled, you don't need to lock Spotter to a single model. Set `worksheetId: 'auto_mode'` and let Spotter pick the right data source per question.
+====
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/working-spotter-embed.mp4[width=100%,options="autoplay,loop"]
+--
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/embed-data-driven-app/base-liveboard-rendering">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/embed-data-driven-app/style-to-match-portal">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-04.adoc b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-04.adoc
new file mode 100644
index 000000000..2917896a8
--- /dev/null
+++ b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-04.adoc
@@ -0,0 +1,54 @@
+= Style it to match the portal
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Style it to match the portal
+:page-pageid: embed-data-driven-app__style-to-match-portal
+:page-description: Use the AI Theme Builder to generate CSS variables and content strings that make the embed match the SpotStay portal.
+
+A Liveboard that looks like a different product breaks the self-serve, built-in feeling you are going for.
+Start in the AI Theme Builder (*Develop* > *Customizations* > *Theme Builder*). Upload brand guidelines or describe them, generate a theme, and then fine-tune colors in Manual Mode.
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/theme-builder-styling.mp4[width=100%,options="autoplay,loop"]
+--
+
+Exporting gives you a set of CSS variables that you can drop straight into `init()`:
+
+[source,javascript]
+----
+init({
+  thoughtSpotHost: tsURL,
+  authType: AuthType.None,
+  customizations: {
+    style: {
+      customCSS: {
+        variables: {
+          '--ts-var-button--primary-background': '#0B5FFF',
+          '--ts-var-root-color': '#1A1A1A',
+          '--ts-var-root-background': '#FFFFFF',
+          '--ts-var-spotter-prompt-background': '#F0F4FF',
+        },
+      },
+    },
+    content: {
+      strings: {
+        'Spotter': 'Ask SpotStay', //  matches the nav button copy
+      },
+    },
+  },
+});
+----
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/themed-app.mp4[width=100%,options="autoplay,loop"]
+--
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/embed-data-driven-app/make-it-conversational">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/embed-data-driven-app/wire-custom-action">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-05.adoc b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-05.adoc
new file mode 100644
index 000000000..ffb79058f
--- /dev/null
+++ b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-05.adoc
@@ -0,0 +1,67 @@
+= Wire in a custom action
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Wire in a custom action
+:page-pageid: embed-data-driven-app__wire-custom-action
+:page-description: Add a custom action so hosts can escalate a listing straight from the Liveboard into your internal ticketing tool.
+
+Your team does not want to only look at the data.
+When a host spots a listing with a maintenance issue dragging down occupancy, they want to escalate it into the internal ticketing tool without leaving the portal.
+That is a custom action.
+
+Modify the `renderLiveboard` function to include the custom action:
+
+[source,javascript]
+----
+function renderLiveboard() {
+    const liveboardEmbed = new LiveboardEmbed(container, {
+        frameParams: { width: '100%', height: '100%' },
+        liveboardId: '<your-liveboard-guid>',
+        customActions: [
+            {
+                name: 'Open listing',
+                id: 'open-listing',
+                target: CustomActionTarget.VIZ,
+                position: CustomActionPosition.PRIMARY,
+            },
+        ],
+    });
+
+    liveboardEmbed.on(EmbedEvent.LiveboardRendered, () => console.log('Liveboard rendered'));
+
+    liveboardEmbed.on(EmbedEvent.CustomAction, (payload) => {
+        if (payload.data.id === 'open-listing') {
+            handleCustomAction(payload.data);
+        }
+    });
+
+    liveboardEmbed.render();
+}
+
+function handleCustomAction(data) {
+    const panel = document.getElementById('detail-panel');
+    panel.classList.remove('hidden');
+    panel.innerHTML = `<pre>${JSON.stringify(data, null, 2)}</pre>`;
+    // In production: POST this payload to your ticketing API
+}
+----
+
+`CustomActionTarget` determines where the button appears — `VIZ`, `LIVEBOARD`, `SPOTTER`, or `ANSWER`. `CustomActionPosition` determines whether it appears in the primary toolbar or the overflow menu.
+
+[NOTE]
+====
+If you only want this action visible on the bookings Liveboard and not every Liveboard in the instance, use `metadataIds`, `groupId`, and `orgId` to scope it further.
+====
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/cbca.mp4[width=100%,options="autoplay,loop"]
+--
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/embed-data-driven-app/style-to-match-portal">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/embed-data-driven-app/troubleshooting">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-06.adoc b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-06.adoc
new file mode 100644
index 000000000..5134d12c4
--- /dev/null
+++ b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-step-06.adoc
@@ -0,0 +1,37 @@
+= Step 6: Lock it down
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Step 6: Lock it down
+:page-pageid: embed-data-driven-app__step-06
+:page-description: Hide and disable ThoughtSpot actions that don't make sense for external, non-power-user hosts.
+
+Hosts aren't ThoughtSpot power users, and you don't want them downloading raw exports or seeing sharing options that don't map to anything in your portal.
+
+[source,javascript]
+----
+import {
+  LiveboardEmbed,
+  Action, // <1>
+} from '@thoughtspot/visual-embed-sdk';
+
+const liveboardEmbed = new LiveboardEmbed(container, {
+  frameParams: { width: '100%', height: '100%' },
+  liveboardId: 'YOUR_LIVEBOARD_GUID',
+  hiddenActions: [Action.Download, Action.Share],
+  disabledActions: [Action.SpotIQAnalyze],
+  disabledActionReason: 'Not available on SpotStay accounts — contact IT to enable.',
+});
+----
+<1> `Action` must be imported from the SDK.
+
+`disabledActions` keeps the action visible but greyed out, with `disabledActionReason` as the tooltip explaining why.
+`hiddenActions` removes the action from the UI entirely.
+The full list of targetable actions is in the xref:Action.adoc[Action enum reference]. Worth a skim before deciding what to hide vs disable, since the two send very different signals to the end-user.
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/embed-data-driven-app/step-05">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/embed-data-driven-app/troubleshooting">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-summary.adoc b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-summary.adoc
new file mode 100644
index 000000000..002adbf22
--- /dev/null
+++ b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-summary.adoc
@@ -0,0 +1,62 @@
+= Where to go from here
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Where to go from here
+:page-pageid: embed-data-driven-app__summary
+:page-description: Wrap-up, next steps, and reference appendices for the SpotStay data-driven app embedding build.
+
+Two things are now in place: a host-scoped Liveboard and a conversational Spotter panel underneath it, both themed to match the SpotStay portal and locked down so hosts cannot download or share things that should not leave the tool.
+The pattern underneath does not change for whatever you build next — a Liveboard for a different team, a Spotter embed inside a mobile app, or a custom action that writes back to a different internal system.
+The full working version of this build is in the SpotStay example repo on GitHub if you want to see it end to end.
+
+Every build follows the same loop:
+
+. Grab the exact ID (Liveboard, model, or visualization) from the Developer Playground. Don't hand-type it.
+. Wire it into your existing app shell with the SDK.
+. Style it with CSS variables first. Use `rules_UNSTABLE` only when you have to.
+. Lock down actions before it reaches real users, not after.
+
+== Next steps
+
+* xref:embed-spotter.adoc[Embed Spotter]: full reference
+* xref:embed-pinboard.adoc[Embed a Liveboard]: full reference
+* xref:custom-actions-callback.adoc[Code-based custom actions]
+* xref:css-customization.adoc[CSS customization framework]
+* xref:embed-authentication.adoc[Authentication options]
+* xref:EmbedEvent.adoc[Embed events reference]
+* link:https://github.com/thoughtspot/developer-examples[Developer examples on GitHub, window=_blank]
+
+[#appendix-a]
+== Appendix A: Development environment
+
+* Use the latest Chrome build and keep DevTools open while developing: most embed issues show up as console errors first.
+* Disable the browser cache while iterating (*DevTools* > *Network* > *Disable cache*), or you'll keep debugging a stale build of `app.js`.
+* Blank embed → check the console, then confirm `thoughtSpotHost` is correct and reachable.
+
+[#appendix-b]
+== Appendix B: Security settings
+
+Configure all three settings under *Develop* > *Customizations* > *Security Settings* before anything renders on your domain:
+
+CSP visual embed hosts::
+The domain(s) allowed to embed ThoughtSpot. For example, `+http://localhost:8000+`.
+Use `*` only for local testing, never in production.
+
+CSP connect-src domains::
+Required for custom actions. The full URL (protocol and port) that a custom action or callback needs to reach.
+
+CORS allowlisted domains::
+Required with a token-based `AuthType`. The full URL of your embedding app.
+
+[NOTE]
+====
+In production, your app's domain typically needs to be in all three lists.
+====
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/embed-data-driven-app/troubleshooting">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next tutorial-pagination__done" href="{{navprefix}}/tutorials/walkthroughs">Done</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-troubleshooting.adoc b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-troubleshooting.adoc
new file mode 100644
index 000000000..44ac5e3d2
--- /dev/null
+++ b/modules/tutorials/pages/embed-data-driven-app/build-data-driven-app-with-tse-troubleshooting.adoc
@@ -0,0 +1,36 @@
+= When it doesn't just work
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: When it doesn't just work
+:page-pageid: embed-data-driven-app__troubleshooting
+:page-description: Troubleshooting patterns for blank embeds, styling that doesn't apply, and custom actions with unexpected payloads.
+
+It is worth including in the guide on purpose because it happens on every real project.
+
+== Scenario: blank embed, no errors in the UI
+
+This is almost always a CSP issue.
+Confirm the portal's domain is in the CSP visual embed hosts list (see xref:build-data-driven-app-with-tse-summary.adoc#appendix-b[Appendix B]), then check the browser console — most embed issues surface there first.
+
+== Scenario: styling changes don't apply
+
+Check whether you're using a CSS variable or a `rules_UNSTABLE` selector.
+Selectors can silently stop matching after a ThoughtSpot release. CSS variables are the more durable option and should be the default choice unless you need something a variable can't reach.
+
+== Scenario: custom action fires but the payload looks wrong
+
+Log `payload.data` in full before assuming the SDK is broken. It's usually a target or position mismatch (for example, an action scoped to `VIZ` that you expected on `LIVEBOARD`).
+
+== General checklist
+
+* No response or blank frame → check the CSP allowlist and `thoughtSpotHost` first.
+* Stale behavior after a code change → disable the browser cache (*DevTools* > *Network* > *Disable cache*) before debugging further.
+* Something looks right in the Playground but wrong in your app → check what parameters your app passes versus what the Playground generated.
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/embed-data-driven-app/wire-custom-action">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/embed-data-driven-app/summary">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/guided-walkthroughs.adoc b/modules/tutorials/pages/guided-walkthroughs.adoc
new file mode 100644
index 000000000..d52322473
--- /dev/null
+++ b/modules/tutorials/pages/guided-walkthroughs.adoc
@@ -0,0 +1,47 @@
+:toc!:
+:page-title: Walkthroughs
+:page-pageid: walkthroughs
+:page-description: ThoughtSpot hands-on guides for building an embedded data app
+
+[.non-link]
+++++
+<div class="walkthroughs-page">
+    <div class="radiance-bg">
+        <div class="blob blob-pink"></div>
+        <div class="blob blob-purple"></div>
+        <div class="blob blob-blue"></div>
+        <div class="blob blob-orange"></div>
+        <div class="blob blob-yellow"></div>
+        <div class="blob blob-purple-r"></div>
+        <div class="blob blob-teal"></div>
+        <div class="blob blob-wash-pink"></div>
+        <div class="blob blob-wash-blue"></div>
+    </div>
+    <div class="walkthroughs-hero-text">
+      <h1>Walkthroughs</h1>
+      <p>Hands-on guides that walk you through building intelligent experiences with ThoughtSpot Embedded.</p>
+    </div>
+    <div class="document-body-wrapper walkthroughs-body-wrapper">
+    <div class="row flex pb-10 tutorial-cards-row">
+    	<div class="col-md-6 flex">
+    <div class="boxDiv tutorialCard"><div>
+          <h5>Build faster with SpotterCode</h5>
+    			<p>Use our AI coding assistant to quickly embed ThoughtSpot Liveboards and Spotter in your application.
+    </p>
+    </div><div>
+    			<p><a class="tutorialCardCta" href="{{navprefix}}/tutorials/spottercode-embed/intro">Start</a></p>
+    </div>
+    	</div>
+    	</div>
+    	<div class="col-md-6 flex">
+        <div class="boxDiv tutorialCard"><div>
+    			<h5>Build a data-driven embedded app</h5>
+    			<p>Learn how to embed Liveboards and Spotter through a hands-on, real-world project.</p>
+    </div><div>
+    <p><a class="tutorialCardCta" href="{{navprefix}}/tutorials/embed-data-driven-app/intro">Start</a></p></div>
+    	</div>
+    	</div>
+    </div>
+    </div>
+</div>
+++++
diff --git a/modules/tutorials/pages/react-components/react-components_intro.adoc b/modules/tutorials/pages/react-components/react-components_intro.adoc
index de5cfe70e..611068d3a 100644
--- a/modules/tutorials/pages/react-components/react-components_intro.adoc
+++ b/modules/tutorials/pages/react-components/react-components_intro.adoc
@@ -1,6 +1,5 @@
 = ThoughtSpot React Components Tutorial
-:toc: true
-:toclevels: 2
+:toc!:
 
 :page-pageid: react-components__intro
 :description: This is a self-guided course on the ThoughtSpot Visual Embed SDK React Components
@@ -207,7 +206,8 @@ Again, this is simply to provide a simple example of how you will integrate rout
 === Other subdirectories and files
 The following lessons will cover the other files and the subdirectory structure used within the app to properly use the ThoughtSpot React components.
 
-'''
-
-xref:react-components_lesson-01.adoc[Next: 01 - Initializing ThoughtSpot Embed SDK >]
-
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/react-components/lesson-01">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/react-components/react-components_lesson-01.adoc b/modules/tutorials/pages/react-components/react-components_lesson-01.adoc
index 572cbcc5e..c7869dac0 100644
--- a/modules/tutorials/pages/react-components/react-components_lesson-01.adoc
+++ b/modules/tutorials/pages/react-components/react-components_lesson-01.adoc
@@ -1,6 +1,5 @@
 = Initializing ThoughtSpot Embed SDK
-:toc: true
-:toclevels: 2
+:toc!:
 
 :page-pageid: react-components__lesson-01
 :description: Initializing ThoughtSpot Embed SDK within React app
@@ -92,7 +91,9 @@ You'll notice in the app options for some of the most common set of configuratio
 }
 ----
 
-'''
-
-xref:react-components_intro.adoc[< Previous: Intro] | xref:react-components_lesson-02.adoc[Next: 02 - ThoughtSpot component pages >]
-
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/react-components/intro">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/react-components/lesson-02">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/react-components/react-components_lesson-02.adoc b/modules/tutorials/pages/react-components/react-components_lesson-02.adoc
index 6429ee6be..ac5bc392d 100644
--- a/modules/tutorials/pages/react-components/react-components_lesson-02.adoc
+++ b/modules/tutorials/pages/react-components/react-components_lesson-02.adoc
@@ -1,8 +1,7 @@
 = ThoughtSpot component pages
 :page-pageid: react-components__lesson-02
 :description: Build a page that returns a ThoughtSpot component
-:toc: true
-:toclevels: 2
+:toc!:
 
 == app/dashboard/[dashboardId]/page.tsx
 The link:https://github.com/thoughtspot/embed-example-react-app/blob/main/src/app/dashboard/%5BdashboardId%5D/page.tsx[first page we will build^] uses the `LiveboardEmbed` component to display any Liveboard, if passed an ID that matches existing content.
@@ -153,7 +152,9 @@ The React components have the same properties available as *props* of the compon
 
 The use of *props* for configuration options and xref:react-components_lesson-04.adoc[event handlers] is the biggest difference between the React components and the JavaScript Visual Embed SDK.
 
-
-'''
-
-xref:react-components_lesson-01.adoc[< Previous: 01 - Initializing ThoughtSpot Embed SDK] | xref:react-components_lesson-03.adoc[Next: 03 - Menus and other navigation elements >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/react-components/lesson-01">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/react-components/lesson-03">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/react-components/react-components_lesson-03.adoc b/modules/tutorials/pages/react-components/react-components_lesson-03.adoc
index 34ac53326..71e709db9 100644
--- a/modules/tutorials/pages/react-components/react-components_lesson-03.adoc
+++ b/modules/tutorials/pages/react-components/react-components_lesson-03.adoc
@@ -1,8 +1,7 @@
 = Menus and other navigation elements
 :page-pageid: react-components__lesson-03
 :description: Use REST APIs to create menus and other navigation elements
-:toc: true
-:toclevels: 2
+:toc!:
 
 The ThoughtSpot component page from the previous lesson was designed to display any Liveboard with a valid ID as part of the URL.
 
@@ -250,6 +249,9 @@ Spotter conversations are started against Models, so the set of UI components an
 
 The basic concepts from the entire tutorial apply regardless of which component you are using.
 
-'''
-
-xref:react-components_lesson-02.adoc[< Previous: 02 - ThoughtSpot component pages] | xref:react-components_lesson-04.adoc[Next: 04 - Event handling >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/react-components/lesson-02">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/react-components/lesson-04">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/react-components/react-components_lesson-04.adoc b/modules/tutorials/pages/react-components/react-components_lesson-04.adoc
index 15b0905ae..b864e5870 100644
--- a/modules/tutorials/pages/react-components/react-components_lesson-04.adoc
+++ b/modules/tutorials/pages/react-components/react-components_lesson-04.adoc
@@ -1,8 +1,7 @@
 = Event handling
 :page-pageid: react-components__lesson-04
 :description: React components attach event handlers differently than the JavaScript Visual Embed SDK
-:toc: true
-:toclevels: 2
+:toc!:
 
 The ThoughtSpot Visual Embed SDK provides a set of Embed events that can be listened to and handled via callback functions.
 
@@ -44,6 +43,9 @@ The `embedRef.current` syntax allows for issuing the `.trigger()` method of call
 
 You can use the same syntax to link other UI elements within the React page to the ThoughtSpot component without generating unnecessary and disruptive re-rendering.
 
-'''
-
-xref:react-components_lesson-03.adoc[< Previous: 03 - Menus and other navigation elements]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/react-components/lesson-03">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next tutorial-pagination__done" href="{{navprefix}}/tutorials/tutorials-overview">Done</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/rest-api/rest-api-intro.adoc b/modules/tutorials/pages/rest-api/rest-api-intro.adoc
index 50cc0aa39..a1857d2c6 100644
--- a/modules/tutorials/pages/rest-api/rest-api-intro.adoc
+++ b/modules/tutorials/pages/rest-api/rest-api-intro.adoc
@@ -1,6 +1,5 @@
 = ThoughtSpot REST API tutorials
-:toc: true
-:toclevels: 1
+:toc!:
 
 :page-title: ThoughtSpot REST API tutorials
 :page-pageid: rest-api__intro
@@ -40,6 +39,8 @@ image:images/tutorials/rest-api/open-tutorial-folder.png[Open folder in IDE]
 
 Now you're ready to begin the tutorial lessons.
 
-'''
-
-xref:rest-api_lesson-01.adoc[Next: 01 - REST API Overview >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/rest-api/lesson-01">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/rest-api/rest-api_lesson-01.adoc b/modules/tutorials/pages/rest-api/rest-api_lesson-01.adoc
index bf28715da..dfb69b6cb 100644
--- a/modules/tutorials/pages/rest-api/rest-api_lesson-01.adoc
+++ b/modules/tutorials/pages/rest-api/rest-api_lesson-01.adoc
@@ -1,6 +1,5 @@
 = What is a REST API?
-:toc: true
-:toclevels: 3
+:toc!:
 
 
 :page-pageid: rest-api__lesson-01
@@ -147,6 +146,9 @@ Note that the model and example will only be a singular form of the object that
 
 If you look at the image above, the response is described as an `Array<User>`, and so would be a JSON array containing any number of the `User` model from the example.
 
-'''
-
-xref:rest-api-intro.adoc[< Back: REST API tutorial intro] | xref:rest-api_lesson-02.adoc[Next: 02 - Simple Python Implementation of V2.0 REST API >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/rest-api/intro">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/rest-api/lesson-02">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/rest-api/rest-api_lesson-02.adoc b/modules/tutorials/pages/rest-api/rest-api_lesson-02.adoc
index 5e08236a5..09465f8d9 100644
--- a/modules/tutorials/pages/rest-api/rest-api_lesson-02.adoc
+++ b/modules/tutorials/pages/rest-api/rest-api_lesson-02.adoc
@@ -1,6 +1,5 @@
 = Simple Python implementation of V2.0 REST API
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-pageid: rest-api__lesson-02
 :description: A lesson on a simple implementation of the V2.0 using Python
@@ -315,6 +314,9 @@ You may have noticed many steps that are repeated each time for any given reques
 
 In the next lesson, we'll cover using a *library* that wraps most of these repeated steps, so that you can focus simply on the logic of your API workflows.
 
-'''
-
-xref:rest-api_lesson-01.adoc[< Previous: 01 - What is a REST API?] | xref:rest-api_lesson-03.adoc[Next: 03 - Complex REST API Workflows >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/rest-api/lesson-01">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/rest-api/lesson-03">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/rest-api/rest-api_lesson-03.adoc b/modules/tutorials/pages/rest-api/rest-api_lesson-03.adoc
index a201ea354..a205c4325 100644
--- a/modules/tutorials/pages/rest-api/rest-api_lesson-03.adoc
+++ b/modules/tutorials/pages/rest-api/rest-api_lesson-03.adoc
@@ -2,8 +2,7 @@
 
 :page-pageid: rest-api__lesson-03
 :description: Complex REST API Workflows
-:toc: true
-:toclevels: 1
+:toc!:
 
 == Get started
 The files for this tutorial are `api_training_python_2_begin.py` and `api_training_python_2_end.py`.
@@ -372,6 +371,9 @@ By moving hard-coded values into variables, you can develop reusable scripts to
 
 There are many link:https://github.com/thoughtspot/thoughtspot_rest_api_python/tree/main/examples_v2[existing examples^] of workflows that can be pieced together to accomplish any number of administration and integration tasks.
 
-'''
-
-xref:rest-api_lesson-02.adoc[< Back: 02 - Simple Python implementation of V2.0 REST API] | xref:rest-api_lesson-04.adoc[Next: 04 - Browser JavaScript REST API implementation >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/rest-api/lesson-02">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/rest-api/lesson-04">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/rest-api/rest-api_lesson-04.adoc b/modules/tutorials/pages/rest-api/rest-api_lesson-04.adoc
index abe1b6e96..effe6ca22 100644
--- a/modules/tutorials/pages/rest-api/rest-api_lesson-04.adoc
+++ b/modules/tutorials/pages/rest-api/rest-api_lesson-04.adoc
@@ -1,6 +1,5 @@
 = 04 - Browser JavaScript REST API implementation
-:toc: true
-:toclevels: 1
+:toc!:
 
 :page-pageid: rest-api__lesson-04
 :description: Browser JavaScript REST API implementation
@@ -308,6 +307,9 @@ There is a link:https://github.com/thoughtspot/rest-api-sdk/tree/release/sdks/ty
 
 It is up to you to determine if the extra rigor and structure of the Typescript REST API SDK is helpful in the projects you build, or if a simple light implementation of a few of the REST API calls within a simple set of functions will suffice.
 
-'''
-
-xref:rest-api_lesson-03.adoc[< Back: 03 - Complex Workflows in Python ]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/rest-api/lesson-03">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next tutorial-pagination__done" href="{{navprefix}}/tutorials/tutorials-overview">Done</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/spotter/spotter-in-custom-chatbot.adoc b/modules/tutorials/pages/spotter/spotter-in-custom-chatbot.adoc
index 8385d86b4..6156b7802 100644
--- a/modules/tutorials/pages/spotter/spotter-in-custom-chatbot.adoc
+++ b/modules/tutorials/pages/spotter/spotter-in-custom-chatbot.adoc
@@ -1,6 +1,5 @@
 = Integrate Spotter into your chatbot
-:toc: true
-:toclevels: 1
+:toc!:
 
 :page-title: Integrate Spotter into your own Chatbot
 :page-pageid: spotter__integrate-into-chatbot
diff --git a/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-intro.adoc b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-intro.adoc
new file mode 100644
index 000000000..8aeac7500
--- /dev/null
+++ b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-intro.adoc
@@ -0,0 +1,116 @@
+= Embedding ThoughtSpot with SpotterCode
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Embedding ThoughtSpot with SpotterCode
+:page-pageid: spottercode-embed__intro
+:page-description: Use SpotterCode, ThoughtSpot's AI coding assistant, to accelerate embedding ThoughtSpot Liveboards and Spotter in your application.
+
+
+You’re a full-stack developer at SpotStay, a short-term rental platform.
+Your goal is to give hosts a self-serve analytics view inside the SpotStay host portal, something hosts can open to see how their listings are performing, without filing a support ticket or waiting on a data team.
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/frame-video.mp4[width=100%,options="autoplay,loop"]
+--
+
+
+Two things are on your list:
+
+* Embed a Liveboard so hosts can see occupancy, revenue, and booking trends for their own listings.
+* Embed Spotter so hosts can ask follow-up questions in plain language, such as “why did my weekend bookings drop in March?”, without you building a custom query interface.
+
+You already know the Visual Embed SDK. What you don’t want to do is keep tabbing out to documentation for every parameter, event, and configuration option. That’s the problem SpotterCode solves for any embedding task.
+
+SpotterCode is the ThoughtSpot developer agent, purpose-built for embedded use cases. It answers from the current ThoughtSpot documentation and generates production-ready code tailored to your framework, so you spend less time moving between documentation and your IDE.
+
+[NOTE]
+====
+Liveboard is an AI-augmented dashboard within ThoughtSpot.
+====
+
+[#before-you-start]
+== Before you start: configure your ThoughtSpot instance
+
+Before any embed renders, two things must be true: your SpotStay portal domain is allowed to connect, and the SDK knows which ThoughtSpot cluster to use. Skipping this step is the most common reason a first embed shows a blank frame instead of a Liveboard.
+
+[#allowlist-domain]
+=== 1. Allowlist the portal domain
+
+In the ThoughtSpot UI, an admin or developer-privileged user navigates to *Develop* > *Customizations* > *Security Settings* and adds the SpotStay portal domain (for example, `+https://portal.spotstay.com+`) to the CSP and CORS allowlists. Without this, the browser blocks the embed regardless of how correct the code is.
+
+[NOTE]
+====
+This is a one-time setup step. It's an admin and configuration task, not something SpotterCode generates. Complete this before you write a single line of embed code, so you aren't debugging a CORS error and assuming it's your code.
+====
+
+[#get-cluster-hostname]
+=== 2. Get the cluster hostname
+
+Your SpotStay ThoughtSpot instance lives at a specific hostname. For a Cloud instance, it looks like `spotstay.thoughtspot.cloud`. If you're not sure where to find it, ask SpotterCode:
+
+[source,text]
+----
+"How do I find the hostname of my ThoughtSpot application instance?"
+----
+
+[#choose-auth-type]
+=== 3. Choose an authentication type
+
+The tutorial-friendly option is `AuthType.None`: it prompts for a ThoughtSpot login at runtime and is fine for local development. It is not what ships to production. Before you decide, ask SpotterCode to walk you through the real options:
+
+[source,text]
+----
+"What authentication types does the Visual Embed SDK support, and which one is recommended for a production embed with external users?"
+----
+
+Here's what you'll get back: `AuthType.None` is for testing only. Trusted Authentication (server-side token exchange) is the recommended pattern for production. It suits external, non-ThoughtSpot-licensed users such as SpotStay's hosts.
+
+[#initialize-sdk]
+=== 4. Initialize the SDK once, at the app root
+
+Prompt for the `init` call before touching any individual embed component:
+
+[source,text]
+----
+"Show me how to initialize the Visual Embed SDK in a React app using Trusted Authentication, with a fallback note on AuthType.None for local development."
+----
+
+[source,javascript]
+----
+// Framework-agnostic. Call this once at your app entry point (React, Vue, or vanilla JS).
+
+import { init, AuthType } from '@thoughtspot/visual-embed-sdk';
+
+init({
+    thoughtSpotHost: 'https://spotstay.thoughtspot.cloud',
+    authType: AuthType.TrustedAuthTokenCookieless, // <1>
+    // authType: AuthType.None,                    // <2>
+});
+----
+<1> Production: server-issued token. See xref:embed-authentication.adoc[Authentication] for setup.
+<2> Local development only. Do not ship this.
+
+== Steps in this tutorial
+
+. xref:build-embed-app-with-spottercode-step-01.adoc[Set up SpotterCode]
+. xref:build-embed-app-with-spottercode-step-02.adoc[Embed the Liveboard view]
+. xref:build-embed-app-with-spottercode-step-03.adoc[Embed Spotter]
+. xref:build-embed-app-with-spottercode-step-04.adoc[Troubleshooting]
+. xref:build-embed-app-with-spottercode-summary.adoc[Summary]
+
+////
+. xref:build-embed-app-with-spottercode-step-05.adoc[Summary]
+. xref:build-embed-app-with-spottercode-step-06.adoc[Wire it to real data]
+. xref:build-embed-app-with-spottercode-step-07.adoc[When it doesn't just work]
+////
+
+
+
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/spottercode-embed/set-up-spottercode">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-01.adoc b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-01.adoc
new file mode 100644
index 000000000..9bf5d2255
--- /dev/null
+++ b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-01.adoc
@@ -0,0 +1,67 @@
+= Set up SpotterCode
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Set up SpotterCode
+:page-pageid: spottercode-embed__set-up-spottercode
+:page-description: Connect SpotterCode to your IDE via MCP and verify it has access to the ThoughtSpot developer docs and REST API reference.
+
+This guide uses a Claude Code environment as an example. The setup takes one of two paths, depending on your Claude account.
+
+[#path-claude-web]
+=== If you have Claude AI (web) access
+
+. In Claude AI, go to *Customize* > *Connectors*.
+. Click the *+* icon and select *Add custom connector*.
+. Enter the server URL:
++
+[source,text]
+----
+https://spottercode.thoughtspot.app/mcp
+----
+. Click *Add*.
++
+This syncs to Claude Code automatically; no separate configuration is needed.
+
+[#path-claude-code-only]
+=== If you have Claude Code only
+
+Run the following command from the CLI in your project directory:
+
+[source,bash]
+----
+claude mcp add --transport http SpotterCode https://spottercode.thoughtspot.app/mcp
+----
+
+[#verify-connection]
+=== Verify the connection
+
+Open a chat in your project and ask a scoped question to confirm SpotterCode is connected:
+
+[source,text]
+----
+"Use SpotterCode to confirm you have access to the ThoughtSpot developer docs and REST API reference."
+----
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/spottercode-connector.mp4[width=100%,options="autoplay,loop"]
+--
+
+
+[#other-editors]
+=== Cursor and VS Code
+
+The same pattern applies in Cursor or VS Code:
+
+* *Cursor*: One-click install from the Cursor Marketplace, or add the server URL in *Settings* > *Tools and MCP*.
+* *VS Code*: Add the server via the Extensions view or your workspace `mcp.json`, with GitHub Copilot (or a similar chat agent extension) installed.
+
+The prompting workflow in the following steps is identical once either editor is connected.
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/spottercode-embed/intro">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/spottercode-embed/embed-liveboard-view">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-02.adoc b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-02.adoc
new file mode 100644
index 000000000..43e2db81a
--- /dev/null
+++ b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-02.adoc
@@ -0,0 +1,106 @@
+= Embed the Liveboard view
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Embed the Liveboard view
+:page-pageid: spottercode-embed__embed-liveboard-view
+:page-description: Prompt SpotterCode to generate the React code for embedding a ThoughtSpot Liveboard.
+
+With `init()` in place, the first goal is to render a host's listing-performance Liveboard inside the SpotStay portal. Write a specific prompt rather than a vague one:
+
+[source,text]
+----
+"I want to embed a ThoughtSpot Liveboard showing listing performance in my React app.
+Use the available tools to get this information and generate the embed code."
+----
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/lb-embed-prompt.mp4[width=100%,options="autoplay,loop"]
+--
+
+What SpotterCode needs to complete the task:
+
+* The ThoughtSpot host URL (already set in `init()`)
+* The Liveboard GUID (retrieved from the Developer Playground)
+* Confirmation of the authentication type you're already using
+
+[source,javascript]
+----
+import { LiveboardEmbed, useEmbedRef } from '@thoughtspot/visual-embed-sdk/react';
+
+const HostDashboard = () => {
+    const embedRef = useEmbedRef();
+
+    return (
+        <LiveboardEmbed
+            ref={embedRef}
+            liveboardId="<your-spotstay-listing-liveboard-guid>"
+        />
+    );
+};
+
+export default HostDashboard;
+----
+
+[#make-it-host-specific]
+== Make it host-specific
+
+A shared Liveboard shows every listing on the platform. You need each host to see only their own. Prompt for a runtime filter scoped to the logged-in host:
+
+[source,text]
+----
+"Show a code example for embedding a Liveboard with a runtime filter where host_id equals
+the logged-in user's ID, using the Visual Embed SDK for React."
+----
+
+[source,javascript]
+----
+import {
+    LiveboardEmbed,
+    useEmbedRef,
+    HostEvent,
+    RuntimeFilterOp,
+} from '@thoughtspot/visual-embed-sdk/react';
+
+const HostDashboard = ({ hostId }) => {
+    const embedRef = useEmbedRef();
+
+    const onLiveboardRendered = () => {
+        embedRef.current.trigger(HostEvent.UpdateRuntimeFilters, [
+            {
+                columnName: 'host_id',
+                operator: RuntimeFilterOp.EQ,
+                values: [hostId],
+            },
+        ]);
+    };
+
+    return (
+        <LiveboardEmbed
+            ref={embedRef}
+            liveboardId="spotstay-listing-performance-lb"
+            onLiveboardRendered={onLiveboardRendered}
+        />
+    );
+};
+
+export default HostDashboard;
+----
+
+[NOTE]
+====
+Your prompt has to carry business context ("the logged-in user's ID") that isn't in any documentation. SpotterCode generates the mechanism; you supply the SpotStay-specific meaning.
+====
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/analytics.mp4[width=100%,options="autoplay,loop"]
+--
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/spottercode-embed/set-up-spottercode">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/spottercode-embed/embed-spotter">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-03.adoc b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-03.adoc
new file mode 100644
index 000000000..6278b2000
--- /dev/null
+++ b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-03.adoc
@@ -0,0 +1,109 @@
+= Embed Spotter
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Embed Spotter
+:page-pageid: spottercode-embed__embed-spotter
+:page-description: Prompt SpotterCode to embed Spotter beneath the Liveboard, hide actions for external users, and find the Model ID.
+
+The Liveboard is in place. Now for the second use case: hosts can ask follow-up questions in their own words instead of hunting through Liveboard filters.
+
+[source,text]
+----
+"I want to embed ThoughtSpot Spotter below the Liveboard so hosts can ask follow-up
+questions about their listing data. Use the available tools to get the information
+and generate the code."
+----
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/add-spotter.mp4[width=100%,options="autoplay,loop"]
+--
+
+[source,javascript]
+----
+import { SpotterEmbed } from '@thoughtspot/visual-embed-sdk/react';
+
+const HostInsights = ({ hostModelId }) => {
+    return (
+        <SpotterEmbed
+            worksheetId={hostModelId}
+            hideSampleQuestions={false}
+        />
+    );
+};
+
+export default HostInsights;
+----
+
+Drop `HostInsights` directly beneath `HostDashboard` on the same portal page; no separate authentication flow is required.
+
+[#lock-down-for-external-users]
+=== Step 1: Lock it down for external users
+
+Hosts aren't internal ThoughtSpot users. You don't want them downloading raw data or seeing ThoughtSpot-native sharing options that don't make sense in the SpotStay portal.
+
+[source,text]
+----
+"How do I hide the Download and Share actions on an embedded Liveboard, and disable
+SpotIQ analysis with a custom message, using the Visual Embed SDK?"
+----
+
+[source,javascript]
+----
+<LiveboardEmbed
+    ref={embedRef}
+    liveboardId="spotstay-listing-performance-lb"
+    onLiveboardRendered={onLiveboardRendered}
+    hiddenActions={[Action.Download, Action.Share]}
+    disabledActions={[Action.SpotIQAnalyze]}
+    disabledActionReason="Not available on host accounts"
+/>
+----
+
+[#wire-to-real-data]
+=== Step 2: Wire it to real data
+
+Everything so far used a placeholder Model ID. You still need the actual Model ID for SpotStay's listing data, and you do not need to dig through the ThoughtSpot UI by hand.
+If SpotterCode is not authenticated to your cluster, ask it to generate the REST API
+request and run the request yourself:
+
+[source,text]
+----
+"Generate a REST API request to find the Model ID for a data object named
+'SpotStay Listings', using ThoughtSpot REST API v2."
+----
+
+If SpotterCode is authenticated to your cluster, ask it to run the lookup directly:
+
+[source,text]
+----
+"Find the Model ID for a data object named 'SpotStay Listings' on my cluster."
+----
+
+SpotterCode connects as you, runs the lookup, and returns the ID — no copying `curl` commands, no switching tabs. The same pattern works for finding Liveboard GUIDs, checking CORS settings, or inspecting any metadata on your cluster.
+
+If you prefer to run the lookup manually, use the following REST API request:
+
+[source,bash]
+----
+curl -X POST 'https://spotstay.thoughtspot.cloud/api/rest/2.0/metadata/search' \
+  -H 'Authorization: Bearer <your_access_token>' \
+  -H 'Content-Type: application/json' \
+  -d '{
+    "metadata": [{ "type": "LOGICAL_TABLE", "name_pattern": "SpotStay Listings" }],
+    "record_size": 5
+  }'
+----
+
+
+[div videoContainer]
+--
+video::./images/mktng-tutorials/working-spotter-embed.mp4[width=100%,options="autoplay,loop"]
+--
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/spottercode-embed/embed-liveboard-view">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/spottercode-embed/troubleshooting">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-04.adoc b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-04.adoc
new file mode 100644
index 000000000..ecb188416
--- /dev/null
+++ b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-04.adoc
@@ -0,0 +1,66 @@
+= Troubleshooting
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Troubleshooting
+:page-pageid: spottercode-embed__troubleshooting
+:page-description: Fix outdated SDK versions, vague prompts, and other common SpotterCode issues.
+
+These scenarios come up on almost every real project.
+
+[#outdated-sdk-version]
+== Scenario: outdated SDK version
+
+Your project was scaffolded months ago and still points to an older version of the Visual Embed SDK. You ask for a feature that exists only in a newer release, and the generated code does not run.
+
+*Fix:* Name the version explicitly and ask what changed.
+
+[source,text]
+----
+"Update my Liveboard embed code to the latest Visual Embed SDK version and list any
+breaking changes from my current version in the documentation."
+----
+
+[#vague-prompts]
+== Scenario: vague follow-up gets a vague answer
+
+`"Make the Liveboard better"` will not produce useful code. Keep prompts scoped to one outcome.
+
+[cols="1,3", options="header"]
+|===
+| Approach | Prompt
+
+| *Avoid*
+| `"Can you customize the embed?"`
+
+| *Use instead*
+| `"Fetch the documentation for LiveboardEmbed and summarize the available customization options."` +
+Then pick one option and ask for it by name.
+|===
+
+[#troubleshooting-checklist]
+== General troubleshooting checklist
+
+[cols="2,3", options="header"]
+|===
+| Symptom | Action
+
+| No response or page not loading
+| Confirm SpotterCode is enabled for this project and the MCP server is reachable.
+
+| Slow responses
+| Break the request into smaller, sequential prompts instead of one large request.
+
+| The response looks wrong
+| Check which tool the agent called. Refine the prompt for specificity before assuming the tool is broken.
+
+| The agent infers SpotStay business logic incorrectly
+| You must specify anything that is not in the documentation or the SDK. Do not ask SpotterCode to infer SpotStay-specific business logic.
+|===
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/spottercode-embed/embed-spotter">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/spottercode-embed/summary">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-05.adoc b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-05.adoc
new file mode 100644
index 000000000..fb4c6bb19
--- /dev/null
+++ b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-05.adoc
@@ -0,0 +1,39 @@
+= Step 5: Lock it down for external users
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Step 5: Lock it down for external users
+:page-pageid: spottercode-embed__step-05
+:page-description: Prompt SpotterCode to hide Download and Share actions and disable SpotIQ analysis for external, non-ThoughtSpot users.
+
+Hosts aren't internal ThoughtSpot users.
+You don't want them downloading raw data or seeing ThoughtSpot-native sharing options that don't make sense in the SpotStay portal.
+
+[source, text]
+----
+How do I hide the Download and Share actions on an embedded Liveboard,
+and disable SpotIQ analysis with a custom message, using the Visual Embed SDK?
+----
+
+SpotterCode returns:
+
+[source,javascript]
+----
+import { Action } from '@thoughtspot/visual-embed-sdk';
+
+<LiveboardEmbed
+  ref={embedRef}
+  liveboardId="YOUR_LIVEBOARD_GUID"
+  onLiveboardRendered={onLiveboardRendered}
+  hiddenActions={[Action.Download, Action.Share]}
+  disabledActions={[Action.SpotIQAnalyze]}
+  disabledActionReason="Not available on host accounts"
+/>
+----
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/spottercode-embed/step-04">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/spottercode-embed/step-06">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-06.adoc b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-06.adoc
new file mode 100644
index 000000000..e95f57857
--- /dev/null
+++ b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-06.adoc
@@ -0,0 +1,39 @@
+= Step 6: Wire it to real data
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Step 6: Wire it to real data
+:page-pageid: spottercode-embed__step-06
+:page-description: Use SpotterCode to generate a REST API request that looks up the real worksheet ID for your data.
+
+Everything so far used a placeholder worksheet ID.
+You still need the actual worksheet ID for SpotStay's listing data — no need to dig through the ThoughtSpot UI by hand.
+
+[source,text]
+----
+Generate a REST API request to find the worksheet ID for a data object
+named 'SpotStay Listings', using ThoughtSpot REST API v2.
+----
+
+SpotterCode returns:
+
+[source,shell]
+----
+curl -X POST 'https://your-thoughtspot-host/api/rest/2.0/metadata/search' \
+  -H 'Authorization: Bearer <your_access_token>' \
+  -H 'Content-Type: application/json' \
+  -d '{
+    "metadata": [{ "type": "LOGICAL_TABLE", "name_pattern": "SpotStay Listings" }],
+    "record_size": 5
+  }'
+----
+
+Replace `your-thoughtspot-host` with your instance hostname and `<your_access_token>` with a valid bearer token.
+The response includes the model GUID. Copy it into your `SpotterEmbed` and `LiveboardEmbed` components.
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/spottercode-embed/step-05">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/spottercode-embed/step-07">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-07.adoc b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-07.adoc
new file mode 100644
index 000000000..a6c53e6d9
--- /dev/null
+++ b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-step-07.adoc
@@ -0,0 +1,44 @@
+= Step 7: When it doesn't just work
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Step 7: When it doesn't just work
+:page-pageid: spottercode-embed__step-07
+:page-description: Troubleshooting patterns for outdated SDK versions, vague prompts, and other common SpotterCode issues.
+
+Worth building into the guide on purpose, because it happens on every real project.
+
+== Scenario: outdated SDK version
+
+Your project was scaffolded months ago and still points at an older Visual Embed SDK version.
+You ask for a feature that only exists in a newer release, and the generated code doesn't run.
+
+Fix: name the version explicitly and ask what changed.
+
+[source]
+----
+Update my Liveboard embed code to the latest Visual Embed SDK version
+and list any breaking changes from my current version in the documentation.
+----
+
+== Scenario: vague follow-up gets a vague answer
+
+"Make the dashboard better" will not produce useful code.
+Keep prompts scoped to one outcome:
+
+* Not: "Can you customize the embed?"
+* Instead: "Fetch the documentation for `LiveboardEmbed` and summarize the available customization options." Then pick one and ask for it by name.
+
+== General troubleshooting checklist
+
+* No response or not loading → confirm SpotterCode is enabled for this project and the MCP server is reachable.
+* Slow responses → break the ask into smaller, sequential prompts instead of one large request.
+* Response looks wrong → check which tool the agent actually called. Refine the prompt for specificity before assuming the tool is broken.
+* Don't ask it to infer SpotStay's business logic. Anything not in the docs or the SDK, you still have to specify yourself.
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/spottercode-embed/step-06">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/spottercode-embed/summary">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-summary.adoc b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-summary.adoc
new file mode 100644
index 000000000..ae0a60fc3
--- /dev/null
+++ b/modules/tutorials/pages/spottercode-embed/build-embed-app-with-spottercode-summary.adoc
@@ -0,0 +1,32 @@
+= Summary
+:toc!:
+:linkattrs:
+:sectanchors:
+:page-title: Summary
+:page-pageid: spottercode-embed__summary
+:page-description: Wrap-up and next steps after building a host-scoped Liveboard and Spotter embed with SpotterCode.
+
+You shipped two use cases: a host-scoped Liveboard and a conversational Spotter panel, both locked down and wired to real data. The pattern underneath did not change between them. It also does not change for whatever you build next, whether that is a Liveboard for property hosts, a Spotter embed in a mobile app, or a REST job that syncs booking data on a schedule.
+
+Every task follows the same loop:
+
+. Write one specific, terminology-precise prompt that names the exact ThoughtSpot object and the SDK you're using.
+. Let SpotterCode pull the real, current documentation reference and generate code shaped to your project.
+. Review it. You are checking the code, not accepting it as-is.
+. If something is off, narrow the prompt before assuming the tool cannot do it.
+
+== Next steps
+
+* xref:spottercode.adoc[SpotterCode reference]
+* xref:embed-spotter.adoc[Embed Spotter]: full reference
+* xref:embed-pinboard.adoc[Embed a Liveboard]: full reference
+* xref:embed-authentication.adoc[Authentication options]
+* xref:build-data-driven-app-with-tse-intro.adoc[Build a data-driven app with ThoughtSpot Embedded]
+* link:https://github.com/thoughtspot/developer-examples[Developer examples on GitHub, window=_blank]
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/spottercode-embed/troubleshooting">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next tutorial-pagination__done" href="{{navprefix}}/tutorials/walkthroughs">Done</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/style-customization/style-customization_tutorial-intro.adoc b/modules/tutorials/pages/style-customization/style-customization_tutorial-intro.adoc
new file mode 100644
index 000000000..5b20011d4
--- /dev/null
+++ b/modules/tutorials/pages/style-customization/style-customization_tutorial-intro.adoc
@@ -0,0 +1,32 @@
+= Style customization tutorial
+:toc!:
+
+:page-title: Visual Embed SDK Style customization tutorial
+:page-pageid: style-customization__intro
+:page-description: This is a self-guided course on style customization of the Visual Embed SDK components
+
+One of the main advantages of ThoughtSpot Embedded is the control over the styling and UI elements provided by the Visual Embed SDK.
+
+This tutorial provides a walkthrough of customizable elements of ThoughtSpot UI and essential steps to style your embedded ThoughtSpot content.
+
+ThoughtSpot allows customizing the following aspects of its UI:
+
+1. Large component elements
+2. CSS styles
+3. Text strings and icon replacement
+4. Menu items
+
+== Steps in this tutorial
+
+. xref:style-customization_tutorial-step-01.adoc[Getting started]
+. xref:style-customization_tutorial-step-02.adoc[Large component elements]
+. xref:style-customization_tutorial-step-03.adoc[CSS styles]
+. xref:style-customization_tutorial-step-04.adoc[Text strings and icon replacement]
+. xref:style-customization_tutorial-step-05.adoc[Menu items]
+. xref:style-customization_tutorial-step-06.adoc[Conclusion]
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/style-customization/step-01">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/style-customization/style-customization_tutorial-step-01.adoc b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-01.adoc
new file mode 100644
index 000000000..b4de30530
--- /dev/null
+++ b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-01.adoc
@@ -0,0 +1,100 @@
+= Step 1: Getting started
+:toc!:
+
+:page-title: Step 1: Getting started
+:page-pageid: style-customization__step-01
+:page-description: Use the Visual Embed SDK Playground to demonstrate customizations in a live environment.
+
+This tutorial uses the Visual Embed SDK Playground built into every ThoughtSpot instance to demonstrate various customizations in a live environment.
+
+We suggest copying the code into a text editor or IDE such as Visual Studio Code to make it easier to work on the examples, and then copy the values back into the code editor within the Playground.
+
+To get started:
+
+. Select the `Liveboard` component to embed in the Playground:
++
+[.widthAuto]
+[.bordered]
+image:images/tutorials/style-customization/choose-liveboard-embed.png[Choose LiveboardEmbed component]
+. Select the *(Sample) Sales Performance* Liveboard, which should be available on all instances, including the Free Trial setup.
++
+[.widthAuto]
+[.bordered]
+image:images/tutorials/style-customization/choose-liveboard.png[Choose Liveboard]
+
+. If you do not have "(Sample) Sales Performance" available, use any Liveboard that you have access to.
++
+You should see the following code in the code panel of the Playground page.
+
+. Copy at any point down to `.render();`:
++
+[source,javascript]
+----
+// Import ThoughtSpot SDK
+import {
+    init,
+    LiveboardEmbed,
+    Action,
+    RuntimeFilterOp,
+    EmbedEvent,
+    AuthType,
+    HostEvent
+} from "@thoughtspot/visual-embed-sdk";
+import "./styles.css";
+import {
+    getTokenService
+} from "./tokenService";
+
+// Use prefetch to load static resources early and optimize response time.
+// Call init early to complete authentication during app load for better performance.
+init({
+   thoughtSpotHost:
+   /*param-start-hosturl*/"https://embed-1-do-not-delete.thoughtspotstaging.cloud" /*param-end-hosturl*/,
+   /*param-start-styleCustomization*//*param-end-styleCustomization*/
+    authType: AuthType.TrustedAuthTokenCookieless,
+    getAuthToken: getTokenService,
+    disableTokenVerification: true,
+});
+
+// Instantiate class for embedding a Liveboard
+const embed = new LiveboardEmbed("#your-own-div", {
+    frameParams: {},
+    /*param-start-liveboardId*/liveboardId: "d084c256-e284-4fc4-b80c-111cb606449a" /*param-end-liveboardId*/
+    /*param-start-activeTabId*//*param-end-activeTabId*/
+    /*param-start-liveboardFullHeight*//*param-end-liveboardFullHeight*/
+    /*param-start-customizeLiveboardHeader*//*param-end-customizeLiveboardHeader*/
+    /*param-start-hideLiveboardHeader*//*param-end-hideLiveboardHeader*/
+    /*param-start-runtimeFiltersAndParameters*//*param-end-runtimeFiltersAndParameters*/
+    /*param-start-modifyActions*//*param-end-modifyActions*/
+});
+
+hideNoDataImage();
+showErrorBanner('none');
+
+embed
+    // Register event listeners
+    .on(EmbedEvent.Init, showLoader)
+    .on(EmbedEvent.Load, hideLoader)
+    /*param-start-customActionHandle*//*param-end-customActionHandle*/
+    .on(EmbedEvent.Error, (error) => {
+        if (error?.data?.errorType === 'FULLSCREEN') {
+            showErrorBanner('none');
+        } else
+        if (typeof(error.error) === 'string') {
+            showErrorBanner('flex', error.error);
+        } else {
+            showErrorBanner('flex');
+        }
+        console.log('Error ', error);
+        hideLoader();
+    })
+    // Render Liveboard
+    .render();
+----
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/style-customization/intro">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/style-customization/step-02">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/style-customization/style-customization_tutorial-step-02.adoc b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-02.adoc
new file mode 100644
index 000000000..74b307c13
--- /dev/null
+++ b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-02.adoc
@@ -0,0 +1,85 @@
+= Step 2: Large component elements
+:toc!:
+
+:page-title: Step 2: Large component elements
+:page-pageid: style-customization__step-02
+:page-description: Customize large component elements such as the Liveboard header and tab panel from the Playground.
+
+The checkboxes above the code panel provide quick access to the code to customize embedded elements.
+
+. Click *Customize Liveboard header* checkbox. You'll see the following code block in the code editor:
++
+[source,javascript]
+----
+ /* Show or hide the liveboard title and description */
+ showLiveboardTitle: true,
+ showLiveboardDescription: true,
+ // isLiveboardHeaderSticky: false, /* Removes the header stickiness when scrolling if set to false */
+ // hideLiveboardHeader: true, /* Hides the entire liveboard header */
+
+ /* Customize display of tabs in the liveboard header */
+ // hideTabPanel: true, /* Removes the tab panel */
+ // visibleTabs:['TabId'], /* Remove all tabs if empty array*/
+ // hiddenTabs:['TabId'],
+ /* Use either visibleTabs or hiddenTabs */
+----
++
+If the *Customize Liveboard header* checkbox is unavailable on your instance of ThoughtSpot, check *Full Height* then copy the code above over the `fullHeight: true` section that is added to the Code Editor.
+
++
+[NOTE]
+====
+The code includes examples of several settings that are commented out using the `//` line comment.  Removing `//` enables these settings and allows you to include them in your code.
+====
+
+. Click *Run*. The `LiveboardEmbed` component loads with the new options.
+. Remove `//` before the `hideLiveboardHeader: true` property to enable this setting.
+. Click *Run* again to see the updated results.
+
+== Available options for component element customization
+There are many more configurations available for each component than those available in the Playground. To see all available options, see link:https://developers.thoughtspot.com/docs/VisualEmbedSdk#_interfaces[Embed Classes^] and link:https://developers.thoughtspot.com/docs/VisualEmbedSdk#_interfaces[Embed Interfaces^].
+
+
+[.bordered]
+image:images/tutorials/style-customization/embed-components-reference.png[Components reference]
+
+To use a setting that is not automatically generated by the Playground, go to its link:https://developers.thoughtspot.com/docs/Interface_LiveboardViewConfig[definition within the reference page^] and look at the example code.
+
+To override user's locale settings:
+
+. Click link:https://developers.thoughtspot.com/docs/Interface_LiveboardViewConfig#_locale[locale^].
+. Copy the property into the code in the Playground and specify a valid locale attribute. For example, `fr` or `it`:
++
+[source,javascript]
+----
+ /* We added this one ourselves */
+ locale: 'fr',
+ /* Show or hide the Liveboard title and description */
+ showLiveboardTitle: true,
+ showLiveboardDescription: true,
+ // isLiveboardHeaderSticky: false, /* Removes the header stickiness when scrolling if set to false */
+ // hideLiveboardHeader: true, /* Hides the entire liveboard header */
+
+ /* Customize display of tabs in the liveboard header */
+ // hideTabPanel: true, /* Removes the tab panel */
+ // visibleTabs:['TabId'], /* Remove all tabs if empty array*/
+ // hiddenTabs:['TabId'],
+ /* Use either visibleTabs or hiddenTabs */
+----
+
+. Click *Run* and try some of the items in the menu system when the Liveboard loads.
++
+[.bordered]
+image:images/tutorials/style-customization/locale-override.png[Locale override property]
+
+== Hiding elements without configuration options
+If there are elements of the page that you can't find an option to hide in the embedded interface configuration options, you may need to xref:style-customization_tutorial-step-03.adoc#_hide_elements[use the CSS customization framework to hide a given element] directly.
+
+If your implementation requires hiding certain elements, let ThoughtSpot know the element for which you need a configuration option by submitting an idea to the link:https://community.thoughtspot.com/s/ideas[ThoughtSpot Community^].
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/style-customization/step-01">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/style-customization/step-03">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/style-customization/style-customization_tutorial-step-03.adoc b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-03.adoc
new file mode 100644
index 000000000..751027c1a
--- /dev/null
+++ b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-03.adoc
@@ -0,0 +1,151 @@
+= Step 3: CSS styles
+:toc!:
+
+:page-title: Step 3: CSS styles
+:page-pageid: style-customization__step-03
+:page-description: Use the customizations framework to apply CSS variables and selectors to embedded ThoughtSpot content.
+
+The Visual Embed SDK has a `customizations` framework for adding CSS and other overrides.
+
+In the Playground, select the *Apply custom styles* checkbox. The code panel shows a large block of code with various options for CSS customization:
+
+[NOTE]
+====
+The `customizations` code goes in the `init()` function, whereas the other customizations are applied when the embedded component initializes.
+====
+
+[source,javascript]
+----
+customizations: {
+    style: {
+        customCSSUrl: "https://cdn.jsdelivr.net/gh/thoughtspot/custom-css-demo/css-variables.css", // location of your style sheet
+
+        // To apply overrides for your style sheet in this init, provide variable values below, eg
+        customCSS: {
+            variables: {
+                "--ts-var-button--secondary-background": "#F0EBFF",
+                "--ts-var-button--secondary--hover-background": "#E3D9FC",
+                "--ts-var-root-background": "#F7F5FF",
+            },
+        },
+    },
+},
+----
+
+== Variables and selectors
+ThoughtSpot provides many pre-defined xref:customize-css-styles.adoc[CSS variables] to control the styling of the embedded component UI and its elements.
+
+The style definitions can all be declared directly within the `variables` block of the `customCSS` code.
+
+The customization framework also allows using any CSS selector to target specific elements with changes that do not have a defined variable. Selectors can be declared within the `rules_UNSTABLE` block inside `customCSS`. However, selectors may change with new releases as elements of ThoughtSpot are updated.
+
+Let's add a selector to the code in our Playground. First, comment out the `customCSSUrl` line, then add the `rules_UNSTABLE` block below `variables`:
+
+[source,javascript]
+----
+customizations: {
+    style: {
+        // customCSSUrl: "https://cdn.jsdelivr.net/gh/thoughtspot/custom-css-demo/css-variables.css", // location of your style sheet
+
+        // To apply overrides for your style sheet in this init, provide variable values below, eg
+        customCSS: {
+            variables: {
+                "--ts-var-button--secondary-background": "#F0EBFF",
+                "--ts-var-button--secondary--hover-background": "#E3D9FC",
+                "--ts-var-root-background": "#F7F5FF",
+            },
+            rules_UNSTABLE: {
+
+            }
+        },
+    },
+},
+----
+
+Variables declare a __single__ property, therefore are defined as `"{var-name}" : "{value}"`, whereas selectors allow you to assign several properties to the selected elements.
+
+[NOTE]
+====
+Selectors apply properties to elements with many layers of styling. Always add `!important` after each property to ensure the browser overrides whatever other style rules may be applied for the same property.
+====
+
+One use case of the `rules_UNSTABLE` section is `xref:css-customization.adoc#font-declarations[@font-face]` declarations, which have many properties for one selector.
+
+We'll switch the main font to link:https://fonts.google.com/specimen/Poppins[Poppins^], available from Google Fonts:
+
+. Add the `--ts-var-root-font-family` variable to declare the new font. +
+Note that you'll need to use this exact name value in `@font-face` declarations.
+. Add a selector block within the `rules_UNSTABLE` block.
+. Include xref:css-customization.adoc#_font_declarations[font declarations].
++
+[source,javascript]
+----
+// ...
+ customCSS: {
+     variables: {
+         "--ts-var-button--secondary-background": "#F0EBFF",
+         "--ts-var-button--secondary--hover-background": "#E3D9FC",
+         "--ts-var-root-background": "#F7F5FF",
+         "--ts-var-root-font-family": "Poppins"
+     },
+     rules_UNSTABLE: {
+         '/* ff-400 */ @font-face': {
+             'font-family': "Poppins",
+             'font-style': 'normal',
+             'font-weight': '400',
+             'font-display': 'swap',
+             'src': "url(https://fonts.gstatic.com/s/poppins/v21/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2) format('woff2')"
+         }
+     }
+ },
+----
++
+Notice the format shows the selector as the __key__, then an object block containing individual key-value pairs for the properties. Because the selector is an object key, but all `@font-face` declarations start the same way, we add a unique CSS comment at the beginning to allow for multiple `@font-face` declarations.
+
+. Click *Run*.
+. Notice the Liveboard reload with the `Poppins` font for most of the text.
+
+== CSS files
+You can collect a set of variables and selectors into a CSS file, rather than declaring them in the JavaScript code block.
+CSS files can be included from any domain, but they must be added to the *CSP style-src domains* and *CSP font-src* domains on the *Develop* > *Customizations* -> *Security settings* page.
+
+Both `\https://cdn.jsdelivr.net` and `\https://fonts.gstatic.com` sites are automatically added to ThoughtSpot's CSP allowlist.
+
+In your CSS file, the global variables must be declared in the `:root { }` block, while `@font-face` declarations of a named font can be placed anywhere:
+
+[,css]
+----
+:root {
+  --ts-var-button--primary-background: #2359B6;
+  --ts-var-button--primary--hover-background: blue;
+  --ts-var-button--primary--font-family: Poppins,Helvetica,Arial,sans-serif;;
+}
+
+@font-face {
+  font-family: 'Poppins';
+  font-style: normal;
+  font-weight: 400;
+  font-display: swap;
+  src: url(https://fonts.gstatic.com/s/poppins/v21/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2) format('woff2');
+}
+
+.bk-filter-option {
+  display: none!important;
+}
+----
+
+== Hide elements
+As seen in the CSS file example above, one of the use cases for selectors is to hide embed component elements that do not have a configuration option.
+
+`display: none!important` is the most typical property to accomplish this, but you may choose any CSS rule that causes the desired effect.
+
+Make sure that the selector you use is specific and does not affect other elements that you don't intend to hide.
+
+If you have been hiding certain elements via CSS selectors, link:https://community.thoughtspot.com/s/ideas[contact ThoughtSpot^] to request configuration options for such elements, so that the overall configurations can be expanded over time. Similarly, provide feedback on properties that variables are unavailable by submitting an idea to the link:https://community.thoughtspot.com/s/ideas[ThoughtSpot Community^].
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/style-customization/step-02">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/style-customization/step-04">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/style-customization/style-customization_tutorial-step-04.adoc b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-04.adoc
new file mode 100644
index 000000000..847d09907
--- /dev/null
+++ b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-04.adoc
@@ -0,0 +1,58 @@
+= Step 4: Text strings and icon replacement
+:toc!:
+
+:page-title: Step 4: Text strings and icon replacement
+:page-pageid: style-customization__step-04
+:page-description: Replace text strings and icon sprites in embedded ThoughtSpot content using the customizations framework.
+
+The `customizations` object allows replacing replace specific xref:customize-text-strings.adoc[text strings] and xref:customize-icons.adoc[icons].
+
+== Replace text strings
+
+Let's add the `content` property above the `style` property in the `customizations` code and then add  the  `strings` property block within this code. Now we can declare the exact text elements to replace within ThoughtSpot:
+
+[source,javascript]
+----
+// ...
+customizations: {
+    content: {
+        strings: {
+            "Liveboard": "Dashboard",
+            "SpotIQ": "Insights",
+            "Spotter": "AI Agent"
+        }
+    },
+    style: {
+        ...
+    },
+},
+----
+
+== Replace icon sprites
+
+Icon sprite replacement requires creating a file of SVG icon definitions, the format for which is available in the xref:customize-icons.adoc[icon sprite customization documentation]. After you have the SVG file saved and accessible to ThoughtSpot, add the `iconSpriteUrl` property in the `customizations` block:
+
+[source,javascript]
+----
+// ...
+customizations: {
+    iconSpriteUrl: "https://cdn.jsdelivr.net/gh/thoughtspot/custom-css-demo/icon-override1.svg",
+    content: {
+        strings: {
+            "Liveboard": "Dashboard",
+            "SpotIQ": "Insights",
+            "Spotter": "AI Agent"
+        }
+    },
+    style: {
+        ...
+    },
+},
+----
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/style-customization/step-03">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/style-customization/step-05">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/style-customization/style-customization_tutorial-step-05.adoc b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-05.adoc
new file mode 100644
index 000000000..2a29e6605
--- /dev/null
+++ b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-05.adoc
@@ -0,0 +1,117 @@
+= Step 5: Menu items
+:toc!:
+
+:page-title: Step 5: Menu items
+:page-pageid: style-customization__step-05
+:page-description: Hide, disable, and trigger ThoughtSpot menu items and custom actions from the embedded application.
+
+ThoughtSpot menus are accessible in the top right corner with the ellipsis icon (`...`) or via a right-click on a chart axis or data point. The `...` menu is referred to as the *More* options menu.
+
+On Liveboards, a top menu for the Liveboard and a separate menu for each visualization is available. The menu from right-clicking a data point is referred to as the *Context menu*.
+
+== Hiding or disabling items
+Individual menu items are controlled by their capabilities and are referred to as *Actions*. The Visual Embed SDK reference guide for link:https://developers.thoughtspot.com/docs/Enumeration_Action[Actions^] contains a complete list of named capabilities.
+
+In the Playground, select the checkbox for `Modify available actions`. You'll see the following code in the code editor:
+
+[source,javascript]
+----
+  disabledActions: [],
+  disabledActionReason: "Reason for disabling",
+  // visibleActions: [], /* Removes all actions if empty array */
+  hiddenActions: [],
+  /* Use either visibleActions or hiddenActions */
+----
+
+If you want to show only a small set of selected menu items, use `visibleActions` (an allowlist) and comment out `hiddenActions` (a deny list).
+
+Let's show only the `DownloadAsPdf` action:
+
+[source,javascript]
+----
+  disabledActions: [],
+  disabledActionReason: "Reason for disabling",
+  visibleActions: [Action.DownloadAsPdf], /* Removes all actions if empty array */
+  //hiddenActions: [],
+  /* Use either visibleActions or hiddenActions */
+----
+
+When you click *Run*, the Liveboard reloads with only a single menu item in the *More* options menu as specified in the `visibleActions` array.
+
+[NOTE]
+====
+The above example also hides the right-click context menu items, including the *Drill down* action (`Action.DrillDown`).
+====
+
+The `disabledActions` array keeps the item in the menu but grays it out, and shows `disabledActionReason` when hovering over the disabled action.
+
+== Triggering hidden menu items with HostEvents
+ThoughtSpot Visual Embed SDK defines two types of events:
+
+* link:https://developers.thoughtspot.com/docs/Enumeration_EmbedEvent[EmbedEvents^] - to listen to actions within ThoughtSpot components
+* link:https://developers.thoughtspot.com/docs/Enumeration_HostEvent[HostEvents^] - to send messages to the ThoughtSpot components from the embedding application.
+
+If a menu item has been hidden, you can still send in a *HostEvent* to cause the same behavior.
+
+In the Playground, select the *Use Host Event* checkbox. You'll see the following code block in the code editor:
+
+[source,javascript]
+----
+ document.getElementById('tryBtn').addEventListener('click', e => {
+      // Trigger events can be added here to bind to try button click!
+      // eg use the Reload Event so that clicking on "Try event" button reloads the embed:
+      embed.trigger(HostEvent.Reload);
+ });
+----
+
+The above code block adds a click event to the *Try Event* button above the preview panel in the Playground. Clicking *Try Event* triggers the `HostEvent`.
+
+Let's replace the default `Reload` event with `DownloadAsPdf`:
+
+[source,javascript]
+----
+ document.getElementById('tryBtn').addEventListener('click', e => {
+     // Trigger events can be added here to bind to try button click!
+     // eg use the Reload Event so that clicking on "Try event" button reloads the embed:
+     embed.trigger(HostEvent.DownloadAsPdf);
+ });
+----
+
+Testing this requires the following steps:
+
+1. Click *Run* to reload the embedded component.
+2. Click *Try Event*.
+
+You should see the PDF export modal dialog button pop up within the embedded component area.
+
+If you do not want the modal dialog to appear, you could instead use the ThoughtSpot REST API to accomplish the task either within the browser or in a back-end process. This allows for choosing vastly different behaviors than those allowed by the ThoughtSpot modal dialogs.
+
+== Adding new menu items with custom actions
+ThoughtSpot allows you to add new items called *xref:custom-actions.adoc[custom actions]* to the menu system, either to the *More* options menu on a given visualization of a Liveboard or the context menu that appears when a single point is right-clicked.
+
+The *Callback* custom actions require a three-part setup:
+
+1. Define the custom action within ThoughtSpot, with a particular *id*.
+2. Assign the custom action to the visualization.
+3. Add the `EmbedEvent.CustomAction` listener within the Visual Embed SDK code.
+
+To try it out, select the `Handle custom actions` checkbox. You'll see the following code block in the code editor:
+
+[source,javascript]
+----
+ .on(EmbedEvent.CustomAction, payload => {
+     const customActionId = 'insert Custom Action ID here';
+     if (payload.id === customActionId || payload.data.id === customActionId) {
+         console.log('Custom Action event:', payload.data);
+     }
+ })
+----
+
+Some link:https://developers.thoughtspot.com/docs/Enumeration_EmbedEvent[EmbedEvents^] such as `VizPointClick` fire off without involving the menu system and function similarly to context menu custom action.
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/style-customization/step-04">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/style-customization/step-06">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/style-customization/style-customization_tutorial-step-06.adoc b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-06.adoc
new file mode 100644
index 000000000..6e4e41fea
--- /dev/null
+++ b/modules/tutorials/pages/style-customization/style-customization_tutorial-step-06.adoc
@@ -0,0 +1,17 @@
+= Step 6: Conclusion
+:toc!:
+
+:page-title: Step 6: Conclusion
+:page-pageid: style-customization__step-06
+:page-description: Wrap up the style customization tutorial and next steps for integrating into your application.
+
+This tutorial has covered how to customize the UI and UX of ThoughtSpot's embedded components, but only within the Visual Embed SDK Playground.
+
+The next steps are to move this code into your application page and configure the CSP and CORS settings for your application's test environments, so you begin integrating ThoughtSpot directly into your application.
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/style-customization/step-05">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next tutorial-pagination__done" href="{{navprefix}}/tutorials/tutorials-overview">Done</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/style-customization/style-customization_tutorial.adoc b/modules/tutorials/pages/style-customization/style-customization_tutorial.adoc
deleted file mode 100644
index c3907250e..000000000
--- a/modules/tutorials/pages/style-customization/style-customization_tutorial.adoc
+++ /dev/null
@@ -1,479 +0,0 @@
-= Style customization tutorial
-:toc: true
-:toclevels: 1
-
-:page-title: Visual Embed SDK Style customization tutorial
-:page-pageid: style-customization__tutorial
-:page-description:  This is a self-guided course on style customization of the Visual Embed SDK components
-
-
-One of the main advantages of ThoughtSpot Embedded is the control over the styling and UI elements provided by the Visual Embed SDK.
-
-This tutorial provides a walkthrough of customizable elements of ThoughtSpot UI and essential steps to style your embedded ThoughtSpot content.
-
-ThoughtSpot allows customizing the following aspects of its UI:
-
-1. Large component elements
-2. CSS styles
-3. Text strings and icon replacement
-4. Menu items
-
-
-== 01 - Getting started
-
-This tutorial uses the Visual Embed SDK Playground built into every ThoughtSpot instance to demonstrate various customizations in a live environment.
-
-We suggest copying the code into a text editor or IDE such as Visual Studio Code to make it easier to work on the examples, and then copy the values back into the code editor within the Playground.
-
-To get started:
-
-. Select the `Liveboard` component to embed in the Playground:
-+
-[.widthAuto]
-[.bordered]
-image:images/tutorials/style-customization/choose-liveboard-embed.png[Choose LiveboardEmbed component]
-. Select the *(Sample) Sales Performance* Liveboard, which should be available on all instances, including the Free Trial setup.
-+
-[.widthAuto]
-[.bordered]
-image:images/tutorials/style-customization/choose-liveboard.png[Choose Liveboard]
-
-. If you do not have "(Sample) Sales Performance" available, use any Liveboard that you have access to.
-+
-You should see the following code in the code panel of the Playground page.
-
-. Copy at any point down to `.render();`:
-+
-[source,javascript]
-----
-// Import ThoughtSpot SDK
-import {
-    init,
-    LiveboardEmbed,
-    Action,
-    RuntimeFilterOp,
-    EmbedEvent,
-    AuthType,
-    HostEvent
-} from "@thoughtspot/visual-embed-sdk";
-import "./styles.css";
-import {
-    getTokenService
-} from "./tokenService";
-
-// Use prefetch to load static resources early and optimize response time.
-// Call init early to complete authentication during app load for better performance.
-init({
-   thoughtSpotHost:
-   /*param-start-hosturl*/"https://embed-1-do-not-delete.thoughtspotstaging.cloud" /*param-end-hosturl*/,
-   /*param-start-styleCustomization*//*param-end-styleCustomization*/
-    authType: AuthType.TrustedAuthTokenCookieless,
-    getAuthToken: getTokenService,
-    disableTokenVerification: true,
-});
-
-// Instantiate class for embedding a Liveboard
-const embed = new LiveboardEmbed("#your-own-div", {
-    frameParams: {},
-    /*param-start-liveboardId*/liveboardId: "d084c256-e284-4fc4-b80c-111cb606449a" /*param-end-liveboardId*/
-    /*param-start-activeTabId*//*param-end-activeTabId*/
-    /*param-start-liveboardFullHeight*//*param-end-liveboardFullHeight*/
-    /*param-start-customizeLiveboardHeader*//*param-end-customizeLiveboardHeader*/
-    /*param-start-hideLiveboardHeader*//*param-end-hideLiveboardHeader*/
-    /*param-start-runtimeFiltersAndParameters*//*param-end-runtimeFiltersAndParameters*/
-    /*param-start-modifyActions*//*param-end-modifyActions*/
-});
-
-hideNoDataImage();
-showErrorBanner('none');
-
-embed
-    // Register event listeners
-    .on(EmbedEvent.Init, showLoader)
-    .on(EmbedEvent.Load, hideLoader)
-    /*param-start-customActionHandle*//*param-end-customActionHandle*/
-    .on(EmbedEvent.Error, (error) => {
-        if (error?.data?.errorType === 'FULLSCREEN') {
-            showErrorBanner('none');
-        } else
-        if (typeof(error.error) === 'string') {
-            showErrorBanner('flex', error.error);
-        } else {
-            showErrorBanner('flex');
-        }
-        console.log('Error ', error);
-        hideLoader();
-    })
-    // Render Liveboard
-    .render();
-----
-
-== 02 - Large component elements
-
-The checkboxes above the code panel provide quick access to the code to customize embedded elements.
-
-. Click *Customize Liveboard header* checkbox. You'll see the following code block in the code editor:
-+
-[source,javascript]
-----
- /* Show or hide the liveboard title and description */
- showLiveboardTitle: true,
- showLiveboardDescription: true,
- // isLiveboardHeaderSticky: false, /* Removes the header stickiness when scrolling if set to false */
- // hideLiveboardHeader: true, /* Hides the entire liveboard header */
-
- /* Customize display of tabs in the liveboard header */
- // hideTabPanel: true, /* Removes the tab panel */
- // visibleTabs:['TabId'], /* Remove all tabs if empty array*/
- // hiddenTabs:['TabId'],
- /* Use either visibleTabs or hiddenTabs */
-----
-+
-If the *Customize Liveboard header* checkbox is unavailable on your instance of ThoughtSpot, check *Full Height* then copy the code above over the `fullHeight: true` section that is added to the Code Editor.
-
-+
-[NOTE]
-====
-The code includes examples of several settings that are commented out using the `//` line comment.  Removing `//` enables these settings and allows you to include them in your code.
-====
-
-. Click *Run*. The `LiveboardEmbed` component loads with the new options.
-. Remove `//` before the `hideLiveboardHeader: true` property to enable this setting.
-. Click *Run* again to see the updated results.
-
-=== Available options for component element customization
-There are many more configurations available for each component than those available in the Playground. To see all available options, see link:https://developers.thoughtspot.com/docs/VisualEmbedSdk#_interfaces[Embed Classes^] and link:https://developers.thoughtspot.com/docs/VisualEmbedSdk#_interfaces[Embed Interfaces^].
-
-
-[.bordered]
-image:images/tutorials/style-customization/embed-components-reference.png[Components reference]
-
-To use a setting that is not automatically generated by the Playground, go to its link:https://developers.thoughtspot.com/docs/Interface_LiveboardViewConfig[definition within the reference page^] and look at the example code.
-
-To override user's locale settings:
-
-. Click link:https://developers.thoughtspot.com/docs/Interface_LiveboardViewConfig#_locale[locale^].
-. Copy the property into the code in the Playground and specify a valid locale attribute. For example, `fr` or `it`:
-+
-[source,javascript]
-----
- /* We added this one ourselves */
- locale: 'fr',
- /* Show or hide the Liveboard title and description */
- showLiveboardTitle: true,
- showLiveboardDescription: true,
- // isLiveboardHeaderSticky: false, /* Removes the header stickiness when scrolling if set to false */
- // hideLiveboardHeader: true, /* Hides the entire liveboard header */
-
- /* Customize display of tabs in the liveboard header */
- // hideTabPanel: true, /* Removes the tab panel */
- // visibleTabs:['TabId'], /* Remove all tabs if empty array*/
- // hiddenTabs:['TabId'],
- /* Use either visibleTabs or hiddenTabs */
-----
-
-. Click *Run* and try some of the items in the menu system when the Liveboard loads.
-+
-[.bordered]
-image:images/tutorials/style-customization/locale-override.png[Locale override property]
-
-=== Hiding elements without configuration options
-If there are elements of the page that you can't find an option to hide in the embedded interface configuration options, you may need to xref:_hide_elements[use the CSS customization framework to hide a given element] directly.
-
-If your implementation requires hiding certain elements, let ThoughtSpot know the element for which you need a configuration option by submitting an idea to the link:https://community.thoughtspot.com/s/ideas[ThoughtSpot Community^].
-
-== 03 - CSS styles
-The Visual Embed SDK has a `customizations` framework for adding CSS and other overrides.
-
-In the Playground, select the *Apply custom styles* checkbox. The code panel shows a large block of code with various options for CSS customization:
-
-[NOTE]
-====
-The `customizations` code goes in the `init()` function, whereas the other customizations are applied when the embedded component initializes.
-====
-
-[source,javascript]
-----
-customizations: {
-    style: {
-        customCSSUrl: "https://cdn.jsdelivr.net/gh/thoughtspot/custom-css-demo/css-variables.css", // location of your style sheet
-
-        // To apply overrides for your style sheet in this init, provide variable values below, eg
-        customCSS: {
-            variables: {
-                "--ts-var-button--secondary-background": "#F0EBFF",
-                "--ts-var-button--secondary--hover-background": "#E3D9FC",
-                "--ts-var-root-background": "#F7F5FF",
-            },
-        },
-    },
-},
-----
-
-=== Variables and selectors
-ThoughtSpot provides many pre-defined xref:customize-css-styles.adoc[CSS variables] to control the styling of the embedded component UI and its elements.
-
-The style definitions can all be declared directly within the `variables` block of the `customCSS` code.
-
-The customization framework also allows using any CSS selector to target specific elements with changes that do not have a defined variable. Selectors can be declared within the `rules_UNSTABLE` block inside `customCSS`. However, selectors may change with new releases as elements of ThoughtSpot are updated.
-
-Let's add a selector to the code in our Playground. First, comment out the `customCSSUrl` line, then add the `rules_UNSTABLE` block below `variables`:
-
-[source,javascript]
-----
-customizations: {
-    style: {
-        // customCSSUrl: "https://cdn.jsdelivr.net/gh/thoughtspot/custom-css-demo/css-variables.css", // location of your style sheet
-
-        // To apply overrides for your style sheet in this init, provide variable values below, eg
-        customCSS: {
-            variables: {
-                "--ts-var-button--secondary-background": "#F0EBFF",
-                "--ts-var-button--secondary--hover-background": "#E3D9FC",
-                "--ts-var-root-background": "#F7F5FF",
-            },
-            rules_UNSTABLE: {
-
-            }
-        },
-    },
-},
-----
-
-Variables declare a __single__ property, therefore are defined as `"{var-name}" : "{value}"`, whereas selectors allow you to assign several properties to the selected elements.
-
-[NOTE]
-====
-Selectors apply properties to elements with many layers of styling. Always add `!important` after each property to ensure the browser overrides whatever other style rules may be applied for the same property.
-====
-
-One use case of the `rules_UNSTABLE` section is `xref:css-customization.adoc#font-declarations[@font-face]` declarations, which have many properties for one selector.
-
-We'll switch the main font to link:https://fonts.google.com/specimen/Poppins[Poppins^], available from Google Fonts:
-
-. Add the `--ts-var-root-font-family` variable to declare the new font. +
-Note that you'll need to use this exact name value in `@font-face` declarations.
-. Add a selector block within the `rules_UNSTABLE` block.
-. Include xref:css-customization.adoc#_font_declarations[font declarations].
-+
-[source,javascript]
-----
-// ...
- customCSS: {
-     variables: {
-         "--ts-var-button--secondary-background": "#F0EBFF",
-         "--ts-var-button--secondary--hover-background": "#E3D9FC",
-         "--ts-var-root-background": "#F7F5FF",
-         "--ts-var-root-font-family": "Poppins"
-     },
-     rules_UNSTABLE: {
-         '/* ff-400 */ @font-face': {
-             'font-family': "Poppins",
-             'font-style': 'normal',
-             'font-weight': '400',
-             'font-display': 'swap',
-             'src': "url(https://fonts.gstatic.com/s/poppins/v21/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2) format('woff2')"
-         }
-     }
- },
-----
-+
-Notice the format shows the selector as the __key__, then an object block containing individual key-value pairs for the properties. Because the selector is an object key, but all `@font-face` declarations start the same way, we add a unique CSS comment at the beginning to allow for multiple `@font-face` declarations.
-
-. Click *Run*.
-. Notice the Liveboard reload with the `Poppins` font for most of the text.
-
-=== CSS files
-You can collect a set of variables and selectors into a CSS file, rather than declaring them in the JavaScript code block.
-CSS files can be included from any domain, but they must be added to the *CSP style-src domains* and *CSP font-src* domains on the *Develop* > *Customizations* -> *Security settings* page.
-
-Both `\https://cdn.jsdelivr.net` and `\https://fonts.gstatic.com` sites are automatically added to ThoughtSpot's CSP allowlist.
-
-In your CSS file, the global variables must be declared in the `:root { }` block, while `@font-face` declarations of a named font can be placed anywhere:
-
-[,css]
-----
-:root {
-  --ts-var-button--primary-background: #2359B6;
-  --ts-var-button--primary--hover-background: blue;
-  --ts-var-button--primary--font-family: Poppins,Helvetica,Arial,sans-serif;;
-}
-
-@font-face {
-  font-family: 'Poppins';
-  font-style: normal;
-  font-weight: 400;
-  font-display: swap;
-  src: url(https://fonts.gstatic.com/s/poppins/v21/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2) format('woff2');
-}
-
-.bk-filter-option {
-  display: none!important;
-}
-----
-
-=== Hide elements
-As seen in the CSS file example above, one of the use cases for selectors is to hide embed component elements that do not have a configuration option.
-
-`display: none!important` is the most typical property to accomplish this, but you may choose any CSS rule that causes the desired effect.
-
-Make sure that the selector you use is specific and does not affect other elements that you don't intend to hide.
-
-If you have been hiding certain elements via CSS selectors, link:https://community.thoughtspot.com/s/ideas[contact ThoughtSpot^] to request configuration options for such elements, so that the overall configurations can be expanded over time. Similarly, provide feedback on properties that variables are unavailable by submitting an idea to the link:https://community.thoughtspot.com/s/ideas[ThoughtSpot Community^].
-
-== 04 - Text strings and icon replacement
-The `customizations` object allows replacing replace specific xref:customize-text-strings.adoc[text strings] and xref:customize-icons.adoc[icons].
-
-=== Replace text strings
-
-Let's add the `content` property above the `style` property in the `customizations` code and then add  the  `strings` property block within this code. Now we can declare the exact text elements to replace within ThoughtSpot:
-
-[source,javascript]
-----
-// ...
-customizations: {
-    content: {
-        strings: {
-            "Liveboard": "Dashboard",
-            "SpotIQ": "Insights",
-            "Spotter": "AI Agent"
-        }
-    },
-    style: {
-        ...
-    },
-},
-----
-
-=== Replace icon sprites
-
-Icon sprite replacement requires creating a file of SVG icon definitions, the format for which is available in the xref:customize-icons.adoc[icon sprite customization documentation]. After you have the SVG file saved and accessible to ThoughtSpot, add the `iconSpriteUrl` property in the `customizations` block:
-
-[source,javascript]
-----
-// ...
-customizations: {
-    iconSpriteUrl: "https://cdn.jsdelivr.net/gh/thoughtspot/custom-css-demo/icon-override1.svg",
-    content: {
-        strings: {
-            "Liveboard": "Dashboard",
-            "SpotIQ": "Insights",
-            "Spotter": "AI Agent"
-        }
-    },
-    style: {
-        ...
-    },
-},
-----
-
-== 05 - Menu items
-ThoughtSpot menus are accessible in the top right corner with the ellipsis icon (`...`) or via a right-click on a chart axis or data point. The `...` menu is referred to as the *More* options menu.
-
-On Liveboards, a top menu for the Liveboard and a separate menu for each visualization is available. The menu from right-clicking a data point is referred to as the *Context menu*.
-
-=== Hiding or disabling items
-Individual menu items are controlled by their capabilities and are referred to as *Actions*. The Visual Embed SDK reference guide for link:https://developers.thoughtspot.com/docs/Enumeration_Action[Actions^] contains a complete list of named capabilities.
-
-In the Playground, select the checkbox for `Modify available actions`. You'll see the following code in the code editor:
-
-[source,javascript]
-----
-  disabledActions: [],
-  disabledActionReason: "Reason for disabling",
-  // visibleActions: [], /* Removes all actions if empty array */
-  hiddenActions: [],
-  /* Use either visibleActions or hiddenActions */
-----
-
-If you want to show only a small set of selected menu items, use `visibleActions` (an allowlist) and comment out `hiddenActions` (a deny list).
-
-Let's show only the `DownloadAsPdf` action:
-
-[source,javascript]
-----
-  disabledActions: [],
-  disabledActionReason: "Reason for disabling",
-  visibleActions: [Action.DownloadAsPdf], /* Removes all actions if empty array */
-  //hiddenActions: [],
-  /* Use either visibleActions or hiddenActions */
-----
-
-When you click *Run*, the Liveboard reloads with only a single menu item in the *More* options menu as specified in the `visibleActions` array.
-
-[NOTE]
-====
-The above example also hides the right-click context menu items, including the *Drill down* action (`Action.DrillDown`).
-====
-
-The `disabledActions` array keeps the item in the menu but grays it out, and shows `disabledActionReason` when hovering over the disabled action.
-
-=== Triggering hidden menu items with HostEvents
-ThoughtSpot Visual Embed SDK defines two types of events:
-
-* link:https://developers.thoughtspot.com/docs/Enumeration_EmbedEvent[EmbedEvents^] - to listen to actions within ThoughtSpot components
-* link:https://developers.thoughtspot.com/docs/Enumeration_HostEvent[HostEvents^] - to send messages to the ThoughtSpot components from the embedding application.
-
-If a menu item has been hidden, you can still send in a *HostEvent* to cause the same behavior.
-
-In the Playground, select the *Use Host Event* checkbox. You'll see the following code block in the code editor:
-
-[source,javascript]
-----
- document.getElementById('tryBtn').addEventListener('click', e => {
-      // Trigger events can be added here to bind to try button click!
-      // eg use the Reload Event so that clicking on "Try event" button reloads the embed:
-      embed.trigger(HostEvent.Reload);
- });
-----
-
-The above code block adds a click event to the *Try Event* button above the preview panel in the Playground. Clicking *Try Event* triggers the `HostEvent`.
-
-Let's replace the default `Reload` event with `DownloadAsPdf`:
-
-[source,javascript]
-----
- document.getElementById('tryBtn').addEventListener('click', e => {
-     // Trigger events can be added here to bind to try button click!
-     // eg use the Reload Event so that clicking on "Try event" button reloads the embed:
-     embed.trigger(HostEvent.DownloadAsPdf);
- });
-----
-
-Testing this requires the following steps:
-
-1. Click *Run* to reload the embedded component.
-2. Click *Try Event*.
-
-You should see the PDF export modal dialog button pop up within the embedded component area.
-
-If you do not want the modal dialog to appear, you could instead use the ThoughtSpot REST API to accomplish the task either within the browser or in a back-end process. This allows for choosing vastly different behaviors than those allowed by the ThoughtSpot modal dialogs.
-
-=== Adding new menu items with custom actions
-ThoughtSpot allows you to add new items called *xref:custom-actions.adoc[custom actions]* to the menu system, either to the *More* options menu on a given visualization of a Liveboard or the context menu that appears when a single point is right-clicked.
-
-The *Callback* custom actions require a three-part setup:
-
-1. Define the custom action within ThoughtSpot, with a particular *id*.
-2. Assign the custom action to the visualization.
-3. Add the `EmbedEvent.CustomAction` listener within the Visual Embed SDK code.
-
-To try it out, select the `Handle custom actions` checkbox. You'll see the following code block in the code editor:
-
-[source,javascript]
-----
- .on(EmbedEvent.CustomAction, payload => {
-     const customActionId = 'insert Custom Action ID here';
-     if (payload.id === customActionId || payload.data.id === customActionId) {
-         console.log('Custom Action event:', payload.data);
-     }
- })
-----
-
-Some link:https://developers.thoughtspot.com/docs/Enumeration_EmbedEvent[EmbedEvents^] such as `VizPointClick` fire off without involving the menu system and function similarly to context menu custom action.
-
-== 06 - Conclusion
-
-This tutorial has covered how to customize the UI and UX of ThoughtSpot's embedded components, but only within the Visual Embed SDK Playground.
-
-The next steps are to move this code into your application page and configure the CSP and CORS settings for your application's test environments, so you begin integrating ThoughtSpot directly into your application.
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-intro.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-intro.adoc
index c2526f551..c199d0f96 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-intro.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-intro.adoc
@@ -1,6 +1,5 @@
 = ThoughtSpot Embedding fundamentals
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-title: ThoughtSpot Embeddig fundamentals
 :page-pageid: tse-fundamentals__intro
@@ -53,3 +52,9 @@ This tutorial is split into smaller lessons, with specific objectives for each s
 |xref:tse-fundamentals-lesson-10.adoc[10 - Styling ThoughtSpot]|Explore styling options when embedding ThoughtSpot into your application.
 |xref:tse-fundamentals-lesson-11.adoc[11 - Summary and Next Steps]|Wrap up the course with a few miscellaneous topics and next steps.
 |===
+
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-01">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-01.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-01.adoc
index 3cbc09d17..c40cdc12e 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-01.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-01.adoc
@@ -1,6 +1,5 @@
 = Introduction to ThoughtSpot Embedded
-:toc: true
-:toclevels: 3
+:toc!:
 :icons: font
 
 :page-title: Introduction to ThoughtSpot Embedded
@@ -47,6 +46,9 @@ image:images/tutorials/tse-fundamentals/lesson-01-playground.png[Developer playg
 
 . If you don't already have one, create a link:https://www.thoughtspot.com/trial?tsref=ts-dev-training[ThoughtSpot Account, window=_blank].
 
-'''
-[.text-right]
-xref:tse-fundamentals-lesson-02.adoc[Next >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/tse-fundamentals/intro">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-02">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-02.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-02.adoc
index 82c2cefbf..60d6667f5 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-02.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-02.adoc
@@ -1,6 +1,5 @@
 = Set up for the course
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-title: Set up for the course
 :page-pageid: tse-fundamentals__lesson-02
@@ -78,4 +77,9 @@ image:images/tutorials/tse-fundamentals/lesson-02-download-git.png[Download from
 3. Open the Visual Embed SDK Playground, modify content, and run the resulting code to become familiar with the code.
 4. Download the code or clone the repository.
 
-xref:tse-fundamentals-lesson-01.adoc[< prev] | xref:tse-fundamentals-lesson-03.adoc[next >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-01">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-03">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-03.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-03.adoc
index 145401076..49cd95c62 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-03.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-03.adoc
@@ -1,6 +1,5 @@
 = Security setup
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-title: Security setup
 :page-pageid:  tse-fundamentals__lesson-03
@@ -142,4 +141,9 @@ See the link:https://developers.thoughtspot.com/docs/trusted-auth[documentation]
 2. Review the documentation for authentication link:https://developers.thoughtspot.com/docs/saml-sso[SAML SSO], link:https://developers.thoughtspot.com/docs/oidc-auth[OIDC], link:https://developers.thoughtspot.com/docs/trusted-auth[Trusted Authentication].
 3. Set the appropriate settings for your environment unless you are using the ThoughtSpot trial instance.
 
-xref:tse-fundamentals-lesson-02.adoc[< prev] | xref:tse-fundamentals-lesson-04.adoc[next >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-02">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-04">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-04.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-04.adoc
index 2360473a8..041c3d018 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-04.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-04.adoc
@@ -1,6 +1,5 @@
 = Start coding
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-title: Start coding
 :page-pageid: tse-fundamentals__lesson-04
@@ -172,4 +171,9 @@ At this point, you're ready to start adding content.
 4. Open the application in a browser.
 5. Open the developer tools and disable the cache.
 
-xref:tse-fundamentals-lesson-03.adoc[< prev] | xref:tse-fundamentals-lesson-05.adoc[next >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-03">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-05">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-05.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-05.adoc
index 7579d96e9..55af07228 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-05.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-05.adoc
@@ -1,6 +1,5 @@
 = Init and Search embedding
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-title: Init and Search embedding
 :page-pageid: tse-fundamentals__lesson-05
@@ -237,4 +236,9 @@ If you run into issues, you can reference the code in the `src` folder.
 * index.html
 * tse.js
 
-xref:tse-fundamentals-lesson-04.adoc[< prev] | xref:tse-fundamentals-lesson-06.adoc[next >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-04">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-06">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-06.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-06.adoc
index deaafb094..25a1a71e0 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-06.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-06.adoc
@@ -1,6 +1,5 @@
 = Embed Natural Language Search
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-title: Lesson 6 - Embed Natural Language Search
 :page-pageid: tse-fundamentals__lesson-06
@@ -137,4 +136,9 @@ If you run into issues, you can reference the code in the `src` folder.
 * index.html
 * tse.js
 
-xref:tse-fundamentals-lesson-05.adoc[< prev] | xref:tse-fundamentals-lesson-07.adoc[next >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-05">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-07">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-07.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-07.adoc
index 0ad51666e..42cf6ea95 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-07.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-07.adoc
@@ -1,6 +1,5 @@
 = Embed a Liveboard
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-title: Embed a Liveboard
 :page-pageid: tse-fundamentals__lesson-07 
@@ -156,4 +155,9 @@ If you run into problems, you can look at the code in the `src` folder in this s
 * index.html
 * tse.js
 
-xref:tse-fundamentals-lesson-06.adoc[< prev] | xref:tse-fundamentals-lesson-08.adoc[next >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-06">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-08">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-08.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-08.adoc
index 658565a26..64d207308 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-08.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-08.adoc
@@ -1,6 +1,5 @@
 = Embed a Liveboard visualization
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-title:  Embed a Liveboard Visualization
 :page-pageid: tse-fundamentals__lesson-08
@@ -124,4 +123,9 @@ If you run into problems, you can look at the code in the `src` folder in this s
 * index.html
 * tse.js
 
-xref:tse-fundamentals-lesson-07.adoc[< prev] | xref:tse-fundamentals-lesson-09.adoc[next >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-07">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-09">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-09.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-09.adoc
index f9b4ddaaa..b8212a8be 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-09.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-09.adoc
@@ -1,6 +1,5 @@
 = Embed the full ThoughtSpot application
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-title: Embed the Full ThoughtSpot Application
 :page-pageid: tse-fundamentals__lesson-09
@@ -201,4 +200,9 @@ If you run into problems, you can look at the code in the `src` folder in this s
 * index.html
 * tse.js
 
-xref:tse-fundamentals-lesson-08.adoc[< prev] | xref:tse-fundamentals-lesson-10.adoc[next >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-08">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-10">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-10.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-10.adoc
index a29a5fc67..040976076 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-10.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-10.adoc
@@ -1,6 +1,5 @@
 = Style embedded ThoughtSpot content
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-title: Styling Embedded ThoughtSpot Content
 :page-pageid: tse-fundamentals__lesson-10
@@ -89,4 +88,9 @@ The majority of the style is related to colors and fonts. The custom styles also
 
 * None
 
-xref:tse-fundamentals-lesson-09.adoc[< prev] | xref:tse-fundamentals-lesson-11.adoc[next >]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-09">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-11">Next &rarr;</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-11.adoc b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-11.adoc
index 210ed8613..b2d6ed35c 100644
--- a/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-11.adoc
+++ b/modules/tutorials/pages/tse-fundamentals/tse-fundamentals-lesson-11.adoc
@@ -1,6 +1,5 @@
 = Course summary
-:toc: true
-:toclevels: 3
+:toc!:
 
 :page-title: Course Summary
 :page-pageid: tse-fundamentals__lesson-11
@@ -52,4 +51,9 @@ It's also where you enter support tickets and make feature recommendations.
 Finally, we post about upcoming events and important activities.
 It's a great place to get connected and stay informed.
 
-xref:tse-fundamentals-lesson-10.adoc[< prev]
+++++
+<div class="tutorial-pagination">
+<a class="tutorial-pagination__btn tutorial-pagination__prev" href="{{navprefix}}/tutorials/tse-fundamentals/lesson-10">&larr; Previous</a>
+<a class="tutorial-pagination__btn tutorial-pagination__next tutorial-pagination__done" href="{{navprefix}}/tutorials/tutorials-overview">Done</a>
+</div>
+++++
diff --git a/modules/tutorials/pages/tutorials-overview.adoc b/modules/tutorials/pages/tutorials-overview.adoc
index a5e4acc45..ff2cd8ce4 100644
--- a/modules/tutorials/pages/tutorials-overview.adoc
+++ b/modules/tutorials/pages/tutorials-overview.adoc
@@ -14,7 +14,7 @@ xref:tse-fundamentals-intro.adoc[Begin Tutorial >]
 == ThoughtSpot UI elements and style customization
 Tutorial covering how to use customize ThoughtSpot UI elements and styles using Visual Embed SDK.
 
-xref:style-customization_tutorial.adoc[Begin Tutorial >]
+xref:style-customization_tutorial-intro.adoc[Begin Tutorial >]
 
 == ThoughtSpot REST API V2.0
 Tutorial covering how to use ThoughtSpot V2.0 REST API, with examples in both Python and JavaScript.
@@ -24,5 +24,4 @@ xref:rest-api-intro.adoc[Begin Tutorial >]
 == ThoughtSpot Spotter
 Tutorial covering how to integrate ThoughtSpot Spotter AI into a chatbot and embed conversational analytics.
 
-xref:spotter-in-custom-chatbot.adoc[Begin Tutorial >]
-
+xref:spotter-in-custom-chatbot.adoc[Begin Tutorial >]
\ No newline at end of file
diff --git a/package-lock.json b/package-lock.json
index 1f7de314b..9280c70f4 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -20686,6 +20686,15 @@
                 "@sideway/pinpoint": "^2.0.0"
             }
         },
+        "node_modules/jose": {
+            "version": "5.10.0",
+            "resolved": "https://registry.npmjs.org/jose/-/jose-5.10.0.tgz",
+            "integrity": "sha512-s+3Al/p9g32Iq+oqXxkW//7jk2Vig6FF1CFqzVXoTUXt2qz89YWbL+OwS17NFYEvxC35n0FKeGO2LGYSxeM2Gg==",
+            "license": "MIT",
+            "funding": {
+                "url": "https://github.com/sponsors/panva"
+            }
+        },
         "node_modules/js-cookie": {
             "version": "2.2.1",
             "resolved": "https://registry.npmjs.org/js-cookie/-/js-cookie-2.2.1.tgz",
@@ -30174,7 +30183,7 @@
             "version": "8.21.0",
             "resolved": "https://registry.npmjs.org/ws/-/ws-8.21.0.tgz",
             "integrity": "sha512-Vsp28b7DRcimFQvrqu2Wek3z1iYxDCWqHYB8Qsnk/S4RfaCQzPGPyBNuVjJV3cd6UiKtUtp6sNM77gWvzcCH+g==",
-            "dev": true,
+            "devOptional": true,
             "license": "MIT",
             "engines": {
                 "node": ">=10.0.0"
@@ -45489,6 +45498,11 @@
                 "@sideway/pinpoint": "^2.0.0"
             }
         },
+        "jose": {
+            "version": "5.10.0",
+            "resolved": "https://registry.npmjs.org/jose/-/jose-5.10.0.tgz",
+            "integrity": "sha512-s+3Al/p9g32Iq+oqXxkW//7jk2Vig6FF1CFqzVXoTUXt2qz89YWbL+OwS17NFYEvxC35n0FKeGO2LGYSxeM2Gg=="
+        },
         "js-cookie": {
             "version": "2.2.1",
             "resolved": "https://registry.npmjs.org/js-cookie/-/js-cookie-2.2.1.tgz",
@@ -52433,7 +52447,7 @@
             "version": "8.21.0",
             "resolved": "https://registry.npmjs.org/ws/-/ws-8.21.0.tgz",
             "integrity": "sha512-Vsp28b7DRcimFQvrqu2Wek3z1iYxDCWqHYB8Qsnk/S4RfaCQzPGPyBNuVjJV3cd6UiKtUtp6sNM77gWvzcCH+g==",
-            "dev": true,
+            "devOptional": true,
             "requires": {}
         },
         "xdg-app-paths": {
diff --git a/src/assets/styles/index.scss b/src/assets/styles/index.scss
index 6ecb6ed39..bf085df8a 100644
--- a/src/assets/styles/index.scss
+++ b/src/assets/styles/index.scss
@@ -1,3 +1,4 @@
+@import './radiant-colors.css';
 @import './variables.scss';
 @import './padding.scss';
 @import './margin.scss';
@@ -655,7 +656,7 @@ button {
     border-left: 4px solid var(--var-note-color);
     td.content {
         border: 1px solid var(--note-border-color);
-        box-shadow: 0 1px 1px var(--note-border-color);
+        box-shadow: var(--box-shadow);
         border-radius: 5px !important;;
         background: var(--note-block-color);
 
@@ -666,11 +667,20 @@ button {
         padding-bottom: 10px;
     }
 }
+
+// Dark mode: all admonition types share one flat background, overriding
+// each type's light-mode background variable (--note-block-color,
+// --important-block-color, --admonition-background).
+#wrapper[data-theme='dark'] .admonitionblock td.content,
+#docsModal[data-theme='dark'] .admonitionblock td.content {
+    background: var(--admonition-background-dark);
+}
+
 .admonitionblock.important {
     border-left: 4px solid var(--var-important-color);
     td.content {
         border: 1px solid var(--important-border-color);
-        box-shadow: 0 1px 1px var(--important-border-color);
+        box-shadow: var(--box-shadow);
         border-radius: 5px !important;
         background: var(--important-block-color);
     }
@@ -683,9 +693,22 @@ button {
 .admonitionblock.warning {
     border-left: 5px solid $warning-color;
     td.content {
-        border: none !important;
-        border-radius: 0 !important;
-        box-shadow: none !important;
+        border: 1px solid $warning-color;
+        box-shadow: var(--box-shadow);
+        border-radius: 5px !important;
+    }
+    td.icon {
+        left: 20px !important;
+        top: 5px !important;
+    }
+}
+
+.admonitionblock.caution {
+    border-left: 5px solid $caution-color;
+    td.content {
+        border: 1px solid $caution-color;
+        box-shadow: var(--box-shadow);
+        border-radius: 5px !important;
     }
     td.icon {
         left: 20px !important;
@@ -698,7 +721,7 @@ button {
     td.content {
         border: 0 !important;
         border-radius: 0.5 !important;
-        box-shadow: none !important;
+        box-shadow: var(--box-shadow);
     }
     td.icon {
         left: 20px !important;
@@ -710,11 +733,24 @@ button {
 .videoContainer {
     border-radius: 10px;
     overflow-x: auto;
+    overflow-y: hidden;
     width: 100%;
     box-shadow: var(--box-shadow);
     border: 2px solid var(--border-color);
     margin: 10px;
     padding: 15px;
+
+    // The video:: macro only sets width="100%" on the <video> tag, with no
+    // height/aspect-ratio — the browser has nothing to reserve layout space
+    // with until the video's metadata loads async, so the page renders short
+    // and grows later, pushing everything below (incl. Prev/Next) further
+    // down mid-scroll. All tutorial demo videos are 16:9 screen recordings.
+    video {
+        display: block;
+        width: 100%;
+        height: auto;
+        aspect-ratio: 16 / 9;
+    }
 }
 
 summary.title {
@@ -1125,17 +1161,142 @@ a.anchor {
         mask-position: -136px -68px;
     }
 }
+// ── Radiance blob gradient — confined to the header banner only ────────────
+// `.radiance-bg` lives *inside* `.header-banner` (which is `position:
+// relative` and already scoped to the content column, next to the sidebar
+// — see the header-banner rule below) instead of being `position: fixed`
+// relative to the full viewport. A viewport-wide fixed layer bled behind
+// the sidebar, wasting part of the gradient and throwing off the visible
+// color balance. `position: absolute` here is sized relative to
+// `.header-banner`'s own box, so it only ever spans the visible content
+// lane.
+// `bottom: 0` (instead of a fixed/viewport height) makes this match
+// `.header-banner`'s own content-driven height exactly, so the gradient —
+// including its own `overflow: hidden` clipping of the oversized blobs —
+// ends exactly where the banner ends and never bleeds into the cards
+// section below, regardless of viewport height.
+.radiance-bg {
+    position: absolute;
+    inset: 0;
+    // z-index 0 (an explicit stacking context via position + z-index) keeps
+    // this behind the header-banner text/search bar, which are given their
+    // own explicit stacking priority below rather than relying on DOM order.
+    z-index: 0;
+    overflow: hidden;
+    pointer-events: none;
+    background-color: var(--header-banner-base);
+
+    // Blobs (below) are sized/positioned to fill most of the banner box,
+    // which spreads visible color across it. This overlay sits above the
+    // blobs (explicit z-index beats their z-index:auto) and fades from
+    // transparent — letting the blobs show through near the top — to the
+    // flat base color toward the bottom.
+    // A plain 2-stop linear fade (transparent -> solid) has a sharp change
+    // in slope right where it hits full opacity — even though the color
+    // matches the page background exactly, that slope discontinuity reads
+    // as a visible "seam" (a Mach-band effect) right at the banner/cards
+    // boundary. The extra `color-mix` stops below ease the taper in
+    // gradually (S-curve) instead of snapping from "still fading" to
+    // "fully flat", which removes that perceived hard edge.
+    &::after {
+        content: '';
+        position: absolute;
+        inset: 0;
+        z-index: 1;
+        background: linear-gradient(
+            to bottom,
+            transparent 0%,
+            transparent 40%,
+            color-mix(in srgb, var(--header-banner-base) 20%, transparent) 55%,
+            color-mix(in srgb, var(--header-banner-base) 45%, transparent) 68%,
+            color-mix(in srgb, var(--header-banner-base) 75%, transparent) 82%,
+            var(--header-banner-base) 96%,
+            var(--header-banner-base) 100%
+        );
+    }
+
+    .blob {
+        position: absolute;
+        border-radius: 50%;
+        // The radial-gradient's own falloff still reads as a bounded shape
+        // with a visible (if soft) edge — an actual blur is what turns it
+        // into ambient diffuse light with no perceptible boundary.
+        filter: blur(60px);
+    }
+
+    // height/top use `vh` (not `%`) so blob proportions stay the same
+    // regardless of how tall `.radiance-bg` itself is. With `%`, sizing
+    // against this now-short (header-banner-height) box made every blob so
+    // vertically compressed (nearly as tall as the whole clipped area) that
+    // there was no visible core/edge left to show drift against — the
+    // blur+clip just read as a flat wash, and the animation, while still
+    // running, was imperceptible.
+    // Light mode blobs
+    .blob-pink {
+        width: 72%;
+        height: 85vh;
+        left: -14%;
+        top: -18vh;
+        // Toned down from 0.44 — read as too vivid/rose against the reference.
+        background: radial-gradient(ellipse at center, rgba(255, 93, 142, 0.32) 0%, transparent 68%);
+        animation: drift-a 6s ease-in-out infinite alternate;
+    }
+
+    .blob-purple {
+        width: 55%;
+        height: 70vh;
+        left: 4%;
+        top: 35vh;
+        background: radial-gradient(ellipse at center, rgba(138, 93, 255, 0.46) 0%, transparent 66%);
+        animation: drift-b 7s ease-in-out infinite alternate;
+    }
+
+    .blob-blue {
+        width: 70%;
+        height: 80vh;
+        right: -14%;
+        top: -15vh;
+        background: radial-gradient(ellipse at center, rgba(39, 140, 255, 0.42) 0%, transparent 68%);
+        animation: drift-c 5s ease-in-out infinite alternate;
+    }
+
+    .blob-wash-pink {
+        width: 90%;
+        height: 100vh;
+        left: -5%;
+        top: 0;
+        background: radial-gradient(ellipse at 35% 50%, rgba(255, 170, 210, 0.09) 0%, transparent 70%);
+    }
+
+    .blob-wash-blue {
+        width: 90%;
+        height: 100vh;
+        right: -5%;
+        top: 0;
+        background: radial-gradient(ellipse at 65% 50%, rgba(160, 196, 255, 0.12) 0%, transparent 70%);
+    }
+
+    // Dark-only blobs — hidden in light mode
+    .blob-orange,
+    .blob-yellow,
+    .blob-purple-r,
+    .blob-teal {
+        display: none;
+    }
+}
+
 .header-banner {
+    position: relative;
     min-height: 240px;
-    background: var(--header-banner-background);
-    box-shadow: 0 2px 2px #1B3E61;
+    border-bottom: none;
     padding: 30px 0 0 40px;
 
-
     .header-banner-text {
+        position: relative;
+        z-index: 1;
         display: flex;
         flex-direction: column;
-        color: #fff;
+        color: var(--primary-color);
         width: 60%;
         h1 {
             font-size: $font-size-large;
@@ -1149,13 +1310,313 @@ a.anchor {
             letter-spacing: -0.064px;
         }
     }
+
+    #homePageSearchBar {
+        position: relative;
+        z-index: 1;
+    }
+}
+
+// Walkthroughs landing page — one wrapper around the hero text AND the card
+// grid, with the gradient wash as a position:absolute layer sized to that
+// whole wrapper instead of its own fixed-height box. A boxed hero (even a
+// generously tall one) still has a hard bottom edge where overflow:hidden
+// clips the blur/falloff mid-fade — visible as a seam or, with a taller box,
+// a softer rounded silhouette. Sizing the layer to the full page instead
+// means the blobs have all the room they need to fade out completely on
+// their own before any edge is reached, so nothing is left to clip.
+// It also means the gradient no longer reserves its own vertical space, so
+// the hero text and the card grid below sit at normal content spacing
+// instead of being pushed apart by an artificial min-height.
+.walkthroughs-page {
+    position: relative;
+    padding-top: 48px;
+    margin-top: 0;
+    
+    @media (max-width: $mobile-resolution-max) {
+        padding-top: 32px;
+    }
+
+    .radiance-bg {
+        position: absolute;
+        // Bleeds under this page's 60px/60px left-right content padding AND
+        // .doc-wrapper-detail's shared 20px top padding, so the wash
+        // reaches the header on all three edges instead of leaving a plain
+        // gap — matching the home page, which has no such padding to begin
+        // with. Bottom stays 0: the card grid below should keep its normal
+        // padding untouched.
+        inset: -20px -60px 0 -60px;
+
+        @media (max-width: $mobile-resolution-max) {
+            // .doc-wrapper-detail's padding (including its 20px top) drops
+            // to 0 at this breakpoint, so there's no padding left to bleed
+            // under — inset:0 here, not the desktop offsets above.
+            inset: 0;
+        }
+
+        // home's ::after mask (above) uses %-based stops, which are relative
+        // to its OWN box — since that box now spans the whole page, a %
+        // stop would stretch the fade-out proportionally with page length,
+        // tinting the cards. It also only masks down to its own 100% stop;
+        // giving it a shorter *height* instead (tried first) left the
+        // segment between that height and .radiance-bg's real (page-length)
+        // bottom completely unmasked, so the raw blobs showed through at
+        // full strength there with a hard cutoff at the very end — visible
+        // in a screenshot as full-strength color straight through the card
+        // row. Fixed px stops sidestep both: the fade still completes at a
+        // constant depth, and every pixel past 190px keeps resolving to the
+        // final (fully opaque, page-matching) stop, all the way to the
+        // page's actual bottom edge.
+        &::after {
+            background: linear-gradient(
+                to bottom,
+                transparent 0px,
+                transparent 76px,
+                color-mix(in srgb, var(--header-banner-base) 20%, transparent) 104px,
+                color-mix(in srgb, var(--header-banner-base) 45%, transparent) 129px,
+                color-mix(in srgb, var(--header-banner-base) 75%, transparent) 156px,
+                var(--header-banner-base) 182px,
+                var(--header-banner-base) 100%
+            );
+        }
+
+        // pink/purple/blue are home's values (tuned for its taller banner —
+        // h1 + search bar — where their cores sit ~200px down). This page's
+        // hero is just a heading + one line of text, and the gap to the
+        // cards is intentionally kept tight, so the visible band above is
+        // only ~190px (the mask height above) — home's positions would put
+        // each blob's core below that band, in the now-flattened tail, so
+        // only their pale outer edges would show. Pulling all three up
+        // brings their cores (peak color) back inside the visible band —
+        // but that also means this page actually shows each blob's full-
+        // strength core, where home (by design) never does. Same alpha as
+        // home would read far more saturated here, so it's toned down to
+        // land at a similar visual intensity to home/the reference.
+        .blob-pink {
+            top: -31vh;
+            background: radial-gradient(ellipse at center, rgba(255, 93, 142, 0.16) 0%, transparent 68%);
+        }
+
+        .blob-blue {
+            top: -29vh;
+            background: radial-gradient(ellipse at center, rgba(39, 140, 255, 0.20) 0%, transparent 68%);
+        }
+
+        .blob-purple {
+            top: -24vh;
+            background: radial-gradient(ellipse at center, rgba(138, 93, 255, 0.22) 0%, transparent 66%);
+        }
+
+        .blob-wash-pink {
+            background: radial-gradient(ellipse at 35% 50%, rgba(255, 170, 210, 0.06) 0%, transparent 70%);
+        }
+
+        .blob-wash-blue {
+            background: radial-gradient(ellipse at 65% 50%, rgba(160, 196, 255, 0.08) 0%, transparent 70%);
+        }
+    }
+
+    // Guarantees the card grid paints above the gradient layer regardless
+    // of stacking order — harmless once the fade completes well above it,
+    // but avoids relying on that timing.
+    .document-body-wrapper {
+        position: relative;
+        z-index: 1;
+    }
 }
 
-// In-product presentation only: override banner color to match product sidebar (#232F43).
-// Standalone light/dark banner gradient is preserved via var(--header-banner-background) above.
-.embedded-mode .header-banner {
-    background: #232F43;
-    box-shadow: none;
+// Total gap from the top of the page to the first card row is now just
+// this padding-bottom + .tutorial-cards-row's own margin-top (24px,
+// index.scss) — no more artificial min-height holding them apart, which is
+// what made the gap so large before.
+.walkthroughs-hero-text {
+    position: relative;
+    z-index: 1;
+    display: flex;
+    flex-direction: column;
+    align-items: center;
+    text-align: center;
+    color: var(--primary-color);
+    padding: 0 24px 20px;
+
+    h1 {
+        font-size: $font-size-large;
+        font-weight: 400;
+        margin: 0;
+    }
+
+    p {
+        margin: 12px 0 0;
+    }
+}
+
+#wrapper[data-theme='dark'] .radiance-bg,
+#docsModal[data-theme='dark'] .radiance-bg {
+    // Light-only blobs — hidden in dark mode
+    .blob-pink,
+    .blob-purple {
+        display: none;
+    }
+
+    .blob-orange {
+        display: block;
+        width: 65%;
+        height: 80vh;
+        // Shifted in from the corner (-10%) toward center-left so the warm
+        // glow reads as centered on the left half, not hugging the edge.
+        left: -2%;
+        top: 8vh;
+        // Toned down slightly (0.28 -> 0.22) so it stays a subtle accent
+        // and doesn't compete with the purple emphasis at center.
+        background: radial-gradient(ellipse at center, rgba(255, 180, 90, 0.22) 0%, transparent 68%);
+        animation: drift-a 6s ease-in-out infinite alternate;
+    }
+
+    .blob-yellow {
+        display: block;
+        width: 48%;
+        height: 58vh;
+        left: 8%;
+        top: -8vh;
+        background: radial-gradient(ellipse at center, rgba(255, 232, 150, 0.08) 0%, transparent 65%);
+        animation: drift-d 8s ease-in-out infinite alternate;
+    }
+
+    // Same size as light — different position + animation delay
+    .blob-blue {
+        width: 55%;
+        height: 65vh;
+        // Pulled back in (right: -4% -> 6%) so its center sits closer to
+        // purple-r's — with two separate radial falloffs, centers too far
+        // apart leave a dim/desaturated "valley" between them instead of a
+        // smooth hand-off (that's what didn't match the reference). The
+        // wider falloff (62% -> 70%) also softens/extends its own tail so
+        // it carries color further into the middle.
+        right: 6%;
+        top: -10vh;
+        background: radial-gradient(ellipse at center, rgba(39, 140, 255, 0.34) 0%, transparent 70%);
+        animation-delay: -3s;
+    }
+
+    .blob-purple-r {
+        display: block;
+        // Widened further (62% -> 68%) and pulled toward true center
+        // (right: 14% -> 26%) so purple is the highlighted center-of-banner
+        // tone, with strengthened opacity (0.52 -> 0.58) to make it read as
+        // the focal glow while everything else stays subtle around it.
+        width: 68%;
+        height: 68vh;
+        // Pulled in a bit further (26% -> 18%) to close the gap toward blue
+        // — see blob-blue above.
+        right: 18%;
+        top: 6vh;
+        background: radial-gradient(ellipse at center, rgba(138, 93, 255, 0.58) 0%, transparent 72%);
+        animation: drift-b 7s ease-in-out infinite alternate;
+    }
+
+    .blob-teal {
+        display: block;
+        width: 40%;
+        height: 50vh;
+        right: 14%;
+        top: 8vh;
+        background: radial-gradient(ellipse at center, rgba(45, 220, 177, 0.18) 0%, transparent 65%);
+        animation: drift-d 9s ease-in-out infinite alternate;
+    }
+}
+
+// Same fix as the light-mode blobs in .walkthroughs-page above, for dark
+// mode's distinct orange/yellow/purple-r/teal set — their positions above
+// are tuned for home's taller banner, putting every core below this page's
+// much shorter (~190px) visible band.
+#wrapper[data-theme='dark'] .walkthroughs-page .radiance-bg,
+#docsModal[data-theme='dark'] .walkthroughs-page .radiance-bg {
+    // Same reasoning as the light-mode alpha overrides above: home never
+    // shows these blobs' full-strength cores, this page does (that's the
+    // point of the repositioning), so the same alpha reads more saturated
+    // here than on home/the reference.
+    .blob-orange {
+        top: -29vh;
+        background: radial-gradient(ellipse at center, rgba(255, 180, 90, 0.11) 0%, transparent 68%);
+    }
+
+    .blob-yellow {
+        top: -18vh;
+        background: radial-gradient(ellipse at center, rgba(255, 232, 150, 0.05) 0%, transparent 65%);
+    }
+
+    .blob-blue {
+        top: -21vh;
+        background: radial-gradient(ellipse at center, rgba(39, 140, 255, 0.16) 0%, transparent 70%);
+    }
+
+    .blob-purple-r {
+        top: -23vh;
+        background: radial-gradient(ellipse at center, rgba(138, 93, 255, 0.24) 0%, transparent 72%);
+    }
+
+    .blob-teal {
+        top: -14vh;
+        background: radial-gradient(ellipse at center, rgba(45, 220, 177, 0.09) 0%, transparent 65%);
+    }
+}
+
+// Mostly-horizontal drift: large vertical swings pushed blobs down into the
+// `::after` fade-to-flat zone for part of each cycle, dimming the glow right
+// when it should stay visible. Horizontal movement stays large enough to
+// read clearly as motion, without carrying the glow out of the visible band;
+// the smaller scale swing (vs. an earlier, more dramatic pass) keeps the
+// pulse subtle rather than a noticeable "breathing" effect.
+@keyframes drift-a {
+    from { transform: translate(0px, 0px) scale(1.00); }
+    to   { transform: translate(200px, -60px) scale(1.15); }
+}
+
+@keyframes drift-b {
+    from { transform: translate(0px, 0px) scale(1.00); }
+    to   { transform: translate(-160px, 70px) scale(1.18); }
+}
+
+@keyframes drift-c {
+    from { transform: translate(0px, 0px) scale(1.00); }
+    to   { transform: translate(-180px, -50px) scale(1.14); }
+}
+
+@keyframes drift-d {
+    from { transform: translate(0px, 0px) scale(1.00); }
+    to   { transform: translate(140px, 60px) scale(1.16); }
+}
+
+@media (prefers-reduced-motion: reduce) {
+    .radiance-bg .blob {
+        animation: none;
+    }
+}
+
+// In-product presentation only: override banner color to match product sidebar (#232F43),
+// and suppress the page-wide gradient entirely.
+.embedded-mode {
+    .radiance-bg {
+        display: none;
+    }
+
+    .header-banner {
+        background: #232F43;
+        border-bottom: none;
+        box-shadow: none;
+
+        .header-banner-text {
+            color: #fff;
+        }
+    }
+
+    .walkthroughs-page {
+        background: #232F43;
+
+        .walkthroughs-hero-text {
+            color: #fff;
+        }
+    }
 }
 
 // Fluid home page cards for both standalone and embedded presentations.
@@ -1172,6 +1633,140 @@ a.anchor {
     width: auto;
 }
 
+// Tutorials overview cards — same boxDiv look, but sized to fill the
+// grid column edge-to-edge (no width cap) so the three cards in a row
+// read as evenly sized tiles rather than centered fixed-width boxes.
+.tutorialCard {
+    flex: 1 1 280px;
+    width: 100%;
+    margin: 10px;
+    padding: 24px;
+
+    h5 {
+        overflow-wrap: break-word;
+        word-wrap: break-word;
+    }
+
+    p {
+        overflow-wrap: break-word;
+        word-wrap: break-word;
+    }
+}
+
+// Small uppercase label above the card title, e.g. "Tutorial".
+.tutorialCardLabel {
+    font-size: 13px;
+    font-weight: 800;
+    letter-spacing: 0.06em;
+    text-transform: uppercase;
+    color: var(--breadcrums-font-color);
+    margin: 0 0 8px;
+}
+
+// "Start" call-to-action link at the bottom of the card.
+.tutorialCardCta {
+    font-size: 13px;
+    font-weight: 600;
+    letter-spacing: 0.06em;
+    text-transform: uppercase;
+}
+
+// Center the tutorial-card rows as a group and tighten the gap between cards —
+// .row/.col-md-4/.col-md-6 (grid.scss) add 15px of column padding on top of
+// .tutorialCard's own margin, which otherwise leaves ~50px between cards.
+.tutorial-cards-row {
+    justify-content: center;
+
+    // Breathing room between the intro paragraph and the first card row —
+    // only the first row needs it; the row-to-row gap is already handled by .pb-10.
+    &:first-of-type {
+        margin-top: 24px;
+    }
+
+    .col-md-4,
+    .col-md-6 {
+        padding: 0 8px;
+    }
+
+    // .row (grid.scss) pulls the row in by -15px on each side to offset a
+    // Bootstrap-style container gutter that doesn't exist on this page.
+    // Override it here via the compound selector (higher specificity than
+    // the plain .row rule, so it wins regardless of stylesheet order).
+    // The surrounding container padding is symmetric (.doc-wrapper-detail.
+    // doc-walkthroughs + .walkthroughs-body-wrapper), so both margins match.
+    &.row {
+        margin-left: 0;
+        margin-right: 0;
+    }
+}
+
+// Prev/Next footer buttons on tutorial content pages — prev sits on the left,
+// next (or the final "Done") is pushed to the right via margin-left: auto so
+// it stays right-aligned even when prev is absent (first page of a tutorial).
+// (The SpotterCode floating assistant hides itself on tutorials pages — see
+// isTutorialsPath in FloatingAssistant/index.tsx — so no space needs reserving
+// here for it.)
+.tutorial-pagination {
+    display: flex;
+    align-items: center;
+    margin-top: 32px;
+    padding-top: 20px;
+    border-top: 1px solid var(--border-color);
+
+    // `.documentWrapper a, .documentWrapper a:active { color: var(--link-text-color); }`
+    // (Document/index.scss) has specificity 0,1,1 — a single `&__btn` class (0,1,0)
+    // loses to it in the resting state, so the text color only ever showed correctly
+    // under `:hover` (0,2,0). Compounding with the `a` element + parent class here
+    // raises these to 0,2,1 / 0,3,1 so they always win.
+    a.tutorial-pagination__btn {
+        display: inline-flex;
+        align-items: center;
+        padding: 8px 18px;
+        border: 1px solid var(--border-color);
+        border-radius: 6px;
+        font-size: 14px;
+        font-weight: $font-weight-bold;
+        color: var(--rd-comp-color-button-primary-default);
+        text-decoration: none;
+        background: var(--body-background-color);
+        box-shadow: var(--box-shadow);
+        transition: border-color 0.15s ease, color 0.15s ease, box-shadow 0.15s ease;
+
+        &:hover {
+            border-color: var(--rd-comp-color-button-primary-hover);
+            color: var(--rd-comp-color-button-primary-hover);
+            box-shadow: var(--box-shadow-hover);
+        }
+
+        &:active {
+            border-color: var(--rd-comp-color-button-primary-pressed);
+            color: var(--rd-comp-color-button-primary-pressed);
+        }
+    }
+
+    &__next {
+        margin-left: auto;
+    }
+
+    a.tutorial-pagination__done {
+        background: var(--rd-comp-color-button-primary-default);
+        border-color: var(--rd-comp-color-button-primary-default);
+        color: #fff;
+
+        &:hover {
+            background: var(--rd-comp-color-button-primary-hover);
+            border-color: var(--rd-comp-color-button-primary-hover);
+            color: #fff;
+        }
+
+        &:active {
+            background: var(--rd-comp-color-button-primary-pressed);
+            border-color: var(--rd-comp-color-button-primary-pressed);
+            color: #fff;
+        }
+    }
+}
+
 .cardHeading {
     font-size: $font-size-h2;
     color: var(--primary-color) #1d232f;
@@ -1185,6 +1780,20 @@ a.anchor {
 .document-body-wrapper {
     padding: 5px 30px 20px 30px;
 }
+
+// Walkthroughs landing page only — extra breathing room on both sides.
+// Scoped via the class added directly on this page's markup
+// (guided-walkthroughs.adoc), so it can't affect .document-body-wrapper on
+// any other page (e.g. home.adoc uses the same base class).
+.document-body-wrapper.walkthroughs-body-wrapper {
+    padding-left: 60px;
+    padding-right: 60px;
+    margin-top: 60px;
+    @media (max-width: $mobile-resolution-max) {
+        padding-left: 10px;
+        padding-right: 10px;
+    }
+}
 .searchInputBanner {
     padding: 20px 0;
     .searchIcon {
@@ -1226,6 +1835,7 @@ a.anchor {
     width: 100%;
     border-spacing: 0;
     border-collapse: collapse;
+    border: none;
 
 
     /* reset borders applied by the generic table rule */
@@ -1271,7 +1881,7 @@ a.anchor {
     .cl-label p {
         display: inline-block;
         border: 1px solid var(--rel-notes-pill-border);
-        background-color: var(--rel-notes-tag-bg-color);
+        background-color: var(--rd-comp-color-button-primary-on-color-hover);
         color: var(--rel-notes-tag-text);
         font-size: 14px;
         font-weight: 300;
diff --git a/src/assets/styles/radiant-colors.css b/src/assets/styles/radiant-colors.css
new file mode 100644
index 000000000..d6e7d7eb4
--- /dev/null
+++ b/src/assets/styles/radiant-colors.css
@@ -0,0 +1,237 @@
+/*
+ * Radiant colour tokens — ThoughtSpot
+ * Same values the product ships. Generated from @thoughtspot/radiant-styles.
+ *
+ * Light is the default (:root). Dark applies when data-theme="dark" is set on
+ * a container — same contract the docs site already uses.
+ *
+ * --rd-sys-color-*   system tokens (surfaces, text, borders)
+ * --rd-comp-color-*  component tokens (buttons, chips, toggles)
+ */
+
+
+/* Light theme (default) */
+:root {
+    --rd-sys-color-background-base: #ffffff;
+    --rd-sys-color-background-sunken: #f6f8fa;
+    --rd-sys-color-background-raised: #ffffff;
+    --rd-sys-color-background-active: #ffffff;
+    --rd-sys-color-background-secondary-action: #eaedf2;
+    --rd-sys-color-background-on-base: #f6f8fa;
+    --rd-sys-color-background-brand: #2770ef;
+    --rd-sys-color-background-overlay: rgba(31, 38, 50, 0.8);
+    --rd-sys-color-background-inverse: #1d232f;
+    --rd-sys-color-background-success: #e0f8ef;
+    --rd-sys-color-background-warning: #fff8e5;
+    --rd-sys-color-background-failure: #ffebec;
+    --rd-sys-color-background-information: #dee8fa;
+    --rd-sys-color-background-ghost-hover: rgba(192, 198, 207, 0.12);
+    --rd-sys-color-background-secondary-hover: #dbdfe7;
+    --rd-sys-color-background-ghost-highlight: rgba(113, 161, 244, 0.12);
+    --rd-sys-color-background-accent-green: #e0f8ef;
+    --rd-sys-color-background-accent-yellow: #fff8e5;
+    --rd-sys-color-background-accent-red: #ffebec;
+    --rd-sys-color-background-accent-blue: #dee8fa;
+    --rd-sys-color-background-accent-gray: #f6f8fa;
+    --rd-sys-color-background-accent-purple-subtle: #f0ebff;
+    --rd-sys-color-background-accent-purple-bold: #8c62f5;
+    --rd-sys-color-content-primary: #1d232f;
+    --rd-sys-color-content-secondary: #777e8b;
+    --rd-sys-color-content-tertiary: #c0c6cf;
+    --rd-sys-color-content-brand: #2770ef;
+    --rd-sys-color-content-inverse: #ffffff;
+    --rd-sys-color-content-success: #06bf7f;
+    --rd-sys-color-content-warning: #fcc838;
+    --rd-sys-color-content-failure: #e22b3d;
+    --rd-sys-color-content-information: #2770ef;
+    --rd-sys-color-content-accent-green: #06bf7f;
+    --rd-sys-color-content-accent-yellow: #fcc838;
+    --rd-sys-color-content-accent-red: #e22b3d;
+    --rd-sys-color-content-accent-gray: #777e8b;
+    --rd-sys-color-content-accent-blue: #2770ef;
+    --rd-sys-color-content-accent-purple: #8c62f5;
+    --rd-sys-color-border-bold: #c0c6cf;
+    --rd-sys-color-border-bold-hover: #a5acb9;
+    --rd-sys-color-border-subtle: #eaedf2;
+    --rd-sys-color-border-subtle-hover: #dbdfe7;
+    --rd-sys-color-border-brand: #2770ef;
+    --rd-sys-color-border-warning: #fcc838;
+    --rd-sys-color-border-failure: #e22b3d;
+    --rd-sys-color-border-focus: #71a1f4;
+    --rd-sys-color-border-gap: #ffffff;
+    --rd-sys-color-border-accent-green: #06bf7f;
+    --rd-sys-color-border-accent-yellow: #fcc838;
+    --rd-sys-color-border-accent-red: #e22b3d;
+    --rd-sys-color-border-accent-gray: #777e8b;
+    --rd-sys-color-border-accent-blue: #2770ef;
+    --rd-sys-color-border-accent-purple: #8c62f5;
+}
+
+/* Dark theme */
+[data-theme="dark"] {
+    --rd-sys-color-background-sunken: #0a0a0b;
+    --rd-sys-color-background-base: #131416;
+    --rd-sys-color-background-raised: #26282c;
+    --rd-sys-color-background-active: #60656c;
+    --rd-sys-color-background-secondary-action: #2f3237;
+    --rd-sys-color-background-on-base: #1a1b1e;
+    --rd-sys-color-background-brand: #71a1f4;
+    --rd-sys-color-background-overlay: rgba(0, 3, 10, 0.73);
+    --rd-sys-color-background-inverse: #dfe0e2;
+    --rd-sys-color-background-success: #003b26;
+    --rd-sys-color-background-warning: #4f3d09;
+    --rd-sys-color-background-failure: #3d090e;
+    --rd-sys-color-background-information: #71a1f4;
+    --rd-sys-color-background-ghost-hover: rgba(192, 198, 207, 0.12);
+    --rd-sys-color-background-secondary-hover: #45494e;
+    --rd-sys-color-background-ghost-highlight: rgba(113, 161, 244, 0.12);
+    --rd-sys-color-background-accent-green: #003b26;
+    --rd-sys-color-background-accent-yellow: #4f3d09;
+    --rd-sys-color-background-accent-red: #3d090e;
+    --rd-sys-color-background-accent-blue: #082559;
+    --rd-sys-color-background-accent-gray: #26282c;
+    --rd-sys-color-background-accent-purple-subtle: #422e75;
+    --rd-sys-color-background-accent-purple-bold: #b094f8;
+    --rd-sys-color-content-primary: #dfe0e2;
+    --rd-sys-color-content-secondary: #979ba0;
+    --rd-sys-color-content-tertiary: #60656c;
+    --rd-sys-color-content-brand: #71a1f4;
+    --rd-sys-color-content-inverse: #131416;
+    --rd-sys-color-content-success: #56d3a8;
+    --rd-sys-color-content-warning: #fcd977;
+    --rd-sys-color-content-failure: #f47e89;
+    --rd-sys-color-content-information: x;
+    --rd-sys-color-content-accent-green: #56d3a8;
+    --rd-sys-color-content-accent-yellow: #fcd977;
+    --rd-sys-color-content-accent-red: #f47e89;
+    --rd-sys-color-content-accent-gray: #60656c;
+    --rd-sys-color-content-accent-blue: #71a1f4;
+    --rd-sys-color-content-accent-purple: #b094f8;
+    --rd-sys-color-border-bold: #60656c;
+    --rd-sys-color-border-bold-hover: #808389;
+    --rd-sys-color-border-subtle: #2f3237;
+    --rd-sys-color-border-subtle-hover: #45494e;
+    --rd-sys-color-border-brand: #71a1f4;
+    --rd-sys-color-border-warning: #fcd977;
+    --rd-sys-color-border-failure: #f47e89;
+    --rd-sys-color-border-focus: #2770ef;
+    --rd-sys-color-border-gap: #131416;
+    --rd-sys-color-border-accent-green: #56d3a8;
+    --rd-sys-color-border-accent-yellow: #fcd977;
+    --rd-sys-color-border-accent-red: #f47e89;
+    --rd-sys-color-border-accent-gray: #60656c;
+    --rd-sys-color-border-accent-blue: #71a1f4;
+    --rd-sys-color-border-accent-purple: #b094f8;
+}
+
+/* ---------- component tokens ---------- */
+
+/* Light theme (default) */
+:root {
+    --rd-comp-color-button-bg-overlay: rgba(32, 41, 58, 0.6);
+    --rd-comp-color-button-primary-default: #2770ef;
+    --rd-comp-color-button-primary-hover: #2359b6;
+    --rd-comp-color-button-primary-pressed: #163772;
+    --rd-comp-color-button-primary-on-color-default: #ffffff;
+    --rd-comp-color-button-primary-on-color-hover: #dee8fa;
+    --rd-comp-color-button-primary-on-color-pressed: #cedcf5;
+    --rd-comp-color-button-secondary-default: #eaedf2;
+    --rd-comp-color-button-secondary-hover: #dbdfe7;
+    --rd-comp-color-button-secondary-pressed: #c0c6cf;
+    --rd-comp-color-button-tertiary-hover: rgba(192, 198, 207, 0.12);
+    --rd-comp-color-button-tertiary-pressed: rgba(113, 161, 244, 0.12);
+    --rd-comp-color-chip-loading-default: #f6f8fa;
+    --rd-comp-color-chip-attribute-default: #dee8fa;
+    --rd-comp-color-chip-attribute-hover: #cedcf5;
+    --rd-comp-color-chip-attribute-pressed: #abc7f9;
+    --rd-comp-color-chip-attribute-icon: #2770ef;
+    --rd-comp-color-chip-attribute-active-border: #cedcf5;
+    --rd-comp-color-chip-measure-default: #e0f8ef;
+    --rd-comp-color-chip-measure-hover: #c7f2e3;
+    --rd-comp-color-chip-measure-pressed: #9be5cb;
+    --rd-comp-color-chip-measure-icon: #06bf7f;
+    --rd-comp-color-chip-measure-active-border: #c7f2e3;
+    --rd-comp-color-chip-filter-default: #eaedf2;
+    --rd-comp-color-chip-filter-hover: #dbdfe7;
+    --rd-comp-color-chip-filter-pressed: #c0c6cf;
+    --rd-comp-color-chip-filter-icon: #777e8b;
+    --rd-comp-color-chip-filter-active-border: #dbdfe7;
+    --rd-comp-color-chip-date-default: #f0ebff;
+    --rd-comp-color-chip-date-hover: #e3d9fc;
+    --rd-comp-color-chip-date-pressed: #d1c0fb;
+    --rd-comp-color-chip-date-icon: #8c62f5;
+    --rd-comp-color-chip-date-active-border: #e3d9fc;
+    --rd-comp-color-chip-input-default: #ffffff;
+    --rd-comp-color-chip-input-hover: #f6f8fa;
+    --rd-comp-color-chip-input-pressed: #eaedf2;
+    --rd-comp-color-chip-input-selected-default: #4a515e;
+    --rd-comp-color-chip-input-selected-hover: #323946;
+    --rd-comp-color-chip-input-selected-pressed: #1d232f;
+    --rd-comp-color-chip-error-default: #ffebec;
+    --rd-comp-color-chip-error-hover: #fcd4d7;
+    --rd-comp-color-chip-error-active-border: #dbdfe7;
+    --rd-comp-color-progress-track-active: #f0ebff;
+    --rd-comp-color-progress-track-empty: #eaedf2;
+    --rd-comp-color-progress-indicator-default: #8c62f5;
+    --rd-comp-color-segmented-control-content-active: #2770ef;
+    --rd-comp-color-toggle-track-off: #c0c6cf;
+    --rd-comp-color-toggle-track-on: #cedcf5;
+    --rd-comp-color-toggle-thumb-off: #ffffff;
+    --rd-comp-color-toggle-thumb-on: #2770ef;
+    --rd-comp-color-toggle-thumb-outline-off: #dbdfe7;
+}
+
+/* Dark theme */
+[data-theme="dark"] {
+    --rd-comp-color-button-bg-overlay: rgba(32, 41, 58, 0.6);
+    --rd-comp-color-button-primary-default: #71a1f4;
+    --rd-comp-color-button-primary-hover: #abc7f9;
+    --rd-comp-color-button-primary-pressed: #cedcf5;
+    --rd-comp-color-button-primary-on-color-default: #ffffff;
+    --rd-comp-color-button-primary-on-color-hover: #dee8fa;
+    --rd-comp-color-button-primary-on-color-pressed: #cedcf5;
+    --rd-comp-color-button-secondary-default: #26282c;
+    --rd-comp-color-button-secondary-hover: #2f3237;
+    --rd-comp-color-button-secondary-pressed: #60656c;
+    --rd-comp-color-button-tertiary-hover: rgba(192, 198, 207, 0.12);
+    --rd-comp-color-button-tertiary-pressed: rgba(113, 161, 244, 0.12);
+    --rd-comp-color-chip-loading-default: #1a1b1e;
+    --rd-comp-color-chip-attribute-default: #082559;
+    --rd-comp-color-chip-attribute-hover: #163772;
+    --rd-comp-color-chip-attribute-pressed: #2359b6;
+    --rd-comp-color-chip-attribute-icon: #71a1f4;
+    --rd-comp-color-chip-attribute-active-border: #163772;
+    --rd-comp-color-chip-measure-default: #003b26;
+    --rd-comp-color-chip-measure-hover: #025b3c;
+    --rd-comp-color-chip-measure-pressed: #049160;
+    --rd-comp-color-chip-measure-icon: #56d3a8;
+    --rd-comp-color-chip-measure-active-border: #025b3c;
+    --rd-comp-color-chip-filter-default: #26282c;
+    --rd-comp-color-chip-filter-hover: #2f3237;
+    --rd-comp-color-chip-filter-pressed: #45494e;
+    --rd-comp-color-chip-filter-icon: #808389;
+    --rd-comp-color-chip-filter-active-border: #2f3237;
+    --rd-comp-color-chip-date-default: #210f4f;
+    --rd-comp-color-chip-date-hover: #422e75;
+    --rd-comp-color-chip-date-pressed: #6847ba;
+    --rd-comp-color-chip-date-icon: #b094f8;
+    --rd-comp-color-chip-date-active-border: #422e75;
+    --rd-comp-color-chip-input-default: #0a0a0b;
+    --rd-comp-color-chip-input-hover: #1a1b1e;
+    --rd-comp-color-chip-input-pressed: #26282c;
+    --rd-comp-color-chip-input-selected-default: #afb2b6;
+    --rd-comp-color-chip-input-selected-hover: #c7c9cc;
+    --rd-comp-color-chip-input-selected-pressed: #dfe0e2;
+    --rd-comp-color-chip-error-default: #3d090e;
+    --rd-comp-color-chip-error-hover: #721f27;
+    --rd-comp-color-chip-error-active-border: #2f3237;
+    --rd-comp-color-progress-track-active: #210f4f;
+    --rd-comp-color-progress-track-empty: #1d232f;
+    --rd-comp-color-progress-indicator-default: #b094f8;
+    --rd-comp-color-segmented-control-content-active: #dfe0e2;
+    --rd-comp-color-toggle-track-off: #45494e;
+    --rd-comp-color-toggle-track-on: #163772;
+    --rd-comp-color-toggle-thumb-off: #afb2b6;
+    --rd-comp-color-toggle-thumb-on: #71a1f4;
+    --rd-comp-color-toggle-thumb-outline-off: #afb2b6;
+}
diff --git a/src/assets/styles/variables.scss b/src/assets/styles/variables.scss
index cb6346fc1..a3f74bb95 100644
--- a/src/assets/styles/variables.scss
+++ b/src/assets/styles/variables.scss
@@ -36,7 +36,13 @@ $highlight-fadedgreen: #dfd;
 $highlight-yellow: #e18114;
 $highlight-cyan: #78d9ec;
 
-$header-zIndex: 10;
+// `header` is `position: absolute` + this z-index, which makes it its own
+// stacking context — so no descendant (e.g. the version/Resources dropdown
+// menus) can ever paint above content outside `header`, no matter how high
+// a z-index that descendant sets locally. Must stay above the SpotterCode
+// floating-assistant panel/chip (FloatingAssistant/index.scss, z-index up
+// to 1002) so header's dropdowns aren't trapped behind it.
+$header-zIndex: 1200;
 $header-logo-width: 273px;
 $header-link-margin: 45px;
 $font-weight-normal: 300;
@@ -147,7 +153,7 @@ $rem-base: 18;
 $body-font-size-desktop: 1.125em; /* 18px */
 $body-font-size-print: 0.9375em; /* 15px */
 $body-line-height: 1.15;
-$body-font-family: 'Roboto', sans-serif;
+$body-font-family: Optimo-Plain, Roboto, sans-serif;
 $body-font-weight-bold: 500;
 $monospace-font-family: 'Roboto Mono', monospace;
 $monospace-font-weight-bold: 500;
@@ -175,8 +181,106 @@ $tag-color-yellow: #ffbc00;
 $tag-color-white: var(--body-background-color);
 $tag-color-light: $lightgrey;
 
+// ---------------------------------------------------------------------------
+// radiant remap â a custom property whose value contains var() is resolved on
+// the element where it is DECLARED, not where it is used. If we alias
+//     --body-background-color: var(--rd-sys-color-background-base);
+// only on :root, dark mode would resolve against :root's (light) token and
+// silently stop working. So the SAME alias block must be emitted on every
+// element that carries data-theme. Hence one mixin, included twice.
+// ---------------------------------------------------------------------------
+
+@mixin ts-docs-radiant-aliases {
+    /* --- surfaces --- */
+    --body-background-color:      var(--rd-sys-color-background-base);
+    --table-header-bg:            #f6f8fa;
+    --copy-page-menu-bg:          #f6f8fa;
+    --left-nav-color:             var(--rd-sys-color-background-raised);
+    --panel-bg-color:             var(--rd-sys-color-background-on-base);
+    --block-background:           var(--rd-sys-color-background-on-base);
+    --admonition-background:      var(--rd-sys-color-background-on-base);
+    --code-text-bg:                var(--rd-sys-color-background-sunken);
+    --code-block-light:           var(--rd-sys-color-background-sunken);
+    --was-helpful-bg:              var(--rd-sys-color-background-sunken);
+    --back-button-background:     var(--rd-sys-color-background-secondary-action);
+    --copy-btn-bg:                 var(--rd-sys-color-background-secondary-action);
+    --copy-btn-hover:               var(--rd-sys-color-background-secondary-hover);
+    --announcement-block-color:   var(--rd-sys-color-background-secondary-action);
+
+    /* --- text / icons --- */
+    --primary-color:               var(--rd-sys-color-content-primary);
+    --sidebar-title:                var(--rd-sys-color-content-primary);
+    --side-nav-text:                var(--rd-sys-color-content-primary);
+    --back-button-color:           var(--rd-sys-color-content-primary);
+    --announcement-text-color:     var(--rd-sys-color-content-primary);
+    --breadcrums-font-color:        var(--rd-sys-color-content-secondary);
+    --icon-color:                   var(--rd-sys-color-content-secondary);
+    --var-docmap-nested-color:     var(--rd-sys-color-content-secondary);
+    --header-primary-color:        var(--rd-sys-color-content-inverse);
+
+    /* --- links / active states --- */
+    --link-text-color:             var(--rd-sys-color-content-brand);
+    --side-nav-active-text:        var(--rd-sys-color-content-brand);
+    --side-nav-active-bg:          var(--rd-sys-color-background-ghost-highlight);
+    --secondary-color:             var(--rd-sys-color-content-brand);
+    // Docmap (right-nav) hover/active text + border. Deliberately its own
+    // alias rather than reusing --var-note-color: that one maps to
+    // --rd-sys-color-content-information, whose dark-theme value in
+    // radiant-colors.css is a broken placeholder ("x", not a real color),
+    // so anything using it renders with no visible color in dark mode.
+    // --rd-sys-color-content-brand matches --link-text-color exactly and is
+    // valid in both themes.
+    --docmap-active-color:          var(--rd-sys-color-content-brand);
+
+    /* --- borders --- */
+    --border-color:                 var(--rd-sys-color-border-subtle);
+    --border-color-tr:              var(--rd-sys-color-border-subtle);
+    --was-helpful-border:           var(--rd-sys-color-border-subtle);
+    --docmap-border-color:          var(--rd-sys-color-border-bold);
+    --search-border-color:          var(--rd-sys-color-border-bold);
+    --sidebar-connector-color:      var(--rd-sys-color-border-bold);
+    --important-border-color:       var(--rd-sys-color-border-bold);
+    --border-color-home-search:     var(--rd-sys-color-border-bold-hover);
+    --scrollbar-color:               var(--rd-sys-color-border-bold-hover);
+    --docmap-scrollbar-color:        var(--rd-sys-color-content-brand);
+
+    /* --- admonitions / status --- */
+    --note-block-color:            var(--rd-sys-color-background-information);
+    --note-border-color:           var(--rd-sys-color-border-brand);
+    // --rd-sys-color-content-information is broken in dark mode (see
+    // --docmap-active-color note above: its dark value in radiant-colors.css
+    // is the placeholder "x", not a real color), which made the NOTE block's
+    // left border disappear in dark mode. --rd-sys-color-content-brand is
+    // byte-identical to it in light mode and valid in both themes.
+    --var-note-color:               var(--rd-sys-color-content-brand);
+    --var-important-color:          var(--rd-sys-color-content-failure);
+    --important-block-color:        var(--rd-sys-color-background-on-base);
+
+    /* --- release-notes pills --- */
+    --rel-notes-tag-bg-color:       var(--rd-comp-color-button-primary-on-color-hover);
+    --rel-notes-tag-text:           var(--rd-sys-color-content-information);
+    --rel-notes-pill-border:        var(--rd-sys-color-content-information);
+
+    /* --- elevation ---
+       $box-shadow-search-box is already byte-identical to radiant's
+       shadow-menu token, so these are a straight swap. */
+    --box-shadow:       0 0 4px rgba(25, 35, 49, 0.10), 0 2px 4px rgba(25, 35, 49, 0.04);
+    --box-shadow-hover: 0 0 4px rgba(25, 35, 49, 0.08), 0 12px 24px rgba(25, 35, 49, 0.12);
+}
+
+// Dark-mode elevation is NOT the same shadow at higher opacity â radiant uses a
+// separate ramp, so this one group does need a per-theme override.
+@mixin ts-docs-radiant-elevation-dark {
+    --box-shadow:       0 0 4px rgba(0, 0, 0, 0.24), 0 4px 8px rgba(0, 0, 0, 0.20);
+    --box-shadow-hover: 0 0 6px rgba(0, 0, 0, 0.16), 0 14px 28px rgba(0, 0, 0, 0.32);
+}
+
 :root {
-    /* Brand tokens */
+    @include ts-docs-radiant-aliases;
+
+    /* ---- NOT remapped: marketing/brand chrome. These are deliberate brand
+       colours, not product-surface colours â radiant has no token for them and
+       shouldn't. Left exactly as-is. ---- */
     --ts-black: #000000;
     --ts-grey: #f1f4f8;
     --ts-blue: #0568fa;
@@ -186,48 +290,21 @@ $tag-color-light: $lightgrey;
     --ts-purple: #dcadff;
     --ts-yellow: #fcde18;
 
-    --body-background-color: #fff;
-    --primary-color: #1d232f;
-    --header-primary-color: #fff;
     --header-color: #08062B;
     --header-border-color: #08072C;
     --header-link-color: rgba(255, 255, 255, 0.85);
     --nav-bar-color: #08062B;
-    --left-nav-color: #fff;
-    --header-banner-background: linear-gradient(180deg, #08062B, #122246, #122246);
-    --panel-bg-color: #f1f4f8;
     --secondary-header-bg: #08062B;
     --secondary-header-border: #323946;
     --secondary-header-text: #f1f4f8;
     --secondary-header-active: #0568fa;
-    --rel-notes-tag-bg-color: #dce5f9;
-    --rel-notes-tag-text: #0568fa;
-    --rel-notes-pill-border: #aac2f8;    
-    --breadcrums-font-color: #5f6368;
-    --docmap-border-color: #d9d9d9;
-    --border-color-home-search: #a5acb9;
-    --announcement-block-color: #e1e1e1;
-    --announcement-text-color: #1d232f;
-    --admonition-background: #f1f4f8;
+    --nav-accent-color: #A9E8FF;
+    --header-background-color: #012676;
+    --header-banner-base: #fff;
+    --left-nav-color: #f6f8fa;
     --code-block-color: #0d1117;
-    --code-block-light: #f6f8fa;
     --code-text-color: #e6edf3;
-    --code-text-bg: #f6f8fa;
-    --side-nav-text: #374151;
-    --sidebar-title: #393939;
-    --side-nav-active-bg: rgba(5, 104, 250, 0.08);
-    --side-nav-active-text: #0568fa;
     --text-color-code-lang: #fff;
-    --icon-color: #6b7280;
-    --back-button-color: #1d232f;
-    --back-button-background: #eaedf2;
-    --block-background: #f1f4f8;
-    --search-border-color: #cccdcd;
-    --border-color: #eaedf2;
-    --table-header-color: #fff;
-    --border-color-tr: #e5e7eb;
-    --scrollbar-color: #a5acb9;
-    --docmap-scrollbar-color: #0568fa;
     --color-jet-70: #d14;
     --highlight-purple: #9334e6;
     --highlight-green: #188038;
@@ -235,75 +312,46 @@ $tag-color-light: $lightgrey;
     --highlight-lightblue: #0086b3;
     --highlight-darkblue: #000080;
     --highlight-blue: #458;
-    --highlight-orange: ;
     --highlight-yellow: #e1b514;
+    --highlight-orange: $warning-color;
     --highlight-darkred: #900;
     --highlight-lilac: #d7aefb;
     --highlight-violet: #990073;
-    --secondary-color: #393939;
-    --link-text-color: #0568fa;
-    --header-background-color: #012676;
-    --var-note-color: #0568fa;
-    --note-block-color: #eef7ff;
-    --note-border-color: #7492d5;
-    --var-important-color: #e22b3d;
-    --important-border-color: #cccdcd;
-    --important-block-color: #f1f4f8;
-    --var-docmap-nested-color: #6b7280;
-    --box-shadow: 0 1px 3px 0 rgba(0, 0, 0, 0.1), 0 1px 2px 0 rgba(0, 0, 0, 0.06);
-    --box-shadow-hover: 0 4px 6px -1px rgba(0, 0, 0, 0.1),
-        0 2px 4px -1px rgba(0, 0, 0, 0.06);
-    --sidebar-connector-color: #d1d5db;
-    --copy-btn-bg: #f3f4f6;
-    --copy-btn-hover: #e5e7eb;
-    --was-helpful-bg: #f9fafb;
-    --was-helpful-border: #e5e7eb;
 }
 
 #wrapper[data-theme='dark'],
 #docsModal[data-theme='dark'] {
+    // Same aliases, re-declared so they resolve against the DARK tokens.
+    @include ts-docs-radiant-aliases;
+    @include ts-docs-radiant-elevation-dark;
 
-    --body-background-color: #161b22;
-    --header-color: #0d1117;
-    --header-border-color: #cccdcd;
-    --header-link-color: rgba(255, 255, 255, 0.85);
-    --nav-bar-color: #0d1117;
-    --left-nav-color: #161b22;
-    --panel-bg-color: #0d1117;
-    --secondary-header-bg: #0d1117;
-    --secondary-header-border: #393939;
+    /* brand chrome â dark variants previously hardcoded here */
+    --header-color: #26282c;
+    --header-border-color: #34363C;
+    --nav-bar-color: #26282C;
+    --secondary-header-bg: #26282C;
+    --secondary-header-border: #34363C;
     --secondary-header-text: #c9d1d9;
     --secondary-header-active: #0086b3;
-    --primary-color: #cccdcd;
-    --header-primary-color: #cccdcd;
-    --header-banner-background: linear-gradient(180deg, #0d1117, #1B3E61);
-    --breadcrums-font-color: #8b949e;
-    --docmap-border-color: #30363d;
-    --rel-notes-tag-bg-color: #232F43;
-    --rel-notes-tag-text: #fff;
-    --rel-notes-pill-border: #74daff;
-    --announcement-block-color: #3c4356;
-    --announcement-text-color: #e6edf3;
-    --admonition-background: #161b22;
-    --code-block-color:#1e2430;
-    --code-block-light: #21262d;
-    --code-text-bg: #21262d;
+    --nav-accent-color: #71a1f4;
+    --header-banner-base: #1F2024;
+    --header-background-color: #26282C;
+
+    /* main content surface reads darker/blacker than the raised header/left-nav in the product */
+    --body-background-color: #1F2024;
+    --table-header-bg: #26282C;
+    --copy-page-menu-bg: #26282C;
+    --rel-notes-tag-bg-color: #A0C4FF;
+    --rel-notes-tag-text: #71a1f4;
+    --rel-notes-pill-border: #278CFF;
+    /* dark-mode-only admonition background — light mode keeps its existing
+       per-type values (--note-block-color, --important-block-color,
+       --admonition-background) unchanged */
+    --admonition-background-dark: #26282C;
+    /* code-syntax dark set â unchanged */
+    --code-block-color: #26282C;
     --code-text-color: #e6edf3;
-    --sidebar-title: #5f6368;
-    --side-nav-text: #c9d1d9;
-    --side-nav-active-bg: rgba(116, 218, 255, 0.12);
-    --side-nav-active-text: #74daff;
     --text-color-code-lang: #8b949e;
-    --icon-color: #8b949e;
-    --back-button-color: #e6edf3;
-    --table-header-color: #21262d;
-    --back-button-background: #21262d;
-    --block-background: #161b22;
-    --border-color: #30363d;
-    --search-border-color: #30363d;
-    --border-color-home-search: #a5acb9;
-    --border-color-tr: #21262d;
-    --scrollbar-color: #30363d;
     --color-jet-70: #ffa657;
     --highlight-purple: #d2a8ff;
     --highlight-green: #3fb950;
@@ -314,25 +362,6 @@ $tag-color-light: $lightgrey;
     --highlight-darkred: #ffa198;
     --highlight-lilac: #b083f0;
     --highlight-violet: #f8bbd0;
-    --secondary-color: #74daff;
-    --link-text-color: #74daff;
-    --header-background-color: #012676;
-    --var-note-color: #74daff;
-    --note-block-color: #1e2430;
-    --note-border-color: #74daff;
-    --var-important-color: #e22b3d;
-    --important-border-color: #30363d;
-    --important-block-color: #1e2430;
-    --var-docmap-nested-color: #8b949e;
-    --sidebar-connector-color: #30363d;
-    --copy-btn-bg: #21262d;
-    --copy-btn-hover: #30363d;
-    --was-helpful-bg: #161b22;
-    --was-helpful-border: #30363d;
-
-    --box-shadow: 0 1px 3px 0 rgba(0, 0, 0, 0.4), 0 1px 2px 0 rgba(0, 0, 0, 0.3);
-    --box-shadow-hover: 0 4px 6px -1px rgba(0, 0, 0, 0.4),
-        0 2px 4px -1px rgba(0, 0, 0, 0.3);
 
     .header-banner {
         box-shadow: none;
diff --git a/src/components/Breadcrums/index.tsx b/src/components/Breadcrums/index.tsx
index 3a7449604..fbf5f28f6 100644
--- a/src/components/Breadcrums/index.tsx
+++ b/src/components/Breadcrums/index.tsx
@@ -6,6 +6,12 @@ import './index.scss';
 type BreadcrumsProps = {
     pageid?: string;
     breadcrumsData: any;
+    // Individual walkthrough step pages use compound pageids
+    // ({subdir}__{finalSegment}) that only ever match the leaf node in
+    // nav-walkthroughs.adoc's own list, not the "Walkthroughs" entry that lives
+    // in nav.adoc — so there's no way back to the overview from a step page
+    // other than this explicit crumb.
+    showWalkthroughsCrumb?: boolean;
 };
 
 const Breadcrums: React.FC<BreadcrumsProps> = (props: BreadcrumsProps) => {
@@ -23,6 +29,13 @@ const Breadcrums: React.FC<BreadcrumsProps> = (props: BreadcrumsProps) => {
                                 Developer Guides
                             </a>
                         </li>
+                        {props.showWalkthroughsCrumb && (
+                            <li>
+                                <a href="/docs/tutorials/walkthroughs">
+                                    Walkthroughs
+                                </a>
+                            </li>
+                        )}
                         {breadcrums.map(({ name, href }) => (
                             <li key={`${name}-${href}`}>
                                 {href ? <a href={href}>{name}</a> : name}
diff --git a/src/components/CopyPageDropdown/index.scss b/src/components/CopyPageDropdown/index.scss
index cda100ace..498bbe207 100644
--- a/src/components/CopyPageDropdown/index.scss
+++ b/src/components/CopyPageDropdown/index.scss
@@ -54,20 +54,32 @@
         }
     }
 
+    #wrapper[data-theme='dark'] &__trigger,
+    #docsModal[data-theme='dark'] &__trigger {
+        background: #26282C;
+        border-color: #26282C;
+    }
+
     &__menu {
         position: absolute;
         top: calc(100% + 6px);
         right: 0;
-        background: var(--body-background-color);
+        background: var(--copy-page-menu-bg);
         border: 1px solid var(--border-color, #d1d5db);
         border-radius: 8px;
-        box-shadow: 0 8px 24px rgba(0, 0, 0, 0.12);
-        min-width: 240px;
+        box-shadow: var(--box-shadow-hover);
+        min-width: 16rem;
         padding: 6px;
         z-index: 50;
         animation: cpDropFadeIn 0.12s ease;
     }
 
+    #wrapper[data-theme='light'] &__menu,
+    #docsModal[data-theme='light'] &__menu {
+        border-color: #cccdcd;
+        box-shadow: none;
+    }
+
     &__item {
         display: flex;
         align-items: flex-start;
diff --git a/src/components/DevDocTemplate/index.tsx b/src/components/DevDocTemplate/index.tsx
index d6961ab96..3d6f2e643 100644
--- a/src/components/DevDocTemplate/index.tsx
+++ b/src/components/DevDocTemplate/index.tsx
@@ -12,7 +12,7 @@ import { BiSearch } from '@react-icons/all-files/bi/BiSearch';
 import { Analytics } from '@vercel/analytics/react';
 import { Seo } from '../Seo';
 import { queryStringParser, isPublicSite } from '../../utils/app-utils';
-import { passThroughHandler, fetchChild } from '../../utils/doc-utils';
+import { passThroughHandler, fetchChild, getPageIdFromHref } from '../../utils/doc-utils';
 import Header from '../Header';
 import SecondaryHeader, { DocCategory, CATEGORY_PAGEIDS, CATEGORY_NAV_ID } from '../SecondaryHeader';
 import LeftSidebar from '../LeftSidebar';
@@ -185,6 +185,12 @@ const isVersionedIframe = VERSION_DROPDOWN.some(
         typeof window !== 'undefined' &&
         new URLSearchParams(location.search).get('_iframe') === '1';
 
+    // The walkthroughs overview is a card-grid landing page (like home) — no
+    // in-page nav to browse, so skip the left sidebar entirely and let the
+    // cards use the full width. tutorials-overview is presented like any other
+    // tutorial content page (left nav + right TOC), same as its own lessons.
+    const hideLeftNav = curPageNode.pageAttributes.pageid === 'walkthroughs';
+
     const isGQPlayGround =
         params[TS_PAGE_ID_PARAM] === CUSTOM_PAGE_ID.GQ_PLAYGROUND;
     const isPlayGround =
@@ -196,18 +202,22 @@ const isVersionedIframe = VERSION_DROPDOWN.some(
 
     /* Build pageId → category map by parsing hrefs from each category's nav HTML.
      * This means writers only need to update nav-*.adoc — no TypeScript changes needed.
-     * Excludes the merged in-product nav, which isn't a real tab/category. */
+     * Skips any merged nav key that isn't a real tab/category (e.g. the in-product nav,
+     * or a content-only nav file like nav-release-notes.adoc that a category points to
+     * via CATEGORY_NAV_ID rather than being a category itself) — otherwise `cat` ends up
+     * as a bogus DocCategory and CATEGORY_NAV_ID[activeCategory] later resolves to
+     * undefined, crashing on the `.startsWith` call in activeNavContent below. */
     const pageIdToCategoryMap = React.useMemo(() => {
         if (typeof window === 'undefined') return {};
+        const knownCategories = new Set(Object.keys(CATEGORY_NAV_ID));
         const map: Record<string, DocCategory> = {};
         Object.entries(processedNavMap).forEach(([cat, html]) => {
-            if (cat === IN_PRODUCT_NAV_KEY) return;
+            if (cat === IN_PRODUCT_NAV_KEY || !knownCategories.has(cat)) return;
             const doc = new DOMParser().parseFromString(html as string, 'text/html');
             doc.querySelectorAll('a[href]').forEach((a) => {
-                const href = a.getAttribute('href') || '';
-                // hrefs are like /docs/pageid or /pageid — extract the last segment
-                const pageId = href.split('?')[0].split('/').filter(Boolean).pop();
-                if (pageId) map[pageId] = cat as DocCategory;
+                const pageId = getPageIdFromHref(a.getAttribute('href'));
+                if (!pageId) return;
+                map[pageId] = cat as DocCategory;
             });
         });
         return map;
@@ -218,9 +228,15 @@ const isVersionedIframe = VERSION_DROPDOWN.some(
      * page (gatsby-node.js doesn't vary $pageId per version-wrapper page), so the real page
      * being shown in the nested iframe is tracked via the ?pageid= query param instead. */
     useEffect(() => {
-        const currentPageId = isVersionedIframe
-            ? new URLSearchParams(location.search).get('pageid') || 'introduction'
-            : curPageNode.pageAttributes.pageid;
+        const currentPageId = curPageNode.pageAttributes.pageid;
+        // tutorials-overview is also linked from nav.adoc's own "Tutorials" section
+        // (so it has a real breadcrumb entry), which would otherwise dynamically
+        // claim it under 'guides' and show the wrong sidebar. Force it under
+        // 'tutorials' so it gets nav-tutorials.adoc's sidebar like its own lessons.
+        if (currentPageId === 'tutorials-overview') {
+            setActiveCategory('tutorials');
+            return;
+        }
         // First try the auto-derived map from nav files
         if (pageIdToCategoryMap[currentPageId]) {
             setActiveCategory(pageIdToCategoryMap[currentPageId]);
@@ -465,7 +481,13 @@ const isVersionedIframe = VERSION_DROPDOWN.some(
         });
     }
 
-    const shouldShowRightNav = params[TS_PAGE_ID_PARAM] !== HOME_PAGE_ID;
+    // The walkthroughs overview is a card-grid landing page like home — it has
+    // no in-page headings worth a right-nav TOC, and the extra 260px it reserves
+    // squashes the cards. tutorials-overview gets the normal right nav, same as
+    // any other tutorial content page.
+    const shouldShowRightNav =
+        params[TS_PAGE_ID_PARAM] !== HOME_PAGE_ID &&
+        params[TS_PAGE_ID_PARAM] !== 'walkthroughs';
     Modal.setAppElement('#___gatsby');
     const renderSearch = () => {
         const customStyles = {
@@ -527,26 +549,29 @@ const isVersionedIframe = VERSION_DROPDOWN.some(
     const renderDocTemplate = () => (
         <>
             {renderSearch()}
-            <div className="leftNavContainer">
-                <LeftSidebar
-                    backLink={getParentBackButtonLink()}
-                    navTitle={navTitle}
-                    navContent={activeNavContent}
-                    docWidth={width}
-                    location={location}
-                    setLeftNavOpen={setLeftNavOpen}
-                    leftNavOpen={leftNavOpen}
-                    isPublicSiteOpen={isPublicSiteOpen}
-                    isMaxMobileResolution={isMaxMobileResolution}
-                    setDarkMode={setDarkMode}
-                    isDarkMode={isDarkMode}
-                    curPageid={curPageNode.pageAttributes.pageid}
-                    searchClickHandler={() => {
-                        setShowSearch(true);
-                        if (!isMaxMobileResolution) setLeftNavOpen(false);
-                    }}
-                />
-            </div>
+            {!hideLeftNav && (
+                <div className="leftNavContainer">
+                    <LeftSidebar
+                        backLink={getParentBackButtonLink()}
+                        navTitle={navTitle}
+                        navContent={activeNavContent}
+                        docWidth={width}
+                        location={location}
+                        setLeftNavOpen={setLeftNavOpen}
+                        leftNavOpen={leftNavOpen}
+                        isPublicSiteOpen={isPublicSiteOpen}
+                        isMaxMobileResolution={isMaxMobileResolution}
+                        setDarkMode={setDarkMode}
+                        isDarkMode={isDarkMode}
+                        curPageid={curPageNode.pageAttributes.pageid}
+                        isTutorialsNav={activeCategory === 'tutorials' || activeCategory === 'walkthroughs'}
+                        searchClickHandler={() => {
+                            setShowSearch(true);
+                            if (!isMaxMobileResolution) setLeftNavOpen(false);
+                        }}
+                    />
+                </div>
+            )}
             {isAskDocsPage ? (
                 <div className="documentBody">
                     <AskDocs />
@@ -555,6 +580,10 @@ const isVersionedIframe = VERSION_DROPDOWN.some(
                 <div
                     className={`documentBody ${
                         isHomePage ? 'doc-home' : 'doc-wrapper-detail'
+                    }${
+                        params[TS_PAGE_ID_PARAM] === 'walkthroughs'
+                            ? ' doc-walkthroughs'
+                            : ''
                     }`}
                 >
                     <div className="introWrapper">
@@ -565,6 +594,7 @@ const isVersionedIframe = VERSION_DROPDOWN.some(
                                 docTitle={docTitle}
                                 docContent={docContent}
                                 breadcrumsData={breadcrumsData}
+                                showWalkthroughsCrumb={activeCategory === 'walkthroughs'}
                                 isPublicSiteOpen={isPublicSiteOpen}
                                 markdownBody={curPageNode.fields?.markdownBody}
                             />
@@ -595,6 +625,7 @@ const isVersionedIframe = VERSION_DROPDOWN.some(
                     backLink={backLink}
                     isPublisSiteOpen={isPublicSiteOpen}
                     params={params}
+                    isDarkMode={isDarkMode}
                 />
             );
 
diff --git a/src/components/DevDocTemplate/playGround/RESTAPI.tsx b/src/components/DevDocTemplate/playGround/RESTAPI.tsx
index 2d5d7b94a..45944fd01 100644
--- a/src/components/DevDocTemplate/playGround/RESTAPI.tsx
+++ b/src/components/DevDocTemplate/playGround/RESTAPI.tsx
@@ -23,7 +23,7 @@ const EXTERNAL_PLAYGROUND_EVENTS = {
 };
 
 const RenderPlayGround: FC<RenderPlayGroundProps> = (props) => {
-    const { location, backLink, isPublisSiteOpen = false } = props;
+    const { location, backLink, isPublisSiteOpen = false, isDarkMode = false } = props;
 
     const isBrowser = () => typeof window !== 'undefined';
 
@@ -60,11 +60,24 @@ const RenderPlayGround: FC<RenderPlayGroundProps> = (props) => {
     };
     const baseUrl = isPublisSiteOpen ? DEFAULT_HOST : getParentURL();
 
-    const playgroundUrl =
+    const playgroundBaseUrl =
         clusterType === CLUSTER_TYPES.PROD
             ? playgroundUrlTemplate({ version: DOC_VERSION_PROD })
             : playgroundUrlTemplate({ version: DOC_VERSION_DEV });
 
+    // Same convention VersionIframe uses to propagate theme into a nested
+    // iframe: an `isDarkMode` query param. Standalone site: `isDarkMode`
+    // already reflects the user's toggle/OS preference. In-product help:
+    // `isDarkMode` already reflects the cluster's theme (DevDocTemplate
+    // forces it from the embedding product rather than letting the user
+    // toggle it) — so this needs no extra logic, just forwarding the same
+    // value versioned URLs already use.
+    const playgroundUrl = (() => {
+        const url = new URL(playgroundBaseUrl);
+        url.searchParams.set('isDarkMode', String(isDarkMode));
+        return url.toString();
+    })();
+
     useEffect(() => {
         async function fetchData() {
             try {
@@ -226,4 +239,5 @@ type RenderPlayGroundProps = {
     backLink: string;
     isPublisSiteOpen: boolean;
     params: Object;
+    isDarkMode?: boolean;
 };
diff --git a/src/components/Docmap/index.scss b/src/components/Docmap/index.scss
index d28015f90..0b1158921 100644
--- a/src/components/Docmap/index.scss
+++ b/src/components/Docmap/index.scss
@@ -36,7 +36,7 @@
                 }
 
                 > a:hover {
-                    color: var(--var-note-color);
+                    color: var(--docmap-active-color);
                 }
 
                 &.activeTag {
@@ -47,11 +47,11 @@
                         top: 0;
                         bottom: 10px;
                         width: 1px;
-                        background: var(--var-note-color);
+                        background: var(--docmap-active-color);
                     }
 
                     > a {
-                        color: var(--var-note-color) !important;
+                        color: var(--docmap-active-color) !important;
                         font-weight: 500;
                     }
                 }
@@ -72,7 +72,7 @@
                         }
 
                         &.activeTag > a {
-                            color: var(--var-note-color) !important;
+                            color: var(--docmap-active-color) !important;
                             font-weight: 500;
                         }
 
@@ -91,7 +91,7 @@
                                 }
 
                                 &.activeTag > a {
-                                    color: var(--var-note-color) !important;
+                                    color: var(--docmap-active-color) !important;
                                     font-weight: 500;
                                     opacity: 1;
                                 }
@@ -115,7 +115,7 @@
 }
 
 .activeTag {
-    color: var(--var-note-color) !important;
+    color: var(--docmap-active-color) !important;
 }
 
 @media screen and (min-width: $tablet-resolution-min) and (max-width: $tablet-resolution-max) {
diff --git a/src/components/Document/helper.tsx b/src/components/Document/helper.tsx
index 100bcd703..b890f5249 100644
--- a/src/components/Document/helper.tsx
+++ b/src/components/Document/helper.tsx
@@ -1,8 +1,10 @@
 import React from 'react';
 import hljs from 'highlight.js';
-import { FiCopy } from '@react-icons/all-files/fi/FiCopy';
+import { MdContentCopy } from '@react-icons/all-files/md/MdContentCopy';
+import { MdCheck } from '@react-icons/all-files/md/MdCheck';
 import t from '../../utils/lang-utils';
 import { getHTMLFromComponent } from '../../utils/react-utils';
+import { isTutorialsPath } from '../../utils/app-utils';
 import selectors from '../../constants/selectorsContant';
 
 export const enableCopyToClipboard = (
@@ -31,19 +33,28 @@ export const enableCopyToClipboard = (
             document.body.removeChild(ta);
         }
 
-        /* Tooltip appended inside the button so it floats via absolute positioning */
-        if (element.querySelector('.tooltip')) return;
-        const divElement = document.createElement('div');
-        divElement.classList.add('tooltip');
-        const spanElement = document.createElement('span');
-        spanElement.classList.add('tooltiptext');
-        spanElement.innerText = t('CODE_COPY_BTN_AFTER_CLICK_TEXT');
-        divElement.appendChild(spanElement);
-        element.appendChild(divElement);
+        /* Swap the icon for a checkmark and reverting after a delay. The
+           "Copied" text is no longer shown as an always-visible popup —
+           it's only surfaced via `aria-label`/`title`, which browsers only
+           display on hover. `.copyIcon` is the <svg> itself, so replace it
+           wholesale via outerHTML rather than innerHTML, which would nest a
+           new svg inside the existing one instead of swapping it. */
+        const iconEl = element.querySelector('.copyIcon');
+        if (iconEl) {
+            iconEl.outerHTML = getHTMLFromComponent(<MdCheck />, 'copyIcon');
+        }
+        element.classList.add('copied');
+        element.setAttribute('aria-label', t('CODE_COPY_BTN_AFTER_CLICK_TEXT'));
+        element.setAttribute('title', t('CODE_COPY_BTN_AFTER_CLICK_TEXT'));
+
         setTimeout(() => {
-            if (element.contains(divElement)) {
-                element.removeChild(divElement);
+            const icon = element.querySelector('.copyIcon');
+            if (icon) {
+                icon.outerHTML = getHTMLFromComponent(<MdContentCopy />, 'copyIcon');
             }
+            element.classList.remove('copied');
+            element.setAttribute('aria-label', t('CODE_COPY_BTN_HOVER_TEXT'));
+            element.setAttribute('title', t('CODE_COPY_BTN_HOVER_TEXT'));
         }, 1500);
     });
 };
@@ -51,7 +62,7 @@ export const enableCopyToClipboard = (
 export const customizeDocContent = () => {
     /*
      * Restructure code blocks to have a permanent header bar:
-     *   lang label (left)  ·  copy button (right)
+     *   lang label (left)  ·  Ask SpotterCode + copy button (right)
      *
      * Covers all listing/literal blocks regardless of [source,lang] annotation.
      * For annotated blocks, lang is read from code[data-lang] and the code element
@@ -60,6 +71,12 @@ export const customizeDocContent = () => {
      *
      * Guard against double-processing on re-render.
      */
+    // The SpotterCode assistant is hidden entirely on tutorials pages (see
+    // FloatingAssistant) — its "Ask SpotterCode" CTA here would just dispatch
+    // spotter-code-ask to nothing. Keep the copy button everywhere, including there.
+    const hideAskSpotterCode =
+        typeof window !== 'undefined' && isTutorialsPath(window.location.pathname);
+
     document.querySelectorAll<HTMLElement>(
         '.listingblock>.content>pre, .literalblock>.content>pre',
     ).forEach((pre) => {
@@ -83,14 +100,16 @@ export const customizeDocContent = () => {
         const rightGroup = document.createElement('div');
         rightGroup.classList.add('code-block-header-actions');
 
-        const ctaLink = document.createElement('button');
-        ctaLink.classList.add('ctaButton');
-        ctaLink.innerText = 'Ask SpotterCode';
-        ctaLink.addEventListener('click', () => {
-            const code = copySource.innerText.trim();
-            window.dispatchEvent(new CustomEvent('spotter-code-ask', { detail: { quotedText: code } }));
-        });
-        rightGroup.appendChild(ctaLink);
+        if (!hideAskSpotterCode) {
+            const ctaLink = document.createElement('button');
+            ctaLink.classList.add('ctaButton');
+            ctaLink.innerText = 'Ask SpotterCode';
+            ctaLink.addEventListener('click', () => {
+                const code = copySource.innerText.trim();
+                window.dispatchEvent(new CustomEvent('spotter-code-ask', { detail: { quotedText: code } }));
+            });
+            rightGroup.appendChild(ctaLink);
+        }
 
         /* Copy button — icon style */
         const buttonElement = document.createElement('button');
@@ -99,7 +118,7 @@ export const customizeDocContent = () => {
         buttonElement.setAttribute('title', t('CODE_COPY_BTN_HOVER_TEXT'));
 
         const imageElement = document.createElement('span');
-        imageElement.innerHTML = getHTMLFromComponent(<FiCopy />, 'copyIcon');
+        imageElement.innerHTML = getHTMLFromComponent(<MdContentCopy />, 'copyIcon');
         buttonElement.appendChild(imageElement);
 
         enableCopyToClipboard(buttonElement, copySource);
@@ -140,7 +159,7 @@ export const customizeDocContent = () => {
 
                     enableCopyToClipboard(buttonElement, contentWrapper);
                     const imageElement = document.createElement('span');
-                    imageElement.innerHTML = getHTMLFromComponent(<FiCopy />, 'copyIcon');
+                    imageElement.innerHTML = getHTMLFromComponent(<MdContentCopy />, 'copyIcon');
                     buttonElement.appendChild(imageElement);
                     cellElement.appendChild(buttonElement);
                 });
@@ -150,6 +169,49 @@ export const customizeDocContent = () => {
     document.querySelectorAll('pre code').forEach((block) => {
         hljs.highlightBlock(block as HTMLElement);
     });
+
+    /*
+     * Autoplaying <video> elements without `muted` get silently blocked or
+     * repeatedly stalled by the browser's autoplay policy in a real (non-
+     * automated) browser — each buffering/retry attempt can intercept
+     * trackpad scroll for a second or two. The video:: macro's options list
+     * doesn't forward "muted" through this Asciidoctor version, so set it
+     * directly on the element instead.
+     */
+    document.querySelectorAll<HTMLVideoElement>('video[autoplay]').forEach((video) => {
+        video.muted = true;
+        video.setAttribute('muted', '');
+        // Setting `muted` after the browser already evaluated (and likely
+        // blocked) the initial autoplay attempt doesn't retroactively start
+        // playback — re-trigger it explicitly.
+        video.play().catch(() => {});
+    });
+
+    /*
+     * Expand/collapse for code blocks taller than the collapsed max-height.
+     * Avoids trapping mouse-wheel scroll inside a nested scrollbar: collapsed
+     * blocks clip + fade instead of scrolling internally; "Show more" reveals
+     * the full block (no scroll) so page scroll takes over normally.
+     */
+    document.querySelectorAll<HTMLElement>('.code-block-wrapper').forEach((wrapper) => {
+        if (wrapper.querySelector('.code-expand-btn')) return;
+
+        const pre = wrapper.querySelector('pre');
+        if (!pre) return;
+
+        if (pre.scrollHeight <= pre.clientHeight + 2) return;
+
+        wrapper.classList.add('has-overflow');
+
+        const expandBtn = document.createElement('button');
+        expandBtn.classList.add('code-expand-btn');
+        expandBtn.textContent = 'Show more';
+        expandBtn.addEventListener('click', () => {
+            const isExpanded = wrapper.classList.toggle('expanded');
+            expandBtn.textContent = isExpanded ? 'Show less' : 'Show more';
+        });
+        wrapper.appendChild(expandBtn);
+    });
 };
 
 const isInViewport = (el: HTMLElement) => {
diff --git a/src/components/Document/index.scss b/src/components/Document/index.scss
index 47c9a64c9..acf200ce7 100644
--- a/src/components/Document/index.scss
+++ b/src/components/Document/index.scss
@@ -169,10 +169,57 @@
 
     /* ── Code block wrapper — holds header bar + pre ─────────────────── */
     .code-block-wrapper {
+        position: relative;
         margin: 16px 0;
         border-radius: 8px;
         border: 1px solid #323946;
         overflow: hidden;
+        background: var(--code-block-color);
+
+        /* Collapsed + overflowing: fade the clipped edge instead of an inner scrollbar,
+           so mouse-wheel scroll always falls through to the page, never gets trapped. */
+        &.has-overflow:not(.expanded) pre {
+            overflow: hidden;
+            mask-image: linear-gradient(to bottom, #000 calc(100% - 56px), transparent 100%);
+            -webkit-mask-image: linear-gradient(to bottom, #000 calc(100% - 56px), transparent 100%);
+        }
+
+        &.expanded pre {
+            max-height: none;
+            overflow: visible;
+        }
+
+        .code-expand-btn {
+            display: block;
+            margin: 0 auto;
+            padding: 5px 16px;
+            font-size: 12.5px;
+            font-weight: 500;
+            font-family: 'Optimo-Plain', sans-serif;
+            color: var(--link-text-color);
+            background: var(--copy-btn-bg);
+            // Bold (not subtle) border so the button reads clearly against
+            // the code background instead of blending in.
+            border: 1px solid var(--rd-sys-color-border-bold);
+            border-radius: 999px;
+            cursor: pointer;
+        }
+
+        &.has-overflow:not(.expanded) .code-expand-btn {
+            position: absolute;
+            left: 50%;
+            // Extra clearance from the bottom edge so the button doesn't
+            // sit right on top of the last (masked-fade) line of code.
+            bottom: 20px;
+            transform: translateX(-50%);
+            z-index: 3;
+        }
+
+        &.expanded .code-expand-btn {
+            // More breathing room above than below, so it doesn't crowd
+            // the last line of code once expanded.
+            margin: 16px auto 10px;
+        }
     }
 
     /* ── Code block header bar ────────────────────────────────────────── */
@@ -203,9 +250,9 @@
             display: inline-flex;
             align-items: center;
             padding: 4px 10px;
-            font-size: 12px;
+            font-size: 13px;
             font-weight: 500;
-            color: #2770ef;
+            color: var(--nav-accent-color);
             background: transparent;
             border: none;
             border-radius: 5px;
@@ -227,7 +274,7 @@
             font-weight: 500;
             color: #fff;
             background: transparent;
-            border: 1px solid rgba(255, 255, 255, 0.15);
+            border: none;
             border-radius: 5px;
             cursor: pointer;
             white-space: nowrap;
@@ -235,7 +282,21 @@
             transition: background 0.15s ease, color 0.15s ease;
 
             &:hover { background: rgba(255, 255, 255, 0.1); }
-            &.copied { color: #0d9f6e; border-color: #0d9f6e; }
+            // Filled green chip (not just a colored icon) to match the
+            // highlighted checkmark treatment shown in the reference.
+            &.copied,
+            &.copied:hover {
+                color: #0d9f6e;
+                background: rgba(13, 159, 110, 0.14);
+            }
+
+            // The global `.icon` rule (assets/styles/index.scss) sets its
+            // own `color`, which wins over inheriting the button's `color`
+            // here (since currentColor resolves against the SVG's own
+            // color, not an ancestor's) — so the checkmark stayed grey even
+            // once the button itself turned green. `.copyIcon` has higher
+            // specificity than the single-class `.icon` rule, so this wins.
+            &.copied .copyIcon { color: #0d9f6e; }
         }
     }
 
@@ -285,9 +346,19 @@
 
                 .lang { color: #fff; }
                 .copyButton {
-                    border-color: rgba(255, 255, 255, 0.15);
                     color: #fff;
                     &:hover { background: rgba(255, 255, 255, 0.1); color: #cdd9e5; }
+                    // Higher specificity than the plain :hover above (both live
+                    // under this same `#wrapper[data-theme='light'] &` block),
+                    // so the checkmark stays green even while the mouse is
+                    // still over the button right after clicking.
+                    &.copied,
+                    &.copied:hover {
+                        color: #0d9f6e;
+                        background: rgba(13, 159, 110, 0.14);
+                    }
+
+                    &.copied .copyIcon { color: #0d9f6e; }
                 }
             }
         }
@@ -297,18 +368,41 @@
         }
     }
 
+    /* Dark mode: header matches the pre body color, subtle grey borders throughout */
+    #wrapper[data-theme='dark'] & {
+        .code-block-wrapper {
+            border-color: #34363C;
+
+            .code-block-header {
+                background: #26282C;
+                border-bottom: 1px solid #34363C;
+            }
+        }
+        pre {
+            border-color: #34363C;
+        }
+    }
+
     #preview-in-playground {
-        background: var(--secondary-color);
+        background: var(--rd-comp-color-button-primary-default);
         color: $white;
         font-size: $font-size-normal;
         font-weight: $font-weight-normal;
         border: 0;
         padding: $preview-padding;
-        border: 0;
         border-radius: $preview-border-radius;
         margin-bottom: $preview-margin-bottom;
         display: inline-block;
         height: $preview-height;
+        transition: background 0.15s ease;
+
+        &:hover {
+            background: var(--rd-comp-color-button-primary-hover);
+        }
+
+        &:active {
+            background: var(--rd-comp-color-button-primary-pressed);
+        }
     }
     .paragraph #preview-in-playground {
         padding: 4px 16px !important;
@@ -317,29 +411,40 @@
     table {
         border-spacing: 0;
         border-collapse: separate;
+        border-top: 1px solid var(--border-color);
+        border-left: none;
+        border-right: none;
+        border-bottom: none;
+        table-layout: fixed;
         width: 100%;
         overflow: auto;
 
         th {
             border-bottom: 1px solid var(--border-color);
-            font-size: 13.5px;
+            font-size: 13px;
             text-align: left;
             padding: 20px $padding-sm 20px $padding-sm;
-            background-color: var(--table-header-color);
+            background-color: var(--table-header-bg);
             position: sticky;
             top: 0;
             z-index: 2;
         }
 
         td {
-            font-size: 13.5px;
+            font-size: 13px;
             border-bottom: 1px solid var(--border-color-tr);
             padding: 5px $padding-md $padding-sm $padding-sm;
             font-weight: $font-weight-normal;
             vertical-align: top;
 
+            code {
+                overflow-wrap: break-word;
+                word-break: break-word;
+                white-space: normal;
+            }
+
             p {
-                font-size: 13.5px;
+                font-size: 13px;
                 margin: 3px 0;
             }
         }
@@ -362,6 +467,9 @@
                 gap: 4px;
                 font-size: 12px;
                 color: var(--secondary-color);
+
+                &.copied { color: #0d9f6e; }
+                &.copied .copyIcon { color: #0d9f6e; }
             }
 
             &:hover .tableCopyButton,
@@ -504,8 +612,11 @@
     }
 
     .copyIcon {
-        height: 15px;
-        width: 20px;
+        // Was 15x20 (non-square) — the source glyphs have a square 24x24
+        // viewBox, so a non-square box stretched/distorted them instead of
+        // rendering the icon as designed.
+        height: 16px;
+        width: 16px;
     }
 
     a,
@@ -578,6 +689,18 @@ pre {
     }
 }
 
+// Walkthroughs landing page only — zeroed out entirely (rather than mirrored
+// like other pages) so .radiance-bg's own negative inset has a clean 0
+// baseline to bleed from on all three edges. Compound selector (higher
+// specificity than .doc-wrapper-detail alone) so it doesn't need source
+// order and doesn't affect any other page using .doc-wrapper-detail.
+.doc-wrapper-detail.doc-walkthroughs {
+    padding: 0;
+    @media (max-width: $mobile-resolution-max) {
+        padding-right: 0;
+    }
+}
+
 @media screen and (min-width: $tablet-resolution-min) and (max-width: $tablet-resolution-max) {
     .documentWrapper {
         width: 96%;
diff --git a/src/components/Document/index.tsx b/src/components/Document/index.tsx
index 6e3ab5942..5a2305447 100644
--- a/src/components/Document/index.tsx
+++ b/src/components/Document/index.tsx
@@ -7,6 +7,7 @@ import LinkableHeader from '../LinkableHeader';
 import WasThisHelpful from '../WasThisHelpful';
 import CopyPageDropdown from '../CopyPageDropdown';
 import { HOME_PAGE_ID } from '../../configs/doc-configs';
+import { isTutorialsPath } from '../../utils/app-utils';
 import parse, { HTMLReactParserOptions, domToReact, attributesToProps } from 'html-react-parser';
 
 const Document = (props: {
@@ -16,6 +17,7 @@ const Document = (props: {
     isPublicSiteOpen: boolean;
     shouldShowRightNav: boolean;
     breadcrumsData: any;
+    showWalkthroughsCrumb?: boolean;
     markdownBody?: string;
 }) => {
     const openAssistantWithQuote = (text: string) => {
@@ -29,6 +31,10 @@ const Document = (props: {
         let mouseDownY = 0;
 
         const handleMouseUp = (e: MouseEvent) => {
+            // The SpotterCode assistant is hidden entirely on tutorials pages (see
+            // FloatingAssistant and Document/helper.tsx) — don't surface this CTA there either.
+            if (isTutorialsPath(window.location.pathname)) return;
+
             const target = e.target as HTMLElement;
             if (target.closest('.selection-cta-button')) return;
             if (target.closest('.floating-assistant__panel, .floating-assistant__chip-ring')) return;
@@ -177,6 +183,12 @@ const Document = (props: {
     };
 
     const isHomePage = props.pageid === HOME_PAGE_ID;
+    // The walkthroughs overview is a card-grid landing page with no real body
+    // text to copy and no meaningful parent to link back to — hide the copy
+    // button and the breadcrumb there. tutorials-overview shows both like any
+    // other tutorial content page.
+    const isWalkthroughsLandingPage = props.pageid === 'walkthroughs';
+    const hideCopyPage = isWalkthroughsLandingPage;
 
     return (
         <div
@@ -196,13 +208,14 @@ const Document = (props: {
                     Ask SpotterCode
                 </button>
             )}
-            {!isHomePage && (
+            {!isHomePage && !isWalkthroughsLandingPage && (
                 <Breadcrums
                     breadcrumsData={props.breadcrumsData}
                     pageid={props.pageid}
+                    showWalkthroughsCrumb={props.showWalkthroughsCrumb}
                 />
             )}
-            {!isHomePage && props.isPublicSiteOpen && (
+            {!isHomePage && !hideCopyPage && props.isPublicSiteOpen && (
                 <div className="document-toolbar">
                     <CopyPageDropdown pageTitle={props.docTitle} markdownBody={props.markdownBody} />
                 </div>
diff --git a/src/components/Dropdown/index.scss b/src/components/Dropdown/index.scss
index 7add63496..0014187f9 100644
--- a/src/components/Dropdown/index.scss
+++ b/src/components/Dropdown/index.scss
@@ -28,7 +28,7 @@
 
         &:hover {
             background: rgba(255, 255, 255, 0.1);
-            color: #A9E8FF;
+            color: var(--nav-accent-color);
         }
     }
 
@@ -52,7 +52,10 @@
         right: 0;
         left: auto;
         padding-top: 6px;
-        z-index: 200;
+        // Above the SpotterCode floating-assistant panel (z-index: 1002),
+        // which otherwise covers this dropdown's right edge on narrower
+        // viewports where the panel is open.
+        z-index: 1100;
     }
 
     .dropdown:hover .dropdownContent {
@@ -107,13 +110,13 @@
 
         &:hover {
             background: rgba(169, 232, 255, 0.08);
-            color: #A9E8FF;
+            color: var(--nav-accent-color);
 
             .version-item-sub { color: rgba(169, 232, 255, 0.5); }
         }
 
         &.active {
-            .version-item-label { color: #A9E8FF; }
+            .version-item-label { color: var(--nav-accent-color); }
         }
     }
 
diff --git a/src/components/FloatingAssistant/index.tsx b/src/components/FloatingAssistant/index.tsx
index e54a98e5a..22edad90d 100644
--- a/src/components/FloatingAssistant/index.tsx
+++ b/src/components/FloatingAssistant/index.tsx
@@ -1,7 +1,7 @@
 import React, { useState, useRef, useEffect } from 'react';
 import { createPortal } from 'react-dom';
 import { useFloatingAssistant } from '../../contexts/FloatingAssistantContext';
-import { isPublicSite } from '../../utils/app-utils';
+import { isPublicSite, isTutorialsPath } from '../../utils/app-utils';
 import { CUSTOM_PAGE_ID } from '../../configs/doc-configs';
 import { Alert, Icon, IconID, IconSize, IconColor, LoadingIndicator } from '@thoughtspot/radiant-react';
 import '@thoughtspot/radiant-react/styles';
@@ -41,6 +41,12 @@ const AssistantAvatar = () => (
 const FloatingAssistant: React.FC = () => {
     const [pageId, setPageId] = useState<string | undefined>(getPageId);
     const [isEmbedded, setIsEmbedded] = useState(false);
+    // Tutorials pages have their own footer navigation (Previous/Next/Done) that this
+    // fixed, always-on-top panel has no awareness of — hide the widget there entirely
+    // rather than fight over screen space.
+    const [isTutorialsPage, setIsTutorialsPage] = useState(
+        () => typeof window !== 'undefined' && isTutorialsPath(window.location.pathname),
+    );
     const {
         isOpen,
         setIsOpen,
@@ -263,6 +269,14 @@ const FloatingAssistant: React.FC = () => {
         return () => window.removeEventListener('gatsby-route-update', handler as EventListener);
     }, []);
 
+    useEffect(() => {
+        const handler = (e: CustomEvent<{ location: Location }>) => {
+            setIsTutorialsPage(isTutorialsPath(e.detail.location.pathname));
+        };
+        window.addEventListener('gatsby-route-update', handler as EventListener);
+        return () => window.removeEventListener('gatsby-route-update', handler as EventListener);
+    }, []);
+
     useEffect(() => {
         const handler = (e: CustomEvent<{ quotedText: string }>) => {
             setQuotedText(e.detail.quotedText);
@@ -412,6 +426,7 @@ const FloatingAssistant: React.FC = () => {
     const isLandingPage = messages.length === 0 && !isLoading;
 
     if (pageId === CUSTOM_PAGE_ID.API_PLAYGROUND) return null;
+    if (isTutorialsPage) return null;
 
     return (
         <>
diff --git a/src/components/Footer/index.scss b/src/components/Footer/index.scss
index 12b701637..004cefec4 100644
--- a/src/components/Footer/index.scss
+++ b/src/components/Footer/index.scss
@@ -6,7 +6,7 @@ footer {
 
     .footerWrapper {
         text-align: center;
-        color: #777e8b;
+        color: $darkgrey;
         font-size: 12px;
         font-weight: 300;
         margin-top: 50px;
diff --git a/src/components/Header/index.scss b/src/components/Header/index.scss
index c8d800792..6193b8d78 100644
--- a/src/components/Header/index.scss
+++ b/src/components/Header/index.scss
@@ -73,7 +73,7 @@ header {
 
         &:hover {
             background: rgba(255, 255, 255, 0.1);
-            color: #A9E8FF;
+            color: var(--nav-accent-color);
         }
     }
 
@@ -113,7 +113,9 @@ header {
         top: 100%;
         right: 0;
         padding-top: 6px;
-        z-index: 200;
+        // Above the SpotterCode floating-assistant panel (z-index: 1002),
+        // which otherwise covers this dropdown's right edge when open.
+        z-index: 1100;
         transition: opacity 0.15s ease, visibility 0.15s ease;
     }
 
@@ -151,7 +153,9 @@ header {
         position: absolute;
         top: calc(100% + 6px);
         right: 0;
-        z-index: 200;
+        // Above the SpotterCode floating-assistant panel (z-index: 1002),
+        // which otherwise covers this dropdown's right edge when open.
+        z-index: 1100;
         background: var(--nav-bar-color, #232F43);
         border: 1px solid #458;
         box-shadow: 0 8px 24px rgba(68, 85, 136, 0.35);
@@ -187,10 +191,10 @@ header {
 
         &:hover {
             background: rgba(169, 232, 255, 0.08);
-            color: #A9E8FF;
+            color: var(--nav-accent-color);
 
-            .dropdown-item-name { color: #A9E8FF; }
-            .dropdown-item-icon { color: #A9E8FF; }
+            .dropdown-item-name { color: var(--nav-accent-color); }
+            .dropdown-item-icon { color: var(--nav-accent-color); }
             .external-link-icon { color: rgba(169, 232, 255, 0.5); }
         }
 
diff --git a/src/components/Header/index.tsx b/src/components/Header/index.tsx
index 763a8e248..f21d07b3e 100644
--- a/src/components/Header/index.tsx
+++ b/src/components/Header/index.tsx
@@ -85,17 +85,17 @@ const Header = (props: {
     ];
 
     const renderDropdownItems = (
-        items: { name: string; sub: string; link: string; icon: any }[],
+        items: { name: string; sub: string; link: string; icon: any; external?: boolean }[],
         onClose?: () => void,
     ) =>
         items.map((item) => {
             const Icon = item.icon;
+            const isExternal = item.external !== false;
             return (
                 <a
                     key={item.name}
                     href={item.link}
-                    target="_blank"
-                    rel="noopener noreferrer"
+                    {...(isExternal ? { target: '_blank', rel: 'noopener noreferrer' } : {})}
                     className="header-dropdown-item"
                     role="menuitem"
                     onClick={onClose}
@@ -107,9 +107,11 @@ const Header = (props: {
                         <span className="dropdown-item-name">{item.name}</span>
                         <span className="dropdown-item-sub">{item.sub}</span>
                     </span>
-                    <IconContext.Provider value={{ className: 'external-link-icon' }}>
-                        <FiExternalLink />
-                    </IconContext.Provider>
+                    {isExternal && (
+                        <IconContext.Provider value={{ className: 'external-link-icon' }}>
+                            <FiExternalLink />
+                        </IconContext.Provider>
+                    )}
                 </a>
             );
         });
diff --git a/src/components/LeftSidebar/NavContent.tsx b/src/components/LeftSidebar/NavContent.tsx
index e9d6a8d96..2398f1b05 100644
--- a/src/components/LeftSidebar/NavContent.tsx
+++ b/src/components/LeftSidebar/NavContent.tsx
@@ -16,6 +16,7 @@ const NavContent = (props: {
     isDarkMode: boolean;
     setDarkMode: Function;
     searchClickHandler: Function;
+    isTutorialsNav?: boolean;
 }) => {
     return (
         <aside
@@ -69,7 +70,7 @@ const NavContent = (props: {
                 <div
                     className={`navWrapper ${
                         props.isPublicSiteOpen ? 'withHeaderFooter' : ''
-                    }`}
+                    } ${props.isTutorialsNav ? 'tutorialsNavWrapper' : ''}`}
                     dangerouslySetInnerHTML={{
                         __html: props.navContent,
                     }}
diff --git a/src/components/LeftSidebar/index.scss b/src/components/LeftSidebar/index.scss
index 769db1547..cff9058b2 100644
--- a/src/components/LeftSidebar/index.scss
+++ b/src/components/LeftSidebar/index.scss
@@ -84,12 +84,17 @@
         }
 
         &:focus {
-            border-color: var(--secondary-color);
-            box-shadow: 0 0 0 2px rgba(5, 104, 250, 0.12);
+            outline: none;
         }
     }
 }
 
+#wrapper[data-theme='dark'] .searchInputLeftNav input,
+#docsModal[data-theme='dark'] .searchInputLeftNav input {
+    border-color: #34363C;
+    background: #26282C;
+}
+
 .leftNav-askdocs-wrapper {
     margin-top: 12px;
     padding-right: 16px;
@@ -129,6 +134,8 @@
 }
 
 .aside {
+    position: relative;
+    z-index: $z-index-left-nav;
     padding: 0 0 0 10px;
     width: 100%;
     border-right: 1px solid var(--border-color);
@@ -335,6 +342,77 @@
     .node-child {
         padding-left: 0;
     }
+
+    /* Tutorials nav: number each step (including Introduction/Summary) with a
+       circular badge, reset per tutorial so every tutorial's steps start at 1. */
+    .tutorialsNavWrapper {
+        & > .ulist > ul > li > .ulist > ul {
+            counter-reset: tutorialStep;
+
+            > li {
+                counter-increment: tutorialStep;
+                // Extra breathing room between steps — overrides the shared
+                // `margin: 3px 0` (index.scss above) for tutorial/walkthrough
+                // nav only, since this selector requires .tutorialsNavWrapper.
+                margin: 8px 0;
+
+                > p.node-child {
+                    display: flex;
+                    align-items: center;
+                    gap: 8px;
+                    padding-left: 0;
+
+                    &::before {
+                        content: counter(tutorialStep);
+                        flex: 0 0 auto;
+                        display: inline-flex;
+                        align-items: center;
+                        justify-content: center;
+                        width: 24px;
+                        height: 24px;
+                        border-radius: 50%;
+                        background: var(--border-color);
+                        color: var(--primary-color);
+                        font-size: 13px;
+                        font-weight: $font-weight-bold;
+                    }
+
+                    &:has(a.active) {
+                        a {
+                            color: var(--var-note-color);
+                            font-weight: $font-weight-bold;
+                        }
+
+                        &::before {
+                            background: var(--var-note-color);
+                            color: #fff;
+                        }
+                    }
+                }
+            }
+        }
+
+        /* Drill-down: once a tutorial's step list is expanded (open — the user is
+           on one of its pages), hide the other tutorials and this tutorial's own
+           heading row, leaving just its numbered child pages. The "All tutorials"
+           link lives in a separate .ulist (see nav-tutorials.adoc) so it's
+           unaffected and always reachable. */
+        & > .ulist > ul:has(> li > .ulist > ul:not(.displayNone)) > li {
+            display: none;
+
+            &:has(> .ulist > ul:not(.displayNone)) {
+                display: block;
+
+                > p {
+                    display: none;
+                }
+
+                > .ulist {
+                    margin-left: 0;
+                }
+            }
+        }
+    }
 }
 
 /* Overriding react-resizable package class to match UI */
@@ -383,7 +461,7 @@
     // Selected nav link normally uses --var-note-color (shared with NOTE: admonition
     // styling elsewhere) — override just here so mobile nav selection doesn't touch that.
     .aside .active {
-        color: #a9e8ff !important;
+        color: var(--nav-accent-color) !important;
     }
 
     .menuContainer {
diff --git a/src/components/LeftSidebar/index.tsx b/src/components/LeftSidebar/index.tsx
index 0e6461296..891fb64b6 100644
--- a/src/components/LeftSidebar/index.tsx
+++ b/src/components/LeftSidebar/index.tsx
@@ -35,6 +35,7 @@ const LeftSideBar = (props: {
     setDarkMode: Function;
     curPageid: string;
     searchClickHandler: Function;
+    isTutorialsNav?: boolean;
 }) => {
     const params = queryStringParser(props.location.search);
     const [navContent, setNavContent] = useState('');
@@ -105,7 +106,12 @@ const LeftSideBar = (props: {
             );
             if (activeLink) {
                 lastScrolledPageIdRef.current = props.curPageid;
-                activeLink.scrollIntoView({ block: 'center' });
+                // 'nearest' is a no-op once the link is already visible. 'center' isn't —
+                // it nudges toward exact-center even when already in view, and since this
+                // sidebar has no scroll room to spare on most pages (content fits exactly),
+                // that nudge has nowhere to go but the window itself, which is what was
+                // sliding the fixed header out of view on some walkthrough pages.
+                activeLink.scrollIntoView({ block: 'nearest' });
             }
         }
     }, [props.curPageid, isMaxMobileResolution, navContent, props.leftNavOpen]);
@@ -143,6 +149,7 @@ const LeftSideBar = (props: {
                         setDarkMode={props.setDarkMode}
                         isDarkMode={props.isDarkMode}
                         searchClickHandler={props.searchClickHandler}
+                        isTutorialsNav={props.isTutorialsNav}
                     />
                 </ResizableBox>
             </div>
@@ -159,6 +166,7 @@ const LeftSideBar = (props: {
                     setDarkMode={props.setDarkMode}
                     isDarkMode={props.isDarkMode}
                     searchClickHandler={props.searchClickHandler}
+                    isTutorialsNav={props.isTutorialsNav}
                 />
             </div>
         );
diff --git a/src/components/SecondaryHeader/index.scss b/src/components/SecondaryHeader/index.scss
index 8adedf60b..91dd62a77 100644
--- a/src/components/SecondaryHeader/index.scss
+++ b/src/components/SecondaryHeader/index.scss
@@ -3,7 +3,7 @@
 .secondary-header {
     background: var(--secondary-header-bg);
     border-bottom: 0.5px solid var(--secondary-header-border);
-    box-shadow: 0 1px 1px #1B3E61;
+    box-shadow: 0 0 1px 0 var(--secondary-header-border);
     border-top: 0.5px solid var(--secondary-header-border);
     position: sticky;
     top: $header-height;
@@ -21,7 +21,8 @@
 
     &__tabs {
         display: flex;
-        align-items: center;
+        align-items: stretch;
+        height: 100%;
         gap: 0;
         list-style: none;
         margin: 0;
@@ -38,6 +39,7 @@
         position: relative;
         display: inline-flex;
         align-items: center;
+        height: 100%;
         padding: 12px 20px 12px $padding-sm;
         font-size: 14px;
         font-weight: 300;
@@ -48,19 +50,35 @@
         white-space: nowrap;
         font-family: 'Optimo-Plain';
         transition: color 0.15s ease;
-        border-radius: 8px;
-        border-bottom: 1px solid transparent;
-        margin-bottom: -1px;
+        border-radius: 0;
+        margin-right: 8px;
         letter-spacing: 0.01em;
 
+        &::after {
+            content: '';
+            position: absolute;
+            left: $padding-sm;
+            right: 20px;
+            bottom: 0;
+            height: 2px;
+            background: transparent;
+        }
+
         &:hover {
-            color: #A9E8FF;
-            background-color: #122246;
+            color: var(--nav-accent-color);
+
+            &::after {
+                background: var(--nav-accent-color);
+            }
         }
 
         &.active {
-            color: #A9E8FF !important;
+            color: var(--nav-accent-color) !important;
             font-weight: 400;
+
+            &::after {
+                background: var(--nav-accent-color);
+            }
         }
     }
 
@@ -93,7 +111,7 @@
 
                 &:hover {
                     background: rgba(255, 255, 255, 0.1);
-                    color: #A9E8FF;
+                    color: var(--nav-accent-color);
                 }
             }
 
@@ -128,7 +146,7 @@
 
                     &:hover {
                         background: rgba(169, 232, 255, 0.08);
-                        color: #A9E8FF;
+                        color: var(--nav-accent-color);
                     }
                 }
 
@@ -164,7 +182,7 @@
         flex-shrink: 0;
 
         &:hover {
-            color: #A9E8FF;
+            color: var(--nav-accent-color);
             background: rgba(169, 232, 255, 0.06);
         }
     }
@@ -196,7 +214,7 @@
         white-space: nowrap;
 
         &:hover {
-            color: #A9E8FF;
+            color: var(--nav-accent-color);
             background: rgba(169, 232, 255, 0.06);
         }
     }
@@ -247,13 +265,13 @@
 
         &:hover {
             background: rgba(169, 232, 255, 0.08);
-            color: #A9E8FF;
+            color: var(--nav-accent-color);
         }
 
         &.active {
             // Needs !important to beat the global .active rule in assets/styles/index.scss
             // (var(--var-note-color) !important), same as __tab.active above.
-            color: #A9E8FF !important;
+            color: var(--nav-accent-color) !important;
             background: rgba(169, 232, 255, 0.08);
         }
     }
diff --git a/src/components/SecondaryHeader/index.tsx b/src/components/SecondaryHeader/index.tsx
index cc2419811..751a71460 100644
--- a/src/components/SecondaryHeader/index.tsx
+++ b/src/components/SecondaryHeader/index.tsx
@@ -9,19 +9,23 @@ import './index.scss';
 export type DocCategory =
     | 'all'
     | 'guides'
+    | 'walkthroughs'
     | 'embedding'
     | 'rest-api'
     | 'mcp-server'
     | 'spottercode'
+    | 'tutorials'
     | 'whats-new';
 
 export const CATEGORY_LABELS: Record<DocCategory, string> = {
     all: 'All docs',
     guides: 'Developer guides',
+    walkthroughs: 'Guided Walkthroughs',
     embedding: 'Embedding',
     'rest-api': 'REST APIs',
     'mcp-server': 'MCP server',
     spottercode: 'SpotterCode',
+    tutorials: 'Tutorials',
     'whats-new': "What's new",
 };
 
@@ -31,10 +35,12 @@ export const CATEGORY_LABELS: Record<DocCategory, string> = {
 export const CATEGORY_LANDING: Record<DocCategory, string> = {
     all: '/introduction',
     guides: '/introduction',
+    walkthroughs: '/tutorials/walkthroughs',
     embedding: '/getting-started',
     'rest-api': '/rest-apis',
     'mcp-server': '/mcp-integration',
     spottercode: '/SpotterCode',
+    tutorials: '/tutorials/tutorials-overview',
     'whats-new': '/whats-new',
 };
 
@@ -45,11 +51,13 @@ export const CATEGORY_LANDING: Record<DocCategory, string> = {
 export const CATEGORY_NAV_ID: Record<DocCategory, string> = {
     all: 'nav',
     guides: 'nav',
+    walkthroughs: 'nav-walkthroughs',
     embedding: 'nav-embedding',
     'rest-api': 'nav-rest-api',
     'mcp-server': 'nav-mcp-server',
     spottercode: 'nav-spottercode',
-    'whats-new': 'nav',
+    tutorials: 'nav-tutorials',
+    'whats-new': 'nav-release-notes',
 };
 
 /*
@@ -70,6 +78,7 @@ export const CATEGORY_PAGEIDS: Record<DocCategory, string[]> = {
         'webhooks-overview', 'webhooks-ui', 'webhooks-comm-channel', 'webhooks-lb-schedule',
         'webhooks-s3-integration', 'webhooks-gcs-storage', 'webhooks-lb-payload', 'webhooks-kpi',
     ],
+    walkthroughs: [],
     embedding: [
         'getting-started', 'tsembed', 'embed-liveboard', 'embed-a-viz',
         'embed-ai-search-analytics', 'embed-spotter', 'embed-spotter-agent',
@@ -114,6 +123,7 @@ export const CATEGORY_PAGEIDS: Record<DocCategory, string[]> = {
     spottercode: [
         'SpotterCode', 'integrate-SpotterCode', 'spottercode-prompting-guide',
     ],
+    tutorials: [],
     'whats-new': [
         'whats-new', 'fixed-issues', 'known-issues', 'deprecated-features',
         'embed-sdk-changelog', 'mobile-sdk-changelog',
@@ -142,6 +152,12 @@ const SecondaryHeader = (props: {
     const [mobileMenuOpen, setMobileMenuOpen] = useState(false);
     const menuRef = useRef<HTMLDivElement>(null);
 
+    // 'tutorials' and 'walkthroughs' intentionally excluded — reachable from links
+    // inside nav.adoc's own sidebar rather than a secondary-header tab, and the
+    // secondary header/left sidebar are hidden altogether on their card-grid overview
+    // pages (see DevDocTemplate). Their category config (label/landing/nav id/pageids)
+    // still exists above — it's what makes nav-tutorials.adoc/nav-walkthroughs.adoc
+    // resolve as the active sidebar once you're on one of their pages.
     const categories: DocCategory[] = [
         'guides', 'embedding', 'rest-api', 'mcp-server', 'spottercode', 'whats-new',
     ];
@@ -269,7 +285,6 @@ const SecondaryHeader = (props: {
                 <div className="secondary-header__mobile-version">
                     <Dropdown location={location} isMobile={false} />
                 </div>
-
             </div>
         </nav>
     );
diff --git a/src/utils/app-utils.ts b/src/utils/app-utils.ts
index 337639e62..ae9fccfa5 100644
--- a/src/utils/app-utils.ts
+++ b/src/utils/app-utils.ts
@@ -64,6 +64,19 @@ export const removeTrailingSlash = (url: string) => {
     return url.replace(/\/$/, '');
 };
 
+/**
+ * True for any tutorials-module page (/tutorials/... locally, /docs/tutorials/...
+ * in production) — path-segment check so it's robust to the {{navprefix}} prefix.
+ * Tutorials pages have their own pagination footer and no SpotterCode assistant
+ * (see FloatingAssistant), so SpotterCode-related affordances elsewhere (e.g. the
+ * "Ask SpotterCode" code-block CTA in Document/helper.tsx) should stay hidden there too.
+ * @param {string} pathname - location.pathname
+ * @returns {boolean} true if the path is under /tutorials/
+ */
+export const isTutorialsPath = (pathname: string) => {
+    return pathname.split('/').filter(Boolean).includes('tutorials');
+};
+
 /**
  * Used to check if the docs portal open as public site or inside embed iframe
  * @param {string} queryParamStr - query string from location.search
diff --git a/src/utils/doc-utils.ts b/src/utils/doc-utils.ts
index ad56deac4..997d5e576 100644
--- a/src/utils/doc-utils.ts
+++ b/src/utils/doc-utils.ts
@@ -58,15 +58,22 @@ export const fetchChild = (html: string) => {
     return topLevelItems.map((el) => buildJSON(el));
 };
 
-// Not being used anywhere
-const getParentHref = (current) => {
-    if (current.href) {
-        return current.href;
-    }
-    if (current?.children?.length > 1) {
-        return current.children[0]?.href;
-    }
-    return null;
+/**
+ * Reconstructs a page's pageid from an href found in nav content. Tutorials/
+ * walkthroughs module pages use compound pageids ({subdirectory}__{finalSegment},
+ * see getTutorialLinkFromEdge in gatsby-utils.js) while their nav links use the
+ * human-readable URL (/tutorials/{subdirectory}/{finalSegment}) — this bridges
+ * the two so matching works regardless of the {{navprefix}} substitution ('' on
+ * LOCAL, '/docs' otherwise), since only the trailing segments are inspected.
+ */
+export const getPageIdFromHref = (href?: string | null): string | null => {
+    if (!href) return null;
+    const segments = href.split('?')[0].split('/').filter(Boolean);
+    const lastSegment = segments.pop();
+    if (!lastSegment) return null;
+    const tutorialsIdx = segments.indexOf('tutorials');
+    const subdir = tutorialsIdx !== -1 ? segments[tutorialsIdx + 1] : undefined;
+    return subdir ? `${subdir}__${lastSegment}` : lastSegment;
 };
 
 export const getBreadcrumsPath = (data: any, pageid?: string) => {
@@ -77,18 +84,23 @@ export const getBreadcrumsPath = (data: any, pageid?: string) => {
     return data.reduce((previous, current) => {
         if (
             current.href === `?pageid=${pageid}` ||
-            current.href === `/${SITE_PREFIX}/${pageid}`
+            current.href === `/${SITE_PREFIX}/${pageid}` ||
+            getPageIdFromHref(current.href) === pageid
         ) {
             // To avoid having link for the same page we are setting href to null
             return [{ name: current.name, href: null }];
         }
         if (current.children) {
-            const parentObj = [
-                { name: current.name, href: getParentHref(current) },
-            ];
             const childObj = getBreadcrumsPath(current.children, pageid);
             if (childObj.length) {
-                return [...parentObj, ...childObj];
+                // Group labels with no link of their own (e.g. an unlinked nav
+                // heading used purely to group tutorial steps) aren't a real
+                // page — skip them rather than falling back to a child's href,
+                // which would make the crumb redundantly link to that child.
+                if (current.href) {
+                    return [{ name: current.name, href: current.href }, ...childObj];
+                }
+                return childObj;
             }
         }
         if (previous.length) {
diff --git a/static/doc-images/images/mktng-tutorials/add-spotter.mp4 b/static/doc-images/images/mktng-tutorials/add-spotter.mp4
new file mode 100644
index 000000000..ce44792f2
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/add-spotter.mp4 differ
diff --git a/static/doc-images/images/mktng-tutorials/analytics.mp4 b/static/doc-images/images/mktng-tutorials/analytics.mp4
new file mode 100644
index 000000000..656349f82
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/analytics.mp4 differ
diff --git a/static/doc-images/images/mktng-tutorials/cbca.mp4 b/static/doc-images/images/mktng-tutorials/cbca.mp4
new file mode 100644
index 000000000..adca0a193
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/cbca.mp4 differ
diff --git a/static/doc-images/images/mktng-tutorials/dev-section.mp4 b/static/doc-images/images/mktng-tutorials/dev-section.mp4
new file mode 100644
index 000000000..b1d98c094
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/dev-section.mp4 differ
diff --git a/static/doc-images/images/mktng-tutorials/frame-video.mp4 b/static/doc-images/images/mktng-tutorials/frame-video.mp4
new file mode 100644
index 000000000..476ebca4e
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/frame-video.mp4 differ
diff --git a/static/doc-images/images/mktng-tutorials/lb-embed-prompt.mp4 b/static/doc-images/images/mktng-tutorials/lb-embed-prompt.mp4
new file mode 100644
index 000000000..ea40e60ab
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/lb-embed-prompt.mp4 differ
diff --git a/static/doc-images/images/mktng-tutorials/liveboard.mp4 b/static/doc-images/images/mktng-tutorials/liveboard.mp4
new file mode 100644
index 000000000..13a941a8a
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/liveboard.mp4 differ
diff --git a/static/doc-images/images/mktng-tutorials/spotter-embed-playground.mp4 b/static/doc-images/images/mktng-tutorials/spotter-embed-playground.mp4
new file mode 100644
index 000000000..8a62f98db
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/spotter-embed-playground.mp4 differ
diff --git a/static/doc-images/images/mktng-tutorials/spottercode-connector.mp4 b/static/doc-images/images/mktng-tutorials/spottercode-connector.mp4
new file mode 100644
index 000000000..2f14ee6bc
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/spottercode-connector.mp4 differ
diff --git a/static/doc-images/images/mktng-tutorials/theme-builder-styling.mp4 b/static/doc-images/images/mktng-tutorials/theme-builder-styling.mp4
new file mode 100644
index 000000000..14490d6f6
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/theme-builder-styling.mp4 differ
diff --git a/static/doc-images/images/mktng-tutorials/themed-app.mp4 b/static/doc-images/images/mktng-tutorials/themed-app.mp4
new file mode 100644
index 000000000..7afffa5f7
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/themed-app.mp4 differ
diff --git a/static/doc-images/images/mktng-tutorials/working-spotter-embed.mp4 b/static/doc-images/images/mktng-tutorials/working-spotter-embed.mp4
new file mode 100644
index 000000000..5c471042d
Binary files /dev/null and b/static/doc-images/images/mktng-tutorials/working-spotter-embed.mp4 differ