Page MenuHomePhabricator

Rearrange selectors in the dashboard
Closed, ResolvedPublic

Description

We need to reorganise the view and language selectors in order to emphasise the focus on the main piece of content as the design guidelines recommend.

Currently, the "New translation" action is repeated for each of the options in the view selector (suggestions, in-progress and published) and it would make more sense as a top primary action. In addition, the language selector is not always clear which elements it affects.

We can reorganise these selectors int he following way:

  • Make the "Start translation button" and the view selector form a single row of navigation actions.
  • Integrate the language selector in the list that it affects (more on T160398).

Below you can see the proposal for the suggestions and in-progress views:

A summary of the elements to be moved around is captured in the mockup below:

Event Timeline

Amire80 moved this task from Needs Triage to Bugs on the ContentTranslation board.
  • Renaming “Suggestions” to “Suggested”? To be aligned with “In progress/Published”?

"Published" brings a sense of completion that is appropriate for that view, butI don't think it is for the rest ("Suggested" or "Progressed")

I can see the point about Published, but I didn't talk about changing “in progress”.

  1. “Translations suggestions“
  2. “Translations [i]n progress“
  3. “Published translations”

As you can see, suggestions being a noun throw me off here.

Pginer-WMF removed Pginer-WMF as the assignee of this task.Jun 27 2017, 7:59 AM
Pginer-WMF added a subscriber: User-Petar.petkovic.
Pginer-WMF removed a subscriber: User-Petar.petkovic.

Change 363769 had a related patch set uploaded (by Petar.petkovic; owner: Petar.petkovic):
[mediawiki/extensions/ContentTranslation@master] Rearrange selectors in the dashboard

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

Great progress. I created a separate ticket (T169967) to polish the style of the language selector, which now it is more visible when it goes extra-wide.

I am bit unsure whether to comment in her eof T169967 or here, but I think it fits better in here as a separate issue from T169967.

In this design each language name is allocated only less than one-ninth of the page width at maximum. (both have one-sixth of the header which itself only has two-thirds of the page width given the sidebar. That is very little, and given there is more space available, I think we can do better utilization of it. Below is a screenshot of the default view with Finnish translations on my laptop:

In this design each language name is allocated only less than one-ninth of the page width at maximum. (both have one-sixth of the header which itself only has two-thirds of the page width given the sidebar. That is very little, and given there is more space available, I think we can do better utilization of it. Below is a screenshot of the default view with Finnish translations on my laptop:

A couple of thoughts:

  • Yes. There is room to go a bit wider. I'd like to identify a good maximum width that is able to accommodate most of the language names, cropping only in extreme cases where enough of the name would be already shown for it to be understood.
  • Regarding the default case, I think the current messages could be shortened. Instead of "From/to any language" showing just "Any" (or "All") may work well in this context.
  • Regarding the default case, I think the current messages could be shortened. Instead of "From/to any language" showing just "Any" (or "All") may work well in this context.

Yes, I can shorten the Finnish translations, but I would prefer that tweaking translations to be only the last option after trying to improve the design :)

  • Regarding the default case, I think the current messages could be shortened. Instead of "From/to any language" showing just "Any" (or "All") may work well in this context.

Yes, I can shorten the Finnish translations, but I would prefer that tweaking translations to be only the last option after trying to improve the design :)

I was talking about changing the source message, not a language-specific translation. That is, using just the core concept (any) and relying on the context to communicate the whole meaning instead of including all the context in writing.

Change 363769 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] Rearrange selectors in the dashboard

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

@Pginer-WMF The label "From/to any language" appears only if a user hasn't made any selection (or a new user or a user who clicked 'Reset all default settings' ). If "From/to any language" has some length problems, may be it makes sense to present a user with a pre-set pair of languages - it's not too intrusive or confusing. In a sense, the purpose of "From/to any language" is to invite users to change it, so presenting them instead with a pair of pre-set languages will serve the same purpose.

Etonkovidova added a comment.EditedAug 7 2017, 11:50 PM

Checked in betalabs
'Start a new translation' label (as in the mockups) is not present in cx-testins, betalabs, and enwiki. 'New translation' is the label that present everywhere.

Etonkovidova closed this task as Resolved.Aug 7 2017, 11:54 PM

Checked in betalabs
'Start a new translation' label (as in the mockups) is not present in cx-testins, betalabs, and enwiki. 'New translation' is the label that present everywhere.

'Start a new translation' is changed to 'New translation' in T160067. Mockups are outdated as mentioned in T160398#3406824