@thebase/ui 1.2.1 → 1.3.0

package/docs/components/popover.md

@@ -5,7 +5,7 @@ Use `b-ui="popover"` with trigger and content nodes.
 ## Base component
 
 ```js
-import { Popover, PopoverContent, PopoverTrigger } from "@thebase/ui";
+import { Popover, PopoverContent, PopoverTrigger } from "nodexui";
 ```
 
 ```base-ui
@@ -32,13 +32,13 @@ import { Popover, PopoverContent, PopoverTrigger } from "@thebase/ui";
 | `PopoverContent` | `className` | `String` | optional |
 | `PopoverTrigger` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
-Both the pure Base and static forms are driven by a live `bootstrap.Popover` instance owned on the trigger element — **the visible popup is Bootstrap's own generated DOM (a `.popover`/`.popover-arrow`/`.popover-body` node, positioned via Popper), appended to `document.body`, not rendered inline where you authored the popover.** Don't query for it as a descendant of the trigger or root; query `document.body.querySelector(".popover .popover-body")` instead. There's no separate heading/title concept in the current API — only body content (`.popover-body`); no `.popover-header` is generated.
+Both the pure Base and static forms are driven by a live `bootstrap.Popover` instance owned on the trigger element — **the visible popup is the built-in generated DOM (a `.popover`/`.popover-arrow`/`.popover-body` node, positioned via Popper), appended to `document.body`, not rendered inline where you authored the popover.** Don't query for it as a descendant of the trigger or root; query `document.body.querySelector(".popover .popover-body")` instead. There's no separate heading/title concept in the current API — only body content (`.popover-body`); no `.popover-header` is generated.
 
-The default slot's rendered markup is captured into an HTML string for Bootstrap's `content`/`html: true` options (Bootstrap can't consume live vnodes): `PopoverContent` renders the slot into a hidden buffer element internal to its own template (it is no longer a visibly-toggled popup itself), `PopoverTrigger` reads that buffer's `innerHTML` on mount to seed the bootstrap instance, and re-syncs the live popup via `.setContent({'.popover-body': html})` whenever that HTML changes on a later render.
+The default slot's rendered markup is captured into an HTML string for the built-in `content`/`html: true` options (the library can't consume live vnodes): `PopoverContent` renders the slot into a hidden buffer element internal to its own template (it is no longer a visibly-toggled popup itself), `PopoverTrigger` reads that buffer's `innerHTML` on mount to seed the bootstrap instance, and re-syncs the live popup via `.setContent({'.popover-body': html})` whenever that HTML changes on a later render.
 
-Unlike `Tooltip`/hover-driven components, Bootstrap's own `trigger: "click"` option would bind its own click listener directly on the trigger element, independent of `PopoverTrigger`'s own `t-on-click`. To avoid double-toggling on a single click, the pure Base `PopoverTrigger` constructs its `bootstrap.Popover` instance with `trigger: "manual"` and calls `.toggle()` itself from `onClick` — `shown.bs.popover`/`hidden.bs.popover` still fire from `.toggle()` regardless of the `trigger` option, since that option only gates Bootstrap's own auto-binding, not event dispatch. The static adapter, which has no competing click handler of its own, passes `trigger: "click"` and relies on Bootstrap's built-in binding instead.
+Unlike `Tooltip`/hover-driven components, the built-in `trigger: "click"` option would bind its own click listener directly on the trigger element, independent of `PopoverTrigger`'s own `t-on-click`. To avoid double-toggling on a single click, the pure Base `PopoverTrigger` constructs its `bootstrap.Popover` instance with `trigger: "manual"` and calls `.toggle()` itself from `onClick` — `shown.bs.popover`/`hidden.bs.popover` still fire from `.toggle()` regardless of the `trigger` option, since that option only gates the built-in auto-binding, not event dispatch. The static adapter, which has no competing click handler of its own, passes `trigger: "click"` and relies on the built-in built-in binding instead.
 
 ## Static component
 
@@ -49,7 +49,7 @@ Unlike `Tooltip`/hover-driven components, Bootstrap's own `trigger: "click"` opt
 </span>
 ```
 
-The static adapter reads `[b-popover-content]` once at mount time as the popover's HTML content, then removes that node from the DOM — Bootstrap owns showing/hiding the content from then on, so no `[b-popover-content]` element survives in the authored markup post-mount. Events: `baseui:open`, `baseui:close` (dispatched from the root element on Bootstrap's own `shown.bs.popover`/`hidden.bs.popover`).
+The static adapter reads `[b-popover-content]` once at mount time as the popover's HTML content, then removes that node from the DOM — the library owns showing/hiding the content from then on, so no `[b-popover-content]` element survives in the authored markup post-mount. Events: `nodexui:open`, `nodexui:close` (dispatched from the root element on the built-in `shown.bs.popover`/`hidden.bs.popover`).
 
 ## Enhanced usage
 
@@ -57,7 +57,7 @@ Call `thebase.mount(element)` or rely on `thebase.mountAll()` after the script l
 
 ## Options and attributes
 
-See `dist/baseui.registry.json` for the supported attribute list.
+See `dist/nodexui.registry.json` for the supported attribute list.
 
 ## Methods
 
@@ -65,11 +65,11 @@ Use the global runtime methods: `thebase.mount()`, `thebase.mountAll()`, and `th
 
 ## Events
 
-Interactive components emit documented `baseui:*` events from their root element. Listen for Bootstrap's own `shown.bs.popover`/`hidden.bs.popover` on the trigger element to react to show/hide; the Base UI mirrors those into `b-att-state` (`open`/`closed`) and `aria-expanded` on the static trigger, and `this.env.popover.open`-equivalent reactive state on the Base components.
+Interactive components emit documented `nodexui:*` events from their root element. Listen for the built-in `shown.bs.popover`/`hidden.bs.popover` on the trigger element to react to show/hide; Nodex UI mirrors those into `b-att-state` (`open`/`closed`) and `aria-expanded` on the static trigger, and `this.env.popover.open`-equivalent reactive state on the Base components.
 
 ## CSS variables
 
-The component inherits the Base UI semantic tokens such as `--b-surface`, `--b-border`, `--b-primary`, and `--b-radius`. The popup itself is styled by Bootstrap's own bundled `.popover`/`.popover-arrow`/`.popover-body` CSS (loaded via `dist/baseui.min.css`), not the Base UI's own classes.
+The component inherits Nodex UI semantic tokens such as `--b-surface`, `--b-border`, `--b-primary`, and `--b-radius`. The popup itself is styled by the built-in bundled `.popover`/`.popover-arrow`/`.popover-body` CSS (loaded via `dist/nodexui.min.css`), not Nodex UI's own classes.
 
 ## Accessibility behavior
 
@@ -81,7 +81,7 @@ See `examples/index.html` for a working CDN-style page.
 
 ## Browser support
 
-The Base UI targets modern evergreen browsers that support ES modules, CSS variables, and Bootstrap 5.3.
+Nodex UI targets modern evergreen browsers that support ES modules, CSS variables.
 
 ## Test checklist
 

package/docs/components/progress.md

@@ -3,7 +3,7 @@
 ## Base component
 
 ```js
-import { Progress } from "@thebase/ui";
+import { Progress } from "nodexui";
 ```
 
 ```base-ui
@@ -18,7 +18,7 @@ import { Progress } from "@thebase/ui";
 | `Progress` | `max` | `Number` | optional |
 | `Progress` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 

package/docs/components/pwa.md

@@ -16,7 +16,7 @@ import {
   PwaSteps,
   PwaTitle,
   PwaTrigger,
-} from "@thebase/ui";
+} from "nodexui";
 ```
 
 ```base-ui
@@ -59,7 +59,7 @@ A launcher rendered outside the `Pwa` tree opens it through `PwaTrigger`, or by
 
 Render a second `Pwa` instance for a follow-up prompt (e.g. "Allow notifications" after install is dismissed) — each `Pwa` owns its own open state independently.
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 
@@ -77,7 +77,7 @@ See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how
 </div>
 ```
 
-The prompt closes on backdrop click, `[b-pwa-close]`, or Escape. `element.BaseUIPwa.open()`/`.close()` are also available once mounted, for a launcher button rendered elsewhere in the page (e.g. only once `beforeinstallprompt` has fired).
+The prompt closes on backdrop click, `[b-pwa-close]`, or Escape. `element.NodexUIPwa.open()`/`.close()` are also available once mounted, for a launcher button rendered elsewhere in the page (e.g. only once `beforeinstallprompt` has fired).
 
 ## Options and attributes
 
@@ -89,7 +89,7 @@ The prompt closes on backdrop click, `[b-pwa-close]`, or Escape. `element.BaseUI
 
 ## Events
 
-`baseui:open` and `baseui:close` fire on the root element (shared `createModal()` contract with `dialog`/`sheet`).
+`nodexui:open` and `nodexui:close` fire on the root element (shared `createModal()` contract with `dialog`/`sheet`).
 
 ## Accessibility behavior
 

package/docs/components/questionnaire.md

@@ -4,12 +4,12 @@ Use `b-ui="questionnaire"` for a CDN-ready questionnaire component.
 
 ## CDN install requirements
 
-Load the pinned the Base UI CSS and JavaScript files; no extra dependency is required for this component.
+Load the pinned Nodex UI CSS and JavaScript files; no extra dependency is required for this component.
 
 ## Base component
 
 ```js
-import { Questionnaire, QuestionnaireNext, QuestionnairePrevious, QuestionnaireStep } from "@thebase/ui";
+import { Questionnaire, QuestionnaireNext, QuestionnairePrevious, QuestionnaireStep } from "nodexui";
 ```
 
 ```base-ui
@@ -83,7 +83,7 @@ import { Questionnaire, QuestionnaireNext, QuestionnairePrevious, QuestionnaireS
 | `QuestionnaireStep` | `index` | `Number` | required |
 | `QuestionnaireStep` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 
@@ -97,7 +97,7 @@ Call `thebase.mount(element)` or rely on `thebase.mountAll()` after the script l
 
 ## Options and attributes
 
-See `dist/baseui.registry.json` for the supported attribute list.
+See `dist/nodexui.registry.json` for the supported attribute list.
 
 ## Methods
 
@@ -105,11 +105,11 @@ Use the global runtime methods: `thebase.mount()`, `thebase.mountAll()`, and `th
 
 ## Events
 
-Interactive components emit documented `baseui:*` events from their root element. Static components do not emit events.
+Interactive components emit documented `nodexui:*` events from their root element. Static components do not emit events.
 
 ## CSS variables
 
-The component inherits the Base UI semantic tokens such as `--b-surface`, `--b-border`, `--b-primary`, and `--b-radius`.
+The component inherits Nodex UI semantic tokens such as `--b-surface`, `--b-border`, `--b-primary`, and `--b-radius`.
 
 ## Accessibility behavior
 
@@ -121,7 +121,7 @@ See `examples/index.html` for a working CDN-style page.
 
 ## Browser support
 
-The Base UI targets modern evergreen browsers that support ES modules, CSS variables, and Bootstrap 5.3.
+Nodex UI targets modern evergreen browsers that support ES modules, CSS variables.
 
 ## Test checklist
 

package/docs/components/radio-group.md

@@ -5,7 +5,7 @@ Native radio input or label wrapper.
 ## Base component
 
 ```js
-import { RadioGroup, RadioGroupItem } from "@thebase/ui";
+import { RadioGroup, RadioGroupItem } from "nodexui";
 ```
 
 ```base-ui
@@ -28,7 +28,7 @@ import { RadioGroup, RadioGroupItem } from "@thebase/ui";
 | `RadioGroupItem` | `disabled` | `Boolean` | optional |
 | `RadioGroupItem` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 

package/docs/components/resizable.md

@@ -4,12 +4,12 @@ Use `b-ui="resizable"` for a CDN-ready resizable component.
 
 ## CDN install requirements
 
-Load the pinned the Base UI CSS and JavaScript files; no extra dependency is required for this component.
+Load the pinned Nodex UI CSS and JavaScript files; no extra dependency is required for this component.
 
 ## Base component
 
 ```js
-import { Resizable } from "@thebase/ui";
+import { Resizable } from "nodexui";
 ```
 
 ```base-ui
@@ -39,7 +39,7 @@ import { Resizable } from "@thebase/ui";
 | `Resizable` | `onChange` | `Function` | optional |
 | `Resizable` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 
@@ -53,7 +53,7 @@ Call `thebase.mount(element)` or rely on `thebase.mountAll()` after the script l
 
 ## Options and attributes
 
-See `dist/baseui.registry.json` for the supported attribute list.
+See `dist/nodexui.registry.json` for the supported attribute list.
 
 ## Methods
 
@@ -61,11 +61,11 @@ Use the global runtime methods: `thebase.mount()`, `thebase.mountAll()`, and `th
 
 ## Events
 
-Interactive components emit documented `baseui:*` events from their root element. Static components do not emit events.
+Interactive components emit documented `nodexui:*` events from their root element. Static components do not emit events.
 
 ## CSS variables
 
-The component inherits the Base UI semantic tokens such as `--b-surface`, `--b-border`, `--b-primary`, and `--b-radius`.
+The component inherits Nodex UI semantic tokens such as `--b-surface`, `--b-border`, `--b-primary`, and `--b-radius`.
 
 ## Accessibility behavior
 
@@ -77,7 +77,7 @@ See `examples/index.html` for a working CDN-style page.
 
 ## Browser support
 
-The Base UI targets modern evergreen browsers that support ES modules, CSS variables, and Bootstrap 5.3.
+Nodex UI targets modern evergreen browsers that support ES modules, CSS variables.
 
 ## Test checklist
 

package/docs/components/scroll-area.md

@@ -4,12 +4,12 @@ Use `b-ui="scroll-area"` for a CDN-ready scroll area component.
 
 ## CDN install requirements
 
-Load the pinned the Base UI CSS and JavaScript files; no extra dependency is required for this component.
+Load the pinned Nodex UI CSS and JavaScript files; no extra dependency is required for this component.
 
 ## Base component
 
 ```js
-import { ScrollArea } from "@thebase/ui";
+import { ScrollArea } from "nodexui";
 ```
 
 ```base-ui
@@ -43,7 +43,7 @@ import { ScrollArea } from "@thebase/ui";
 | --- | --- | --- | --- |
 | `ScrollArea` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 
@@ -57,7 +57,7 @@ Call `thebase.mount(element)` or rely on `thebase.mountAll()` after the script l
 
 ## Options and attributes
 
-See `dist/baseui.registry.json` for the supported attribute list.
+See `dist/nodexui.registry.json` for the supported attribute list.
 
 ## Methods
 
@@ -65,11 +65,11 @@ Use the global runtime methods: `thebase.mount()`, `thebase.mountAll()`, and `th
 
 ## Events
 
-Interactive components emit documented `baseui:*` events from their root element. Static components do not emit events.
+Interactive components emit documented `nodexui:*` events from their root element. Static components do not emit events.
 
 ## CSS variables
 
-The component inherits the Base UI semantic tokens such as `--b-surface`, `--b-border`, `--b-primary`, and `--b-radius`.
+The component inherits Nodex UI semantic tokens such as `--b-surface`, `--b-border`, `--b-primary`, and `--b-radius`.
 
 ## Accessibility behavior
 
@@ -81,7 +81,7 @@ See `examples/index.html` for a working CDN-style page.
 
 ## Browser support
 
-The Base UI targets modern evergreen browsers that support ES modules, CSS variables, and Bootstrap 5.3.
+Nodex UI targets modern evergreen browsers that support ES modules, CSS variables.
 
 ## Test checklist
 

package/docs/components/select.md

@@ -3,7 +3,7 @@
 ## Base component
 
 ```js
-import { Select, SelectContent, SelectItem, SelectTrigger } from "@thebase/ui";
+import { Select, SelectContent, SelectItem, SelectTrigger } from "nodexui";
 ```
 
 ```base-ui
@@ -46,7 +46,7 @@ Set `useTip="1"` to move `supportingText` into a tooltip: a question-mark icon a
 | `SelectItem` | `className` | `String` | optional |
 | `SelectTrigger` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 

package/docs/components/separator.md

@@ -5,7 +5,7 @@ Visual divider with separator semantics.
 ## Base component
 
 ```js
-import { Separator } from "@thebase/ui";
+import { Separator } from "nodexui";
 ```
 
 ```base-ui
@@ -30,7 +30,7 @@ import { Separator } from "@thebase/ui";
 | `Separator` | `orientation` | `String` | optional |
 | `Separator` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 

package/docs/components/sheet.md

@@ -5,7 +5,7 @@ Use `b-ui="sheet"` for offcanvas panels.
 ## Base component
 
 ```js
-import { Sheet, SheetClose, SheetContent, SheetDescription, SheetFooter, SheetHeader, SheetTitle, SheetTrigger } from "@thebase/ui";
+import { Sheet, SheetClose, SheetContent, SheetDescription, SheetFooter, SheetHeader, SheetTitle, SheetTrigger } from "nodexui";
 ```
 
 ```base-ui
@@ -38,7 +38,7 @@ import { Sheet, SheetClose, SheetContent, SheetDescription, SheetFooter, SheetHe
 | `SheetTitle` | `className` | `String` | optional |
 | `SheetTrigger` | `className` | `String` | optional |
 
-`SheetContent` also accepts `side` (`"left"` or the default right), falling back to the `side` prop on the parent `Sheet` when unset. It is driven by a real `bootstrap.Offcanvas` instance bound to its own root, rendered as `.offcanvas.offcanvas-end` by default or `.offcanvas.offcanvas-start` for `side="left"`, permanently mounted rather than added/removed from the DOM. Escape, backdrop click, and the Tab focus trap are Bootstrap's own native Offcanvas behavior; focus-restore-to-trigger on close is kept by hand (not native to Offcanvas). `SheetClose` closes via `data-bs-dismiss="offcanvas"`. See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+`SheetContent` also accepts `side` (`"left"` or the default right), falling back to the `side` prop on the parent `Sheet` when unset. It is driven by a real `bootstrap.Offcanvas` instance bound to its own root, rendered as `.offcanvas.offcanvas-end` by default or `.offcanvas.offcanvas-start` for `side="left"`, permanently mounted rather than added/removed from the DOM. Escape, backdrop click, and the Tab focus trap are the built-in native Offcanvas behavior; focus-restore-to-trigger on close is kept by hand (not native to Offcanvas). `SheetClose` closes via `data-bs-dismiss="offcanvas"`. See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 
@@ -53,6 +53,6 @@ import { Sheet, SheetClose, SheetContent, SheetDescription, SheetFooter, SheetHe
 
 At mount, `[b-ui="sheet"]` itself becomes the `.offcanvas.offcanvas-end` element (`.offcanvas.offcanvas-start` when `b-att-side="left"`, `tabindex="-1"`) driven by a real `bootstrap.Offcanvas` instance (`backdrop: true, keyboard: true, scroll: false`); `[b-sheet-panel]` stays as a plain cosmetic content box inside it. `[b-sheet-close]` buttons get `data-bs-dismiss="offcanvas"` at mount time instead of a manual click handler.
 
-Events: `baseui:open`, `baseui:close` (the Base UI), plus the underlying `shown.bs.offcanvas`/`hidden.bs.offcanvas`.
+Events: `nodexui:open`, `nodexui:close` (Nodex UI), plus the underlying `shown.bs.offcanvas`/`hidden.bs.offcanvas`.
 
 Options: `b-att-side="left"` moves the sheet panel to the left (`offcanvas-start` instead of `offcanvas-end`). The sheet closes on backdrop click, close button (`data-bs-dismiss="offcanvas"`), or Escape — all native `bootstrap.Offcanvas` behavior — and traps Tab focus while open, restoring focus to the trigger on close (kept by hand — not native to Offcanvas).

package/docs/components/shell.md

@@ -14,8 +14,8 @@ import {
   ShellSidebar,
   ShellSidebarHeader,
   ShellUserMenu,
-} from "@thebase/ui";
-import { SidebarClose, SidebarTrigger } from "@thebase/ui";
+} from "nodexui";
+import { SidebarClose, SidebarTrigger } from "nodexui";
 ```
 
 ```base-ui
@@ -51,7 +51,7 @@ Four cross-cutting concerns are opt-in via props instead of baked into the layou
 
 - `authState` — an arbitrary object (e.g. `{ username, onLogout }`), exposed to descendants via `env.shell.authState`. `ShellUserMenu` reads it directly and renders nothing when it's absent; pass its own default slot to fully customize the markup instead of the built-in username/logout row.
 - `toast`/`onToastOpenChange` — when `toast` is set (`{ variant, message, delay, persistent, actionLabel, onAction }`), `Shell` renders a built-in `Toast` bound to it, positioned as a fixed top-right overlay (`.b-shell-toast`) so it survives regardless of where `ShellContent` scrolls. Useful for a single app-wide notification channel (e.g. a message-bus toast) that should outlive route changes.
-- `notificationPage`/`pwa` — each an Owl component class, mounted once at the shell root (`<t t-component="..."/>`) alongside the sidebar, same shape as a consumer app's own `PWAInstallDrawer`. `Shell` doesn't know or care what they render — they're expected to manage their own trigger/visibility.
+- `notificationPage`/`pwa` — each a Nodex component class, mounted once at the shell root (`<t t-component="..."/>`) alongside the sidebar, same shape as a consumer app's own `PWAInstallDrawer`. `Shell` doesn't know or care what they render — they're expected to manage their own trigger/visibility.
 
 | Component | Prop | Type | Notes |
 | --- | --- | --- | --- |
@@ -64,8 +64,8 @@ Four cross-cutting concerns are opt-in via props instead of baked into the layou
 | `Shell` | `authState` | `Object` | optional, exposed to descendants via `env.shell.authState` |
 | `Shell` | `toast` | `Object` | optional, `{ variant, message, delay, persistent, actionLabel, onAction }` |
 | `Shell` | `onToastOpenChange` | `Function` | optional, called with `false` when the built-in toast is dismissed |
-| `Shell` | `notificationPage` | `Function` | optional, an Owl component class mounted at the shell root |
-| `Shell` | `pwa` | `Function` | optional, an Owl component class mounted at the shell root |
+| `Shell` | `notificationPage` | `Function` | optional, a Nodex component class mounted at the shell root |
+| `Shell` | `pwa` | `Function` | optional, a Nodex component class mounted at the shell root |
 | `Shell` | `className` | `String` | optional |
 | `ShellSidebar` | `className` | `String` | optional |
 | `ShellSidebarHeader` | `className` | `String` | optional |
@@ -76,7 +76,7 @@ Four cross-cutting concerns are opt-in via props instead of baked into the layou
 | `ShellContent` | `className` | `String` | optional |
 | `ShellUserMenu` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 
@@ -93,4 +93,4 @@ See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how
 </div>
 ```
 
-State is reflected through `b-att-collapsed="true|false"`. Events: `baseui:collapse`, `baseui:expand`.
+State is reflected through `b-att-collapsed="true|false"`. Events: `nodexui:collapse`, `nodexui:expand`.

package/docs/components/sidebar.md

@@ -5,7 +5,7 @@ Use `b-ui="sidebar"` for app navigation panels. The component mirrors shadcn's c
 ## Base component
 
 ```js
-import { Sidebar, SidebarContent, SidebarFooter, SidebarHeader, SidebarMenu, SidebarMenuButton, SidebarMenuItem } from "@thebase/ui";
+import { Sidebar, SidebarContent, SidebarFooter, SidebarHeader, SidebarMenu, SidebarMenuButton, SidebarMenuItem } from "nodexui";
 ```
 
 `Sidebar` owns the open/collapsed state itself (`defaultOpen`/`open`/`onOpenChange`) and lays out its `SidebarContent` panel next to `SidebarInset` as siblings — do **not** wrap it in a separate `SidebarProvider`, that duplicates the layout/state and breaks rendering. `SidebarHeader`, the nav `SidebarGroup`s, and `SidebarFooter` all nest *inside* `SidebarContent` (which renders the actual bordered/fixed-width panel), not beside it.
@@ -234,7 +234,7 @@ Reusable nav-content primitives, extracted from the recurring group/item shapes
 | `SidebarMenuSubButton` | `href` | `String` | optional |
 | `SidebarMenuSubItem` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 
@@ -305,6 +305,6 @@ See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how
 </div>
 ```
 
-State is reflected through `b-att-state="open|closed"`. Events: `baseui:open`, `baseui:close`.
+State is reflected through `b-att-state="open|closed"`. Events: `nodexui:open`, `nodexui:close`.
 
 Below 992px the sidebar is an off-canvas drawer closed by navigation; the `Shell` and `Sidebar` CSS and `matchMedia` checks share this breakpoint.

package/docs/components/skeleton.md

@@ -5,7 +5,7 @@ Loading placeholder for content that is not ready yet.
 ## Base component
 
 ```js
-import { Skeleton } from "@thebase/ui";
+import { Skeleton } from "nodexui";
 ```
 
 ```base-ui
@@ -29,7 +29,7 @@ import { Skeleton } from "@thebase/ui";
 | `Skeleton` | `shape` | `String` | optional |
 | `Skeleton` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 

package/docs/components/slider.md

@@ -3,7 +3,7 @@
 ## Base component
 
 ```js
-import { Slider } from "@thebase/ui";
+import { Slider } from "nodexui";
 ```
 
 ```base-ui
@@ -22,7 +22,7 @@ import { Slider } from "@thebase/ui";
 | `Slider` | `className` | `String` | optional |
 | `Slider` | `onChange` | `Function` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 

package/docs/components/spinner.md

@@ -1,11 +1,11 @@
 # Spinner
 
-Inline loading indicator using Bootstrap spinner classes.
+Inline loading indicator using built-in spinner classes.
 
 ## Base component
 
 ```js
-import { Spinner } from "@thebase/ui";
+import { Spinner } from "nodexui";
 ```
 
 ```base-ui
@@ -24,7 +24,7 @@ import { Spinner } from "@thebase/ui";
 | `Spinner` | `label` | `String` | optional |
 | `Spinner` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 
@@ -35,4 +35,4 @@ See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how
 
 Options: `b-att-type="border|grow"`, `b-att-label`.
 
-Accessibility: The Base UI adds `role="status"` and hidden loading text.
+Accessibility: Nodex UI adds `role="status"` and hidden loading text.

package/docs/components/switch.md

@@ -5,7 +5,7 @@ Checkbox-backed switch control using `role="switch"`.
 ## Base component
 
 ```js
-import { Switch } from "@thebase/ui";
+import { Switch } from "nodexui";
 ```
 
 ```base-ui
@@ -32,7 +32,7 @@ import { Switch } from "@thebase/ui";
 | `Switch` | `className` | `String` | optional |
 | `Switch` | `onChange` | `Function` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 

package/docs/components/table.md

@@ -5,7 +5,7 @@ Native table styling for static or server-rendered data.
 ## Base component
 
 ```js
-import { Table } from "@thebase/ui";
+import { Table } from "nodexui";
 ```
 
 ```base-ui
@@ -50,7 +50,7 @@ import { Table } from "@thebase/ui";
 | `Table` | `hover` | `Boolean` | optional |
 | `Table` | `className` | `String` | optional |
 
-See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how to load `@base/owl` and `dist/baseui.templates.xml`.
+See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how to load `nodexui` and `dist/nodexui.templates.xml`.
 
 ## Static component
 

package/docs/components/tabs.md

@@ -1,6 +1,6 @@
 # Tabs
 
-Matches [shadcn/base's Tabs](https://ui.shadcn.com/docs/components/base/tabs): `TabsList` renders
+Matches [shadcn/the built-in Tabs](https://ui.shadcn.com/docs/components/base/tabs): `TabsList` renders
 as a segmented pill control on a muted background by default, or a transparent underline list via
 `variant="'line'"`. `TabContent`/`b-panel` render as bare panels with no default border or
 background — a bordered/padded look is opt-in via `className` on `TabsContainer` (or the
@@ -9,7 +9,7 @@ consumer's own wrapper), not baked into every panel.
 ## Base component
 
 ```js
-import { Tabs, TabContent, TabsContainer, TabsList, TabTrigger } from "@thebase/ui";
+import { Tabs, TabContent, TabsContainer, TabsList, TabTrigger } from "nodexui";
 ```
 
 ```base-ui
@@ -57,10 +57,10 @@ The `"line"` variant swaps the segmented pill for a transparent, underline-drive
 
 ArrowLeft/ArrowRight (or ArrowUp/ArrowDown when vertical) move focus and selection between
 `TabTrigger`s, same as the static API — each trigger's own live `bootstrap.Tab` instance handles
-this natively. See [Base Components](/examples/blocks.html#/docs/guide/owl-components) for how
-to load `@base/owl` and `dist/baseui.templates.xml`.
+this natively. See [Nodex UI Component](/examples/blocks.html#/docs/guide/owl-components) for how
+to load `nodexui` and `dist/nodexui.templates.xml`.
 
-Each `TabTrigger` (`b-tab` button / pure Base `TabTrigger`'s own root) is driven by a live `bootstrap.Tab` instance: it always carries `role="tab"` plus a `data-bs-target="#<id>"` pointing at its linked pane, and Bootstrap itself manages the pane's `tab-pane fade`/`show`/`active` classes and the trigger's `active`/`aria-selected`/`tabindex` across switches — don't rely on node removal to detect the active panel; every `TabContent`/`b-panel` stays mounted permanently (`role="tabpanel"`, `tab-pane fade` + `show active` on the initially active one).
+Each `TabTrigger` (`b-tab` button / pure Base `TabTrigger`'s own root) is driven by a live `bootstrap.Tab` instance: it always carries `role="tab"` plus a `data-bs-target="#<id>"` pointing at its linked pane, and the library itself manages the pane's `tab-pane fade`/`show`/`active` classes and the trigger's `active`/`aria-selected`/`tabindex` across switches — don't rely on node removal to detect the active panel; every `TabContent`/`b-panel` stays mounted permanently (`role="tabpanel"`, `tab-pane fade` + `show active` on the initially active one).
 
 ## Static component
 
@@ -78,6 +78,6 @@ of the default segmented pill. `orientation` is a pure Base-only prop — the st
 `[b-tab]`/`[b-panel]` flat as siblings with no `TabsList`/`TabsContainer`-equivalent grouping
 wrapper to flip into a row/column pair.
 
-Events: `baseui:change` with `{ value }`.
+Events: `nodexui:change` with `{ value }`.
 
 Keyboard: Left and Right arrows move between tabs.

package/docs/components/text-editor.md

@@ -1,6 +1,6 @@
 # Text Editor
 
-Use `b-ui="text-editor"` (or the pure Base `TextEditor` component) for WYSIWYG rich-text editing backed by [Milkdown](https://milkdown.dev/) (ProseMirror + a Markdown-aware schema, via `@milkdown/kit`). The editor runtime is lazy-loaded from `dist/runtime/milkdown/milkdown-text-editor.js`, so the default the Base UI bundle stays small until an editor is actually mounted. `content`/`onChange` still deal in HTML — Milkdown's document is converted to/from HTML at the boundary, so nothing in this contract changes even though the engine now understands Markdown natively (e.g. typing a leading `#`, `**bold**`, or `1.` auto-formats as you type).
+Use `b-ui="text-editor"` (or the pure Base `TextEditor` component) for WYSIWYG rich-text editing backed by [Milkdown](https://milkdown.dev/) (ProseMirror + a Markdown-aware schema, via `@milkdown/kit`). The editor runtime is lazy-loaded from `dist/runtime/milkdown/milkdown-text-editor.js`, so the default Nodex UI bundle stays small until an editor is actually mounted. `content`/`onChange` still deal in HTML — Milkdown's document is converted to/from HTML at the boundary, so nothing in this contract changes even though the engine now understands Markdown natively (e.g. typing a leading `#`, `**bold**`, or `1.` auto-formats as you type).
 
 Collaborative mode (`collaborative` / `b-att-collaborative`) is optional and off by default; toggle it per editor without changing anything else. It runs on Yjs + `@milkdown/plugin-collab` over one of two providers, picked with `provider` / `b-att-provider`:
 
@@ -12,7 +12,7 @@ Collaboration actually turns on when `collaborative` is explicitly truthy, **or*
 ## Base Component
 
 ```js
-import { TextEditor } from "@base/component";
+import { TextEditor } from "nodexui";
 ```
 
 ```base-ui
@@ -89,13 +89,13 @@ Or the same session hosted on an external websocket backend instead of peer-to-p
 - `b-att-room` / `room` — document/room name for collaborative sessions (defaults to `b-text-editor`); shared across peers for y-webrtc, or used as the document name on the y-websocket backend.
 - `b-att-url` / `url` — y-websocket server URL (e.g. `wss://your-backend.example.com/mkdn`), required when `provider` is `"websocket"`. Ignored for `"webrtc"`.
 - `b-att-password` / `password` — optional y-webrtc room password. Ignored for `"websocket"`.
-- `b-att-signaling` / `signaling` — comma-separated signaling URLs for the static API, or an array prop for Owl. y-webrtc only.
+- `b-att-signaling` / `signaling` — comma-separated signaling URLs for the static API, or an array prop for Nodex. y-webrtc only.
 
 ## Events
 
-- `baseui:text-editor-ready` — fired after the Milkdown editor mounts (`detail.collaborative`, `detail.room`).
-- `baseui:text-editor-change` — fired whenever the rich-text document emits a new HTML string (`detail.html`, `detail.previousHtml`).
-- `baseui:text-editor-error` — fired when fetching or editor mounting fails (`detail.error`).
+- `nodexui:text-editor-ready` — fired after the Milkdown editor mounts (`detail.collaborative`, `detail.room`).
+- `nodexui:text-editor-change` — fired whenever the rich-text document emits a new HTML string (`detail.html`, `detail.previousHtml`).
+- `nodexui:text-editor-error` — fired when fetching or editor mounting fails (`detail.error`).
 
 ## Methods