diff --git a/content/influxdb3/enterprise/admin/explorer-ui.md b/content/influxdb3/enterprise/admin/explorer-ui.md
index 6496047992..7357e9fb30 100644
--- a/content/influxdb3/enterprise/admin/explorer-ui.md
+++ b/content/influxdb3/enterprise/admin/explorer-ui.md
@@ -237,7 +237,7 @@ The integrated Explorer keeps its application state in a SQLite database that
 the server synchronizes to object storage for each cluster.
 You don't mount a volume to persist it, which is the main operational
 difference from the
-[Explorer Docker container](/influxdb3/explorer/install/#persist-data-across-restarts).
+[Explorer Docker container](/influxdb3/explorer/install/docker/#persist-data-across-restarts).
 
 ## Migrate data from the 3.11 UI {#migrate-data-from-the-311-ui metadata="v3.12+"}
 
diff --git a/content/influxdb3/enterprise/visualize-data/explorer.md b/content/influxdb3/enterprise/visualize-data/explorer.md
index 8cfdb6deb1..e8de4f8f22 100644
--- a/content/influxdb3/enterprise/visualize-data/explorer.md
+++ b/content/influxdb3/enterprise/visualize-data/explorer.md
@@ -123,4 +123,4 @@ works with v3.11 and later.
 Use the container when you run Core, when you run an Enterprise release
 earlier than v3.11, or when you want Explorer to run separately from the
 database server--for example, on an operator workstation.
-See [Install and run InfluxDB 3 Explorer](/influxdb3/explorer/install/).
+See [Install and run InfluxDB 3 Explorer with Docker](/influxdb3/explorer/install/docker/).
diff --git a/content/influxdb3/explorer/_index.md b/content/influxdb3/explorer/_index.md
index a3bb240a38..a53003150f 100644
--- a/content/influxdb3/explorer/_index.md
+++ b/content/influxdb3/explorer/_index.md
@@ -1,7 +1,7 @@
 ---
 title: InfluxDB 3 Explorer documentation
 description: >
-  InfluxDB 3 Explorer is a standalone web-based interface for interacting with InfluxDB 3 Core and Enterprise. Visualize, query, and manage your time series data efficiently.
+  InfluxDB 3 Explorer is a web-based interface for InfluxDB 3 Core and Enterprise. Visualize, query, and manage your time series data efficiently.
 menu:
   influxdb3_explorer:
     name: InfluxDB 3 Explorer
@@ -9,9 +9,20 @@ weight: 1
 cascade:
   product: influxdb3_explorer
   version: explorer
+  prepend: |
+    > [!Important]
+    > #### How you install Explorer depends on your InfluxDB 3 server
+    >
+    > Starting with InfluxDB 3 Enterprise v3.11, Explorer is included with
+    > the server and runs as WebAssembly (WASM)--there's no separate
+    > container to install. Docker is required for InfluxDB 3 Core and
+    > Enterprise earlier than v3.11, and remains an option for later
+    > Enterprise releases. See
+    > [Install Explorer](/influxdb3/explorer/install/) to find the
+    > instructions for your server.
 ---
 
-InfluxDB 3 Explorer is the standalone web application designed for visualizing, querying, and managing your data stored in InfluxDB 3 Core and Enterprise.
+InfluxDB 3 Explorer is the web application for visualizing, querying, and managing your data stored in InfluxDB 3 Core and Enterprise.
 Explorer provides an intuitive interface for interacting with your time series data, streamlining database operations and enhancing data insights.
 
 ## Key features
@@ -24,23 +35,28 @@ Use InfluxDB 3 Explorer for:
 
 ## Quick start
 
-Run the Docker image to start InfluxDB 3 Explorer:
+How you install {{% product-name %}} depends on your InfluxDB 3 server:
 
-```sh
-# Pull the Docker image
-docker pull influxdata/influxdb3-ui
+- **InfluxDB 3 Enterprise v3.11 and later** includes Explorer as an
+  integrated WASM component. See
+  [Use the integrated Explorer UI](/influxdb3/enterprise/admin/explorer-ui/).
+- **InfluxDB 3 Core and Enterprise** can run Explorer as a standalone Docker
+  container. Docker is required for Core and Enterprise earlier than v3.11:
 
-# Run the Docker container
-docker run --detach \
-  --name influxdb3-explorer \
-  --publish 8080:8080 \
-  --publish 8443:8443 \
-  influxdata/influxdb3-ui \
-  --mode=admin
+  ```sh
+  # Pull the Docker image
+  docker pull influxdata/influxdb3-ui
 
-# Visit http://localhost:8080 in your browser to begin using InfluxDB 3 Explorer
-```
+  # Run the Docker container
+  docker run --detach \
+    --name influxdb3-explorer \
+    --publish 8080:8080 \
+    --publish 8443:8443 \
+    influxdata/influxdb3-ui \
+    --mode=admin
 
+  # Visit http://localhost:8080 in your browser to begin using InfluxDB 3 Explorer
+  ```
 
-For installation and configuration options, see [Install and run InfluxDB 3 Explorer](/influxdb3/explorer/install/).
+For installation and configuration options, see [Install InfluxDB 3 Explorer](/influxdb3/explorer/install/).
 <a class="btn" href="/influxdb3/explorer/get-started/">Get started using InfluxDB 3 Explorer</a>
diff --git a/content/influxdb3/explorer/about/_index.md b/content/influxdb3/explorer/about/_index.md
index 98a9a5cc50..5bc4b6fc44 100644
--- a/content/influxdb3/explorer/about/_index.md
+++ b/content/influxdb3/explorer/about/_index.md
@@ -18,6 +18,13 @@ Explorer is fully featured for [InfluxDB 3 Core](/influxdb3/core/) and
 [InfluxDB 3 Enterprise](/influxdb3/enterprise/).
 You can use Explorer to query data in and administer these products.
 
+Explorer runs as a standalone Docker container that works with either Core or
+Enterprise. Starting with InfluxDB 3 Enterprise v3.11, Explorer is also
+available as an integrated WebAssembly (WASM) component of the Enterprise
+server; it isn't distributed this way for Core. See
+[Install Explorer](/influxdb3/explorer/install/) to find the instructions for
+your InfluxDB 3 server.
+
 Explorer provides only _partial_ support for
 [InfluxDB Cloud Dedicated](/influxdb3/cloud-dedicated/) and
 [InfluxDB Cloud Serverless](/influxdb3/cloud-serverless/).
diff --git a/content/influxdb3/explorer/get-started.md b/content/influxdb3/explorer/get-started.md
index d46988ff37..33ca503d8e 100644
--- a/content/influxdb3/explorer/get-started.md
+++ b/content/influxdb3/explorer/get-started.md
@@ -73,7 +73,10 @@ InfluxDB 3 Explorer supports the following InfluxDB 3 products:
        > For Linux Docker Engine details, see the [Docker daemon documentation](https://docs.docker.com/reference/cli/dockerd/#configure-host-gateway-ip).
 
     - **Token**: The authorization token to use to connect to your InfluxDB 3 server.
-      We recommend using an InfluxDB 3 _admin_ token.
+      A resource token is enough to query and write data within the permissions
+      you grant it.
+      To manage databases, tokens, and other resources from Explorer, use an
+      admin token.
       
       > [!Important]
       > #### Token permissions determine Explorer's access
@@ -83,10 +86,18 @@ InfluxDB 3 Explorer supports the following InfluxDB 3 products:
       > tokens with limited permissions may not be able to use some Explorer
       > functionality.
       >
-      > The token's permissions also define what anyone with access to this
-      > Explorer instance can do. Use a token scoped to what you need, and
-      > control who can reach Explorer. See
-      > [Network exposure and access control](/influxdb3/explorer/install/#network-exposure-and-access-control).
+      > Without user authentication, the token's permissions also define what
+      > anyone with access to this Explorer instance can do. Use a token scoped
+      > to what you need, and control who can reach Explorer.
+      > With user authentication on an InfluxDB 3 Enterprise v3.12 or later
+      > server, users sign in first and their role determines what they can do.
+      > If you're running the
+      > [Docker container](/influxdb3/explorer/install/docker/), see
+      > [Network exposure and access control](/influxdb3/explorer/install/docker/#network-exposure-and-access-control).
+      > If you're using the
+      > [integrated Explorer UI](/influxdb3/enterprise/admin/explorer-ui/),
+      > control access through
+      > [`--http-bind`](/influxdb3/enterprise/reference/config-options/#http-bind).
 
 4.  Click **Add Server**.
 
diff --git a/content/influxdb3/explorer/install/_index.md b/content/influxdb3/explorer/install/_index.md
new file mode 100644
index 0000000000..d82a7753cf
--- /dev/null
+++ b/content/influxdb3/explorer/install/_index.md
@@ -0,0 +1,52 @@
+---
+title: Install InfluxDB 3 Explorer
+description: >
+  Install and run InfluxDB 3 Explorer. Instructions depend on your InfluxDB 3
+  server--integrated WASM for InfluxDB 3 Enterprise v3.11 and later, or
+  Docker for InfluxDB 3 Core and Enterprise.
+menu:
+  influxdb3_explorer:
+    name: Install Explorer
+weight: 2
+alt_links:
+  enterprise: /influxdb3/enterprise/admin/explorer-ui/
+related:
+  - /influxdb3/enterprise/admin/explorer-ui/, Use the integrated Explorer UI
+---
+
+How you install {{% product-name %}} depends on the InfluxDB 3 server you're
+connecting it to:
+
+- **InfluxDB 3 Enterprise v3.11 and later** includes Explorer as an
+  integrated WebAssembly (WASM) component--there's no separate container to
+  install. For setup instructions, see
+  [Use the integrated Explorer UI](/influxdb3/enterprise/admin/explorer-ui/).
+- **InfluxDB 3 Core and Enterprise** can run Explorer as a standalone Docker
+  container. Docker is required for Core and Enterprise earlier than v3.11.
+  For installation and configuration instructions, see
+  [Install and run InfluxDB 3 Explorer with Docker](/influxdb3/explorer/install/docker/).
+
+## Check which version applies to you
+
+If you already have an InfluxDB 3 server running, check its version and
+edition with `GET /ping`:
+
+```sh
+curl --get "http://localhost:8181/ping" \
+  --header "Authorization: Bearer AUTH_TOKEN"
+```
+
+The response includes the following version details:
+
+- `x-influxdb-version` reports the InfluxDB 3 server version.
+- `x-influxdb-build` reports whether the server is Core or Enterprise.
+- The response body includes the version in its `version` field.
+
+Use `GET`; a `HEAD` request to `/ping` returns `404`.
+
+If `x-influxdb-build` reports `Enterprise` and `x-influxdb-version` is `3.11`
+or later, use the
+[integrated Explorer UI](/influxdb3/enterprise/admin/explorer-ui/).
+Otherwise, use [Docker](/influxdb3/explorer/install/docker/).
+Docker also works with Enterprise v3.11 and later if you want to run Explorer
+separately from the server.
diff --git a/content/influxdb3/explorer/install.md b/content/influxdb3/explorer/install/docker.md
similarity index 95%
rename from content/influxdb3/explorer/install.md
rename to content/influxdb3/explorer/install/docker.md
index 7e9f0ede7b..04d6e7c6ac 100644
--- a/content/influxdb3/explorer/install.md
+++ b/content/influxdb3/explorer/install/docker.md
@@ -1,14 +1,23 @@
 ---
-title: Install and run InfluxDB 3 Explorer
+title: Install and run InfluxDB 3 Explorer with Docker
 description: >
-  Use [Docker](https://docker.com) to install and run **InfluxDB 3 Explorer**.
+  Use [Docker](https://docker.com) to install and run **InfluxDB 3 Explorer**
+  as a standalone container against InfluxDB 3 Core or Enterprise.
 menu:
   influxdb3_explorer:
-    name: Install Explorer
-weight: 2
+    name: Docker
+weight: 1
+metadata: [InfluxDB 3 Core and Enterprise]
 ---
 
-Use [Docker](https://docker.com) to install and run **InfluxDB 3 Explorer**.
+Use [Docker](https://docker.com) to install and run **InfluxDB 3 Explorer**
+as a standalone container with [InfluxDB 3 Core](/influxdb3/core/) or
+[InfluxDB 3 Enterprise](/influxdb3/enterprise/), including Enterprise v3.11
+and later.
+Starting with Enterprise v3.11, Explorer is also available as an integrated
+WebAssembly (WASM) component of the server. See
+[Use the integrated Explorer UI](/influxdb3/enterprise/admin/explorer-ui/)
+if you run Enterprise v3.11 or later and don't need a separate container.
 
 > [!Important]
 > #### Control who can reach Explorer
@@ -232,8 +241,8 @@ Use the following practices to control access:
 
    {{< code-tabs-wrapper >}}
    {{% code-tabs %}}
-   [Docker](#)
-   [Docker Compose](#)
+   [Run container](#)
+   [Compose](#)
    {{% /code-tabs %}}
 
    {{% code-tab-content %}}
@@ -350,8 +359,8 @@ Instead of configuring connections through the UI, you can pre-define connection
 
    {{< code-tabs-wrapper >}}
    {{% code-tabs %}}
-   [Docker](#)
-   [Docker Compose](#)
+   [Run container](#)
+   [Compose](#)
    {{% /code-tabs %}}
 
    {{% code-tab-content %}}
@@ -405,8 +414,8 @@ To enable TLS/SSL for secure connections:
 
    {{< code-tabs-wrapper >}}
    {{% code-tabs %}}
-   [Docker](#)
-   [Docker Compose](#)
+   [Run container](#)
+   [Compose](#)
    {{% /code-tabs %}}
 
    {{% code-tab-content %}}
@@ -481,12 +490,12 @@ To configure Explorer to trust self-signed or custom CA certificates when connec
 3. **Mount the CA certificate directory and set the `NODE_EXTRA_CA_CERTS` environment variable:**
 
 {{< expand-wrapper >}}
-{{% expand "View example Docker configuration for self-signed certificates" %}}
+{{% expand "View example configuration for self-signed certificates" %}}
 
 {{< code-tabs-wrapper >}}
 {{% code-tabs %}}
-[Docker](#)
-[Docker Compose](#)
+[Run container](#)
+[Compose](#)
 {{% /code-tabs %}}
 {{% code-tab-content %}}
 
@@ -548,8 +557,8 @@ Set the mode using the `--mode` parameter:
 
 {{< code-tabs-wrapper >}}
 {{% code-tabs %}}
-[Docker](#)
-[Docker Compose](#)
+[Run container](#)
+[Compose](#)
 {{% /code-tabs %}}
 
 {{% code-tab-content %}}
@@ -635,8 +644,8 @@ services:
 
 {{< code-tabs-wrapper >}}
 {{% code-tabs %}}
-[Docker](#)
-[Docker Compose](#)
+[Run container](#)
+[Compose](#)
 {{% /code-tabs %}}
 
 {{% code-tab-content %}}
diff --git a/content/influxdb3/explorer/manage-databases.md b/content/influxdb3/explorer/manage-databases.md
index 2759afeea2..22ea4b46c1 100644
--- a/content/influxdb3/explorer/manage-databases.md
+++ b/content/influxdb3/explorer/manage-databases.md
@@ -17,9 +17,12 @@ or InfluxDB 3 Enterprise cluster.
 
 > [!Important]
 > Using {{% product-name %}} to manage a database in InfluxDB 3 requires that
-> Explorer is running in [admin mode](/influxdb3/explorer/install/#choose-operational-mode)
-> and that the token used in the InfluxDB 3 server configuration is an
+> the token used in the InfluxDB 3 server configuration is an
 > [admin token](/influxdb3/enterprise/admin/tokens/admin/).
+> If you're running the
+> [Docker container](/influxdb3/explorer/install/docker/), Explorer must also
+> be running in
+> [admin mode](/influxdb3/explorer/install/docker/#choose-operational-mode).
 
 To manage databases, navigate to **Manage Databases** in Explorer.
 This page provides a list of databases in the connected InfluxDB 3 server that
diff --git a/content/influxdb3/explorer/manage-tokens.md b/content/influxdb3/explorer/manage-tokens.md
index 7034aa690d..e915c70d03 100644
--- a/content/influxdb3/explorer/manage-tokens.md
+++ b/content/influxdb3/explorer/manage-tokens.md
@@ -16,10 +16,13 @@ related:
 Core instance or InfluxDB 3 Enterprise cluster.
 
 > [!Important]
-> Using {{% product-name %}} to manage authorization tokens in InfluxDB 3 requires that
-> Explorer is running in [admin mode](/influxdb3/explorer/install/#choose-operational-mode)
-> and that the token used in the InfluxDB 3 server configuration is an
+> Using {{% product-name %}} to manage authorization tokens in InfluxDB 3
+> requires that the token used in the InfluxDB 3 server configuration is an
 > [admin token](/influxdb3/enterprise/admin/tokens/admin/).
+> If you're running the
+> [Docker container](/influxdb3/explorer/install/docker/), Explorer must also
+> be running in
+> [admin mode](/influxdb3/explorer/install/docker/#choose-operational-mode).
 
 To manage InfluxDB authorization tokens, navigate to **Manage Tokens** in Explorer.
 This page provides a list of databases in the connected InfluxDB 3 server that
diff --git a/content/influxdb3/explorer/release-notes/_index.md b/content/influxdb3/explorer/release-notes/_index.md
index 0f4ae87608..c427214e5e 100644
--- a/content/influxdb3/explorer/release-notes/_index.md
+++ b/content/influxdb3/explorer/release-notes/_index.md
@@ -10,11 +10,88 @@ related:
   - /influxdb3/explorer/
 ---
 
-To upgrade, pull the latest Docker image:
+To upgrade, use the method you run Explorer with:
+
+{{< expand-wrapper >}}
+{{% expand "Integrated web UI (InfluxDB 3 Enterprise)" %}}
+Explorer is built into InfluxDB 3 Enterprise 3.11 and later.
+[Upgrade InfluxDB 3 Enterprise](/influxdb3/enterprise/admin/upgrade/)
+and start it with `--mode all,webui`.
+{{% /expand %}}
+{{% expand "Standalone Docker image" %}}
+Pull the latest image:
 
 ```sh
 docker pull influxdata/influxdb3-ui
 ```
+{{% /expand %}}
+{{< /expand-wrapper >}}
+
+## v1.11.0 {date="2026-09-30"}
+
+#### Features
+
+- **Password sign-in**: Sign in with a username and password when connected to an InfluxDB 3 Enterprise server that uses [user authentication](/influxdb3/enterprise/admin/security/manage-users/).
+  On first run, create the administrator account and save the operator token.
+- **Single sign-on**: Sign in through an OpenID Connect (OIDC) provider.
+- **Role-based access**: Explorer shows the pages and actions your role allows.
+  After upgrading, choose whether to keep your existing dashboards and saved queries; stored keys and tokens are not carried over.
+- **Manage Users**: Add users with password, SSO, or both; assign roles; require a password reset; and delete users from the new **Manage Users** page.
+  Change your own password from the profile menu.
+- **Security navigation section**: Find **Tokens** and **Users** under a new **Security** section in the navigation.
+- **New visualization types**: Visualize query results as Area, Single Stat, Gauge, Pie, Scatter, and Ranking charts in the Data Explorer and in dashboard cells.
+- **EXPLAIN in SQL**: Run `EXPLAIN` and `EXPLAIN ANALYZE` statements in the SQL editor to view query plans.
+- **Flux to SQL feedback**: Rate a conversion and add an optional comment.
+
+#### Bug fixes
+
+- **Query mode**: Enforce read-only access on the server. In query mode, admin API endpoints now refuse requests instead of only hiding the admin pages.
+- **Security**: Stop sending the InfluxDB token to plugin registry URLs, refuse registry fetches to internal addresses, and update dependency versions.
+- **SQL**: Fix `SELECT *` over CTEs and subqueries without a time column failing, and show the reason a query was rejected instead of "Something went wrong".
+- **Data Explorer**: Keep the Export button visible and disable it when there is nothing to export, and stop paging through results from adding history entries and re-fetching chart data.
+- **Transform Data**: Fix Rename Table and Filter Data transformations that deployed but never wrote data, and show an error status when a trigger's latest run fails.
+- **Downsample**: Fix jobs with minute-level intervals writing one row per series instead of one row per interval.
+- **Plugins**: Fix deploys failing on InfluxDB 3.12 when a plugin has no Python dependencies, show why an install failed in the deploy dialog, and stop reporting successful package installs as errors.
+- **Plugins**: Show the plugin's response status and body in Run Now, including failures, and export trigger logs as plain text.
+- **Plugins**: Hide the `_internal` database from deploy dialogs, fix the copied CLI install command, display plugin names as provided by the registry, and make the Signal Generator plugin available for InfluxDB 3 Cloud servers.
+- **Connections**: Accept database-scoped tokens when adding an InfluxDB 3 Enterprise server, and report a refused token instead of showing empty states.
+- **Connections**: Explain an untrusted TLS certificate instead of reporting the server as unreachable, honor `DEFAULT_INFLUX_DATABASE`, and fix the Enterprise start command in the Configure Servers onboarding steps.
+- **System overview**: Fix status colors and labels in the query log, fix the query history failing on Enterprise while a query is running, and fix the request count that showed the number of metric series.
+- **Query history**: Fix search returning no results for terms containing an underscore.
+- **Command line builder**: Show the product name instead of a number in the start command hint.
+- **Caches**: Fix the empty-state message on the Distinct Value Caches tab.
+- **Version display**: Show the correct release version in the sidebar.
+- **Layout**: Fix page header button sizing and dashboard list spacing.
+
+## v1.10.1 {date="2026-08-03"}
+
+#### Bug fixes
+
+- **Upgrades**: Restore dashboards that disappeared after upgrading from v1.9.0 with a pre-configured default server.
+- **Charts**: Plot the full SQL query result instead of only the rows on the current table page.
+- **SQL**: Fix `SHOW` and `DESCRIBE` statements failing in the Data Explorer.
+- **Query history**: Preserve the query language so saved InfluxQL queries load in the InfluxQL editor.
+- **Databases**: Keep deleted databases hidden in database selectors unless you choose to show them.
+- **Dashboards**: Restore vertical scrolling on dashboard pages.
+- **Plugins**: Show a clear message when the Processing Engine isn't enabled, and fix the heading of the Add Registry dialog.
+- **Write data**: Improve error messages for CSV and JSON imports.
+- **Security**: Update dependency versions.
+
+## v1.10.0 {date="2026-07-29"}
+
+#### Features
+
+- **Plugin registries**: The Plugin Library now loads plugins from the InfluxData plugin registry, and you can add other registries by name and index URL to browse and install plugins from additional sources.
+  Plugin cards show logos, New and Beta tags, and the required InfluxDB version, and each plugin page includes a copyable CLI install command.
+- **Server setup guide**: The Configure Servers empty state walks you through connecting your first server, with copyable CLI commands for finding the server URL and creating an admin token.
+- **Configure AI in place**: Configure a missing AI provider from a dialog without leaving the current page.
+- **Stock Portfolio Tracker**: Generate live sample data with the new Stock Portfolio Tracker plugin.
+- **Faster page loads**: Admin pages and the query page load on demand.
+
+#### Bug fixes
+
+- **Queries**: Loading a saved InfluxQL query opens the InfluxQL tab.
+- **Charts**: Fit the time axis to the selected time range instead of the data extent.
 
 ## v1.9.0 {date="2026-06-22"}
 
@@ -66,7 +143,7 @@ docker pull influxdata/influxdb3-ui
 #### Breaking changes
 
 - **Container user change**: The Docker container now runs as non-root user `influxui` (uid 1500) instead of root for improved security.
-- **Upgrade action**: See [Install InfluxDB 3 Explorer](/influxdb3/explorer/install/#set-file-permissions-for-upgrades)
+- **Upgrade action**: See [Install and run InfluxDB 3 Explorer with Docker](/influxdb3/explorer/install/docker/#set-file-permissions-for-upgrades)
   for upgrade file permission steps.
 
 #### Features
diff --git a/data/products.yml b/data/products.yml
index 596dd5c89f..55896c965d 100644
--- a/data/products.yml
+++ b/data/products.yml
@@ -142,7 +142,7 @@ influxdb3_explorer:
   list_order: 1
   search_includes_resources: false
   latest: explorer
-  latest_patch: 1.9.0
+  latest_patch: 1.11.0
   placeholder_host: localhost:8080
   scheme: http
   ai_sample_questions:
diff --git a/docs/exec-plans/2026-09-02-explorer-install-version-routing.md b/docs/exec-plans/2026-09-02-explorer-install-version-routing.md
new file mode 100644
index 0000000000..43b5fa2f78
--- /dev/null
+++ b/docs/exec-plans/2026-09-02-explorer-install-version-routing.md
@@ -0,0 +1,121 @@
+# Explorer install docs: route by version and edition
+
+**Status:** In review — PR [#7734](https://github.com/influxdata/docs-v2/pull/7734)
+**Closes:** [#6702](https://github.com/influxdata/docs-v2/issues/6702)
+
+## Goal
+
+Restructure the InfluxDB 3 Explorer install documentation so that each page
+states which Explorer versions and which InfluxDB 3 editions it applies to.
+After this change, `/influxdb3/explorer/install/` routes readers by version
+instead of presenting Docker as the only deployment method, and the Docker
+instructions live on a child page that states which products they support.
+
+## Why now
+
+Starting with InfluxDB 3 Enterprise v3.11, Explorer is included with the
+server and deployed as WebAssembly (WASM).
+The standalone Docker container remains available for Core and Enterprise.
+The original pages have no version or edition scoping:
+
+- `content/influxdb3/explorer/install.md` documents only Docker.
+- `content/influxdb3/explorer/_index.md` repeats a `docker pull` quick start.
+- `content/influxdb3/explorer/about/_index.md` states full Core and Enterprise
+  support with no end version.
+- `data/products.yml` lists `Docker` in `schema.operating_system`, which feeds
+  the JSON-LD `SoftwareApplication` node.
+
+Each of these tells readers, search engines, retrieval systems, and coding
+agents only about the Docker deployment.
+The restructure adds the integrated Enterprise path without removing Docker.
+
+Issue #6702 reports the related gap: the docs never state outright which
+distributions exist, so a docs-grounded assistant can only infer the
+limitation.
+
+## Decisions
+
+- **Keep `/influxdb3/explorer/install/` as the URL and convert it to a
+  version-routing hub.** The URL holds the search ranking, seven inbound
+  in-repo links (three of them deep anchors), the `llms.txt` corpus entry, and
+  any existing model memory. Moving the page under `/get-started/` or demoting
+  it in the navigation would break those without addressing the actual problem,
+  which is the page content, not its address.
+- **Move the Docker body to `install/docker.md` unchanged.** Keeping the body
+  intact preserves the three anchors that other pages link to:
+  `#choose-operational-mode`, `#network-exposure-and-access-control`, and
+  `#set-file-permissions-for-upgrades`.
+- **Do not redirect `/install/` to `/install/docker/`.** A redirect would send
+  every "install Explorer" search result and every agent's first URL guess to
+  the Docker path, even when they run Enterprise v3.11 or later.
+- **State Docker compatibility without a version ceiling.** Product review in
+  [PR #7788](https://github.com/influxdata/docs-v2/pull/7788) confirmed that
+  Docker remains supported with Enterprise v3.11 and later.
+- **Keep the Docker page published and indexed.** Docker remains required for
+  Core and Enterprise earlier than v3.11, and remains optional for later
+  Enterprise releases.
+- **Use `cascade.prepend` on `explorer/_index.md` for the transition notice,
+  not a template banner.** `article/stable-version.html` is gated on a
+  hardcoded product whitelist and a `/vN/` URL segment, neither of which
+  applies to Explorer, and extending it would add magic values to a template
+  (see `.claude/rules/layouts.md`). `article/special-state.html` has the same
+  problem. `cascade.prepend` is documented in `DOCS-FRONTMATTER.md` and needs no
+  template change.
+- **Accept the twin cost of the cascaded notice, and remove it at v1.11.**
+  Prepended content appears in every Explorer Markdown twin and in
+  `llms-full.txt`, which makes the first chunk of all 12 Explorer pages more
+  alike (the twin-hygiene problem tracked in
+  [#7323](https://github.com/influxdata/docs-v2/issues/7323)). The notice is
+  three lines and is worth that cost while the transition is live.
+- **Document version verification with `GET /ping`, not only
+  `influxdb3 --version`.** WASM availability depends on the InfluxDB 3 server
+  version and build, not on Explorer alone. `GET /ping` returns
+  `x-influxdb-version` and `x-influxdb-build` (`Core` or `Enterprise`) in
+  headers and `version` in the body
+  (`api-docs/influxdb3/enterprise/influxdb3-enterprise-openapi.yaml`), so one
+  command answers both questions and works headlessly against a remote
+  instance. A `HEAD` request returns 404, so the docs specify `GET`.
+
+## Explicitly out of scope
+
+- New Explorer feature pages and the v1.11 release notes. This change only
+  prepares the routing and cross-links.
+- `data/products.yml` updates to `latest_patch` and `schema.operating_system`.
+  Both change on release day, not before.
+- The `localhost` connection failure reported in
+  [#7333](https://github.com/influxdata/docs-v2/issues/7333). It affects the
+  Docker instructions but is a separate content fix.
+- Extending `article/stable-version.html` to support products without a `/vN/`
+  URL segment.
+
+## How to update
+
+The Docker compatibility statement appears in the `metadata` frontmatter,
+the `description` frontmatter, and the lede of
+`content/influxdb3/explorer/install/docker.md`.
+The transition notice cascades from `content/influxdb3/explorer/_index.md`
+to every Explorer page.
+Remove the `cascade.prepend` block when v1.11 ships.
+
+## Verification
+
+1. `npx hugo --quiet` builds without errors.
+2. Confirm the three anchors still resolve within `install/docker/`, and that no
+   in-repo link points at `/influxdb3/explorer/install/#` for a Docker-only
+   section.
+3. `yarn check:md-coherence` confirms the head link, `sitemap-md.xml`, and
+   corpus surfaces agree after the URL structure changes.
+4. Run the Cypress navigation tests. Converting a single page to a section
+   changes the menu tree.
+5. After deploy, check the published Markdown twins. PR previews return 404 for
+   twins, so use production or staging:
+
+   ```sh
+   curl -s --compressed https://docs.influxdata.com/influxdb3/explorer/install/index.md | head -20
+   curl -s --compressed https://docs.influxdata.com/influxdb3/explorer/install/docker/index.md | head -20
+   ```
+
+   The Docker twin starts with `* InfluxDB 3 Core and Enterprise` above the lede.
+6. Ask the documentation MCP server "How do I install InfluxDB 3 Explorer?"
+   after the corpus rebuilds. The answer routes by version instead of returning
+   `docker run`.
diff --git a/docs/exec-plans/2026-09-02-explorer-v110-release-readiness.md b/docs/exec-plans/2026-09-02-explorer-v110-release-readiness.md
new file mode 100644
index 0000000000..cf657c0286
--- /dev/null
+++ b/docs/exec-plans/2026-09-02-explorer-v110-release-readiness.md
@@ -0,0 +1,99 @@
+# Explorer v1.10 release readiness
+
+**Status:** In progress — PR [#7734](https://github.com/influxdata/docs-v2/pull/7734)
+**Refs:** [2026-09-02-explorer-install-version-routing.md](2026-09-02-explorer-install-version-routing.md)
+
+## Goal
+
+Define the documentation work for the InfluxDB 3 Explorer v1.10 release and the
+InfluxDB 3 Enterprise release that carries it. The install restructure prepares
+the version routing; this plan covers what changes when v1.10 ships.
+
+## Decisions
+
+- **Every new feature page tells the reader how to check whether their version
+  has the feature.** A version marker states the requirement, but a reader
+  arriving from search doesn't know which version they're running. Each feature
+  page states the requirement and shows the check, or links to the check in the
+  install hub. See
+  [DOCS-VERSION-AVAILABILITY.md](../../DOCS-VERSION-AVAILABILITY.md).
+- **The check covers both the Explorer version and the InfluxDB 3 server
+  version and edition.** A v1.10 feature can require both. `GET /ping` returns
+  `x-influxdb-version` and `x-influxdb-build` (`Core` or `Enterprise`), so it
+  answers the server half in one request, including against a remote instance.
+- **Merge at release rather than publishing with `draft: true`.** Content pages
+  merge on release day. Use `draft: true` only when a page must exist in the
+  branch before the release for a specific reason, such as a link target that
+  other merged content depends on.
+- **Use `data/notifications.yaml` for the release announcement, and keep the
+  version facts in the pages.** Notifications render in the footer, outside the
+  article, so they don't appear in Markdown twins or `llms-full.txt`. The
+  announcement is for readers; the version scope that agents and retrieval
+  systems need stays in frontmatter and the lede.
+- **Order the release-day merge so no published page points at an unpublished
+  one.** Feature pages first, then the install hub lede, then
+  `data/products.yml`.
+
+## Before the release
+
+1. Write each new feature page with its version marker: page-level `metadata:`
+   when the whole page is new in v1.10, a `{metadata="v1.10+"}` heading
+   attribute when only a section is.
+2. Add the version check to each feature page. State the Explorer version the
+   feature requires and, when the feature depends on the server, the InfluxDB 3
+   version and edition. Show the `/ping` request or link to the check in the
+   install hub.
+3. Add the WASM deployment instructions to the InfluxDB 3 Enterprise section,
+   including the server version that introduced them.
+4. Add `alt_links` in both directions between each Explorer feature page and
+   the Enterprise page that documents the server side.
+5. Write the release notes entry in
+   `content/influxdb3/explorer/release-notes/_index.md`.
+6. Add a commented-out `data/notifications.yaml` entry with the final `id`,
+   `scope`, `title`, and `slug`, following the `influxdb3-cloud-ga` stub
+   already in that file.
+
+## On release day
+
+Merge in this order.
+
+1. Feature pages and the Enterprise WASM deployment page.
+2. The install hub lede at `content/influxdb3/explorer/install/_index.md`, so
+   the WASM path is described first and Docker reads as the path for v1.9 and
+   earlier.
+3. `data/products.yml`: set `latest_patch` to the new Explorer version and
+   update `schema.operating_system`, which lists `Docker` and feeds the JSON-LD
+   `SoftwareApplication` node.
+4. The release notes entry.
+5. The `data/notifications.yaml` entry, uncommented.
+
+## At v1.11
+
+1. Delete the `data/notifications.yaml` entry by `id`.
+2. Remove the `cascade.prepend` transition notice from
+   `content/influxdb3/explorer/_index.md`.
+3. Leave the frontmatter version markers. They state a fact about the release,
+   not a temporary condition.
+
+## Verification
+
+1. `npx hugo --quiet` builds without errors.
+
+2. `yarn check:md-coherence` confirms the head links, `sitemap-md.xml`, and
+   corpus surfaces agree after the new pages publish.
+
+3. The notification renders on its scoped paths and not on the excluded ones.
+
+4. After deploy, the version marker leads each new page's Markdown twin. PR
+   previews return 404 for twins, so use production or staging:
+
+   ```sh
+   curl -s --compressed https://docs.influxdata.com/influxdb3/explorer/<page>/index.md | head -20
+   ```
+
+5. The notification text appears in neither the twins nor
+   `https://docs.influxdata.com/influxdb3/explorer/llms-full.txt`. If it does,
+   it was added to the wrong surface.
+
+6. Ask the documentation MCP server how to use a new v1.10 feature. The answer
+   states the version requirement and how to check it.