Add more helpful invariant if you're updating an unrendered component
Add pagination to blog

- Add pagination
- Display full content in /blog
- Truncate Recent posts
- Add permalink that lists all the blog posts
- Add spacing and bullet around recent posts to make it more readable
Tutorial: show how to add showdown.js
sync with tastejs todomvc
move lifecycle check into replaceProps instead of updateComponent
Merge pull request #307 from chenglou/todomvc-director

sync with tastejs todomvc
Redirect /docs to the right page

I've hit this a few times where I want to get to docs so I take whatever
my urlbar gives me and strip out the actual page so I can get to the
root, however that's a 404.

This introduces a super easy way to redirect, which could be handy in
the future as docs get rewritten.

I would much rather do this with a real htaccess file or even just
handle 404s gracefully, but that's not currently an option with GitHub
pages (since we generate our own and don't use a custom domain).
Merge pull request #312 from zpao/docs-redirect

Redirect /docs to the right page
Merge pull request #305 from brianr/tutorial-explain-showdown

Tutorial: show how to add showdown.js
Merge pull request #298 from vjeux/pagination

Add pagination to blog
Fix a few GC leaks in events system

Summary:
    - Weren't pooling the Transaction in the batching strategy
    - Creating a new closure for every event tick due to batchedUpdates()
    - EnterLeaveEventPlugin creates a new array on each event.

I wonder if there is more optimization opportunity in accumulate(). Squinting at the fps graph this seems to be faster and waste less memory but it's hard to conclusively tell. I did verify that these were all hotspots though.
Remove React.autoBind for real

This has been deprecated for a long while now, we should actually remove it.
Add Stack Overflow link for doc support page.
Update wording
Add ReactTransitionGroup

This introduces <ReactTransitionGroup>, a component that works a lot
like Angular's ng-animate.

The problem we're currently facing is twofold:
1. We don't really have a great convention surrounding CSS transitions
   in React
2. (harder) we can't animate nodes that are leaving the DOM, as their
   nodes are instantly destroyed.

To solve the first issue I've adopted Angular's convention. It's
implemented in ReactTransitionableChild.

The second part is what's tricky. To do this I've implemented three modules:
- ReactTransitionableChild, which can keep its old children around if they
  change to null
- ReactTransitionKeySet, which can look at a prev and next set of child
  keys and merge them in a reasonable way
- ReactTransitionGroup, which combines ReactTransitionableChild and
  ReactTransitionKeySet to keep nodes that are leaving the DOM in the
  DOM until their animations are complete
Improve error behavior of Danger.dangerouslyRenderMarkup.

HTML comment nodes are now interspersed in the original markup list so
that we can tell which chunks of markup rendered as more or less than one
node, and give a more helpful error message in that case.

Regardless of how many nodes were rendered, we only take the first one. If
zero nodes were rendered, then `resultList` will contain `null` at the
corresponding position.

If we decide to revisit the idea of using document fragments, it will be
very easy to handle the `!== 1` case by returning a document fragment.
Test cases covering rendering onto document

There were some bug reports here, I couldn't reproduce but wrote tests anyway. We should definitely have these.
Use dumpCache() rather than manual reset

I forgot this module existed until @benjamn reminded we had a way to do it.
Sync CSSCore from upstream
fix formatting and test for correct error