AMO:Projects/developer.AMO/Features - Revision history

Fligtar at 23:41, 13 May 2009

2009-05-13T23:41:55Z

← Older revision		Revision as of 23:41, 13 May 2009
Line 16:		Line 16:
	; 1.7 [[AMO:Projects/developer.AMO/Features/Tools\|Developer Tools]] : The Developer Tools part of AMO will stay where it is, but should be reskinned and otherwise associated with the developer site.<br/>Status: ''Awaiting spec''		; 1.7 [[AMO:Projects/developer.AMO/Features/Tools\|Developer Tools]] : The Developer Tools part of AMO will stay where it is, but should be reskinned and otherwise associated with the developer site.<br/>Status: ''Awaiting spec''
	; 1.8 [[AMO:Projects/developer.AMO/Features/Skeletons\|Extension/Theme skeletons]] : Provide downloadable, documented skeletons for major extension types, such as a toolbar, sidebar, statusbar extension.<br/>Status: ''Awaiting spec''		; 1.8 [[AMO:Projects/developer.AMO/Features/Skeletons\|Extension/Theme skeletons]] : Provide downloadable, documented skeletons for major extension types, such as a toolbar, sidebar, statusbar extension.<br/>Status: ''Awaiting spec''
	; 1.9 [[AMO:Projects/developer.AMO/Features/~~News~~\|Metrics]] : We should display developer-related metrics such as average time in queue and others TBD.<br/>Status: ''Awaiting spec''		; 1.9 [[AMO:Projects/developer.AMO/Features/Metrics\|Metrics]] : We should display developer-related metrics such as average time in queue and others TBD.<br/>Status: ''Awaiting spec''
	; 1.10 [[AMO:Projects/developer.AMO/Features/BPD\|Best Practices Documents]] : We should create Best Practices Documents on important topics like Security, Performance, and Usability<br/>Status: ''Awaiting spec''		; 1.10 [[AMO:Projects/developer.AMO/Features/BPD\|Best Practices Documents]] : We should create Best Practices Documents on important topics like Security, Performance, and Usability<br/>Status: ''Awaiting spec''
	; 1.11 [[AMO:Projects/developer.AMO/Features/Forums\|Forums]] : Forums for extension development support, add-on ideas, etc.<br/>Status: ''Awaiting spec''		; 1.11 [[AMO:Projects/developer.AMO/Features/Forums\|Forums]] : Forums for extension development support, add-on ideas, etc.<br/>Status: ''Awaiting spec''
	; 1.12 [[AMO:Projects/developer.AMO/Features/Surveys\|Surveys]] : Designated area/widget for developer surveys to be posted.<br/>Status: ''Awaiting spec''		; 1.12 [[AMO:Projects/developer.AMO/Features/Surveys\|Surveys]] : Designated area/widget for developer surveys to be posted.<br/>Status: ''Awaiting spec''

Fligtar: /* Hosted Content */

2009-05-13T23:34:25Z

Hosted Content

← Older revision		Revision as of 23:34, 13 May 2009
Line 11:		Line 11:

	== Hosted Content ==		== Hosted Content ==
	; [[AMO:Projects/developer.AMO/Features/Policies\|AMO Policies]] : Policies for hosting add-ons on the site, review guidelines, etc.		; 1.4 [[AMO:Projects/developer.AMO/Features/Policies\|AMO Policies]] : Policies for hosting add-ons on the site, review guidelines, etc.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Case_Studies\|Case Studies]] : Case studies of add-ons		; 1.5 [[AMO:Projects/developer.AMO/Features/Case_Studies\|Case Studies]] : Case studies of add-ons<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Repo\|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.		; 1.6 [[AMO:Projects/developer.AMO/Features/Repo\|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.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Tools\|Developer Tools]] : The Developer Tools part of AMO will stay where it is, but should be reskinned and otherwise associated with the developer site.		; 1.7 [[AMO:Projects/developer.AMO/Features/Tools\|Developer Tools]] : The Developer Tools part of AMO will stay where it is, but should be reskinned and otherwise associated with the developer site.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Skeletons\|Extension/Theme skeletons]] : Provide downloadable, documented skeletons for major extension types, such as a toolbar, sidebar, statusbar extension.		; 1.8 [[AMO:Projects/developer.AMO/Features/Skeletons\|Extension/Theme skeletons]] : Provide downloadable, documented skeletons for major extension types, such as a toolbar, sidebar, statusbar extension.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/News\|Metrics]] : We should display developer-related metrics such as average time in queue and others TBD.		; 1.9 [[AMO:Projects/developer.AMO/Features/News\|Metrics]] : We should display developer-related metrics such as average time in queue and others TBD.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/BPD\|Best Practices Documents]] : We should create Best Practices Documents on important topics like Security, Performance, and Usability		; 1.10 [[AMO:Projects/developer.AMO/Features/BPD\|Best Practices Documents]] : We should create Best Practices Documents on important topics like Security, Performance, and Usability<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Forums\|Forums]] : Forums for extension development support, add-on ideas, etc.		; 1.11 [[AMO:Projects/developer.AMO/Features/Forums\|Forums]] : Forums for extension development support, add-on ideas, etc.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Surveys\|Surveys]] : Designated area/widget for developer surveys to be posted.		; 1.12 [[AMO:Projects/developer.AMO/Features/Surveys\|Surveys]] : Designated area/widget for developer surveys to be posted.<br/>Status: ''Awaiting spec''

Fligtar: /* Aggregated Content */

2009-05-13T23:33:05Z

Aggregated Content

← Older revision		Revision as of 23:33, 13 May 2009
Line 6:		Line 6:

	== Aggregated Content ==		== Aggregated Content ==
	; [[AMO:Projects/developer.AMO/Features/News\|Developer News]] : ~~Widget~~ on ~~homepage with latest articles from AMO blog in developers category.~~		; 1.1 [[AMO:Projects/developer.AMO/Features/News\|Developer News]] : News of interest to Add-on Developers<br/>Status: ''Spec'd; awaiting design''
	; [[AMO:Projects/developer.AMO/Features/Events\|Upcoming Events]] : ~~Widget~~ on ~~homepage with upcoming events from AMO blog in events category~~		; 1.2 [[AMO:Projects/developer.AMO/Features/Events\|Upcoming Events]] : Upcoming events of interest to Add-on Developers<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Documentation\|Documentation, Tutorials, Code Samples]] : Links to relevant documentation on MDC and other content		; 1.3 [[AMO:Projects/developer.AMO/Features/Documentation\|Documentation, Tutorials, Code Samples]] : Links to relevant documentation on MDC and other content<br/>Status: ''Awaiting spec''

	== Hosted Content ==		== Hosted Content ==

Fligtar at 23:10, 13 May 2009

2009-05-13T23:10:41Z

Fligtar: /* Hosted Content */

2009-05-10T19:46:47Z

Hosted Content

← Older revision		Revision as of 19:46, 10 May 2009
Line 13:		Line 13:
	; 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 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.		; 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.		; 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.		; Extension/Theme skeletons : Provide downloadable, documented skeletons for major extension types, such as a toolbar, sidebar, statusbar extension.

Fligtar at 19:45, 10 May 2009

2009-05-10T19:45:45Z

← Older revision		Revision as of 19:45, 10 May 2009
Line 1:		Line 1:
	= developer.AMO Features =		= developer.AMO Features =

	<span style="font-weight: bold; color: red">Please post comments on the ~~Talk page,~~ blog post, or newsgroup -- ~~but~~ not here.</span>		<span style="font-weight: bold; color: red">Please post comments on the blog post or [http://groups.google.com/group/mozilla.dev.amo/topics AMO newsgroup] -- not here.</span>

	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 11:		Line 11:

	== Hosted Content ==		== Hosted Content ==
	~~; Forums : Forums for extension development support, add-on ideas, etc.~~
	~~; 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
Line 20:		Line 18:
	; Metrics : We should display developer-related metrics such as average time in queue and others TBD.		; 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		; 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.

Fligtar at 21:51, 8 May 2009

2009-05-08T21:51:59Z

← Older revision		Revision as of 21:51, 8 May 2009
Line 1:		Line 1:
	= developer.AMO Features =		= developer.AMO Features =

	~~'''~~Please post comments on the Talk page, blog post, or newsgroup.~~'''~~		<span style="font-weight: bold; color: red">Please post comments on the Talk page, blog post, or newsgroup -- but not here.</span>

	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.

Fligtar at 21:50, 8 May 2009

2009-05-08T21:50:22Z

← Older revision		Revision as of 21:50, 8 May 2009
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

Fligtar at 19:55, 7 May 2009

2009-05-07T19:55:54Z

← Older revision		Revision as of 19:55, 7 May 2009
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.

Fligtar: 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. ...'

2009-05-07T19:45:20Z

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. ...'

New page

= 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. Therefore, we can break content into two groups: aggregated and hosted.

== Aggregated Content ==
* Developer News (add-ons blog feed)
* Upcoming Events (add-ons blog feed)
* most documentation and tutorials (MDC)
*
== Hosted Content ==
* Forums
* Surveys
* AMO Policies
* Case Studies
* Taggable Searchable Code Repository
* Developer Tools (reskinned but kept on AMO)

← Older revision		Revision as of 23:41, 13 May 2009
Line 16:		Line 16:
	; 1.7 [[AMO:Projects/developer.AMO/Features/Tools\|Developer Tools]] : The Developer Tools part of AMO will stay where it is, but should be reskinned and otherwise associated with the developer site.<br/>Status: ''Awaiting spec''		; 1.7 [[AMO:Projects/developer.AMO/Features/Tools\|Developer Tools]] : The Developer Tools part of AMO will stay where it is, but should be reskinned and otherwise associated with the developer site.<br/>Status: ''Awaiting spec''
	; 1.8 [[AMO:Projects/developer.AMO/Features/Skeletons\|Extension/Theme skeletons]] : Provide downloadable, documented skeletons for major extension types, such as a toolbar, sidebar, statusbar extension.<br/>Status: ''Awaiting spec''		; 1.8 [[AMO:Projects/developer.AMO/Features/Skeletons\|Extension/Theme skeletons]] : Provide downloadable, documented skeletons for major extension types, such as a toolbar, sidebar, statusbar extension.<br/>Status: ''Awaiting spec''
	; 1.9 [[AMO:Projects/developer.AMO/Features/~~News~~\|Metrics]] : We should display developer-related metrics such as average time in queue and others TBD.<br/>Status: ''Awaiting spec''		; 1.9 [[AMO:Projects/developer.AMO/Features/Metrics\|Metrics]] : We should display developer-related metrics such as average time in queue and others TBD.<br/>Status: ''Awaiting spec''
	; 1.10 [[AMO:Projects/developer.AMO/Features/BPD\|Best Practices Documents]] : We should create Best Practices Documents on important topics like Security, Performance, and Usability<br/>Status: ''Awaiting spec''		; 1.10 [[AMO:Projects/developer.AMO/Features/BPD\|Best Practices Documents]] : We should create Best Practices Documents on important topics like Security, Performance, and Usability<br/>Status: ''Awaiting spec''
	; 1.11 [[AMO:Projects/developer.AMO/Features/Forums\|Forums]] : Forums for extension development support, add-on ideas, etc.<br/>Status: ''Awaiting spec''		; 1.11 [[AMO:Projects/developer.AMO/Features/Forums\|Forums]] : Forums for extension development support, add-on ideas, etc.<br/>Status: ''Awaiting spec''
	; 1.12 [[AMO:Projects/developer.AMO/Features/Surveys\|Surveys]] : Designated area/widget for developer surveys to be posted.<br/>Status: ''Awaiting spec''		; 1.12 [[AMO:Projects/developer.AMO/Features/Surveys\|Surveys]] : Designated area/widget for developer surveys to be posted.<br/>Status: ''Awaiting spec''

← Older revision		Revision as of 23:34, 13 May 2009
Line 11:		Line 11:

	== Hosted Content ==		== Hosted Content ==
	; [[AMO:Projects/developer.AMO/Features/Policies\|AMO Policies]] : Policies for hosting add-ons on the site, review guidelines, etc.		; 1.4 [[AMO:Projects/developer.AMO/Features/Policies\|AMO Policies]] : Policies for hosting add-ons on the site, review guidelines, etc.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Case_Studies\|Case Studies]] : Case studies of add-ons		; 1.5 [[AMO:Projects/developer.AMO/Features/Case_Studies\|Case Studies]] : Case studies of add-ons<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Repo\|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.		; 1.6 [[AMO:Projects/developer.AMO/Features/Repo\|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.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Tools\|Developer Tools]] : The Developer Tools part of AMO will stay where it is, but should be reskinned and otherwise associated with the developer site.		; 1.7 [[AMO:Projects/developer.AMO/Features/Tools\|Developer Tools]] : The Developer Tools part of AMO will stay where it is, but should be reskinned and otherwise associated with the developer site.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Skeletons\|Extension/Theme skeletons]] : Provide downloadable, documented skeletons for major extension types, such as a toolbar, sidebar, statusbar extension.		; 1.8 [[AMO:Projects/developer.AMO/Features/Skeletons\|Extension/Theme skeletons]] : Provide downloadable, documented skeletons for major extension types, such as a toolbar, sidebar, statusbar extension.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/News\|Metrics]] : We should display developer-related metrics such as average time in queue and others TBD.		; 1.9 [[AMO:Projects/developer.AMO/Features/News\|Metrics]] : We should display developer-related metrics such as average time in queue and others TBD.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/BPD\|Best Practices Documents]] : We should create Best Practices Documents on important topics like Security, Performance, and Usability		; 1.10 [[AMO:Projects/developer.AMO/Features/BPD\|Best Practices Documents]] : We should create Best Practices Documents on important topics like Security, Performance, and Usability<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Forums\|Forums]] : Forums for extension development support, add-on ideas, etc.		; 1.11 [[AMO:Projects/developer.AMO/Features/Forums\|Forums]] : Forums for extension development support, add-on ideas, etc.<br/>Status: ''Awaiting spec''
	; [[AMO:Projects/developer.AMO/Features/Surveys\|Surveys]] : Designated area/widget for developer surveys to be posted.		; 1.12 [[AMO:Projects/developer.AMO/Features/Surveys\|Surveys]] : Designated area/widget for developer surveys to be posted.<br/>Status: ''Awaiting spec''

← Older revision		Revision as of 23:10, 13 May 2009
Line 6:		Line 6:

	== Aggregated Content ==		== Aggregated Content ==
	; Developer News : Widget on homepage with latest articles from AMO blog in developers category.		; [[AMO:Projects/developer.AMO/Features/News\|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		; [[AMO:Projects/developer.AMO/Features/Events\|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:Projects/developer.AMO/Features/Documentation\|Documentation, Tutorials, Code Samples]] : Links to relevant documentation on MDC and other content

	== Hosted Content ==		== Hosted Content ==
	; AMO Policies : Policies for hosting add-ons on the site, review guidelines, etc.		; [[AMO:Projects/developer.AMO/Features/Policies\|AMO Policies]] : Policies for hosting add-ons on the site, review guidelines, etc.
	; Case Studies : Case studies of add-ons		; [[AMO:Projects/developer.AMO/Features/Case_Studies\|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.		; [[AMO:Projects/developer.AMO/Features/Repo\|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.		; [[AMO:Projects/developer.AMO/Features/Tools\|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.		; [[AMO:Projects/developer.AMO/Features/Skeletons\|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.		; [[AMO:Projects/developer.AMO/Features/News\|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		; [[AMO:Projects/developer.AMO/Features/BPD\|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.		; [[AMO:Projects/developer.AMO/Features/Forums\|Forums]] : Forums for extension development support, add-on ideas, etc.
	; Surveys : Designated area/widget for developer surveys to be posted.		; [[AMO:Projects/developer.AMO/Features/Surveys\|Surveys]] : Designated area/widget for developer surveys to be posted.