* Add a more prominent link to the guide

As a contributor, I know where to find the documentation/guide since
know the codebase, but I've seen people miss the link to it in the
README, because it's not very prominent. Let's try to make it more
discoverable by including a link to it right on top of the page.

* Make the wording of links more obvious

* Rename the "How Do I...?" section to "User Guide" for consistency

* ignore .idea folder
this change is requred for IntelliJ-based products because project information files are written before actual generator is invoked

* better method name and explanation

Shameless plug of course.

If you want hot reloading and the best DX experience (friendly errors, desktop notifications, decorators, very fast reload times with dlls...) you should really check out [The Awsesom REact Cli](https://github.com/geowarin/tarec) (tarec).

I have used it in numerous projects that now run in production and I continue to make it better day after day with a lot of love 

Typescript and SSR are on the roadmap!

Thanks for create-react-app, it's an awesome project and a great source of inspiration 

Remove the `include` setting from webpack loaders for CSS, JSON and other static assets.
This way it's possible to import files from a separate config folder, a parent directory etc.

* Started using babel-preset-latest

* Updated babel dependencies

* Remove redundant babel-plugin-syntax-async-functions

* Disabled redundant regenerator transform

* Get latest version numbers of react and react-dom from npm before install.

* Run separate npm installs for react, react-dom, and react-test-renderer.

* Consolidate into a single npm install.

* Fix misplaced parenthesis, add missing semicolon.

* Add missing semicolon.

According to the official SemVer FAQ, versioning should start at 0.1.0 (http://semver.org/#how-should-i-deal-with-revisions-in-the-0yz-initial-development-phase)

Small typo line 572 "becasue" to "because"

This rule is considered dangerous in certain situations. This is especially true for Immutable.js users. See the discussion at issue #465 for more information about this.

* add off font format to loaders

* add otf format support

This will work correctly when there are duplicate filenames in different paths.
Fixes: #445

* Load favicon through html-loader.

Fixes #291.

* Add test for *.ico in e2e test suite

* Configure html-loader to process <link href="...">

* Address feedback on html-loader inclusion.

* Place favicon.ico at the root of the build dir

* Make comment style consistent between prod and dev webpack configs

* Fix html-loader config in dev mode

Ref #387

Thanks to @geowarin for the tip in https://github.com/facebookincubator/create-react-app/issues/401#issuecomment-238291901

* Add Surge.sh to deploy instructions

* Add it also to the Table of Contents

Fixes #391

* Creating a new app in the current directory

* Fixed style mistakes

Disable timer mocking and enable verbose output.

Fixes #377

* Small grammatical correction

* Fix another grammatical error for consistency