[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Page MenuHomePhabricator

[EPIC] Improve language switching capabilities
Closed, ResolvedPublic

Description

Background

Currently, language links are found at the bottom of the sidebar for many wikis. We would like to give the language switcher a more prominent position within the interface in order to make language switching easier. This epic will track the development of this work, as well as its deployment to our test wikis

Requirements

  1. There will be a button on the top of the page
  2. Selecting the button will open the list of languages
  3. The list will contain the following:
    • suggested languages
    • a full list of all available languages
    • display settings
    • input settings
  4. The original list will NOT appear on the sidebar
  5. We will be able to track when a user switches from one language to another
  6. We will be able to A/B test the frequency of language switching in the control version (current interface) and the test version (button interface). It would be preferable if we can do the test on all users, although only logged-in users will be acceptable as well
  7. Button location will require changes to the header of the page and moving current article indicators as per design guidelines
  8. We will have a non-JS fallback which will display the full list of all languages

Acceptance criteria

  • Finalize design and product requirements
  • Develop feature based on the above and user testing results
  • Deploy to all test wikis

Open questions

  • What about keyboard support?

Related Objects

StatusSubtypeAssignedTask
Resolvedovasileva
Resolvedovasileva
Resolvedovasileva
Resolved alexhollender_WMF
Resolved alexhollender_WMF
Resolvedovasileva
Resolvedovasileva
Resolvedovasileva
ResolvedSpikeovasileva
ResolvedBUG REPORTNone
Resolvedovasileva
Resolved alexhollender_WMF
ResolvedPginer-WMF
ResolvedBUG REPORTJdlrobson
ResolvedEdtadros
Resolvedovasileva
Resolvedovasileva
Resolved nray
Resolvedovasileva
ResolvedJdrewniak
Resolvedovasileva
Resolvedphuedx
Resolvedovasileva
Resolvedovasileva
DuplicateNone
Resolvedovasileva
Resolvedovasileva
Declinedovasileva
Resolvedovasileva
Resolvedovasileva
ResolvedEdtadros
ResolvedEdtadros
ResolvedNone
ResolvedBUG REPORTTheklan
Resolvedovasileva
Resolvedovasileva
ResolvedSpikeJdrewniak
OpenSpikeNone
Resolvedjwang
Resolvedjwang
Resolvedovasileva
ResolvedNone
Resolvedjwang
Resolvedovasileva
ResolvedJdlrobson
DuplicateNone
Openovasileva
Resolvedovasileva
Resolvedjwang
Resolvedcjming
Duplicateovasileva
DuplicateNone
DeclinedKrinkle
ResolvedNone
DeclinedJdrewniak
OpenNone
Resolvedovasileva
OpenJScherer-WMF
Resolvedabi_
ResolvedPRODUCTION ERRORabi_

Event Timeline

ovasileva renamed this task from [EPIC] Improvve language switching capabilities to [EPIC] Improve language switching capabilities.Jun 22 2020, 4:26 PM
ovasileva triaged this task as Medium priority.
ovasileva added a subscriber: alexhollender_WMF.

@alexhollender Inspirational examples (implemented in the dropdown menu patch):

300px600px900px1500px
language-selector-300px.png (178×266 px, 16 KB)
language-selector-600px.png (156×571 px, 23 KB)
language-selector-900px.png (109×881 px, 33 KB)
language-selector-1500px.png (113×1 px, 29 KB)
ovasileva raised the priority of this task from Medium to High.Oct 22 2020, 1:18 PM
ovasileva updated the task description. (Show Details)
ovasileva updated the task description. (Show Details)

@ovasileva the remaining open sub-tasks are T262472, T269093, and T278372. Do we need to resolve all 3 of these to close out this ticket? Are there others that need to be added as sub-tasks to complete this goal e.g. completing the A/B test?

@ovasileva the remaining open sub-tasks are T262472, T269093, and T278372. Do we need to resolve all 3 of these to close out this ticket? Are there others that need to be added as sub-tasks to complete this goal e.g. completing the A/B test?

Current blocker is T286932, now on subtasks list officially. The remainder can be completed separately after the epic is closed

I wonder why there's this mentioned in the 7th point: Button location will require changes to the header of the page and moving current article indicators as per design guidelines. Where can I find those design guidelines?