KidsUI is a small UI kit for kid-friendly web projects. I built it because I keep finding small reasons to make little things for my daughter, her kindergarten, and the teachers who sometimes reach out for help.
I did not set out to make a design system. I just kept needing the same kind of parts.
A few little projects for my girl in kindergarten. A small page or tool when one of her teachers reaches out for help. And a few simple web apps I want to build later, partly for fun and partly for educational use.
So I pulled those pieces into one place and called it KidsUI.
Why this exists
The goal is not completeness. The goal is a small set of components that already feel right for children: friendly, clear, a little playful, and easy to drop into tiny projects without dragging in a whole frontend stack.
Why web components and motion
The stack is web components with motion. I do not want the kit bound to any one library.
Not React. Not Vue. Not even my usual favorite, ViewComponent.
If a project is plain HTML, Rails with Stimulus, or some other stack entirely, the UI pieces should still work. That portability matters more to me here than framework convenience.
Motion is part of the language too. Kids notice movement immediately. Used lightly, it makes an interface feel alive and welcoming instead of static and dry.
That is the whole idea behind KidsUI: small components, small projects, and a softer place to start building simple web apps for kids.