[joduplessis]

This looks really interesting. I'd be very interested to see how you guys iterate to accommodate other frameworks or actual design systems. IMO Chakra isn't so much a design system as it is a framework (like Tailwind) - it's an abstraction to make common tasks easier. Would love to see something a little more "ui-kit-agnostic".

[dabbott]

That's a great point! For simplicity we've been referring to our current "design system" as Chakra, but it's definitely more nuanced than that. We think of a design system as "a library of components and tokens, and rules for how these are used in a design". Our current design system uses Chakra for the component library part of it, while we created the rules for using those components in a design.

We're currently working on a protocol for adding new design systems, which will support integrations at different levels, from component libraries like Chakra to more complete design systems like Airbnb's DLS. We'll have more to share on this soon!

[Terretta]

Here is a design system. While beautifully on-brand, as you click in, you get all the way to literal cut and paste code:

- Overview: https://adele.uxpin.com/audi-audi-ui

- The system: https://www.audi.com/ci/en/renewed-brand.html

Some less brand-y examples:

- https://polaris.shopify.com/patterns/app-settings-layout

- https://ux.mailchimp.com/patterns/color

- https://designsystem.digital.gov/design-tokens/

Frameworks or component libraries like Tailwind or Material, are not design systems.

Therefore, when you say you plan to integrate open source design systems, this should not mean frameworks or component libraries. It should mean design system systems, such as:

- https://storybook.js.org/

This, on transforming component libraries into design systems, is worth reading:

Design Systems for Developers - A guide that teaches professional developers how to transform component libraries into design systems and set up the production infrastructure used by leading frontend teams:

https://storybook.js.org/tutorials/design-systems-for-develo...

There's a huge need to fill the gap for design systems that "implement themselves" in the transition from wireframe to code. Hopefully you can vector to align with actual design systems instead of components/frameworks. Serving companies with real design system needs is how you get the enterprise ecosystem revenue to get bought by Adobe for $20B in cash and stock!

// Disclosure: Was co-founder and CTO of a top 5 digital (web design) agency, am enterprise customer of today's design agencies.