Mixins / Authoring components

Authoring components

When the shipped foldkit-mixins-ui catalog doesn't have the widget you need, you don't have to copy a template or manage DOM state in hooks. Foldkit Plus lets you assemble custom components from the same pieces the catalog uses: foldkit-mixins for typed Slots, styles, and accessibility contracts; foldkit-primitives for reusable interaction state and keyboard/focus Behaviors; and foldkit-bundle for packaging repeatable child state.

Every component follows one state rule: your application Model owns domain facts, a placed primitive Bundle owns interaction state (like which item is highlighted), Behaviors attach DOM attributes and mounts to named Slots, and every event or attribute on a slot has a single owner.