Hi! I'm currently using kibo-ui and love the component quality. I noticed the registry endpoint (/r/{name}.json) is designed around shadcn/ui + Radix UI.
I'm wondering if there's any plan to support Base UI (the new headless library from the MUI team) as an alternative foundation, either as:
- A separate registry endpoint (e.g.,
/r/base-ui/{name}.json)
- Or components that can be configured to use Base UI primitives instead of Radix UI
Base UI is gaining traction as a modern, unstyled alternative to Radix UI with a similar API surface. It would be great to know if this is on the roadmap or if there's a recommended approach for using kibo-ui components with Base UI.
Thanks!
Hi! I'm currently using kibo-ui and love the component quality. I noticed the registry endpoint (
/r/{name}.json) is designed around shadcn/ui + Radix UI.I'm wondering if there's any plan to support Base UI (the new headless library from the MUI team) as an alternative foundation, either as:
/r/base-ui/{name}.json)Base UI is gaining traction as a modern, unstyled alternative to Radix UI with a similar API surface. It would be great to know if this is on the roadmap or if there's a recommended approach for using kibo-ui components with Base UI.
Thanks!