Background
Some wikis still have Vector legacy as the default skin. Maintaining two skins as a default experience makes shipping new features difficult (e.g. temporary accounts), and since nobody is actively testing on legacy Vector the risk of larger issues surfacing in the software is real.
User story
As a user I want a consistent express across all wikis
Requirements
- All wikis have Vector 2022 as the default skin (with special exceptions for Thank you, Nostalgia and donate)
- The Fundraising tech team acknowledge the risks of supporting Thank you and donate wiki
- This will be completed by June 2025
BDD
- For QA engineer to fill out
Test Steps
- For QA engineer to fill out
Design
- Add mockups and design requirements
Acceptance criteria
We will deploy in various batches:
These are the groups of wikis that currently use legacy Vector. The sequence of batches does not reflect the expected sequence of deployments and some of these deployments may be done together:
- romdwikimedia (T379765)
- azwiki, azwikimedia (T383942)
- ruwiki (T375046)
- ruwikimedia, arbcom_ruwiki (T390112)
- ukwiki, uawikimedia (T381041)
- enwiktionary, jawiktionary, svwiktionary (T379799)
- arbcom_dewiki, dewiki (T387155)
- arbcom_fiwiki, fiwiki, fiwikimedia (T384824)
- itwiki, sysop_itwiki (T379765)
- wikidatawiki (T387154)
- testwikidatawiki (T384824)
- commonswiki (T384824)
- enwikisource (T381041)
- cswiktionary (T381041)
- enwikivoyage (T379799)
- specieswiki (T379799)
- tewiki, kkwiki (T379799)
- elwiktionary (T384824)
Communication criteria - does this need an announcement or discussion?
- Add communication criteria
Rollback plan
- What is the rollback plan in production for this task if something goes wrong?
This task was created by Version 1.2.0 of the Web team task template using phabulous