Page MenuHomePhabricator

Use Codex CSS components or OOUI form instead of mediawiki.ui in Translate
Open, MediumPublic

Description

Split off from parent T340263: Deprecate mediawiki.ui.button. Use Codex markup instead.

Checklist

Pages to transition:

QA

Event Timeline

Change 987877 had a related patch set uploaded (by VolkerE; author: Jdlrobson):

[mediawiki/extensions/Translate@master] [WIP] Migrate special pages to Codex from mediawiki ui

https://gerrit.wikimedia.org/r/987877

Volker_E renamed this task from Use Codex CSS components instead of mediawiki ui in Translate to Use Codex CSS components instead of mediawiki.ui in Translate.Jan 9 2024, 1:24 PM
Volker_E added a project: Design-System-Team.

Change 987877 abandoned by Jdlrobson:

[mediawiki/extensions/Translate@master] [WIP] Migrate special pages to Codex from mediawiki ui

Reason:

Abandoning in favor of https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Translate/+/976192

https://gerrit.wikimedia.org/r/987877

Jdlrobson renamed this task from Use Codex CSS components instead of mediawiki.ui in Translate to Use Codex CSS components or OOUI form instead of mediawiki.ui in Translate.Jan 11 2024, 9:10 PM
Jdlrobson updated the task description. (Show Details)

Language team: would it make sense to use OOUI as an intermediate state here for pages other than Special:PagePreparation, or jump directly to Codex (as you've begun on https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Translate/+/976192) ?

Depends on case by case. For simple pages OOUI/mw core thing provides smoothest migration path. Special:PagePreparation is a good learning opportunity and Special:Translate probably needs a full redesign for better mobile compatibility, so it's likely to happen last.