* Add Advanced Configuration section
* Reference package.json instead
* Add HOST, HTTPS, and CI
* Switch wording from Amazon to a CDN
* Add test runner comment
* Add top-level README link
* Simplify wording
* Link to relevant docs
* Link to apps
* Add .env link
* Simpler links
* Add a CI flag note
* 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
* 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
* 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
* 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
* 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
* 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.
