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

; Developer News : Widget on homepage with latest articles from AMO blog in developers category.

; Upcoming Events : Widget on homepage with upcoming events from AMO blog in events category

; Documentation, Tutorials, Code Samples : Links to relevant documentation on MDC and other content

; AMO Policies : Policies for hosting add-ons on the site, review guidelines, etc.

; Case Studies : Case studies of add-ons

; 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 select 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.

; 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

; Forums : Forums for extension development support, add-on ideas, etc.

; Surveys : Designated area/widget for developer surveys to be posted.