This repository was archived by the owner on Apr 4, 2025. It is now read-only.
This repository was archived by the owner on Apr 4, 2025. It is now read-only.
Landing Page Re-Thinking #152
Open
Description
Problems (as opined by @davideast and @jeffbcross):
- It's ugly, feels cold and unwelcoming, feels outdated
- Too much information on one page. This page should primarily act as a feeder to other content.
- Primary calls to action (view on Github and Download) don't reflect actual goals
- Confusing navigation. E.g. Learn link takes users away from the controlled experience, "Develop" isn't clear that this is where Docs live.
- Random content thrown onto page (videos take a lot of space, random codeschool link)
- Tiny fonts with lots of text, makes users less likely to read (too much time commitment)
- 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.
- Edit Me links cause SSL warning because they post to non-https.
Proposals:
- 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)
- Start with fresh content outline for the page, and write content more purposefully and succinctly
- Relevant, targeted content and calls to action above the fold. (TBD what is most relevant)
- Re-think navigation from user perspective
- Create parts of IA to allow for content that's currently randomly placed throughout page