Guide for setting up and hosting node/iojs apps

[jandet-zz]

When our ops and web teams were researching how to set up and host a node app, we had trouble finding updated and comprehensive guides for this. In contrast, setting up app serving in python, etc. has a wealth of information and resources online (ops pointed out to me that maybe python engineers "just like to nerd out about this stuff" but let's not let them think we don't like to as well!). I imagine this may be a point of turnoff for other teams who are also looking to use node in production.

Since the iojs team is all about progress and stability, I would suggest providing at the very least a section that includes links to the best resources and guides to learn how to host & maintain node/iojs apps effectively.

[therebelrobot]

+1. This would be an excellent guide to have in our future guide section.

[domenic]

Contrast with Ruby and Rails:

• Extensive getting started documentation one click away from the Ruby homepage: https://www.ruby-lang.org/en/documentation/
• Rails has a giant "Get Started" button on the homepage that leads to http://rubyonrails.org/download/, and apparently more information inside http://localhost:3000 once the server is up and running.
• Rails also has a Documentation link that, after one more click, takes you to http://guides.rubyonrails.org/; yet another click and you get to http://guides.rubyonrails.org/getting_started.html, which is excellent.

[snostorm]

Our build process is 90% there to help us rapidly add new content now. Getting some volunteer efforts now in writing the content (and formatting/organizing it) are the next steps 👍

One of my goals from the start has been to get us a "Guides" section. I think this content suggestion is a great suggestion @jandet! Thanks

[snostorm]

http://emberjs.com/guides/ is another good source of inspiration I'd say. So much more we can be doing :)

[mikeal]

If we're gearing up to add a lot of content we should make sure that is worked in to the new design.

[Fishrock123]

The new design needs to be able to support generic content pages, just as it does now for the es6 article.

[bnb]

This is an issue that can be handled by the Docs WG. I've marked it as invalid and docs to ensure its responsibility is handed to the Docs WG. If you want to discuss this issue, see nodejs/docs#10.