Page MenuHomePhabricator

StarterKit Essential Tasks: Translate core interface messages
Closed, ResolvedPublic

Description

Overview

As part of the Essential Tasks block in the Starter Kit Dashboard, we need to implement a card that provides guidance and support for translating core interface messages via Translatewiki.net. This helps ensure that the wiki interface is properly localized for the user’s language.

Interactive prototype: Link

Screenshot

image.png (520×438 px, 37 KB)

User journey

  1. Account check. The app asks whether the user has a Translatewiki.net account. If yes, they proceed. If not, the app guides them through registration and waits for confirmation before continuing.
  2. Open. The app opens Translatewiki.net preloaded with the MediaWiki core message group, filtered by the user’s language and sorted by most-used messages.
  3. Translate. The user translates messages in Translatewiki.net. The app tracks progress and unlocks completion after 10 messages. Translations are automatically synced to the wiki within 24 hours; no manual publishing is required.

Card implementation details

Category: Editing
Tool: Translatewiki.net
Difficulty: Beginner

Details

Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
Feat: add "Translate core interface messages" essential taskrepos/lpl/starterkit-v1!62ngkountasfeat/twn-essential-taskmain
Customize query in GitLab

Event Timeline

MaryMunyoki raised the priority of this task from Medium to High.Apr 28 2026, 11:42 AM

Ideally, there should be a way to automatically detect how many messages the user has translated. If that were possible, we could simplify this into two steps and remove the need for the third step where users manually count their progress.

In the future, it would be worth thinking about how we handle tasks that involve repeated actions such as translating multiple articles, multiple messages, or creating multiple articles. We may need to consider whether to allow users to repeat the same action within a single task (e.g., translate multiple messages in one flow), or instead create separate task instances for each action.

The design may also need to be adjusted based on what is technically feasible, for example, whether it is possible to pull a list of untranslated messages from Translatewiki and also detect whether the suggested messages have been translated.

If it is possible to detect changes automatically, we can have a revised and simplified design. Link here. Based on what is technically feasible or not, we can improve the design further.

Based on the discussion on another task (gadget-related T422481), one additional thought for consistency is to keep the implementation simple and the user flow straightforward by removing auto-detection entirely.

Also, the list of messages we currently show isn’t very usable, since users can’t directly land on a specific message on Translatewiki from the starter kit tool anyway.

With that in mind, I’ve revised the prototype - you can find it here.