@thebase/ui 1.2.1 → 1.3.0

package/docs/components/textarea.md

@@ -1,11 +1,11 @@
 # Textarea
 
-Native multiline text input with Base UI and Bootstrap styling.
+Native multiline text input with Nodex UI and built-in styling.
 
 ## Base component
 
 ```js
-import { Textarea } from "@thebase/ui";
+import { Textarea } from "nodexui";
 ```
 
 ```base-ui
@@ -64,7 +64,7 @@ Set `useTip="1"` to move `supportingText` into a tooltip: a question-mark icon a
 | `Textarea` | slots `start` / `end` / `footer` | slot | content drawn inside the box; `footer` sits along the bottom edge |
 | `Textarea` | `label`, `supportingText`, `useTip`, `errorText`, `maxLength`, `invalid`, `placeholder` | `String` / `Boolean` | Material-style outlined field, same behaviour as [Input](/examples/blocks.html#/docs/components/input): the label floats onto the border, `errorText` replaces `supportingText`. Also inherited from a parent `Field`. |
 
-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/theme-button.md

@@ -4,12 +4,12 @@ Use `b-ui="theme-button"` for an icon-only light/dark theme toggle.
 
 ## CDN install requirements
 
-Load the Base UI CSS and the Base UI JavaScript bundle (`baseui.min.js`). The component uses the built-in Lucide icon renderer and the `@base/theme` helper bundled with Base UI.
+Load Nodex UI CSS and Nodex UI JavaScript bundle (`nodexui.min.js`). The component uses the built-in Lucide icon renderer and the `nodexui` helper bundled with Nodex UI.
 
 ## Base component
 
 ```js
-import { ThemeButton } from "@thebase/ui";
+import { ThemeButton } from "nodexui";
 ```
 
 ```base-ui
@@ -24,7 +24,7 @@ import { ThemeButton } from "@thebase/ui";
 | `ThemeButton` | `className` | `String` | optional |
 | `ThemeButton` | `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
 
@@ -42,11 +42,11 @@ Use `b-att-variant="default|outline|ghost|destructive|secondary|link"` and `b-at
 
 ## Methods
 
-Use the global runtime methods: `thebase.mount()`, `thebase.mountAll()`, and `thebase.destroy()`. For direct theme control, import `createThemeController` from `@thebase/ui`.
+Use the global runtime methods: `thebase.mount()`, `thebase.mountAll()`, and `thebase.destroy()`. For direct theme control, import `createThemeController` from `nodexui`.
 
 ## Events
 
-Theme changes dispatch `baseui:theme-change` on `document` with `{ theme }` in `event.detail`.
+Theme changes dispatch `nodexui:theme-change` on `document` with `{ theme }` in `event.detail`.
 
 ## CSS variables
 
@@ -62,7 +62,7 @@ See the example page headers for working `b-ui="theme-button"` navigation usage.
 
 ## 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/toast.md

@@ -5,7 +5,7 @@ Use `b-ui="toast"` for transient status messages.
 ## Base component
 
 ```js
-import { Toast } from "@thebase/ui";
+import { Toast } from "nodexui";
 ```
 
 ```base-ui
@@ -35,7 +35,7 @@ The toast stays hidden until `open`/`state` becomes truthy (never shows on mount
 | `Toast` | `onOpenChange` | `Function` | optional |
 | `Toast` | `action` slot | — | optional — e.g. a `<Button/>`, rendered grouped next to the close button (`<t t-set-slot="action">...</t>`) |
 
-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
 
@@ -54,7 +54,7 @@ The toast stays hidden until shown — omit `b-att-state="open"` and call `.show
 
 ```base-ui
 <div class="d-flex flex-column align-items-center gap-3">
-  <button type="button" class="btn b-button btn-outline-secondary" onclick="document.getElementById('demo-toast').BaseUIToast.show()">Show Toast</button>
+  <button type="button" class="btn b-button btn-outline-secondary" onclick="document.getElementById('demo-toast').NodexUIToast.show()">Show Toast</button>
   <div id="demo-toast" b-ui="toast" b-att-delay="3000">
     <div class="b-toast-content">
       <div class="fw-medium">Event created</div>
@@ -68,13 +68,13 @@ The toast stays hidden until shown — omit `b-att-state="open"` and call `.show
 </div>
 ```
 
-Programmatic API: after mount, call `element.BaseUIToast.show()` or `element.BaseUIToast.hide()`. Events: `baseui:open`, `baseui:close`.
+Programmatic API: after mount, call `element.NodexUIToast.show()` or `element.NodexUIToast.hide()`. Events: `nodexui:open`, `nodexui:close`.
 
-Toasts are backed by `bootstrap.Toast`: the root receives Bootstrap's `toast fade` classes, and visibility is driven by Bootstrap's own `show`/`showing` classes (not `hidden`). The close button(s) carry `data-bs-dismiss="toast"` in addition to the `b-toast-close`/`b-toast-close` selector, so Bootstrap's own delegated dismiss handler drives them.
+Toasts are backed by `bootstrap.Toast`: the root receives the built-in `toast fade` classes, and visibility is driven by the built-in `show`/`showing` classes (not `hidden`). The close button(s) carry `data-bs-dismiss="toast"` in addition to the `b-toast-close`/`b-toast-close` selector, so the built-in delegated dismiss handler drives them.
 
 ### Screen-corner placement
 
-Set `b-att-position` to `top-left`, `top-right`, `bottom-left`, or `bottom-right` to fix the toast to that corner of the viewport. The toast element itself gets the Bootstrap `toast-container position-fixed p-3 pe-auto` classes plus the matching edge utility classes (`top-0`/`bottom-0` + `start-0`/`end-0`) merged in — no wrapper element. Omit the attribute to leave the toast inline in the document flow (the previous, default behavior):
+Set `b-att-position` to `top-left`, `top-right`, `bottom-left`, or `bottom-right` to fix the toast to that corner of the viewport. The toast element itself gets the built-in `toast-container position-fixed p-3 pe-auto` classes plus the matching edge utility classes (`top-0`/`bottom-0` + `start-0`/`end-0`) merged in — no wrapper element. Omit the attribute to leave the toast inline in the document flow (the previous, default behavior):
 
 ```base-ui
 <div id="corner-toast" b-ui="toast" b-att-position="bottom-right" b-att-delay="3000">

package/docs/components/toggle-group.md

@@ -4,12 +4,12 @@ Use `b-ui="toggle-group"` for a CDN-ready toggle group 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 { ToggleGroup, ToggleGroupItem } from "@thebase/ui";
+import { ToggleGroup, ToggleGroupItem } from "nodexui";
 ```
 
 ```base-ui
@@ -36,7 +36,7 @@ import { ToggleGroup, ToggleGroupItem } from "@thebase/ui";
 | `ToggleGroupItem` | `value` | `String` | required |
 | `ToggleGroupItem` | `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
 
@@ -50,7 +50,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
 
@@ -58,11 +58,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
 
@@ -74,7 +74,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/toggle.md

@@ -4,12 +4,12 @@ Use `b-ui="toggle"` for a CDN-ready toggle 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 { Toggle } from "@thebase/ui";
+import { Toggle } from "nodexui";
 ```
 
 ```base-ui
@@ -37,7 +37,7 @@ import { Toggle } from "@thebase/ui";
 | `Toggle` | `className` | `String` | optional |
 | `Toggle` | `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
 
@@ -51,7 +51,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
 
@@ -59,11 +59,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
 
@@ -75,7 +75,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/tooltip.md

@@ -5,7 +5,7 @@ Use `b-ui="tooltip"` with either `b-att-content` or a tooltip content child.
 ## Base component
 
 ```js
-import { Tooltip } from "@thebase/ui";
+import { Tooltip } from "nodexui";
 ```
 
 ```base-ui
@@ -24,11 +24,11 @@ import { Tooltip } from "@thebase/ui";
 | `Tooltip` | `state` | `String` | optional; `"open"`/`"on"`/`"active"` shows the tooltip once on mount (uncontrolled testing hook) |
 | `Tooltip` | `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.Tooltip` instance owned on the trigger element, with `trigger: "hover focus"` — **the visible popup is Bootstrap's own generated DOM (a `.tooltip`/`.tooltip-arrow`/`.tooltip-inner` node, positioned via Popper), appended to `document.body`, not rendered inline where you authored the tooltip.** Don't query for it as a descendant of the trigger; query `document.body.querySelector(".tooltip .tooltip-inner")` instead. Bootstrap sets `aria-describedby` on the trigger itself, but only while the tooltip is actually shown (removed again on hide) — the Base UI does not additionally set a static `aria-describedby` up front.
+Both the pure Base and static forms are driven by a live `bootstrap.Tooltip` instance owned on the trigger element, with `trigger: "hover focus"` — **the visible popup is the built-in generated DOM (a `.tooltip`/`.tooltip-arrow`/`.tooltip-inner` node, positioned via Popper), appended to `document.body`, not rendered inline where you authored the tooltip.** Don't query for it as a descendant of the trigger; query `document.body.querySelector(".tooltip .tooltip-inner")` instead. base sets `aria-describedby` on the trigger itself, but only while the tooltip is actually shown (removed again on hide) — Nodex UI does not additionally set a static `aria-describedby` up front.
 
-The default slot's rendered markup is captured into an HTML string for Bootstrap's `title`/`html: true` options (Bootstrap can't consume live vnodes): the Base component renders the slot into a hidden buffer element internal to its own template, reads its `innerHTML` on mount, and re-syncs the live popup via `.setContent({'.tooltip-inner': 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 `title`/`html: true` options (the library can't consume live vnodes): the Base component renders the slot into a hidden buffer element internal to its own template, reads its `innerHTML` on mount, and re-syncs the live popup via `.setContent({'.tooltip-inner': html})` whenever that HTML changes on a later render.
 
 ## Static component
 
@@ -38,7 +38,7 @@ The default slot's rendered markup is captured into an HTML string for Bootstrap
 </span>
 ```
 
-Tooltips show on hover and focus, then hide on mouse leave and blur — Bootstrap's own `trigger: "hover focus"` wires this, not manual event listeners. The static adapter reads `[b-tooltip-content]` (or the element built from `b-att-content`) once at mount time as the tooltip's HTML content, then removes that node from the DOM — Bootstrap owns showing/hiding the content from then on, so no `[b-tooltip-content]` element survives in the authored markup post-mount.
+Tooltips show on hover and focus, then hide on mouse leave and blur — the built-in `trigger: "hover focus"` wires this, not manual event listeners. The static adapter reads `[b-tooltip-content]` (or the element built from `b-att-content`) once at mount time as the tooltip's HTML content, then removes that node from the DOM — the library owns showing/hiding the content from then on, so no `[b-tooltip-content]` element survives in the authored markup post-mount.
 
 ## Enhanced usage
 
@@ -46,7 +46,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
 
@@ -54,11 +54,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.tooltip`/`hidden.bs.tooltip` on the trigger element to react to show/hide; the Base UI mirrors those into `b-att-state` (`open`/`closed`) on the static root and `this.state.open` on the Base component.
+Interactive components emit documented `nodexui:*` events from their root element. Listen for the built-in `shown.bs.tooltip`/`hidden.bs.tooltip` on the trigger element to react to show/hide; Nodex UI mirrors those into `b-att-state` (`open`/`closed`) on the static root and `this.state.open` on the Base component.
 
 ## 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 `.tooltip`/`.tooltip-arrow`/`.tooltip-inner` 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 `.tooltip`/`.tooltip-arrow`/`.tooltip-inner` CSS (loaded via `dist/nodexui.min.css`), not Nodex UI's own classes.
 
 ## Accessibility behavior
 
@@ -70,7 +70,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/typography.md

@@ -5,7 +5,7 @@ Small text helpers for plain content.
 ## Base component
 
 ```js
-import { Typography } from "@thebase/ui";
+import { Typography } from "nodexui";
 ```
 
 ```base-ui
@@ -86,23 +86,23 @@ import { Typography } from "@thebase/ui";
 | `Typography` | `tag` | `String` | optional; defaults to `h1`-`h4`, `blockquote`, `small`, `ul` for those variants, else `p` |
 | `Typography` | `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`.
 
-## Bootstrap typography classes
+## built-in typography classes
 
-Base UI redefines the Bootstrap 5 typography classes to the shadcn typeset values
-(`src/styles/base-extensions.css`), in Be Vietnam Pro. Use plain Bootstrap markup:
+Nodex UI redefines the built-in typography classes to the shadcn typeset values
+(`src/styles/base-extensions.css`), in Be Vietnam Pro. Use plain built-in markup:
 
 | Element / class | Result |
 | --- | --- |
 | `h1` / `.h1` ... `h4` / `.h4` | 1.75rem, 1.25rem, 1.125rem, 1rem; weight 600; line-height 1.3 to 1.5 |
 | `h5` / `.h5`, `h6` / `.h6` | 0.875rem / 0.8125rem, weight 500, muted; `h6` is uppercase with 0.08em tracking |
-| `.display-1` ... `.display-6` | Bootstrap sizes, weight 600, line-height 1.2 |
+| `.display-1` ... `.display-6` | built-in sizes, weight 600, line-height 1.2 |
 | `.lead`, `.small`, `mark`, `del`, `abbr[title]` | muted lead text, `--b-text-sm`, shadcn highlight, muted strike-through, dotted underline |
 | `blockquote` / `.blockquote` | 2px start border, 1em inline padding, inherited size |
 | `hr`, `dt`, `dd`, `code`, `pre`, `kbd`, `caption` | shadcn rule, weights, muted-background code, keycap border |
 
-Bootstrap's bottom-margin rhythm is unchanged. For the shadcn flow model (margin-top only,
+the built-in bottom-margin rhythm is unchanged. For the shadcn flow model (margin-top only,
 1.25em between blocks, 1.75 line-height, styled lists, links and tables) wrap prose in
 `class="b-typeset"`; tune with `--b-typeset-flow` and `--b-typeset-leading`.
 
@@ -110,9 +110,9 @@ Bootstrap's bottom-margin rhythm is unchanged. For the shadcn flow model (margin
 
 ```base-ui
 <p b-ui="typography" b-att-variant="lead">Readable intro text.</p>
-<span b-ui="typography" b-att-variant="code">baseui</span>
+<span b-ui="typography" b-att-variant="code">nodexui</span>
 ```
 
 Options: `b-att-variant="body|lead|muted|code|kbd|h1|h2|h3|h4|blockquote|small|list"` (static markup keeps its own element, so write `<h2 b-ui="typography" b-att-variant="h2">`; the variant only adds the class).
 
-Accessibility: choose semantic HTML elements first, then add the Base UI typography attributes for styling.
+Accessibility: choose semantic HTML elements first, then add Nodex UI typography attributes for styling.

package/docs/i18n.md

@@ -1,10 +1,10 @@
 # i18n service
 
-Instructions for adding translations to a page or app with the Base UI i18n service (`@thebase/ui/i18n`). It is optional and standalone: no Owl, Bootstrap or component runtime, and it is not part of the main bundles.
+Instructions for adding translations to a page or app with Nodex UI i18n service (`nodexui/i18n`). It is optional and standalone: no framework or component runtime, and it is not part of the main bundles.
 
 - **Audience:** developers adding a language switcher or translating an existing page.
 - **Runnable example:** `examples/i18n/` (open `/examples/i18n/` from `npm run dev`).
-- **Real-world use:** `emvhub/i18n.js` and the `i18n/*.po` folders beside each emvhub module.
+- **Real-world use:** `emvhub/i18n.js` and the `i18n/*.po` folders beside each emvhub module; the examples app does the same in `examples/i18n.js` and `examples/components/*/i18n/` (English and Vietnamese). Update catalogs with `node scripts/emvhub-i18n.mjs extract [--site=emvhub|examples/components] [newLang]`.
 
 ## 1. How it works
 
@@ -24,9 +24,9 @@ flowchart LR
 
 | How you load it | Use |
 | --- | --- |
-| ES module | `import { init, t, loadCatalog } from "@thebase/ui/i18n"` (file: `dist/baseui.i18n.esm.js`) |
-| Import map | map `@base/i18n` to the ESM file, then `import … from "@base/i18n"` |
-| Script tag | `dist/baseui.i18n.min.js` sets `window.thebase.i18n` |
+| ES module | `import { init, t, loadCatalog } from "nodexui/i18n"` (file: `dist/nodexui.i18n.esm.js`) |
+| Import map | map `nodexui/i18n` to the ESM file, then `import … from "nodexui/i18n"` |
+| Script tag | `dist/nodexui.i18n.min.js` sets `window.thebase.i18n` |
 
 ## 3. Quick start
 
@@ -34,14 +34,14 @@ flowchart LR
 
 ```html
 <script type="importmap">
-  { "imports": { "@base/i18n": "https://cdn.jsdelivr.net/npm/@thebase/ui@<version>/dist/baseui.i18n.esm.js" } }
+  { "imports": { "nodexui/i18n": "https://cdn.jsdelivr.net/npm/nodexui@<version>/dist/nodexui.i18n.esm.js" } }
 </script>
 ```
 
 2. Configure once, then load the catalog next to your module:
 
 ```js
-import { init, t, loadCatalog, languages, currentLanguage, setLanguage, translateHead } from "@base/i18n";
+import { init, t, loadCatalog, languages, currentLanguage, setLanguage, translateHead } from "nodexui/i18n";
 
 init({ languages: [{ code: "en", label: "English" }, { code: "vi", label: "Tiếng Việt" }], storageKey: "my-lang" });
 await loadCatalog(import.meta.url); // fetches ./i18n/vi.po when Vietnamese is picked
@@ -99,10 +99,10 @@ Each module loads its own catalog, but language selection and `init()` must happ
 
 ```js
 // i18n.js
-import { init } from "@base/i18n";
+import { init } from "nodexui/i18n";
 
 init({ languages: [{ code: "en", label: "English" }, { code: "vi", label: "Tiếng Việt" }], storageKey: "my-lang" });
-export * from "@base/i18n";
+export * from "nodexui/i18n";
 ```
 
 Because ES modules evaluate dependencies first, `init()` runs before any module's top-level `await loadCatalog(import.meta.url)`. A module that shares another folder's texts loads both: `await Promise.all([loadCatalog(import.meta.url), loadCatalog(new URL("../lib/", import.meta.url))])`.
@@ -116,4 +116,4 @@ Because ES modules evaluate dependencies first, `init()` runs before any module'
 | Module-level texts untranslated | `t()` ran before `await loadCatalog(...)` finished. Await it at the top of the module. |
 | Switching language reloads the page | By design: every text is redrawn in the new language. |
 | Choice not remembered | Storage is blocked; the `?lang=` link still works for that visit. |
-| Offline/PWA | Precache each `i18n/<code>.po` in your service worker (see `emvhub/baseui.pwa.config.js`). |
+| Offline/PWA | Precache each `i18n/<code>.po` in your service worker (see `emvhub/nodexui.pwa.config.js`). |

package/docs/icons.md

@@ -1,6 +1,6 @@
 # Built-in Icons
 
-The Base UI ships the full Lucide icon set as a built-in CDN-ready icon library. Icons use the `b-icon` attribute, render as CSS masks, and inherit `currentColor` from the surrounding button, link, menu item, block, or theme.
+Nodex UI ships the full Lucide icon set as a built-in CDN-ready icon library. Icons use the `b-icon` attribute, render as CSS masks, and inherit `currentColor` from the surrounding button, link, menu item, block, or theme.
 
 ```html
 <button b-ui="button" type="button">
@@ -15,20 +15,20 @@ The Base UI ships the full Lucide icon set as a built-in CDN-ready icon library.
 
 ## Install
 
-Load the normal the Base UI assets. No separate icon script is required.
+Load the normal Nodex UI assets. No separate icon script is required.
 
 ```html
-<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@thebase/ui@latest/dist/baseui.min.css">
-<script src="https://cdn.jsdelivr.net/npm/@thebase/ui@latest/dist/baseui.min.js" defer></script>
+<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/nodexui@latest/dist/nodexui.min.css">
+<script src="https://cdn.jsdelivr.net/npm/nodexui@latest/dist/nodexui.min.js" defer></script>
 ```
 
-`https://unpkg.com/@thebase/ui@latest/dist/...` mirrors the same files as an alternative CDN if jsDelivr is unreachable. Pin an exact version (e.g. `@1.2.1`, or `@1` to take only non-breaking updates) instead of `@latest` for production. `b-icon` also works with the [pure Base `Icon` component](components/icon.md) — the recommended API in an application; the classic script above is for pages using the static `b-ui` API.
+`https://unpkg.com/nodexui@latest/dist/...` mirrors the same files as an alternative CDN if jsDelivr is unreachable. Pin an exact version (e.g. `@1.3.0`, or `@1` to take only non-breaking updates) instead of `@latest` for production. `b-icon` also works with the [pure Base `Icon` component](components/icon.md) — the recommended API in an application; the classic script above is for pages using the static `b-ui` API.
 
 The build publishes every Lucide SVG to `dist/icons/lucide/` and writes the generated icon manifest to `dist/icons/lucide.json`.
 
 ## Markup
 
-Use the Lucide icon name in kebab-case, camelCase, snake_case, or space-separated form. The Base UI normalizes the name to the matching Lucide SVG file.
+Use the Lucide icon name in kebab-case, camelCase, snake_case, or space-separated form. Nodex UI normalizes the name to the matching Lucide SVG file.
 
 ```html
 <span b-icon="check"></span>
@@ -46,7 +46,7 @@ Use `b-icon-size` when the surrounding component should not control the icon siz
 
 ## Color
 
-Icons inherit `currentColor`, so set color on the parent element or let the Base UI component variants and themes do it.
+Icons inherit `currentColor`, so set color on the parent element or let Nodex UI component variants and themes do it.
 
 ```html
 <button b-ui="button" b-att-variant="destructive" type="button">
@@ -62,7 +62,7 @@ Icons inherit `currentColor`, so set color on the parent element or let the Base
 
 ## Accessibility
 
-Decorative icons should not have a label. The Base UI marks them with `aria-hidden="true"`.
+Decorative icons should not have a label. Nodex UI marks them with `aria-hidden="true"`.
 
 ```html
 <span b-icon="mail"></span>
@@ -84,7 +84,7 @@ Standalone meaningful icons can use `aria-label`.
 
 ## Self-hosting
 
-By default, icon URLs point to the pinned Lucide CDN configured in the registry. To serve icons from your own the Base UI build, point `b-icon-base-url` at the published icon folder.
+By default, icon URLs point to the pinned Lucide CDN configured in the registry. To serve icons from your own Nodex UI build, point `b-icon-base-url` at the published icon folder.
 
 ```html
 <span b-icon="search" b-icon-base-url="/dist/icons/lucide"></span>

package/docs/installation.md

@@ -2,60 +2,58 @@
 
 See the [Usage Guide](usage-guide.md) for the end-to-end integration path (choosing an API, install, theming, verification). This page covers install mechanics only.
 
-The Base UI is distributed as one CSS file and one JavaScript file for browser use. `dist/baseui.min.js` is fully self-contained: Bootstrap's JS bundle (Popper.js included) and the Owl runtime are embedded ahead of the Base UI's own code, in load order (Bootstrap, then Owl, then the Base UI) — nothing else needs to load first. Both install paths below load this same file; the Base component API is the recommended way to consume the Base UI in an application, with the base static markup (`b-ui`) API available as a lighter-weight alternative for non-Owl pages.
+Nodex UI is distributed as one CSS file and one JavaScript file for browser use. `dist/nodexui.min.js` is fully self-contained: the JS bundle (Popper.js included) and the Nodex runtime are embedded ahead of Nodex UI's own code, in load order (JS bundle, then runtime, then Nodex UI) — nothing else needs to load first. Both install paths below load this same file; the Base component API is the recommended way to consume Nodex UI in an application, with the base static markup (`b-ui`) API available as a lighter-weight alternative for non-component pages.
 
-The snippets below use the `@latest` tag for readability. Pin an exact version instead (e.g. `@1.2.1`, or `@1` to take only non-breaking updates) for any production page — `@latest` can silently change what your page loads the moment a new version is published.
+The snippets below use the `@latest` tag for readability. Pin an exact version instead (e.g. `@1.3.0`, or `@1` to take only non-breaking updates) for any production page — `@latest` can silently change what your page loads the moment a new version is published.
 
 ## Base component install (recommended)
 
-If you're building your own application and want to import the Base UI components as real Owl component classes (`<Button/>`, `<Card/>`, `<Tabs/>`, ...) instead of `b-ui` markup, it's the same one file as the static install, just accessed through an import map:
+If you're building your own application and want to import Nodex UI components as real Nodex component classes (`<Button/>`, `<Card/>`, `<Tabs/>`, ...) instead of `b-ui` markup, it's the same one file as the static install, just accessed through an import map:
 
 ```html
-<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@thebase/ui@latest/dist/baseui.min.css">
+<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/nodexui@latest/dist/nodexui.min.css">
 <script type="importmap">
 {
   "imports": {
-    "@base/owl": "https://cdn.jsdelivr.net/npm/@thebase/ui@latest/dist/baseui.esm.js",
-    "@base/component": "https://cdn.jsdelivr.net/npm/@thebase/ui@latest/dist/baseui.esm.js",
-    "@base/theme": "https://cdn.jsdelivr.net/npm/@thebase/ui@latest/dist/baseui.esm.js",
-    "@base/templates": "https://cdn.jsdelivr.net/npm/@thebase/ui@latest/dist/baseui.templates.xml"
+    "nodexui": "https://cdn.jsdelivr.net/npm/nodexui@latest/dist/nodexui.esm.js",
+    "nodexui/templates": "https://cdn.jsdelivr.net/npm/nodexui@latest/dist/nodexui.templates.xml"
   }
 }
 </script>
 ```
 
-`https://unpkg.com/@thebase/ui@latest/dist/...` mirrors the same files if jsDelivr is unreachable — swap the host in each URL above.
+`https://unpkg.com/nodexui@latest/dist/...` mirrors the same files if jsDelivr is unreachable — swap the host in each URL above.
 
-`@base/owl`, `@base/component`, and `@base/theme` all resolve to the exact same `dist/baseui.esm.js` module — the browser fetches and evaluates it once, so `Component`/`mount`/`xml` from `@base/owl` and `Button`/`Card`/... from `@base/component` are guaranteed to be the same runtime identity (no separate script needs to load first to set up a shared global). Your own app code should still import Owl from `@base/owl`, never install or import `@odoo/owl` directly — that's what keeps a `class Root extends Component` you write instanceof-compatible with Base UI's own components. `@base/templates` maps to the templates XML — not a JS module, so resolve it with `import.meta.resolve("@base/templates")` and `fetch()` the result rather than `import`ing it.
+`nodexui` resolves to the `dist/nodexui.esm.js` module — the browser fetches and evaluates it once, so `Component`/`mount`/`xml` from `nodexui` and `Button`/`Card`/... from `nodexui` are guaranteed to be the same runtime identity (no separate script needs to load first to set up a shared global). Your own app code should still import Nodex from `nodexui`, never install or import `@odoo/owl` directly — that's what keeps a `class Root extends Component` you write instanceof-compatible with Nodex UI's own components. `nodexui/templates` maps to the templates XML — not a JS module, so resolve it with `import.meta.resolve("nodexui/templates")` and `fetch()` the result rather than `import`ing it.
 
-For npm/bundler usage, everything (Owl framework, component classes, theme helper) is exported from the one `@thebase/ui` package entry: `import { Component, mount, xml, Button, Card, createThemeController } from "@thebase/ui";` — plus `@thebase/ui/dist/baseui.templates.xml` (component templates — fetch or load them before mounting). Note that importing the main entry always runs its `autoMount()` side effect (it scans the DOM for `[b-ui]`/`[b-icon]` markers on `DOMContentLoaded`) — harmless if your page has none, but worth knowing if you specifically wanted a side-effect-free import.
+For npm/bundler usage, everything (Nodex runtime, component classes, theme helper) is exported from the one `nodexui` package entry: `import { Component, mount, xml, Button, Card, createThemeController } from "nodexui";` — plus `nodexui/dist/nodexui.templates.xml` (component templates — fetch or load them before mounting). Note that importing the main entry always runs its `autoMount()` side effect (it scans the DOM for `[b-ui]`/`[b-icon]` markers on `DOMContentLoaded`) — harmless if your page has none, but worth knowing if you specifically wanted a side-effect-free import.
 
-See [Base Components](owl-components.md) for the full loading contract, a worked example, and common mistakes.
+See [Nodex UI Component](owl-components.md) for the full loading contract, a worked example, and common mistakes.
 
 ## Static `b-ui` install (alternative)
 
-For static HTML, a server-rendered page, or a Base HUB website page that has no Owl runtime of its own, load the same bundle as plain CSS + a classic `<script>` tag instead of an import map:
+For static HTML, a server-rendered page, or a Base HUB website page that has no Nodex runtime of its own, load the same bundle as plain CSS + a classic `<script>` tag instead of an import map:
 
 ```html
-<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@thebase/ui@latest/dist/baseui.min.css">
-<script src="https://cdn.jsdelivr.net/npm/@thebase/ui@latest/dist/baseui.min.js" defer></script>
+<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/nodexui@latest/dist/nodexui.min.css">
+<script src="https://cdn.jsdelivr.net/npm/nodexui@latest/dist/nodexui.min.js" defer></script>
 ```
 
-Bootstrap 5 is the bundled baseline CSS framework, and its JS bundle now drives the Base UI's interactive components directly.
+base is the bundled baseline CSS framework, and its JS bundle now drives Nodex UI's interactive components directly.
 
-`@thebase/ui` is published on npm, so [unpkg](https://unpkg.com/@thebase/ui@latest/) mirrors the same files as an alternative CDN (`https://unpkg.com/@thebase/ui@latest/dist/baseui.min.css` / `baseui.min.js`) if jsDelivr is unreachable in your environment. Pin an exact version (e.g. `@1.2.1`, or `@1` to take only non-breaking updates) instead of `@latest` for production.
+`nodexui` is published on npm, so [unpkg](https://unpkg.com/nodexui@latest/) mirrors the same files as an alternative CDN (`https://unpkg.com/nodexui@latest/dist/nodexui.min.css` / `nodexui.min.js`) if jsDelivr is unreachable in your environment. Pin an exact version (e.g. `@1.3.0`, or `@1` to take only non-breaking updates) instead of `@latest` for production.
 
 For npm/self-hosted usage:
 
 ```sh
-npm install @thebase/ui
+npm install nodexui
 ```
 
-Then copy or serve `node_modules/@thebase/ui/dist/baseui.min.css` and `node_modules/@thebase/ui/dist/baseui.min.js`.
+Then copy or serve `node_modules/nodexui/dist/nodexui.min.css` and `node_modules/nodexui/dist/nodexui.min.js`.
 
-`dist/bootstrap.bundle.min.js` also ships standalone, unmodified, with its own integrity hash in `dist/baseui.registry.json`, in case a project wants vendored Bootstrap JS on its own — the Base UI itself never needs it loaded separately.
+`dist/bootstrap.bundle.min.js` also ships standalone, unmodified, with its own integrity hash in `dist/nodexui.registry.json`, in case a project wants vendored built-in JS on its own — Nodex UI itself never needs it loaded separately.
 
-The static bundle auto-mounts existing `[b-ui]` and `[b-icon]` markers on `DOMContentLoaded`. Use `thebase.mountAll(root)` after later DOM injection, and `thebase.destroy(root)` before removing a mounted subtree that owns listeners or an Owl-backed controller.
+The static bundle auto-mounts existing `[b-ui]` and `[b-icon]` markers on `DOMContentLoaded`. Use `thebase.mountAll(root)` after later DOM injection, and `thebase.destroy(root)` before removing a mounted subtree that owns listeners or an runtime-backed controller.
 
 The package also ships the complete Lucide SVG icon set under `dist/icons/lucide/` and a generated `dist/icons/lucide.json` manifest. The built-in icon component can use the pinned jsDelivr Lucide CDN by default or your own self-hosted path:
 
@@ -70,20 +68,20 @@ Production pages should use pinned version URLs. `latest` is for demos and exper
 
 | Need | npm/bundler export | Browser import-map key | Dist file |
 | --- | --- | --- | --- |
-| Static `b-ui` runtime, Owl framework, every Base component class, theme helper | `@thebase/ui` | `@base/owl`, `@base/component`, `@base/theme` (all three point at the same file) | `dist/baseui.esm.js`, `dist/baseui.min.js` |
-| Styles | `@thebase/ui/baseui.css` | none; load with `<link>` | `dist/baseui.min.css` |
-| Bootstrap JS | embedded; standalone file is a vendoring convenience only, not part of the Base UI's own load path | none | `dist/bootstrap.bundle.min.js` |
-| Named-icon components (`IconEye`, ...) | `@thebase/ui/icons` | `@base/icons` | `dist/baseui.icons.esm.js` |
-| Owl templates XML | `@thebase/ui/dist/baseui.templates.xml` | `@base/templates` | `dist/baseui.templates.xml` |
-| Registry metadata | `@thebase/ui/registry` | none; fetch the JSON file | `dist/baseui.registry.json` |
-| Optional analytics service (`init`, `track`) | `@thebase/ui/analytics` | none; import the file URL or load the `<script>` build (sets `window.thebase.analytics`) | `dist/baseui.analytics.esm.js`, `dist/baseui.analytics.min.js` |
-| Optional i18n service (`init`, `t`, `loadCatalog`) | `@thebase/ui/i18n` | `@base/i18n` (as in `emvhub/index.html`); or load the `<script>` build (sets `window.thebase.i18n`) | `dist/baseui.i18n.esm.js`, `dist/baseui.i18n.min.js` |
-| Standalone ApiDoc (`mountApiDoc`) | `@thebase/ui/apidoc` | none; embeds Owl + its templates, still needs `baseui.min.css`; set `assetBase` for the language logos | `dist/baseui.apidoc.esm.js`, `dist/baseui.apidoc.min.js` |
-
-`@base/templates` points to XML, not JavaScript. Resolve and fetch it (`fetch(import.meta.resolve("@base/templates"))`) before mounting an application that uses the Base UI component classes.
+| Static `b-ui` runtime, Nodex runtime, every Base component class, theme helper | `nodexui` | `nodexui` (one key pointing at the same file) | `dist/nodexui.esm.js`, `dist/nodexui.min.js` |
+| Styles | `nodexui/nodexui.css` | none; load with `<link>` | `dist/nodexui.min.css` |
+| built-in JS | embedded; standalone file is a vendoring convenience only, not part of Nodex UI's own load path | none | `dist/bootstrap.bundle.min.js` |
+| Named-icon components (`IconEye`, ...) | `nodexui/icons` | `nodexui/icons` | `dist/nodexui.icons.esm.js` |
+| Nodex templates XML | `nodexui/dist/nodexui.templates.xml` | `nodexui/templates` | `dist/nodexui.templates.xml` |
+| Registry metadata | `nodexui/registry` | none; fetch the JSON file | `dist/nodexui.registry.json` |
+| Optional analytics service (`init`, `track`) | `nodexui/analytics` | none; import the file URL or load the `<script>` build (sets `window.thebase.analytics`) | `dist/nodexui.analytics.esm.js`, `dist/nodexui.analytics.min.js` |
+| Optional i18n service (`init`, `t`, `loadCatalog`) | `nodexui/i18n` | `nodexui/i18n` (as in `emvhub/index.html`); or load the `<script>` build (sets `window.thebase.i18n`) | `dist/nodexui.i18n.esm.js`, `dist/nodexui.i18n.min.js` |
+| Standalone ApiDoc (`mountApiDoc`) | `nodexui/apidoc` | none; embeds Nodex + its templates, still needs `nodexui.min.css`; set `assetBase` for the language logos | `dist/nodexui.apidoc.esm.js`, `dist/nodexui.apidoc.min.js` |
+
+`nodexui/templates` points to XML, not JavaScript. Resolve and fetch it (`fetch(import.meta.resolve("nodexui/templates"))`) before mounting an application that uses Nodex UI component classes.
 
 ## Release Guardrails
 
-The Base UI intentionally keeps Bootstrap bundled for the browser build, both CSS and JS. Bootstrap's JS bundle and the Owl runtime are embedded directly into `dist/baseui.min.js`/`baseui.esm.js` — in that load order — along with every Base component class and the theme helper, so both the static API and the pure Base API install with one stylesheet and one script/import: there is no more separate `baseui.owl.*`/`baseui.components.esm.js`/`baseui.theme.esm.js` file to keep in load order. Bootstrap's JS instances (`bootstrap.Modal`, `Dropdown`, `Collapse`, `Tab`, `Toast`, `Carousel`, `Tooltip`, `Popover`, `Alert`) drive the components that map to them, wrapped by the Base UI's own `.behavior.js`/`runtime/*.js` helpers so both the static and pure Base APIs share identical ARIA/keyboard/event behavior.
+Nodex UI intentionally keeps its built-in styles and scripts bundled for the browser build, both CSS and JS. The JS bundle and the Nodex runtime are embedded directly into `dist/nodexui.min.js`/`nodexui.esm.js` — in that load order — along with every Base component class and the theme helper, so both the static API and the pure Base API install with one stylesheet and one script/import: there is no more separate `nodexui.owl.*`/`nodexui.components.esm.js`/`nodexui.theme.esm.js` file to keep in load order. the bundled JS instances (`bootstrap.Modal`, `Dropdown`, `Collapse`, `Tab`, `Toast`, `Carousel`, `Tooltip`, `Popover`, `Alert`) drive the components that map to them, wrapped by Nodex UI's own `.behavior.js`/`runtime/*.js` helpers so both the static and pure Base APIs share identical ARIA/keyboard/event behavior.
 
 Release checks enforce runtime dependency, peer dependency, scoped CSS selector, and CDN file-size budgets through `npm run lint` and `npm run build`.