Support from Acquia helps fund testing for Drupal Acquia logo

Comments

apaderno’s picture

Component: Site organization » Localize.drupal.org
Gábor Hojtsy’s picture

Status: Active » Postponed (maintainer needs more info)

Your back button? These do not reside under the same navigation tree as can be seen from the path, they are cross-referenced. Also, the translation UI allows for filtering with projects, and does not consider the project a navigation item in that sense (as can be seen from the project name being in a form element and in the query string consequently).

What would you suggest? Where did you expect a navigational item to that project's page?

Gábor Hojtsy’s picture

Project: Drupal.org site moderators » Localization server
Version: » 6.x-2.x-dev
Component: Localize.drupal.org » User interface

Also moving to the right project.

joachim’s picture

Title: now way back from language to project » no way back from language to project

Yup, I can see form the URLs that I'm jumping into another tree, but the project language list does feel like it's a place from which to browse the languages for this particular project.

Maybe hack in header text for that view that picks up on the filter value and shows a link like 'Show all languages for project foo'?

Gábor Hojtsy’s picture

Status: Postponed (maintainer needs more info) » Needs work
FileSize
48.1 KB
1.21 KB

Produced this quickly. I think the link could belong there but it is way too close to the select box and can easily drive you away, while you are translating, could have unsaved changes, etc. Better suggestions are welcome.

Gábor Hojtsy’s picture

Any feedback on this? Not interested anymore?

joachim’s picture

Sorry...

I think my point was that when you're on the project page, the list of languages makes you think you are about to drill down, but you're actually drilling *sideways* to go to the language page that's been filtered down to the project.

However, what's still not clear to me is how you get to http://localize.drupal.org/translate/languages/eo/translate in the first place.

The patch would certainly help navigation -- though I think linking the name of the project in the filtered view title would be better.

Overall though, I think the localize site would benefit from some kind of analysis to figure out the different flows and landing pages. Browsing it I don't get a feeling of where I am and this makes it confusing to use.

SebCorbin’s picture

Issue summary: View changes
Status: Needs work » Postponed (maintainer needs more info)

Agreed, some UX testing is required.

It may happen in 7.x-1.x branch