Apps/Developers: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 112: Line 112:
{{Draft}}
{{Draft}}


marketplace.m.o/developers should be a one-stop destination for developers.
marketplace.m.o/developers should be a one-stop destination for developers who want to develop open web apps.


=== Developer Hub vs. MDN ===
=== Developer Hub vs. MDN ===

Revision as of 23:01, 26 July 2012

This page contains all of the important details for the Apps Developers project (marketplace.mozilla.org/developers).

Elevator Pitch

Imagine you're a web developer and you want to learn about this Open Web Apps thing. The Apps Developers project focuses on explaining what this is, what you can do with it and how to build a web app, providing you with guidance and resources along the way.

Overview

Project Status

  • Phase 2. (see below)
  • Target release date: Q3 2012 goal

Development Phases

Phase 1: General Apps Landing Page and Tutorial

Phase 2: Turn Developer Hub into a one-stop destination

Draft-template-image.png THIS PAGE IS A WORKING DRAFT Pencil-emoji U270F-gray.png
The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly.
If you have any questions or ideas, please add them as a new topic on the discussion page.

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

Content

Existing/in-progress content

Planned content

  • landing page for potential partners.

Next steps

  • Develop information architecture to tie content together meaningfully (w/TBD UX help)
  • Define scope for upcoming product milestones (w/Caitlin)