Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I go here: http://localize.drupal.org/translate/projects/uc_notforsale
and follow a language.
That gets me here: http://localize.drupal.org/translate/languages/uk/translate?project=uc_n...
How do I get back?
Comment | File | Size | Author |
---|---|---|---|
#5 | project-link.patch | 1.21 KB | Gábor Hojtsy |
#5 | JumpToProject.png | 48.1 KB | Gábor Hojtsy |
Comments
Comment #1
apadernoComment #2
Gábor HojtsyYour 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?
Comment #3
Gábor HojtsyAlso moving to the right project.
Comment #4
joachim CreditAttribution: joachim commentedYup, 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'?
Comment #5
Gábor HojtsyProduced 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.
Comment #6
Gábor HojtsyAny feedback on this? Not interested anymore?
Comment #7
joachim CreditAttribution: joachim commentedSorry...
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.
Comment #8
SebCorbin CreditAttribution: SebCorbin at Makina Corpus commentedAgreed, some UX testing is required.
It may happen in 7.x-1.x branch