From 9c2eb640f650ef241328451fbc10143e4f0cae98 Mon Sep 17 00:00:00 2001 From: rdlabo Date: Wed, 18 Nov 2026 20:42:03 +0900 Subject: [PATCH 1/3] docs: Start the Engine guides with native view registration --- README.md | 6 ++---- docs/README.md | 10 +--------- 2 files changed, 3 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index 8663449..f7e221e 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,6 @@ -# Beyond the WebView. +# WebView Native UI Engine -**Bring Native UI seamlessly into Web apps.** - -Build your screens with the flexibility of the Web and the controls and capabilities of native platforms. WebView Native UI Engine helps them work together as one experience, while keeping your Web layouts and navigation. +Integrate native views into Web-driven screens in a Capacitor or Cordova plugin. Start by [registering a native view and its Web container](docs/getting-started/initialization.md). ## Web UI. Native UI. One experience. diff --git a/docs/README.md b/docs/README.md index 3614904..01f14b0 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,14 +1,6 @@ # Documentation -Build Web-driven screens with native controls and capabilities. These guides -explain how to integrate the Engine into a plugin so Web UI and Native UI can -coexist. Start with [the shared model](concepts.md): how a native component belongs in a Web layout, -which layer presents it, and how interaction returns to the live view. Scrolling -and overlays are examples of that coordination, not separate integration models. - -Then choose the smallest integration that fits your ownership model. Register a -native view and its DOM container, connect the lifecycle notifications your UI -needs, and add advanced APIs only if you already own a renderer's batching or placement. +Start with [basic registration](getting-started/initialization.md) to connect a native view to its DOM container. Then follow the host guide for [Capacitor](getting-started/capacitor.md) or [Cordova](getting-started/cordova.md). The [shared model](concepts.md) explains how scrolling, overlays and interaction work across the two layers. ## Choose by the problem you need to solve From 1b5a74fff450d094a61737a7ab04f13b594ea886 Mon Sep 17 00:00:00 2001 From: rdlabo Date: Wed, 18 Nov 2026 20:51:50 +0900 Subject: [PATCH 2/3] docs: link README guides to the documentation website --- README.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index f7e221e..428054f 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # WebView Native UI Engine -Integrate native views into Web-driven screens in a Capacitor or Cordova plugin. Start by [registering a native view and its Web container](docs/getting-started/initialization.md). +Integrate native views into Web-driven screens in a Capacitor or Cordova plugin. Start by [registering a native view and its Web container](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/getting-started/initialization). ## Web UI. Native UI. One experience. @@ -33,7 +33,7 @@ The plugin supplies a native view and a DOM container that defines its place in When the Web layer needs to own presentation, the Engine displays a prepared image of the native component in that container. When native presentation can resume, it coordinates placement and restoration of the interactive view. -The image is a temporary visual projection, not a second interactive control. It does not forward clicks or play live video. Capture eligibility and platform rendering limits still apply, including differences in Liquid Glass highlights. When a suitable image is unavailable, the integration uses its configured Web fallback. See [concepts and limits](docs/concepts.md) and [platform support](docs/reference/platforms.md) before choosing a component. +The image is a temporary visual projection, not a second interactive control. It does not forward clicks or play live video. Capture eligibility and platform rendering limits still apply, including differences in Liquid Glass highlights. When a suitable image is unavailable, the integration uses its configured Web fallback. See [concepts and limits](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/concepts) and [platform support](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/reference/platforms) before choosing a component. On iOS 26+, an experimental workaround using a **private Apple API** is enabled by default for Liquid Glass capture. Review the risks and [disable it if required](docs/experimental/glass-capture.md) before adopting this version. @@ -43,10 +43,10 @@ The Engine supports **iOS and Android**. Ionic and Angular are optional. Start w | Start here | Why | | -------------------------------------------------------------- | ------------------------------------------------------------------------------------- | -| [Basic initialization](docs/getting-started/initialization.md) | Register a native view and its DOM container with the minimum required setup. | -| [Capacitor plugin guide](docs/getting-started/capacitor.md) | Connect the Engine to an existing Capacitor plugin. | -| [Cordova plugin guide](docs/getting-started/cordova.md) | Use the same lifecycle through Cordova's native hooks. | -| [Documentation](docs/README.md) | Find optional settings, renderer APIs and reference by the problem you need to solve. | +| [Basic initialization](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/getting-started/initialization) | Register a native view and its DOM container with the minimum required setup. | +| [Capacitor plugin guide](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/getting-started/capacitor) | Connect the Engine to an existing Capacitor plugin. | +| [Cordova plugin guide](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/getting-started/cordova) | Use the same lifecycle through Cordova's native hooks. | +| [Documentation](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/overview) | Find optional settings, renderer APIs and reference by the problem you need to solve. | Use matching Engine versions across npm and native dependencies, and retain dependency lockfiles for reproducible builds. Android placement requires API 23+, with composited snapshots available from API 26+. @@ -60,14 +60,14 @@ import { enableSupportIonicOverlays } from '@webview-native-ui/engine/ionic'; enableSupportIonicOverlays(); ``` -Call it once during application startup unless your plugin already enables it. Applications importing it directly need `@webview-native-ui/engine` as a direct dependency. This shared framework integration coordinates coverage across plugins; each plugin retains control of its own presentation API. See [Ionic overlay support](docs/configuration/ionic-overlays.md) for setup, supported overlays and renderer helpers. +Call it once during application startup unless your plugin already enables it. Applications importing it directly need `@webview-native-ui/engine` as a direct dependency. This shared framework integration coordinates coverage across plugins; each plugin retains control of its own presentation API. See [Ionic overlay support](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/configuration/ionic-overlays) for setup, supported overlays and renderer helpers. ## Contributing -For repository development, verification and publishing, see [development and releases](docs/maintenance.md). +For repository development, verification and publishing, see [development and releases](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/maintenance). ## License [MIT](LICENSE). Commercial use, modification and redistribution are permitted with the license's notice and attribution requirements. The Engine's license does not change the licenses of applications or plugins that depend on it. -For the optional shared control runtime and adapter boundaries, see [shared controls](docs/controls.md). +For the optional shared control runtime and adapter boundaries, see [shared controls](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/controls). From 02e2e21af9c510f723b297f243c31c07391b1f15 Mon Sep 17 00:00:00 2001 From: rdlabo Date: Wed, 18 Nov 2026 20:56:37 +0900 Subject: [PATCH 3/3] docs: apply package guide review feedback --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 428054f..ee5c681 100644 --- a/README.md +++ b/README.md @@ -41,12 +41,12 @@ On iOS 26+, an experimental workaround using a **private Apple API** is enabled The Engine supports **iOS and Android**. Ionic and Angular are optional. Start with a native view and its DOM container, then connect the lifecycle notifications your UI needs. The integration guides cover runtime startup and optional framework support. -| Start here | Why | -| -------------------------------------------------------------- | ------------------------------------------------------------------------------------- | +| Start here | Why | +| --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | | [Basic initialization](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/getting-started/initialization) | Register a native view and its DOM container with the minimum required setup. | | [Capacitor plugin guide](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/getting-started/capacitor) | Connect the Engine to an existing Capacitor plugin. | | [Cordova plugin guide](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/getting-started/cordova) | Use the same lifecycle through Cordova's native hooks. | -| [Documentation](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/overview) | Find optional settings, renderer APIs and reference by the problem you need to solve. | +| [Documentation](https://webview-native-ui.com/projects/webview-native-ui-engine/docs/overview) | Find optional settings, renderer APIs and reference by the problem you need to solve. | Use matching Engine versions across npm and native dependencies, and retain dependency lockfiles for reproducible builds. Android placement requires API 23+, with composited snapshots available from API 26+.