react_on_rails 2.0.2 → 2.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: c2f1692d27068c5ff56f536cb757df449c45f24b
-  data.tar.gz: 318551a2d916e05290e9016c3b6b711e5626df6c
+  metadata.gz: fb99dea8d39f2e84fd72b80d73d7333815b40bf9
+  data.tar.gz: bfdf9b5e78fbfe0449500ad8e033b5d5ca7806f4
 SHA512:
-  metadata.gz: bccce7baf521f616d7e3114e4ec3a1ce76d838c2079255ae842f17190c92b732a664f72bff6fc750b8751bbfd8e482ace93573c5b61d84767a8c4c376cbcdc80
-  data.tar.gz: cd5e62885e22cf3f30e3402f65dc2e4d1d25adbeb9e1a941848821e73315c9ccd2408e8de4f8c49d45d25c3ed145611b6cbfc097222c2f2cff7b0aa89d66811c
+  metadata.gz: 35bb78629f6618a2551559b052eda1e8fe5d5ab1929716881d617fbb9c6b3fa4204d0c16f2513243825cc68a96aefd394940ae4f76cab8e7d48c1ef4b2fbb159
+  data.tar.gz: c944b722816f3fb8e87392b223d43f09d7ff1ab26bf3c546ce86fe50c618d603c5a5b44d7c60be2df94253a0f51ad08e2a101a0a4e5cb634a8ac94bd11515f70

data/.eslintignore

@@ -5,3 +5,7 @@ spec/dummy
 node_package/lib/
 node_package/tests/node_modules
 node_package/webpack.config.js
+**/node_modules/**
+**/generated/**
+**/app/assets/javascripts/application.js
+**/coverage/**

data/.gitignore

@@ -20,9 +20,10 @@
 .ruby-gemset
 
 node_modules
-/examples
 
 /node_package/lib
 
 npm-debug.*
 spec/dummy/client/npm-debug.log.*
+
+/gen-examples

data/.npmignore

@@ -18,3 +18,5 @@ rakelib
 ruby-lint.yml
 spec
 node_modules
+tmp
+gen-examples

data/.rubocop.yml

@@ -20,7 +20,7 @@ AllCops:
     - !ruby/regexp /old_and_unused\.rb$/
     - 'spec/react_on_rails/dummy-for-generators/**/*'
     - 'spec/dummy/bin/**/*'
-    - 'examples/**/*'
+    - 'gen-examples/examples/**/*'
 
 Metrics/LineLength:
   Max: 120
@@ -43,7 +43,7 @@ Lint/HandleExceptions:
 
 # Offense count: 1
 Metrics/AbcSize:
-  Max: 23
+  Max: 24
 
 # Offense count: 1
 # Configuration parameters: CountComments.
@@ -69,4 +69,3 @@ Metrics/ModuleLength:
 Style/GlobalVars:
   Exclude:
     - 'spec/dummy/config/environments/development.rb'
-

data/CHANGELOG.md

@@ -1,7 +1,34 @@
 # Change Log
 All notable changes to this project will be documented in this file. Items under `Unreleased` is upcoming features that will be out in next version.
 
-## v2.0.0
+Contributors: please follow the recommendations outlined at [keepachangelog.com](http://keepachangelog.com/). Please use the existing headings and styling as a guide, and add a link for the version diff at the bottom of the file. Also, please update the `Unreleased` link to compare to the latest release version.
+
+## [Unreleased]
+
+## [2.1.0] - 2016-01-26
+##### Added
+- Added EnsureAssetsCompiled feature so that you do not accidentally run tests without properly compiling the JavaScript bundles. Add a line to your `rails_helper.rb` file to check that the latest Webpack bundles have been generated prior to running tests that may depend on your client-side code. See [docs](docs/additional_reading/rspec_configuration.md) for more detailed instructions. [#222](https://github.com/shakacode/react_on_rails/pull/222)
+- Added [migration guide](https://github.com/shakacode/react_on_rails#migrate-from-react-rails) for migrating from React-Rails. [#219](https://github.com/shakacode/react_on_rails/pull/219)
+- Added [React on Rails Doctrine](docs/doctrine.md) to docs. Discusses the project's motivations, conventions, and principles. [#220](https://github.com/shakacode/react_on_rails/pull/220)
+- Added ability to skip `display:none` style in the generated content tag for a component. Some developers may want to disable inline styles for security reasons. See generated config [initializer file](lib/generators/react_on_rails/templates/base/base/config/initializers/react_on_rails.rb#L27) for example on setting `skip_display_none`. [#218](https://github.com/shakacode/react_on_rails/pull/218)
+
+##### Changed
+- Changed message when running the dev (a.k.a. "express" server). [#227](https://github.com/shakacode/react_on_rails/commit/543ae70254d0c7b477e2c92af86f40746e58a431)
+
+##### Fixed
+- Fixed handling of Turbolinks. Code was checking that Turbolinks was installed when it was not yet because some setups load Turbolinks after the bundles. The changes to the code will check if Turbolinks is installed after the page loaded event fires. Code was also added to allow easy debugging of Turbolinks, which should be useful when v5 of Turbolinks is released shortly. Details of how to configure Turbolinks with troubleshooting were added to docs/additional_reading/turbolinks.md. [#221](https://github.com/shakacode/react_on_rails/pull/221)
+- Fixed issue with already initialized constant warning appearing when starting a Rails server [#226](https://github.com/shakacode/react_on_rails/pull/226)
+- Fixed to make backwards compatible with Ruby v2.0 and updated all Ruby and Node dependencies.
+
+---
+
+## [2.0.2]
+- Added better messages after generator runs. [#210](https://github.com/shakacode/react_on_rails/pull/210)
+
+## [2.0.1]
+- Fixed bug with version matching between gem and npm package.
+
+## [2.0.0]
 - Move JavaScript part of react_on_rails to npm package 'react-on-rails'.
 - Converted JavaScript code to ES6! with tests!
 - No global namespace pollution. ReactOnRails is the only global added.
@@ -39,7 +66,7 @@ Best done with Object destructing:
 - JS Linter uses ShakaCode JavaScript style: https://github.com/shakacode/style-guide-javascript
 - Generators account these differences.
 
-### Migration Steps
+##### Migration Steps
 [Example of upgrading](https://github.com/shakacode/react-webpack-rails-tutorial/commit/5b1b8698e8daf0f0b94e987740bc85ee237ef608)
 
 1. Update the `react_on_rails` gem.
@@ -51,42 +78,46 @@ Best done with Object destructing:
 7. Run `cd client && npm i --save react-on-rails` to get react-on-rails into your `client/package.json`.
 8. You should also update any other dependencies if possible to match up with the [react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial/).
 
-## v1.2.2
-### Fixed
+---
+
+## [1.2.2]
+##### Fixed
 - Missing Lodash from generated package.json [#175](https://github.com/shakacode/react_on_rails/pull/175)
 - Rails 3.2 could not run generators [#182](https://github.com/shakacode/react_on_rails/pull/182)
 - Better placement of jquery_ujs dependency [#171](https://github.com/shakacode/react_on_rails/pull/171)
 - Add more detailed description when adding --help option to generator [#161](https://github.com/shakacode/react_on_rails/pull/161)
 - Lots of better docs.
 
-## v1.2.0
-### Added
+## [1.2.0]
+##### Added
 - Support `--skip-bootstrap` or `-b` option for generator.
 - Create examples tasks to test generated example apps.
 
-### Fixed
+##### Fixed
 - Fix non-server rendering configuration issues.
 - Fix application.js incorrect overwritten issue.
 - Fix Gemfile dependencies.
 - Fix several generator issues.
 
-### Removed
-- Remove templates/client folder.
+##### Removed
+- Removed templates/client folder.
+
+---
 
 ## [1.1.1] - 2015-11-28
-### Added
+##### Added
 - Support for React Router.
 - Error and redirect handling.
 - Turbolinks support.
 
-### Fixed
+##### Fixed
 - Fix several generator related issues.
 
-### Deprecated
-- Nothing.
-
-### Removed
-- Nothing.
-
-[Unreleased]: https://github.com/shakacode/react_on_rails/compare/v1.0.0...HEAD
-[1.1.1]: https://github.com/shakacode/react_on_rails/compare/v1.0.0...v1.1.1
+[Unreleased]: https://github.com/shakacode/react_on_rails/compare/v2.1.0...HEAD
+[2.1.0]: https://github.com/shakacode/react_on_rails/compare/v2.0.2...v2.1.0
+[2.0.2]: https://github.com/shakacode/react_on_rails/compare/v2.0.1...v2.0.2
+[2.0.1]: https://github.com/shakacode/react_on_rails/compare/v2.0.0...v2.0.1
+[2.0.0]: https://github.com/shakacode/react_on_rails/compare/v1.2.2...v2.0.0
+[1.2.2]: https://github.com/shakacode/react_on_rails/compare/v1.2.0...v1.2.2
+[1.2.0]: https://github.com/shakacode/react_on_rails/compare/v1.1.0...v1.2.0
+[1.1.1]: https://github.com/shakacode/react_on_rails/compare/v1.1.1...v1.0.0

data/README.md

@@ -2,16 +2,19 @@
 
 # NEWS
 
-* 2.0 has shipped! Please grab the latest and let us know if you see any issues! [Migration steps from 1.x](https://github.com/shakacode/react_on_rails/blob/master/CHANGELOG.md#migration-steps).
-* It does not yet have *generator* support for building new apps that use CSS modules and hot reloading via the Rails server as is demonstrated in the [shakacode/react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial/). *We do support this, but we don't generate the code.* If you did generate a fresh app from react_on_rails and want to move to CSS Modules, then see [PR 175: Babel 6 / CSS Modules / Rails hot reloading](https://github.com/shakacode/react-webpack-rails-tutorial/pull/175). Note, while there are probably fixes after this PR was accepted, this has the majority of the changes. See [the tutorial](https://github.com/shakacode/react-webpack-rails-tutorial/#news) for more information. Ping us if you want to help!
+* 2.1 is almost ready and will probably ship on Monday, 1/25/2016. Please grab the latest and let us know if you see any issues! [Migration steps from 1.x](https://github.com/shakacode/react_on_rails/blob/master/CHANGELOG.md#migration-steps).
+* React on Rails does not yet have *generator* support for building new apps that use CSS modules and hot reloading via the Rails server as is demonstrated in the [shakacode/react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial/). *We do support this, but we don't generate the code.* If you did generate a fresh app from react_on_rails and want to move to CSS Modules, then see [PR 175: Babel 6 / CSS Modules / Rails hot reloading](https://github.com/shakacode/react-webpack-rails-tutorial/pull/175). Note, while there are probably fixes after this PR was accepted, this has the majority of the changes. See [the tutorial](https://github.com/shakacode/react-webpack-rails-tutorial/#news) for more information. Ping us if you want to help!
 
 # React on Rails
 
-**Project Objective**: To provide an opinionated and optimal framework for integrating **Ruby on Rails** with modern JavaScript tooling and libraries, including [**Webpack**](http://webpack.github.io/), [**Babel**](https://babeljs.io/), [**React**](https://github.com/rackt/react-router), [**Redux**](https://github.com/rackt/redux), [**React-Router**](https://github.com/rackt/react-router). This differs significantly from typical Rails. When considering what goes into **react_on_rails**, we ask ourselves, is the functionality related to the intersection of using Rails and with modern JavaScript? If so, then the functionality belongs right here. In other cases, we're releasing separate npm packages or Ruby gems.
+**Project Objective**: To provide an opinionated and optimal framework for integrating **Ruby on Rails** with modern JavaScript tooling and libraries, including [**Webpack**](http://webpack.github.io/), [**Babel**](https://babeljs.io/), [**React**](https://github.com/rackt/react-router), [**Redux**](https://github.com/rackt/redux), [**React-Router**](https://github.com/rackt/react-router). This differs significantly from typical Rails. When considering what goes into **react_on_rails**, we ask ourselves, is the functionality related to the intersection of using Rails and with modern JavaScript? If so, then the functionality belongs right here. In other cases, we're releasing separate npm packages or Ruby gems. If you are interested in implementing React using traditional Rails architecture, see [react-rails](https://github.com/reactjs/react-rails).
 
 React on Rails integrates Facebook's [React](https://github.com/facebook/react) front-end framework with Rails. React v0.14.x is supported, with server rendering. [Redux](https://github.com/rackt/redux) and [React-Router](https://github.com/rackt/react-redux) are supported as well. See the Rails on Maui [blog post](http://www.railsonmaui.com/blog/2014/10/03/integrating-webpack-and-the-es6-transpiler-into-an-existing-rails-project/) that started it all!
 
-Be sure to see the [React Webpack Rails Tutorial Code](https://github.com/shakacode/react-webpack-rails-tutorial) along with the live example at [www.reactrails.com](http://www.reactrails.com).
+Be sure to see:
+
+* [The React on Rails Doctrine](docs/doctrine.md)
+* [React Webpack Rails Tutorial Code](https://github.com/shakacode/react-webpack-rails-tutorial) along with the live example at [www.reactrails.com](http://www.reactrails.com).
 
 ## Including your React Component in your Rails Views
 Please see [Getting Started](#getting-started) for how to set up your Rails project for React on Rails to understand how `react_on_rails` can see your ReactComponents.
@@ -76,6 +79,7 @@ Please see [Getting Started](#getting-started) for how to set up your Rails proj
         + [Running the Linters](#running-the-linters)
 + [Developing with the Webpack Dev Server](#developing-with-the-webpack-dev-server)
 + [Adding Additional Routes for the Dev Server](#adding-additional-routes-for-the-dev-server)
++ [Migrate From react-rails](#migrate-from-react-rails)
 + [Additional Reading](#additional-reading)
 + [Contributing](#contributing)
 + [License](#license)
@@ -350,6 +354,23 @@ Note that **React-related error messages are typically significantly more helpfu
 ### Adding Additional Routes for the Dev Server
 As you add more routes to your front-end application, you will need to make the corresponding API for the dev server in `client/server.js`. See our example `server.js` from our [tutorial](https://github.com/shakacode/react-webpack-rails-tutorial/blob/master/client/server.js).
 
+## Migrate From react-rails
+If you are using [react-rails](https://github.com/reactjs/react-rails) in your project, it is pretty simple to migrate to [react_on_rails](https://github.com/shakacode/react_on_rails).
+
+- Remove the 'react-rails' gem from your Gemfile.
+
+- Remove the generated generated lines for react-rails in your application.js file. 
+
+```
+//= require react
+//= require react_ujs
+//= require components
+```
+
+- Follow our getting started guide: https://github.com/shakacode/react_on_rails#getting-started.
+
+Note: If you have components from react-rails you want to use, then you will need to port them into react_on_rails which uses webpack instead of the asset pipeline.
+
 ## Additional Reading
 + [Generated Client Code](docs/additional_reading/generated_client_code.md)
 + [Heroku Deployment](docs/additional_reading/heroku_deployment.md)
@@ -357,11 +378,23 @@ As you add more routes to your front-end application, you will need to make the
 + [Node Dependencies and NPM](docs/additional_reading/node_dependencies_and_npm.md)
 + [Optional Configuration](docs/additional_reading/optional_configuration.md)
 + [React Router](docs/additional_reading/react_router.md)
++ [RSpec Configuration](docs/additional_reading/rspec_configuration.md)
 + [Server Rendering Tips](docs/additional_reading/server_rendering_tips.md)
 + [Tips](docs/additional_reading/tips.md)
++ [Tutorial for v2.0](docs/tutorial-v2.md), deployed [here](https://shakacode-react-on-rails.herokuapp.com/).
++ [Turbolinks](docs/additional_reading/turbolinks.md)
 + [Webpack Configuration](docs/additional_reading/webpack.md)
 + [Webpack Cookbook](https://christianalfoni.github.io/react-webpack-cookbook/index.html)
 
+## Demos
++ [www.reactrails.com](http://www.reactrails.com)
++ [spec app](spec/dummy): Great simple examples used for our tests.
+  ```
+  cd spec/dummy
+  bundle && npm i
+  foreman start
+  ```
+
 ## Contributing
 Bug reports and pull requests are welcome. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to our version of the [Contributor Covenant](contributor-covenant.org) code of conduct (see [CODE OF CONDUCT](docs/code_of_conduct.md)).
 

data/app/helpers/react_on_rails_helper.rb

@@ -40,11 +40,11 @@ module ReactOnRailsHelper
     # We use this react_component_index in case we have the same component multiple times on the page.
     react_component_index = next_react_component_index
     react_component_name = component_name.camelize # Not sure if we should be doing this (JG)
-    if options[:id].nil?
-      dom_id = "#{component_name}-react-component-#{react_component_index}"
-    else
-      dom_id = options[:id]
-    end
+    dom_id = if options[:id].nil?
+               "#{component_name}-react-component-#{react_component_index}"
+             else
+               options[:id]
+             end
 
     # Setup the page_loaded_js, which is the same regardless of prerendering or not!
     # The reason is that React is smart about not doing extra work if the server rendering did its job.
@@ -61,7 +61,7 @@ module ReactOnRailsHelper
       content_tag(:div,
                   "",
                   class: "js-react-on-rails-component",
-                  style: "display:none",
+                  style: ReactOnRails.configuration.skip_display_none ? nil : "display:none",
                   data: data)
 
     # Create the HTML rendering part

data/docs/additional_reading/rspec_configuration.md

@@ -0,0 +1,10 @@
+# RSpec Configuration
+Because you will probably want to run RSpec tests that rely on compiled webpack assets (typically, your integration/feature specs where `js: true`), you will want to ensure you don't accidentally run tests on missing or stale webpack assets. If you did use stale Webpack assets, you will get invalid test results as your tests do not use the very latest JavaScript code.
+
+ReactOnRails provides a helper method called `configure_rspec_to_compile_assets`. Call this method from inside of the `RSpec.configure` block in your `spec/rails_helper.rb` file, passing the config as an argument.
+
+You can pass an RSpec metatag as an optional second parameter to this helper method if you want this helper to run on examples other than where `js: true` (default). The helper will compile webpack files only once per test run.
+
+If you do not want to be slowed down by re-compiling webpack assets from scratch every test run, you can call `npm run build:client` (and `npm run build:server` if doing server rendering) to have webpack recompile these files in the background, which will be much faster. The helper looks for these processes and will abort recompiling if it finds them to be running.
+
+If you want to use a testing framework other than RSpec, we suggest you implement similar logic.

data/docs/additional_reading/turbolinks.md

@@ -0,0 +1,39 @@
+# Turbolinks
+
+* See [Turbolinks on Github](https://github.com/rails/turbolinks)
+* Currently support 2.5.x of Turbolinks. We plan to update to Turbolinks 5 soon.
+
+## Why Turbolinks?
+As you switch between Rails HTML controller requests, you will only load the HTML and you will 
+not reload JavaScript and stylesheets. This definitely can make an app perform better, even if 
+the JavaScript and stylesheets are cached by the browser, as they will still require parsing.
+
+### Install Checklist
+1. Include the gem "turbolinks".
+1. Included the proper "track" tags when you include the javascript and stylesheet:
+  ```erb
+    <%= stylesheet_link_tag 'application', media: 'all', 'data-turbolinks-track' => true %>
+    <%= javascript_include_tag 'application', 'data-turbolinks-track' => true %>
+  ```
+1. Add turbolinks to your `application.js` file:
+   ```javascript
+   //= require turbolinks
+   ```
+   
+## Troubleshooting
+
+You cans set a global debug flag in your `application.js` to turn on tracing of Turbolinks events
+as they pertain to React on Rails.
+
+1. Add this line to your `application.js`:
+   ```javascript
+   //= require testGlobals
+   ```
+2. Initialie the global debug value of `DEBUG_TURBOLINKS` like this:
+   ```javascript
+   window.DEBUG_TURBOLINKS = true;
+   console.log('window.DEBUG_TURBOLINKS = true;');
+   ```
+   
+This will print out events related to the initialization of the components created with the view 
+helper `react_component`.

data/docs/additional_reading/updating-dependencies.md

@@ -0,0 +1,33 @@
+# Updating Dependencies
+
+If you frequently update you dependencies in small batches, you will avoid large and painful updates later. Then again, if you don't have good tests coverage, it's hazardous to update dependencies at any time.
+
+## Ruby
+
+Delete any unwanted version constraints from your Gemfile and run:
+
+```bash
+bundle update
+```
+
+## NPM
+
+1. Install [npm-check-updates](https://www.npmjs.com/package/npm-check-updates)
+1. Run `npm outdated` and read CHANGELOGs of major updated packages before you update. You might not be ready for some updates.
+1. Run these commands. Note, you may or may not want to remove your npm-shrinkwrap.json if you get some werid conflicts, and you may or may not need to `rm -rf` your `node_modules` directory. 
+
+```
+cd client
+rm npm-shrinkwrap.json
+ncu -u -a
+npm i
+```
+
+Some combinations that I often run:
+
+### remove old installed `node_modules` so you only get what corresponds to package.json
+```
+ncu -u -a && rm -rf node_modules && npm i
+```
+
+Note: newer versions of npm (>3) automatically create a new version of the npm-shrinkwrap.json.

data/docs/coding-style/style.md

@@ -18,7 +18,6 @@ Follow these style guidelines per the linter configuration. Basically, lint your
 ### JavaScript Coding Standards
 * [ShakaCode Javascript](https://github.com/shakacode/style-guide-javascript)
 * Use the [eslint-config-shakacode](https://github.com/shakacode/style-guide-javascript/tree/master/packages/eslint-config-shakacode) npm package with eslint.
-* [AirBnb Javascript](https://github.com/airbnb/javascript)
 * [JSDoc](http://usejsdoc.org/)
 
 ### Git coding Standards

data/docs/contributing.md

@@ -12,7 +12,8 @@ bundle && npm i && rake examples:prepare_all && rake symlink_node_package && rak
 It's critical to configure your IDE/editor to ignore certain directories. Otherwise your IDE might slow to a crawl!
 
 * /coverage
-* /examples
+* /tmp
+* /gen-examples
 * /node_package/lib
 * /node_modules
 * /spec/dummy/app/assets/javascripts/generated

data/docs/doctrine.md

@@ -0,0 +1,78 @@
+# The React on Rails Doctrine
+
+By Justin Gordon, January 24, 2016
+
+This document is an extension and complement to [The Rails Doctrine](http://rubyonrails.org/doctrine/). If you haven't read that document, I suggest you do so first.
+
+As stated in the [React on Rails README](../README.md), the project objective is to provide an opinionated and optimal framework for integrating **Ruby on Rails** with modern JavaScript tooling and libraries. When considering what goes into **react_on_rails**, we ask ourselves, is the functionality related to the intersection of using Rails and with modern JavaScript? A good example is view helper integration of React components on a Rails view. If the answer is yes, then the functionality belongs right here. In other cases, we're releasing separate npm packages or Ruby gems. For example, we needed an easy way to integrate [Twitter Bootstrap](http://getbootstrap.com/) with Webpack, and we released the [npm bootstrap-loader](https://github.com/shakacode/bootstrap-loader/). 
+
+Besides the project objective, let's stick with the "Rails Doctrine" and keep the following in mind.
+
+## Optimize for Programmer Happiness
+The React on Rails setup provides several key components related to front-end developer happiness:
+
+1. [Hot reloading of both JavaScript and CSS](https://gaearon.github.io/react-hot-loader/), via the [webpack dev server](https://webpack.github.io/docs/webpack-dev-server.html). This works for both using an [express server](http://expressjs.com/) to load stubs for the ajax requests, as well as using a live Rails server. **Oh yes**, your Rails server can do hot reloading!
+2. [CSS modules](https://github.com/css-modules/webpack-demo) which remove the madness of a global namespace for CSS. We organize our CSS (Sass, actually) right next to our JavaScript React component files. This means no more creating long class names to ensure that CSS picks up the right styles.
+3. [ES6 JavaScript](http://es6-features.org/#Constants) is a great language for client side coding, much more so than Ruby due to the asynchronous nature of UI programming.
+4. JavaScript libraries and tooling work better in the native node way, rather than via some aspect of Sprockets and the Rails Asset Pipeline. We find way less frustration this way, especially from being able to get the latest advances with the rest of the JavaScript community. Why complicated beautiful JavaScript tooling Rails asset pipeline complexity?
+5. We want our JavaScript from npm. Getting JavaScript from rubygems.org is comparatively frustrating.
+6. Happiness for us is actively participating in open source, so we want to be where the action is, which is with the npm libraries on github.com.
+7. You can get set up on React on Rails **FAST** using our application generator.
+8. By placing all client-side development inside of the `/client` directory, pure JavaScript developers can productively do development separate from Rails. Instead of Rails APIs, stub APIs on an express server can provide a simple backend, allowing for rapid iteration of UI prototypes.
+9. Just because we're not relying on the Rails asset pipeline for ES6 conversion does not mean that we're deploying Rails apps in any different way. We still use the asset pipeline to include our Webpack compiled JavaScript. This only requires a few small modifications, as explained in our doc [Heroku Deployment](additional_reading/heroku_deployment.md).
+
+## Convention over Configuration
+* React on Rails has taken the hard work out of figuring out the JavaScript tooling that works best with Rails. Not only could you spend lots of time researching different tooling, but then you'd have to figure out how to splice it all together. This is where a lot of "JavaScript fatigue" comes from. The following keep the code clean and consistent:
+* [Style Guide](coding-style/style.md)
+* [linters](coding-style/linters.md)
+* [Recommended Project Structure](recommended-project-structure.md)
+
+We're big believers in this quote from the Rails Doctrine: 
+
+> The same goes even when you understand how all the pieces go together. When there’s an obvious next step for every change, we can scoot through the many parts of an application that is the same or very similar to all the other applications that went before it. A place for everything and everything in its place. Constraints liberate even the most able minds.
+
+
+## The Menu Is Omakase
+Here's the chef's selection from the React on Rails community:
+
+### Libraries
+* [Bootstrap](http://getbootstrap.com/), loaded from [bootstrap-loader](https://github.com/shakacode/bootstrap-loader/). Common UI styles.
+* [Lodash](https://lodash.com/): Swiss army knife of utilities.
+* [React](https://facebook.github.io/react/): UI components.
+* [React-Router](https://github.com/rackt/react-router): Provider of deep links for client-side application.
+* [Redux](https://github.com/rackt/redux): Flux implementation (aka "state container").
+
+### JavaScript Tooling
+* [Babel](https://babeljs.io/): Transpiler for ES6 into ES5 and much more.
+* [EsLint](http://eslint.org/) and [Jsrc](http://jscs.info/): JavaScript linters.
+* [Webpack](http://webpack.github.io/): Generator of deployment assets and provider of hot module reloading.
+
+By having a common set of tools, we can discuss what we should or shouldn't be using. Thus, this takes out the "JavaScript Fatigue" from having too many unclear choices in the JavaScript world.
+
+By the way, we're *not* omakase for standard Rails. That would be CoffeeScript. However, the Rails Doctrine makes it clear that non-standard menu choices are certainly welcome!
+
+## No One Paradigm
+React on Rails fits into the "No One Paradigm" of the Rails ecosystem from the perspective that it rocks for client side development with Rails, even though it's a totally different language than the server code written in Ruby.
+
+## Exalt Beautiful Code
+ES5 was ugly. ES6 is beautiful. React is beautiful. Client side code written with React plus Redux, fully linted with the ShakaCode linters, and organized per our recommended project structure is beautiful. Don't take our word for it. Take a look at the component sample code in the [react-webpack-rails-tutorial sample code](https://github.com/shakacode/react-webpack-rails-tutorial/tree/master/client/app/bundles/comments).
+
+## Value Integrated Systems
+Assuming that you're building the type of app that's a good fit for Rails (document/database based with lots of business rules), the tight integration of modern JavaScript with React on top of Ruby on Rails is better than building a pure client side app and separate microservices. Here's why:
+
+* Via React on Rails, we can seamlessly integrate React UI components with Rails.
+* Tight integration allows for trivial set up of server rendering of React on top of Rails, complete with support for fragment caching of the server rendered HTML, and integration with [Turbolinks](https://github.com/rails/turbolinks).
+* Tight integration allows mixing and matching Rails pages with React driven pages, even on the same page. Not every part of a UI requires the high fidelity achievable using React. Many existing apps may have hundreds of standards Rails forms. Support for mixing and matching React with Rails forms provides the best of both worlds.
+
+## Progress over Stability
+React on Rails will maintain an active pace of development, to keep up with:
+
+* Community suggestions.
+* New client side tooling, libraries, and techniques.
+* Updates to Rails.
+
+## Raise a Big Tent
+React on Rails is definitely a part of the big tent of Rails. Plus, React on Rails provides its own big tent. A huge benefit of the React on Rails system is simple integration with Webpack and NPM, allowing integration with almost any library available on [npm](https://www.npmjs.org/)! The integration with Webpack also allows for other Webpack supported build tools.
+
+## Thanks!
+Thanks for reading and being a part of the React on Rails community. Feedback on this document and *anything* in React on Rails is welcome. Please [open an issue](https://github.com/shakacode/react_on_rails/issues/new) or a pull request. If you'd like to join our private Slack channel, please [email](mailto:contact@shakacode.com) us a request.