Design Localizer dashboard

VERIFIED FIXED in 5.5

Status

addons.mozilla.org Graveyard
Localization
P2
enhancement
VERIFIED FIXED
8 years ago
2 years ago

People

(Reporter: wenzel, Assigned: wenzel)

Tracking

unspecified
Dependency tree / graph

Details

(URL)

Attachments

(2 attachments)

(Assignee)

Description

8 years ago
Our localizer "landing page" is currently, uhm, un-pretty. In AMO 5.5 I am planning on making it slightly more useful for the individual localizer.

This bug for discussing and mocking up what to show and how. Implementation bugs to follow.
(Assignee)

Comment 1

8 years ago
Okay, information that we have right now:
- translated dynamic strings for all locales
- L10n log entries

and finally, on sub-pages
- untranslated gettext strings
- localized pages

I'd like to combine this info on the front page, at least as an overview, pointing to the sub-pages for details. Also, it's probably better to just show info on the current user's locale, instead of a huge list of all locales.

More info for us to show:
- checkin RSS feed from the locale dir
- localization resources (AMO wiki? Verbatim?)

Comments? Anything else I am missing?
Created attachment 414601 [details]
mockup

I spent some time thinking about this (attached) and the more I think about it, the more I think we need localizer input sooner rather than later, which makes the timeline tight.

Anyway, I put my thoughts in that mockup.  The bottom left/middle feel like maybe there is something more important that could go there, but nothing came to mind.  Let me know what you think and let's get dev-l10n-web's feedback once we come up with something here.
(Assignee)

Comment 3

8 years ago
Nice mockup, Wil! At first I was wondering where the links to the actual translation pages are, but I am guessing making the categories clickable in the overview is sufficient?

Since you included all points I could think about above in your mockup, I'll send this bug to the localizers asking for feedback.

Comment 4

8 years ago
Could we have po strings in (5) in addition to categories and pages? I don't see missing po strings anywhere in the mockup.
(Assignee)

Comment 5

8 years ago
(In reply to comment #4)
> Could we have po strings in (5) in addition to categories and pages? I don't
> see missing po strings anywhere in the mockup.

Yes, definitely. That should, in fact, be the first entry in the list, if you ask me.

Comment 6

8 years ago
I like the mockup. 

Is there a way for the overall l10n dashboard to get to the progress summary? I assume there is, as amo needs to get it out of verbatim as well.
(Assignee)

Comment 7

8 years ago
(In reply to comment #6)
> Is there a way for the overall l10n dashboard to get to the progress summary? I
> assume there is, as amo needs to get it out of verbatim as well.

You mean, an overview of all locales' progress? Looks like we could make that one of the options under "change language", and change the layout for that page only, so that the progress indicators are the central content on that page.

Also, I won't grab anything from Pootle. Any stats we need to collect I'll pull from the .po files, then cache.

Comment 8

8 years ago
(In reply to comment #7)
I would guess Axel referred to either http://l10n.mozilla.org/dashboard/ or http://l10n.mozilla.org/webdashboard/
(In reply to comment #5)
> (In reply to comment #4)
> > Could we have po strings in (5) in addition to categories and pages? I don't
> > see missing po strings anywhere in the mockup.
> 
> Yes, definitely. That should, in fact, be the first entry in the list, if you
> ask me.

Agreed.  I stuck "..." down there because there are more things to put in that list.

(In reply to comment #7)
> You mean, an overview of all locales' progress? Looks like we could make that
> one of the options under "change language", and change the layout for that page
> only,
I made this URL have /pl on the end and I figured we could stick something on just /localizers/ that is a cool summary.  This particular bug was about specific locales though, so I went with that.

I had some implementation thoughts:
- The right column should mostly stick around on sub pages (we can adjust it's contents to be more useful) and the left "main" pane will be what changes when localizing categories, etc.

- In order to say "the en-US category changed, please update yours" we'd have to store an "out-of-date" flag with categories.  Perhaps we should consider whether the way we are doing categories now is the best way. I don't have any other great ideas, just throwing that out there.  An out-of-date flag could be useful on the translations table anyway.

- I remembered we're already using simple/small graphs for our collection ratings, so where the mockup says it would use the verbatim graphs I really mean the collection rating graphs, just so we can use the same CSS/code.

Comment 10

8 years ago
(In reply to comment #2)
> Created an attachment (id=414601) [details]
> mockup
> 

Thanks Wil! I like this mockup. :)
(Assignee)

Comment 11

8 years ago
(In reply to comment #9)
> I made this URL have /pl on the end and I figured we could stick something on
> just /localizers/ that is a cool summary.  This particular bug was about
> specific locales though, so I went with that.

We should make a mockup for that page as well. If you get to it before I do, go right ahead! My suggestion is to have a big indicator on the top for the *global* progress, then one for each language. Clicking on a lang takes you to its dashboard.

On the bottom left, we show the global news feed.

What to show in the sidebar (if anything), I don't know yet.
I like the plans. Good job Fred and Wil!
(Assignee)

Updated

8 years ago
Blocks: 531883
Created attachment 415276 [details]
global mockup

(In reply to comment #11)
> (In reply to comment #9)
> > I made this URL have /pl on the end and I figured we could stick something on
> > just /localizers/ that is a cool summary.  This particular bug was about
> > specific locales though, so I went with that.
> 
> We should make a mockup for that page as well. If you get to it before I do, go
> right ahead! My suggestion is to have a big indicator on the top for the
> *global* progress, then one for each language. Clicking on a lang takes you to
> its dashboard.
> 
> On the bottom left, we show the global news feed.
> 
> What to show in the sidebar (if anything), I don't know yet.

Alright, here is a go at that.  Happy to have feedback since I'm not really sure what is useful here.  I tried to give an overall status without making it really complicated.

I don't think a "recent activity" list is useful though.  40+ locales making updates - who's going to pay attention to the list?  (It does look good on the page, I'm just talking about subscribing to an RSS feed)
Ideas for the global mockup:
- fligtar suggested a "Did you find a problem?" link.  Let's stick that at the top of the wiki page and point people to bugzilla.  We could put a link on this page that points to the wiki.

- On the individual locale page I have a dropdown in the top right that chooses the language.  I think we should bring that back here and just have it say "Choose locale...".  That way people don't need to dissect the huge blob in the middle if they don't want to

- Let's remove the "These locales are currently hidden..." line and the implication that locales under 70% are automatically hidden.  I don't think that's a good idea anymore and we should only hide locales on an individual basis.  For the crazy 3 piece chart here, hidden locales should be italicized and maybe less bold.

- "hidden" means that they don't show up in any dropdowns, and any page with /$lang/ in it where $lang is hidden includes a meta tag for search engines to not index them.  A hidden language _will_ show up in translation boxes, and on the localizer control panel pages, and if someone manually types in the URL it will still work.
(Assignee)

Comment 15

8 years ago
Comments on the global mockup:

- I like the mockup and the suggestions. I agree that these locales shouldn't be automatically hidden, but on a case-by-case basis. We'll still show it on the pre-locale page, but not implying that it automatically happened.

- I do think the news feed makes sense, and if people don't want to subscribe to it they don't have to. If we don't put an RSS symbol there, however, that'll be the first bug someone's going to file.

- For the messages on the side, I wonder if we can get away with a simple inline-editing (like photo names on flickr, for example), or if we need a full-blown admin interface, localizable strings, etc. I extracted that to bug 532064 for now.

- To answer the question in your mockup: l.m.o cannot handle the traffic yet, but once it's actually up and running, it should.

Comment 16

8 years ago
Can we find disambiguous shorts for the l.m.o servers? My brain maps that to l10n.m.o, and you're probably talking about localize.m.o, right? Or just deal with it and use the full host name?
(Assignee)

Comment 17

8 years ago
(In reply to comment #16)
> Can we find disambiguous shorts for the l.m.o servers? My brain maps that to
> l10n.m.o, and you're probably talking about localize.m.o, right? Or just deal
> with it and use the full host name?

wfm.
> - I do think the news feed makes sense, and if people don't want to subscribe
> to it they don't have to. If we don't put an RSS symbol there, however, that'll
> be the first bug someone's going to file.

The dev hub uses that because it just rips the RSS feed from the blog.  We could create an L10n tag on the blog and do the same thing, but all the news that we would post there comes out on the mailing list and it's all relatively dull (e.g. "5.4 strings are ready.  Launch 12/8").  I could start posting in both places, just seems like a pain.
(Assignee)

Comment 19

8 years ago
(In reply to comment #18)
> > - I do think the news feed makes sense, and if people don't want to subscribe
> > to it they don't have to. If we don't put an RSS symbol there, however, that'll
> > be the first bug someone's going to file.
> 
> The dev hub uses that because it just rips the RSS feed from the blog.

Aren't we just talking about the "recent activity" that we already show on the per-locale pages?
(In reply to comment #19)
> (In reply to comment #18)
> > > - I do think the news feed makes sense, and if people don't want to subscribe
> > > to it they don't have to. If we don't put an RSS symbol there, however, that'll
> > > be the first bug someone's going to file.
> > 
> > The dev hub uses that because it just rips the RSS feed from the blog.
> 
> Aren't we just talking about the "recent activity" that we already show on the
> per-locale pages?

If we are, nevermind! :)  I was talking about creating a feed in the column on the right like on the dev hub.  I think the word "news" made my brain move to the announcements box.
Priority: -- → P2
CCing Ehsan for RTL input as this bug progresses. :)
(Assignee)

Updated

8 years ago
Blocks: 536141
(Assignee)

Comment 22

8 years ago
We're good on the design front, the dashboard is almost ready to go.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Verified FIXED on https://preview.addons.mozilla.org/en-US/localizers and friends; still probably a few small bugs to be found and filed, but this is done.
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.