👩‍🎨 🎨 Second screen enhancements

Our community is using Second Screen as a visual way to see more information about their tokens in a grid-style display, and they have requested some enhancements:

• Resolved values for color modifiers need to be accurate

  • Today, the values don't match what is being shown in the plugin when references are a part of the color token

  • Modifier value doesn't appear in the UI as expected.

• When viewing the JSON of my tokens in Second Screen, each token includes a system generated ID kvp. This is an issue because:

  • It's not accounted for in our transforms

  • because it is system generated, duplicating or creating tokens in JSON view makes the value impossible to work with

  • If two or more tokens contain the same ID value, changes to the tokens will not save and an error is presented

• Remove the name label from the token name property, as it triggers password keepers to assume it is a name input field.
  

  

😬 The reality

Color-modified tokens were added after Second Screen was launched, and these features weren't included in the scope of work.

💭 How might we...

Ensure that new token types and improvements on existing token types are supported in Second Screen as a part of our project planning?

💬 Feedback that is valuable

• What other enhancements to Second Screen would be valuable to you?

• How does this issue impact your day-to-day workflow?

• What workarounds do you have?

↔ Related topics

• TBD →