As a volunteer technical contributor, I'd like to understand which recommended technologies I should use and which ones are legacy.
* https://www.mediawiki.org/wiki/Vue.js ~~says it's "being evaluated" but~~ T241180 implies that evaluation was finished a year ago.
* https://www.mediawiki.org/wiki/Vue.js/OOUI_migration_guide exists ~~and does not mention Codex~~.
** https://www.mediawiki.org/wiki/Vue.js/OOUI_migration_guide and https://www.mediawiki.org/wiki/Vue.js don't link to #Vue.js and #vue.js_migration and #wvui; what's the relation of technical docs on-wiki and technical tasks on-Phab?
[x] Mentions [[ https://www.mediawiki.org/w/index.php?title=Vue.js/OOUI_migration_guide&type=revision&diff=5203711&oldid=4693670&diffmode=visual | Codex now ]]
* #WVUI at https://phabricator.wikimedia.org/project/profile/4898/ states that "we transition away from OOUI". See also T290051.
* However, https://www.mediawiki.org/wiki/OOUI and https://phabricator.wikimedia.org/project/profile/697/ do not mention "Vue".
* Scope of Phab project tags feels unclear - when to [not] use #Vue.js versus #Vue.js_Migration (Vue.js_Migration subproject) (versus #WVUI), vs #Codex? Please clarify the Phabricator project descriptions to shed more light on this.
** Status 2022-05-09: All above mentioned tags have been updated with clearer pointers to #Codex and scope.
* https://design.wikimedia.org/style-guide/resources.html mentions OOUI. Should it [also] mention Vue or describe future plans?
** Status 2022-05-09 Yes, it should. And it will. As soon as we've built out #Codex with more components and nearing first real public release, we'll update the DSG as well with links to it.