Improve overview section of readme.

[Garbee]

From the discussion on feedback in Issue #361 I found the current overview in the readme to be bland and slightly unclear. A good step to solving developer confusion or unease about the project would be to improve this critical section.

Based on this comment I am thinking something like this would be a better overview. The final update however is dependent up on the rest of the discussion in issue #361 since that could change how things are approached.

Overview

Web Starter Kit is an opinionated boilerplate for web development. Tooling for building an experience that works great across multiple devices and is performance oriented. We help you stay productive and aligned with the best practices outlined in Google's Web Fundamentals. A solid starting point for both professionals and newcomers to the industry.

[addyosmani]

Thanks for kicking off a rethink of the current overview, @Garbee. This is solid. It checks off the multi-device focus, performance and manages to be more general in the opening line.

cc @PaulKinlan & @petele for any further thoughts on improvements we can make to the copy here.

[Garbee]

Going over some old reddit threads myself, I notice a lot of 'how does it compare to bootstrap?' posts. We should really find a good way to address the fact that (at least currently, and looking at the discussion in the main thread it looks to stay that way) that WSK is not a direct competitor to full frameworks.

EDIT: duh, great place to address this is the FAQ. And going there to check, of it is already done so this should get floated somehow in the main readme while not being a direct part of the overview.

[addyosmani]

I wonder if we should just flat-out include the text from that portion of the FAQs in the readme as a start. I'm also wondering whether it's worth investing a small amount of time in showing developers how (if they needed to) they could say, add in something like Bootstrap to WSK. Ideally however they should just straight up be using their own styles.

[Garbee]

Adding a doc section on integrating a framework like Bootstrap would be a good step. I assume that developers could see that, then realize they don't need to chose WSK or Bootstrap/insert framework here. They can work together and overall without too much effort. You don't lose frameworks by choosing to use WSK, you gain a good base for workflow/tools that you can add them into.

[Garbee]

Something just hit me...

We help you stay productive and aligned

Should the use of "we" also be avoided in the documentation for this project as is done in the Chrome DevTool Docs?

[addyosmani]

Web Starter Kit helps you stay productive and aligned would be the alternative?

[Garbee]

That or just:

Helping you to stay productive....

Let me run these through hemmingwayapp and see if it complains at all about either. I'd personally prefer this version since it reduces the number of times the name of WSK is mentioned. It should be the object of reference throughout the entire paragraph.

[Garbee]

Each of these methods creates a hard to read sentence (along with the tooling sentence.) I'll work on a cleaner copy and follow-up when it is ready.

[Garbee]

Web Starter Kit is an opinionated boilerplate for web development. Tools for building a great experience across many devices and performance oriented. Helping you to stay productive following the best practices outlined in Google's Web Fundamentals. A solid starting point for both professionals and newcomers to the industry.

Missing links in this copy, but no issues in Hemmingway.

[addyosmani]

Awesome. Want to submit a PR when you're ready? (alternatively I can directly edit)

[Garbee]

Sure thing, I'll PR this in about 40 seconds.