@thebase/ui 1.2.1 → 1.3.0

package/README.md

@@ -1,28 +1,54 @@
-# The Base UI
+# Nodex UI
 
-The Base UI is a CDN-installable UI kit built with Bootstrap 5 styling and Owl framework enhanced behavior. The primary way to consume it is as **Base components** (`<Button/>`-style imports into your own application); the base static markup (`b-ui`) adapter is the alternative for plain static HTML, server-rendered pages, and Base HUB website pages that have no application of their own.
+**Nodex UI** is an HTML-first, framework-independent UI component library for the web. It ships its own styling and behavior, loads straight from a CDN or npm, and needs no build step. Use it as **Nodex components** (`<Button/>`-style imports in your own application) or as the static `b-ui` markup adapter for plain HTML, server-rendered pages and CMS pages.
 
-Its strong points: **no build step** — every component runs straight from a CDN `<script>`/import map, nothing to compile; **modular component design** — each component is a self-contained unit you import or mark up individually, not a monolith; **vanilla JavaScript/TypeScript** — no framework lock-in, no JSX, no compiler-specific syntax to learn; and this combination makes it well suited to building **WYSIWYG website builders**, where components must mount, unmount, and re-render dynamically from user-driven markup or drag-and-drop edits rather than a fixed build-time component tree.
+- npm package: [`nodexui`](https://www.npmjs.com/package/nodexui) · current version **1.3.0**
+- Website, live demos and docs: <https://ui.thebase.vn>
+- Release history: [CHANGELOG.md](CHANGELOG.md)
 
-Both APIs load straight from a CDN — jsDelivr or unpkg — no build step, no self-hosting required. 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, since `@latest` can change what your page loads the moment a new version ships. Pure Base usage:
+## Why Nodex UI
+
+- **No build step.** Every component runs from a CDN `<script>` or import map; nothing to compile.
+- **No framework lock-in.** Vanilla JavaScript/TypeScript, no JSX, no React or Vue required.
+- **Modular.** Each component is a self-contained unit you import or mark up on its own (74 in the current registry).
+- **Dynamic-friendly.** Components mount, unmount and re-render from user-driven markup, which suits WYSIWYG website builders and drag-and-drop editors.
+- **Batteries included.** Lucide icons, light/dark theming, PWA tooling, ApiDoc, i18n and cookieless analytics (the last three are optional standalone bundles).
+
+## Install
+
+### npm
+
+```sh
+npm install nodexui
+```
+
+```js
+import { Component, mount, xml } from "nodexui";
+import { Button, Card, CardBody, CardHeader, CardTitle } from "nodexui";
+import "nodexui/nodexui.css";
+```
+
+Subpath exports: `nodexui/analytics`, `nodexui/i18n`, `nodexui/apidoc`, `nodexui/icons`, `nodexui/pwa`, `nodexui/vite`, `nodexui/registry`.
+
+### CDN (Nodex components)
+
+Both APIs load from jsDelivr or unpkg. The snippets use `@latest` for readability; pin an exact version (`@1.3.0`, or `@1` for non-breaking updates) on any production page.
 
 ```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>
 <script type="module">
-  import { Component, mount, xml } from "@base/owl";
-  import { Button, Card, CardBody, CardHeader, CardTitle } from "@base/component";
+  import { Component, mount, xml } from "nodexui";
+  import { Button, Card, CardBody, CardHeader, CardTitle } from "nodexui";
 
-  const templates = await fetch(import.meta.resolve("@base/templates")).then((r) => r.text());
+  const templates = await fetch(import.meta.resolve("nodexui/templates")).then((r) => r.text());
 
   class Root extends Component {
     static components = { Button, Card, CardBody, CardHeader, CardTitle };
@@ -39,124 +65,89 @@ Both APIs load straight from a CDN — jsDelivr or unpkg — no build step, no s
 </script>
 ```
 
-[unpkg](https://unpkg.com/@thebase/ui@latest/) mirrors the same files as an alternative CDN — swap any `cdn.jsdelivr.net/npm` URL above for `unpkg.com` (e.g. `https://unpkg.com/@thebase/ui@latest/dist/baseui.esm.js`) if jsDelivr is unreachable in your environment. See [Base Components](docs/owl-components.md) for the full API, npm/bundler usage, and mixing with the static adapter.
+Swap `cdn.jsdelivr.net/npm` for `unpkg.com` if jsDelivr is unreachable. See [Nodex Components](docs/owl-components.md) for the full API and bundler usage.
+
+### CDN (static `b-ui` markup)
 
-If you have no application, use the base static markup (`b-ui`) adapter instead — one stylesheet and one script tag, no import map:
+With no application of your own, use one stylesheet and one script tag, no 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>
 ```
 
-`dist/baseui.min.js`/`baseui.esm.js` are fully self-contained and back both APIs above: Bootstrap's JS bundle, the Owl runtime, every Base component class, and the theme helper are all embedded in load order (Bootstrap, then Owl, then the Base UI) — one file, nothing else to load first. There is no separate `baseui.owl.*`/`baseui.components.esm.js`/`baseui.theme.esm.js`. (`dist/bootstrap.bundle.min.js` still ships standalone, unmodified, for a project that wants vendored Bootstrap JS on its own — the Base UI itself never needs it loaded separately.)
+`dist/nodexui.min.js` and `dist/nodexui.esm.js` are self-contained and back both APIs: the JS bundle, the Nodex runtime, every component class and the theme helper are embedded in load order. There is no separate runtime, components or theme file.
 
-The Base UI exposes every component (74 in the current registry) as a real Owl component class — see [Base Components](docs/owl-components.md) for the complete API, npm/bundler usage, and mixing with the static adapter.
+Every component ships both APIs from `src/components/<name>/`: the static adapter (`<name>.js`, using `b-att-*` attributes and `nodexui:*` events) and a component class (`<name>.component.js`). A few components are intentionally reshaped in the component API, notably `chart` and the data-driven `data-table`, `combobox`, `command` and `calendar`. Each page under `docs/components/` explains the specifics.
 
-For app-level theme controls, import `createThemeController`/`BaseUITheme` as `@base/theme` in browser import maps (pointing at the same `dist/baseui.esm.js`) or straight from `@thebase/ui` in npm/bundler apps, to create persisted light/dark toggles like the documentation pages use.
+## Theming
 
-Every component ships both APIs from `src/components/<name>/`: the static `b-ui` adapter (`<name>.js`, using `b-att-*` attributes and `baseui:*` events) and a Base component class (`<name>.component.js`, exported from `@thebase/ui/components`). A few components' pure Base treatment is intentionally lighter or reshaped versus their static markup-driven adapter — most notably `chart` (a slotted container; static Chart.js bootstrapping stays a `b-ui`-only concern) and the data-driven `data-table`/`combobox`/`command`/`calendar` (props-driven instead of slot/markup-driven). See each component's doc page under `docs/components/` for specifics.
+Colour tokens, `--base-radius` and `--b-overlay` live in the downloadable `nodexui-light.css` and `nodexui-dark.css` themes. The **Theme** tab of the examples app (`examples/index.html#/theme`) builds a custom pair for you. For app-level light/dark toggles, import `createThemeController` / `NodexUITheme` as `nodexui` (import map) or from `nodexui` (bundler). See [Theming](docs/theming.md).
 
-## Analytics
+## Optional services
 
-The Base UI also ships an optional, cookieless web-analytics service (from 1.1.0). It is a standalone bundle — not part of `dist/baseui.min.js`/`baseui.esm.js`, with no Owl, Bootstrap, or component runtime dependency (~5.6 KB minified) — so you can load it with or without the rest of the Base UI. Nothing is collected until the page calls `init()`:
+| Service | Import | What it is |
+| --- | --- | --- |
+| **Analytics** | `nodexui/analytics`, `dist/nodexui.analytics.min.js` | Cookieless, standalone (about 5.6 KB min). Nothing is collected until `init()` is called. Covers pageviews (including SPA), engagement, outbound links, downloads and forms. See [Analytics](docs/analytics.md) and [`examples/analytics/`](examples/analytics/). |
+| **i18n** | `nodexui/i18n`, `dist/nodexui.i18n.min.js` | Gettext-style `.po` catalogs, no runtime dependencies. See [i18n](docs/i18n.md) and [`examples/i18n/`](examples/i18n/). |
+| **ApiDoc** | `nodexui/apidoc` | Renders an OpenAPI 3 JSON file as browsable docs with a Try It panel and 17 code-sample languages. See [ApiDoc](docs/components/apidoc.md) and [`examples/apidoc/`](examples/apidoc/). |
+| **PWA toolkit** | `nodexui/pwa`, `nodexui/vite` | `buildManifest`, `buildServiceWorker` and the `nodexuiPwa()` Vite plugin. |
 
 ```html
 <script type="module">
-  import { init, track } from "https://cdn.jsdelivr.net/npm/@thebase/ui@latest/dist/baseui.analytics.esm.js";
+  import { init, track } from "https://cdn.jsdelivr.net/npm/nodexui@1.3.0/dist/nodexui.analytics.esm.js";
   init({ backendUrl: "https://stats.example.com" }); // events POST to <backendUrl>/api/event
   track("Signup", { props: { plan: "pro" } });
 </script>
 ```
 
-From npm, use `import { init, track } from "@thebase/ui/analytics"`; for a classic `<script>` tag, `dist/baseui.analytics.min.js` sets `window.thebase.analytics`. It covers automatic and SPA pageviews, engagement (time on page and scroll depth), outbound links, file downloads, form submissions, and `thebase-event-*` class tagging. See [Analytics](docs/analytics.md) for every option, the payload format, opt-out, and sample Go Fiber / FastAPI backends. [`examples/analytics/`](examples/analytics/) holds a ready-to-run the Base UI dashboard for the collected data.
-
-## PWA toolkit and CLI
-
-The Base UI can scaffold and ship installable apps (from 1.1.2). The `create-baseui-app` CLI creates a static-importmap or Vite project (`create`, `init`, `convert`) and generates `manifest.webmanifest`, `sw.js` and a default icon set (`pwa`, icons from 1.1.3); the same generators are exported from `@thebase/ui/pwa` as `buildManifest` / `buildServiceWorker`.
-
-```sh
-npx create-baseui-app create my-app
-npx create-baseui-app pwa . --config baseui.pwa.config.js
-```
-
-See [Usage Guide §5b](docs/usage-guide.md) and the [PWA component](docs/components/pwa.md). The examples site itself is an installable PWA (`examples/pwa/`).
-
-## Outlined fields
-
-New in 1.1.5 (1.1.6 adds `useTip` to show helper text in an info-icon tooltip): `Input`, `Textarea`, `NativeSelect`, `Combobox`, `DatePicker` and `Select` share one Material-style outlined look (`label`, `supportingText`, `errorText`, `invalid`), and `Field` passes its `label`/`description`/`error` to the control inside. See [Field](docs/components/field.md) and [Input](docs/components/input.md).
-
-## ApiDoc
-
-New in 1.1.3: `ApiDoc` (`b-ui="apidoc"`) renders an OpenAPI 3 JSON file as browsable API docs — grouped sidebar, parameters, request bodies, responses, a Try It panel with code samples in 17 languages, and an Authorize dialog. See [ApiDoc](docs/components/apidoc.md), the `apidoc-01` block, and the live demo in [`examples/apidoc/`](examples/apidoc/).
-
-## Internationalization
-
-New in 1.2.1: an optional, standalone i18n service (gettext-style `.po` catalogs, no Owl or Bootstrap). It is not part of the main bundles.
-
 ```js
-import { init, t, loadCatalog } from "https://cdn.jsdelivr.net/npm/@thebase/ui@1.2.1/dist/baseui.i18n.esm.js";
+import { init, t, loadCatalog } from "https://cdn.jsdelivr.net/npm/nodexui@1.3.0/dist/nodexui.i18n.esm.js";
 init({ languages: [{ code: "en", label: "English" }, { code: "vi", label: "Tiếng Việt" }] });
 await loadCatalog(import.meta.url); // fetches ./i18n/vi.po when Vietnamese is picked
 console.log(t("Hello {name}", { name: "An" }));
 ```
 
-From npm use `@thebase/ui/i18n`; for a `<script>` tag, `dist/baseui.i18n.min.js` sets `window.thebase.i18n`. See [i18n](docs/i18n.md) and the runnable example in [`examples/i18n/`](examples/i18n/).
+### Project CLI
 
-## Theming
+`create-nodexui-app` scaffolds a static-importmap or Vite PWA project (`create`, `init`, `convert`) and generates the manifest, service worker and icons (`pwa`):
+
+```sh
+npx create-nodexui-app create my-app
+npx create-nodexui-app pwa . --config nodexui.pwa.config.js
+```
 
-New in 1.2.0: colour tokens, `--base-radius` and `--b-overlay` live only in the downloadable `baseui-light.css` / `baseui-dark.css` themes (new `--b-success|warning|info` status tokens), and the **Theme** tab of the examples app (`examples/index.html#/theme`) builds a custom pair for you. **Breaking in 1.2.0:** the `bu-` class and `--bu-*` variable prefix is now `b-` (`bu-button` -> `b-button`); see the CHANGELOG migration note. See [Theming](docs/theming.md).
+See [Usage Guide §5b](docs/usage-guide.md) and the [PWA component](docs/components/pwa.md).
 
-## Release notes
+## Search and discoverability
 
-See [CHANGELOG.md](CHANGELOG.md) for the full version history. Current version: **1.2.1**.
+The public site <https://ui.thebase.vn> keeps its hostname and URLs under the Nodex UI brand. The examples app sets per-route title, description, canonical and Open Graph tags (`examples/seo.js`), ships `sitemap.xml`, and reports first-party events through `examples/tracking.js`. Search Console is used for search visibility; Google Analytics is not. The plan, constraints and KPIs are in [the SEO, developer marketing and analytics brief](.agents/knowledge/base-ui-seo-analytics-ai-agent-brief.md).
 
 ## Versioning policy
 
-From 1.0.0 on, the Base UI follows [Semantic Versioning](https://semver.org/). The public API covered by this promise is:
+Nodex UI follows [Semantic Versioning](https://semver.org/) from **1.3.0**. The public API covered by this promise is:
 
-- Base component classes, their names, props, slots, and callback props exported from `@thebase/ui`.
-- Static markup: `b-ui`/`b-icon` names, `b-att-*` attributes, and `baseui:*` events.
+- Component classes, their names, props, slots and callback props exported from `nodexui`.
+- Static markup: `b-ui` / `b-icon` names, `b-att-*` attributes and `nodexui:*` events.
 - CSS: `b-*` class names and `--b-*` design tokens.
-- Runtime exports (`BaseUI`, `Component`, `mount`, `xml`, `cn`, `mergeStyle`, theme helpers), including `Component`'s fallback to globally registered the Base UI components, and the published `dist/` file names and package `exports` paths.
-
-What each release type means:
-
-- **Major** (`2.0.0`): removes or renames any of the above, or changes its behavior or default look in a way existing pages must adapt to. Every breaking change is listed under a **Breaking** heading in the CHANGELOG with a migration note.
-- **Minor** (`1.1.0`): new components, props, variants, tokens, or icons — existing code keeps working unchanged.
-- **Patch** (`1.0.1`): bug fixes and visual fixes that don't change the API.
-
-Anything prefixed `_`, undocumented internals, and the `docs/`/`examples/` sources are not part of the public API. Neither are the source-level authoring helpers described in [Component Authoring](docs/component-authoring.md) (`optional()`, `slotProps`, the `open-state.js` hooks, `bindBootstrapOverlay()`): they aren't exported from the package and may change in any release. Deprecated APIs keep working until the next major and are flagged in the CHANGELOG first.
-
-Pinning: use an exact version (`@1.2.1`) when you need byte-identical output, or the major range (`@1` on jsDelivr/unpkg, `^1.0.0` in npm) to receive fixes and features without breaking changes. Avoid `@latest` in production — it will move to the next major.
+- Runtime exports (`NodexUI`, `Component`, `mount`, `xml`, `cn`, `mergeStyle`, theme helpers), the published `dist/` file names and the package `exports` paths.
 
-## Project Documents
+**Major** releases remove or rename any of the above (listed under **Breaking** in the CHANGELOG with a migration note), **minor** releases add components, props, variants, tokens or icons, and **patch** releases fix bugs without changing the API. Names prefixed `_`, undocumented internals, `docs/` and `examples/` sources, and the authoring helpers in [Component Authoring](docs/component-authoring.md) are not public API. Deprecated APIs keep working until the next major and are flagged in the CHANGELOG first.
 
-Use these documents as the canonical project map:
+Pin an exact version (`@1.3.0`) for byte-identical output, or the major range (`@1` on jsDelivr/unpkg, `^1.3.0` in npm) to receive non-breaking updates. Avoid `@latest` in production.
 
-- [Usage Guide](docs/usage-guide.md) is the single entry point for integrating the Base UI into a consumer project — start here, then follow its links into the reference docs below.
-- [Installation](docs/installation.md) covers CDN, npm, self-hosted usage, icon assets, pinned versions, and release guardrails.
-- [Analytics](docs/analytics.md) documents the optional, standalone cookieless analytics service (`@thebase/ui/analytics`).
-- [i18n](docs/i18n.md) documents the optional, standalone translation service (`@thebase/ui/i18n`): `.po` catalogs, language detection, and the `init`/`t`/`loadCatalog` API.
-- [Runtime API](docs/runtime-api.md) documents the `window.thebase` global, mounting lifecycle, theming API, and destroy behavior.
-- [Registry](docs/registry.md) explains `dist/baseui.registry.json`, build files, block metadata, component metadata, and integrity hashes.
-- [Theming](docs/theming.md) describes `b-theme`, runtime theme overrides, shadcn-aligned tokens, Bootstrap variable mapping, and shared example theme persistence.
-- [Built-in Icons](docs/icons.md) covers the Lucide icon library, `b-icon` markup, accessibility rules, self-hosted icon paths, and JavaScript helpers.
-- [Component Authoring](docs/component-authoring.md) defines the `src/components/<name>/` source contract, component registration rules, event naming, cleanup requirements, and CSS scoping policy. Repo-only — not published to npm (see below).
-- [Base Components](docs/owl-components.md) covers the Base component API (`@thebase/ui` + `dist/baseui.templates.xml`), what to load, and common mistakes.
-- [Blocks](docs/blocks.md) documents copyable static shadcn-style blocks, source stylesheet ownership under `examples/blocks/`, gallery/viewer URLs, and block icon rules.
-- [Component Reference](docs/components/button.md) starts the per-component documentation set in `docs/components/`; each component page includes usage, attributes, events, accessibility notes, and test guidance where relevant.
-- [Frontend Implementation Plan](.agents/planning/2026-08-11-frontend-baseui-bootstrap-owl-implementation-plan.md) records the completed the Base UI 1.0.0 delivery checklist and earlier decisions for engineering context.
-- [Historical Product Plan](.agents/knowledge/baseUI/2026-08-11-baseui-bootstrap-owl-plan.md) preserves the original Bootstrap 5 + Owl product brief; use current `docs/` and registry files when they disagree with older planning assumptions.
+## Documentation
 
-The links above work as-is when browsing this repo. `docs/*.md` and `docs/components/` also ship inside the published npm package (see `files` in `package.json`), so the same docs are reachable straight from a CDN without cloning the repo — no HTML rendering, just the raw Markdown source:
+- [Usage Guide](docs/usage-guide.md): the entry point for integrating Nodex UI into a project.
+- [Installation](docs/installation.md): CDN, npm, self-hosting, icon assets, pinned versions, release guardrails.
+- [Nodex Components](docs/owl-components.md): the component API, what to load, common mistakes.
+- [Runtime API](docs/runtime-api.md): the `window.thebase` global, mounting lifecycle, theming API, destroy behavior.
+- [Registry](docs/registry.md): `dist/nodexui.registry.json`, build files, component and block metadata.
+- [Theming](docs/theming.md), [Icons](docs/icons.md), [Blocks](docs/blocks.md), [Analytics](docs/analytics.md), [i18n](docs/i18n.md).
+- [Component reference](docs/components/button.md): usage, attributes, events and accessibility per component.
+- [Component Authoring](docs/component-authoring.md): the `src/components/<name>/` contract (repo only, not published).
 
-```text
-https://unpkg.com/@thebase/ui@latest/docs/usage-guide.md
-https://unpkg.com/@thebase/ui@latest/docs/components/button.md
-https://cdn.jsdelivr.net/npm/@thebase/ui@latest/docs/usage-guide.md
-```
-
-Drop the version (`@thebase/ui/docs/...`) to always resolve to latest, or pin a version the way the rest of this README recommends pinning `dist/` assets. `docs/v2/` (the vendored general Owl framework reference) and `docs/component-authoring.md` (the Base UI's own component-authoring contract) are intentionally **not** published — they're development-time references for working inside this repo, not something a consumer needs to use the library.
+`docs/*.md` and `docs/components/` also ship in the npm package, so the raw Markdown is reachable from a CDN, for example `https://cdn.jsdelivr.net/npm/nodexui@1.3.0/docs/usage-guide.md`. `docs/v2/` and `docs/component-authoring.md` are not published.
 
 ## Development
 
@@ -166,22 +157,22 @@ npm run build
 npm run dev
 ```
 
-Open `examples/index.html` through the dev server to test the browser build. Standalone demos: `examples/apidoc/` (ApiDoc with a Petstore spec), `examples/analytics/` (dashboard + Go/FastAPI backends), and `momo_demo/` (static `b-ui` business-admin page).
-
-`examples/index.html` is the single application shell for docs, the component gallery, the block gallery, icons, and the chart catalog, all reachable through one `main-nav` and hash routes (`#/docs`, `#/components`, `#/blocks`, `#/icons`, `#/chart`). Old bookmarked URLs like `/docs` and `/blocks` redirect to their hash-route equivalent. Each block has a shadcn-style Preview/Code/responsive viewer plus its source stylesheet colocated in `examples/blocks/`. `examples/charts/index.html` mirrors the current shadcn chart catalog with interactive the Base UI examples for area, bar, line, pie, radar, radial, and tooltip charts, and is embedded inline at `#/chart`.
+Open `examples/index.html` through the dev server. It is the single shell for docs, the component gallery, blocks, icons and charts, routed by hash (`#/docs`, `#/components`, `#/blocks`, `#/icons`, `#/chart`). Standalone demos: `examples/apidoc/`, `examples/analytics/` and `momo_demo/` (static `b-ui` admin page).
 
-The Base UI includes the full Lucide SVG icon set as a built-in icon library. Use `<span b-icon="search"></span>` in HTML, or `thebase.icons.lucide.url("search")` from JavaScript. Builds publish all SVGs to `dist/icons/lucide/` and an index at `dist/icons/lucide.json`.
+Lucide's full SVG set is built in: `<span b-icon="search"></span>` in HTML or `thebase.icons.lucide.url("search")` from JavaScript. Builds publish the SVGs to `dist/icons/lucide/` and an index at `dist/icons/lucide.json`.
 
-## Package Scripts
-
-- `npm run dev` starts a static server for examples and built `dist/` assets.
-- `npm run build` creates CDN and npm artifacts in `dist/`.
-- `npm run lint` checks JavaScript and CSS policy.
-- `npm run test` runs runtime tests.
-- `npm publish` runs `prepublishOnly` first.
+| Script | Purpose |
+| --- | --- |
+| `npm run dev` | Static server for examples and built `dist/` assets |
+| `npm run build` | Build CDN and npm artifacts into `dist/` |
+| `npm run lint` | JavaScript and CSS policy checks |
+| `npm run test` | Runtime tests |
+| `npm publish` | Runs `prepublishOnly` (lint, test, build) first |
 
 ## Distribution
 
-The npm package publishes the built `dist/` artifacts plus package metadata. The browser build bundles Bootstrap CSS, and `dist/baseui.min.js`/`baseui.esm.js` embed Bootstrap's JS bundle, the Owl runtime, every Base component class, and the theme helper directly (Bootstrap then Owl then the Base UI, in that load order) — consumers install the Base UI with one stylesheet and one script tag for either API. Bootstrap's JS drives every component that has a Bootstrap JS equivalent (modal, dropdown, collapse, tab, toast, carousel, tooltip, popover, alert); the Base UI's `.behavior.js`/`runtime/*.js` helpers wrap Bootstrap's JS API instead of reimplementing it, for both the static and pure Base APIs. `dist/bootstrap.bundle.min.js` also ships standalone (unmodified) and `dist/baseui.icons.esm.js` stays a separate, deliberate exception (2000+ generated icon components would blow the main bundle's size budget), as do the ApiDoc language logos (`dist/apidoc/img/`, loaded on demand) and the opt-in analytics service (`dist/baseui.analytics.esm.js`/`.min.js`, so pages that don't track pay nothing for it) — everything else is one file. Every shipped CSS/JS artifact is minified — there are no unminified twins to keep in sync.
+The npm package `nodexui` publishes the built `dist/` artifacts, `docs/`, `README.md`, `CHANGELOG.md` and `LICENSE`. Everything is minified, with no unminified twins. Deliberate separate files: `dist/nodexui.icons.esm.js` (2000+ generated icon components), the ApiDoc language logos in `dist/apidoc/img/`, the analytics, i18n and ApiDoc bundles, and `dist/bootstrap.bundle.min.js` (unmodified, for projects that vendor built-in JS themselves).
+
+## License
 
-The published tarball also carries `docs/*.md` and `docs/components/` (see the "Project Documents" section above), `README.md`, `CHANGELOG.md`, and `LICENSE` — `docs/v2/` and `docs/component-authoring.md` are deliberately excluded from `package.json`'s `files` list since they're development-time-only references for working inside this repo.
+MIT. See [LICENSE](LICENSE).