Plan for removing euiColorGhost and euiColorInk

[ryankeairns]

With the transition to Emotion complete, do we have a plan for fully deprecating euiColorInk and euiColorGhost from EUI?
Further, if not already done, guidelines should be provided for consumers of EUI on removing these variables and, if applicable, use Emotion theming at a UI level.

[JasonStoltz]

Just dropping in here to +1

[cee-chen]

Unless there's a very compelling reason to (e.g. the new theme, etc) I think my vote at this point would be to just leave those 2 tokens alone and not remove them. My two reasons for saying this:

• It doesn't feel worth the time/effort spent to hunt down existing usages in both our own codebase and Kibana/Cloud and convert/remove said usages (vs. spending time elsewhere)
• From my recent work in implementing high contrast modes in EUI, ghost and ink actually came in use once or twice there, particularly when working with Windows' high contrast themes which forces specific colors and tends to be very white/black

The above are not super strongly held opinions and I'd be open being argued against this vote.

[ryankeairns]

Maybe we take a half step, don't change any code, but add this topic to the color guidelines:

1. When to use ink, ghost
2. When to use textInverse, and
3. When/how to use Emotion to make a section always dark, for example

[kyrspl]

Adding to what @cee-chen mentioned:
I noticed a few occasions where euiColorGhost / euiColorInk are used for background colors, rather than text. It will require some digging to understand whether other tokens would be more fit for purpose.