MDN/Development/Google Summer of Code 2013: Difference between revisions
< MDN | Development
Jump to navigation
Jump to search
(→Assets) |
No edit summary |
||
| Line 3: | Line 3: | ||
Build a Localization Dashboard for the Mozilla Developer Network (MDN) to help contributors view localization progress and find articles that need to be localized. The dashboard should be somewhat similar to the existing [https://developer.mozilla.org/dashboards/revisions Revision Dashboard]. Over the course of the summer, the student should build a [https://en.wikipedia.org/wiki/Minimum_viable_product minimum viable product] and work with the MDN team to iterate on it, making as many improvements as time allows. | Build a Localization Dashboard for the Mozilla Developer Network (MDN) to help contributors view localization progress and find articles that need to be localized. The dashboard should be somewhat similar to the existing [https://developer.mozilla.org/dashboards/revisions Revision Dashboard]. Over the course of the summer, the student should build a [https://en.wikipedia.org/wiki/Minimum_viable_product minimum viable product] and work with the MDN team to iterate on it, making as many improvements as time allows. | ||
== | == Considerations == | ||
=== Performance === | |||
Some of these features could be taxing on the server-side. Even the [https://developer.mozilla.org/dashboards/revisions Revision Dashboard] is having trouble with this. We will need to keep this in mind during implementation. | |||
== Design Proposals == | |||
=== Design Proposal #1 === | === Design Proposal #1 === | ||
Revision as of 17:45, 7 May 2013
Project statement
Build a Localization Dashboard for the Mozilla Developer Network (MDN) to help contributors view localization progress and find articles that need to be localized. The dashboard should be somewhat similar to the existing Revision Dashboard. Over the course of the summer, the student should build a minimum viable product and work with the MDN team to iterate on it, making as many improvements as time allows.
Considerations
Performance
Some of these features could be taxing on the server-side. Even the Revision Dashboard is having trouble with this. We will need to keep this in mind during implementation.