migrated server rendering docs

Author: ryanflorence

docs/README.md

@@ -5,6 +5,7 @@
 - [Route Matching](RouteMatching.md)
 - [Dynamic Routing](DynamicRouting.md)
 - [Confirming Navigation](ConfirmingNavigation.md)
+- [Server Rendering](Server Rendering.md)
 - [Glossary](Glossary.md)
 - [Route](Route.md)
 - [Plain Route](Plain Route.md)

docs/RouteMatching.md

@@ -4,7 +4,7 @@ A [route](Glossary.md#route) has two attributes that determine whether or not it
 
 ### Nesting
 
-React Router uses the concept of nested routes to let you declare nested sets of views that should be rendered when a given URL is invoked. Nested routes are arranged in a tree-like structure. To find a match, React Router traverses the [route config](Glossary.md#routeconfig) depth-first searching for a route that matches the URL. 
+React Router uses the concept of nested routes to let you declare nested sets of views that should be rendered when a given URL is invoked. Nested routes are arranged in a tree-like structure. To find a match, React Router traverses the [route config](Glossary.md#routeconfig) depth-first searching for a route that matches the URL.
 
 ### Path Syntax
 

docs/ServerRendering.md

@@ -0,0 +1,42 @@
+## Server Rendering
+
+Server rendering is a bit different than in a client because you'll want
+to:
+
+- Send `500` responses for errors
+- Send `30x` responses for redirects
+- Fetch data before rendering (and use the router to help you do it)
+
+To facilitate these needs, you drop one level lower than the `<Router/>`
+API with
+
+- `createLocation` from the history package
+- `match` to match the routes to a location without rendering
+- `RoutingContext` for synchronous rendering of route components
+
+It looks something like this with an imaginary JavaScript server:
+
+```js
+import createLocation from 'history/lib/createLocation'
+import { RoutingContext, match } from 'react-router'
+import routes from './routes'
+import { renderToString } from 'react-dom/server'
+
+serve((req, res) => {
+  let location = createLocation(req.url)
+  match(routes, location, (err, props, redirectInfo) => {
+    if (redirectInfo)
+      res.redirect(redirectInfo.path)
+    else if (err)
+      res.error(err.message)
+    else
+      res.send(renderToString(<RoutingContext {...props}/>))
+  })
+})
+```
+
+For data loading, you can use the `props` argument to build whatever
+convention you want--like adding static `load` methods to your route
+components, or putting data loading functions on the routes, its up to
+you.
+