* Fix paths in CSS files when homepage is set to "./"

In the production build, ExtractTextPlugin is used to generate a separate CSS file instead of injecting style through JavaScript. This plugin does not work well by default with nested output structure. To fix it, we give it a relative publicPath pointing to the build folder.

* Add section in README to explain how to make builds deployable anywhere

* Apply review requested change

* Apply review changes 2

* clarifying the use of custom environment variables

* Tweak

Updated README.md to refer to the current rebranding.

* Add ESLint config for VS Code users

* Update VSC ESLint note to a better solution 

Update VSC ESLint note to a better solution as discussed in Pull Request

* Reflect websocket proxy support on README

* Add 'the'

Per final comment in #372

`Snapshot rendering should actually be pretty stable / useable after React 15.4.1.
See this post for more info.`

* Added Rails link to User Guide

* docs: unify sections for rails and node backend integration

* docs: fix faulty link and indentation

* Add causes of dev server not detecting changes

Add causes of `npm start` not detecting changes to Troubleshooting chapter of User Guide

* Reworded slightly

* Update README.md

* Adds note on how to resolve file or directory not found errors for heroku deployments

* Style tweaks

* Add "Changing the Page Title" to User Guide

* Add link to main README

* Add syntax highlighting configuration guide.

* Update link.

* Add deploy to Firebase CDN on template's README (Closes #374)

* Move section and minor tweaks

* Document what npm build does and pushState

* Fix typos, add express example

* Tweaks

* Update README.md

* Add "npm run build silently fails" to Troubleshooting

* Update README.md

* Added functionality to crash the build during CI whenever linter warnings are encountered.

* Updated the docs with a description on how to use the build in CI

* Fixed small typo

* Fixed description of build error.

* Add a note for OSX users about watchman and jest

Minor additional information on how to solve watchman problems reported in #713 and #1767

* Introduced new Troubleshooting section

Add better explanation how to solve #713 and linked related Issues.

* Tweak wording and add it to TOC

* Adds to docs - deployment with S3/CloudFront

* Tweaks

* Added info on using global variables.

See issue #972.

* Fixed typo.

* Moved new section.

* Small tweaks

* Syntax highlighting

* Add Storybook to the user guide

* Add the missing "Snapshot Testing" link.

* Change the title to something nicer

Old title was looks like a marketing pitch. Change it to something looks great.
The new one is: Developing UI Components with React Storybook.

* Mention React Storybook as a third party tool.

* Nits

* Minor changes

* Always build before deploying to gh-pages

* Add line to gh-pages deploy docs about CNAME file

* Remove spaces in npm run command for Windows

* Grammar nit

* Minor tweaks

gh-pages supports https. It's important for prominent help files to encourage best practices.

* Update dependencies

* Use published version of eslint-config-react-app for development

We dogfood on our eslint-config-react-app by using it as our ESLint config,
but installing it from the local folder causes problems when its peerDependencies
are updated, because npm won't update it unless the version number changes.

Use the published version for dogfooding so it can be installed from npm.