We want to try different approaches to bring more users into the translation process. In order to do so, after prioritising the different ideas in T87867, we decided to prototype the following ideas (high priorities are marked as [hi]):
T89701: Ask users to try the ContentTranslation beta feature when creating an article (Already designed and implemented)
- Scope: When visiting an article that is missing in a language I know, I'm told that I can translate it and I'm suggested to enable the CX beta feature. I can enable the beta feature with just one click.
- Expected impact: Increase the numbers of activations of the beta feature.
- Scope: After enabling the beta feature I'm introduced to the "contributions" entry point. So that I can follow the process of creating an article.
- Expected impact: By helping users to associate the contributions as a place to create new contributions, we expect users to start more translations.
- Scope: Provide direct access to the translation action.
- Expected impact: By making more fluent the access to the translation dashboard, users will easilly find the way to start more translations.
- Scope: some suggestions are presented to the user when reaching the dashboard.
- Expected impact: Increase in the number of translations per user.
- Scope: Some kind of affordance that allows users to ask others (specific users or in general) for an article to be translated into a language.
- Expected impact: spread the word about CX (more translators).
- Scope: Simulate a notification to communicate that an article you created has been translated by user Ludmilla into another language.
- Scope: Ask the user to consider translating an article instead. We probably should assume that we don't know what the article is about or there is uncertainty about it (not matching search in Wikidata). so the message should be along the lines of informing about the possibility in general ("now you can create articles also by translating." instead of "This article seem to be missing in German, do you want to translate it?")
- Expected impact: By intersecting on the regular article creation process, we expect to turn more editors into translators (increase on users that translated).
- Scope: Simulate a notification about an article being featured to understand if the user (a ) understands why is getting the notification, and (b) finds notifications of this kind useful.
- Expected impact: More high quality articles being created.