Skip to content

carbon-design-system/roadmap

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits
 
 
 
 
 
 

Repository files navigation

Carbon Design System roadmap

This repository houses the Carbon Design System roadmap so you can learn about what we're working on and what we have planned for the future. Have questions or comments? Join the discussion in Carbon's primary repository for backlog specifics.

Using the roadmap

Each roadmap item is an issue with one or many labels to indicate its related libraries, services, and the status of each. Instead of commenting on roadmap items in this repository, each roadmap item will have linked issues to other repositories where the work and discussions are actively taking place.

Libraries

  • Carbon Adobe XD - Adobe XD design kit of common visual assets like color, type, iconography, and components
  • Carbon Angular - Angular implementation of Carbon components
  • Carbon Axure - Axure design kit of common visual assets like color, type, iconography, and components
  • Carbon Charts - Data visualizations implemented as Angular, React, Svelte, Vue, and vanilla JavaScript
  • Carbon Components - Component styles and vanilla JavaScript
  • Carbon Elements - IBM Design Language elements like colors, type, iconography, and more
  • Carbon Figma - Figma design kit of common visual assets like color, type, iconography, and components
  • Carbon Gatsby Theme - GatsbyJS theme to build websites with Carbon
  • Carbon Icons - Icons implemented as Angular, React, Svelte, Vue and vanilla JavaScript components
  • Carbon Patterns - Reusable combinations of components and templates that address common user objectives
  • Carbon Pictograms - Pictograms implemented as React and vanilla JavaScript components
  • Carbon React - React implementation of Carbon components
  • Carbon React Native - Carbon mobile Sketch kit and React Native assets
  • Carbon Sketch - Sketch design kit of common visual assets like color, type, iconography, and components
  • Carbon Svelte - Svelte implementation of Carbon components
  • Carbon Vue - Vue implementation of Carbon components
  • Carbon Web Components - Web Components implementation of Carbon components
  • IBM Plex - IBM's typeface

More libraries will be added as needed.

Services

  • Carbon Devtools - Browser extensions to aide in the design, development, and QA of Carbon-built pages
  • Carbon Telemetry - Collects Carbon package usage information for IBM and Carbon properties
  • Carbon Website - Carbon Design System website
  • IDL Website - IBM Design Language website

More services will be added as needed.

Status

  • Experimental - Exploratory efforts, no delivery committments yet
  • Alpha - Partially complete, limited documentation, no delivery timeline
  • Beta - Mostly complete, fully documented, published timeline
  • RC - Release candidate, final quality assurance
  • GA - Generally available and published via package latest tags

Teams

GitHub teams in the carbon-design-system organization might be added in the future and mapped to various libraries, services, and/or roadmap items to provide more clarity on who is maintaining and contributing to what.

Contributing to the roadmap

This roadmap is intended for higher-level items across our design system. As such, it's not a place to document bugs or daily/weekly tasks. If the feature or enhancement is big enough to share in a Medium article, then it's worth including it in this roadmap.

  • Use the issue template to add roadmap items
  • Lock issue conversations so we can concentrate comments and discussions in the repositories where the work is taking place
  • Once there's a related GitHub issue for a roadmap item, add that issue as a comment to the roadmap item
  • Once a roadmap item has been delivered, add a comment linking to the release notes, announcement, etc. and close the issue

Issue template

The following issue template is used to create roadmap items.

Issue template

### Summary

_What problem (or opportunity) are we solving? Why are we solving it? Is there supporting user conversations or research? How does this affect different parts of IBM and beyond?_

### Job stories

_Describe job stories to make the value we deliver to our makers clear, and what it will enable them to do._

1. When ___, I want to ___, so I can ___.

### Success measures

_How we will determine whether the problem as been solved, should that be qualitative and/or quantitative measures?_

1. To do

### Sponsoring team

_If there is a team or group of individuals that are carrying the effort forward, list them here._

Disclaimer

This roadmap does not represent a commitment, guarantee, obligation or promise to deliver any library or service, or to deliver anything by any particular date, and is intended to outline the general design and development plans.