Closed
Bug 790803
Opened 12 years ago
Closed 12 years ago
Add "My Documents" menu to list my translated articles in my profile
Categories
(support.mozilla.org :: Knowledge Base Software, task, P2)
support.mozilla.org
Knowledge Base Software
Tracking
(Not tracked)
RESOLVED
FIXED
2012Q4
People
(Reporter: atopal, Assigned: rrosario)
References
Details
(Whiteboard: u=contributor c=wiki p=2 s=2012.23)
Attachments
(2 files)
* As a localizer (and as a English KB editor) I would like to see in my profile the documents that I've worked on, so that I can have an impression of my contribution.
* As a locale leader and community manager I would like to see the contributions of others, so that I can understand what the contributor has been working on and I'm able to help, organize and reward.
https://sumo.etherpad.mozilla.org/102
Comment 1•12 years ago
|
||
This is a mockup of the profile page with a “Translated Documents” section added on top of “About this user”.
Reporter | ||
Comment 2•12 years ago
|
||
Bram, most localizers have dozens or even hundreds of articles they have worked on. I think we'll need something similar to the forum posts, where we show the number of articles contributed to and then link to a listing.
Reporter | ||
Updated•12 years ago
|
Assignee: nobody → bram
Comment 3•12 years ago
|
||
(In reply to Kadir Topal [:atopal] from comment #2)
> Bram, most localizers have dozens or even hundreds of articles they have
> worked on. I think we'll need something similar to the forum posts, where we
> show the number of articles contributed to and then link to a listing.
Sorry, I had completely missed your comment.
As usual, I’m thinking about how to solve the bigger underlying issue, rather than how to fix the surface.
Yes, if there are a lot of articles (more than 10 or 15), we should put the list of translated documents in a separate page.
The way that the translated article list looks could be a simple list. But if we’re going to give this information its own page, then maybe it’s worth it to put the article title in a table. This table would also contain informations like title of article, original author, who made the last edit, when was the last edit made, what is the article status, etc.
But this brings up another interesting point.
The list of my translated articles contains the same type of information as the Contributor Forums Dashboard. Both concern themselves with contributions.
Contributions mean everything that you have added to SUMO: every KB change you made, every article you translated, every support question you answered, and every contributor forum posts you wrote.
So it makes sense that these informations all belong in the same area, and be named consistently.
The “Contributor Forums Dashboard” should be renamed for continuity and consistency, to something like “Contributor Forum Posts”.
If we have another page that tracks your support forum answers, we could call it “Support Forum Posts”.
If we have a page that tracks your en-US KB article contributions, we could call it “KB articles” if you open it in en-US, or “English KB articles” if you open it in any other language.
The heading “Translated Documents” should be renamed to “Translated KB articles” so that it’s consistent with the other items.
And finally, all of these informations should be accessible from your sidebar, and be grouped in one area.
So that way, the information space is clear, and new users have one place to track everything.
Of course, We don’t have to implement all of these today. But if we’re planning to expand functionality, we should keep consistency and integration in mind.
Assignee | ||
Comment 4•12 years ago
|
||
(In reply to Bram Pitoyo [:bram] from comment #3)
> Created attachment 663889 [details]
> Organizing the dashboard
I think this is mostly what we already have in our group dashboards. I am pretty sure what we want is to show some numbers on the the profile page with links to the full list. This is more about showing off than organizing all the information, I think?
Comment 5•12 years ago
|
||
(In reply to Ricky Rosario [:rrosario, :r1cky] from comment #4)
> I think this is mostly what we already have in our group dashboards. I am
> pretty sure what we want is to show some numbers on the the profile page
> with links to the full list. This is more about showing off than organizing
> all the information, I think?
I agree. This is about showing off the information in a separate page.
Plus, this is also about giving some ideas as to how many documents each user had translated on their profile pages.
If we’re going to put numbers on the profile page, we can put it on the right of the heading “Translated Documents”. So you’ll see “Translated Documents (84)”, for example. The heading will also be a link.
I think the design of the listing page will just be a simple list of article. An <ol> <li>. Alternatively, it can also be a list that’s put inside a table, where in addition to the article name, we also see the last change and original author.
Reporter | ||
Updated•12 years ago
|
Whiteboard: u=contributor c=wiki p= → u=contributor c=wiki p=2012.22
Reporter | ||
Updated•12 years ago
|
Whiteboard: u=contributor c=wiki p=2012.22 → u=contributor c=wiki p= s=2012.22
Reporter | ||
Updated•12 years ago
|
Priority: -- → P2
Assignee | ||
Comment 6•12 years ago
|
||
We need to add the links and create the simple list views (comment 5).
Whiteboard: u=contributor c=wiki p= s=2012.22 → u=contributor c=wiki p=2 s=2012.22
Assignee | ||
Comment 7•12 years ago
|
||
Dropping to next sprint.
Assignee: bram → nobody
Whiteboard: u=contributor c=wiki p=2 s=2012.22 → u=contributor c=wiki p=2 s=2012.23
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → rrosario
Assignee | ||
Comment 8•12 years ago
|
||
In a pull request:
https://github.com/mozilla/kitsune/pull/973
Assignee | ||
Comment 9•12 years ago
|
||
Landed and deployed:
https://github.com/mozilla/kitsune/commit/aa518d87a74e8824ed79f3476352d979cd362fc7
https://github.com/mozilla/kitsune/commit/4ff9102d6c5459d36ff8ec41f706535d8352e4dd
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•