If anything, one of the biggest lessons I've learned while building it has been knowing when not to add another feature.
At some point, a library has to stop being an experiment and start making promises.
There will undoubtedly be things I look back at later and wonder why I designed them that way.
And I definitely didn't want Juice to become responsible for every possible design decision.
Instead of describing every implementation detail, Juice could provide a small vocabulary for common design intentions.
A lot of Juice didn't come from sitting down and trying to invent a design system.
One of the more recent milestones has been getting Juice to consume configuration and generate stylesheets from it.
Juice can then generate the stylesheet that supports its attribute-based styling system.
That's important because I don't want applications to rely on Juice for their entire identity.
Strangely, getting closer to 1.0 hasn't made me think about everything else Juice could do.
And every feature expands the surface area that has to be understood, documented, tested, supported, and maintained.
I want them to have reasonable confidence that I'm not going to wake up next month and decide the entire vocabulary should work differently.
The little things that were easy to ignore while experimenting suddenly matter much more.
I don't want it to become a giant collection of options simply so I can say it supports everything.
And when Juice isn't the right tool for something, I want developers to be able to use CSS without fighting the framework.
KiwiEngine is an ecosystem, and ecosystems become real one stable piece at a time.
Juice becoming stable gives everything built above it a more dependable foundation.
And after spending so much time writing about systems, abstractions, constraints, real projects, documentation, and intent, it's satisfying to see those ideas materializing in an actual library.