One of the current differences in WVUI and Wikit is the variables (design tokens) architecture.
== Goals of design tokens
- single source of truth for design to development handover,
- in a set of predefined, centralized, limited and traceable design decisions
== Comparison of current approaches
Wikimedia Vue UI has been relying on [[ https://gerrit.wikimedia.org/r/plugins/gitiles/wikimedia-ui-base/ | WikimediaUI Base ]], which has seen an initial implementation based on OOUI widgets.
It has been following the idea of
- base variables that are applied in as many components as possible to clearly indicate going away from those `-base` variables needs to have a strong cause to add an extra variable
Wikit applies three type of variable levels:
- base (taking WikimediaUI base)
- global aka general
- component-level tokens
Additionally Wikit relies on JSON format
== Open questions
- Abstraction issues to hunt down source of an issue (which in turn might lead to a lot of unnecessary overrides and less consistency)
- …together with additional level of abstraction in component-level tokens
- Why is redefinition of base into global necessary?
- Technological format choice (CSS/LESS/Sass vs JSON)