After years of development, experimentation, architectural decisions, and more CSS than I care to admit, Juice has officially reached v1.0.0.
And I couldn't be more excited to finally say that.
For those who haven't followed my previous articles, Juice is an open-source, attribute-first CSS and UI library I've been developing as part of CitrusWorx's WebEngine ecosystem.
It started with a relatively simple question:
What if building interfaces felt more like describing what you wanted, rather than constantly wrestling with how to style it?
That question eventually became Juice.
Today, I'm excited to share its first major release.
The Problem I Wanted to Solve
Modern frontend development is incredibly powerful.
We have mature frameworks, sophisticated design systems, utility-first CSS libraries, component ecosystems, and tooling that would have seemed unimaginable a decade ago.
But somewhere along the way, building a relatively simple interface started requiring an increasingly complicated collection of abstractions.
Sometimes you need a component library.
Sometimes you need a CSS framework.
Sometimes you need a JavaScript framework just to make everything work together.
And sometimes, all you really want is a card with a heading, some content, and a button.
I kept asking myself whether we could make the everyday parts of UI development simpler without sacrificing the flexibility needed for more sophisticated applications.
I didn't want to reinvent CSS.
I wanted to rethink how we interact with it.
Enter Juice: Attribute-First UI Development
Juice takes a different approach to expressing layout and presentation.
Instead of relying entirely on lengthy class lists or custom component abstractions, Juice allows developers to describe their interfaces directly through HTML attributes.
For example, here's a conceptual illustration of the attribute-first approach:
<div stack gap="4">
<div card padding="4">
<h2>Welcome to Juice</h2>
<p>
Build interfaces with expressive markup.
</p>
</div>
</div>
The idea is straightforward:
Your markup describes the structure. Your theme defines the visual identity. Juice connects the two.
Attributes such as stack, row, grid, gap, padding, card, and surface make layout intentions visible where the interface is actually being constructed.
This isn't about replacing every CSS rule with an attribute.
It's about providing a more expressive foundation for the things developers do repeatedly.
More Than Another CSS Framework
One of the most important architectural decisions behind Juice was making it useful independently of WebEngine.
Although Juice is being developed as part of the larger CitrusWorx ecosystem, it isn't intended to require developers to adopt that entire ecosystem.
You should be able to use Juice in a standalone project, integrate it into an existing application, or combine it with the frontend technologies you already enjoy.
That independence matters to me.
I don't believe developers should have to replace their entire toolchain just to benefit from one useful library.
Juice is designed around a CSS-first foundation, with JavaScript capabilities available where they make sense.
Its broader architecture also brings together design tokens, themes, components, and optional runtime behavior.
The goal is to provide a consistent UI foundation without forcing every application into the same architecture.
Why Themes Matter
One of the principles driving Juice is the separation of structure and identity.
A layout shouldn't have to be completely rewritten just because an application needs a different visual personality.
The same structural building blocks should be reusable across projects while themes control how those building blocks look and feel.
For CitrusWorx, this is especially important.
WebEngine is intended to support a growing ecosystem of applications and developer tools.
Having a shared visual foundation means we can establish consistency without requiring every application to look identical.
That's the balance I'm working toward with Juice.
What v1.0.0 Actually Means
Reaching version 1.0 isn't the same as declaring a project finished.
If anything, it means accepting a new level of responsibility for the foundation you've created.
During the 0.x development cycle, I spent a considerable amount of time exploring the boundaries of what Juice should become.
There were questions about how attributes should behave, how themes should work, how much JavaScript belongs in a CSS-first library, and how to organize the different pieces into something developers can reasonably understand.
There was also the temptation to keep adding features.
Another component.
Another runtime.
Another abstraction.
Another improvement before calling it ready.
Eventually, though, a library needs to stop being an endless experiment and start becoming something people can actually build with.
Juice v1.0.0 represents that transition.
It's a commitment to a public foundation that developers can begin adopting, testing, and helping improve.
It doesn't mean every idea on the roadmap has been implemented.
It means the project has reached its first major milestone, and future improvements can build on that foundation.
Juice and the Bigger WebEngine Picture
If you've followed my Road to WebEngine series, you know Juice isn't being developed in isolation.
It's one part of a much larger effort at CitrusWorx to build an ecosystem of modular, interoperable developer technologies.
Another major part of that ecosystem is Sig.js, our JavaScript library for building reactive interfaces.
With Sig.js and Juice both reaching their first major releases, two important pieces of the WebEngine vision are beginning to come together.
Sig.js addresses how interfaces are constructed and updated.
Juice addresses how those interfaces are structured and presented.
They have different responsibilities, and that's intentional.
I want developers to be able to adopt individual pieces of WebEngine without being forced into an all-or-nothing framework decision.
The broader vision is ambitious, but it's being built one library, one package, and one release at a time.
Getting Started
Juice v1.0.0 is available on npm.
npm install @citrusworx/juiceui@1.0.0
You can explore the package and source code here:
npm: https://www.npmjs.com/package/@citrusworx/juiceui/v/1.0.0
GitHub: https://github.com/citrusworx/webengine/tree/master/libraries/juice
Whether you're interested in attribute-driven styling, design systems, frontend architecture, or simply exploring a different approach to building interfaces, I'd love for you to take a look.
What's Next?
Reaching v1.0.0 doesn't mean development slows down.
It means the focus changes.
Moving forward, I want to spend more time improving the developer experience, refining documentation, expanding practical examples, addressing issues that emerge from real-world usage, and continuing to evolve the library without losing sight of its original purpose.
I also want to explore how Juice can make UI development more accessible to people who aren't necessarily frontend specialists.
Because I believe good developer tools should make creativity easier, not introduce unnecessary barriers.
A Personal Milestone
Building something like Juice takes a surprising amount of persistence.
There are days when everything comes together beautifully.
And there are days when you find yourself questioning an architectural decision you made three months earlier.
But that's part of engineering.
You experiment.
You discover limitations.
You rethink assumptions.
You improve the design.
And eventually, you ship.
For me, Juice reaching v1.0.0 is another step toward turning CitrusWorx from a collection of ideas and experiments into a real ecosystem of software that other developers can use.
There's still an enormous amount of work ahead.
But today, I'm celebrating this milestone.
Juice 1.0 is here.
If you try it, I'd genuinely appreciate your feedback. Tell me what works, what doesn't, and what you think an attribute-first UI library should do differently.
Thanks for following along on the Road to WebEngine.
We're just getting started.
Built with curiosity, persistence, and a whole lot of CSS.
#webdev #css #opensource #javascript
Top comments (0)