Sarai-WMDE added a comment.
The WMDE team involved in the conception of our design system already provided an overview of the benefits attached to the use of JSON tokens in the context of WiKit a while ago in this presentation <https://docs.google.com/presentation/d/1Oze04iKqgBhk9cVgWL_mTkwyPAgFskHApEisa6mpIiI/edit>. Now this document <https://docs.google.com/document/d/1KWhQ1Fi951fRCZnnZb85_bYrKdehTl29Et_rEP4kGPY/edit#bookmark=id.xacrlpjnf5js> tries to also collect the drawbacks of our current solution. JSON tokens were originally adopted by our team because they represented the most theoretically ideal solution in the market (e.g. Salesforce <https://www.lightningdesignsystem.com/design-tokens/>, Adobe <https://spectrum.adobe.com/page/design-tokens/>). We wanted to try whether this stictly agnostic and scalable approach would work in our scenario. So far, we’ve been able to use JSON tokens organized in three levels of abstraction to embed design decisions in our components, since they didn’t present any critical limitations in our workflow. But the set-up, of course, doesn’t come without some downsides (majorly related to the use of component-level tokens, as described by the document). We agree that there’s room for improvement, and we'd be keen to collaborate to get there through exploration, in order to come up with the most convenient solution in the specific context of WVUI. TASK DETAIL https://phabricator.wikimedia.org/T266688 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Sarai-WMDE Cc: AnneT, Pginer-WMF, raja_wmde, ItamarWMDE, Sarai-WMDE, Aklapper, Volker_E, caldera, maantietaja, Akuckartz, DannyS712, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Iniquity, _jensen, rosalieper, JGirault, Scott_WUaS, Niedzielski, abian, Wikidata-bugs, aude, Prtksxna, Lydia_Pintscher, Mbch331, Jay8g
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
