Page MenuHomePhabricator

Support the "For later" list in Section Translation
Closed, ResolvedPublic


Currently, the new translation dashboard for Section Translation does not include the "For later" list (unlike the old Content Translation dashboard). The "For later" list allows users to keep at hand articles they are interested in translating but may not have availability to translate them immediately. For example, this can be helpful when the user finds more than one interesting article in the suggestions list.

Supporting the "For later" list requires to support both the display of the list and the action to bookmark translations to be added to the list. Considerations for both of those aspects are listed below.

The list:

  • The list is placed at the suggestions view of the dashboard, above the suggestions list.
  • The list is only displayed if it contains one or more items in it. That is, the "For later" list will be only visible once the user adds an article to it, and will disappear if all items are removed.
  • Each item in the list is an article for a specific language pair. Notice that this list includes no language filter options. Thus, it lists all articles added by the user regardless of their languages (there is a bug in Content Translation where the language pair filter for suggestions affects also the "For later" list, let's not replicate that here).
  • For articles that already exist in the target language, an indicator of the missing sections is shown (see 2nd item in the example below):

Dashboard lists - For later.png (768×1 px, 142 KB)

Actions to bookmark an article:

  • Suggestions include a bookmark icon that would add them to the "for Later list". Once a suggestion is added, it will disappear from the list of suggestions and a new suggestion will be added to the bottom of the suggestions list to keep the number of suggestions constant.
  • The confirmation step (T241587) includes a bookmark icon.
  • In both cases, taping the bookmark icon will switch between the empty ("bookmarkOutline") and filled ("bookmark") version of the icon. The filled version will be rendered in blue (Accent50: #36c).

The parent ticket (T253253) includes more details about the general layout and structure of the lists on the dashboard:

Dashboard lists - List structure.png (768×1 px, 190 KB)
Dashboard lists - List structure Dimensions.png (768×1 px, 122 KB)

Event Timeline

Pginer-WMF triaged this task as Medium priority.Aug 11 2020, 4:43 PM
Pginer-WMF renamed this task from Translation dashboard lists: "For later" list update to Support the "For later" list in Section Translation.Jul 14 2021, 9:55 AM
Pginer-WMF updated the task description. (Show Details)

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

[mediawiki/extensions/ContentTranslation@master] SX Dashboard: Support \"For later\" list

Change 710041 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] SX Dashboard: Support \"For later\" list

The confirmation step (T241587) includes a bookmark icon.
the confirmation step bookmark icon right now is not working:

  • doesn't get blue when the article is bookmarked
  • doesn't do anything when we click it

is this going to be done in a different task?

Looking at the implementation it seems that the "for later" list was added as a section of the "Suggestions" list. However, it should be a separate list showing above Suggestions instead (as it is in Content Translation). I'll add screenshots of both for a more visual comparison:

"For later" in Content Translation (separate)"For later" in Section Translation (combined with suggestions)
cx-for-later.png (1×2 px, 229 KB)
sx-for-later.png (1×2 px, 323 KB)

Given that the "For later" items get not affected by the language selector or the "Refresh suggestions" options, it is preferred to show them in their own separate list as more persistent items.

I created a follow-up ticket to capture the pending items mentioned above: T290482: Adjust the "For later" list presentation and access

If there is nothing else missing, I thing we can resolve the current ticket. Even with the above pending aspects, it is nice to see these steps towards the dashboard unification. Thanks everyone!