Update some outdated pages on the site

Author: Daniel15

site/jekyll/_posts/2015-10-17-2.0.0-release.md

@@ -14,6 +14,7 @@ Full list of changes:
  * By default, only handle `*.jsx` files in ASP.NET 5 and OWIN middleware. You can modify the `Extensions` setting in `BabelFileOptions` to change this behaviour.
 
 Under the hood:
+
  * [#168](https://github.com/reactjs/React.NET/issues/168) - Everything relating to JSX transformer has been renamed to Babel (eg. `IJsxTransformer` is now `IBabel`).
  * Renamed `React` assembly to `React.Core`. The NuGet package has been called "React.Core" forever, but the corresponding assembly name didn't match, resulting in confusion.
  * Deprecated `IReactEnvironment.TransformJsxFile` and `IReactEnvironment.TransformJsx` have finally been removed. These methods have been obsolete since ReactJS.NET 0.2.

site/jekyll/dev/code-structure.md

@@ -8,8 +8,8 @@ are just a regular user of ReactJS.NET, you don't have to read it.
 
 Assemblies
 ----------
-ReactJS.NET is split into several different dependencies (React, React.Web,
-etc.). Ideally, the main "React" assembly should have as few dependencies as
+ReactJS.NET is split into several different dependencies (React.Core, React.Web,
+etc.). Ideally, the main "React.Core" assembly should have as few dependencies as
 possible. Dependencies with third-party libraries should be kept in separate
 assemblies unless they're required by core ReactJS.NET functionality (such as
 JavaScript engines)

site/jekyll/getting-started/aspnet5.md

@@ -6,7 +6,7 @@ title: Getting Started on ASP.NET 5
 
 Getting started with ReactJS.NET on ASP.NET 5 and MVC 6 requires a few more steps compared to previous versions of ASP.NET and MVC. A more fully featured tutorial will be released once the stable release of ASP.NET 5 is out.
 
-Note that ASP.NET 5 is still in beta, and so there may still be some sharp edges. ReactJS.NET requires at least Visual Studio 2015 and ASP.NET 5 Beta 6. Additionally, ReactJS.NET does not support the Core CLR at this point in time, so you will need to ensure your project is not referencing it. Remove the `"dnxcore50": { }` line from your `project.json` file.
+Note that ASP.NET 5 is still in beta, and so there may still be some sharp edges. ReactJS.NET requires at least Visual Studio 2015 and ASP.NET 5 **Beta 8**. Additionally, ReactJS.NET does not support the Core CLR at this point in time, so you will need to ensure your project is not referencing it. Remove the `"dnxcore50": { }` line from your `project.json` file.
 
 Once this has been removed, install the `React.AspNet` package through NuGet. After the package is installed, ReactJS.NET needs to be initialised in your `Startup.cs` file (unfortunately this can not be done automatically like in previous versions of ASP.NET with WebActivator). At the top of the file, add:
 ```
@@ -27,7 +27,7 @@ services.AddReact();
 ```
 
 
-Directly above:
+Directly **above**:
 
 ```csharp
 // Add static files to the request pipeline.
@@ -37,21 +37,24 @@ app.UseStaticFiles();
 Add:
 
 ```csharp
+// Initialise ReactJS.NET. Must be before static files.
 app.UseReact(config =>
 {
-  // ES6 features are enabled by default. Uncomment the below line to disable them.
-  // See http://reactjs.net/guides/es6.html for more information.
-  //config.SetUseHarmony(false);
-  // Uncomment the below line if you are using Flow
-  // See http://reactjs.net/guides/flow.html for more information.
-  //config.SetStripTypes(true);
   // If you want to use server-side rendering of React components,
   // add all the necessary JavaScript files here. This includes
   // your components as well as all of their dependencies.
   // See http://reactjs.net/ for more information. Example:
   //config
-  //  .AddScript("~/Scripts/First.jsx")
-  //  .AddScript("~/Scripts/Second.jsx");
+  //	.AddScript("~/Scripts/First.jsx")
+  //	.AddScript("~/Scripts/Second.jsx");
+
+  // If you use an external build too (for example, Babel, Webpack,
+  // Browserify or Gulp), you can improve performance by disabling
+  // ReactJS.NET's version of Babel and loading the pre-transpiled
+  // scripts. Example:
+  //config
+  //	.SetLoadBabel(false)
+  //	.AddScriptWithoutTransform("~/Scripts/bundle.server.js");
 });
 ```
 

site/jekyll/getting-started/download.md

@@ -51,7 +51,7 @@ feature or fixing a bug):
 2. Reference React.dll and React.Mvc4.dll (if using MVC 4) in your Web
    Application project
 
-Your first build always needs to be done using the build script (build.bat) as
+Your first build always needs to be done using the build script (`dev-build.bat`) as
 this generates a few files required by the build (such as
 `SharedAssemblyVersionInfo.cs`). Once this build is completed, you can open
 `React.sln` in Visual Studio and compile directly from Visual Studio.

site/jekyll/guides/cassette.md

@@ -24,7 +24,7 @@ bundles.Add<ScriptBundle>("main.js",
 This will add all three files into a `main.js` bundle that you can reference and
 render from your view using Cassette:
 
-```html{2-3,13}
+```html{2-3,14}
 @{
 	Bundles.Reference("main.css");
 	Bundles.Reference("main.js");

site/jekyll/guides/es6.md

@@ -1,9 +1,9 @@
 ---
 layout: docs
-title: ES6 Features
+title: ES6 Features (Babel)
 ---
 
-React can optionally use some ECMAScript 6 features thanks to the bundled version of [JSTransform](https://github.com/facebook/jstransform). ECMAScript 6 (or "ES6" for short) is the next version of ECMAScript/JavaScript and contains several useful features:
+ReactJS.NET supports the use of ECMAScript 6 features, thanks to [Babel](http://babeljs.io/). These features include:
 
 * **[Arrow functions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/arrow_functions)** — A syntax for inline lambda functions similar to C#. These are very useful when combined with the `map` and `filter` methods of arrays:
 
@@ -52,19 +52,4 @@ foo.add(2, 3); // 5
 ```
 
 * **[Short object notation](http://ariya.ofilabs.com/2013/02/es6-and-object-literal-property-value-shorthand.html)**
-* And more! See the [JSTransform source code](https://github.com/facebook/jstransform/tree/master/visitors), you never know what goodies you'll find.
-
-How to use
-----------
-To use the ES6 transforms, you'll need to enable them. For ASP.NET MVC sites, this is done in your `ReactConfig.cs` by calling `.SetUseHarmony(true)`:
-
-```csharp{2}
-ReactSiteConfiguration.Configuration
-  .SetUseHarmony(true)
-  .AddScript("~/Content/Sample.jsx");
-```
-If you are using [MSBuild to precompile your JSX](/guides/msbuild.html), you also need to enable it in MSBuild via the `UseHarmony="true"` flag in your build script (`TransformJsx.proj` by default):
-
-```xml
-<TransformJsx SourceDir="$(MSBuildProjectDirectory)" UseHarmony="true" />
-```
+* And more! See the [Babel website](http://babeljs.io/docs/learn-es2015/) for a full list of supported features.

site/jekyll/guides/flow.md

@@ -3,9 +3,7 @@ layout: docs
 title: Linux (Mono)
 ---
 
-**New in ReactJS.NET 1.0**
-
-ReactJS.NET 1.0 includes full support for Mono via Google's [V8 JavaScript engine](https://code.google.com/p/v8/), the same engine used by Google Chrome and Node.js. To use ReactJS.NET with Mono, you need to compile V8 and VroomJs (a .NET wrapper around V8). This can be accomplished by running the following shell commands on your Linux or Mac OS X machine:
+ReactJS.NET includes full support for Mono via Google's [V8 JavaScript engine](https://code.google.com/p/v8/), the same engine used by Google Chrome and Node.js. To use ReactJS.NET with Mono, you need to compile V8 and VroomJs (a .NET wrapper around V8). This can be accomplished by running the following shell commands on your Linux or Mac OS X machine:
 
 ```sh
 # Get a supported version of V8
@@ -32,6 +30,4 @@ cp libVroomJsNative.so /usr/local/lib/
 ldconfig
 ```
 
-Once this has been completed, install the **React.JavaScriptEngine.VroomJs** package to your website.
-
 If VroomJs fails to load, you will see an exception when your application is started. If this happens, run Mono with the `MONO_LOG_LEVEL=debug` environment variable to get more useful debugging information. Often, this occurs when Mono is unable to locate V8 (ie. it's not in /usr/lib/ or /usr/local/lib/)

site/jekyll/guides/mono.md

@@ -3,30 +3,28 @@ layout: docs
 title: MSBuild
 ---
 
-**New in ReactJS.NET 0.2**
-
 ReactJS.NET includes an MSBuild task for compiling JSX into JavaScript. This is
 handy to improve the start time of your application, especially if you have a
 large number of JSX files.
 
-To use it, first reference the `TransformJsx` task, and then call it wherever
+To use it, first reference the `TransformBabel` task, and then call it wherever
 you like:
 
 ```xml
 <UsingTask
 	AssemblyFile="tools\React\React.MSBuild.dll"
-	TaskName="TransformJsx"
+	TaskName="TransformBabel"
 />
-<Target Name="TransformJsx">
-	<TransformJsx SourceDir="$(MSBuildProjectDirectory)" TargetDir="" />
+<Target Name="TransformBabel">
+	<TransformBabel SourceDir="$(MSBuildProjectDirectory)" TargetDir="" />
 </Target>
 ```
 
 To get started easily, you can install the [React.MSBuild]
 (https://www.nuget.org/packages/React.MSBuild/) NuGet package which will
 automatically modify your web application's `.csproj` file to reference the task
 and run it after every site compilation. To customise the process (for example,
-to only compile the JSX files for release builds), modify the `TransformJsx`
+to only compile the JSX files for release builds), modify the `TransformBabel`
 build target that was added to the csproj file.
 
 The NuGet package is good for getting started quickly, but it has some

site/jekyll/guides/msbuild.md

@@ -83,8 +83,7 @@ If there is no need to have a React application client side and you just want to
 @Html.React("HelloWorld", new
 {
 	name = "Daniel"
-}
-serverOnly:true)
+}, serverOnly: true)
 ```
 
 And the Html mark up will look like the one following which is a lot cleaner. In this case there is no need to load the React script or call the `Html.ReactInitJavaScript()` method.
@@ -96,4 +95,4 @@ And the Html mark up will look like the one following which is a lot cleaner. In
 		<span>Daniel</span>
 	</div>
 </div>
-```
+```