Page MenuHomePhabricator

[EPIC] Translation Suggestions for New Editors
Closed, ResolvedPublic

Description

Description

This epic aims to capture the effort towards enhancing the Content Translation experience on the unified dashboard for new editors by prioritizing and presenting translation suggestions in a meaningful way.
By guiding new editors towards manageable and impactful translation tasks, the intention is to improve their initial success, contribute to higher-quality translated articles, and increase their survival rates.


1st Iteration
Q1: build & enablement2.1.2 hypothesis: If we developed and released translation suggestions tailored for new editors, we would then be able to test whether this approach produces better translation outcomes compared to our current approach. This addresses the known challenges faced by new editors, who have a higher probability of article deletion. By pointing them towards translating more manageable content, the goal is to provide a less overwhelming and more accessible introduction to the translation process. Good article and section candidates could look like limited complexity in terms of formatting and overall length.
Q2: measurement & impact2.1.9 hypothesis: If we presented translation suggestions suitable for new editors, then we would observe an improved average article quality score of X in their translated articles.

Technical:
We will achieve this by subjecting the article and section recommendations to a ranking based on a set of defined criteria.

  • A key factor in selecting these criteria for the initial iteration will be the ease of fetching and implementation complexity for each factor.
  • These criteria will be used to generate a score OR a weighted rank for each translation suggestion.
Experience criteria:
i)New editors (as defined on MediaWiki)Level 0: 0 edits for X days [newcomer]. These users require the most "easy suggestions".
Level 1: 10 edits and account created at least 4 days ago [learner].
Content criteria:
i)Articles:2000-3000 kBs for article suggestions; by default this excludes stubs
ii)Sections:Estimated time or another proxy for section suggestions

UX & Design:
-The UX and Design approach will focus on presenting these suggestions intuitively and providing targeted support for new editors.
1.Choice Guidance (ideas):
-Clear visual indicators to highlight suggestions that meet the "easy pieces of content" criteria for new editors, similar to T360570.
-2nd-level guidance on individual sections when expanding section suggestions.
-Tag newcomer-friendly content that are also part of existing collections.
-Swapping the default order of section suggestions with full article suggestions.

Testing:
-First iterations (Q1-2) will focus on testing these interventions on all wikis to validate the technical content criteria approach and guide future refinements.


Future Iterations

Additional Content Criteria:
1.Lead sections (giving higher priority to these sections over other sections where available)
2.Presence of Images (at least one image)
3.Presence of References (at least 4 references)
4.Number of templates (lower template count)
5.Maintenance templates (filter out content displaying critical maintenance templates)
6.Good, Featured article tags (these articles are typically too long for new editors)
7.High translation demand (page views/ high reader interest)
8.Presence of wikilinks (potential challenge of ensuring corresponding target articles exist)

Testing Approach:
-Future iterations (Q3-4) could benefit from an A/B testing approach to gauge which interventions have the most positive effect on translations published by new editors.

Feature Guidance:
a) Enhance the existing Tooltips, Contextual feedback messages, Step-by-step guidance, etc, within the translation editor.

Event Timeline

PWaigi-WMF renamed this task from [Epic] Translation Suggestions for New Editors to [EPIC] Translation Suggestions for New Editors.Jun 3 2025, 11:02 AM
PWaigi-WMF added a project: OKR-Work.
PWaigi-WMF updated the task description. (Show Details)
SBisson changed the task status from Open to In Progress.Oct 24 2025, 6:52 PM
SBisson moved this task from Backlog to Product Signoff on the LPL Hypothesis board.

I think this is all done

Nikerabbit removed a project: LPL Hypothesis.
Nikerabbit subscribed.

I think Epics shouldn't be on sprint boards.