The Language-Team plans for this fiscal year include work in the areas described below.

1. Growing small wikis with translation

Millions of speakers of less supported languages have limited access to knowledge. They have access to few articles with little coverage.

We want to help small wikis grow by:

• Encouraging the use of ContentTranslation to create new articles on desktop.
• Support the translation of new sections on mobile and desktop to expand existing articles anytime.

Check CX-boost for more details.

Key interventions and rough schedule

Q1 (Jul-Aug-Sep):
Learn about needs and explore potential solutions:

• T225300: Start conversation with selected communities with potential to grow with translation
• T225498: User research about small wikis, section translation and mobile translation
• T225301: Design and prototype cross-wiki propagation concepts
• T225493: Technical explorations for section translation and mobile

Attract more people to translate on desktop:

• T225302: Enable Content Translation in selected small Wikipedias as a default tool
• T217322: Allow anonymous users to translate
• More visible entry points (T216500, T216500)
• More proactive communication with notifications
• Surface better the content gap (T113257, T188634, T213420)
• Compensate for lower-quality MT support (T96165)
• T226171: Dashboard 2019-20 annual plan metrics for the Language team

Q2 (Oct-Nov-Dec):
Transfer sections to existing articles on desktop
Support basic translation on mobile

Q3 (Jan-Feb-Mar):
Transfer sections to existing articles on mobile
Transfer articles on mobile

Q4 (Apr-May-Jun):
Expand the basic capabilities to find and translate types of content.

Metrics and impact

Increase the size of the community of translators and the content created/expanded by them in small wikis:

• Increase the percentage of new editors that completed their second translation in a month.
• Double the number of weekly translations on selected wikis (to create new content or extend existing one).

2. Comfortable creation of multilingual content

We want content such as project documentation, policies, campaigns, reports, and other types of documentation to be available in all languages, but currently making content multilingual makes it hard to work with it. The Translate extension (MediaWiki-extensions-Translate) helps with the translation process, but it also adds complexity that discourages users from creating multilingual content.

Key interventions and rough schedule

Q1 (Jul-Aug-Sep):
Learn about the needs of other Wikimedia Foundation teams
Translation project management workflows

Q2 (Oct-Nov-Dec):
Support communication and coordination with translators
Reusable language metadata

Q3 (Jan-Feb-Mar):
Support the parsing changes
Improve translation quality (1/2)

Q4 (Apr-May-Jun):
Improve translation quality (2/2)
Visual editing support of translatable content (Research & Designs)