Carbon coverage: Feedback session Nov 2024

[RichKummer]

To better understand designer needs with the Carbon coverage plugin, we want to run a feedback session with designers. Before then, we want to make sure everyone is able to install and begin using the plugin locally in Figma.

Tasks

Preview Give feedback

1. Schedule feedback session
2. Run/record feedback session
3. Collect notes

[RichKummer]

Plugin feedback session 11/20/24

Participants: Najeeb P, Vora Supadulya, Will Ragan, Samuel Ting

Carbon team: Eliad Moosavi, Tracey King, Rich Kummer

Enable the plugin from the Figma community: https://www.figma.com/community/plugin/1440754449508082367/carbon-v11-coverage

Vora

• Will share Community link with watsonx team.
• The “Check for v11 libraries” notification is not clear. Would it be possible to show this more in-line with the issues it is relevant for?
  • This is similar to Mike’s feedback with an icon/tooltip.
  • The warning makes me think something may have gone wrong.
• Sometimes teams get confused because they think they’re working with a v11 file when it’s really a v10 file.
• Definite request for a way to automate updating v10 to v11 tokens for that migration use case.

Will Ragan

• Transitioning to v11. On Cognos team.
• We have designs from v9.
• Eliad: We could test on a v9 spec, we haven’t done that already.
• This will be extremely helpful!

Sam Ting

• Also looking for automated solution.
• Will share out to his team.

Shaun Lynch

I noticed it will sometimes have trouble searching through nested instances. For example I'm looking within the content autolayout within a modal I'm working with and it's only catching the Text area component despite there being a context switcher, text input and tertiary button also within that layout.

• Figma file

Rich Note

• Tabs should only appear if they are relevant, instead of Color (0) for example.
• We should update description for community to be more thorough.
• We should update thumbnail for any paragraph description below.

Design updates ++++

• The warning notification makes users feel that something has gone wrong in running the plugin.
• Update design with updated top paragraph and removed warning notification.