Translation UX

''This is a design documentation page of an ongoing project. Please leave your feedback on design proposals in their respective talk pages. You can participate by signing up at the bottom of the page''

The Extension:Translate can make mediawiki a powerful collaborative translation platform. It is currently deployed on translatewiki.net and is the central tool used to localize all wikimedia projects. Translatewiki.net currently maintains an active community of community translators making an extensive number of translations every day.

The UI for the extension has seen the addition of several features over the years but in an ad-hoc manner. The Translation UX improvement project will consist of evaluating the usability of the current extension and proposing a series of design improvements to enhance the experience of translating messages. Increasing the number of message translations has a direct bearing on making free knowledge more accessible to every human being on earth.

Project Timeline & Status

 * Apr 26: Start initial research - Arun
 * May 29: File:Ux-Translate user workflow design.pdf Documentation of user research, competitor analysis, usability issues, and workflow redesign guidelines
 * Jun 10 First team discussion on research document, fix focus areas for phase1:
 * New translator registration
 * Message search
 * Translation UI
 * Jul 18: /Wireframes A/ for translator registration, message search and translation UI - Pau
 * Jul 23: /Wireframes B/ for integrated message search + translation workflow - Arun
 * Jul 24: /Design feedback 1/
 * Aug 21: Started /Design feedback 2/
 * Sep 4: /Wireframes C/ for translation task list feature

Planned

 * Prototypes for initial user test
 * Project etherpad

Existing UX Issues

 * Many new users do not complete the user registration and rights requisition process, leading to lost translators
 * Searching translations is cumbersome and does not have sufficient filtering options
 * Hidden features and interactions in the translation editor interface (eg. keyboard shortcuts, inline editor)
 * Proofreading of translations is not seen as an important activity by translators
 * Confusing information architecture (Translate | Proofread | Message group statistics | Language statistics) are all on the same level of hierarchy
 * TWN Support page for translators
 * On LanguageStats: «I didn't realise the collapses could have several levels, nor that there was a button called "expand all"»
 * Pop-up vs. inline: one, two.

Design Considerations

 * Optimize translation process for keyboard-only operation and touch based interaction
 * Grandma friendly interface and workflow
 * Eliminate redundant interactions

Future Ideas

 * Design a chrome interface for translatewiki.net as a dedicated translation platform

Research Documentation

 * User research, competitor analysis, usability issues, and workflow redesign guidelines

Specifications

 * /Specification

Be a part of the design team!
Your participation and feedback helps to improve the proposed designs that would eventually go live. You can contribute by building a feature wishlist (on talk page), reviewing the proposed designs and documents (talk page of respective subpage), participating in user tests and even proposing your own designs here for peer review.

See Translation UX/Participate for more information

Project Coordinators

 * User:Aganesh (Localisation team) aganesh@wikimedia.org
 * User:Pginer (Localisation team) pginer@wikimedia.org