Page MenuHomePhabricator

CX2: Make translation editor layout responsive to adapt to small screens
Open, MediumPublic

Description

The translation editor of Content Translation is not well suited for small screens. Given the need for contextual information, it provides three columns to show the original article, the translation and the tools provided to facilitate the process. This is convenient in wider screens, but it would help to have an alternative solution to support smaller screens.

A narrow width mode is proposed to better accommodate small windows:

Full-widthNarrow width
cx-regular-translate.png (768×1 px, 238 KB)
cx-small-translate.png (720×650 px, 168 KB)

A narrow mode

When the width does not allow the three columns to comfortably fit, only two columns will be shown at a time.
The default view will show the source and target columns. There will be a "+" action on the margin that will make the viewport to transition showing the target and tools column instead.

cx-small-translate.png (720×650 px, 168 KB)
cx-small-translate-tools.png (720×650 px, 167 KB)

Some considerations:

  • The "+" icon will appear in the margin next to the current active paragraph, and will include an active area much bigger than the "+" shape.
  • The transition to show the tools column will be triggered by either clicking or hovering the "+" icon.
  • An "X" icon will be provided in the tools panel for users to go back to the default view.
  • Swiping left and right will allow to show the tools column and hide it.
  • When the tools panel is visible, part of the source article will remain visible on the other extreme. That area will be used also to return to the default view either by clicking or hovering. Note that in this context the source article would act as a whole block, the user intent is not to click on a specific link of the partially visible article, so the click should not be propagated beyond making the source article return into the viewport.

A prototype and an animated example illustrates some of these aspects:

cx-small-screens.gif (406×376 px, 2 MB)

Event Timeline

Considering to hide some of the headers may give room for the keyboard, as suggested by @santhosh.
We can also explore how to make use of the keyboard space when the keyboard is not needed.

Nice, but a few points:

I'm a bit reluctant about a single plus sign in the tools panel. A plus conveys adding something, and this is not quite what is done here. I'd imagine something like a chevron as an icon for expansion. Or the words "Tools" (possibly written vertically). Or, instead of an expansion icon we could have some icons that say what kinds of actions can be found in that bar. But maybe simple communication about expansion is enough. Then, the button to collapse it can perhaps be changed from an X to a chevron that points the other way, because it's just collapsing and not closing.

That area will be used also to return to the default view either by clicking or hovering

I'm really not sure about hovering. But tapping back on the translation column should probably collapse the tools panel.

I'm a bit reluctant about a single plus sign in the tools panel. A plus conveys adding something, and this is not quite what is done here.

Discoverability is a key challenge here. The idea was to align the action with user intents such as "adding a link", "adding bold format", etc. which is what the translator may be looking for. Just telling "expand" won't be anticipating what the user will find there. Representing "tools" was another approach I explored initially, but we can explore that direction further.
In any case, testing with some users will help us understand the expectations about the discovery of the translation tools.

That area will be used also to return to the default view either by clicking or hovering

I'm really not sure about hovering. But tapping back on the translation column should probably collapse the tools panel.

One relevant question is whether we want to keep the translation view editable when the tools are visible. If we want to support adding several links in a row it may be more convenient to keep the tools column open as the user does so, and only returning to the default view when comparing source and target content is needed. This is not possible if we move back to the default view as soon as the user touches the translation again.

Arrbee triaged this task as Medium priority.Feb 8 2017, 6:49 AM
Pginer-WMF renamed this task from Make translation editor layout responsive to adapt to small screens to CX2: Make translation editor layout responsive to adapt to small screens.Mar 8 2018, 1:49 PM
Pginer-WMF removed a project: Design.
Pginer-WMF updated the task description. (Show Details)

I created a quick prototype (prepared for an iPad in portrait mode), and tried it to check how it feels on a real device. I marked the ticket as CX2 since I think that including it as part of version 2 of CX allows us to try experiment and iterate better on different devices in this front.