Token names have been updated for easier application. Names are more logical and easier to apply without always having to refer to a guide.
Nothing visually has changed in any of the components, and so no redesign work is required.
CSS grid provides easier implementation of layouts, support for sub-grid, and other features that come along with this new technology.
CSS custom properties for theming (light mode / dark mode).
A significant reduction in compile times for most projects with the update to Sass architecture.
Quality of life updates such as:
- Consistent component API across the board.
- Improvements to Sass structure for getting started and productive use experiences.
- Cover a wider variety of use-cases in your product with some of our new components.
- Easily build our more accessible experiences with our accessibility component primitives.
- Light/dark mode support.
- Faster time to develop new features.
- New components added that can be used instead of being newly developed.
- Accessibility primitives to help build more accessible experiences as early as possible to the development process.
- Faster load times due to smaller bundle sizes.
- Faster time to develop new features
- New components added that can be used to build off of instead of being newly developed
- Accessibility primitives to help build more accessible experiences as early as possible in the development process
Carbon v11 includes functionality that may be a motivator for migration, but teams can migrate to v11 when they have the bandwidth.
Teams that are using v10 today can continue to stay on v10 and everything that is implemented will continue to work.
No new functionality will be introduced in v10 after the v11 release.
We will continue to address high impact bugs that come up for the v10 release after the v11 release.
We will continue to accept any contributions that look to address issues in the v10 release if we are unable to get to them in time for your product roadmap.
Assets that were deprecated from v9 to v10 will be removed in v11.
Assets that are deprecated in v10 will remain in v11 and will be removed in v12. While the timeline of v12 has not been set, the team’s intent is for major versions to be at minimum 12 months apart.
Visually, nothing is changing.
There are system-side changes that will require changes to design specs and code, like the token names update and inline theming.
Token names are largely a 1:1 update and very few tokens are keeping their v10 name. This means color tokens will have to be updated across assets.
We are hoping to be able to provide a script that can make these changes on the code side automatically, however this has not been built or tested yet.
Making these updates now creates a better system user experience and it sets us up for growth and scale so new tokens can fit into the set more easily.
The new names imply the usage and so will be much easier to apply. For example,
The Carbon Sketch files will automatically update to v11. Connected styles and symbols will automatically receive the v11 updates once the library update is accepted by the users in each design file.
If you’re not ready to update to v11, you can stop accepting library updates to that file until you are ready.
Sketch files for v10 will be available in the GitHub archive but will no longer be an attached library. There is no way to properly version Sketch Cloud files. There is only the latest version.
The effort to update local/PAL assets depends on the structure of files. If you are using the Carbon layer styles then the update will be automatic. If you’re using hard values and just specing the token names, then you will need to update your specs.
Read the Sketch documentation for more details.
We’ll have more on this once we have interviewed teams that have successfully migrated to v11.