{"patch":"diff --git a\/docs\/docs\/04-scaling-up.md b\/docs\/docs\/04-scaling-up.md\ndeleted file mode 100644\nindex 8d54dc571b..0000000000\n--- a\/docs\/docs\/04-scaling-up.md\n+++ \/dev\/null\n@@ -1,129 +0,0 @@\n----\n-id: 04-scaling-up\n-title: Scaling Up and Using Multiple Components\n-layout: docs\n-prev: 03-interactivity-and-dynamic-uis.html\n-next: 05-building-reusable-components.html\n----\n-So far, we've looked at how to write a single component to display data and handle user input. Next let's examine one of React's finest features: composability.\n-\n-### Motivation: separation of concerns\n-\n-By building modular components that reuse other components with well-defined interfaces, you get much of the same benefits that you get by using functions or classes. Specifically you can *separate the different concerns* of your app however you please simply by building new components. By building a custom component library for your application, you are expressing your UI in a way that best fits your domain.\n-\n-### Composition example\n-\n-Let's create a simple Avatar component which shows a profile picture and username using the Facebook Graph API.\n-\n-```javascript\n-\/** @jsx React.DOM *\/\n-\n-var Avatar = React.createClass({\n- render: function() {\n- return (\n-

\n- \n- \n- <\/div>\n- );\n- }\n-});\n-\n-var ProfilePic = React.createClass({\n- render: function() {\n- return (\n-

\n- );\n- }\n-});\n-\n-var ProfileLink = React.createClass({\n- render: function() {\n- return (\n- \n- {this.props.username}\n- <\/a>\n- );\n- }\n-});\n-\n-React.renderComponent(\n- ,\n- document.getElementById('example')\n-);\n-```\n-\n-### Ownership\n-\n-In the above example, instances of `Avatar` *own* instances of `ProfilePic` and `ProfileLink`. In React, **an owner is the component that sets the `props` of other components**. More formally, if a component `X` is created in component `Y`'s `render()` method, it is said that `X` is *owned by* `Y`. As discussed earlier, a component cannot mutate its `props` -- they are always consistent with what its owner sets them to. This key property leads to UIs that are guaranteed to be consistent.\n-\n-It's important to draw a distinciton between the owner-ownee relationship and the parent-child relationship. The owner-ownee relationship is specific to React, while the parent-child relationship is simply the one you know and love from the DOM. In the example above, `Avatar` owns the `div`, `ProfilePic` and `ProfileLink` instances, and `div` is the **parent** (but not owner) of the `ProfilePic` and `ProfileLink` instances.\n-\n-### Children\n-\n-When you create a React component instance, you can include additional React components or JavaScript expressions between the opening and closing tags like this:\n-\n-```javascript\n-<\/Parent>\n-```\n-\n-`Parent` can read its children by accessing the special `this.props.children` prop.\n-\n-#### Child Reconciliation\n-\n-> Reconciliation is the process by which React updates the DOM with each new render pass.\n-\n-In general, children are reconciled according to the order in which they are rendered. For example, suppose two render passes generate the following respective markup:\n-\n-```html\n-\/\/ Render Pass 1\n-

Paragraph 1<\/p>

Paragraph 2<\/p><\/Card>\n-\/\/ Render Pass 2\n-

Paragraph 2<\/p><\/Card>\n-```\n-\n-Intuitively, `

Paragraph 1<\/p>` was removed. Instead, React will reconcile the DOM by changing the text content of the first child and destroying the last child. React reconciles according to the *order* of the children.\n-\n-#### Stateful Children\n-\n-For most components, this is not a big deal. However, for stateful components that maintain data in `this.state` across render passes, this can be very problematic.\n-\n-In most cases, this can be sidestepped by hiding elements instead of destroying them:\n-\n-```html\n-\/\/ Render Pass 1\n-

Paragraph 1<\/p>

Paragraph 2<\/p><\/Card>\n-\/\/ Render Pass 2\n-

Paragraph 1<\/p>

Paragraph 2<\/p><\/Card>\n-```\n-\n-#### Dynamic Children\n-\n-The situation gets more complicated when the children are shuffled around (as in search results) or if new components are added onto the front of the list (as in streams). In these cases where the identity and state of each child must be maintained across render passes, you can uniquely identify each child by assigning it a `key`:\n-\n-```javascript\n- render: function() {\n- var results = this.props.results;\n- return (\n-

{result.text}<\/li>;\n- })}\n- <\/ol>\n- );\n- }\n-```\n-\n-When React reconciles the keyed children, it will ensure that any child with `key` will be reordered (instead of clobbered) or destroyed (instead of reused).\n-\n-### Data flow\n-\n-In React, data flows from owner to owned component through `props` as discussed above. This is effectively one-way data binding: owners bind their owned component's props to some value the owner has computed based on its `props` or `state`. Since this process happens recursively, data changes are automatically reflected everywhere they are used.\n-\n-### A note on performance\n-\n-You may be thinking that it's expensive to react to changing data if there are a large number of nodes under an owner. The good news is that JavaScript is fast and `render()` methods tend to be quite simple, so in most applications this is extremely fast. Additionally, the bottleneck is almost always the DOM mutation and not JS execution, and React will optimize this for you using batching and change detection.\n-\n-However, sometimes you really want to have fine-grained control over your performance. In that case, simply override `shouldComponentUpdate()` to return false when you want React to skip processing of a subtree. See [the React API docs](.\/api.html) for more information.\n-\n-**Note:** if `shouldComponentUpdate()` returns false when data has actually changed, React can't keep your UI in sync. Be sure you know what you're doing while using it, and only use this function when you have a noticeable performance problem. Don't underestimate how fast JavaScript is relative to the DOM.\n\\ No newline at end of file\n","commit":{"authoredAt":"2013-07-16T13:55:42-07:00","subject":"Remove \"Scaling Up\"","shortRevision":"04bfa545f7","authorName":"Paul O’Shannessy","revision":"04bfa545f7148dfdce5df5cf2e6d1f6ba31cbfab","authorEmail":"paul@oshannessy.com"},"parents":["e9e89345778d9a1a0f4dcbe2f2ff2d97c0651562"],"body":"","files":[{"path":"docs\/docs\/04-scaling-up.md","status":"D"}]}

dillon1000/react

Files changed