MDN/Projects/Completed/Localization UX Improvements
The localization interface is cumbersome. Even it allows to translate pages and make them look them good, it needs a lot of non-needed work to reach this goal. Newbies need a lot of mentoring and most of them are quickly discouraged.
Performing simple tasks like editorial review is a pain.
As part of the plan to reach 1000 wiki editors / month in 2014, we need to make the use of the l10n interface much more easy, so that we stop loosing as many wannabe-translators. At the same time, it will increase their productivity and the quality of their work: more docs participates in the increase Firefox/Firefox OS marketshare company goals.
The increase in l10n community resulting in these better things will build over the months. To reach a number significant enough to allow us to reach the 1000 editors/month goal, we need this asap. Given we are in June and the amount of work to be done, we set a realistic deadline for September 30th, 2014. Past this deadline, fixing this bug won't have a significant impact to reach the goal we were given.
Goal
- Improve L10n contribution levels and retention rates by making the user experience less tedious.
- This will help us reach our 1,000 editors per month goal by boosting our contributions across multiple locales. We estimate we will gain approximately 5-7% of our new L10n editors through improved retention of users.
- Non-goal: Completely revamp the localization UX.
Risk
- Low. Even if it doesn't lead to improve the participation significantly, it will improve the productivity of current edits.
- It is a collection of bugs that can be done independently. Partially done is already useful.
Bugs
| Bug 776048 | Tags with diacritics and tags without diacritics are mixed. | P1 |
| This lead to erroneous tags spontaneously added to thousand of page. A simple orthographic mistake by a casual editor propagates very quickly to a lot of articles. Non-mistakes also lead to incorrect tags added.
This bug also shows blatantly that l10n is an afterthought and not a strong commitment. | ||
| Bug 777434 | Mechanism to hide the English text. | P1 |
| Translations happens in different phases, and in different ways. Some people copy the English text in the translated area and translate it. Similarly, some people are performing the editorial review of the translated text and do not need the English text.
More, in both these use cases, the display of the English text makes the translated area very small and make it very difficult to perform the task. A button (or other widget) to toggle the side display of the English original will solve both problem. | ||
User Stories
Localizer
- Make the interface convenient to use.
- While the side-by-side comparison of English and translated content is useful, the lost width makes editing difficult and makes it hard to judge what the content will actually look like. A solution needs to be found.
Notes
- There's a lot of low-hanging fruit, as well as some larger problems that need to be addressed.