Backlog
3Under consideration
Branches
Branches allow users to work in isolation, allowing to merge back to the main branch. This makes collaboration easier where more drastic changes are tried out.
Marketplace
A place for community members to share and reuse projects, graphs, token sets
Cross-project dependencies
We’ll work on allowing you to use tokens defined in one project in another project.
Next up
1Committed and queued
In Progress
2Actively being built
Releases
We’re working on introducing Releases in Studio, letting you publish versions of your design system and freezing it in time. Creating a release You’ll be able to create a release by going to the Releases page and then creating a new one. To understand what changes are going to be part of that release, there’s going to be a preview of the changes that the release will consist of. If you haven’t ever published a release, we’ll let you choose your initial version. After that, we’ll increment every time you release - you’ll be able too choose if it’s a Patch, Minor or Major release. Token previews In the list of changes a release consists of, you will be able to select each token, and see a preview of the before/after Usage outside of Studio We’ll also add support for specifying the release when pulling from the CLI, letting you pull either the latest published release, or a specific release version. That way, you can start integrating Releases into your build pipeline. Upcoming releases features That’s not all - once we have built the core version of Releases, we’ll work on enhancements, such as adding Webhook support so you can automatically trigger new deployments of your packages or website whenever tokens change. If there’s anything you’d like us to include when working on that feature, please let us know!
Better upload experience
Uploading often comes with token validation steps, the system should ideally tell users what wasnt valid about their tokens, and offer ways to remediate.
Done
Recently shipped
No Done issues