Page MenuHomePhabricator

Make Timeless the default skin for translatewiki.net
Open, Needs TriagePublic

Description

Reasons for switching:

  • Responsive design, works better on mobile devices
  • The proposer likes it
  • It aligns better with the color scheme of our logo
  • Most glitches appearing with Timeless have been fixed
  • Google search complains that our site is not mobile friendly, probably also demotes our listings

Manually set skin preferences would not change, and Vector would still be available as a choice.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 19 2020, 8:39 AM
abi_ added a subscriber: abi_.Mar 19 2020, 8:40 AM
Nikerabbit updated the task description. (Show Details)Mar 19 2020, 8:41 AM
Nikerabbit updated the task description. (Show Details)Apr 20 2020, 11:30 AM

I agree this is probably the easiest and most efficient way to make the website suitable for mobile devices.

But is Special:Translate itself usable in Timeless on a phone? Did we get some testing on that? Do we have some statistics on how many active translators have chosen Timeless as their skin and can we maybe ask for their opinion?

Before such a switch, we would need to determine how we're going to check any negative side effect, how many translators are getting lost in the new skin for whatever reason, etc. It's not always easy to communicate with our very diverse community of translators. At a minimum, keep track of how the activity statistics evolve? But I'm not sure that's a reliable indicator of user (non) frustration.

But is Special:Translate itself usable in Timeless on a phone? Did we get some testing on that? Do we have some statistics on how many active translators have chosen Timeless as their skin and can we maybe ask for their opinion?

It works better, because sidebar gets automatically collapsed. On the smallest screen sizes, the translation editor is not usable.

https://translatewiki.net/wiki/Special:UserOptionStats/skin

Before such a switch, we would need to determine how we're going to check any negative side effect, how many translators are getting lost in the new skin for whatever reason, etc. It's not always easy to communicate with our very diverse community of translators. At a minimum, keep track of how the activity statistics evolve? But I'm not sure that's a reliable indicator of user (non) frustration.

I'm gathering feedback before (and after if it's positive) the change is made.