Apps/Developers: Difference between revisions

transcribed whiteboard content
(transcribed whiteboard content)
Line 12: Line 12:
* Code: Django (part of Zamboni = AMO/Marketplace)
* Code: Django (part of Zamboni = AMO/Marketplace)
* Product Owner: Daniel Buchner
* Product Owner: Daniel Buchner
* Dev Team: Arron Schaar (dev)
* Dev Team: Arron Schaar (dev), Jen Fong (dev)
* IRC Channel: [irc://irc.mozilla.org:6697/devecosystem #devecosystem on irc.mozilla.org]
* IRC Channel: [irc://irc.mozilla.org:6697/devecosystem #devecosystem on irc.mozilla.org]


Line 18: Line 18:
* Phase 2. (see below)
* Phase 2. (see below)
* Target release date: Q3 2012 [https://intranet.mozilla.org/2012Q3Goals#Web_Development goal]
* Target release date: Q3 2012 [https://intranet.mozilla.org/2012Q3Goals#Web_Development goal]
== Developer Hub vs. MDN ==
To avoid confusion and duplication, the distinction between the developer hub and MDN is important:
Devhub:
* provides tutorials and end-to-end guide from ideation to publishing/maintaining an app
* outlines platform capabilities
* links to resources
* provides links to download key developer products, like development templates, web components
* has examples and excerpts
* limited scope to "interesting aspects" of the apps stack
* does '''not''' go into nitty-gritty details of APIs and all conceivable tools
MDN:
* Canonical source of all docs content, even the content displayed as part of the dev hub (devhub pulls specific data from MDN)
* has in-detail API documentation, for all relevant APIs
* covers the entire web stack


= Development Phases =
= Development Phases =
Line 113: Line 130:


marketplace.m.o/developers should be a one-stop destination for developers who want to develop open web apps.
marketplace.m.o/developers should be a one-stop destination for developers who want to develop open web apps.
=== Developer Hub vs. MDN ===
To avoid confusion and duplication, the distinction between the developer hub and MDN is important:
Devhub:
* provides tutorials and end-to-end guide from ideation to publishing/maintaining an app
* outlines platform capabilities
* links to resources
* provides links to download key developer products, like development templates, web components
* has examples and excerpts
* limited scope to "interesting aspects" of the apps stack
* does '''not''' go into nitty-gritty details of APIs and all conceivable tools
MDN:
* Canonical source of all docs content, even the content displayed as part of the dev hub (devhub pulls specific data from MDN)
* has in-detail API documentation, for all relevant APIs
* covers the entire web stack


=== DebHub Structure ===
=== DebHub Structure ===
Line 141: Line 141:
* [http://people.mozilla.com/~fwenzel/files/debhub/wb-support.jpg Support]
* [http://people.mozilla.com/~fwenzel/files/debhub/wb-support.jpg Support]


==== Proposed Page Structure ====
cf. whiteboard drafts for sketches
* Global structure, always visible:
** Front page (placeholder. "Developer Hub", perhaps?)
** Developers
** Partners
** Support
* Front page sections:
** Platform pitch (borrow from phase 1 content)
** Developers (link to tutorials for webdevs, native devs, and to tools section)
** Partners (content tbd)
* Developers page:
** Get started
*** HTML5 etc. (technology basics)
*** Manifests etc (parts of an open web app)
*** Application types / security model (TBD)
*** example apps
** Design it
*** (subsections as developed by [[Apps/Design]] project)
** Code it
*** templates
*** emulators
*** web components (x-tags)
** Publish it
*** Marketplace submission
*** Hosting / packaging
*** Payments
*** Metrics
*** Updates
** Partners page:
*** Content TBD


=== Content pieces ===
=== Content pieces ===
Confirmed users
1,209

edits