[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E added a project: Codex.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, STHart, 
karapayneWMDE, Invadibot, Lectrician1, caldera, maantietaja, Akuckartz, 
DannyS712, Nandana, Lahi, Gq86, Inductiveload, Xover, GoranSMilovanovic, 
QZanden, LawExplorer, Iniquity, _jensen, rosalieper, JGirault, Scott_WUaS, 
Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E added a comment.


  In T266688#7267420 , 
@AnneT wrote:
  
  > Another practical question: when does a value become a design token? This 
is the process I've been following:
  >
  > 1. Is it a simple keyword, like `display: flex`? If so, probably don't use 
a token, unless it's something that gets repeated a lot like the value of 
`cursor: disabled`
  
  Follow-up on `cursor` tokens in T302181#7724398 
 (tl;dr for themability 
reasons it seems useful to tokenize them)

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, STHart, 
karapayneWMDE, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, Nandana, 
Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, 
rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E updated the task description.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, Invadibot, 
caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, 
JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, 
Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E closed this task as "Resolved".
Volker_E claimed this task.
Volker_E added a comment.


  Conclusion from the Vue.js taskforce convening:
  **Proposal on “2 levels vs 3 levels of abstraction (do we need the final 
level, component tokens)?” with vote results: WMDE approach 2 - WMF approach w. 
rare exceptions of single-use components 7 - abstain 3**
  
  We're settling on base tokens file for general and grouped (f.e. input-binary 
specifics) tokens and on component tokens file, which will contain 
single-component-tokens only when needed.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, Invadibot, 
caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, 
JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, 
Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E added a comment.


  In T266688#7271853 , 
@Sarai-WMDE wrote:
  
  >> There's a lot of gray area in here, though, especially step 2. I looked 
through some WVUI components I've built and found some examples of values for 
which I did not create a token:
  >>
  >> - `outline: 1px solid transparent`
  >> - `content: ' '`
  >> - `top: 50%`
  >> - `border: @border-width-base @border-style-base transparent`
  >> - `transition: background-color @transition-base, border-color 
@transition-base, border-width @transition-base;`
  >>
  >> Those could all be debatable. The goal would be to take the debate out of 
it as much as possible with clear instructions on when one should create a 
token.
  >
  > I'd say that, except for `content:' '`, all the listed properties could be 
defined using tokens or composite tokens, in case the creation of an alias is 
not justified.
  
  For the colors it's absolutely necessary to provide them as tokens, as 
themeability might be negatively impacted. For functionality like certain 
accessibility features, we might remain with a more static token 
implementation. Theming should and will be limited to a certain extent to not 
negatively impact users of the library.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, Invadibot, 
caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, 
JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, 
Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Sarai-WMDE]

Sarai-WMDE added a comment.


  Sorry about the late response! Here are my thoughts:
  
  > [...] but perhaps it would be more accurate to say that we will try to 
expand WikimediaUI base with more tokens that come from design decisions and 
can be used by components, but that we will keep single-component variables 
separate.
  
  That would be ideal. I have to say that I'm not familiar with how 
single-use/component-specific variables are used in OOUI. I'm only aware of how 
they're intended to "document" exceptions (aka used instead of missing aliases) 
in WVUI components. What's for sure is that, if there's anything that tokens 
can help with, that's theming.
  
  Let my clarify the following sentence, just in case:
  
  > I would encourage the DST to prevent the creation of said single "component 
tokens" as much as possible.
  
  Being more direct, this simply means that the detection of a missing alias 
should encourage the DST to reconsider whether a new alias token needs to be 
created, instead of directly triggering the introduction of an exception.
  
  Also, for extra clarification (I'm sure you already know this, Anne): In the 
context of WiKit (an many other design systems), component tokens are part of 
the token solution. They're the highest level of abstraction, and capture 
design decisions in their final context (+ have some other technical benefits, 
like allowing the introduction of style updates without resulting in breaking 
changes). I know they received push-back, but they are such common practice 
that I hope we'll still be able to consider their benefits.
  
  > All in all, I think I will be able to best understand this whole process 
once we start experimenting with it! I hope we can do this within the shared 
library as soon as possible.
  
  Definitely! Can't wait to understand all the requirements better and provide 
all possible support to materialize a solution.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Sarai-WMDE
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, Invadibot, 
caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, 
JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, 
Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[AnneT]

AnneT added a comment.


  Thank you, @Sarai-WMDE, for your thorough response! It's really helpful to 
learn from your experience with design tokens in WiKit so far.
  
  I have some remaining questions/thoughts about one topic, but everything else 
seems clear to me.
  
  > This all sounds about right, but I would encourage the DST to prevent the 
creation of said single "component tokens" as much as possible. Meaning: 
Wikimedia UI base (or whichever token solution is built from it, T288383 
) should ideally anticipate and 
provide an exhaustive and organized list of the available, premade design 
decisions that communicate intent and can be used with as many components as 
possible, all in order to centralize and propagate the system's source of truth.
  
  This makes sense, although it's something I didn't fully understand about the 
design token architecture proposal until now. Single-component-specific 
variables are used widely in OOUI and WVUI in the name of theming (something 
that actually exists in OOUI, and could potentially exist in WVUI). I was 
thinking the design token architecture would apply to these variables, too, but 
perhaps it would be more accurate to say that we will try to expand WikimediaUI 
base with more tokens that come from design decisions and can be used by 
components, but that we will keep single-component variables separate.
  
  All in all, I think I will be able to best understand this whole process once 
we start experimenting with it! I hope we can do this within the shared library 
as soon as possible.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: AnneT
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, Invadibot, 
caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, 
JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, 
Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E updated the task description.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, Invadibot, 
caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, 
JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, 
Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Sarai-WMDE]

Sarai-WMDE added a comment.


  Thank you so much for collecting all those valid thoughts here, @AnneT 
  Adding my two cents to each one of your points, based on our experience with 
WiKit, and trying to keep in mind the new context:
  
  **Designer-developer hand off**
  
  Although I'd say this is still up for validation with the UX teams, designers 
should ideally be able to use tokens as values for specification. This means 
that they should select (e.g., from a visualization in Storybook) and document 
(in Figma) the tokens that apply to each individual property of the component 
that they are designing, in preparation for handover. Designers and developers 
should meet to validate and, if needed, complete said specifications together. 
For this to be possible, an exhaustive set of predefined design decisions 
should be made available early on. That first batch of tokens should document 
all known stylistic values (e.g. available border colors, background colors, 
heights, border-radius, etc.), and it might be subject to change (additions, 
modification, deletions) as the system evolves.
  
  **Where do component-specific tokens live? + Token visualization**
  
  I'm glad you're considering a monorepo setup. I know this would be encouraged 
by the developers involved in the creation of our design system. As you 
mention, this would reduce inefficiencies and provide better access to the 
design tokens (whichever their format) during implemention, also allow their 
visualization in Storybook, which is convenient.
  
  Also adding some inline responses to your last comment:
  
  In T266688#7267420 , 
@AnneT wrote:
  
  > Another practical question: when does a value become a design token?
  
  This should primarily be a design decision. Tokens are used to document and 
propagate predefined system styles. Detecting which those styles are, naming 
and organizing/grouping them, should be the responsibility of the system 
designer(s).
  
  > This is the process I've been following:
  >
  > 1. Is it a simple keyword, like `display: flex`? If so, probably don't use 
a token, unless it's something that gets repeated a lot like the value of 
`cursor: disabled`
  
  
  
  1. This matches our approach. We originally "over documented" styles, and 
ended up having to remove tokens that did not represent a design decision, but 
only translated a choice among default CSS values. Curiously enough, we 
actually got rid of cursor tokens!
  
  > 2. Is it a simple value, like `width: 100%` or `margin: 0`? If so, probably 
don't use a token
  
  
  
  2. Agreed, although we did document `width: 100%` as "full-width", a token 
that applies to all our block-elements by default. We also work with 50% and 
200% (width-double), but I can see why this might not be necessary. Maybe it 
might be worth agreeing  on the definition of "simple value". One of its 
characteristics might be the fact that it doesn't belong to a scale.
  
  > 3. Is there an existing token in Wikimedia UI base whose name makes 
semantic sense for this component-specific use? e.g. `border-color: 
@border-color-base`? If so, just use the Wikimedia UI base token
  > 4. Is there an existing token in Wikimedia UI base but the name doesn't 
make semantic sense for this component-specific use, like `background-color: 
@color-primary--active` or `border-color: @wmui-color-base20`? If so, create a 
new component-specific token
  > 5. If none of these things are true, create a new component-specific token
  
  This all sounds about right, but I would encourage the DST to prevent the 
creation of said single "component tokens" as much as possible. Meaning: 
Wikimedia UI base (or whichever token solution is built from it, T288383 
) should ideally anticipate and 
provide an exhaustive and organized list of the available, premade design 
decisions that communicate intent and can be used with as many components as 
possible, all in order to centralize and propagate the system's source of truth.
  
  For example, looking at`margin-right: 
@margin-end-typeahead-suggestion-thumb;`, I assume that this component level 
token had to be created because there's no record of all the predefined system 
spacing values. In the context of WiKit, we'd select one of the reusable alias 
tokens from the spacing scale (e.g. `$dimension-spacing-medium`) to define the 
value of our component-level token (which we'd later use as the final styling 
value).
  
  > There's a lot of gray area in here, though, especially step 2. I looked 
through some WVUI components I've built and found some examples of values for 
which I did not create a token:
  >
  > - `outline: 1px solid transparent`
  > - `content: ' '`
  > - `top: 50%`
  > - `border: @border-width-base @border-style-base transparent`
  > - `transition: background-color @transition-base, border-color 
@transition-base, border-width @transition-bas

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E updated the task description.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, Invadibot, 
caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, 
JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, 
Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E updated the task description.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, Invadibot, 
caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, 
JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, 
Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E added a parent task: T288383: Decide on design tokens architecture for 
Wikimedia Design System and its shared component library.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, Invadibot, 
caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, 
JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, 
Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[AnneT]

AnneT added a comment.


  Another practical question: when does a variable become a design token? This 
is the process I've been following:
  
  1. Is it a simple keyword, like `display: flex`? If so, probably don't use a 
token, unless it's something that gets repeated a lot like the value of 
`cursor: disabled`
  2. Is it a simple value, like `width: 100%` or `margin: 0`? If so, probably 
don't use a token
  3. Is there an existing token in Wikimedia UI base whose name makes semantic 
sense for this component-specific use? e.g. `border-color: @border-color-base`? 
If so, just use the Wikimedia UI base token
  4. Is there an existing token in Wikimedia UI base but the name doesn't make 
semantic sense for this component-specific use, like `background-color: 
@color-primary--active` or `border-color: @wmui-color-base20`? If so, create a 
new component-specific token
  5. If none of these things are true, create a new component-specific token
  
  There's a lot of gray area in here, though, especially step 2. I looked 
through some WVUI components I've built and found some examples of values for 
which I did not create a token:
  
  - `outline: 1px solid transparent`
  - `content: ' '`
  - `top: 50%`
  - `border: @border-width-base @border-style-base transparent`
  - `transition: background-color @transition-base, border-color 
@transition-base, border-width @transition-base;`
  
  Those could all be debatable. The goal would be to take the debate out of it 
as much as possible with clear instructions on when one should create a token.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: AnneT
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, Invadibot, 
caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, 
JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, 
Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[AnneT]

AnneT added subscribers: Tonina_Zhelyazkova_WMDE, Catrope, egardner.
AnneT added a comment.


  Some thoughts post-Designer summit:
  
  Designer-developer handoff
  --
  
  This could use stronger definition. Is the designer creating tokens for some 
values in Figma? Will the designer and developer meet to discuss which tokens 
will likely be needed? Or will this happen during the development process? I 
ask because during our experimental WVUI development, we would identify 
component-specific tokens that were needed while building the component, since 
these values sometimes depend on the template and stylesheet structure (e.g. 
will it be a margin-left or a margin-right?) It's hard to imagine being able to 
accurately identify and name all tokens solely based on the design.
  
  Where do component-specific tokens live?
  
  
  Initially I thought they should live along with the component code in the 
shared library, but @Tonina_Zhelyazkova_WMDE brought up an excellent point that 
tokens should be technology-agnostic (e.g. what if someone needs the token and 
is building in OOUI rather than Vue?) So, they should probably live along with 
the base tokens in Wikimedia UI Base. However, if we have to add or update a 
token during development in the shared component library, we would have to 
update a separate repository, create a new release, then consume that new 
release. We have been following this process in WVUI development so far and it 
is quite inefficient. I would propose we consider a monorepo setup that 
includes the shared component library and WikimediaUI Base as separate but 
related exports to resolve this inefficiency.
  
  Token visualization
  ---
  
  From the development side, easy access to tokens during development is 
important. Right now, I have to open the Wikimedia UI Base file somewhere 
separate from where I'm working, which is inconvenient. I would propose doing 
something similar to what WMDE has done in WiKit to visualize design tokens 
within Storybook (which would be possible if we did the monorepo setup 
mentioned above).

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: AnneT
Cc: egardner, Catrope, Tonina_Zhelyazkova_WMDE, Jakob_WMDE, Michael, AnneT, 
Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, Invadibot, 
caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, 
GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, 
JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, Lydia_Pintscher, 
Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E updated the task description.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: Jakob_WMDE, Michael, AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, 
Aklapper, Volker_E, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, 
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, 
_jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E updated the task description.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: Jakob_WMDE, Michael, AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, 
Aklapper, Volker_E, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, 
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, 
_jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E closed subtask T277616: Clarify technical choice with product team 
needs for design tokens/variables as "Resolved".

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: Jakob_WMDE, Michael, AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, 
Aklapper, Volker_E, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, 
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, 
_jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E added a comment.


  A counter-point to my conviction, from Adobe Spectrum 
:
  
  > Use component-specific tokens for their respective component
  >  When building Spectrum verified components, use component-specific tokens. 
This ensures that as a component’s design evolves, you won’t have to retrace 
any higher-level design decisions that informed the updates. It’s not 
recommended to use component-specific tokens interchangeably with other 
components, unless one is derivative of the other.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: Jakob_WMDE, Michael, AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, 
Aklapper, Volker_E, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, 
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, 
_jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E updated the task description.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: Jakob_WMDE, Michael, AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, 
Aklapper, Volker_E, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, 
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, 
_jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E updated the task description.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: Jakob_WMDE, Michael, AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, 
Aklapper, Volker_E, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, 
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, 
_jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[AnneT]

AnneT added a comment.


  Quick comment that's probably obvious, but from a developer standpoint, one 
thing I would prioritize is ease of use/visibility during development. Two 
concerns:
  
  - In MediaWiki extensions, we use a pretty manual process to include and 
update Wikimedia UI base, which must be set up per-extension
  - In WVUI (and any codebase that properly uses Wikimedia UI base as an npm 
module), it's easy to include and update the library, but difficult to view it. 
I have to open up the variable sheet elsewhere, or dig into node_modules

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: AnneT
Cc: Jakob_WMDE, Michael, AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, 
Aklapper, Volker_E, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, 
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, 
_jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Sarai-WMDE]

Sarai-WMDE added a comment.


  Considering the above recommendation:
  
  > Therefore I'd strongly recommend to go a CSS way of implementation. From 
general to specific: Use aliased base variables when applicable and only define 
component-level tokens when specifically needed.
  
  
  
  - What would be the granularity of "component-level" implied by this 
approach? Are these single-use variables or are they shared by a component 
category (e.g. input, button)? If the former: Would they be documented in 
Wikimedia-ui-base too? In which cases would they be preferred to global/base 
variables?
  
  And following up on what's probably implied by:
  
  > Other action points are tackling shortcomings from above for Foundation 
side.
  
  We could have an exchange on our individual teams' experiences with component 
specification. It would be interesting to hear from WMF:
  
  - How easy and convenient is it (or does it sound) to use Wikimedia UI base 
variables  
as values for specification? What's the "coverage", in terms of styles, that 
the file offers (can they always find the values they are looking for)? And how 
do they expect for variables to be modified, added or removed? Is the source 
code a suitable source of spec values, or would they appreciate some sort of 
preview?

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Sarai-WMDE
Cc: Jakob_WMDE, Michael, AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, 
Aklapper, Volker_E, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, 
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, 
_jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Sarai-WMDE]

Sarai-WMDE updated the task description.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Sarai-WMDE
Cc: Jakob_WMDE, Michael, AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, 
Aklapper, Volker_E, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, 
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, 
_jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[Volker_E]

Volker_E added a parent task: T287538: Identify Design System hurdles & 
blockers and resolve open questions.

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Volker_E
Cc: Jakob_WMDE, Michael, AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, 
Aklapper, Volker_E, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, 
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, 
_jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org

[Wikidata-bugs] [Maniphest] T266688: Evaluate variables aka tokens abstraction

[AnneT]

AnneT renamed this task from "Evaluate (and implement) variables aka tokens 
abstraction" to "Evaluate variables aka tokens abstraction".

TASK DETAIL
  https://phabricator.wikimedia.org/T266688

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: AnneT
Cc: Jakob_WMDE, Michael, AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, 
Aklapper, Volker_E, Invadibot, caldera, maantietaja, Akuckartz, DannyS712, 
Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, 
_jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, Wikidata-bugs, aude, 
Lydia_Pintscher, Mbch331, Jay8g
___
Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org
To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org