Sarai-WMDE added a comment.
I have been wondering the same. From our conversations with product, and the outcome of the previous investigation, it seems that the initial route we're taking is the latter: no. In order to deliver this feature faster, we're building a custom component that will be replaced, together with all the other instances of the language selector, once the Codex solution is ready. My assumption was, too, that this approach would help answer the majority of the questions listed in the comment above <https://phabricator.wikimedia.org/T328148#8568487>. Nevertheless, I can't avoid thinking that we're missing an opportunity to create a reusable solution here. Something we won't have to 'throw away'. This route would, of course, take quite some more time from all fronts (design, organization, probably implementation): the component needs to be visually standardized, and we'd need to align both with the Design System Team and with the Language Team (to align on ownership, define the component characteristics and the scope of our initial implementation). I'm not the right person to say but, while I don't think a new collab sprint is necessary (I believe we can be autonomous), we'd definitely need to allocate time to coordinate and prepare. Which would pay off: this is a widely used core pattern. TASK DETAIL https://phabricator.wikimedia.org/T328148 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Sarai-WMDE Cc: Michael, karapayneWMDE, Sarai-WMDE, Aklapper, Arian_Bozorg, Astuthiodit_1, Invadibot, maantietaja, ItamarWMDE, Akuckartz, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Scott_WUaS, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
