Convert all skins and extensions to OOUI.
Please see task for mw special pages at T107037
Convert all skins and extensions to OOUI.
Please see task for mw special pages at T107037
Could some of the subtasks be small enough to be (or split into) Google-Code-in-2018 tasks provided by Design folks, maybe? Anyone?
I've detached this from T100270: Replace use of jQuery UI and MW UI with OOUI across all Wikimedia-deployed extensions and core; that's "only" for core and the ~200 extensions and skins in Wikimedia production; this task covers all 2000 such items.
This should be Codex now, I guess? Could Design-System-Team provide some guidance on what to do with this task and its subtasks?
Given there's no like-for-like replacement yet from Codex, I think this is a premature judgement. That may be different for T100270: Replace use of jQuery UI and MW UI with OOUI across all Wikimedia-deployed extensions and core, however.
I'm generally not a fan of these evergreen tracking tasks, but if we're going to keep them around, I think it makes sense to consider using Codex for all these interfaces where possible. That said, Design-System-Team is not driving a large-scale Codex migration effort at this time, but we are happy to support anyone in that pursuit. With our recent work on CodexHTMLForm (T359011) and upcoming support for Codex markup generation in PHP (T373708), some of these migrations should be made easier.