Own our fiddles so we can update them more easily
Paul O’Shannessy committed
Dec 1, 2014 at 19:33 UTC
2c2cac00f9e8d0378d5e07e3b79bb1ec89d0e80f
3 files changed
+7
-7
docs/docs/getting-started.md
+2
-2
@@ -9,8 +9,8 @@ redirect_from: "docs/index.html"
9
10
The easiest way to start hacking on React is using the following JSFiddle Hello World examples:
11
12
- * **[React JSFiddle](http://jsfiddle.net/vjeux/kb3gN/)**
13
- * [React JSFiddle without JSX](http://jsfiddle.net/vjeux/VkebS/)
12
+ * **[React JSFiddle](http://jsfiddle.net/reactjs/69z2wepo/)**
13
+ * [React JSFiddle without JSX](http://jsfiddle.net/reactjs/5vjqabv3/)
14
15
## Starter Kit
16
docs/docs/getting-started.zh-CN.md
+2
-2
@@ -8,8 +8,8 @@ next: tutorial.html
8
9
开始 Hack React 的最简单的方法是用下面 JSFiddle 的Hello Worlds
10
11
- * **[React JSFiddle](http://jsfiddle.net/vjeux/kb3gN/)**
12
- * [React JSFiddle without JSX](http://jsfiddle.net/vjeux/VkebS/)
11
+ * **[React JSFiddle](http://jsfiddle.net/reactjs/69z2wepo/)**
12
+ * [React JSFiddle without JSX](http://jsfiddle.net/reactjs/5vjqabv3/)
13
14
## 入门教程包 (Starter Kit)
15
docs/docs/thinking-in-react.md
+3
-3
@@ -60,7 +60,7 @@ Now that we've identified the components in our mock, let's arrange them into a
60
61
## Step 2: Build a static version in React
62
63
-<iframe width="100%" height="300" src="http://jsfiddle.net/n25pd/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
63
+<iframe width="100%" height="300" src="http://jsfiddle.net/reactjs/yun1vgqb/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
64
65
Now that you have your component hierarchy it's time to start implementing your app. The easiest way is to build a version that takes your data model and renders the UI but has no interactivity. It's easiest to decouple these processes because building a static version requires a lot of typing and no thinking, and adding interactivity requires a lot of thinking and not a lot of typing. We'll see why.
66
@@ -104,7 +104,7 @@ So finally, our state is:
104
105
## Step 4: Identify where your state should live
106
107
-<iframe width="100%" height="300" src="http://jsfiddle.net/t53sx/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
107
+<iframe width="100%" height="300" src="http://jsfiddle.net/reactjs/zafjbw1e/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
108
109
OK, so we've identified what the minimal set of app state is. Next we need to identify which component mutates, or *owns*, this state.
110
@@ -129,7 +129,7 @@ You can start seeing how your application will behave: set `filterText` to `"bal
129
130
## Step 5: Add inverse data flow
131
132
-<iframe width="100%" height="300" src="http://jsfiddle.net/F8H7p/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
132
+<iframe width="100%" height="300" src="http://jsfiddle.net/reactjs/n47gckhr/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
133
134
So far we've built an app that renders correctly as a function of props and state flowing down the hierarchy. Now it's time to support data flowing the other way: the form components deep in the hierarchy need to update the state in `FilterableProductTable`.
135