AMO:Projects/developer.AMO/Features: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| 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. | ||
Revision as of 23:10, 13 May 2009
developer.AMO Features
Please post comments on the blog post or AMO newsgroup -- not here.
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
- 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
Hosted 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.