AMO:Projects/developer.AMO/Features: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 1: Line 1:
= developer.AMO Features =
= developer.AMO Features =
'''Please post comments on the Talk page, blog post, or newsgroup.'''


One of the primary goals of developer.AMO is to aggregate resources into one place, but we shouldn't duplicate or copy content that we don't need to. Therefore, we can break content into two groups: aggregated and hosted.
One of the primary goals of developer.AMO is to aggregate resources into one place, but we shouldn't duplicate or copy content that we don't need to. Therefore, we can break content into two groups: aggregated and hosted.
Line 10: Line 12:
== Hosted Content ==
== Hosted Content ==
; Forums : Forums for extension development support, add-on ideas, etc.
; Forums : Forums for extension development support, add-on ideas, etc.
; Surveys : Area for us to post surveys and have developers take them.
; Surveys : Designated area/widget for developer surveys to be posted.
; AMO Policies : Policies for hosting add-ons on the site, review guidelines, etc.
; AMO Policies : Policies for hosting add-ons on the site, review guidelines, etc.
; Case Studies : Case studies of add-ons
; Case Studies : Case studies of add-ons
; Taggable Searchable Code Repository : All extension that have their source as viewable online should be accessible in a repository for searching and tagging specific lines of code
; Taggable Searchable Code Repository : All extensions that have their source as viewable online should be accessible in a repository that's searchable. Users will also be able to selected lines of code and tag them, such as "opens a new tab" or "creates new about: page" for easy access to code snippets.
; Developer Tools : The Developer Tools part of AMO will stay where it is, but should be reskinned and otherwise associated with the developer site.
; Developer Tools : The Developer Tools part of AMO will stay where it is, but should be reskinned and otherwise associated with the developer site.
; Extension/Theme skeletons : Provide downloadable, documented skeletons for major extension types, such as a toolbar, sidebar, statusbar extension.
; Metrics : We should display developer-related metrics such as average time in queue and others TBD.
; Best Practices Documents : We should create Best Practices Documents on important topics like Security, Performance, and Usability
canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,043

edits

Navigation menu