Kevin Powell
Kevin Powell
@romainmenke can you elaborate on how: > A simpler and more straight forward format is: > more difficult to read and write by hand Perhaps with an example? Those two...
Reviewed by the spec editors on 2021-10-19. No further changes to the spec decided based on current discussion. Leaving this thread open for further discussion.
At a minimum, whatever capabilities we add to the Color Type in future iterations, token authors who hand-edit their files must be able to specify a color using only a...
@c1rrus I agree the current structure creates duplication of headers, but I find that structure more scannable when looking at the outline. Your proposed changes will DRY up the document,...
Thank you for this suggestion. The spec editors have reviewed this issue and decided not to add this functionality to the specification. Our rationale for this decision is to allow...
>I know that the ideal scenario of design tokens is for designers and developers to equally be able to update/change/add tokens, including directly from a design tool, but for teams...
@c1rrus I agree with your outline and I think those concepts will hold, regardless of how broad or narrow our token types are. I believe our aim, regarding specific types,...
@romainmenke **narrow type example**: Color - supports HEX representation of colors **broad type example**: Color - supports HEX + multiple other representations of colors (including those in color spaces HEX...
@romainmenke by what definition is HEX notation obsolete?