Page MenuHomePhabricator

Design: adding a Translation task to the Newcomer Homepage
Closed, ResolvedPublic

Description

As the Growth team Product Manager, I want to understand how we can integrate Section Translation or Content Translation into the Newcomer Homepage in a logical and low-effort way.

Background
The Growth team has been working on Structured Tasks as a way to help onboard newcomers, onboard new types of editors, and create edit opportunities that work well on mobile. Adding a Translation suggested edit or a Translation CTA from the newcomer homepage fits within all of our main goals, and could be fairly low effort.

Requirements

  • Newcomers can access Section Translation or Content Translation from their Newcomer Homepage in some way. There is clear indication on the Newcomer homepage to help inform newcomers about the task. (Should we mirror the icon and language used on the new Contributions menu?)
  • For an initial MVP we can't pull in specific Content Translation tasks into the Suggested Edits feed, we could only add a generic Content Translation task and link.

Questions:
This task doesn't need to answer all of these questions, but here are some things we will need to consider as we start to design and plan for this:

  • Do we want to integrate Content Translation, or only Section Translation?
  • Should Translation be a task in Suggested Edits, or should we consider adding it to a separate module on the newcomer homepage?
    • If it's a task in Suggested Edits, then how do we decide when to display the task in the feed? What difficultly level task is it?
    • If it's a separate module: Is it simply a list of other "newcomer friendly" tasks configurable by wiki (or something similar), or a module only related to Translation?
  • Should we limit the task to multilingual users?
  • How can gather data on this? Will these edits get both a "ContentTranslation" tag and a "Newcomer task" tag?

Acceptance Criteria

  • Provide initial wireframes for how we might add a translation task into the newcomer homepage.

Designs

Figma file with initial wireframes. Explorations for an approach with a new module and an approach with a banner were provided.

Event Timeline

KStoller-WMF moved this task from Inbox to Upcoming Work on the Growth-Team board.

@Pginer-WMF - Just FYI, Growth hopes to start the discovery / initial design side of this soon.

@RHo - I'm not sure if you'll have capacity for this immediately, so I didn't pull it into the current sprint... but feel free to add more questions or details to the task description.

KStoller-WMF lowered the priority of this task from Medium to Low.Dec 22 2022, 11:24 PM

How can gather data on this? Will these edits get both a "ContentTranslation" tag and a "Newcomer task" tag?

We would need to modify the ContentTranslation software to ensure that "newcomer task" and e.g. "newcomer task: content translation" tags are added.

Should Translation be a task in Suggested Edits, or should we consider adding it to a separate module on the newcomer homepage?

Our existing feed is based on using Special:Search to articles matching the task types / topics. In this case, we need to find articles that don't exist on the local wiki that match the topics the user has selected. I think what we might want to do in that case is:

  • get the languages that the user is interested in translating from, with some upper bound (5?). We would probably need to add another UX element in the task types dialog to allow the user to update their language choices.
  • use the the RemoteSearchSuggester to make queries to the language wikis that user is interested in. E.g. if the user is on enwiki and selected Arabic as an additional language, then we'd do a search on arwiki for "hastopic:art". We'd then need to fold these results into the Suggested Edits feed; we currently have some code that validates that the article exists, so we would need to work around that.

How can gather data on this? Will these edits get both a "ContentTranslation" tag and a "Newcomer task" tag?

We would need to modify the ContentTranslation software to ensure that "newcomer task" and e.g. "newcomer task: content translation" tags are added.

IMO, we should only consider adding a "newcomer task: content translation" tag if we are integrating CX into the tasks module/workflow. If we are initially only looking to act as a 'source' or entry point for newcomers to go to CX/SX, then this is confusing to add to as a tag.

Should Translation be a task in Suggested Edits, or should we consider adding it to a separate module on the newcomer homepage?

Our existing feed is based on using Special:Search to articles matching the task types / topics. In this case, we need to find articles that don't exist on the local wiki that match the topics the user has selected. I think what we might want to do in that case is:

  • get the languages that the user is interested in translating from, with some upper bound (5?). We would probably need to add another UX element in the task types dialog to allow the user to update their language choices.
  • use the the RemoteSearchSuggester to make queries to the language wikis that user is interested in. E.g. if the user is on enwiki and selected Arabic as an additional language, then we'd do a search on arwiki for "hastopic:art". We'd then need to fold these results into the Suggested Edits feed; we currently have some code that validates that the article exists, so we would need to work around that.

Initially, I do not think we want to integrate into the Suggested edits feed as it is a lot of effort and would require more information from the user (about languages they can translate to/from) per @kostajh's notes above. Instead, to gauge initial interest from newcomers before developing further, the concepts I will design will be to show it as a separate module, or as a link/CTA from the Suggested edits module to CX.

@kostajh, on a related note: there is a ticket requesting an improved API to get recommendations for articles to translate in T293648: Content Translation Recommendations API. This includes new requirements to support the translation of sections, but feel free to comment in that ticket if there is any other aspect that can be include to facilitate the Growth usecases for translation.

KStoller-WMF raised the priority of this task from Low to Medium.Jan 12 2023, 10:14 PM

@kostajh, on a related note: there is a ticket requesting an improved API to get recommendations for articles to translate in T293648: Content Translation Recommendations API. This includes new requirements to support the translation of sections, but feel free to comment in that ticket if there is any other aspect that can be include to facilitate the Growth usecases for translation.

Ack, I'll have a look at that, thanks @Pginer-WMF.

I'll be closing this as resolved! I've wrapped up initial explorations / wireframes for this work. As soon as we decide to start engineering efforts for this I'm happy to revisit the designs and re-open this task if needed!