We looked at user experience for translations and unifying that across interface/content/configuration, and would like to propose that the content listing page gains more features in terms of translations. The features currently supported include:

- language information in table
- filtering for specific language
- filtering by outdated translation or up to date translation status

These are great. However, you cannot really search for stuff to translate. There is no way to look for posts in a language that are looking for translations + there is no information on the translation status. Finally, it would be more than superb if there would be a small condensed view of translation status for your node. So to compare, we are trying to unify the experience for UI and content translation, like so:

VS:

One might say, we basically propose moving translation overview module to core but with a much slimmer UI (and built in with the much more versatile features of the node admin listing page). What we are looking for here really is leveling the UX between interface and content translation, which looks like really about filling in the gaps for content translation that are missing. (I tried to find an issue for the missing search but I did not find any, will submit an issue for that momentarily).

Parent issue

#1260690: META: Improve multilingual user experience in Drupal 8

CommentFileSizeAuthor
TranslationContent.png85.22 KBGábor Hojtsy
TranslateUI.png121.65 KBGábor Hojtsy
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Gábor Hojtsy’s picture

Gábor Hojtsy’s picture

BTW I admit adding yet another column on this page for translation makes it more busy. We might want to look into options to turn sets of info or columns on/off(?). Like if you are interested in language support, you'd pick language and translation status columns to show. That might quickly become too complex there (and probably not for this issue anyway).

Gábor Hojtsy’s picture

Issue tags: +language-content

Tagging for the content handling leg of D8MI.

YesCT’s picture

Title: Add translation information to content listing admin page » Add translation filter to content listing admin page
Issue tags: +Novice, +challenging

lets do here:
add the translations filter, so that someone could find content that was say: missing french translation

Novice tasks to (just) open separate issues:

lets open a new issue for adding the languages quick summary of translation status column

lets open a new issue for a setting to show/hide columns (does views listing content effect that?)

Gábor Hojtsy’s picture

@YesCT: I think this would be great to cross-check with VDC people. This page is I think in the process of being converted to a view somehow (there is basic VBO in core too). Once this page is a view, it becomes interesting as to how could the entity translation module expand on the view when enabled... Possibly it would ship with an expanded version of the core node admin view, so users can switch between the two.

YesCT’s picture

YesCT’s picture

looks like we should try and help the view of the content listing. There is a start of a patch at: #1823608-5: Admin views in core and we should probably read the whole thing, especially comment #1 there.

tim.plunkett’s picture

Issue tags: +VDC

Tagging.

Gábor Hojtsy’s picture

Status: Active » Postponed
Gábor Hojtsy’s picture

Issue tags: +SprintWeekend2013
Gábor Hojtsy’s picture

Make it full HTML

Gábor Hojtsy’s picture

Status: Postponed » Closed (duplicate)

This page is now an admin view and people can make most of these adjustments. We will NOT make the view have these by default because that is impossible in the Drupal 8 configuration system (due to how active config always need to have owners installed). Marking duplicate of #1823608: Admin views in core.