@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.

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.

In T321529#8515985, @kostajh wrote:

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.

In T321529#8516803, @Pginer-WMF wrote:

@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.