Doc updates (#2372)

* Fix VS Code debugging instructions + spelling/grammar

* Moar spelling

* Capitalz

* Created a section for RBP forks to clean up the electron stuff and add gretzky's SSR repo

Author: julienben

.github/PULL_REQUEST_TEMPLATE.md

@@ -10,7 +10,7 @@ on something that might not end up being merged into the project.
 Before opening a pull request, please ensure:
 
 - [ ] You have followed our [**contributing guidelines**](https://github.com/react-boilerplate/react-boilerplate/blob/master/CONTRIBUTING.md)
-- [ ] double-check your branch is based on `dev` and targets `dev`
+- [ ] Double-check your branch is based on `dev` and targets `dev` 
 - [ ] Pull request has tests (we are going for 100% coverage!)
 - [ ] Code is well-commented, linted and follows project conventions
 - [ ] Documentation is updated (if necessary)

docs/README.md

@@ -34,7 +34,7 @@
   - [routing](js/routing.md)
 - [Maintenance](maintenance)
   - [Dependency Update](maintenance/dependency.md)
-- [Convert React Boilerplate To Electron App](electron)
+- [Forks](forks)
 
 ## Overview
 

docs/electron/README.md

@@ -0,0 +1,17 @@
+# Forks
+
+## Electron
+
+Electron is a very popular open source library developed by GitHub. It enables the creation of cross-platform desktop applications using HTML, CSS and Javascript. This fork provide steps through which you can kickstart an Electron application using `react-boilerplate`.
+
+Electron provides a combined single runtime of Chromium and Node.js. No server is needed to host your React application. You can simply package the entire source code in a `.exe`, `.dmg` or `.deb` file.
+
+This fork gives you two options:
+
+1. Clone the repository for a fresh start: [reactron](https://github.com/mjangir/reactron)
+
+2. Read the steps to [convert an existing RBP-based project to an Electron application](https://github.com/mjangir/reactron/wiki/Convert-Existing-To-Electron)
+
+## Server-side rendering
+
+This repo receives many requests for server-side rendering and there have been plenty of long discussions on the topic. None have led to an implementation that we're happy to merge into the main repo. That being said, @gretzky has a fork which you can use as a solid starting point for your SSR needs: [react-boilerplate-ssr](https://github.com/gretzky/react-boilerplate-ssr)

docs/forks/README.md

@@ -1,15 +1,16 @@
 # Debugging
 
-## Table of Contents
-
-- [Debugging with VC Code](#debugging-with-vscode)
-- [Debugging with WebStorm](#debugging-with-webStorm)
+- [Debugging with Visual Studio Code](#debugging-with-visual-studio-code)
+- [Debugging with WebStorm](#debugging-with-webstorm)
   - [Troubleshooting](#troubleshooting)
   - [Enable ESLint](#enable-eslint)
 
 ## Debugging with Visual Studio Code
 
-You can super charge your React debugging workflow with VS Code and Chrome debugging by using this `launch.json` config:
+You can super charge your React debugging workflow via VS Code and Chrome. Here are the steps:
+
+1. Install the [Debugger for Chrome](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome) extension in VS Code.
+2. Add the `Launch Chrome` option to your `launch.json` config:
 
 ```json
 {
@@ -30,13 +31,18 @@ You can super charge your React debugging workflow with VS Code and Chrome debug
 }
 ```
 
-You can read more in [Live edit and debug your React apps directly from VS Code — without leaving the editor 🔥 🎉🎈](https://medium.com/front-end-hacking/live-edit-and-debug-your-react-apps-directly-from-vs-code-without-leaving-the-editor-3da489ed905f)
+3. Start your dev server with `npm run start`.
+4. Launch the VS Code Debugger with the `Launch Chrome` configuration.
+
+You can then set breakpoints directly from inside VS Code, use stepping with the Chrome or VS Code buttons and more.
 
-**Note**: There's currently a [known problem](https://github.com/react-boilerplate/react-boilerplate/pull/1698) with source maps and VS Code. You can change your webpack config to use `inline-source-map` and the issue should be resolved.
+Read all about it in the [Debugger for Chrome page](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome).
+
+**Note**: There's currently a [known problem](https://github.com/react-boilerplate/react-boilerplate/pull/1698) with source maps and VS Code. You can change your Webpack dev config to use `inline-source-map` instead of `eval-source-map` and the issue should be resolved.
 
 ## Debugging with WebStorm
 
-WebStorm is a powerful IDE, and why not also use it as debugger tool? Here is the steps
+WebStorm is a powerful IDE, and why not also use it as debugger tool? Here are the steps:
 
 1.  [Install JetBrain Chrome Extension](https://chrome.google.com/webstore/detail/jetbrains-ide-support/hmhgeddbohgjknpmjagkdomcpobmllji)
 2.  [Setting up the PORT](https://www.jetbrains.com/help/webstorm/2016.1/using-jetbrains-chrome-extension.html)
@@ -61,16 +67,11 @@ WebStorm is a powerful IDE, and why not also use it as debugger tool? Here is th
 
 ### Enable ESLint
 
-ESLint help making all developer follow the same coding format. Please also setting up in your IDE, otherwise, you will fail ESLint test.
+ESLint helps developers on a team follow the same coding format. It's highly recommended to set it up in your IDE to avoid failing the linting step in tests.
 
-1.  Go to WebStorm Preference
+1.  Go to WebStorm Preferences
 2.  Search for `ESLint`
 3.  Click `Enable`
 
 ![Setting up ESLint](webstorm-eslint.png)
 
-## Have another question?
-
-Submit an [issue](https://github.com/react-boilerplate/react-boilerplate/issues),
-hop onto the [Gitter channel](https://gitter.im/mxstbr/react-boilerplate)
-or contact Max direct on [twitter](https://twitter.com/mxstbr)!