*.angularjs.org Information Architecture

[jeffbcross]

Let's re-imagine:

• Who angularjs.org caters to
• What content is most valuable to these folks
• How to best organize this content

This issue can be considered resolved when:

• The needs of users visiting the sites have been defined
• Content hierarchy of content on the sites has been agreed upon, final approval from @IgorMinar (ideally this would be represented by a graphic)

The scope of this discussion is primarily concerned with, but not limited to, www.angularjs.org and docs.angularjs.org.