- Issue created by @gwenweb
In fact, each team uses the tabs in a different way, so for me, whatever changes we make, we're going to be creating more problems than solving them. So do we need to go any further?
When the Localize page is opened, and after choosing the language/community, the tab which is highlighted is the "Translate tab". I wonder if the order of the tabs is the right one, in order to facilitate the tool usability.
I've asked the question about the "Overview" tab on the Drupal slack, channel #localize and had some incomes such as :
From the Catalan community, more or less the same as the French-speaking one (quick and loose translation): «We use it to explain how to translate and provide guidelines. It is handy for a brief introduction and mention some documentation which depends on each translation community.»
Yeah I think the front page for example leads right into the translation UI, so even though that is not the default tab, we have other ways to lead relevant people there.
Here in Germany it is a quick way to find the issue queue, if we remove it, we should find a way to link to the issue queue on Drupal.org for a specific language so that queue remains accessible with one or two clicks. The Page itself isn't that much important, but it could be a great place to on-board people in their native language.
In the Dutch community we use it to give (relatively) new users a quick intro and links to places where to find info (style guide, word list, procedure) get in touch (slack, leading people) and where to get started (links to untranslated, to be reviewed)
And I've asked the question about the "Board" tab :
The Board tab is just a message board where some of us had written articles and notes about translation. They communicated there in particular languages and across the translator community. We do not need the tab. But it would be nice to have similar functionality to communicate with each other in the feature. So If we use groups some place to write and comment sth. about translation globally and in a particular language would be a handy tool for the feature, too.
There is little community activity on the Dutch board. One comment per year or less in recent years. We use Slack. I don’t see added value in its current form.
Reflect together, we can use wireframes if needed.
Integrate changes in css and settings if needed.
Active
3.0
User interface
In fact, each team uses the tabs in a different way, so for me, whatever changes we make, we're going to be creating more problems than solving them. So do we need to go any further?