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

no edit summary
(Created page with '= developer.AMO Features = 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. ...')
 
No edit summary
Line 4: Line 4:


== Aggregated Content ==
== Aggregated Content ==
* Developer News (add-ons blog feed)
; Developer News : Widget on homepage with latest articles from AMO blog in developers category.
* Upcoming Events (add-ons blog feed)
; Upcoming Events : Widget on homepage with upcoming events from AMO blog in events category
* most documentation and tutorials (MDC)
; Documentation, Tutorials, Code Samples : Links to relevant documentation on MDC and other content
*
 
== Hosted Content ==
== Hosted Content ==
* Forums
; Forums : Forums for extension development support, add-on ideas, etc.
* Surveys
; Surveys : Area for us to post surveys and have developers take them.
* AMO Policies
; AMO Policies : Policies for hosting add-ons on the site, review guidelines, etc.
* Case Studies
; Case Studies : Case studies of add-ons
* Taggable Searchable Code Repository
; 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
* Developer Tools (reskinned but kept on AMO)
; Developer Tools : The Developer Tools part of AMO will stay where it is, but should be reskinned and otherwise associated with the developer site.
canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,043

edits