- Issue created by @G4MBINI
- 🇫🇷France pdureau Paris
OKLCH is interesting and can be considered in a bigger
When we created UI Skins, we took inspiration from UI Patterns Settings & Layout Options, so we used form elements plugin ID: textfield, color, checkbox...
Today, UI Patterns Settings & Layout Options are getting merged into UI Patterns 2 which is using JSON Schema for typing, instead of form elements plugin ID.
Why not decoupling data structure from form building in CSS variables too?
We can take the CSS data types:
https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Types
Or the new design tokens data types:
- Color
- Dimension
- Font family
- Font weight
- Duration
- Cubic Bézier
- Number
- Stroke style
- Border
- Transition
- Shadow
- Gradient
- Typography
https://design-tokens.github.io/community-group/format/#types
- 🇫🇷France Grimreaper France 🇫🇷
So, duplicate of ✨ UX: Add other widgets Active ?
- 🇫🇷France pdureau Paris
Yes, but not using the Drupal form elements as data type. We need to bad this practice. And promote the use of proper well-defined, industry standard, data types.