carbon-platform
carbon-platform copied to clipboard
carbon-design-system
Add version numbers to design kits
🔎 Missing content
Page: https://next.carbondesignsystem.com/design-kits?q= Issue: Versioning numbers are missing for v10 on themes (both Carbon System and IBM Dot com) Suggestion: Adding v10 numbers on the titles. For example: Figma gray 10 theme -> Figma v10 gray 10 theme
Originally posted by @thyhmdo in https://github.com/carbon-design-system/carbon-platform/discussions/1270#discussioncomment-3684331
Another thing that has come up around Design Kits is not all teams have their library kits in the 4 themes. A lot of them only support one maybe two themes. The only place we mentioned the theme color ATM is in the Title.
Schema data should expand to:
- Tool: Figma, Sketch, XD
- Type of kit: UI, Guidelines, Wireframe
- Maintainer:
- Status:
- Theme: White, Gray 10, Gray 90, Gray 100, n/a
- Carbon version: V10, V11
- Local version: Cloud PAL v1, v2 etc
Some of the data is also conditional. UI kits would have themes, but a wireframe kit probably doesn't.
Other random thought Anna had while looking at the Kit catalog and talking to Diana.
The titles also seem to be doing a lot of work, in some cases it has the tool + version + theme + name all in the title. And other times kit titles don't include the tool type.
I think we need a strategy for when essentially the same files exist across multiple manifestations.
I also think it might be nice if there was an easy way to see what didn't exist. Especially regarding a kit that exist in one manifestation but not another. IE production guides exist in Sketch but not Figma (yet ... and is there a way to tell people if its coming?)
Yes 100% agree that the title is doing too much work and that the schema could expand here to include the theme. We'd need another level of visual cue to show the kit theme.
Could it be a tag... or could it also be a thumbnail... showing the components on the correct themed background... this might really help with the read... since a lot of kits are different... I also don't think it would get too repetitive. I think this is something to explore.
The thumbnails might be too repetitive regardless, or they might work… but at least it would be a much quicker read on theme. Otherwise, we could try using another tag… but it would be better to color coded tag or something… it would just be nice to get another visual cue apart from text. on the theme.
@jeanservaas @aagonzales @aubrey-oneal if we add a key to the schema for "supported Carbon major versions", we could show that in the inline meta data. Same with supported color themes.
We'd want to allow one or many supported Carbon versions and Carbon themes.
One idea is to comma-separate them in the meta data line. Most of our design kits only support one Carbon version, and one color theme, so there would be no commas.
It would more commonly look like:
We could then add "Carbon version" and "Color theme" to the two open spots in the multi-select filter.
