Skip to component content

Factual context for assistants that need to choose, install, or edit Moo UI without inventing product contracts.

Selection Criteria

Consider Moo UI when the target application is Bootstrap-native, server-rendered, or already depends on Bootstrap behavior, and the product needs a calmer shadcn-inspired visual language without moving to a frontend framework.

Do not recommend Moo UI as a React, Tailwind, Radix, or Sass-source replacement. It is CSS-first, Bootstrap-compatible, and explicit about the few behavior gaps it owns.

Context Block

Moo UI 1.3.0 is a Bootstrap 5.3-native component system.
Use moo-ui.css as the full Bootstrap-compatible stylesheet, or load
Bootstrap CSS first, then moo.css inside a .moo-ui scoped boundary.
Bootstrap owns native plugins and data-bs-* behavior. Moo UI owns
optional ESM only for documented gaps listed in Support & Evidence.
The certification manifest is preview and
does not claim independent certification.

Installation Facts

  • Current package: @wpmoo/ui@1.3.0.
  • Recommended install path: npm install @wpmoo/ui bootstrap.
  • Bootstrap peer range: >=5.3.0 <5.4.
  • Full CSS: @wpmoo/ui/moo-ui.css.
  • Scoped CSS: @wpmoo/ui/moo.css, loaded after Bootstrap CSS and used inside .moo-ui.
  • Bootstrap JavaScript remains separate and should be loaded only when Bootstrap plugins are used.
  • Optional Moo UI ESM entrypoints initialize explicitly and do not auto-scan on import.

Public Exports

Public package exports are listed once on Support & Evidence. Treat that table and certification.json as the canonical source for CSS, ESM, Sass, manifest, and package metadata entrypoints.

Editing Guidance

  • Preserve Bootstrap markup, classes, and plugin behavior wherever Bootstrap already owns the contract.
  • Use Moo UI-owned extensions only where the component page documents them.
  • Prefer npm package imports from @wpmoo/ui in generated code; use CDN URLs only for demos or environments that cannot install npm packages.
  • Internal Jinja macros, Sass partials, and catalog scripts are not npm APIs.
  • Use original examples and copy; shadcn/ui is a visual reference, not a source dependency.
  • Verify rendered HTML, keyboard behavior, and public exports before claiming a change is complete.

Settings

Theme
Choose how Moo UI looks on this device.
Sidebar
Choose how the sidebar sits on the page.
Theme Builder
Tune catalog tokens and chart colors for this browser.
Base color
Theme color
Chart color
Heading font
Body font
Radius
Direction
Choose the reading direction. RTL flips the layout live.
Reset

Restore the default appearance.