Re: [community-group] Legacy color (#137)

The proposals in this thread are great, keep them coming!

From a technical perspective, this is all solvable. There are canonical implementation of color space translation functions, and design tools as well as token translation tools could work around this when consuming tokens. That said, some tools are aim to not only consume tokens, but also manage them.

I'm really curious about the user experience for someone consuming/editing/exporting tokens in a design tool like XD, UXPin, Framer, Figma… which don't have full color space/profile management (yet).

Here's an example use-case, followed by a few questions about the possible flows:

### Use-case

1. import a token file
2. edit a wide-gamut color
3. save/re-export the token file

### Questions

1. When editing the color in an sRGB-only tool, or with a custom color profile setting, what should the flow/color picking UX be?
2. During the export phase, what sort of prompts would you expect in relation to potential data-loss?
3. What should the exported data look like?
4. What about people working on monitors that don't cover sRGB? What should their editing experience be?

-- 
GitHub Notification of comment by kaelig
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/137#issuecomment-1175759343 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 6 July 2022 04:10:27 UTC