Change 753439 had a related patch set uploaded (by Nik Gkountas; author: Nik Gkountas):

[mediawiki/extensions/ContentTranslation@master] SX Entrypoints: Add hook to register missinglanguages module

https://gerrit.wikimedia.org/r/753439

Change 757550 had a related patch set uploaded (by Nik Gkountas; author: Nik Gkountas):

[mediawiki/extensions/MobileFrontend@master] LanguageSearcher: Fire a hook when LanguageSearcher view is rendered

https://gerrit.wikimedia.org/r/757550

Change 757554 had a related patch set uploaded (by Nik Gkountas; author: Nik Gkountas):

[mediawiki/extensions/ContentTranslation@master] SX: Add missing languages entrypoint module

https://gerrit.wikimedia.org/r/757554

A general question about entrypoint: Usually when we add entry points, we make sure that we present translation as one of the option. We will provide an option to choose creating article from scratch(for example using VE). But in language selector entry point we are assuming translation is the only way to create that article. I agree that this context provides two languages to work on, that too frequently used language. So translation is valid way to create missing language. But why are we excluding other ways to create article?

In T298032#7655989, @santhosh wrote:

A general question about entrypoint: Usually when we add entry points, we make sure that we present translation as one of the option. We will provide an option to choose creating article from scratch(for example using VE). But in language selector entry point we are assuming translation is the only way to create that article. I agree that this context provides two languages to work on, that too frequently used language. So translation is valid way to create missing language. But why are we excluding other ways to create article?

In this particular context, the option to translate felt much more relevant compared to alternatives, so exposing other options seemed to result in more distraction/friction than value compared to providing just a shortcut for translation:

• In this context it seems much more likely that the user is multilingual, and therefore capable of doing a translation. Less risk of suggesting an invalid next step that needs fall-back alternatives.
• Data shows that articles created by translation are less likely to be deleted than when starting from scratch. So it makes sense to surface an option that makes them more equipped for success.
• User research shows that a common starting point of the translation process is to check the availability of the article in the given language. So it is a natural starting point for a multi-step process for which we can provide a shortcut and reduce the number of steps to make it more convenient.

Users interested in doing other contributions are still able to do that in the existing ways. If we find out that there is a need to provide shortcuts to other relevant actions for this context we can explore how to do so.

Change 757554 abandoned by Nik Gkountas:

[mediawiki/extensions/ContentTranslation@master] SX: Add mf frequent languages entrypoint module

Reason:

https://gerrit.wikimedia.org/r/757554

@ngkountas happy to get you unblocked here. Would it help if I put something in our calendars this week/next week?

@Jdlrobson Following the latest review cycle I think that we are very close to complete this task, so I do not think any extra effort will be needed. Thank you a lot for your help!

Should be unblocked now. Let me know on the ticket if you need any help with reviewing any follow up work!

Change 757550 merged by jenkins-bot:

[mediawiki/extensions/MobileFrontend@master] LanguageSearcher: Fire a hook when LanguageSearcher view is rendered

https://gerrit.wikimedia.org/r/757550

Qn: Should we avoid having multiple entrypoints like this from language selector? First one is frequentlanguages based. Last one is the search based one.

In T298032#7844534, @santhosh wrote:

Qn: Should we avoid having multiple entrypoints like this from language selector? First one is frequentlanguages based. Last one is the search based one.

Yes, we should avoid both to show at the same time.

The "frequentlanguages" based one should not be visible in search mode (in the same way that the "Suggested languages" header is gone when searching). Thus, the empty state for search should be the only one visible when there is a search with no results.

Thanks for surfacing this overlap, @santhosh.

Change 753439 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] SX Entrypoints: Add mffrequentlanguages module and register it to RL

https://gerrit.wikimedia.org/r/753439

Change 789775 had a related patch set uploaded (by Santhosh; author: Santhosh):

[mediawiki/extensions/ContentTranslation@master] ULS entrypoint: Do not show current language, fix domain redirects

https://gerrit.wikimedia.org/r/789775

Change 789832 had a related patch set uploaded (by KartikMistry; author: Santhosh):

[mediawiki/extensions/ContentTranslation@wmf/1.39.0-wmf.10] ULS entrypoint: Do not show current language, fix domain redirects

https://gerrit.wikimedia.org/r/789832

Change 789832 abandoned by KartikMistry:

[mediawiki/extensions/ContentTranslation@wmf/1.39.0-wmf.10] ULS entrypoint: Do not show current language, fix domain redirects

Reason:

Will cherry-pick new change.

https://gerrit.wikimedia.org/r/789832

Change 789832 restored by KartikMistry:

[mediawiki/extensions/ContentTranslation@wmf/1.39.0-wmf.10] ULS entrypoint: Do not show current language, fix domain redirects

https://gerrit.wikimedia.org/r/789832

Change 789775 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] ULS entrypoint: Do not show current language, fix domain redirects

https://gerrit.wikimedia.org/r/789775

Change 789832 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@wmf/1.39.0-wmf.10] ULS entrypoint: Do not show current language, fix domain redirects

https://gerrit.wikimedia.org/r/789832

Mentioned in SAL (#wikimedia-operations) [2022-05-09T13:37:15Z] <taavi@deploy1002> Synchronized php-1.39.0-wmf.10/extensions/ContentTranslation/modules/entrypoints: Backport: [[gerrit:789832|ULS entrypoint: Do not show current language, fix domain redirects (T307745 T298032)]] (duration: 00m 50s)

@KartikMistry Tested the story. It is working as expected but I do have some questions

• When I do a search of different languages ( Language A, Language B, Language C) , is there a way the order should be displayed? Should B come before C because I searched B first ?. As it is now the ordering is random. Unless this is not part of the story
• When a user searches for example, 10 - 15 languages, is there an upper limit and/or lower limit to what is been displayed on the screen while the user is in session? if all is displayed it will look clunky
• Simply reloading the page flashes the base article to be translated ( see video). This can be ignore it isn't a problem going forward
• How do I get to see the "Missing in XXX, YYY and more" under the "Suggested Languages" section

In T298032#7936991, @EChukwukere-WMF wrote:

• How do I get to see the "Missing in XXX, YYY and more" under the "Suggested Languages" section

The option is intended to be shown only when some of your frequently/previously accessed languages are missing this time.
These languages are based on previous navigations. So you can follow these steps:

1. Access an article available in many languages such as "Moon"
2. Switch to another language such as Korean or Bengali
3. Access an article available only in a few languages (not in Korean or Bengali) such as "Avocado toast" or "Extreme ironing"
4. Open the language selector and Korean/Bengali should appear as missing.

Note also the following criteria listed in the ticket:

Only languages for which Section Translation is enabled will be considered. This additional filter won't be needed when Section Translation is available in all languages.

I noticed that the following is not supported currently:

• When the "Missing languages" item is shown, the "Suggested languages" section is also shown, even if there are no other suggested items. This helps to set the context for the missing ones. Example illustrated below.

I tried the Perger prism article which is only available in English and German and got the invite without the "Suggested languages" header:

The above issue mentioned by @Pginer-WMF is resolved in the upcoming patch.

Screenshot before fix:

Screenshot after fix:

Change 805845 had a related patch set uploaded (by Nik Gkountas; author: Nik Gkountas):

[mediawiki/extensions/MobileFrontend@master] LanguageSearcher: Add suggested languages header when banner exists

https://gerrit.wikimedia.org/r/805845

Change 805845 merged by jenkins-bot:

[mediawiki/extensions/MobileFrontend@master] LanguageSearcher: Add suggested languages header when banner exists

https://gerrit.wikimedia.org/r/805845

@Pginer-WMF thats for the clear steps.

@ngkountas I see the fix.. thanks

Marking this as done

In T298032#8054192, @EChukwukere-WMF wrote:

In the screenshot shared, the "Suggested languages" header is not showing above the "Missing in Igbo" invite. I tested the Perger prism example and the same happens:

The expected result would be for the "Suggested languages" header to show above the missing languages.
I think the latest changes fixing this may have not been deployed yet, so maybe it is worth testing again on Friday.

thanks for the clarificiton moving it back to check after deploy

The "Suggested Languages" header now displays above the :

1. language(s) being suggested
2. Missing languages ( suggested due to prefrential selections). This is for an article where the suggested language(s) are ALL missing
3. Language(s) that is suggested should always be above the missing languages that are been suggested. This is for an article where the suggested languages have some already existing and others missing.

See attachment