René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Landing Page Re-Thinking","articleBody":"Problems (as opined by @davideast and @jeffbcross):\n- It's ugly, feels cold and unwelcoming, feels outdated\n- Too much information on one page. This page should primarily act as a feeder to other content.\n- Primary calls to action (view on Github and Download) don't reflect actual goals\n- Confusing navigation. E.g. Learn link takes users away from the controlled experience, \"Develop\" isn't clear that this is where Docs live.\n- Random content thrown onto page (videos take a lot of space, random codeschool link)\n- Tiny fonts with lots of text, makes users less likely to read (too much time commitment)\n- Examples are lacking context (Ie the basics requires interaction with annotations before anything is explained). There should probably be one in-context example that gives the gist of Angular, and links to other documentation.\n- Edit Me links cause SSL warning because they post to non-https.\n\nProposals:\n- Think more about the experience for these types of users: developers who are new to Angular (What's Angular about?), advanced angular developers looking for specific reference (How do I use this service?), occasional developer looking for tutorial or guide (What's the best way to define a complex directive), (secondary user: non-developers curious about angular)\n- Start with fresh content outline for the page, and write content more purposefully and succinctly\n- Relevant, targeted content and calls to action above the fold. (TBD what is most relevant)\n- Re-think navigation from user perspective\n- Create parts of IA to allow for content that's currently randomly placed throughout page\n","author":{"url":"https://github.com/jeffbcross","@type":"Person","name":"jeffbcross"},"datePublished":"2015-01-08T20:31:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/152/angularjs.org/issues/152"}