Publish non-React Low-Code integration guide

docs/en/docs-nav.json

@@ -2117,6 +2117,14 @@
           "text": "React Runtime",
           "path": "low-code/react-runtime.md"
         },
+        {
+          "text": "Add to an Existing Solution",
+          "path": "low-code/add-to-existing-solution.md"
+        },
+        {
+          "text": "Non-React UI Integration",
+          "path": "low-code/non-react-ui-integration.md"
+        },
         {
           "text": "Health",
           "path": "low-code/health.md"

docs/en/low-code/index.md

@@ -51,7 +51,7 @@ The generated React project includes:
 * `useMenuItems`
 * Page, form, dashboard, file, and attachment hooks
 
-If you already have a compatible solution and want to retrofit Low-Code later, see [Add Low-Code to an Existing Solution](add-to-existing-solution.md).
+If you already have a compatible solution and want to retrofit Low-Code later, see [Add Low-Code to an Existing Solution](add-to-existing-solution.md). When the existing UI is MVC, Razor Pages, Angular, or Blazor, continue with [Use Low-Code from a Non-React Application](non-react-ui-integration.md) for the companion runtime and navigation integration.
 
 The host application wires the low-code modules, calls the generated `_Dynamic` initializer, configures EF Core dynamic entities, and seeds the required OpenIddict clients.
 
@@ -175,6 +175,7 @@ The designer stores and reads the same descriptor metadata described in the refe
 |-------|------------|
 | [Designer](designer.md) | Admin Console tabs, entity/page/form setup, permissions, and health |
 | [Add Low-Code to an Existing Solution](add-to-existing-solution.md) | Retrofitting an existing EF Core solution with Studio import plus manual backend and React wiring |
+| [Use Low-Code from a Non-React Application](non-react-ui-integration.md) | Keeping an MVC, Razor Pages, Angular, or Blazor UI while hosting the React Low-Code runtime and Designer alongside it |
 | [React Runtime](react-runtime.md) | React package wiring, routes, menu items, filters, forms, and export |
 | [Health](health.md) | Selected-layer readiness review across entities, pages, forms, page groups, permissions, and scripts |
 | [Dashboards](dashboards.md) | Dashboard page descriptors, visualization layout, filters, and runtime data flow |
@@ -205,6 +206,7 @@ The generated pages are powered by these services:
 
 * [Low-Code Designer](designer.md)
 * [Add Low-Code to an Existing Solution](add-to-existing-solution.md)
+* [Use Low-Code from a Non-React Application](non-react-ui-integration.md)
 * [React Runtime](react-runtime.md)
 * [Health](health.md)
 * [Dashboards](dashboards.md)

docs/en/low-code/non-react-ui-integration.md

@@ -1,13 +1,13 @@
 ```json
 //[doc-seo]
 {
-    "Description": "Internal draft for adding the Low-Code designer and a companion React runtime to an existing MVC, Razor Pages, Blazor, or Angular ABP application."
+    "Description": "Add the Low-Code designer and a companion React runtime to an existing MVC, Razor Pages, Blazor, or Angular ABP application."
 }
 ```
 
 # Use Low-Code from a Non-React Application
 
-> **Internal draft and target release:** This page is intentionally not linked from the Low-Code index or the documentation navigation. It targets the ABP `10.6.x` release line and .NET `10`. Keep the existing solution, Admin Console, Low-Code backend, and companion React packages on the same `10.6.x` patch version.
+> **Target release:** This guide targets the ABP `10.6.x` release line and .NET `10`. Keep the existing solution, Admin Console, Low-Code backend, and companion React packages on the same `10.6.x` patch version.
 
 > **Verification history:** The workflow was first verified on July 22, 2026 with ABP `10.5.0`, .NET `10`, a layered MVC application, a layered Angular application, and a layered Blazor Web App application. Version-specific `10.5.0` observations below are historical regression checkpoints, not package-version instructions for a `10.6.x` solution.