canmove, Confirmed users
737
edits
JetpackWeb: Difference between revisions
→Current Structure
No edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
The diagram below shows the parts of the AMO and MDN web sites that add-on developers looking for documentation must navigate. I’ve highlighted the pages that contain actual developer documentation: | The diagram below shows the parts of the AMO and MDN web sites that add-on developers looking for documentation must navigate. I’ve highlighted the pages that contain actual developer documentation: | ||
[[File: | [[File:Jetpack_web_presence_proposed.png]] | ||
There are a couple of problems with this structure: | There are a couple of problems with this structure: | ||
| Line 40: | Line 40: | ||
* present developers, early on, with the choice of toolset, and given them the information they need to make the right choice. Subsequently, they only see information relevant to that choice. | * present developers, early on, with the choice of toolset, and given them the information they need to make the right choice. Subsequently, they only see information relevant to that choice. | ||
[[File: | [[File:Jetpack_web_presence_current.png]] | ||
From both the AMO and the MDN main page, a fairly prominent link called “Developing Add-ons” or “Developer Hub” or something like that goes to a new page, hosted at MDN - we’ve kept the name “Add-ons Developer Community” here, but it doesn’t have to be called that. | From both the AMO and the MDN main page, a fairly prominent link called “Developing Add-ons” or “Developer Hub” or something like that goes to a new page, hosted at MDN - we’ve kept the name “Add-ons Developer Community” here, but it doesn’t have to be called that. | ||