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 <https://gerrit.wikimedia.org/r/plugins/gitiles/wikimedia-ui-base/> 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 -- [email protected] To unsubscribe send an email to [email protected]
