839666 - IA changes for devhub build section

Status: RESOLVED FIXED

(Marketplace Graveyard :: Developer Pages, defect)

Description

[Fred Wenzel [:wenzel]]

In bug 832531, Tony proposes an iteration on the devhub IA.

Tony, please give some guidance on the specific changes to happen to the Build section.

These changes are more extensive. Let's file separate bugs if necessary.

Comment 3

[Tony Santos [:tsmuse]]

The following are the details of the proposed IA changes to the Build section of devhub:

New page: Quick Start
content:
content should be in production via dbuc?

=====
New page: Intro to Open Web Apps
content:
content from existing MDN page at https://developer.mozilla.org/en-US/docs/Open_Web_apps_and_Web_standards

=====
Current page: Firefox OS
changes:
Title to "Intro to Firefox OS"
remove the "Getting help from the community", "Related Topics" and "Resources" sections from existing page. All other content stays the same.

=====
New Page: Reference Apps
content:
What can you do with an Open Web App? What can't you do? Here you'll find some examples of the kind of Open Web Apps that are possible. Use them for inspiration, as example code, or as a jumping off point for your new app. 

Chrono (link to Chrono page)
Chrono is a simple chronometer with lap counter, built to highlight various aspects of the Firefox OS development process. 

Face Value (link to Face Value page)
Face Value is a currency conversion app that does things differently: instead of converting arbitrary amounts it shows you the actual denominations in the country you're visiting. It lets you think in your home currency even with a foreign currency in your pocket.

Roller (link to Roller page)
Roller is a micro blog app that allows you to post text, upload an image or paste a link that has an image extension such as jpg, gif, png or jpeg.

=====
New page: For Current Web Developers
content:
content from existing MDN page at https://developer.mozilla.org/en-US/docs/Apps/For_Web_developers

=====
New page: For Current Mobile Developers
content:
content from existing MDN page at https://developer.mozilla.org/en-US/docs/Apps/For_mobile_developers

=====
New page: Using apps offline
content from existing MDN page at https://developer.mozilla.org/en-US/docs/Apps/Using_apps_offline

=====
New page: Developing Game Apps
content from existing MDN page at https://developer.mozilla.org/en-US/docs/Apps/Developing_game_apps

=====
Current page: Manifests FAQ
changes:
Title to "Intro to Manifests"

=====
New page: Tools
content:
What do you use to build Open Web Apps? The answer is "anything you would normally use to build for the web." The following is a list of tools and resources to help you get started making Open Web Apps. They can be easily integrated into your existing web development workflow, if you have one, or you can build a new workflow around them. 

App Generator (link to new App Generator page)
To help you start writing web apps quickly, we provide a few templates which has a lot already set up. Each template is a static web project with tools to help build and deploy.

App Validator (Link to App Validator https://marketplace.firefox.com/developers/validator)
Is your app ready for the Firefox Marketplace? The App validator will check your manifest and show you any errors it may have, or warnings you should consider.

Firefox OS Simulator (Link to new FFOS Simulator page)
You have a Firefox OS app but you don't have a Firefox OS phone to test it on? The Firefox OS simulator will let you run your app in the browser, so you can test early and often. 

Firefox Developer Tools (link to the Dev Tools page)
Firefox now ships with a default set of developer tools built from the ground up to ensure a great development experience that is both snappy and efficient.

=====
New Page: App Generator
content:
this page is a mashup of the existing Using App Templates and App Generator pages. The content from both pages should be combined in the following order:
* App generator page content
* Introduction (from using app templates) renamed to "Introduction to App Generator templates". The line "You can view all of the available templates in the mortar repo." should be changed to "You can download the templates above, or view all the available templates in the mortar repo." The lines "The following are available: mortar-app-stub: a blank template that comes only with the basic things required to get started mortar-list-detail: comes with a layouts library and sets up a list-detail layout for you mortar-game-stub: a minimal web game template that handles input and a render loop" should be removed.
 
* Tutorial (from using app templates)

=====
New page: Firefox OS Simulator
content:
this page is a mashup of the existing Firefox OS Simulator and Using Firefox OS Simulator pages.The content from both pages should be combined in the following order:
* Develop for Firefox OS without a phone (from Firefox OS Simulator)
* Download (from Firefox OS Simulator)
* All content from Using Firefox OS Simulator page in current order
* Download (from Firefox OS Simulator)

=====

Comment 4

[Fred Wenzel [:wenzel]]

Jen, will you take a look?

For the "content from MDN" and "mashup pages", we'll need to copy-and-paste the content from MDN (no pulling in via API), and then remove said content from MDN (for now, anyway). You can file followup bugs for the removal, so you don't have to do it all yourself and at once.

Comment 5

[Fred Wenzel [:wenzel]]

dbuc: do you still want to reduce the amount of groupings underneath Build, or do you want to land all these links on the front page?

Comment 6

[Daniel Buchner [:dbuc]]

(In reply to Tony Santos [:tsmuse] from comment #3)
> The following are the details of the proposed IA changes to the Build
> section of devhub:

If we want anything better than headings and paragraph tags before MWC, we're going to need implementation-ready mocks delivered by EOD. Is this our goal, or are we ok with the new pages going out very raw?

Comment 7

[Tony Santos [:tsmuse]]

There were no changes to the content templates intended, just text being moved around, added or removed, that's why no mocks were produced. If we want to discuss a graphic design overhaul we can do that after MWC.

Comment 8

[Jen Fong-Adwent [:ednapiranha]]

merged in https://github.com/mozilla/zamboni/commit/d426158a81b9ca34d2553f6611b416679a55ec05