bambiui documentation
Installation
Initialize a project, choose a framework target, and copy only the components you use.
Architecture
Understand the core → generator → registry → CLI → user project flow.
Design tokens
Theme components with CSS custom properties, semantic aliases, and intent aliases.
What makes bambiui different?
Section titled “What makes bambiui different?”bambiui does not ask applications to depend on a runtime component package. The CLI copies generated public artifacts into the user project. The installed files are local source: framework wrappers, component CSS, and shared helpers declared by the public registry.
Framework-aware docs
Section titled “Framework-aware docs”Use the framework selector in the top-right navbar to switch installation and usage snippets between React, Solid, Svelte 5, and Vue 3. Component behavior and tokens remain consistent because every framework output is generated from the same internal DOM Protocol contracts.
Component docs
Section titled “Component docs”Every component has its own page with:
- installation command for the selected framework
- usage snippet for the selected framework
- preview guidance
- behavior notes
- accessibility guidance
- related token list at the end