{"body":"New marketing copy","commit":{"authorName":"Pete Hunt","authorEmail":"pete@instagram.com","subject":"Merge pull request #440 from petehunt\/new-taglines","authoredAt":"2013-12-01T14:00:13-08:00","shortRevision":"285e3a8929","revision":"285e3a89290f6a06a3e8089a5577c7ba4f63e0dd"},"patch":"diff --git a\/docs\/index.md b\/docs\/index.md\nindex 2edff30307..2ccbb676d6 100644\n--- a\/docs\/index.md\n+++ b\/docs\/index.md\n@@ -7,23 +7,25 @@ id: home\n

\n-

Declarative<\/h3>\n+

Just the UI<\/h3>\n
\n- React uses a declarative paradigm that makes it easier to reason about\n- your application.\n+ Lots of people use React as the V in MVC.\n+ Since React makes no assumptions about the rest of your technology stack,\n+ it's easy to try it out on a small feature in an existing project.\n <\/p>\n <\/div>\n
\n-
Efficient<\/h3>\n+
Virtual DOM<\/h3>\n
\n- React computes the minimal set of changes necessary to keep your DOM\n- up-to-date.\n+ React uses a virtual DOM<\/i> diff implementation for ultra-high performance. It can also\n+ render on the server using Node.js — no heavy browser DOM required.\n <\/p>\n <\/div>\n
\n-
Flexible<\/h3>\n+
Data flow<\/h3>\n
\n- React works with the libraries and frameworks that you already know.\n+ React implements one-way reactive data flow which reduces boilerplate and is\n+ easier to reason about than traditional data binding.\n <\/p>\n <\/div>\n <\/div>\n@@ -60,7 +62,7 @@ id: home\n This example uses `state` to track the current list of items as well as\n the text that the user has entered. Although event handlers appear to be\n rendered inline, they will be collected and implemented using event\n- delegation. \n+ delegation.\n <\/p>\n
<\/div>\n <\/div>\n","parents":["ab36b114fc40361ff0cec5a7ad74862640cafab4","9f69b12e5b34bfeb064456726c3ee39ef23923ba"],"files":[{"status":"M","path":"docs\/index.md"}]}

dillon1000/react

Files changed