Right now we have:
- Node source (singular, Node should not be used in the UI)
- Entity sources (plural, entity is also a technical term)
- i18n string sources (plural, more technical stuff, the actually understandable labels like Terms, Rules configuration, Node types are hidden below it)
"source" I think is also a technical thing that shouldn't be exposed. Maybe use "overview" instead?
I was also thinking about merging the secondary tabs into a single top-level task "Translation overview" and then have all of them on the same level (stuff in here are my comments, not part of the title):
- Content (hoping that most sites don't mix entity and node translation, don't have an answer for that, D8 is the answer :p)
- Blocks (entity)
- Terms (entity),
- Files
- Node types
- Blocks (i18n, another overlap that not evenD8 will solve)
- Rules configuration
So a lot of overlaps which is problematic. Another unrelated idea could be per-source pemissions for the overview. Content translation managers don't need to see some things like Node types)
Ideas?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | menu-restructuring-sources-2010384-4.patch | 37.41 KB | berdir |
| #4 | menu-restructuring-sources-2010384-4-interdiff.txt | 11.12 KB | berdir |
| #2 | menu-restructuring-sources-2010384-2.patch | 34.95 KB | berdir |
Comments
Comment #1
miro_dietikerSomehow related to the recent discussion here #1931638: Dashboard page callback missing
Comment #2
berdirTaking over this issue as it also takes care of that.
Apart from the described problem here, , we also have the problem that the source overviews are too deeply hidden in the menu.
We discussed our current (menu) structure and came up with the following:
- Introduce a new top level translation menu entry called Translations, path is admin/tmgmt
- Below that, have admin/tmgmt/jobs and job overviews and pages as before under regional
- Have a new top level sources tab, below it are all overviews of the different source plugins, on the same level (!). This means we no longer have to find non-technical labels for technicals terms, we can just drop them and stop differenting in the UI, to a large part.
- The source overview with the lowest weight automatically becomes the default tab
- The only remaining things in Regional are now translators and settings, as two separate menu items
- Some minor UI changes, like "Node overview (Entity)" instead of "Entity overview (Node)".
Two possibles problems:
- Making the translations top level menu entry too important for some sites. It can be moved around in the UI but at least admin_menu with it's exposure of local tasks will probably not like that as you will end up with jobs and sources being top-level menu items I think.
- Clashes between source overview labels. e.g. Taxonomy term entity translation and Taxonomy term i18n localization. The path contains the plugin name and can not clash (at least not the default menu generation) and the page title already contains the plugin. We could additionally add the plugin to the menu label if there are multiple labels with the same name, but that can be a low-prio follow-up.
Comment #4
berdirThis should fix the tests, not sure why I missed these.
Comment #5
miro_dietikerI like the new UI structure a lot.
Searching for tmgmt job mansgement in config was a pain.
Tmgmt separates the concept of trynslation of content creation. Now we have a representing ui structure for this new concept missing in core.
I believe that for projects where tmgmt applies the top-levelness is appropriate.
I was unable to scan through the code in detail via mobile enough.
Is configuration links added to translators?
Is LUI still in navigation? Did we decide on having it in navigation or the new top level item?
Comment #6
berdirConfigure links are added to file and local translator, LUI still is and always was in the user menu by default.
Comment #7
miro_dietikerYes makes sense. It's a personalized perspective.
Comment #8
berdirCommitted and pushed!