From 148b625cc4aead8f64554ba7981ac1b07e693437 Mon Sep 17 00:00:00 2001
From: Nicolas Charpentier <nicolas.charpentier079@gmail.com>
Date: Wed, 4 Sep 2019 16:38:36 +0200
Subject: [PATCH 01/26] Split components and APIs grid in 2 or 3 (#1231)

---
 website/static/css/react-native.css | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/website/static/css/react-native.css b/website/static/css/react-native.css
index 13f645d7f19..20ccc17f515 100644
--- a/website/static/css/react-native.css
+++ b/website/static/css/react-native.css
@@ -160,10 +160,7 @@ a code {
   }
 }
 
-@media only screen and (min-device-width: 768px) {
-  .mainContainer .component-grid {
-    width: 768px;
-  }
+@media only screen and (min-width: 768px) {
   .mainContainer .component-grid.component-grid-border {
     border-bottom: 1px solid #f1eff0;
   }
@@ -176,7 +173,12 @@ a code {
 
   @supports (display: grid) {
     .mainContainer .component-grid {
-      grid-template-columns: repeat(3, 1fr);
+      grid-template-columns: repeat(2, 1fr);
+    }
+    @media only screen and (min-width: 1440px) {
+      .mainContainer .component-grid {
+        grid-template-columns: repeat(3, 1fr);
+      }
     }
     .mainContainer .component {
       width: auto;

From 08feca77717ae2c44c08de4ddb6bae4e094a6c2d Mon Sep 17 00:00:00 2001
From: Kacper Wiszczuk <kacperwiszczuk@gmail.com>
Date: Wed, 4 Sep 2019 16:39:42 +0200
Subject: [PATCH 02/26] imp: Add snack examples to FlatList (#1221)

* imp: Add snack examples to FlatList

* Update flatlist.md
---
 docs/flatlist.md                              | 193 +++++++++++++-----
 .../versioned_docs/version-0.60/flatlist.md   | 193 +++++++++++++-----
 2 files changed, 276 insertions(+), 110 deletions(-)

diff --git a/docs/flatlist.md b/docs/flatlist.md
index c5dbd708b97..5f3793dca56 100644
--- a/docs/flatlist.md
+++ b/docs/flatlist.md
@@ -18,76 +18,159 @@ A performant interface for rendering simple, flat lists, supporting the most han
 
 If you need section support, use [`<SectionList>`](sectionlist.md).
 
-Minimal Example:
+### Basic Example:
+
+```SnackPlayer name=flatlist-simple
+import React from 'react';
+import { SafeAreaView, View, FlatList, StyleSheet, Text } from 'react-native';
+import Constants from 'expo-constants';
+
+const DATA = [
+  {
+    id: 'bd7acbea-c1b1-46c2-aed5-3ad53abb28ba',
+    title: 'First Item',
+  },
+  {
+    id: '3ac68afc-c605-48d3-a4f8-fbd91aa97f63',
+    title: 'Second Item',
+  },
+  {
+    id: '58694a0f-3da1-471f-bd96-145571e29d72',
+    title: 'Third Item',
+  },
+];
+
+function Item({ title }) {
+  return (
+    <View style={styles.item}>
+      <Text style={styles.title}>{title}</Text>
+    </View>
+  );
+}
 
-```jsx
-<FlatList
-  data={[{key: 'a'}, {key: 'b'}]}
-  renderItem={({item}) => <Text>{item.key}</Text>}
-/>
+export default function App() {
+  return (
+    <SafeAreaView style={styles.container}>
+      <FlatList
+        data={DATA}
+        renderItem={({ item }) => <Item title={item.title} />}
+        keyExtractor={item => item.id}
+      />
+    </SafeAreaView>
+  );
+}
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+    marginTop: Constants.statusBarHeight,
+  },
+  item: {
+    backgroundColor: '#f9c2ff',
+    padding: 20,
+    marginVertical: 8,
+    marginHorizontal: 16,
+  },
+  title: {
+    fontSize: 32,
+  },
+});
 ```
 
 To render multiple columns, use the [`numColumns`](flatlist.md#numcolumns) prop. Using this approach instead of a `flexWrap` layout can prevent conflicts with the item height logic.
 
-More complex, multi-select example demonstrating `PureComponent` usage for perf optimization and avoiding bugs.
+More complex, multi-select example demonstrating `` usage for perf optimization and avoiding bugs.
 
-- By binding the `onPressItem` handler, the props will remain `===` and `PureComponent` will prevent wasteful re-renders unless the actual `id`, `selected`, or `title` props change, even if the components rendered in `MyListItem` did not have such optimizations.
-- By passing `extraData={this.state}` to `FlatList` we make sure `FlatList` itself will re-render when the `state.selected` changes. Without setting this prop, `FlatList` would not know it needs to re-render any items because it is also a `PureComponent` and the prop comparison will not show any changes.
+- By passing `extraData={selected}` to `FlatList` we make sure `FlatList` itself will re-render when the state changes. Without setting this prop, `FlatList` would not know it needs to re-render any items because it is a `PureComponent` and the prop comparison will not show any changes.
 - `keyExtractor` tells the list to use the `id`s for the react keys instead of the default `key` property.
 
-```jsx
-class MyListItem extends React.PureComponent {
-  _onPress = () => {
-    this.props.onPressItem(this.props.id);
-  };
-
-  render() {
-    const textColor = this.props.selected ? 'red' : 'black';
-    return (
-      <TouchableOpacity onPress={this._onPress}>
-        <View>
-          <Text style={{color: textColor}}>{this.props.title}</Text>
-        </View>
-      </TouchableOpacity>
-    );
-  }
+```SnackPlayer name=flatlist-selectable
+import React from 'react';
+import {
+  SafeAreaView,
+  TouchableOpacity,
+  FlatList,
+  StyleSheet,
+  Text,
+} from 'react-native';
+import Constants from 'expo-constants';
+
+const DATA = [
+  {
+    id: 'bd7acbea-c1b1-46c2-aed5-3ad53abb28ba',
+    title: 'First Item',
+  },
+  {
+    id: '3ac68afc-c605-48d3-a4f8-fbd91aa97f63',
+    title: 'Second Item',
+  },
+  {
+    id: '58694a0f-3da1-471f-bd96-145571e29d72',
+    title: 'Third Item',
+  },
+];
+
+function Item({ id, title, selected, onSelect }) {
+  return (
+    <TouchableOpacity
+      onPress={() => onSelect(id)}
+      style={[
+        styles.item,
+        { backgroundColor: selected ? '#6e3b6e' : '#f9c2ff' },
+      ]}
+    >
+      <Text style={styles.title}>{title}</Text>
+    </TouchableOpacity>
+  );
 }
 
-class MultiSelectList extends React.PureComponent {
-  state = {selected: (new Map(): Map<string, boolean>)};
-
-  _keyExtractor = (item, index) => item.id;
-
-  _onPressItem = (id: string) => {
-    // updater functions are preferred for transactional updates
-    this.setState((state) => {
-      // copy the map rather than modifying state.
-      const selected = new Map(state.selected);
-      selected.set(id, !selected.get(id)); // toggle
-      return {selected};
-    });
-  };
-
-  _renderItem = ({item}) => (
-    <MyListItem
-      id={item.id}
-      onPressItem={this._onPressItem}
-      selected={!!this.state.selected.get(item.id)}
-      title={item.title}
-    />
+export default function App() {
+  const [selected, setSelected] = React.useState(new Map());
+
+  const onSelect = React.useCallback(
+    id => {
+      const newSelected = new Map(selected);
+      newSelected.set(id, !selected.get(id));
+
+      setSelected(newSelected);
+    },
+    [selected],
   );
 
-  render() {
-    return (
+  return (
+    <SafeAreaView style={styles.container}>
       <FlatList
-        data={this.props.data}
-        extraData={this.state}
-        keyExtractor={this._keyExtractor}
-        renderItem={this._renderItem}
+        data={DATA}
+        renderItem={({ item }) => (
+          <Item
+            id={item.id}
+            title={item.title}
+            selected={!!selected.get(item.id)}
+            onSelect={onSelect}
+          />
+        )}
+        keyExtractor={item => item.id}
+        extraData={selected}
       />
-    );
-  }
+    </SafeAreaView>
+  );
 }
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+    marginTop: Constants.statusBarHeight,
+  },
+  item: {
+    backgroundColor: '#f9c2ff',
+    padding: 20,
+    marginVertical: 8,
+    marginHorizontal: 16,
+  },
+  title: {
+    fontSize: 32,
+  },
+});
 ```
 
 This is a convenience wrapper around [`<VirtualizedList>`](virtualizedlist.md), and thus inherits its props (as well as those of [`<ScrollView>`](scrollview.md)) that aren't explicitly listed here, along with the following caveats:
diff --git a/website/versioned_docs/version-0.60/flatlist.md b/website/versioned_docs/version-0.60/flatlist.md
index 3bcc83baa2d..28328ce2c69 100644
--- a/website/versioned_docs/version-0.60/flatlist.md
+++ b/website/versioned_docs/version-0.60/flatlist.md
@@ -19,76 +19,159 @@ A performant interface for rendering simple, flat lists, supporting the most han
 
 If you need section support, use [`<SectionList>`](sectionlist.md).
 
-Minimal Example:
+### Basic Example:
+
+```SnackPlayer name=flatlist-simple
+import React from 'react';
+import { SafeAreaView, View, FlatList, StyleSheet, Text } from 'react-native';
+import Constants from 'expo-constants';
+
+const DATA = [
+  {
+    id: 'bd7acbea-c1b1-46c2-aed5-3ad53abb28ba',
+    title: 'First Item',
+  },
+  {
+    id: '3ac68afc-c605-48d3-a4f8-fbd91aa97f63',
+    title: 'Second Item',
+  },
+  {
+    id: '58694a0f-3da1-471f-bd96-145571e29d72',
+    title: 'Third Item',
+  },
+];
+
+function Item({ title }) {
+  return (
+    <View style={styles.item}>
+      <Text style={styles.title}>{title}</Text>
+    </View>
+  );
+}
 
-```jsx
-<FlatList
-  data={[{key: 'a'}, {key: 'b'}]}
-  renderItem={({item}) => <Text>{item.key}</Text>}
-/>
+export default function App() {
+  return (
+    <SafeAreaView style={styles.container}>
+      <FlatList
+        data={DATA}
+        renderItem={({ item }) => <Item title={item.title} />}
+        keyExtractor={item => item.id}
+      />
+    </SafeAreaView>
+  );
+}
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+    marginTop: Constants.statusBarHeight,
+  },
+  item: {
+    backgroundColor: '#f9c2ff',
+    padding: 20,
+    marginVertical: 8,
+    marginHorizontal: 16,
+  },
+  title: {
+    fontSize: 32,
+  },
+});
 ```
 
 To render multiple columns, use the [`numColumns`](flatlist.md#numcolumns) prop. Using this approach instead of a `flexWrap` layout can prevent conflicts with the item height logic.
 
-More complex, multi-select example demonstrating `PureComponent` usage for perf optimization and avoiding bugs.
+More complex, multi-select example demonstrating `` usage for perf optimization and avoiding bugs.
 
-- By binding the `onPressItem` handler, the props will remain `===` and `PureComponent` will prevent wasteful re-renders unless the actual `id`, `selected`, or `title` props change, even if the components rendered in `MyListItem` did not have such optimizations.
-- By passing `extraData={this.state}` to `FlatList` we make sure `FlatList` itself will re-render when the `state.selected` changes. Without setting this prop, `FlatList` would not know it needs to re-render any items because it is also a `PureComponent` and the prop comparison will not show any changes.
+- By passing `extraData={selected}` to `FlatList` we make sure `FlatList` itself will re-render when the state changes. Without setting this prop, `FlatList` would not know it needs to re-render any items because it is a `PureComponent` and the prop comparison will not show any changes.
 - `keyExtractor` tells the list to use the `id`s for the react keys instead of the default `key` property.
 
-```jsx
-class MyListItem extends React.PureComponent {
-  _onPress = () => {
-    this.props.onPressItem(this.props.id);
-  };
-
-  render() {
-    const textColor = this.props.selected ? 'red' : 'black';
-    return (
-      <TouchableOpacity onPress={this._onPress}>
-        <View>
-          <Text style={{color: textColor}}>{this.props.title}</Text>
-        </View>
-      </TouchableOpacity>
-    );
-  }
+```SnackPlayer name=flatlist-selectable
+import React from 'react';
+import {
+  SafeAreaView,
+  TouchableOpacity,
+  FlatList,
+  StyleSheet,
+  Text,
+} from 'react-native';
+import Constants from 'expo-constants';
+
+const DATA = [
+  {
+    id: 'bd7acbea-c1b1-46c2-aed5-3ad53abb28ba',
+    title: 'First Item',
+  },
+  {
+    id: '3ac68afc-c605-48d3-a4f8-fbd91aa97f63',
+    title: 'Second Item',
+  },
+  {
+    id: '58694a0f-3da1-471f-bd96-145571e29d72',
+    title: 'Third Item',
+  },
+];
+
+function Item({ id, title, selected, onSelect }) {
+  return (
+    <TouchableOpacity
+      onPress={() => onSelect(id)}
+      style={[
+        styles.item,
+        { backgroundColor: selected ? '#6e3b6e' : '#f9c2ff' },
+      ]}
+    >
+      <Text style={styles.title}>{title}</Text>
+    </TouchableOpacity>
+  );
 }
 
-class MultiSelectList extends React.PureComponent {
-  state = {selected: (new Map(): Map<string, boolean>)};
-
-  _keyExtractor = (item, index) => item.id;
-
-  _onPressItem = (id: string) => {
-    // updater functions are preferred for transactional updates
-    this.setState((state) => {
-      // copy the map rather than modifying state.
-      const selected = new Map(state.selected);
-      selected.set(id, !selected.get(id)); // toggle
-      return {selected};
-    });
-  };
-
-  _renderItem = ({item}) => (
-    <MyListItem
-      id={item.id}
-      onPressItem={this._onPressItem}
-      selected={!!this.state.selected.get(item.id)}
-      title={item.title}
-    />
+export default function App() {
+  const [selected, setSelected] = React.useState(new Map());
+
+  const onSelect = React.useCallback(
+    id => {
+      const newSelected = new Map(selected);
+      newSelected.set(id, !selected.get(id));
+
+      setSelected(newSelected);
+    },
+    [selected],
   );
 
-  render() {
-    return (
+  return (
+    <SafeAreaView style={styles.container}>
       <FlatList
-        data={this.props.data}
-        extraData={this.state}
-        keyExtractor={this._keyExtractor}
-        renderItem={this._renderItem}
+        data={DATA}
+        renderItem={({ item }) => (
+          <Item
+            id={item.id}
+            title={item.title}
+            selected={!!selected.get(item.id)}
+            onSelect={onSelect}
+          />
+        )}
+        keyExtractor={item => item.id}
+        extraData={selected}
       />
-    );
-  }
+    </SafeAreaView>
+  );
 }
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+    marginTop: Constants.statusBarHeight,
+  },
+  item: {
+    backgroundColor: '#f9c2ff',
+    padding: 20,
+    marginVertical: 8,
+    marginHorizontal: 16,
+  },
+  title: {
+    fontSize: 32,
+  },
+});
 ```
 
 This is a convenience wrapper around [`<VirtualizedList>`](virtualizedlist.md), and thus inherits its props (as well as those of [`<ScrollView>`](scrollview.md)) that aren't explicitly listed here, along with the following caveats:

From bba1d2e1907cdea8618e0e4d6580d14be9fe9baa Mon Sep 17 00:00:00 2001
From: Radek Pietruszewski <radexpl@gmail.com>
Date: Mon, 9 Sep 2019 16:07:35 +0200
Subject: [PATCH 03/26] Update inputaccessoryview.md (#1253)

---
 docs/inputaccessoryview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/inputaccessoryview.md b/docs/inputaccessoryview.md
index c00d4f11b9d..f4e732d698f 100644
--- a/docs/inputaccessoryview.md
+++ b/docs/inputaccessoryview.md
@@ -44,7 +44,7 @@ export default class UselessTextInput extends Component {
 }
 ```
 
-This component can also be used to create sticky text inputs (text inputs which are anchored to the top of the keyboard). To do this, wrap a `TextInput` with the `InputAccessoryView` component, and don't set a `nativeID`. For an example, look at [InputAccessoryViewExample.js](https://github.com/facebook/react-native/blob/master/RNTester/js/InputAccessoryViewExample.js).
+This component can also be used to create sticky text inputs (text inputs which are anchored to the top of the keyboard). To do this, wrap a `TextInput` with the `InputAccessoryView` component, and don't set a `nativeID`. For an example, look at [InputAccessoryViewExample.js](https://github.com/facebook/react-native/blob/master/RNTester/js/examples/InputAccessoryView/InputAccessoryViewExample.js).
 
 ---
 

From c549569366fbfeb140c8e584822d19fdd06137e9 Mon Sep 17 00:00:00 2001
From: Rachel Nabors <rachelnabors@users.noreply.github.com>
Date: Fri, 13 Sep 2019 15:19:11 +0100
Subject: [PATCH 04/26] Adding banner for docs survey, please remove in 2 weeks
 (#1263)

---
 website/siteConfig.js                 |  1 +
 website/static/css/header.css         | 37 +++++++++++++++++++++++++++
 website/static/js/2019_docs-survey.js | 10 ++++++++
 3 files changed, 48 insertions(+)
 create mode 100644 website/static/js/2019_docs-survey.js

diff --git a/website/siteConfig.js b/website/siteConfig.js
index 35369225090..b20dba72cd0 100644
--- a/website/siteConfig.js
+++ b/website/siteConfig.js
@@ -81,6 +81,7 @@ const siteConfig = {
     'https://buttons.github.io/buttons.js',
     baseUrl + 'js/codeblocks.js',
     baseUrl + 'js/tabs.js',
+    baseUrl + 'js/2019_docs-survey.js',
   ],
   cleanUrl: true,
   scrollToTop: true,
diff --git a/website/static/css/header.css b/website/static/css/header.css
index 7ff7da88c4e..cd293efcb51 100644
--- a/website/static/css/header.css
+++ b/website/static/css/header.css
@@ -182,3 +182,40 @@ input#search_input_react {
 input#search_input_react:focus {
   background-color: $light;
 }
+
+/* 2019_docs-survey */
+.callout_docs-survey-2019-2 {
+  background-color: rgba(5, 165, 209, 0.25);
+  border-radius: 0.15em;
+  color: #001217;
+  display: block;
+  margin: 1em 0;
+  position: relative;
+  padding: 1em 2em 1em 3.5em;
+  transition: transform 300ms ease-out;
+}
+
+.callout_docs-survey-2019-2 svg {
+  fill: rgba(5, 165, 209, 1);
+  height: 2em;
+  width: 2em;
+  position: absolute;
+  top: 0.75em;
+  left: 1em;
+}
+
+.callout_docs-survey-2019-2:link,
+.callout_docs-survey-2019-2:visited {
+  color: #001217;
+}
+
+.callout_docs-survey-2019-2:hover,
+.callout_docs-survey-2019-2:active,
+.callout_docs-survey-2019-2:focus {
+  color: #001217;
+  transform: translate(0.1em, 0.1em);
+}
+
+.callout_docs-survey-2019-2 span {
+  text-decoration: underline;
+}
diff --git a/website/static/js/2019_docs-survey.js b/website/static/js/2019_docs-survey.js
new file mode 100644
index 00000000000..54b7cc89617
--- /dev/null
+++ b/website/static/js/2019_docs-survey.js
@@ -0,0 +1,10 @@
+document.addEventListener('DOMContentLoaded', function() {
+  const container = document.querySelector('.container.mainContainer .wrapper');
+  if (container) {
+    const div = document.createElement('div');
+    div.innerHTML =
+      '<a class="callout_docs-survey-2019-2" href="https://www.surveymonkey.co.uk/r/PCFLG7B"><svg height="100px" width="100px"  fill="#000000" xmlns="http://www.w3.org/2000/svg" data-name="Layer 1" viewBox="0 0 100 100" x="0px" y="0px"><title>89all</title><path d="M80.17,11.5H69.11a11.13,11.13,0,0,0-3.6-7.12l0,0A11.09,11.09,0,0,0,58.05,1.5H41.95a11.09,11.09,0,0,0-7.43,2.85l0,0a11.13,11.13,0,0,0-3.6,7.13H19.83a9,9,0,0,0-9,9v69a9,9,0,0,0,9,9H80.17a9,9,0,0,0,9-9v-69A9,9,0,0,0,80.17,11.5ZM71.48,63.4H60.2a6,6,0,0,0-6,6V81.64H28.52V26.36h2.31v.14a3,3,0,0,0,3,3H66.17a3,3,0,0,0,3-3v-.14h2.31ZM68,69.4l-7.85,8v-8ZM36.83,12.61a5.12,5.12,0,0,1,1.69-3.8l0,0a5.1,5.1,0,0,1,3.4-1.3H58.05a5.1,5.1,0,0,1,3.4,1.3l0,0a5.12,5.12,0,0,1,1.69,3.8V23.5H36.83ZM83.17,89.5a3,3,0,0,1-3,3H19.83a3,3,0,0,1-3-3v-69a3,3,0,0,1,3-3h11v2.86H28.52a6,6,0,0,0-6,6V81.64a6,6,0,0,0,6,6H58.58l18.9-19.29v-42a6,6,0,0,0-6-6H69.17V17.5h11a3,3,0,0,1,3,3Z"></path><path d="M36.28,45H47.9a3,3,0,1,0,0-6H36.28a3,3,0,0,0,0,6Z"></path><path d="M62.9,51H36.28a3,3,0,0,0,0,6H62.9a3,3,0,1,0,0-6Z"></path></svg>Have two minutes to help us make the React Native docs even better? <span>Take our short survey!</span></a>';
+    const content = div.childNodes[0];
+    container.insertBefore(content, container.childNodes[0]);
+  }
+});

From c87fe3ac9d9f0414aa958072200ac5470468e38a Mon Sep 17 00:00:00 2001
From: Nicolas Charpentier <nicolas.charpentier079@gmail.com>
Date: Fri, 13 Sep 2019 13:52:55 -0400
Subject: [PATCH 05/26] Run sync-guides (#1228)

---
 .../version-0.5/accessibility.md              | 154 ++--
 .../versioned_docs/version-0.5/animations.md  |  79 +-
 .../version-0.5/app-extensions.md             |   2 +-
 .../version-0.5/communication-ios.md          |   6 +-
 .../version-0.5/components-and-apis.md        |   8 -
 .../versioned_docs/version-0.5/debugging.md   |   4 +-
 .../version-0.5/direct-manipulation.md        |  10 +-
 website/versioned_docs/version-0.5/flexbox.md | 159 +++-
 .../version-0.5/getting-started.md            | 129 +--
 .../version-0.5/handling-text-input.md        |   8 +-
 .../version-0.5/headless-js-android.md        |  39 +
 .../version-0.5/height-and-width.md           |  15 +-
 website/versioned_docs/version-0.5/images.md  |   4 +-
 .../integration-with-existing-apps.md         |  34 +-
 .../version-0.5/javascript-environment.md     |  13 +-
 .../version-0.5/more-resources.md             |   6 +-
 .../version-0.5/native-components-ios.md      |  73 ++
 .../version-0.5/native-modules-android.md     |  19 +-
 .../version-0.5/native-modules-setup.md       |  10 +-
 .../versioned_docs/version-0.5/navigation.md  |   8 +
 website/versioned_docs/version-0.5/network.md |   4 +-
 .../versioned_docs/version-0.5/performance.md |  56 +-
 website/versioned_docs/version-0.5/props.md   |  16 +-
 .../removing-default-permissions.md           |  17 +-
 .../version-0.5/running-on-simulator-ios.md   |   2 +-
 .../version-0.5/signed-apk-android.md         |  68 +-
 website/versioned_docs/version-0.5/state.md   |  14 +-
 website/versioned_docs/version-0.5/style.md   |   9 +-
 website/versioned_docs/version-0.5/timers.md  |  23 -
 .../version-0.5/troubleshooting.md            |   2 +-
 .../versioned_docs/version-0.5/tutorial.md    |   2 +-
 .../versioned_docs/version-0.5/upgrading.md   |   4 +-
 .../version-0.5/using-a-scrollview.md         |  11 +-
 website/versioned_docs/version-0.59/images.md | 223 -----
 .../version-0.60/accessibility.md             | 306 -------
 .../versioned_docs/version-0.60/animations.md | 409 ---------
 .../version-0.60/app-extensions.md            |  27 -
 .../version-0.60/communication-ios.md         | 201 -----
 .../version-0.60/components-and-apis.md       | 222 -----
 .../versioned_docs/version-0.60/debugging.md  | 182 ----
 .../version-0.60/direct-manipulation.md       | 207 -----
 .../versioned_docs/version-0.60/flexbox.md    | 229 -----
 .../version-0.60/getting-started.md           | 560 ------------
 .../version-0.60/handling-text-input.md       |  43 -
 .../version-0.60/headless-js-android.md       | 185 ----
 .../version-0.60/height-and-width.md          |  59 --
 website/versioned_docs/version-0.60/images.md | 223 -----
 .../integration-with-existing-apps.md         | 799 ------------------
 .../version-0.60/javascript-environment.md    |  90 --
 .../version-0.60/more-resources.md            |  44 -
 .../version-0.60/native-components-ios.md     | 512 -----------
 .../version-0.60/native-modules-android.md    | 484 -----------
 .../version-0.60/native-modules-setup.md      |  27 -
 .../versioned_docs/version-0.60/navigation.md |  69 --
 .../versioned_docs/version-0.60/network.md    | 193 -----
 .../version-0.60/performance.md               | 431 ----------
 website/versioned_docs/version-0.60/props.md  |  62 --
 .../removing-default-permissions.md           |  55 --
 .../version-0.60/running-on-simulator-ios.md  |  15 -
 .../version-0.60/signed-apk-android.md        | 145 ----
 website/versioned_docs/version-0.60/state.md  |  60 --
 website/versioned_docs/version-0.60/style.md  |  46 -
 website/versioned_docs/version-0.60/timers.md |  50 --
 .../version-0.60/troubleshooting.md           | 111 ---
 .../versioned_docs/version-0.60/tutorial.md   |  46 -
 .../versioned_docs/version-0.60/upgrading.md  | 124 ---
 .../version-0.60/using-a-scrollview.md        |  60 --
 67 files changed, 601 insertions(+), 6906 deletions(-)
 delete mode 100644 website/versioned_docs/version-0.59/images.md
 delete mode 100644 website/versioned_docs/version-0.60/accessibility.md
 delete mode 100644 website/versioned_docs/version-0.60/animations.md
 delete mode 100644 website/versioned_docs/version-0.60/app-extensions.md
 delete mode 100644 website/versioned_docs/version-0.60/communication-ios.md
 delete mode 100644 website/versioned_docs/version-0.60/components-and-apis.md
 delete mode 100644 website/versioned_docs/version-0.60/debugging.md
 delete mode 100644 website/versioned_docs/version-0.60/direct-manipulation.md
 delete mode 100644 website/versioned_docs/version-0.60/flexbox.md
 delete mode 100644 website/versioned_docs/version-0.60/getting-started.md
 delete mode 100644 website/versioned_docs/version-0.60/handling-text-input.md
 delete mode 100644 website/versioned_docs/version-0.60/headless-js-android.md
 delete mode 100644 website/versioned_docs/version-0.60/height-and-width.md
 delete mode 100644 website/versioned_docs/version-0.60/images.md
 delete mode 100644 website/versioned_docs/version-0.60/integration-with-existing-apps.md
 delete mode 100644 website/versioned_docs/version-0.60/javascript-environment.md
 delete mode 100644 website/versioned_docs/version-0.60/more-resources.md
 delete mode 100644 website/versioned_docs/version-0.60/native-components-ios.md
 delete mode 100644 website/versioned_docs/version-0.60/native-modules-android.md
 delete mode 100644 website/versioned_docs/version-0.60/native-modules-setup.md
 delete mode 100644 website/versioned_docs/version-0.60/navigation.md
 delete mode 100644 website/versioned_docs/version-0.60/network.md
 delete mode 100644 website/versioned_docs/version-0.60/performance.md
 delete mode 100644 website/versioned_docs/version-0.60/props.md
 delete mode 100644 website/versioned_docs/version-0.60/removing-default-permissions.md
 delete mode 100644 website/versioned_docs/version-0.60/running-on-simulator-ios.md
 delete mode 100644 website/versioned_docs/version-0.60/signed-apk-android.md
 delete mode 100644 website/versioned_docs/version-0.60/state.md
 delete mode 100644 website/versioned_docs/version-0.60/style.md
 delete mode 100644 website/versioned_docs/version-0.60/timers.md
 delete mode 100644 website/versioned_docs/version-0.60/troubleshooting.md
 delete mode 100644 website/versioned_docs/version-0.60/tutorial.md
 delete mode 100644 website/versioned_docs/version-0.60/upgrading.md
 delete mode 100644 website/versioned_docs/version-0.60/using-a-scrollview.md

diff --git a/website/versioned_docs/version-0.5/accessibility.md b/website/versioned_docs/version-0.5/accessibility.md
index c90414f01d2..e3b4bdf6ec2 100644
--- a/website/versioned_docs/version-0.5/accessibility.md
+++ b/website/versioned_docs/version-0.5/accessibility.md
@@ -8,7 +8,7 @@ original_id: accessibility
 
 Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
 
-In addition to this documentation, you might find [this blog post](https://code.facebook.com/posts/435862739941212/making-react-native-apps-accessible/) about React Native accessibility to be useful.
+In addition to this documentation, you might find [this blog post](https://engineering.fb.com/ios/making-react-native-apps-accessible/) about React Native accessibility to be useful.
 
 ## Making Apps Accessible
 
@@ -76,9 +76,9 @@ Inverting screen colors is an Accessibility feature that makes the iPhone and iP
 
 #### accessibilityRole (iOS, Android)
 
-> **Note:** Accessibility Role and Accessibility States are meant to be a cross-platform solution to replace `accessibilityTraits` and `accessibilityComponentType`, which will soon be deprecated. When possible, use `accessibilityRole` and `accessibilityStates` instead of `accessibilityTraits` and `accessibilityComponentType`.
+`accessibilityRole` communicates the purpose of a component to the user of an assistive technology.
 
-Accessibility Role tells a person using either VoiceOver on iOS or TalkBack on Android the type of element that is focused on. To use, set the `accessibilityRole` property to one of the following strings:
+`accessibilityRole` can be one of the following:
 
 - **none** Used when the element has no role.
 - **button** Used when the element should be treated as a button.
@@ -91,43 +91,38 @@ Accessibility Role tells a person using either VoiceOver on iOS or TalkBack on A
 - **imagebutton** Used when the element should be treated as a button and is also an image.
 - **header** Used when an element acts as a header for a content section (e.g. the title of a navigation bar).
 - **summary** Used when an element can be used to provide a quick summary of current conditions in the app when the app first launches.
+- **alert** Used when an element contains important text to be presented to the user.
+- **checkbox** Used when an element represents a checkbox which can be checked, unchecked, or have mixed checked state.
+- **combobox** Used when an element represents a combo box, which allows the user to select among several choices.
+- **menu** Used when the component is a menu of choices.
+- **menubar** Used when a component is a container of multiple menus.
+- **menuitem** Used to represent an item within a menu.
+- **progressbar** Used to represent a component which indicates progress of a task.
+- **radio** Used to represent a radio button.
+- **radiogroup** Used to represent a group of radio buttons.
+- **scrollbar** Used to represent a scroll bar.
+- **spinbutton** Used to represent a button which opens a list of choices.
+- **switch** Used to represent a switch which can be turned on and off.
+- **tab** Used to represent a tab.
+- **tablist** Used to represent a list of tabs.
+- **timer** Used to represent a timer.
+- **toolbar** Used to represent a tool bar (a container of action buttons or components).
 
 #### accessibilityStates (iOS, Android)
 
-> **Note:** > `accessibilityRole` and `accessibilityStates` are meant to be a cross-platform solution to replace `accessibilityTraits` and `accessibilityComponentType`, which will soon be deprecated. When possible, use `accessibilityRole` and `accessibilityStates` instead of `accessibilityTraits` and `accessibilityComponentType`.
+Describes the current state of a component to the user of an assistive technology.
 
-Accessibility State tells a person using either VoiceOver on iOS or TalkBack on Android the state of the element currently focused on. The state of the element can be set either to `selected` or `disabled` or both:
+`accessibilityStates` is an array of values, and may include any of the following:
 
 - **selected** Used when the element is in a selected state. For example, a button is selected.
 - **disabled** Used when the element is disabled and cannot be interacted with.
+- **checked** Used to indicate that a checkable element is currently checked.
+- **unchecked** Used to indicate that a checkable element is not currently checked.
+- **busy** Used to indicate that an element is currently busy.
+- **expanded** Used to indicate that an expandable element is currently expanded.
+- **collapsed** Used to indicate that an expandable element is currently collapsed.
 
-To use, set the `accessibilityStates` to an array containing either `selected`, `disabled`, or both.
-
-#### accessibilityTraits (iOS)
-
-> **Note:** `accessibilityTraits` will soon be deprecated. When possible, use `accessibilityRole` and `accessibilityStates` instead of `accessibilityTraits` and `accessibilityComponentType`.
-
-Accessibility traits tell a person using VoiceOver what kind of element they have selected. Is this element a label? A button? A header? These questions are answered by `accessibilityTraits`.
-
-To use, set the `accessibilityTraits` property to one of (or an array of) accessibility trait strings:
-
-- **none** Used when the element has no traits.
-- **button** Used when the element should be treated as a button.
-- **link** Used when the element should be treated as a link.
-- **header** Used when an element acts as a header for a content section (e.g. the title of a navigation bar).
-- **search** Used when the text field element should also be treated as a search field.
-- **image** Used when the element should be treated as an image. Can be combined with button or link, for example.
-- **selected** Used when the element is selected. For example, a selected row in a table or a selected button within a segmented control.
-- **plays** Used when the element plays its own sound when activated.
-- **key** Used when the element acts as a keyboard key.
-- **text** Used when the element should be treated as static text that cannot change.
-- **summary** Used when an element can be used to provide a quick summary of current conditions in the app when the app first launches. For example, when Weather first launches, the element with today's weather conditions is marked with this trait.
-- **disabled** Used when the control is not enabled and does not respond to user input.
-- **frequentUpdates** Used when the element frequently updates its label or value, but too often to send notifications. Allows an accessibility client to poll for changes. A stopwatch would be an example.
-- **startsMedia** Used when activating an element starts a media session (e.g. playing a movie, recording audio) that should not be interrupted by output from an assistive technology, like VoiceOver.
-- **adjustable** Used when an element can be "adjusted" (e.g. a slider).
-- **allowsDirectInteraction** Used when an element allows direct touch interaction for VoiceOver users (for example, a view representing a piano keyboard).
-- **pageTurn** Informs VoiceOver that it should scroll to the next page when it finishes reading the contents of the element.
+To use, set the `accessibilityStates` to an array containing the list of current states.
 
 #### accessibilityViewIsModal (iOS)
 
@@ -153,23 +148,6 @@ Assign this property to a custom function which will be called when someone perf
 
 Assign this property to a custom function which will be called when someone performs the "escape" gesture, which is a two finger Z shaped gesture. An escape function should move back hierarchically in the user interface. This can mean moving up or back in a navigation hierarchy or dismissing a modal user interface. If the selected element does not have an `onAccessibilityEscape` function, the system will attempt to traverse up the view hierarchy until it finds a view that does or bonk to indicate it was unable to find one.
 
-#### accessibilityComponentType (Android)
-
-> **Note:** > `accessibilityComponentType` will soon be deprecated. When possible, use `accessibilityRole` and `accessibilityStates` instead of `accessibilityTraits` and `accessibilityComponentType`.
-
-In some cases, we also want to alert the end user of the type of selected component (i.e., that it is a “button”). If we were using native buttons, this would work automatically. Since we are using javascript, we need to provide a bit more context for TalkBack. To do so, you must specify the ‘accessibilityComponentType’ property for any UI component. We support 'none', ‘button’, ‘radiobutton_checked’ and ‘radiobutton_unchecked’.
-
-```jsx
-<TouchableWithoutFeedback accessibilityComponentType=”button”
-  onPress={this._onPress}>
-  <View style={styles.button}>
-    <Text style={styles.buttonText}>Press me!</Text>
-  </View>
-</TouchableWithoutFeedback>
-```
-
-In the above example, the TouchableWithoutFeedback is being announced by TalkBack as a native Button.
-
 #### accessibilityLiveRegion (Android)
 
 When components dynamically change, we want TalkBack to alert the end user. This is made possible by the ‘accessibilityLiveRegion’ property. It can be set to ‘none’, ‘polite’ and ‘assertive’:
@@ -210,6 +188,59 @@ In the case of two overlapping UI components with the same parent, default acces
 
 In the above example, the yellow layout and its descendants are completely invisible to TalkBack and all other accessibility services. So we can easily use overlapping views with the same parent without confusing TalkBack.
 
+### Accessibility Actions
+
+Accessibility actions allow an assistive technology to programmatically invoke the actions of a component. In order to support accessibility actions, a component must do two things:
+
+- Define the list of actions it supports via the `accessibilityActions` property.
+- Implement an `onAccessibilityAction` function to handle action requests.
+
+The `accessibilityActions` property should contain a list of action objects. Each action object should contain the following fields:
+
+| Name  | Type   | Required |
+| ----- | ------ | -------- |
+| name  | string | Yes      |
+| label | string | No       |
+
+Actions either represent standard actions, such as clicking a button or adjusting a slider, or custom actions specific to a given component such as deleting an email message. The `name` field is required for both standard and custom actions, but `label` is optional for standard actions.
+
+When adding support for standard actions, `name` must be one of the following:
+
+- `'magicTap'` - iOS only - While VoiceOver focus is on or inside the component, the user double tapped with two fingers.
+- `'escape'` - iOS only - While VoiceOver focus is on or inside the component, the user performed a two finger scrub gesture (left, right, left).
+- `'activate'` - Activate the component. Typically this should perform the same action as when the user touches or clicks the component when not using an assistive technology. This is generated when a screen reader user double taps the component.
+- `'increment'` - Increment an adjustable component. On iOS, VoiceOver generates this action when the component has a role of `'adjustable'` and the user places focus on it and swipes upward. On Android, TalkBack generates this action when the user places accessibility focus on the component and presses the volume up button.
+- `'decrement'` - Decrement an adjustable component. On iOS, VoiceOver generates this action when the component has a role of `'adjustable'` and the user places focus on it and swipes downward. On Android, TalkBack generates this action when the user places accessibility focus on the component and presses the volume down button.
+- `'longpress'` - Android only - This action is generated when the user places accessibility focus on the component and double tap and holds one finger on the screen. Typically, this should perform the same action as when the user holds down one finger on the component while not using an assistive technology.
+
+The `label` field is optional for standard actions, and is often unused by assistive technologies. For custom actions, it is a localized string containing a description of the action to be presented to the user.
+
+To handle action requests, a component must implement an `onAccessibilityAction` function. The only argument to this function is an event containing the name of the action to perform. The below example from RNTester shows how to create a component which defines and handles several custom actions.
+
+```jsx
+<View
+  accessible={true}
+  accessibilityActions={[
+    {name: 'cut', label: 'cut'},
+    {name: 'copy', label: 'copy'},
+    {name: 'paste', label: 'paste'},
+  ]}
+  onAccessibilityAction={(event) => {
+    switch (event.nativeEvent.actionName) {
+      case 'cut':
+        Alert.alert('Alert', 'cut action success');
+        break;
+      case 'copy':
+        Alert.alert('Alert', 'copy action success');
+        break;
+      case 'paste':
+        Alert.alert('Alert', 'paste action success');
+        break;
+    }
+  }}
+/>
+```
+
 ### Checking if a Screen Reader is Enabled
 
 The `AccessibilityInfo` API allows you to determine whether or not a screen reader is currently active. See the [AccessibilityInfo documentation](accessibilityinfo.md) for details.
@@ -245,8 +276,31 @@ In the above example we've created a custom radio button that now behaves like a
 
 ## Testing VoiceOver Support (iOS)
 
-To enable VoiceOver, go to the Settings app on your iOS device. Tap General, then Accessibility. There you will find many tools that people use to make their devices more usable, such as bolder text, increased contrast, and VoiceOver.
+To enable VoiceOver, go to the Settings app on your iOS device (it's not available for simulator). Tap General, then Accessibility. There you will find many tools that people use to make their devices more usable, such as bolder text, increased contrast, and VoiceOver.
 
 To enable VoiceOver, tap on VoiceOver under "Vision" and toggle the switch that appears at the top.
 
 At the very bottom of the Accessibility settings, there is an "Accessibility Shortcut". You can use this to toggle VoiceOver by triple clicking the Home button.
+
+## Testing TalkBack Support (Android)
+
+To enable TalkBack, go to the Settings app on your Android device or emulator. Tap Accessibility, then TalkBack. Toggle the "Use service" switch to enable or disable it.
+
+P.S. Android emulator doesn’t have TalkBack by default. To install it:
+
+1. Download TalkBack file here: https://google-talkback.en.uptodown.com/android
+2. Drag the downloaded `.apk` file into the emulator
+
+You can use the volume key shortcut to toggle TalkBack. To turn on the volume key shortcut, go to the Settings app, then Accessibility. At the top, turn on Volume key shortcut.
+
+To use the volume key shortcut, press both volume keys for 3 seconds to start an accessibility tool.
+
+Additionally, if you prefer, you can toggle TalkBack via command line with:
+
+```
+# disable
+adb shell settings put secure enabled_accessibility_services com.android.talkback/com.google.android.marvin.talkback.TalkBackService
+
+# enable
+adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
+```
diff --git a/website/versioned_docs/version-0.5/animations.md b/website/versioned_docs/version-0.5/animations.md
index 7f0f9f4ffff..7b73d696aed 100644
--- a/website/versioned_docs/version-0.5/animations.md
+++ b/website/versioned_docs/version-0.5/animations.md
@@ -12,56 +12,48 @@ React Native provides two complementary animation systems: [`Animated`](animatio
 
 The [`Animated`](animated.md) API is designed to make it very easy to concisely express a wide variety of interesting animation and interaction patterns in a very performant way. `Animated` focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and simple `start`/`stop` methods to control time-based animation execution.
 
-`Animated` exports four animatable component types: `View`, `Text`, `Image`, and `ScrollView`, but you can also create your own using `Animated.createAnimatedComponent()`.
+`Animated` exports six animatable component types: `View`, `Text`, `Image`, `ScrollView`, `FlatList` and `SectionList`, but you can also create your own using `Animated.createAnimatedComponent()`.
 
 For example, a container view that fades in when it is mounted may look like this:
 
 ```SnackPlayer
-import React from 'react';
+import React, { useState, useEffect } from 'react';
 import { Animated, Text, View } from 'react-native';
 
-class FadeInView extends React.Component {
-  state = {
-    fadeAnim: new Animated.Value(0),  // Initial value for opacity: 0
-  }
+const FadeInView = (props) => {
+  const [fadeAdmin] = useState(new Animated.Value(0))  // Initial value for opacity: 0
 
-  componentDidMount() {
-    Animated.timing(                  // Animate over time
-      this.state.fadeAnim,            // The animated value to drive
+  React.useEffect(() => {
+    Animated.timing(
+      fadeAdmin,
       {
-        toValue: 1,                   // Animate to opacity: 1 (opaque)
-        duration: 10000,              // Make it take a while
+        toValue: 1,
+        duration: 10000,
       }
-    ).start();                        // Starts the animation
-  }
-
-  render() {
-    let { fadeAnim } = this.state;
-
-    return (
-      <Animated.View                 // Special animatable View
-        style={{
-          ...this.props.style,
-          opacity: fadeAnim,         // Bind opacity to animated value
-        }}
-      >
-        {this.props.children}
-      </Animated.View>
-    );
-  }
+    ).start();
+  }, [])
+
+  return (
+    <Animated.View                 // Special animatable View
+      style={{
+        ...props.style,
+        opacity: fadeAdnim,         // Bind opacity to animated value
+      }}
+    >
+      {props.children}
+    </Animated.View>
+  );
 }
 
 // You can then use your `FadeInView` in place of a `View` in your components:
-export default class App extends React.Component {
-  render() {
-    return (
-      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
-        <FadeInView style={{width: 250, height: 50, backgroundColor: 'powderblue'}}>
-          <Text style={{fontSize: 28, textAlign: 'center', margin: 10}}>Fading in</Text>
-        </FadeInView>
-      </View>
-    )
-  }
+export default () => {
+  return (
+    <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+      <FadeInView style={{width: 250, height: 50, backgroundColor: 'powderblue'}}>
+        <Text style={{fontSize: 28, textAlign: 'center', margin: 10}}>Fading in</Text>
+      </FadeInView>
+    </View>
+  )
 }
 ```
 
@@ -69,8 +61,7 @@ Let's break down what's happening here. In the `FadeInView` constructor, a new `
 
 When the component mounts, the opacity is set to 0. Then, an easing animation is started on the `fadeAnim` animated value, which will update all of its dependent mappings (in this case, just the opacity) on each frame as the value animates to the final value of 1.
 
-This is done in an optimized way that is faster than calling `setState` and re-rendering.  
-Because the entire configuration is declarative, we will be able to implement further optimizations that serialize the configuration and runs the animation on a high-priority thread.
+This is done in an optimized way that is faster than calling `setState` and re-rendering. Because the entire configuration is declarative, we will be able to implement further optimizations that serialize the configuration and runs the animation on a high-priority thread.
 
 ### Configuring animations
 
@@ -258,7 +249,7 @@ You may notice that there is no obvious way to read the current value while anim
 
 ### Using the native driver
 
-The `Animated` API is designed to be serializable. By using the [native driver](http://facebook.github.io/react-native/blog/2017/02/14/using-native-driver-for-animated.html), we send everything about the animation to native before starting the animation, allowing native code to perform the animation on the UI thread without having to go through the bridge on every frame. Once the animation has started, the JS thread can be blocked without affecting the animation.
+The `Animated` API is designed to be serializable. By using the [native driver](http://facebook.github.io/react-native/blog/2017/02/14/using-native-driver-for-animated), we send everything about the animation to native before starting the animation, allowing native code to perform the animation on the UI thread without having to go through the bridge on every frame. Once the animation has started, the JS thread can be blocked without affecting the animation.
 
 Using the native driver for normal animations is quite simple. Just add `useNativeDriver: true` to the animation config when starting it.
 
@@ -319,8 +310,8 @@ While using transform styles such as `rotateY`, `rotateX`, and others ensure the
 
 The RNTester app has various examples of `Animated` in use:
 
-- [AnimatedGratuitousApp](https://github.com/facebook/react-native/tree/master/RNTester/js/AnimatedGratuitousApp)
-- [NativeAnimationsExample](https://github.com/facebook/react-native/blob/master/RNTester/js/NativeAnimationsExample.js)
+- [AnimatedGratuitousApp](https://github.com/facebook/react-native/tree/master/RNTester/js/examples/Animated/AnimatedGratuitousApp)
+- [NativeAnimationsExample](https://github.com/facebook/react-native/blob/master/RNTester/js/examples/NativeAnimation/NativeAnimationsExample.js)
 
 ## `LayoutAnimation` API
 
@@ -415,4 +406,4 @@ As mentioned [in the Direct Manipulation section](direct-manipulation.md), `setN
 
 We could use this in the Rebound example to update the scale - this might be helpful if the component that we are updating is deeply nested and hasn't been optimized with `shouldComponentUpdate`.
 
-If you find your animations with dropping frames (performing below 60 frames per second), look into using `setNativeProps` or `shouldComponentUpdate` to optimize them. Or you could run the animations on the UI thread rather than the JavaScript thread [with the useNativeDriver option](http://facebook.github.io/react-native/blog/2017/02/14/using-native-driver-for-animated.html). You may also want to defer any computationally intensive work until after animations are complete, using the [InteractionManager](interactionmanager.md). You can monitor the frame rate by using the In-App Developer Menu "FPS Monitor" tool.
+If you find your animations with dropping frames (performing below 60 frames per second), look into using `setNativeProps` or `shouldComponentUpdate` to optimize them. Or you could run the animations on the UI thread rather than the JavaScript thread [with the useNativeDriver option](http://facebook.github.io/react-native/blog/2017/02/14/using-native-driver-for-animated). You may also want to defer any computationally intensive work until after animations are complete, using the [InteractionManager](interactionmanager.md). You can monitor the frame rate by using the In-App Developer Menu "FPS Monitor" tool.
diff --git a/website/versioned_docs/version-0.5/app-extensions.md b/website/versioned_docs/version-0.5/app-extensions.md
index a27630bec52..bf6f30e1dd2 100644
--- a/website/versioned_docs/version-0.5/app-extensions.md
+++ b/website/versioned_docs/version-0.5/app-extensions.md
@@ -10,7 +10,7 @@ App extensions let you provide custom functionality and content outside of your
 
 As these extensions are loaded outside of the regular app sandbox, it's highly likely that several of these app extensions will be loaded simultaneously. As you might expect, these extensions have small memory usage limits. Keep these in mind when developing your app extensions. It's always highly recommended to test your application on an actual device, and more so when developing app extensions: too frequently, developers find that their extension works just fine in the iOS Simulator, only to get user reports that their extension is not loading on actual devices.
 
-We highly recommend that you watch Conrad Kramer's talk on [Memory Use in Extensions](https://cocoaheads.tv/memory-use-in-extensions-by-conrad-kramer/) to learn more about this topic.
+We highly recommend that you watch Conrad Kramer's talk on [Memory Use in Extensions](https://www.youtube.com/watch?v=GqXMqn6MXrM) to learn more about this topic.
 
 ### Today widget
 
diff --git a/website/versioned_docs/version-0.5/communication-ios.md b/website/versioned_docs/version-0.5/communication-ios.md
index 4b3fe1a4c86..2afc10b0453 100644
--- a/website/versioned_docs/version-0.5/communication-ios.md
+++ b/website/versioned_docs/version-0.5/communication-ios.md
@@ -35,9 +35,9 @@ RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
 
 ```jsx
 import React from 'react';
-import {AppRegistry, View, Image} from 'react-native';
+import {View, Image} from 'react-native';
 
-class ImageBrowserApp extends React.Component {
+export default class ImageBrowserApp extends React.Component {
   renderImage(imgURI) {
     return <Image source={{uri: imgURI}} />;
   }
@@ -45,8 +45,6 @@ class ImageBrowserApp extends React.Component {
     return <View>{this.props.images.map(this.renderImage)}</View>;
   }
 }
-
-AppRegistry.registerComponent('ImageBrowserApp', () => ImageBrowserApp);
 ```
 
 `RCTRootView` also provides a read-write property `appProperties`. After `appProperties` is set, the React Native app is re-rendered with new properties. The update is only performed when the new updated properties differ from the previous ones.
diff --git a/website/versioned_docs/version-0.5/components-and-apis.md b/website/versioned_docs/version-0.5/components-and-apis.md
index 9ce293713f2..af38cd9a26a 100644
--- a/website/versioned_docs/version-0.5/components-and-apis.md
+++ b/website/versioned_docs/version-0.5/components-and-apis.md
@@ -105,10 +105,6 @@ Many of the following components provide wrappers for commonly used UIKit classe
     <h3><a href="./imagepickerios">ImagePickerIOS</a></h3>
     <p>Renders a image picker on iOS.</p>
   </div>
-  <div class="component">
-    <h3><a href="./navigatorios">NavigatorIOS</a></h3>
-    <p>A wrapper around <code>UINavigationController</code>, enabling you to implement a navigation stack.</p>
-  </div>
   <div class="component">
     <h3><a href="./progressviewios">ProgressViewIOS</a></h3>
     <p>Renders a <code>UIProgressView</a></code> on iOS.</p>
@@ -187,10 +183,6 @@ These components may come in handy for certain applications. For an exhaustive l
     <h3><a href="./animated">Animated</a></h3>
     <p>A library for creating fluid, powerful animations that are easy to build and maintain.</p>
   </div>
-  <div class="component">
-    <h3><a href="./cameraroll">CameraRoll</a></h3>
-    <p>Provides access to the local camera roll / gallery.</p>
-  </div>
   <div class="component">
     <h3><a href="./clipboard">Clipboard</a></h3>
     <p>Provides an interface for setting and getting content from the clipboard on both iOS and Android.</p>
diff --git a/website/versioned_docs/version-0.5/debugging.md b/website/versioned_docs/version-0.5/debugging.md
index fa2b6bd3ec8..a839a4d548b 100644
--- a/website/versioned_docs/version-0.5/debugging.md
+++ b/website/versioned_docs/version-0.5/debugging.md
@@ -24,7 +24,7 @@ Instead of recompiling your app every time you make a change, you can reload you
 
 You can speed up your development times by having your app reload automatically any time your code changes. Automatic reloading can be enabled by selecting "Enable Live Reload" from the Developer Menu.
 
-You may even go a step further and keep your app running as new versions of your files are injected into the JavaScript bundle automatically by enabling [Hot Reloading](https://facebook.github.io/react-native/blog/2016/03/24/introducing-hot-reloading.html) from the Developer Menu. This will allow you to persist the app's state through reloads.
+You may even go a step further and keep your app running as new versions of your files are injected into the JavaScript bundle automatically by enabling [Hot Reloading](https://facebook.github.io/react-native/blog/2016/03/24/introducing-hot-reloading) from the Developer Menu. This will allow you to persist the app's state through reloads.
 
 > There are some instances where hot reloading cannot be implemented perfectly. If you run into any issues, use a full reload to reset your app.
 
@@ -89,7 +89,7 @@ However, there are some disadvantages:
 
 ## React Developer Tools
 
-You can use [the standalone version of React Developer Tools](https://github.com/facebook/react-devtools/tree/master/packages/react-devtools) to debug the React component hierarchy. To use it, install the `react-devtools` package globally:
+You can use [the standalone version of React Developer Tools](https://github.com/facebook/react/tree/master/packages/react-devtools) to debug the React component hierarchy. To use it, install the `react-devtools` package globally:
 
 ```
 npm install -g react-devtools
diff --git a/website/versioned_docs/version-0.5/direct-manipulation.md b/website/versioned_docs/version-0.5/direct-manipulation.md
index 5229742d2ee..b759df48f30 100644
--- a/website/versioned_docs/version-0.5/direct-manipulation.md
+++ b/website/versioned_docs/version-0.5/direct-manipulation.md
@@ -8,7 +8,7 @@ It is sometimes necessary to make changes directly to a component without using
 
 > Use setNativeProps when frequent re-rendering creates a performance bottleneck
 >
-> Direct manipulation will not be a tool that you reach for frequently; you will typically only be using it for creating continuous animations to avoid the overhead of rendering the component hierarchy and reconciling many views. `setNativeProps` is imperative and stores state in the native layer (DOM, UIView, etc.) and not within your React components, which makes your code more difficult to reason about. Before you use it, try to solve your problem with `setState` and [shouldComponentUpdate](http://facebook.github.io/react/advanced-performance.md#shouldcomponentupdate-in-action).
+> Direct manipulation will not be a tool that you reach for frequently; you will typically only be using it for creating continuous animations to avoid the overhead of rendering the component hierarchy and reconciling many views. `setNativeProps` is imperative and stores state in the native layer (DOM, UIView, etc.) and not within your React components, which makes your code more difficult to reason about. Before you use it, try to solve your problem with `setState` and [shouldComponentUpdate](https://reactjs.org/docs/optimizing-performance.html#shouldcomponentupdate-in-action).
 
 ## setNativeProps with TouchableOpacity
 
@@ -55,7 +55,7 @@ render() {
 
 This is computationally intensive compared to the original example - React needs to re-render the component hierarchy each time the opacity changes, even though other properties of the view and its children haven't changed. Usually this overhead isn't a concern but when performing continuous animations and responding to gestures, judiciously optimizing your components can improve your animations' fidelity.
 
-If you look at the implementation of `setNativeProps` in [NativeMethodsMixin](https://github.com/facebook/react-native/blob/master/Libraries/Renderer/oss/ReactNativeRenderer-prod.js) you will notice that it is a wrapper around `RCTUIManager.updateView` - this is the exact same function call that results from re-rendering - see [receiveComponent in ReactNativeBaseComponent](https://github.com/facebook/react-native/blob/fb2ec1ea47c53c2e7b873acb1cb46192ac74274e/Libraries/Renderer/oss/ReactNativeRenderer-prod.js#L5793-L5813).
+If you look at the implementation of `setNativeProps` in [NativeMethodsMixin](https://github.com/facebook/react-native/blob/master/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js) you will notice that it is a wrapper around `RCTUIManager.updateView` - this is the exact same function call that results from re-rendering - see [receiveComponent in ReactNativeBaseComponent](https://github.com/facebook/react-native/blob/fb2ec1ea47c53c2e7b873acb1cb46192ac74274e/Libraries/Renderer/oss/ReactNativeRenderer-prod.js#L5793-L5813).
 
 ## Composite components and setNativeProps
 
@@ -140,10 +140,10 @@ export default class App extends React.Component {
 
   render() {
     return (
-      <View style={{flex: 1}}>
+      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
         <TextInput
           ref={component => this._textInput = component}
-          style={{height: 50, flex: 1, marginHorizontal: 20, borderWidth: 1, borderColor: '#ccc'}}
+          style={{height: 50, width: 200, marginHorizontal: 20, borderWidth: 1, borderColor: '#ccc'}}
         />
         <TouchableOpacity onPress={this.clearText}>
           <Text>Clear text</Text>
@@ -190,7 +190,7 @@ Determines the location of the given view in the window and returns the values v
 
 ### measureLayout(relativeToNativeNode, onSuccess, onFail)
 
-Like `measure()`, but measures the view relative an ancestor, specified as `relativeToNativeNode`. This means that the returned x, y are relative to the origin x, y of the ancestor view.
+Like `measure()`, but measures the view relative to an ancestor, specified as `relativeToNativeNode`. This means that the returned x, y are relative to the origin x, y of the ancestor view.
 
 As always, to obtain a native node handle for a component, you can use `findNodeHandle(component)`.
 
diff --git a/website/versioned_docs/version-0.5/flexbox.md b/website/versioned_docs/version-0.5/flexbox.md
index 236e6226c6a..b531fa1e890 100644
--- a/website/versioned_docs/version-0.5/flexbox.md
+++ b/website/versioned_docs/version-0.5/flexbox.md
@@ -10,13 +10,31 @@ You will normally use a combination of `flexDirection`, `alignItems`, and `justi
 
 > Flexbox works the same way in React Native as it does in CSS on the web, with a few exceptions. The defaults are different, with `flexDirection` defaulting to `column` instead of `row`, and the `flex` parameter only supporting a single number.
 
+### Flex
+
+[`flex`](https://facebook.github.io/react-native/docs/layout-props#flex) will define how your items are going to **“fill”** over the available space along your main axis. Space will be divided according to each element's flex property.
+
+In the following example the red, yellow and the green views are all children in the container view that has `flex: 1` set. The red view uses `flex: 1` , the yellow view uses `flex: 2` and the green view uses `flex: 3` . **1+2+3 = 6** which means that the red view will get `1/6` of the space, the yellow `2/6` of the space and the green `3/6` of the space.
+
+![Flex](https://cdn-images-1.medium.com/max/800/1*PhCFmO5tYX_sZSyCd4vO3w.png)
+
 #### Flex Direction
 
-Adding `flexDirection` to a component's `style` determines the **primary axis** of its layout. Should the children be organized horizontally (`row`) or vertically (`column`)? The default is `column`.
+[`flexDirection`](https://facebook.github.io/react-native/docs/layout-props#flexdirection) controls the direction in which the children of a node are laid out. This is also referred to as the _main axis_. The cross axis is the axis perpendicular to the main axis, or the axis which the wrapping lines are laid out in.
+
+- `row` Align children from left to right. If wrapping is enabled then the next line will start under the first item on the left of the container.
+
+- `column` (**default value**) Align children from top to bottom. If wrapping is enabled then the next line will start to the left first item on the top of the container.
+
+- `row-reverse` Align children from right to left. If wrapping is enabled then the next line will start under the first item on the right of the container.
+
+- `column-reverse` Align children from bottom to top. If wrapping is enabled then the next line will start to the left first item on the bottom of the container.
+
+LEARN MORE [HERE](https://yogalayout.com/docs/flex-direction)
 
-```SnackPlayer
+```SnackPlayer name=Flex%20Direction
 import React, { Component } from 'react';
-import { AppRegistry, View } from 'react-native';
+import { View } from 'react-native';
 
 export default class FlexDirectionBasics extends Component {
   render() {
@@ -30,18 +48,39 @@ export default class FlexDirectionBasics extends Component {
     );
   }
 };
-
-// skip this line if using Create React Native App
-AppRegistry.registerComponent('AwesomeProject', () => FlexDirectionBasics);
 ```
 
+![Flex Direction](https://cdn-images-1.medium.com/max/800/1*rA7IbuUsJWsx6evKAsabVw.png)
+
+### Layout Direction
+
+Layout direction specifies the direction in which children and text in a hierarchy should be laid out. Layout direction also affects what edge `start` and `end` refer to. By default React Native lays out with LTR layout direction. In this mode `start` refers to left and `end` refers to right.
+
+- `LTR` (**default value**) Text and children are laid out from left to right. Margin and padding applied the start of an element are applied on the left side.
+
+- `RTL` Text and children are laid out from right to left. Margin and padding applied the start of an element are applied on the right side.
+
 #### Justify Content
 
-Adding `justifyContent` to a component's style determines the **distribution** of children along the **primary axis**. Should children be distributed at the start, the center, the end, or spaced evenly? Available options are `flex-start`, `center`, `flex-end`, `space-around`, `space-between` and `space-evenly`.
+[`justifyContent`](https://facebook.github.io/react-native/docs/layout-props#justifycontent) describes how to align children within the main axis of their container. For example, you can use this property to center a child horizontally within a container with `flexDirection` set to `row` or vertically within a container with `flexDirection` set to `column`.
+
+- `flex-start`(**default value**) Align children of a container to the start of the container's main axis.
+
+- `flex-end` Align children of a container to the end of the container's main axis.
+
+- `center` Align children of a container in the center of the container's main axis.
 
-```SnackPlayer
+- `space-between` Evenly space of children across the container's main axis, distributing remaining space between the children.
+
+- `space-around` Evenly space of children across the container's main axis, distributing remaining space around the children. Compared to `space-between` using `space-around` will result in space being distributed to the beginning of the first child and end of the last child.
+
+- `space-evenly` Evenly distributed within the alignment container along the main axis. The spacing between each pair of adjacent items, the main-start edge and the first item, and the main-end edge and the last item, are all exactly the same.
+
+LEARN MORE [HERE](https://yogalayout.com/docs/justify-content)
+
+```SnackPlayer name=Justify%20Content
 import React, { Component } from 'react';
-import { AppRegistry, View } from 'react-native';
+import { View } from 'react-native';
 
 export default class JustifyContentBasics extends Component {
   render() {
@@ -60,20 +99,31 @@ export default class JustifyContentBasics extends Component {
     );
   }
 };
-
-// skip this line if using Create React Native App
-AppRegistry.registerComponent('AwesomeProject', () => JustifyContentBasics);
 ```
 
+![Justify Content](https://cdn-images-1.medium.com/max/800/1*i5TVlme-TisAVvD5ax2yPA.png)
+
 #### Align Items
 
-Adding `alignItems` to a component's style determines the **alignment** of children along the **secondary axis** (if the primary axis is `row`, then the secondary is `column`, and vice versa). Should children be aligned at the start, the center, the end, or stretched to fill? Available options are `flex-start`, `center`, `flex-end`, and `stretch`.
+[`alignItems`](https://facebook.github.io/react-native/docs/layout-props#alignitems) describes how to align children along the cross axis of their container. Align items is very similar to `justifyContent` but instead of applying to the main axis, `alignItems` applies to the cross axis.
+
+- `stretch` (**default value**) Stretch children of a container to match the `height` of the container's cross axis.
+
+- `flex-start` Align children of a container to the start of the container's cross axis.
+
+- `flex-end` Align children of a container to the end of the container's cross axis.
+
+- `center` Align children of a container in the center of the container's cross axis.
+
+- `baseline` Align children of a container along a common baseline. Individual children can be set to be the reference baseline for their parents.
 
 > For `stretch` to have an effect, children must not have a fixed dimension along the secondary axis. In the following example, setting `alignItems: stretch` does nothing until the `width: 50` is removed from the children.
 
-```SnackPlayer
+LEARN MORE [HERE](https://yogalayout.com/docs/align-items)
+
+```SnackPlayer name=Align%20Items
 import React, { Component } from 'react';
-import { AppRegistry, View } from 'react-native';
+import { View } from 'react-native';
 
 export default class AlignItemsBasics extends Component {
   render() {
@@ -94,13 +144,86 @@ export default class AlignItemsBasics extends Component {
     );
   }
 };
-
-// skip this line if using Create React Native App
-AppRegistry.registerComponent('AwesomeProject', () => AlignItemsBasics);
 ```
 
+![Align Items](https://cdn-images-1.medium.com/max/800/1*evkM7zfxt-9p-HJ1M0Bh2g.png)
+
+### Align Self
+
+[`alignSelf`](https://facebook.github.io/react-native/docs/layout-props#alignself) has the same options and effect as `alignItems` but instead of affecting the children within a container, you can apply this property to a single child to change its alignment within its parent. `alignSelf` overrides any option set by the parent with `alignItems`.
+
+![Align Self](https://cdn-images-1.medium.com/max/800/1*J1JCoKwLCokX9JXVBvP71g.png)
+
+### Align Content
+
+[alignContent](https://facebook.github.io/react-native/docs/layout-props#aligncontent) defines the distribution of lines along the cross-axis. This only has effect when items are wrapped to multiple lines using `flexWrap`.
+
+- `flex-start` (**default value**) Align wrapped lines to the start of the container's cross axis.
+
+- `flex-end` Align wrapped lines to the end of the container's cross axis.
+
+- `stretch` wrapped lines to match the height of the container's cross axis.
+
+- `center` Align wrapped lines in the center of the container's cross axis.
+
+- `space-between` Evenly space wrapped lines across the container's main axis, distributing remaining space between the lines.
+
+- `space-around` Evenly space wrapped lines across the container's main axis, distributing remaining space around the lines. Compared to space between using space around will result in space being distributed to the begining of the first lines and end of the last line.
+
+LEARN MORE [HERE](https://yogalayout.com/docs/align-content)
+
+![Align Content](https://cdn-images-1.medium.com/max/800/1*cC2XFyCF_igp20Ombt4wBw.png)
+
+### Flex Wrap
+
+The [`flexWrap`](https://facebook.github.io/react-native/docs/layout-props#flexwrap) property is set on containers and controls what happens when children overflow the size of the container along the main axis. By default children are forced into a single line (which can shrink elements). If wrapping is allowed items are wrapped into multiple lines along the main axis if needed.
+
+When wrapping lines `alignContent` can be used to specify how the lines are placed in the container. learn more [here](https://yogalayout.com/docs/flex-wrap)
+
+![Flex Wrap](https://cdn-images-1.medium.com/max/800/1*_7v4uQhSsuCn1cfeOMVfrA.png)
+
+### Flex Basis, Grow, and Shrink
+
+- [`flexGrow`](https://facebook.github.io/react-native/docs/layout-props#flexgrow) describes how any space within a container should be distributed among its children along the main axis. After laying out its children, a container will distribute any remaining space according to the flex grow values specified by its children.
+
+  flexGrow accepts any floating point value >= 0, with 0 being the default value. A container will distribute any remaining space among its children weighted by the child’s flex grow value.
+
+- [`flexShrink`](https://facebook.github.io/react-native/docs/layout-props#flexshrink) describes how to shrink children along the main axis in the case that the total size of the children overflow the size of the container on the main axis. Flex shrink is very similar to flex grow and can be thought of in the same way if any overflowing size is considered to be negative remaining space. These two properties also work well together by allowing children to grow and shrink as needed.
+
+  Flex shrink accepts any floating point value >= 0, with 1 being the default value. A container will shrink its children weighted by the child’s flex shrink value.
+
+- [`flexBasis`](https://facebook.github.io/react-native/docs/layout-props#flexbasis) is an axis-independent way of providing the default size of an item along the main axis. Setting the flex basis of a child is similar to setting the `width` of that child if its parent is a container with `flexDirection: row` or setting the `height` of a child if its parent is a container with `flexDirection: column`. The flex basis of an item is the default size of that item, the size of the item before any flex grow and flex shrink calculations are performed.
+
+LEARN MORE [HERE](https://yogalayout.com/docs/flex)
+
+### Width and Height
+
+The `width` property in Yoga specifies the width of the element's content area. Similarly height property specifies the `height` of the element's content area.
+
+Both `width` and `height` can take following values:
+
+- `auto` Is the **default Value**, React Native calculates the width/height for the element based on its content, whether that is other children, text, or an image.
+
+- `pixels` Defines the width/height in absolute pixels. Depending on other styles set on the component, this may or may not be the final dimension of the node.
+
+- `percentage` Defines the width or height in percentage of its parent's width or height respectively.
+
+### Absolute & Relative Layout
+
+The `position` type of an element defines how it is positioned within its parent.
+
+`relative` (**default value**) By default an element is positioned relatively. This means an element is positioned according to the normal flow of the layout, and then offset relative to that position based on the values of `top`, `right`, `bottom`, and `left`. The offset does not affect the position of any sibling or parent elements.
+
+`absolute` When positioned absolutely an element doesn't take part in the normal layout flow. It is instead laid out independent of its siblings. The position is determined based on the `top`, `right`, `bottom`, and `left` values.
+
+![Absolute & Relative Layoutp](https://cdn-images-1.medium.com/max/800/1*NlPeRQCQK3Vb5nyjL0Mqxw.png)
+
 #### Going Deeper
 
+Check out the interactive [yoga playground](https://yogalayout.com/playground) that you can use to get a better understanding of flexbox.
+
 We've covered the basics, but there are many other styles you may need for layouts. The full list of props that control layout is documented [here](./layout-props.md).
 
 We're getting close to being able to build a real application. One thing we are still missing is a way to take user input, so let's move on to [learn how to handle text input with the TextInput component](handling-text-input.md).
+
+See some examples from [Wix Engineers](https://medium.com/wix-engineering/the-full-react-native-layout-cheat-sheet-a4147802405c):
diff --git a/website/versioned_docs/version-0.5/getting-started.md b/website/versioned_docs/version-0.5/getting-started.md
index 031a6711cfe..c2e04056c11 100644
--- a/website/versioned_docs/version-0.5/getting-started.md
+++ b/website/versioned_docs/version-0.5/getting-started.md
@@ -6,9 +6,9 @@ original_id: getting-started
 
 This page will help you install and build your first React Native app. If you already have React Native installed, you can skip ahead to the [Tutorial](tutorial.md).
 
-<strong>If you are coming from a web background</strong>, the easiest way to get started with React Native is with Expo tools because they allow you to start a project without installing and configuring Xcode or Android Studio. Expo CLI sets up a development environment on your local machine and you can be writing a React Native app within minutes. For instant development, you can use [Snack](https://snack.expo.io/) to try React Native out directly in your web browser.
+<strong>If you are new to mobile development</strong>, the easiest way to get started is with Expo CLI. Expo is a set of tools built around React Native and, while it has many [features](https://expo.io/features), the most relevant feature for us right now is that it can get you writing a React Native app within minutes. You will only need a recent version of Node.js and a phone or emulator. If you'd like to try out React Native directly in your web browser before installing any tools, you can try out [Snack](https://snack.expo.io/).
 
-<strong>If you are familiar with native development</strong>, you will likely want to use React Native CLI. It requires Xcode or Android Studio to get started. If you already have one of these tools installed, you should be able to get up and running within a few minutes. If they are not installed, you should expect to spend about an hour installing and configuring them.
+<strong>If you are already familiar with mobile development</strong>, you may want to use React Native CLI. It requires Xcode or Android Studio to get started. If you already have one of these tools installed, you should be able to get up and running within a few minutes. If they are not installed, you should expect to spend about an hour installing and configuring them.
 
 <div class="toggler">
   <ul role="tablist" id="toggle-guide">
@@ -23,7 +23,7 @@ This page will help you install and build your first React Native app. If you al
 
 <block class="quickstart mac windows linux ios android" />
 
-Assuming that you have [Node 10+](https://nodejs.org/en/download/) installed, you can use npm to install the Expo CLI command line utility:
+Assuming that you have [Node 10 LTS](https://nodejs.org/en/download/) or greater installed, you can use npm to install the Expo CLI command line utility:
 
 ```sh
 npm install -g expo-cli
@@ -40,21 +40,21 @@ npm start # you can also use: expo start
 
 This will start a development server for you.
 
-## Running your React Native application
+<h2>Running your React Native application</h2>
 
 Install the [Expo](https://expo.io) client app on your iOS or Android phone and connect to the same wireless network as your computer. On Android, use the Expo app to scan the QR code from your terminal to open your project. On iOS, follow on-screen instructions to get a link.
 
-### Modifying your app
+<h3>Modifying your app</h3>
 
 Now that you have successfully run the app, let's modify it. Open `App.js` in your text editor of choice and edit some lines. The application should reload automatically once you save your changes.
 
-### That's it!
+<h3>That's it!</h3>
 
 Congratulations! You've successfully run and modified your first React Native app.
 
 <center><img src="/react-native/docs/assets/GettingStartedCongratulations.png" width="150"></img></center>
 
-## Now what?
+<h2>Now what?</h3>
 
 Expo also has [docs](https://docs.expo.io) you can reference if you have questions specific to the tool. You can also ask for help at [Expo forums](https://forums.expo.io).
 
@@ -67,54 +67,54 @@ If you have a problem with Expo, before creating a new issue, please see if ther
 
 If you're curious to learn more about React Native, continue on to the [Tutorial](tutorial.md).
 
-### Running your app on a simulator or virtual device
+<h3>Running your app on a simulator or virtual device</h3>
 
-Expo CLI makes it really easy to run your React Native app on a physical device without setting up a development environment. If you want to run your app on the iOS Simulator or an Android Virtual Device, please refer to the instructions for building projects with native code to learn how to install Xcode or set up your Android development environment.
+Expo CLI makes it really easy to run your React Native app on a physical device without setting up a development environment. If you want to run your app on the iOS Simulator or an Android Virtual Device, please refer to the instructions for "React Native CLI Quickstart" to learn how to install Xcode or set up your Android development environment.
 
 Once you've set these up, you can launch your app on an Android Virtual Device by running `npm run android`, or on the iOS Simulator by running `npm run ios` (macOS only).
 
-### Caveats
+<h3>Caveats</h3>
 
 Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
 
-If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "[eject](https://docs.expo.io/versions/latest/expokit/eject)" eventually to create your own native builds. If you do eject, the "Building Projects with Native Code" instructions will be required to continue working on your project.
+If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "[eject](https://docs.expo.io/versions/latest/expokit/eject)" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
 
 Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check [this document](https://docs.expo.io/versions/latest/sdk/#sdk-version) to find out what versions are supported.
 
-If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "Building Projects with Native Code" above for instructions on configuring a native build environment for React Native.
+If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
 
 <block class="native mac windows linux ios android" />
 
-<p>Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from <a href="getting-started.html" onclick="displayTab('guide', 'quickstart')">Expo</a> or Create React Native App, you'll need this section.</p>
+<p>Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from <a href="getting-started" onclick="displayTab('guide', 'quickstart')">Expo</a>, you'll need this section.</p>
 
 The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you just have to pick one to start with, since the setup is a bit different.
 
 <div class="toggler">
   <span>Development OS:</span>
   <span role="tablist" id="toggle-os">
-    <button role="tab" class="button-mac" onclick="displayTab('os', 'mac')">macOS</button>
-    <button role="tab" class="button-windows" onclick="displayTab('os', 'windows')">Windows</button>
-    <button role="tab" class="button-linux" onclick="displayTab('os', 'linux')">Linux</button>
+    <button role="tab" class="button-mac" onclick="displayTab('os', 'mac')">macOS</a>
+    <button role="tab" class="button-windows" onclick="displayTab('os', 'windows')">Windows</a>
+    <button role="tab" class="button-linux" onclick="displayTab('os', 'linux')">Linux</a>
   </span>
 </div>
 
 <div class="toggler">
   <span>Target OS:</span>
   <span role="tablist" id="toggle-platform">
-    <button role="tab" class="button-ios" onclick="displayTab('platform', 'ios')">iOS</button>
-    <button role="tab" class="button-android" onclick="displayTab('platform', 'android')">Android</button>
+    <button role="tab" class="button-ios" onclick="displayTab('platform', 'ios')">iOS</a>
+    <button role="tab" class="button-android" onclick="displayTab('platform', 'android')">Android</a>
   </span>
 </div>
 
 <block class="native linux windows ios" />
 
-## Unsupported
+<h2>Unsupported</h2>
 
-<blockquote><p>A Mac is required to build projects with native code for iOS. You can follow the <a href="getting-started.html" onclick="displayTab('guide', 'quickstart')">Quick Start</a> to learn how to build your app using Expo instead.</p></blockquote>
+<blockquote><p>A Mac is required to build projects with native code for iOS. You can follow the <a href="getting-started" onclick="displayTab('guide', 'quickstart')">Quick Start</a> to learn how to build your app using Expo instead.</p></blockquote>
 
 <block class="native mac ios" />
 
-## Installing dependencies
+<h2>Installing dependencies</h2>
 
 You will need Node, Watchman, the React Native command line interface, and Xcode.
 
@@ -122,19 +122,19 @@ While you can use any editor of your choice to develop your app, you will need t
 
 <block class="native mac android" />
 
-## Installing dependencies
+<h2>Installing dependencies</h2>
 
 You will need Node, Watchman, the React Native command line interface, a JDK, and Android Studio.
 
 <block class="native linux android" />
 
-## Installing dependencies
+<h2>Installing dependencies</h2>
 
 You will need Node, the React Native command line interface, a JDK, and Android Studio.
 
 <block class="native windows android" />
 
-## Installing dependencies
+<h2>Installing dependencies</h2>
 
 You will need Node, the React Native command line interface, Python2, a JDK, and Android Studio.
 
@@ -144,28 +144,33 @@ While you can use any editor of your choice to develop your app, you will need t
 
 <block class="native mac ios android" />
 
-### Node, Watchman
+<h3>Node, Watchman, JDK</h3>
 
-We recommend installing Node and Watchman using [Homebrew](http://brew.sh/). Run the following commands in a Terminal after installing Homebrew:
+We recommend installing Node, Watchman, and JDK using [Homebrew](http://brew.sh/). Run the following commands in a Terminal after installing Homebrew:
 
 ```
+brew install yarn
 brew install node
 brew install watchman
+brew tap AdoptOpenJDK/openjdk
+brew cask install adoptopenjdk8
 ```
 
 If you have already installed Node on your system, make sure it is Node 8.3 or newer.
 
 [Watchman](https://facebook.github.io/watchman) is a tool by Facebook for watching changes in the filesystem. It is highly recommended you install it for better performance.
 
+If you have already installed JDK on your system, make sure it is JDK 8 or newer.
+
 <block class="native linux android" />
 
-### Node
+<h3>Node</h3>
 
 Follow the [installation instructions for your Linux distribution](https://nodejs.org/en/download/package-manager/) to install Node 8.3 or newer.
 
 <block class='native windows android' />
 
-### Node, Python2, JDK
+<h3>Node, Python2, JDK</h3>
 
 We recommend installing Node and Python2 via [Chocolatey](https://chocolatey.org), a popular package manager for Windows.
 
@@ -183,7 +188,7 @@ If you have already installed Node on your system, make sure it is Node 8.3 or n
 
 <block class="native mac ios android" />
 
-### The React Native CLI
+<h3>The React Native CLI</h3>
 
 Node comes with npm, which lets you install the React Native command line interface.
 
@@ -197,7 +202,7 @@ npm install -g react-native-cli
 
 <block class="native windows linux android" />
 
-### The React Native CLI
+<h3>The React Native CLI</h3>
 
 Node comes with npm, which lets you install the React Native command line interface.
 
@@ -211,33 +216,33 @@ npm install -g react-native-cli
 
 <block class="native mac ios" />
 
-### Xcode
+<h3>Xcode</h3>
 
 The easiest way to install Xcode is via the [Mac App Store](https://itunes.apple.com/us/app/xcode/id497799835?mt=12). Installing Xcode will also install the iOS Simulator and all the necessary tools to build your iOS app.
 
 If you have already installed Xcode on your system, make sure it is version 9.4 or newer.
 
-#### Command Line Tools
+<h4>Command Line Tools<h4>
 
 You will also need to install the Xcode Command Line Tools. Open Xcode, then choose "Preferences..." from the Xcode menu. Go to the Locations panel and install the tools by selecting the most recent version in the Command Line Tools dropdown.
 
 ![Xcode Command Line Tools](/react-native/docs/assets/GettingStartedXcodeCommandLineTools.png)
 
-<block class="native mac linux android" />
+<block class="native linux android" />
 
-### Java Development Kit
+<h3>Java Development Kit</h3>
 
-React Native requires a recent version of the Java SE Development Kit (JDK). [Download and install Oracle JDK 8](http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html) if needed. You can also use [OpenJDK 8](http://openjdk.java.net/install/) as an alternative.
+React Native requires version 8 of the Java SE Development Kit (JDK). You may download and install [OpenJDK](http://openjdk.java.net) from [AdoptOpenJDK](https://adoptopenjdk.net/) or your system packager. You may also [Download and install Oracle JDK 8](http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html) if desired.
 
 <block class="native mac linux windows android" />
 
-### Android development environment
+<h3>Android development environment</h3>
 
 Setting up your development environment can be somewhat tedious if you're new to Android development. If you're already familiar with Android development, there are a few things you may need to configure. In either case, please make sure to carefully follow the next few steps.
 
 <block class="native mac windows linux android" />
 
-#### 1. Install Android Studio
+<h4>1. Install Android Studio</h4>
 
 [Download and install Android Studio](https://developer.android.com/studio/index.html). Choose a "Custom" setup when prompted to select an installation type. Make sure the boxes next to all of the following are checked:
 
@@ -262,7 +267,7 @@ Then, click "Next" to install all of these components.
 
 Once setup has finalized and you're presented with the Welcome screen, proceed to the next step.
 
-#### 2. Install the Android SDK
+<h4>2. Install the Android SDK</h4>
 
 Android Studio installs the latest Android SDK by default. Building a React Native app with native code, however, requires the `Android 9 (Pie)` SDK in particular. Additional Android SDKs can be installed through the SDK Manager in Android Studio.
 
@@ -289,13 +294,13 @@ Next, select the "SDK Tools" tab and check the box next to "Show Package Details
 
 Finally, click "Apply" to download and install the Android SDK and related build tools.
 
-#### 3. Configure the ANDROID_HOME environment variable
+<h4>3. Configure the ANDROID_HOME environment variable</h4>
 
 The React Native tools require some environment variables to be set up in order to build apps with native code.
 
 <block class="native mac linux android" />
 
-Add the following lines to your `$HOME/.bash_profile` config file:
+Add the following lines to your `$HOME/.bash_profile` or `$HOME/.bashrc` config file:
 
 <block class="native mac android" />
 
@@ -341,7 +346,7 @@ You can find the actual location of the SDK in the Android Studio "Preferences"
 
 Open a new Command Prompt window to ensure the new environment variable is loaded before proceeding to the next step.
 
-#### 4. Add platform-tools to Path
+<h4>4. Add platform-tools to Path</h4>
 
 Open the System pane under **System and Security** in the Windows Control Panel, then click on **Change settings...**. Open the **Advanced** tab and click on **Environment Variables...**. Select the **Path** variable, then click **Edit**. Click **New** and add the path to platform-tools to the list.
 
@@ -353,7 +358,7 @@ c:\Users\YOUR_USERNAME\AppData\Local\Android\Sdk\platform-tools
 
 <block class="native linux android" />
 
-### Watchman
+<h3>Watchman</h3>
 
 Follow the [Watchman installation guide](https://facebook.github.io/watchman/docs/install.html#buildinstall) to compile and install Watchman from source.
 
@@ -361,7 +366,7 @@ Follow the [Watchman installation guide](https://facebook.github.io/watchman/doc
 
 <block class="native mac ios" />
 
-## Creating a new application
+<h2>Creating a new application</h2>
 
 Use the React Native command line interface to generate a new React Native project called "AwesomeProject":
 
@@ -371,9 +376,9 @@ react-native init AwesomeProject
 
 This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Expo (or Create React Native App), or if you're adding iOS support to an existing React Native project (see [Platform Specific Code](platform-specific-code.md)). You can also use a third-party CLI to init your React Native app, such as [Ignite CLI](https://github.com/infinitered/ignite).
 
-### [Optional] Using a specific version
+<h3>[Optional] Using a specific version</h3>
 
-If you want to start a new project with a specifc React Native version, you can use the `--version` argument:
+If you want to start a new project with a specific React Native version, you can use the `--version` argument:
 
 ```
 react-native init AwesomeProject --version X.XX.X
@@ -385,7 +390,7 @@ react-native init AwesomeProject --version react-native@next
 
 <block class="native mac windows linux android" />
 
-## Creating a new application
+<h2>Creating a new application</h2>
 
 Use the React Native command line interface to generate a new React Native project called "AwesomeProject":
 
@@ -395,9 +400,9 @@ react-native init AwesomeProject
 
 This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Create React Native App, or if you're adding Android support to an existing React Native project (see [Platform Specific Code](platform-specific-code.md)). You can also use a third-party CLI to init your React Native app, such as [Ignite CLI](https://github.com/infinitered/ignite).
 
-### [Optional] Using a specific version
+<h3>[Optional] Using a specific version</h3>
 
-If you want to start a new project with a specifc React Native version, you can use the `--version` argument:
+If you want to start a new project with a specific React Native version, you can use the `--version` argument:
 
 ```
 react-native init AwesomeProject --version X.XX.X
@@ -409,17 +414,17 @@ react-native init AwesomeProject --version react-native@next
 
 <block class="native mac windows linux android" />
 
-## Preparing the Android device
+<h2>Preparing the Android device</h2>
 
 You will need an Android device to run your React Native Android app. This can be either a physical Android device, or more commonly, you can use an Android Virtual Device which allows you to emulate an Android device on your computer.
 
 Either way, you will need to prepare the device to run Android apps for development.
 
-### Using a physical device
+<h3>Using a physical device</h3>
 
 If you have a physical Android device, you can use it for development in place of an AVD by plugging it in to your computer using a USB cable and following the instructions [here](running-on-device.md).
 
-### Using a virtual device
+<h3>Using a virtual device</h3>
 
 If you use Android Studio to open `./AwesomeProject/android`, you can see the list of available Android Virtual Devices (AVDs) by opening the "AVD Manager" from within Android Studio. Look for an icon that looks like this:
 
@@ -445,7 +450,7 @@ Click "Next" then "Finish" to create your AVD. At this point you should be able
 
 <block class="native mac ios" />
 
-## Running your React Native application
+<h2>Running your React Native application</h2>
 
 Run `react-native run-ios` inside your React Native project folder:
 
@@ -458,17 +463,17 @@ You should see your new app running in the iOS Simulator shortly.
 
 ![AwesomeProject on iOS](/react-native/docs/assets/GettingStartediOSSuccess.png)
 
-`react-native run-ios` is just one way to run your app. You can also run it directly from within Xcode or [Nuclide](https://nuclide.io/).
+`react-native run-ios` is just one way to run your app. You can also run it directly from within Xcode.
 
 > If you can't get this to work, see the [Troubleshooting](troubleshooting.md#content) page.
 
-### Running on a device
+<h3>Running on a device</h3>
 
 The above command will automatically run your app on the iOS Simulator by default. If you want to run the app on an actual physical iOS device, please follow the instructions [here](running-on-device.md).
 
 <block class="native mac windows linux android" />
 
-## Running your React Native application
+<h2>Running your React Native application</h2>
 
 Run `react-native run-android` inside your React Native project folder:
 
@@ -489,13 +494,13 @@ If everything is set up correctly, you should see your new app running in your A
 
 <block class="native mac windows linux android" />
 
-`react-native run-android` is just one way to run your app - you can also run it directly from within Android Studio or [Nuclide](https://nuclide.io/).
+`react-native run-android` is just one way to run your app - you can also run it directly from within Android Studio.
 
 > If you can't get this to work, see the [Troubleshooting](troubleshooting.md#content) page.
 
 <block class="native mac ios android" />
 
-### Modifying your app
+<h3>Modifying your app</h3>
 
 Now that you have successfully run the app, let's modify it.
 
@@ -511,7 +516,7 @@ Now that you have successfully run the app, let's modify it.
 
 <block class="native windows linux android" />
 
-### Modifying your app
+<h3>Modifying your app</h3>
 
 Now that you have successfully run the app, let's modify it.
 
@@ -520,7 +525,7 @@ Now that you have successfully run the app, let's modify it.
 
 <block class="native mac ios android" />
 
-### That's it!
+<h3>That's it!</h3>
 
 Congratulations! You've successfully run and modified your first React Native app.
 
@@ -528,7 +533,7 @@ Congratulations! You've successfully run and modified your first React Native ap
 
 <block class="native windows linux android" />
 
-### That's it!
+<h3>That's it!</h3>
 
 Congratulations! You've successfully run and modified your first React Native app.
 
@@ -536,7 +541,7 @@ Congratulations! You've successfully run and modified your first React Native ap
 
 <block class="native mac ios" />
 
-## Now what?
+<h2>Now what?</h2>
 
 - Turn on [Live Reload](debugging.md#reloading-javascript) in the Developer Menu. Your app will now reload automatically whenever you save any changes!
 
@@ -546,7 +551,7 @@ If you're curious to learn more about React Native, continue on to the [Tutorial
 
 <block class="native windows linux mac android" />
 
-## Now what?
+<h2>Now what?</h2>
 
 - Turn on [Live Reload](debugging.md#reloading-javascript) in the Developer Menu. Your app will now reload automatically whenever you save any changes!
 
diff --git a/website/versioned_docs/version-0.5/handling-text-input.md b/website/versioned_docs/version-0.5/handling-text-input.md
index 70622bf5993..e7cd81c83d7 100644
--- a/website/versioned_docs/version-0.5/handling-text-input.md
+++ b/website/versioned_docs/version-0.5/handling-text-input.md
@@ -8,9 +8,9 @@ original_id: handling-text-input
 
 For example, let's say that as the user types, you're translating their words into a different language. In this new language, every single word is written the same way: 🍕. So the sentence "Hello there Bob" would be translated as "🍕🍕🍕".
 
-```SnackPlayer
+```SnackPlayer name=Handling%20Text%20Input
 import React, { Component } from 'react';
-import { AppRegistry, Text, TextInput, View } from 'react-native';
+import { Text, TextInput, View } from 'react-native';
 
 export default class PizzaTranslator extends Component {
   constructor(props) {
@@ -25,6 +25,7 @@ export default class PizzaTranslator extends Component {
           style={{height: 40}}
           placeholder="Type here to translate!"
           onChangeText={(text) => this.setState({text})}
+          value={this.state.text}
         />
         <Text style={{padding: 10, fontSize: 42}}>
           {this.state.text.split(' ').map((word) => word && '🍕').join(' ')}
@@ -33,9 +34,6 @@ export default class PizzaTranslator extends Component {
     );
   }
 }
-
-// skip this line if using Create React Native App
-AppRegistry.registerComponent('AwesomeProject', () => PizzaTranslator);
 ```
 
 In this example, we store `text` in the state, because it changes over time.
diff --git a/website/versioned_docs/version-0.5/headless-js-android.md b/website/versioned_docs/version-0.5/headless-js-android.md
index e26f0d6c3e5..7cfa4e67dba 100644
--- a/website/versioned_docs/version-0.5/headless-js-android.md
+++ b/website/versioned_docs/version-0.5/headless-js-android.md
@@ -67,8 +67,47 @@ service.putExtras(bundle);
 getApplicationContext().startService(service);
 ```
 
+## Retries
+
+By default, the headless JS task will not perform any retries. In order to do so, you need to create a `HeadlessJsRetryPolicy` and throw a specfic `Error`.
+
+`LinearCountingRetryPolicy` is an implementation of `HeadlessJsRetryPolicy` that allows you to specify a maximum number of retries with a fixed delay between each attempt. If that does not suit your needs then you can easily implement your own `HeadlessJsRetryPolicy`. These policies can simply be passed as an extra argument to the `HeadlessJsTaskConfig` constructor, e.g.
+
+```java
+HeadlessJsRetryPolicy retryPolicy = new LinearCountingRetryPolicy(
+  3, // Max number of retry attempts
+  1000 // Delay between each retry attempt
+);
+
+return new HeadlessJsTaskConfig(
+  'SomeTaskName',
+  Arguments.fromBundle(extras),
+  5000,
+  false,
+  retryPolicy
+);
+```
+
+A retry attempt will only be made when a specific `Error` is thrown. Inside a headless JS task, you can import the error and throw it when a retry attempt is required.
+
+Example:
+
+```jsx
+import {HeadlessJsTaskError} from 'HeadlessJsTask';
+
+module.exports = async (taskData) => {
+  const condition = ...;
+  if (!condition) {
+    throw new HeadlessJsTaskError();
+  }
+};
+```
+
+If you wish all errors to cause a retry attempt, you will need to catch them and throw the above error.
+
 ## Caveats
 
+- The function passed to `setTimeout` does not always behave as expected. Instead the function is called only when the application is launched again. If you just need to wait, use the retry functionality.
 - By default, your app will crash if you try to run a task while the app is in the foreground. This is to prevent developers from shooting themselves in the foot by doing a lot of work in a task and slowing the UI. You can pass a fourth `boolean` argument to control this behaviour.
 - If you start your service from a `BroadcastReceiver`, make sure to call `HeadlessJsTaskService.acquireWakeLockNow()` before returning from `onReceive()`.
 
diff --git a/website/versioned_docs/version-0.5/height-and-width.md b/website/versioned_docs/version-0.5/height-and-width.md
index 95a7b6f9fbb..e478ba61d9a 100644
--- a/website/versioned_docs/version-0.5/height-and-width.md
+++ b/website/versioned_docs/version-0.5/height-and-width.md
@@ -10,9 +10,9 @@ A component's height and width determine its size on the screen.
 
 The simplest way to set the dimensions of a component is by adding a fixed `width` and `height` to style. All dimensions in React Native are unitless, and represent density-independent pixels.
 
-```SnackPlayer
+```SnackPlayer name=Height%20and%20Width
 import React, { Component } from 'react';
-import { AppRegistry, View } from 'react-native';
+import { View } from 'react-native';
 
 export default class FixedDimensionsBasics extends Component {
   render() {
@@ -25,9 +25,6 @@ export default class FixedDimensionsBasics extends Component {
     );
   }
 }
-
-// skip this line if using Create React Native App
-AppRegistry.registerComponent('AwesomeProject', () => FixedDimensionsBasics);
 ```
 
 Setting dimensions this way is common for components that should always render at exactly the same size, regardless of screen dimensions.
@@ -38,9 +35,9 @@ Use `flex` in a component's style to have the component expand and shrink dynami
 
 > A component can only expand to fill available space if its parent has dimensions greater than 0. If a parent does not have either a fixed `width` and `height` or `flex`, the parent will have dimensions of 0 and the `flex` children will not be visible.
 
-```SnackPlayer
+````SnackPlayer name=Flex%20Dimensions
 import React, { Component } from 'react';
-import { AppRegistry, View } from 'react-native';
+import { View } from 'react-native';
 
 export default class FlexDimensionsBasics extends Component {
   render() {
@@ -56,9 +53,7 @@ export default class FlexDimensionsBasics extends Component {
     );
   }
 }
-
-// skip this line if using Create React Native App
-AppRegistry.registerComponent('AwesomeProject', () => FlexDimensionsBasics);
 ```
 
 After you can control a component's size, the next step is to [learn how to lay it out on the screen](flexbox.md).
+````
diff --git a/website/versioned_docs/version-0.5/images.md b/website/versioned_docs/version-0.5/images.md
index 169d3d12e0d..b5644f98d29 100644
--- a/website/versioned_docs/version-0.5/images.md
+++ b/website/versioned_docs/version-0.5/images.md
@@ -68,7 +68,7 @@ Note that image sources required this way include size (width, height) info for
 
 The `require` syntax described above can be used to statically include audio, video or document files in your project as well. Most common file types are supported including `.mp3`, `.wav`, `.mp4`, `.mov`, `.html` and `.pdf`. See [packager defaults](https://github.com/facebook/metro/blob/master/packages/metro-config/src/defaults/defaults.js#L14-L44) for the full list.
 
-You can add support for other types by creating a packager config file (see the [packager config file](https://github.com/facebook/react-native/blob/master/local-cli/util/Config.js#L68) for the full list of configuration options).
+You can add support for other types by adding an [`assetExts` resolver option](https://facebook.github.io/metro/docs/en/configuration#assetexts) in your [Metro configuration](https://facebook.github.io/metro/docs/en/configuration).
 
 A caveat is that videos must use absolute positioning instead of `flexGrow`, since size info is not currently passed for non-image assets. This limitation doesn't occur for videos that are linked directly into Xcode or the Assets folder for Android.
 
@@ -163,7 +163,7 @@ In some cases you might only want to display an image if it is already in the lo
 
 ## Local Filesystem Images
 
-See [CameraRoll](cameraroll.md) for an example of using local resources that are outside of `Images.xcassets`.
+See [CameraRoll](https://github.com/react-native-community/react-native-cameraroll) for an example of using local resources that are outside of `Images.xcassets`.
 
 ### Best Camera Roll Image
 
diff --git a/website/versioned_docs/version-0.5/integration-with-existing-apps.md b/website/versioned_docs/version-0.5/integration-with-existing-apps.md
index 6a9b8f00f38..6fbb390f945 100644
--- a/website/versioned_docs/version-0.5/integration-with-existing-apps.md
+++ b/website/versioned_docs/version-0.5/integration-with-existing-apps.md
@@ -9,7 +9,7 @@ React Native is great when you are starting a new mobile app from scratch. Howev
 The specific steps are different depending on what platform you're targeting.
 
 <div class="toggler">
-  <ul role="tablist" id="toggle-language">
+  <ul role="tablist" id="toggle-language" >
     <li id="objc" class="button-objc" aria-selected="false" role="tab" tabindex="0" aria-controls="objctab" onclick="displayTab('language', 'objc')">
       iOS (Objective-C)
     </li>
@@ -165,24 +165,30 @@ target 'NumberTileGame' do
 
   # Your 'node_modules' directory is probably in the root of your project,
   # but if not, adjust the `:path` accordingly
-  pod 'React', :path => '../node_modules/react-native', :subspecs => [
-    'Core',
-    'CxxBridge', # Include this for RN >= 0.47
-    'DevSupport', # Include this to enable In-App Devmenu if RN >= 0.43
-    'RCTText',
-    'RCTNetwork',
-    'RCTWebSocket', # Needed for debugging
-    'RCTAnimation', # Needed for FlatList and animations running on native UI thread
-    # Add any other subspecs you want to use in your project
-  ]
-  # Explicitly include Yoga if you are using RN >= 0.42.0
+  pod 'React', :path => '../node_modules/react-native/'
+  pod 'React-Core', :path => '../node_modules/react-native/React'
+  pod 'React-DevSupport', :path => '../node_modules/react-native/React'
+  pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
+  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
+  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
+  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
+  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
+  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
+  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
+  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
+  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
+  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
+  pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'
+
+  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
+  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
+  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
+  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
   pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
 
-  # Third party deps podspec link
   pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
   pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
   pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
-
 end
 ```
 
diff --git a/website/versioned_docs/version-0.5/javascript-environment.md b/website/versioned_docs/version-0.5/javascript-environment.md
index 23d21f67617..92dc226aad9 100644
--- a/website/versioned_docs/version-0.5/javascript-environment.md
+++ b/website/versioned_docs/version-0.5/javascript-environment.md
@@ -9,7 +9,7 @@ original_id: javascript-environment
 When using React Native, you're going to be running your JavaScript code in two environments:
 
 - In most cases, React Native will use [JavaScriptCore](http://trac.webkit.org/wiki/JavaScriptCore), the JavaScript engine that powers Safari. Note that on iOS, JavaScriptCore does not use JIT due to the absence of writable executable memory in iOS apps.
-- When using Chrome debugging, all JavaScript code runs within Chrome itself, communicating with native code via WebSockets. Chrome uses [V8](https://code.google.com/p/v8/) as its JavaScript engine.
+- When using Chrome debugging, all JavaScript code runs within Chrome itself, communicating with native code via WebSockets. Chrome uses [V8](https://v8.dev/) as its JavaScript engine.
 
 While both environments are very similar, you may end up hitting some inconsistencies. We're likely going to experiment with other JavaScript engines in the future, so it's best to avoid relying on specifics of any runtime.
 
@@ -48,16 +48,16 @@ ES8
 
 Stage 3
 
-- [Object Spread](https://github.com/sebmarkbage/ecmascript-rest-spread): `var extended = { ...obj, a: 10 };`
-
-Stage 1
-
+- [Object Spread](https://github.com/tc39/proposal-object-rest-spread): `var extended = { ...obj, a: 10 };`
+- [Static class fields](https://github.com/tc39/proposal-static-class-features): `class CustomDate { static epoch = new CustomDate(0); }`
 - [Optional Chaining](https://github.com/tc39/proposal-optional-chaining): `var name = obj.user?.name;`
 
 Specific
 
 - [JSX](https://reactjs.org/docs/jsx-in-depth.html): `<View style={{color: 'red'}} />`
-- [Flow](http://flowtype.org/): `function foo(x: ?number): string {};`
+- [Flow](https://flowtype.org/): `function foo(x: ?number): string {};`
+- [TypeScript](https://flowtype.org/): `function foo(x: number | undefined): string {};`
+- [Babel Template](https://babeljs.io/docs/en/babel-template): allows AST templating
 
 ## Polyfills
 
@@ -69,7 +69,6 @@ Browser
 - [CommonJS require](https://nodejs.org/docs/latest/api/modules.html)
 - [XMLHttpRequest, fetch](network.md#content)
 - [{set, clear}{Timeout, Interval, Immediate}, {request, cancel}AnimationFrame](timers.md#content)
-- [navigator.geolocation](geolocation.md#content)
 
 ES6
 
diff --git a/website/versioned_docs/version-0.5/more-resources.md b/website/versioned_docs/version-0.5/more-resources.md
index 0f195877cf3..938c2c28ae3 100644
--- a/website/versioned_docs/version-0.5/more-resources.md
+++ b/website/versioned_docs/version-0.5/more-resources.md
@@ -16,7 +16,7 @@ If you're looking for a library that does a specific thing, check out [Awesome R
 
 ## Examples
 
-Try out apps from the [Showcase](/react-native/showcase.html) to see what React Native is capable of! There are also some [example apps on GitHub](https://github.com/ReactNativeNews/React-Native-Apps). You can run the apps on a simulator or device, and you can see the source code for these apps, which is neat.
+Try out apps from the [Showcase](/react-native/showcase/) to see what React Native is capable of! There are also some [example apps on GitHub](https://github.com/ReactNativeNews/React-Native-Apps). You can run the apps on a simulator or device, and you can see the source code for these apps, which is neat.
 
 The folks who built the app for Facebook's F8 conference also [open-sourced the code](https://github.com/fbsamples/f8app) and wrote up a [detailed series of tutorials](http://makeitopen.com/). This is useful if you want a more in-depth example that's more realistic than most sample apps out there.
 
@@ -25,7 +25,7 @@ The folks who built the app for Facebook's F8 conference also [open-sourced the
 - Fellow developers write and publish React Native modules to npm and open source them on GitHub.
 - Making modules helps grow the React Native ecosystem and community. We recommend writing modules for your use cases and sharing them on npm.
 - Read the guides on Native Modules ([iOS](native-modules-ios.md), [Android](native-modules-android.md)) and Native UI Components ([iOS](native-components-ios.md), [Android](native-components-android.md)) if you are interested in extending native functionality.
-- Looking for a pre-built component? Check [JS.coach](https://js.coach/react-native) or [Native Directory](https://native.directory/) to find what the community has been creating.
+- Looking for a pre-built component? Check [JS.coach](https://js.coach/react-native) or [Native Directory](https://www.native.directory) to find what the community has been creating.
 
 ## Development Tools
 
@@ -39,6 +39,6 @@ The folks who built the app for Facebook's F8 conference also [open-sourced the
 
 [Yoga](https://yogalayout.com/) is a stand-alone layout engine that extends beyond React Native and allows product engineers to build layouts quickly for multiple platforms with a highly optimized open source layout engine designed with speed, size, and ease of use in mind.
 
-[Bugsnag](https://www.bugsnag.com/), [Microsoft App Center](https://appcenter.ms/), and [Sentry](https://sentry.io/welcome/) all provide excellent crash and error monitoring services for React and React Native apps. These services allow you to proactively monitor crashes and issues occuring on your apps in real time so you can fix them quickly and improve user experience.
+[Bugsnag](https://www.bugsnag.com/), [Microsoft App Center](https://appcenter.ms/), and [Sentry](https://sentry.io/welcome/) all provide excellent crash and error monitoring services for React and React Native apps. These services allow you to proactively monitor crashes and issues occurring on your apps in real time so you can fix them quickly and improve user experience.
 
 The [React Developer Tools](debugging.md#react-developer-tools) are great for debugging React and React Native apps.
diff --git a/website/versioned_docs/version-0.5/native-components-ios.md b/website/versioned_docs/version-0.5/native-components-ios.md
index f55f5584bb6..15e3c60295b 100644
--- a/website/versioned_docs/version-0.5/native-components-ios.md
+++ b/website/versioned_docs/version-0.5/native-components-ios.md
@@ -383,6 +383,79 @@ class MyApp extends React.Component {
 }
 ```
 
+## Handling multiple native views
+
+A React Native view can have more than one child view in the view tree eg.
+
+```jsx
+<View>
+  <MyNativeView />
+  <MyNativeView />
+  <Button />
+</View>
+```
+
+In this example, the class `MyNativeView` is a wrapper for a `NativeComponent` and exposes methods, which will be called on the iOS platform. `MyNativeView` is defined in `MyNativeView.ios.js` and contains proxy methods of `NativeComponent`.
+
+When the user interacts with the component, like clicking the button, the `backgroundColor` of `MyNativeView` changes. In this case `UIManager` would not know which `MyNativeView` should be handled and which one should change `backgroundColor`. Below you will find a solution to this problem:
+
+```jsx
+<View>
+  <MyNativeView ref={this.myNativeReference}>/>
+  <MyNativeView ref={this.myNativeReference2}>/>
+  <Button onPress={() => { this.myNativeReference.callNativeMethod() }}/>
+</View>
+```
+
+Now the above component has a reference to a particular `MyNativeView` which allows us to use a specific instance of `MyNativeView`. Now the button can control which `MyNativeView` should change its `backgroundColor`. In this example let's assume that `callNativeMethod` changes `backgroundColor`.
+
+`MyNativeView.ios.js` contains code as follow:
+
+```jsx
+class MyNativeView extends React.Component<> {
+  callNativeMethod = () => {
+    UIManager.dispatchViewManagerCommand(
+      ReactNative.findNodeHandle(this),
+      UIManager.getViewManagerConfig('RNCMyNativeView').Commands
+        .callNativeMethod,
+      [],
+    );
+  };
+
+  render() {
+    return <NativeComponent ref={NATIVE_COMPONENT_REF} />;
+  }
+}
+```
+
+`callNativeMethod` is our custom iOS method which for example changes the `backgroundColor` which is exposed through `MyNativeView`. This method uses `UIManager.dispatchViewManagerCommand` which needs 3 parameters:
+
+- (nonnull NSNumber \*)reactTag  -  id of react view.
+- commandID:(NSInteger)commandID  -  Id of the native method that should be called
+- commandArgs:(NSArray<id> \*)commandArgs  -  Args of the native method that we can pass from JS to native.
+
+`RNCMyNativeViewManager.m`
+
+```objectivec
+#import <React/RCTViewManager.h>
+#import <React/RCTUIManager.h>
+#import <React/RCTLog.h>
+
+RCT_EXPORT_METHOD(callNativeMethod:(nonnull NSNumber*) reactTag) {
+    [self.bridge.uiManager addUIBlock:^(RCTUIManager *uiManager, NSDictionary<NSNumber *,UIView *> *viewRegistry) {
+        NativeView *view = viewRegistry[reactTag];
+        if (!view || ![view isKindOfClass:[NativeView class]]) {
+            RCTLogError(@"Cannot find NativeView with tag #%@", reactTag);
+            return;
+        }
+        [view callNativeMethod];
+    }];
+
+}
+```
+
+Here the `callNativeMethod` is defined in the `RNCMyNativeViewManager.m` file and contains only one parameter which is `(nonnull NSNumber*) reactTag`. This exported function will find a particular view using `addUIBlock` which contains the `viewRegistry` parameter and returns the component based on `reactTag` allowing it to call the method on the correct component.
+
 ## Styles
 
 Since all our native react views are subclasses of `UIView`, most style attributes will work like you would expect out of the box. Some components will want a default style, however, for example `UIDatePicker` which is a fixed size. This default style is important for the layout algorithm to work as expected, but we also want to be able to override the default style when using the component. `DatePickerIOS` does this by wrapping the native component in an extra view, which has flexible styling, and using a fixed style (which is generated with constants passed in from native) on the inner native component:
diff --git a/website/versioned_docs/version-0.5/native-modules-android.md b/website/versioned_docs/version-0.5/native-modules-android.md
index cda3e2d1e92..6f9e3488886 100644
--- a/website/versioned_docs/version-0.5/native-modules-android.md
+++ b/website/versioned_docs/version-0.5/native-modules-android.md
@@ -45,7 +45,7 @@ public class ToastModule extends ReactContextBaseJavaModule {
   private static final String DURATION_SHORT_KEY = "SHORT";
   private static final String DURATION_LONG_KEY = "LONG";
 
-  public ToastModule(ReactApplicationContext reactContext) {
+  ToastModule(ReactApplicationContext reactContext) {
     super(reactContext);
   }
 }
@@ -148,9 +148,12 @@ import com.your-app-name.CustomToastPackage; // <-- Add this line with your pack
 ...
 
 protected List<ReactPackage> getPackages() {
-    return Arrays.<ReactPackage>asList(
-            new MainReactPackage(),
-            new CustomToastPackage()); // <-- Add this line with your package name.
+  @SuppressWarnings("UnnecessaryLocalVariable")
+  List<ReactPackage> packages = new PackageList(this).getPackages();
+  // Packages that cannot be autolinked yet can be added manually here, for example:
+  // packages.add(new MyReactNativePackage());
+  packages.add(new CustomToastPackage()); // <-- Add this line with your package name.
+  return packages;
 }
 ```
 
@@ -179,7 +182,7 @@ import ToastExample from './ToastExample';
 ToastExample.show('Awesome', ToastExample.SHORT);
 ```
 
-Please make sure this JavasScript file to be the same hierarchy as `ToastExample.js`.
+Please make sure this JavaScript is in the same hierarchy as `ToastExample.js`.
 
 ## Beyond Toasts
 
@@ -236,7 +239,7 @@ It is very important to highlight that the callback is not invoked immediately a
 
 ### Promises
 
-Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's `async/await` syntax. When the last parameter of a bridged native method is a `Promise`, its corresponding JS method will return a JS Promise object.
+Native modules can also fulfill a promise, which can simplify your JavaScript, especially when using ES2016's `async/await` syntax. When the last parameter of a bridged native method is a `Promise`, its corresponding JS method will return a JS Promise object.
 
 Refactoring the above code to use a promise instead of callbacks looks like this:
 
@@ -300,6 +303,8 @@ Native modules can signal events to JavaScript without being invoked directly. T
 
 ```java
 ...
+import com.facebook.react.modules.core.DeviceEventManagerModule;
+...
 private void sendEvent(ReactContext reactContext,
                        String eventName,
                        @Nullable WritableMap params) {
@@ -411,7 +416,7 @@ public class ImagePickerModule extends ReactContextBaseJavaModule {
     }
   };
 
-  public ImagePickerModule(ReactApplicationContext reactContext) {
+  ImagePickerModule(ReactApplicationContext reactContext) {
     super(reactContext);
 
     // Add the listener for `onActivityResult`
diff --git a/website/versioned_docs/version-0.5/native-modules-setup.md b/website/versioned_docs/version-0.5/native-modules-setup.md
index 09dc6bfe633..156f5a2daad 100644
--- a/website/versioned_docs/version-0.5/native-modules-setup.md
+++ b/website/versioned_docs/version-0.5/native-modules-setup.md
@@ -6,22 +6,22 @@ original_id: native-modules-setup
 
 Native modules are usually distributed as npm packages, except that on top of the usual Javascript they will include some native code per platform. To understand more about npm packages you may find [this guide](https://docs.npmjs.com/getting-started/publishing-npm-packages) useful.
 
-To get set up with the basic project structure for a native module we will use a third party tool [react-native-create-library](https://github.com/frostney/react-native-create-library). You can go ahead further and dive deep into how that library works, for our needs we will just need:
+To get set up with the basic project structure for a native module we will use a third party tool [create-react-native-module](https://github.com/brodybits/create-react-native-module). You can go ahead further and dive deep into how that library works, for our needs we will just need:
 
 ```
-$ npm install -g react-native-create-library
-$ react-native-create-library MyLibrary
+$ yarn global add create-react-native-module
+$ create-react-native-module MyLibrary
 ```
 
 Where MyLibrary is the name you would like for the new module. After doing this you will navigate into `MyLibrary` folder and install the npm package to be locally available for your computer by doing:
 
 ```
-$ npm install
+$ yarn install
 ```
 
 After this is done you can go to your main react app folder (which you created by doing `react-native init MyApp`)
 
 - add your newly created module as a dependency in your package.json
-- run `npm install` to bring it along from your local npm repository.
+- run `yarn install` to bring it along from your local npm repository.
 
 After this, you will be able to continue to [Native Modules (iOS)](native-modules-ios) or [Native Modules (Android)](native-modules-android) to add in some code. Make sure to read the README.md within your `MyLibrary` Directory for platform-specific instructions on how to include the project.
diff --git a/website/versioned_docs/version-0.5/navigation.md b/website/versioned_docs/version-0.5/navigation.md
index 841f1949568..a752c40b0cb 100644
--- a/website/versioned_docs/version-0.5/navigation.md
+++ b/website/versioned_docs/version-0.5/navigation.md
@@ -20,6 +20,14 @@ The first step is to install in your project:
 npm install --save react-navigation
 ```
 
+The second step is to install react-native-gesture-handler
+
+```
+yarn add react-native-gesture-handler
+# or with npm
+# npm install --save react-native-gesture-handler
+```
+
 Then you can quickly create an app with a home screen and a profile screen:
 
 ```jsx
diff --git a/website/versioned_docs/version-0.5/network.md b/website/versioned_docs/version-0.5/network.md
index 9eb2f3b7e7d..075da1e6e92 100644
--- a/website/versioned_docs/version-0.5/network.md
+++ b/website/versioned_docs/version-0.5/network.md
@@ -127,11 +127,11 @@ export default class FetchExample extends React.Component {
 }
 ```
 
-> By default, iOS will block any request that's not encrypted using SSL. If you need to fetch from a cleartext URL (one that begins with `http`) you will first need to [add an App Transport Security exception](integration-with-existing-apps.md#test-your-integration). If you know ahead of time what domains you will need access to, it is more secure to add exceptions just for those domains; if the domains are not known until runtime you can [disable ATS completely](integration-with-existing-apps.md#app-transport-security). Note however that from January 2017, [Apple's App Store review will require reasonable justification for disabling ATS](https://forums.developer.apple.com/thread/48979). See [Apple's documentation](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW33) for more information.
+> By default, iOS will block any request that's not encrypted using [SSL](https://hosting.review/web-hosting-glossary/#12). If you need to fetch from a cleartext URL (one that begins with `http`) you will first need to [add an App Transport Security exception](integration-with-existing-apps.md#test-your-integration). If you know ahead of time what domains you will need access to, it is more secure to add exceptions just for those domains; if the domains are not known until runtime you can [disable ATS completely](integration-with-existing-apps.md#app-transport-security). Note however that from January 2017, [Apple's App Store review will require reasonable justification for disabling ATS](https://forums.developer.apple.com/thread/48979). See [Apple's documentation](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW33) for more information.
 
 ### Using Other Networking Libraries
 
-The [XMLHttpRequest API](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest) is built in to React Native. This means that you can use third party libraries such as [frisbee](https://github.com/niftylettuce/frisbee) or [axios](https://github.com/mzabriskie/axios) that depend on it, or you can use the XMLHttpRequest API directly if you prefer.
+The [XMLHttpRequest API](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest) is built into React Native. This means that you can use third party libraries such as [frisbee](https://github.com/niftylettuce/frisbee) or [axios](https://github.com/mzabriskie/axios) that depend on it, or you can use the XMLHttpRequest API directly if you prefer.
 
 ```jsx
 var request = new XMLHttpRequest();
diff --git a/website/versioned_docs/version-0.5/performance.md b/website/versioned_docs/version-0.5/performance.md
index 11d6000b3b0..ad287b997d2 100644
--- a/website/versioned_docs/version-0.5/performance.md
+++ b/website/versioned_docs/version-0.5/performance.md
@@ -218,7 +218,7 @@ If you identified a JS problem, look for clues in the specific JS that you're ex
 
 ![Too much JS](/react-native/docs/assets/SystraceBadJS2.png)
 
-This doesn't seem right. Why is it being called so often? Are they actually different events? The answers to these questions will probably depend on your product code. And many times, you'll want to look into [shouldComponentUpdate](https://facebook.github.io/react/component-specs.md#updating-shouldcomponentupdate).
+This doesn't seem right. Why is it being called so often? Are they actually different events? The answers to these questions will probably depend on your product code. And many times, you'll want to look into [shouldComponentUpdate](https://reactjs.org/docs/react-component.html#shouldcomponentupdate).
 
 #### Resolving native UI Issues
 
@@ -240,7 +240,7 @@ To mitigate this, you should:
 - investigate using `renderToHardwareTextureAndroid` for complex, static content that is being animated/transformed (e.g. the `Navigator` slide/alpha animations)
 - make sure that you are **not** using `needsOffscreenAlphaCompositing`, which is disabled by default, as it greatly increases the per-frame load on the GPU in most cases.
 
-If these don't help and you want to dig deeper into what the GPU is actually doing, you can check out [Tracer for OpenGL ES](http://developer.android.com/tools/help/gltracer.html).
+If these don't help and you want to dig deeper into what the GPU is actually doing, you can check out [Tracer for OpenGL ES](http://www.androiddocs.com/tools/help/gltracer.html).
 
 ##### Creating new views on the UI thread
 
@@ -347,52 +347,12 @@ project.ext.react = [
 ]
 ```
 
+> **_Note_**: If you are using [Hermes JS Engine](https://github.com/facebook/hermes), you do not need RAM bundles. When loading the bytecode, `mmap` ensures that the entire file is not loaded.
+
 ### Configure Preloading and Inline Requires
 
 Now that we have a RAM bundle, there is overhead for calling `require`. `require` now needs to send a message over the bridge when it encounters a module it has not loaded yet. This will impact startup the most, because that is where the largest number of require calls are likely to take place while the app loads the initial module. Luckily we can configure a portion of the modules to be preloaded. In order to do this, you will need to implement some form of inline require.
 
-### Adding a packager config file
-
-Create a folder in your project called packager, and create a single file named config.js. Add the following:
-
-```
-const config = {
-  transformer: {
-    getTransformOptions: () => {
-      return {
-        transform: { inlineRequires: true },
-      };
-    },
-  },
-};
-
-module.exports = config;
-```
-
-In Xcode, in the build phase, include `export BUNDLE_CONFIG="packager/config.js"`.
-
-```
-export BUNDLE_COMMAND="ram-bundle"
-export BUNDLE_CONFIG="packager/config.js"
-export NODE_BINARY=node
-../node_modules/react-native/scripts/react-native-xcode.sh
-```
-
-Edit your android/app/build.gradle file to include `bundleConfig: "packager/config.js",`.
-
-```
-project.ext.react = [
-  bundleCommand: "ram-bundle",
-  bundleConfig: "packager/config.js"
-]
-```
-
-Finally, you can update "start" under "scripts" on your package.json to use the config:
-
-`"start": "yarn react-native start --config packager/config.js",`
-
-Start your package server with `npm start`. Note that when the dev packager is automatically launched via xcode and `react-native run-android`, etc, it does not use `npm start`, so it won't use the config.
-
 ### Investigating the Loaded Modules
 
 In your root file (index.(ios|android).js) you can add the following after the initial imports:
@@ -429,14 +389,14 @@ require.Systrace.beginEvent = (message) => {
 }
 ```
 
-Every app is different, but it may make sense to only load the modules you need for the very first screen. When you are satisified, put the output of the loadedModuleNames into a file named `packager/modulePaths.js`.
+Every app is different, but it may make sense to only load the modules you need for the very first screen. When you are satisfied, put the output of the loadedModuleNames into a file named `packager/modulePaths.js`.
 
-### Updating the config.js
+### Updating the metro.config.js
 
-Returning to packager/config.js we should update it to use our newly generated modulePaths.js file.
+We now need to update `metro.config.js` in the root of the project to use our newly generated `modulePaths.js` file:
 
 ```
-const modulePaths = require('./modulePaths');
+const modulePaths = require('./packager/modulePaths');
 const resolve = require('path').resolve;
 const fs = require('fs');
 
diff --git a/website/versioned_docs/version-0.5/props.md b/website/versioned_docs/version-0.5/props.md
index d02ef171f38..771f1b7c692 100644
--- a/website/versioned_docs/version-0.5/props.md
+++ b/website/versioned_docs/version-0.5/props.md
@@ -4,13 +4,13 @@ title: Props
 original_id: props
 ---
 
-Most components can be customized when they are created, with different parameters. These creation parameters are called `props`.
+Most components can be customized when they are created, with different parameters. These creation parameters are called `props`, short for properties.
 
 For example, one basic React Native component is the `Image`. When you create an image, you can use a prop named `source` to control what image it shows.
 
-```SnackPlayer
+```SnackPlayer name=Props
 import React, { Component } from 'react';
-import { AppRegistry, Image } from 'react-native';
+import { Image } from 'react-native';
 
 export default class Bananas extends Component {
   render() {
@@ -22,18 +22,15 @@ export default class Bananas extends Component {
     );
   }
 }
-
-// skip this line if using Create React Native App
-AppRegistry.registerComponent('AwesomeProject', () => Bananas);
 ```
 
 Notice the braces surrounding `{pic}` - these embed the variable `pic` into JSX. You can put any JavaScript expression inside braces in JSX.
 
 Your own components can also use `props`. This lets you make a single component that is used in many different places in your app, with slightly different properties in each place. Just refer to `this.props` in your `render` function. Here's an example:
 
-```SnackPlayer
+```SnackPlayer name=Props
 import React, { Component } from 'react';
-import { AppRegistry, Text, View } from 'react-native';
+import { Text, View } from 'react-native';
 
 class Greeting extends Component {
   render() {
@@ -56,9 +53,6 @@ export default class LotsOfGreetings extends Component {
     );
   }
 }
-
-// skip this line if using Create React Native App
-AppRegistry.registerComponent('AwesomeProject', () => LotsOfGreetings);
 ```
 
 Using `name` as a prop lets us customize the `Greeting` component, so we can reuse that component for each of our greetings. This example also uses the `Greeting` component in JSX, just like the built-in components. The power to do this is what makes React so cool - if you find yourself wishing that you had a different set of UI primitives to work with, you just invent new ones.
diff --git a/website/versioned_docs/version-0.5/removing-default-permissions.md b/website/versioned_docs/version-0.5/removing-default-permissions.md
index 0beb420e2de..2d7cffc247e 100644
--- a/website/versioned_docs/version-0.5/removing-default-permissions.md
+++ b/website/versioned_docs/version-0.5/removing-default-permissions.md
@@ -52,19 +52,4 @@ The default permissions that get added are:
    </manifest>
    ```
 
-4. Now let's remove `SYSTEM_ALERT_WINDOW` from the production APK only.
-5. Go to the `android/app/src/` directory. Create a new directory inside this directory, called `release`. (path: `android/app/src/release/`)
-6. Inside this `android/app/src/release/` directory create a `AndroidManifest.xml` file. (path: `android/app/src/release/AndroidManifest.xml`)
-7. Inside this file paste the following contents. Note, make sure to update your package identifier from "com.myapp" to what yours is.
-
-   ```diff
-   <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-       package="com.myapp"
-       xmlns:tools="http://schemas.android.com/tools">
-
-       <uses-permission tools:node="remove" android:name="android.permission.SYSTEM_ALERT_WINDOW" />
-
-   </manifest>
-   ```
-
-That's it. We did not remove the `INTERNET` permission as pretty much all apps use it. Now whenever you create a production APK all these 4 permissions will be removed. When you create a debug APK (`react-native run-android`) it will install the APK with only the three permissions removed, and `SYSTEM_ALERT_WINDOW` will remain.
+That's it. We did not remove the `INTERNET` permission as pretty much all apps use it. Now whenever you create a production APK, these 3 permissions will be removed. When you create a debug APK (`react-native run-android`) it will install the APK with these permissions added.
diff --git a/website/versioned_docs/version-0.5/running-on-simulator-ios.md b/website/versioned_docs/version-0.5/running-on-simulator-ios.md
index 13911ea73e1..6bb53cdc65d 100644
--- a/website/versioned_docs/version-0.5/running-on-simulator-ios.md
+++ b/website/versioned_docs/version-0.5/running-on-simulator-ios.md
@@ -10,6 +10,6 @@ Once you have your React Native project initialized, you can run `react-native r
 
 ## Specifying a device
 
-You can specify the device the simulator should run with the `--simulator` flag, followed by the device name as a string. The default is `"iPhone X"`. If you wish to run your app on an iPhone 4s, just run `react-native run-ios --simulator="iPhone 4s"`.
+You can specify the device the simulator should run with the `--simulator` flag, followed by the device name as a string. The default is `"iPhone X"`. If you wish to run your app on an iPhone 5s, just run `react-native run-ios --simulator="iPhone 5s"`.
 
 The device names correspond to the list of devices available in Xcode. You can check your available devices by running `xcrun simctl list devices` from the console.
diff --git a/website/versioned_docs/version-0.5/signed-apk-android.md b/website/versioned_docs/version-0.5/signed-apk-android.md
index e3392000bfd..2bb3e48427f 100644
--- a/website/versioned_docs/version-0.5/signed-apk-android.md
+++ b/website/versioned_docs/version-0.5/signed-apk-android.md
@@ -1,58 +1,54 @@
 ---
 id: version-0.5-signed-apk-android
-title: Generating Signed APK
+title: Publishing to Google Play Store
 original_id: signed-apk-android
 ---
 
-Android requires that all apps be digitally signed with a certificate before they can be installed, so to distribute your Android application via [Google Play store](https://play.google.com/store), you'll need to generate a signed release APK. The [Signing Your Applications](https://developer.android.com/tools/publishing/app-signing.html) page on Android Developers documentation describes the topic in detail. This guide covers the process in brief, as well as lists the steps required to package the JavaScript bundle.
+Android requires that all apps be digitally signed with a certificate before they can be installed. In order to distribute your Android application via [Google Play store](https://play.google.com/store) it needs to be signed with a release key that then needs to be used for all future updates. Since 2017 it is possible for Google Play to manage signing releases automatically thanks to [App Signing by Google Play](https://developer.android.com/studio/publish/app-signing#app-signing-google-play) functionality. However, before your application binary is uploaded to Google Play it needs to be signed with an upload key. The [Signing Your Applications](https://developer.android.com/tools/publishing/app-signing.html) page on Android Developers documentation describes the topic in detail. This guide covers the process in brief, as well as lists the steps required to package the JavaScript bundle.
 
-### Generating a signing key
+### Generating an upload key
 
 You can generate a private signing key using `keytool`. On Windows `keytool` must be run from `C:\Program Files\Java\jdkx.x.x_x\bin`.
 
-    $ keytool -genkeypair -v -keystore my-release-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000
+    $ keytool -genkeypair -v -keystore my-upload-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000
 
-This command prompts you for passwords for the keystore and key and for the Distinguished Name fields for your key. It then generates the keystore as a file called `my-release-key.keystore`.
+This command prompts you for passwords for the keystore and key and for the Distinguished Name fields for your key. It then generates the keystore as a file called `my-upload-key.keystore`.
 
 The keystore contains a single key, valid for 10000 days. The alias is a name that you will use later when signing your app, so remember to take note of the alias.
 
-On Mac, if you're not sure where your jdk bin folder is, then perform the following command to find it:
+On Mac, if you're not sure where your JDK bin folder is, then perform the following command to find it:
 
     $ /usr/libexec/java_home
 
-It will output the directory of the jdk, which will look something like this:
+It will output the directory of the JDK, which will look something like this:
 
     /Library/Java/JavaVirtualMachines/jdkX.X.X_XXX.jdk/Contents/Home
 
 Navigate to that directory by using the command `$ cd /your/jdk/path` and use the keytool command with sudo permission as shown below.
 
-    $ sudo keytool -genkey -v -keystore my-release-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000
+    $ sudo keytool -genkey -v -keystore my-upload-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000
 
-_Note: Remember to keep your keystore file private and never commit it to version control._
+_Note: Remember to keep the keystore file private. In case you've lost upload key or it's been compromised you should [follow these instructions](https://support.google.com/googleplay/android-developer/answer/7384423#reset)._
 
-### Setting up gradle variables
+### Setting up Gradle variables
 
-1. Place the `my-release-key.keystore` file under the `android/app` directory in your project folder.
+1. Place the `my-upload-key.keystore` file under the `android/app` directory in your project folder.
 2. Edit the file `~/.gradle/gradle.properties` or `android/gradle.properties`, and add the following (replace `*****` with the correct keystore password, alias and key password),
 
 ```
-MYAPP_RELEASE_STORE_FILE=my-release-key.keystore
-MYAPP_RELEASE_KEY_ALIAS=my-key-alias
-MYAPP_RELEASE_STORE_PASSWORD=*****
-MYAPP_RELEASE_KEY_PASSWORD=*****
+MYAPP_UPLOAD_STORE_FILE=my-upload-key.keystore
+MYAPP_UPLOAD_KEY_ALIAS=my-key-alias
+MYAPP_UPLOAD_STORE_PASSWORD=*****
+MYAPP_UPLOAD_KEY_PASSWORD=*****
 ```
 
-These are going to be global gradle variables, which we can later use in our gradle config to sign our app.
-
-> **Note about saving the keystore:**
-
-> Once you publish the app on the Play Store, you will need to republish your app under a different package name (losing all downloads and ratings) if you want to change the signing key at any point. So backup your keystore and don't forget the passwords.
+These are going to be global Gradle variables, which we can later use in our Gradle config to sign our app.
 
 _Note about security: If you are not keen on storing your passwords in plaintext, and you are running OSX, you can also [store your credentials in the Keychain Access app](https://pilloxa.gitlab.io/posts/safer-passwords-in-gradle/). Then you can skip the two last rows in `~/.gradle/gradle.properties`._
 
-### Adding signing config to your app's gradle config
+### Adding signing config to your app's Gradle config
 
-Edit the file `android/app/build.gradle` in your project folder, and add the signing config,
+The last configuration step that needs to be done is to setup release builds to be signed using upload key. Edit the file `android/app/build.gradle` in your project folder, and add the signing config,
 
 ```gradle
 ...
@@ -61,11 +57,11 @@ android {
     defaultConfig { ... }
     signingConfigs {
         release {
-            if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
-                storeFile file(MYAPP_RELEASE_STORE_FILE)
-                storePassword MYAPP_RELEASE_STORE_PASSWORD
-                keyAlias MYAPP_RELEASE_KEY_ALIAS
-                keyPassword MYAPP_RELEASE_KEY_PASSWORD
+            if (project.hasProperty('MYAPP_UPLOAD_STORE_FILE')) {
+                storeFile file(MYAPP_UPLOAD_STORE_FILE)
+                storePassword MYAPP_UPLOAD_STORE_PASSWORD
+                keyAlias MYAPP_UPLOAD_KEY_ALIAS
+                keyPassword MYAPP_UPLOAD_KEY_PASSWORD
             }
         }
     }
@@ -85,14 +81,16 @@ Simply run the following in a terminal:
 
 ```sh
 $ cd android
-$ ./gradlew assembleRelease
+$ ./gradlew bundleRelease
 ```
 
-Gradle's `assembleRelease` will bundle all the JavaScript needed to run your app into the APK. If you need to change the way the JavaScript bundle and/or drawable resources are bundled (e.g. if you changed the default file/folder names or the general structure of the project), have a look at `android/app/build.gradle` to see how you can update it to reflect these changes.
+Gradle's `bundleRelease` will bundle all the JavaScript needed to run your app into the AAB ([Android App Bundle](https://developer.android.com/guide/app-bundle)). If you need to change the way the JavaScript bundle and/or drawable resources are bundled (e.g. if you changed the default file/folder names or the general structure of the project), have a look at `android/app/build.gradle` to see how you can update it to reflect these changes.
+
+> Note: Make sure gradle.properties does not include _org.gradle.configureondemand=true_ as that will make the release build skip bundling JS and assets into the app binary.
 
-> Note: Make sure gradle.properties does not include _org.gradle.configureondemand=true_ as that will make the release build skip bundling JS and assets into the APK.
+The generated AAB can be found under `android/app/build/outputs/bundle/release/app.aab`, and is ready to be uploaded to Google Play.
 
-The generated APK can be found under `android/app/build/outputs/apk/release/app-release.apk`, and is ready to be distributed.
+_Note: In order for Google Play to accept AAB format the App Signing by Google Play needs to be configured for your application on the Google Play Console. If you are updating an existing app that doesn't use App Signing by Google Play, please check our [migration section](#migrating-old-android-react-native-apps-to-use-app-signing-by-google-play) to learn how to perform that configuration change._
 
 ### Testing the release build of your app
 
@@ -106,7 +104,7 @@ Note that `--variant=release` is only available if you've set up signing as desc
 
 You can kill any running packager instances, since all your framework and JavaScript code is bundled in the APK's assets.
 
-### Split APKs by ABI to reduce file size
+### Publishing to other stores
 
 By default, the generated APK has the native code for both x86 and ARMv7a CPU architectures. This makes it easier to share APKs that run on almost all Android devices. However, this has the downside that there will be some unused native code on any device, leading to unnecessarily bigger APKs.
 
@@ -120,7 +118,7 @@ You can create an APK for each CPU by changing the following line in android/app
 + def enableSeparateBuildPerCPUArchitecture = true
 ```
 
-Upload both these files to markets which support device targetting, such as [Google Play](https://developer.android.com/google/play/publishing/multiple-apks.html) and [Amazon AppStore](https://developer.amazon.com/docs/app-submission/getting-started-with-device-targeting.html), and the users will automatically get the appropriate APK. If you want to upload to other markets, such as [APKFiles](https://www.apkfiles.com/), which do not support multiple APKs for a single app, change the following line as well to create the default universal APK with binaries for both CPUs.
+Upload both these files to markets which support device targeting, such as [Google Play](https://developer.android.com/google/play/publishing/multiple-apks.html) and [Amazon AppStore](https://developer.amazon.com/docs/app-submission/device-filtering-and-compatibility.html), and the users will automatically get the appropriate APK. If you want to upload to other markets, such as [APKFiles](https://www.apkfiles.com/), which do not support multiple APKs for a single app, change the following line as well to create the default universal APK with binaries for both CPUs.
 
 ```diff
 - universalApk false  // If true, also generate a universal APK
@@ -141,3 +139,7 @@ To enable Proguard, edit `android/app/build.gradle`:
  */
 def enableProguardInReleaseBuilds = true
 ```
+
+### Migrating old Android React Native apps to use App Signing by Google Play
+
+If you are migrating from previous version of React Native chances are your app does not use App Signing by Google Play feature. We recommend you enable that in order to take advantage from things like automatic app splitting. In order to migrate from the old way of signing you need to start by [generating new upload key](#generating-an-upload-key) and then replacing release signing config in `android/app/build.gradle` to use the upload key instead of the release one (see section about [adding signing config to gradle](#adding-signing-config-to-your-app-s-gradle-config)). Once that's done you should follow the [instructions from Google Play Help website](https://support.google.com/googleplay/android-developer/answer/7384423) in order to send your original release key to Google Play.
diff --git a/website/versioned_docs/version-0.5/state.md b/website/versioned_docs/version-0.5/state.md
index 2dda5ac7e31..18873cb3de4 100644
--- a/website/versioned_docs/version-0.5/state.md
+++ b/website/versioned_docs/version-0.5/state.md
@@ -10,15 +10,13 @@ In general, you should initialize `state` in the constructor, and then call `set
 
 For example, let's say we want to make text that blinks all the time. The text itself gets set once when the blinking component gets created, so the text itself is a `prop`. The "whether the text is currently on or off" changes over time, so that should be kept in `state`.
 
-```SnackPlayer
+```SnackPlayer name=State
 import React, { Component } from 'react';
-import { AppRegistry, Text, View } from 'react-native';
+import { Text, View } from 'react-native';
 
 class Blink extends Component {
-  constructor(props) {
-    super(props);
-    this.state = { isShowingText: true };
 
+  componentDidMount(){
     // Toggle the state every second
     setInterval(() => (
       this.setState(previousState => (
@@ -27,6 +25,9 @@ class Blink extends Component {
     ), 1000);
   }
 
+  //state object
+  state = { isShowingText: true };
+
   render() {
     if (!this.state.isShowingText) {
       return null;
@@ -50,9 +51,6 @@ export default class BlinkApp extends Component {
     );
   }
 }
-
-// skip this line if using Create React Native App
-AppRegistry.registerComponent('AwesomeProject', () => BlinkApp);
 ```
 
 In a real application, you probably won't be setting state with a timer. You might set state when you have new data from the server, or from user input. You can also use a state container like [Redux](https://redux.js.org/) or [Mobx](https://mobx.js.org/) to control your data flow. In that case you would use Redux or Mobx to modify your state rather than calling `setState` directly.
diff --git a/website/versioned_docs/version-0.5/style.md b/website/versioned_docs/version-0.5/style.md
index cdf59c1d266..6eeb6121647 100644
--- a/website/versioned_docs/version-0.5/style.md
+++ b/website/versioned_docs/version-0.5/style.md
@@ -4,15 +4,15 @@ title: Style
 original_id: style
 ---
 
-With React Native, you don't use a special language or syntax for defining styles. You just style your application using JavaScript. All of the core components accept a prop named `style`. The style names and [values](colors.md) usually match how CSS works on the web, except names are written using camel casing, e.g `backgroundColor` rather than `background-color`.
+With React Native, you don't use a special language or syntax for defining styles. You just style your application using JavaScript. All of the core components accept a prop named `style`. The style names and [values](colors.md) usually match how CSS works on the web, except names are written using camel casing, e.g. `backgroundColor` rather than `background-color`.
 
 The `style` prop can be a plain old JavaScript object. That's the simplest and what we usually use for example code. You can also pass an array of styles - the last style in the array has precedence, so you can use this to inherit styles.
 
 As a component grows in complexity, it is often cleaner to use `StyleSheet.create` to define several styles in one place. Here's an example:
 
-```SnackPlayer
+```SnackPlayer name=Style
 import React, { Component } from 'react';
-import { AppRegistry, StyleSheet, Text, View } from 'react-native';
+import { StyleSheet, Text, View } from 'react-native';
 
 const styles = StyleSheet.create({
   bigBlue: {
@@ -37,9 +37,6 @@ export default class LotsOfStyles extends Component {
     );
   }
 }
-
-// skip this line if using Create React Native App
-AppRegistry.registerComponent('AwesomeProject', () => LotsOfStyles);
 ```
 
 One common pattern is to make your component accept a `style` prop which in turn is used to style subcomponents. You can use this to make styles "cascade" the way they do in CSS.
diff --git a/website/versioned_docs/version-0.5/timers.md b/website/versioned_docs/version-0.5/timers.md
index 4061a493bc7..7f2d5832a75 100644
--- a/website/versioned_docs/version-0.5/timers.md
+++ b/website/versioned_docs/version-0.5/timers.md
@@ -48,26 +48,3 @@ var handle = InteractionManager.createInteractionHandle();
 InteractionManager.clearInteractionHandle(handle);
 // queued tasks run if all handles were cleared
 ```
-
-## TimerMixin
-
-We found out that the primary cause of fatals in apps created with React Native was due to timers firing after a component was unmounted. To solve this recurring issue, we introduced `TimerMixin`. If you include `TimerMixin`, then you can replace your calls to `setTimeout(fn, 500)` with `this.setTimeout(fn, 500)` (just prepend `this.`) and everything will be properly cleaned up for you when the component unmounts.
-
-This library does not ship with React Native - in order to use it on your project, you will need to install it with `npm i react-timer-mixin --save` from your project directory.
-
-```jsx
-import TimerMixin from 'react-timer-mixin';
-
-var Component = createReactClass({
-  mixins: [TimerMixin],
-  componentDidMount: function() {
-    this.setTimeout(() => {
-      console.log('I do not leak!');
-    }, 500);
-  },
-});
-```
-
-This will eliminate a lot of hard work tracking down bugs, such as crashes caused by timeouts firing after a component has been unmounted.
-
-Keep in mind that if you use ES6 classes for your React components [there is no built-in API for mixins](https://facebook.github.io/react/blog/2015/01/27/react-v0.13.0-beta-1.html#mixins). To use `TimerMixin` with ES6 classes, we recommend [react-mixin](https://github.com/brigand/react-mixin).
diff --git a/website/versioned_docs/version-0.5/troubleshooting.md b/website/versioned_docs/version-0.5/troubleshooting.md
index 231608807ca..5cdf3551073 100644
--- a/website/versioned_docs/version-0.5/troubleshooting.md
+++ b/website/versioned_docs/version-0.5/troubleshooting.md
@@ -94,7 +94,7 @@ Try [downgrading your Gradle version to 1.2.3](https://github.com/facebook/react
 
 ## react-native init hangs
 
-If you run into issues where running `react-native init` hangs in your system, try running it again in verbose mode and refering to [#2797](https://github.com/facebook/react-native/issues/2797) for common causes:
+If you run into issues where running `react-native init` hangs in your system, try running it again in verbose mode and referring to [#2797](https://github.com/facebook/react-native/issues/2797) for common causes:
 
 ```
 react-native init --verbose
diff --git a/website/versioned_docs/version-0.5/tutorial.md b/website/versioned_docs/version-0.5/tutorial.md
index c839676ca39..baae3303251 100644
--- a/website/versioned_docs/version-0.5/tutorial.md
+++ b/website/versioned_docs/version-0.5/tutorial.md
@@ -12,7 +12,7 @@ Let's do this thing.
 
 In accordance with the ancient traditions of our people, we must first build an app that does nothing except say "Hello, world!". Here it is:
 
-```SnackPlayer
+```SnackPlayer name=Hello%20World
 import React, { Component } from 'react';
 import { Text, View } from 'react-native';
 
diff --git a/website/versioned_docs/version-0.5/upgrading.md b/website/versioned_docs/version-0.5/upgrading.md
index 607fb1a2388..ba8de09d1c4 100644
--- a/website/versioned_docs/version-0.5/upgrading.md
+++ b/website/versioned_docs/version-0.5/upgrading.md
@@ -30,10 +30,10 @@ Run the following command to start the process of upgrading to the latest versio
 react-native upgrade
 ```
 
-You may specify a React Native version by passing an argument, e.g. to upgrade to `0.59.0-rc.0` run:
+You may specify a React Native version by passing an argument, e.g. to upgrade to `0.61.0-rc.0` run:
 
 ```sh
-react-native upgrade 0.59.0-rc.0
+react-native upgrade 0.61.0-rc.0
 ```
 
 The project is upgraded using `git apply` with 3-way merge, it may happen that you'll need to resolve a few conflicts after it's finished.
diff --git a/website/versioned_docs/version-0.5/using-a-scrollview.md b/website/versioned_docs/version-0.5/using-a-scrollview.md
index 72a358c7775..b65913ed1ac 100644
--- a/website/versioned_docs/version-0.5/using-a-scrollview.md
+++ b/website/versioned_docs/version-0.5/using-a-scrollview.md
@@ -8,9 +8,9 @@ The [ScrollView](scrollview.md) is a generic scrolling container that can host m
 
 This example creates a vertical `ScrollView` with both images and text mixed together.
 
-```SnackPlayer
+```SnackPlayer name=Using%20ScrollView
 import React, { Component } from 'react';
-import { AppRegistry, ScrollView, Image, Text } from 'react-native';
+import { ScrollView, Image, Text } from 'react-native';
 
 export default class IScrolledDownAndWhatHappenedNextShockedMe extends Component {
   render() {
@@ -51,14 +51,9 @@ export default class IScrolledDownAndWhatHappenedNextShockedMe extends Component
     );
   }
 }
-
-// skip these lines if using Create React Native App
-AppRegistry.registerComponent(
-  'AwesomeProject',
-  () => IScrolledDownAndWhatHappenedNextShockedMe);
 ```
 
-ScrollViews can be configured to allow paging through views using swiping gestures by using the `pagingEnabled` props. Swiping horizontally between views can also be implemented on Android using the [ViewPagerAndroid](viewpagerandroid.md) component.
+ScrollViews can be configured to allow paging through views using swiping gestures by using the `pagingEnabled` props. Swiping horizontally between views can also be implemented on Android using the [ViewPager](https://github.com/react-native-community/react-native-viewpager) component.
 
 On iOS a ScrollView with a single item can be used to allow the user to zoom content. Set up the `maximumZoomScale` and `minimumZoomScale` props and your user will be able to use pinch and expand gestures to zoom in and out.
 
diff --git a/website/versioned_docs/version-0.59/images.md b/website/versioned_docs/version-0.59/images.md
deleted file mode 100644
index 1a60ff8eda5..00000000000
--- a/website/versioned_docs/version-0.59/images.md
+++ /dev/null
@@ -1,223 +0,0 @@
----
-id: version-0.59-images
-title: Images
-original_id: images
----
-
-## Static Image Resources
-
-React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
-
-```jsx
-<Image source={require('./my-icon.png')} />
-```
-
-The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for `my-icon.png` in the same folder as the component that requires it. Also, if you have `my-icon.ios.png` and `my-icon.android.png`, the packager will pick the correct file for the platform.
-
-You can also use the `@2x` and `@3x` suffixes to provide images for different screen densities. If you have the following file structure:
-
-```
-.
-├── button.js
-└── img
-    ├── check.png
-    ├── check@2x.png
-    └── check@3x.png
-```
-
-...and `button.js` code contains:
-
-```jsx
-<Image source={require('./img/check.png')} />
-```
-
-...the packager will bundle and serve the image corresponding to device's screen density. For example, `check@2x.png`, will be used on an iPhone 7, while`check@3x.png` will be used on an iPhone 7 Plus or a Nexus 5. If there is no image matching the screen density, the closest best option will be selected.
-
-On Windows, you might need to restart the packager if you add new images to your project.
-
-Here are some benefits that you get:
-
-1. Same system on iOS and Android.
-2. Images live in the same folder as your JavaScript code. Components are self-contained.
-3. No global namespace, i.e. you don't have to worry about name collisions.
-4. Only the images that are actually used will be packaged into your app.
-5. Adding and changing images doesn't require app recompilation, just refresh the simulator as you normally do.
-6. The packager knows the image dimensions, no need to duplicate it in the code.
-7. Images can be distributed via [npm](https://www.npmjs.com/) packages.
-
-In order for this to work, the image name in `require` has to be known statically.
-
-```jsx
-// GOOD
-<Image source={require('./my-icon.png')} />;
-
-// BAD
-var icon = this.props.active ? 'my-icon-active' : 'my-icon-inactive';
-<Image source={require('./' + icon + '.png')} />;
-
-// GOOD
-var icon = this.props.active
-  ? require('./my-icon-active.png')
-  : require('./my-icon-inactive.png');
-<Image source={icon} />;
-```
-
-Note that image sources required this way include size (width, height) info for the Image. If you need to scale the image dynamically (i.e. via flex), you may need to manually set `{ width: undefined, height: undefined }` on the style attribute.
-
-## Static Non-Image Resources
-
-The `require` syntax described above can be used to statically include audio, video or document files in your project as well. Most common file types are supported including `.mp3`, `.wav`, `.mp4`, `.mov`, `.html` and `.pdf`. See [packager defaults](https://github.com/facebook/metro/blob/master/packages/metro-config/src/defaults/defaults.js#L14-L44) for the full list.
-
-You can add support for other types by adding an [`assetExts` resolver option](https://facebook.github.io/metro/docs/en/configuration#assetexts) in your [Metro configuration](https://facebook.github.io/metro/docs/en/configuration).
-
-A caveat is that videos must use absolute positioning instead of `flexGrow`, since size info is not currently passed for non-image assets. This limitation doesn't occur for videos that are linked directly into Xcode or the Assets folder for Android.
-
-## Images From Hybrid App's Resources
-
-If you are building a hybrid app (some UIs in React Native, some UIs in platform code) you can still use images that are already bundled into the app.
-
-For images included via Xcode asset catalogs or in the Android drawable folder, use the image name without the extension:
-
-```jsx
-<Image source={{uri: 'app_icon'}} style={{width: 40, height: 40}} />
-```
-
-For images in the Android assets folder, use the `asset:/` scheme:
-
-```jsx
-<Image source={{uri: 'asset:/app_icon.png'}} style={{width: 40, height: 40}} />
-```
-
-These approaches provide no safety checks. It's up to you to guarantee that those images are available in the application. Also you have to specify image dimensions manually.
-
-## Network Images
-
-Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](running-on-device.md#app-transport-security) requirements on iOS.
-
-```jsx
-// GOOD
-<Image source={{uri: 'https://facebook.github.io/react/logo-og.png'}}
-       style={{width: 400, height: 400}} />
-
-// BAD
-<Image source={{uri: 'https://facebook.github.io/react/logo-og.png'}} />
-```
-
-### Network Requests for Images
-
-If you would like to set such things as the HTTP-Verb, Headers or a Body along with the image request, you may do this by defining these properties on the source object:
-
-```jsx
-<Image
-  source={{
-    uri: 'https://facebook.github.io/react/logo-og.png',
-    method: 'POST',
-    headers: {
-      Pragma: 'no-cache',
-    },
-    body: 'Your Body goes here',
-  }}
-  style={{width: 400, height: 400}}
-/>
-```
-
-## Uri Data Images
-
-Sometimes, you might be getting encoded image data from a REST API call. You can use the `'data:'` uri scheme to use these images. Same as for network resources, _you will need to manually specify the dimensions of your image_.
-
-> This is recommended for very small and dynamic images only, like icons in a list from a DB.
-
-```jsx
-// include at least width and height!
-<Image
-  style={{
-    width: 51,
-    height: 51,
-    resizeMode: 'contain',
-  }}
-  source={{
-    uri:
-      'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADMAAAAzCAYAAAA6oTAqAAAAEXRFWHRTb2Z0d2FyZQBwbmdjcnVzaEB1SfMAAABQSURBVGje7dSxCQBACARB+2/ab8BEeQNhFi6WSYzYLYudDQYGBgYGBgYGBgYGBgYGBgZmcvDqYGBgmhivGQYGBgYGBgYGBgYGBgYGBgbmQw+P/eMrC5UTVAAAAABJRU5ErkJggg==',
-  }}
-/>
-```
-
-### Cache Control (iOS Only)
-
-In some cases you might only want to display an image if it is already in the local cache, i.e. a low resolution placeholder until a higher resolution is available. In other cases you do not care if the image is outdated and are willing to display an outdated image to save bandwidth. The `cache` source property gives you control over how the network layer interacts with the cache.
-
-- `default`: Use the native platforms default strategy.
-- `reload`: The data for the URL will be loaded from the originating source. No existing cache data should be used to satisfy a URL load request.
-- `force-cache`: The existing cached data will be used to satisfy the request, regardless of its age or expiration date. If there is no existing data in the cache corresponding the request, the data is loaded from the originating source.
-- `only-if-cached`: The existing cache data will be used to satisfy a request, regardless of its age or expiration date. If there is no existing data in the cache corresponding to a URL load request, no attempt is made to load the data from the originating source, and the load is considered to have failed.
-
-```jsx
-<Image
-  source={{
-    uri: 'https://facebook.github.io/react/logo-og.png',
-    cache: 'only-if-cached',
-  }}
-  style={{width: 400, height: 400}}
-/>
-```
-
-## Local Filesystem Images
-
-See [CameraRoll](cameraroll.md) for an example of using local resources that are outside of `Images.xcassets`.
-
-### Best Camera Roll Image
-
-iOS saves multiple sizes for the same image in your Camera Roll, it is very important to pick the one that's as close as possible for performance reasons. You wouldn't want to use the full quality 3264x2448 image as source when displaying a 200x200 thumbnail. If there's an exact match, React Native will pick it, otherwise it's going to use the first one that's at least 50% bigger in order to avoid blur when resizing from a close size. All of this is done by default so you don't have to worry about writing the tedious (and error prone) code to do it yourself.
-
-## Why Not Automatically Size Everything?
-
-_In the browser_ if you don't give a size to an image, the browser is going to render a 0x0 element, download the image, and then render the image based with the correct size. The big issue with this behavior is that your UI is going to jump all around as images load, this makes for a very bad user experience.
-
-_In React Native_ this behavior is intentionally not implemented. It is more work for the developer to know the dimensions (or aspect ratio) of the remote image in advance, but we believe that it leads to a better user experience. Static images loaded from the app bundle via the `require('./my-icon.png')` syntax _can be automatically sized_ because their dimensions are available immediately at the time of mounting.
-
-For example, the result of `require('./my-icon.png')` might be:
-
-```jsx
-{"__packager_asset":true,"uri":"my-icon.png","width":591,"height":573}
-```
-
-## Source as an object
-
-In React Native, one interesting decision is that the `src` attribute is named `source` and doesn't take a string but an object with a `uri` attribute.
-
-```jsx
-<Image source={{uri: 'something.jpg'}} />
-```
-
-On the infrastructure side, the reason is that it allows us to attach metadata to this object. For example if you are using `require('./my-icon.png')`, then we add information about its actual location and size (don't rely on this fact, it might change in the future!). This is also future proofing, for example we may want to support sprites at some point, instead of outputting `{uri: ...}`, we can output `{uri: ..., crop: {left: 10, top: 50, width: 20, height: 40}}` and transparently support spriting on all the existing call sites.
-
-On the user side, this lets you annotate the object with useful attributes such as the dimension of the image in order to compute the size it's going to be displayed in. Feel free to use it as your data structure to store more information about your image.
-
-## Background Image via Nesting
-
-A common feature request from developers familiar with the web is `background-image`. To handle this use case, you can use the `<ImageBackground>` component, which has the same props as `<Image>`, and add whatever children to it you would like to layer on top of it.
-
-You might not want to use `<ImageBackground>` in some cases, since the implementation is very simple. Refer to `<ImageBackground>`'s [documentation](imagebackground.md) for more insight, and create your own custom component when needed.
-
-```jsx
-return (
-  <ImageBackground source={...} style={{width: '100%', height: '100%'}}>
-    <Text>Inside</Text>
-  </ImageBackground>
-);
-```
-
-Note that you must specify some width and height style attributes.
-
-## iOS Border Radius Styles
-
-Please note that the following corner specific, border radius style properties are currently ignored by iOS's image component:
-
-- `borderTopLeftRadius`
-- `borderTopRightRadius`
-- `borderBottomLeftRadius`
-- `borderBottomRightRadius`
-
-## Off-thread Decoding
-
-Image decoding can take more than a frame-worth of time. This is one of the major sources of frame drops on the web because decoding is done in the main thread. In React Native, image decoding is done in a different thread. In practice, you already need to handle the case when the image is not downloaded yet, so displaying the placeholder for a few more frames while it is decoding does not require any code change.
diff --git a/website/versioned_docs/version-0.60/accessibility.md b/website/versioned_docs/version-0.60/accessibility.md
deleted file mode 100644
index 8f809189741..00000000000
--- a/website/versioned_docs/version-0.60/accessibility.md
+++ /dev/null
@@ -1,306 +0,0 @@
----
-id: version-0.60-accessibility
-title: Accessibility
-original_id: accessibility
----
-
-## Native App Accessibility (iOS and Android)
-
-Both iOS and Android provide APIs for making apps accessible to people with disabilities. In addition, both platforms provide bundled assistive technologies, like the screen readers VoiceOver (iOS) and TalkBack (Android) for the visually impaired. Similarly, in React Native we have included APIs designed to provide developers with support for making apps more accessible. Take note, iOS and Android differ slightly in their approaches, and thus the React Native implementations may vary by platform.
-
-In addition to this documentation, you might find [this blog post](https://engineering.fb.com/ios/making-react-native-apps-accessible/) about React Native accessibility to be useful.
-
-## Making Apps Accessible
-
-### Accessibility properties
-
-#### accessible (iOS, Android)
-
-When `true`, indicates that the view is an accessibility element. When a view is an accessibility element, it groups its children into a single selectable component. By default, all touchable elements are accessible.
-
-On Android, `accessible={true}` property for a react-native View will be translated into native `focusable={true}`.
-
-```jsx
-<View accessible={true}>
-  <Text>text one</Text>
-  <Text>text two</Text>
-</View>
-```
-
-In the above example, we can't get accessibility focus separately on 'text one' and 'text two'. Instead we get focus on a parent view with 'accessible' property.
-
-#### accessibilityLabel (iOS, Android)
-
-When a view is marked as accessible, it is a good practice to set an accessibilityLabel on the view, so that people who use VoiceOver know what element they have selected. VoiceOver will read this string when a user selects the associated element.
-
-To use, set the `accessibilityLabel` property to a custom string on your View, Text or Touchable:
-
-```jsx
-<TouchableOpacity
-  accessible={true}
-  accessibilityLabel="Tap me!"
-  onPress={this._onPress}>
-  <View style={styles.button}>
-    <Text style={styles.buttonText}>Press me!</Text>
-  </View>
-</TouchableOpacity>
-```
-
-In the above example, the `accessibilityLabel` on the TouchableOpacity element would default to "Press me!". The label is constructed by concatenating all Text node children separated by spaces.
-
-#### accessibilityHint (iOS, Android)
-
-An accessibility hint helps users understand what will happen when they perform an action on the accessibility element when that result is not obvious from the accessibility label.
-
-To use, set the `accessibilityHint` property to a custom string on your View, Text or Touchable:
-
-```jsx
-<TouchableOpacity
-  accessible={true}
-  accessibilityLabel="Go back"
-  accessibilityHint="Navigates to the previous screen"
-  onPress={this._onPress}>
-  <View style={styles.button}>
-    <Text style={styles.buttonText}>Back</Text>
-  </View>
-</TouchableOpacity>
-```
-
-iOS In the above example, VoiceOver will read the hint after the label, if the user has hints enabled in the device's VoiceOver settings. Read more about guidelines for accessibilityHint in the [iOS Developer Docs](https://developer.apple.com/documentation/objectivec/nsobject/1615093-accessibilityhint)
-
-Android In the above example, Talkback will read the hint after the label. At this time, hints cannot be turned off on Android.
-
-#### accessibilityIgnoresInvertColors(iOS)
-
-Inverting screen colors is an Accessibility feature that makes the iPhone and iPad easier on the eyes for some people with a sensitivity to brightness, easier to distinguish for some people with color blindness, and easier to make out for some people with low vision. However, sometimes you have views such as photos that you don't want to be inverted. In this case, you can set this property to be false so that these specific views won't have their colors inverted.
-
-#### accessibilityRole (iOS, Android)
-
-`accessibilityRole` communicates the purpose of a component to the user of an assistive technology.
-
-`accessibilityRole` can be one of the following:
-
-- **none** Used when the element has no role.
-- **button** Used when the element should be treated as a button.
-- **link** Used when the element should be treated as a link.
-- **search** Used when the text field element should also be treated as a search field.
-- **image** Used when the element should be treated as an image. Can be combined with button or link, for example.
-- **keyboardkey** Used when the element acts as a keyboard key.
-- **text** Used when the element should be treated as static text that cannot change.
-- **adjustable** Used when an element can be "adjusted" (e.g. a slider).
-- **imagebutton** Used when the element should be treated as a button and is also an image.
-- **header** Used when an element acts as a header for a content section (e.g. the title of a navigation bar).
-- **summary** Used when an element can be used to provide a quick summary of current conditions in the app when the app first launches.
-- **alert** Used when an element contains important text to be presented to the user.
-- **checkbox** Used when an element represents a checkbox which can be checked, unchecked, or have mixed checked state.
-- **combobox** Used when an element represents a combo box, which allows the user to select among several choices.
-- **menu** Used when the component is a menu of choices.
-- **menubar** Used when a component is a container of multiple menus.
-- **menuitem** Used to represent an item within a menu.
-- **progressbar** Used to represent a component which indicates progress of a task.
-- **radio** Used to represent a radio button.
-- **radiogroup** Used to represent a group of radio buttons.
-- **scrollbar** Used to represent a scroll bar.
-- **spinbutton** Used to represent a button which opens a list of choices.
-- **switch** Used to represent a switch which can be turned on and off.
-- **tab** Used to represent a tab.
-- **tablist** Used to represent a list of tabs.
-- **timer** Used to represent a timer.
-- **toolbar** Used to represent a tool bar (a container of action buttons or components).
-
-#### accessibilityStates (iOS, Android)
-
-Describes the current state of a component to the user of an assistive technology.
-
-`accessibilityStates` is an array of values, and may include any of the following:
-
-- **selected** Used when the element is in a selected state. For example, a button is selected.
-- **disabled** Used when the element is disabled and cannot be interacted with.
-- **checked** Used to indicate that a checkable element is currently checked.
-- **unchecked** Used to indicate that a checkable element is not currently checked.
-- **busy** Used to indicate that an element is currently busy.
-- **expanded** Used to indicate that an expandable element is currently expanded.
-- **collapsed** Used to indicate that an expandable element is currently collapsed.
-
-To use, set the `accessibilityStates` to an array containing the list of current states.
-
-#### accessibilityViewIsModal (iOS)
-
-A Boolean value indicating whether VoiceOver should ignore the elements within views that are siblings of the receiver.
-
-For example, in a window that contains sibling views `A` and `B`, setting `accessibilityViewIsModal` to `true` on view `B` causes VoiceOver to ignore the elements in the view `A`. On the other hand, if view `B` contains a child view `C` and you set `accessibilityViewIsModal` to `true` on view `C`, VoiceOver does not ignore the elements in view `A`.
-
-#### accessibilityElementsHidden (iOS)
-
-A Boolean value indicating whether the accessibility elements contained within this accessibility element are hidden.
-
-For example, in a window that contains sibling views `A` and `B`, setting `accessibilityElementsHidden` to `true` on view `B` causes VoiceOver to ignore the elements in the view `B`. This is similar to the Android property `importantForAccessibility="no-hide-descendants"`.
-
-#### onAccessibilityTap (iOS)
-
-Use this property to assign a custom function to be called when someone activates an accessible element by double tapping on it while it's selected.
-
-#### onMagicTap (iOS)
-
-Assign this property to a custom function which will be called when someone performs the "magic tap" gesture, which is a double-tap with two fingers. A magic tap function should perform the most relevant action a user could take on a component. In the Phone app on iPhone, a magic tap answers a phone call, or ends the current one. If the selected element does not have an `onMagicTap` function, the system will traverse up the view hierarchy until it finds a view that does.
-
-#### onAccessibilityEscape (iOS)
-
-Assign this property to a custom function which will be called when someone performs the "escape" gesture, which is a two finger Z shaped gesture. An escape function should move back hierarchically in the user interface. This can mean moving up or back in a navigation hierarchy or dismissing a modal user interface. If the selected element does not have an `onAccessibilityEscape` function, the system will attempt to traverse up the view hierarchy until it finds a view that does or bonk to indicate it was unable to find one.
-
-#### accessibilityLiveRegion (Android)
-
-When components dynamically change, we want TalkBack to alert the end user. This is made possible by the ‘accessibilityLiveRegion’ property. It can be set to ‘none’, ‘polite’ and ‘assertive’:
-
-- **none** Accessibility services should not announce changes to this view.
-- **polite** Accessibility services should announce changes to this view.
-- **assertive** Accessibility services should interrupt ongoing speech to immediately announce changes to this view.
-
-```jsx
-<TouchableWithoutFeedback onPress={this._addOne}>
-  <View style={styles.embedded}>
-    <Text>Click me</Text>
-  </View>
-</TouchableWithoutFeedback>
-<Text accessibilityLiveRegion="polite">
-  Clicked {this.state.count} times
-</Text>
-```
-
-In the above example method \_addOne changes the state.count variable. As soon as an end user clicks the TouchableWithoutFeedback, TalkBack reads text in the Text view because of its 'accessibilityLiveRegion=”polite”' property.
-
-#### importantForAccessibility (Android)
-
-In the case of two overlapping UI components with the same parent, default accessibility focus can have unpredictable behavior. The ‘importantForAccessibility’ property will resolve this by controlling if a view fires accessibility events and if it is reported to accessibility services. It can be set to ‘auto’, ‘yes’, ‘no’ and ‘no-hide-descendants’ (the last value will force accessibility services to ignore the component and all of its children).
-
-```jsx
-<View style={styles.container}>
-  <View style={{position: 'absolute', left: 10, top: 10, right: 10, height: 100,
-    backgroundColor: 'green'}} importantForAccessibility=”yes”>
-    <Text> First layout </Text>
-  </View>
-  <View style={{position: 'absolute', left: 10, top: 10, right: 10, height: 100,
-    backgroundColor: 'yellow'}} importantForAccessibility=”no-hide-descendants”>
-    <Text> Second layout </Text>
-  </View>
-</View>
-```
-
-In the above example, the yellow layout and its descendants are completely invisible to TalkBack and all other accessibility services. So we can easily use overlapping views with the same parent without confusing TalkBack.
-
-### Accessibility Actions
-
-Accessibility actions allow an assistive technology to programmatically invoke the actions of a component. In order to support accessibility actions, a component must do two things:
-
-- Define the list of actions it supports via the `accessibilityActions` property.
-- Implement an `onAccessibilityAction` function to handle action requests.
-
-The `accessibilityActions` property should contain a list of action objects. Each action object should contain the following fields:
-
-| Name  | Type   | Required |
-| ----- | ------ | -------- |
-| name  | string | Yes      |
-| label | string | No       |
-
-Actions either represent standard actions, such as clicking a button or adjusting a slider, or custom actions specific to a given component such as deleting an email message. The `name` field is required for both standard and custom actions, but `label` is optional for standard actions.
-
-When adding support for standard actions, `name` must be one of the following:
-
-- `'magicTap'` - iOS only - While VoiceOver focus is on or inside the component, the user double tapped with two fingers.
-- `'escape'` - iOS only - While VoiceOver focus is on or inside the component, the user performed a two finger scrub gesture (left, right, left).
-- `'activate'` - Activate the component. Typically this should perform the same action as when the user touches or clicks the component when not using an assistive technology. This is generated when a screen reader user double taps the component.
-- `'increment'` - Increment an adjustable component. On iOS, VoiceOver generates this action when the component has a role of `'adjustable'` and the user places focus on it and swipes upward. On Android, TalkBack generates this action when the user places accessibility focus on the component and presses the volume up button.
-- `'decrement'` - Decrement an adjustable component. On iOS, VoiceOver generates this action when the component has a role of `'adjustable'` and the user places focus on it and swipes downward. On Android, TalkBack generates this action when the user places accessibility focus on the component and presses the volume down button.
-- `'longpress'` - Android only - This action is generated when the user places accessibility focus on the component and double tap and holds one finger on the screen. Typically, this should perform the same action as when the user holds down one finger on the component while not using an assistive technology.
-
-The `label` field is optional for standard actions, and is often unused by assistive technologies. For custom actions, it is a localized string containing a description of the action to be presented to the user.
-
-To handle action requests, a component must implement an `onAccessibilityAction` function. The only argument to this function is an event containing the name of the action to perform. The below example from RNTester shows how to create a component which defines and handles several custom actions.
-
-```jsx
-<View
-  accessible={true}
-  accessibilityActions={[
-    {name: 'cut', label: 'cut'},
-    {name: 'copy', label: 'copy'},
-    {name: 'paste', label: 'paste'},
-  ]}
-  onAccessibilityAction={(event) => {
-    switch (event.nativeEvent.actionName) {
-      case 'cut':
-        Alert.alert('Alert', 'cut action success');
-        break;
-      case 'copy':
-        Alert.alert('Alert', 'copy action success');
-        break;
-      case 'paste':
-        Alert.alert('Alert', 'paste action success');
-        break;
-    }
-  }}
-/>
-```
-
-### Checking if a Screen Reader is Enabled
-
-The `AccessibilityInfo` API allows you to determine whether or not a screen reader is currently active. See the [AccessibilityInfo documentation](accessibilityinfo.md) for details.
-
-### Sending Accessibility Events (Android)
-
-Sometimes it is useful to trigger an accessibility event on a UI component (i.e. when a custom view appears on a screen or a custom radio button has been selected). Native UIManager module exposes a method ‘sendAccessibilityEvent’ for this purpose. It takes two arguments: view tag and a type of an event.
-
-```jsx
-import { UIManager, findNodeHandle } from 'react-native';
-
-_onPress: function() {
-  const radioButton = this.state.radioButton === 'radiobutton_checked' ?
-    'radiobutton_unchecked' : 'radiobutton_checked'
-
-  this.setState({
-    radioButton: radioButton
-  });
-
-  if (radioButton === 'radiobutton_checked') {
-    UIManager.sendAccessibilityEvent(
-      findNodeHandle(this),
-      UIManager.AccessibilityEventTypes.typeViewClicked);
-  }
-}
-
-<CustomRadioButton
-  accessibilityComponentType={this.state.radioButton}
-  onPress={this._onPress}/>
-```
-
-In the above example we've created a custom radio button that now behaves like a native one. More specifically, TalkBack now correctly announces changes to the radio button selection.
-
-## Testing VoiceOver Support (iOS)
-
-To enable VoiceOver, go to the Settings app on your iOS device (it's not available for simulator). Tap General, then Accessibility. There you will find many tools that people use to make their devices more usable, such as bolder text, increased contrast, and VoiceOver.
-
-To enable VoiceOver, tap on VoiceOver under "Vision" and toggle the switch that appears at the top.
-
-At the very bottom of the Accessibility settings, there is an "Accessibility Shortcut". You can use this to toggle VoiceOver by triple clicking the Home button.
-
-## Testing TalkBack Support (Android)
-
-To enable TalkBack, go to the Settings app on your Android device or emulator. Tap Accessibility, then TalkBack. Toggle the "Use service" switch to enable or disable it.
-
-P.S. Android emulator doesn’t have TalkBack by default. To install it:
-
-1. Download TalkBack file here: https://google-talkback.en.uptodown.com/android
-2. Drag the downloaded `.apk` file into the emulator
-
-You can use the volume key shortcut to toggle TalkBack. To turn on the volume key shortcut, go to the Settings app, then Accessibility. At the top, turn on Volume key shortcut.
-
-To use the volume key shortcut, press both volume keys for 3 seconds to start an accessibility tool.
-
-Additionally, if you prefer, you can toggle TalkBack via command line with:
-
-```
-# disable
-adb shell settings put secure enabled_accessibility_services com.android.talkback/com.google.android.marvin.talkback.TalkBackService
-
-# enable
-adb shell settings put secure enabled_accessibility_services com.google.android.marvin.talkback/com.google.android.marvin.talkback.TalkBackService
-```
diff --git a/website/versioned_docs/version-0.60/animations.md b/website/versioned_docs/version-0.60/animations.md
deleted file mode 100644
index 842539239dd..00000000000
--- a/website/versioned_docs/version-0.60/animations.md
+++ /dev/null
@@ -1,409 +0,0 @@
----
-id: version-0.60-animations
-title: Animations
-original_id: animations
----
-
-Animations are very important to create a great user experience. Stationary objects must overcome inertia as they start moving. Objects in motion have momentum and rarely come to a stop immediately. Animations allow you to convey physically believable motion in your interface.
-
-React Native provides two complementary animation systems: [`Animated`](animations.md#animated-api) for granular and interactive control of specific values, and [`LayoutAnimation`](animations.md#layoutanimation-api) for animated global layout transactions.
-
-## `Animated` API
-
-The [`Animated`](animated.md) API is designed to make it very easy to concisely express a wide variety of interesting animation and interaction patterns in a very performant way. `Animated` focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and simple `start`/`stop` methods to control time-based animation execution.
-
-`Animated` exports six animatable component types: `View`, `Text`, `Image`, `ScrollView`, `FlatList` and `SectionList`, but you can also create your own using `Animated.createAnimatedComponent()`.
-
-For example, a container view that fades in when it is mounted may look like this:
-
-```SnackPlayer
-import React, { useState, useEffect } from 'react';
-import { Animated, Text, View } from 'react-native';
-
-const FadeInView = (props) => {
-  const [fadeAdmin] = useState(new Animated.Value(0))  // Initial value for opacity: 0
-
-  React.useEffect(() => {
-    Animated.timing(
-      fadeAdmin,
-      {
-        toValue: 1,
-        duration: 10000,
-      }
-    ).start();
-  }, [])
-
-  return (
-    <Animated.View                 // Special animatable View
-      style={{
-        ...props.style,
-        opacity: fadeAdnim,         // Bind opacity to animated value
-      }}
-    >
-      {props.children}
-    </Animated.View>
-  );
-}
-
-// You can then use your `FadeInView` in place of a `View` in your components:
-export default () => {
-  return (
-    <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
-      <FadeInView style={{width: 250, height: 50, backgroundColor: 'powderblue'}}>
-        <Text style={{fontSize: 28, textAlign: 'center', margin: 10}}>Fading in</Text>
-      </FadeInView>
-    </View>
-  )
-}
-```
-
-Let's break down what's happening here. In the `FadeInView` constructor, a new `Animated.Value` called `fadeAnim` is initialized as part of `state`. The opacity property on the `View` is mapped to this animated value. Behind the scenes, the numeric value is extracted and used to set opacity.
-
-When the component mounts, the opacity is set to 0. Then, an easing animation is started on the `fadeAnim` animated value, which will update all of its dependent mappings (in this case, just the opacity) on each frame as the value animates to the final value of 1.
-
-This is done in an optimized way that is faster than calling `setState` and re-rendering. Because the entire configuration is declarative, we will be able to implement further optimizations that serialize the configuration and runs the animation on a high-priority thread.
-
-### Configuring animations
-
-Animations are heavily configurable. Custom and predefined easing functions, delays, durations, decay factors, spring constants, and more can all be tweaked depending on the type of animation.
-
-`Animated` provides several animation types, the most commonly used one being [`Animated.timing()`](animated.md#timing). It supports animating a value over time using one of various predefined easing functions, or you can use your own. Easing functions are typically used in animation to convey gradual acceleration and deceleration of objects.
-
-By default, `timing` will use a easeInOut curve that conveys gradual acceleration to full speed and concludes by gradually decelerating to a stop. You can specify a different easing function by passing a `easing` parameter. Custom `duration` or even a `delay` before the animation starts is also supported.
-
-For example, if we want to create a 2-second long animation of an object that slightly backs up before moving to its final position:
-
-```jsx
-Animated.timing(this.state.xPosition, {
-  toValue: 100,
-  easing: Easing.back(),
-  duration: 2000,
-}).start();
-```
-
-Take a look at the [Configuring animations](animated.md#configuring-animations) section of the `Animated` API reference to learn more about all the config parameters supported by the built-in animations.
-
-### Composing animations
-
-Animations can be combined and played in sequence or in parallel. Sequential animations can play immediately after the previous animation has finished, or they can start after a specified delay. The `Animated` API provides several methods, such as `sequence()` and `delay()`, each of which simply take an array of animations to execute and automatically calls `start()`/`stop()` as needed.
-
-For example, the following animation coasts to a stop, then it springs back while twirling in parallel:
-
-```jsx
-Animated.sequence([
-  // decay, then spring to start and twirl
-  Animated.decay(position, {
-    // coast to a stop
-    velocity: {x: gestureState.vx, y: gestureState.vy}, // velocity from gesture release
-    deceleration: 0.997,
-  }),
-  Animated.parallel([
-    // after decay, in parallel:
-    Animated.spring(position, {
-      toValue: {x: 0, y: 0}, // return to start
-    }),
-    Animated.timing(twirl, {
-      // and twirl
-      toValue: 360,
-    }),
-  ]),
-]).start(); // start the sequence group
-```
-
-If one animation is stopped or interrupted, then all other animations in the group are also stopped. `Animated.parallel` has a `stopTogether` option that can be set to `false` to disable this.
-
-You can find a full list of composition methods in the [Composing animations](animated.md#composing-animations) section of the `Animated` API reference.
-
-### Combining animated values
-
-You can [combine two animated values](animated.md#combining-animated-values) via addition, multiplication, division, or modulo to make a new animated value.
-
-There are some cases where an animated value needs to invert another animated value for calculation. An example is inverting a scale (2x --> 0.5x):
-
-```jsx
-const a = new Animated.Value(1);
-const b = Animated.divide(1, a);
-
-Animated.spring(a, {
-  toValue: 2,
-}).start();
-```
-
-### Interpolation
-
-Each property can be run through an interpolation first. An interpolation maps input ranges to output ranges, typically using a linear interpolation but also supports easing functions. By default, it will extrapolate the curve beyond the ranges given, but you can also have it clamp the output value.
-
-A simple mapping to convert a 0-1 range to a 0-100 range would be:
-
-```jsx
-value.interpolate({
-  inputRange: [0, 1],
-  outputRange: [0, 100],
-});
-```
-
-For example, you may want to think about your `Animated.Value` as going from 0 to 1, but animate the position from 150px to 0px and the opacity from 0 to 1. This can easily be done by modifying `style` from the example above like so:
-
-```jsx
-  style={{
-    opacity: this.state.fadeAnim, // Binds directly
-    transform: [{
-      translateY: this.state.fadeAnim.interpolate({
-        inputRange: [0, 1],
-        outputRange: [150, 0]  // 0 : 150, 0.5 : 75, 1 : 0
-      }),
-    }],
-  }}
-```
-
-[`interpolate()`](animated.md#interpolate) supports multiple range segments as well, which is handy for defining dead zones and other handy tricks. For example, to get a negation relationship at -300 that goes to 0 at -100, then back up to 1 at 0, and then back down to zero at 100 followed by a dead-zone that remains at 0 for everything beyond that, you could do:
-
-```jsx
-value.interpolate({
-  inputRange: [-300, -100, 0, 100, 101],
-  outputRange: [300, 0, 1, 0, 0],
-});
-```
-
-Which would map like so:
-
-```
-Input | Output
-------|-------
-  -400|    450
-  -300|    300
-  -200|    150
-  -100|      0
-   -50|    0.5
-     0|      1
-    50|    0.5
-   100|      0
-   101|      0
-   200|      0
-```
-
-`interpolate()` also supports mapping to strings, allowing you to animate colors as well as values with units. For example, if you wanted to animate a rotation you could do:
-
-```jsx
-value.interpolate({
-  inputRange: [0, 360],
-  outputRange: ['0deg', '360deg'],
-});
-```
-
-`interpolate()` also supports arbitrary easing functions, many of which are already implemented in the [`Easing`](easing.md) module. `interpolate()` also has configurable behavior for extrapolating the `outputRange`. You can set the extrapolation by setting the `extrapolate`, `extrapolateLeft`, or `extrapolateRight` options. The default value is `extend` but you can use `clamp` to prevent the output value from exceeding `outputRange`.
-
-### Tracking dynamic values
-
-Animated values can also track other values. Just set the `toValue` of an animation to another animated value instead of a plain number. For example, a "Chat Heads" animation like the one used by Messenger on Android could be implemented with a `spring()` pinned on another animated value, or with `timing()` and a `duration` of 0 for rigid tracking. They can also be composed with interpolations:
-
-```jsx
-Animated.spring(follower, {toValue: leader}).start();
-Animated.timing(opacity, {
-  toValue: pan.x.interpolate({
-    inputRange: [0, 300],
-    outputRange: [1, 0],
-  }),
-}).start();
-```
-
-The `leader` and `follower` animated values would be implemented using `Animated.ValueXY()`. `ValueXY` is a handy way to deal with 2D interactions, such as panning or dragging. It is a simple wrapper that basically contains two `Animated.Value` instances and some helper functions that call through to them, making `ValueXY` a drop-in replacement for `Value` in many cases. It allows us to track both x and y values in the example above.
-
-### Tracking gestures
-
-Gestures, like panning or scrolling, and other events can map directly to animated values using [`Animated.event`](animated.md#event). This is done with a structured map syntax so that values can be extracted from complex event objects. The first level is an array to allow mapping across multiple args, and that array contains nested objects.
-
-For example, when working with horizontal scrolling gestures, you would do the following in order to map `event.nativeEvent.contentOffset.x` to `scrollX` (an `Animated.Value`):
-
-```jsx
- onScroll={Animated.event(
-   // scrollX = e.nativeEvent.contentOffset.x
-   [{ nativeEvent: {
-        contentOffset: {
-          x: scrollX
-        }
-      }
-    }]
- )}
-```
-
-When using `PanResponder`, you could use the following code to extract the x and y positions from `gestureState.dx` and `gestureState.dy`. We use a `null` in the first position of the array, as we are only interested in the second argument passed to the `PanResponder` handler, which is the `gestureState`.
-
-```jsx
-onPanResponderMove={Animated.event(
-  [null, // ignore the native event
-  // extract dx and dy from gestureState
-  // like 'pan.x = gestureState.dx, pan.y = gestureState.dy'
-  {dx: pan.x, dy: pan.y}
-])}
-```
-
-### Responding to the current animation value
-
-You may notice that there is no obvious way to read the current value while animating. This is because the value may only be known in the native runtime due to optimizations. If you need to run JavaScript in response to the current value, there are two approaches:
-
-- `spring.stopAnimation(callback)` will stop the animation and invoke `callback` with the final value. This is useful when making gesture transitions.
-- `spring.addListener(callback)` will invoke `callback` asynchronously while the animation is running, providing a recent value. This is useful for triggering state changes, for example snapping a bobble to a new option as the user drags it closer, because these larger state changes are less sensitive to a few frames of lag compared to continuous gestures like panning which need to run at 60 fps.
-
-`Animated` is designed to be fully serializable so that animations can be run in a high performance way, independent of the normal JavaScript event loop. This does influence the API, so keep that in mind when it seems a little trickier to do something compared to a fully synchronous system. Check out `Animated.Value.addListener` as a way to work around some of these limitations, but use it sparingly since it might have performance implications in the future.
-
-### Using the native driver
-
-The `Animated` API is designed to be serializable. By using the [native driver](http://facebook.github.io/react-native/blog/2017/02/14/using-native-driver-for-animated), we send everything about the animation to native before starting the animation, allowing native code to perform the animation on the UI thread without having to go through the bridge on every frame. Once the animation has started, the JS thread can be blocked without affecting the animation.
-
-Using the native driver for normal animations is quite simple. Just add `useNativeDriver: true` to the animation config when starting it.
-
-```jsx
-Animated.timing(this.state.animatedValue, {
-  toValue: 1,
-  duration: 500,
-  useNativeDriver: true, // <-- Add this
-}).start();
-```
-
-Animated values are only compatible with one driver so if you use native driver when starting an animation on a value, make sure every animation on that value also uses the native driver.
-
-The native driver also works with `Animated.event`. This is especially useful for animations that follow the scroll position as without the native driver, the animation will always run a frame behind the gesture due to the async nature of React Native.
-
-```jsx
-<Animated.ScrollView // <-- Use the Animated ScrollView wrapper
-  scrollEventThrottle={1} // <-- Use 1 here to make sure no events are ever missed
-  onScroll={Animated.event(
-    [
-      {
-        nativeEvent: {
-          contentOffset: {y: this.state.animatedValue},
-        },
-      },
-    ],
-    {useNativeDriver: true}, // <-- Add this
-  )}>
-  {content}
-</Animated.ScrollView>
-```
-
-You can see the native driver in action by running the [RNTester app](https://github.com/facebook/react-native/blob/master/RNTester/), then loading the Native Animated Example. You can also take a look at the [source code](https://github.com/facebook/react-native/blob/master/RNTester/js/NativeAnimationsExample.js) to learn how these examples were produced.
-
-#### Caveats
-
-Not everything you can do with `Animated` is currently supported by the native driver. The main limitation is that you can only animate non-layout properties: things like `transform` and `opacity` will work, but flexbox and position properties will not. When using `Animated.event`, it will only work with direct events and not bubbling events. This means it does not work with `PanResponder` but does work with things like `ScrollView#onScroll`.
-
-When an animation is running, it can prevent `VirtualizedList` components from rendering more rows. If you need to run a long or looping animation while the user is scrolling through a list, you can use `isInteraction: false` in your animation's config to prevent this issue.
-
-### Bear in mind
-
-While using transform styles such as `rotateY`, `rotateX`, and others ensure the transform style `perspective` is in place. At this time some animations may not render on Android without it. Example below.
-
-```jsx
-<Animated.View
-  style={{
-    transform: [
-      {scale: this.state.scale},
-      {rotateY: this.state.rotateY},
-      {perspective: 1000}, // without this line this Animation will not render on Android while working fine on iOS
-    ],
-  }}
-/>
-```
-
-### Additional examples
-
-The RNTester app has various examples of `Animated` in use:
-
-- [AnimatedGratuitousApp](https://github.com/facebook/react-native/tree/master/RNTester/js/examples/Animated/AnimatedGratuitousApp)
-- [NativeAnimationsExample](https://github.com/facebook/react-native/blob/master/RNTester/js/examples/NativeAnimation/NativeAnimationsExample.js)
-
-## `LayoutAnimation` API
-
-`LayoutAnimation` allows you to globally configure `create` and `update` animations that will be used for all views in the next render/layout cycle. This is useful for doing flexbox layout updates without bothering to measure or calculate specific properties in order to animate them directly, and is especially useful when layout changes may affect ancestors, for example a "see more" expansion that also increases the size of the parent and pushes down the row below which would otherwise require explicit coordination between the components in order to animate them all in sync.
-
-Note that although `LayoutAnimation` is very powerful and can be quite useful, it provides much less control than `Animated` and other animation libraries, so you may need to use another approach if you can't get `LayoutAnimation` to do what you want.
-
-Note that in order to get this to work on **Android** you need to set the following flags via `UIManager`:
-
-```jsx
-UIManager.setLayoutAnimationEnabledExperimental &&
-  UIManager.setLayoutAnimationEnabledExperimental(true);
-```
-
-```SnackPlayer
-import React from 'react';
-import {
-  NativeModules,
-  LayoutAnimation,
-  Text,
-  TouchableOpacity,
-  StyleSheet,
-  View,
-} from 'react-native';
-
-const { UIManager } = NativeModules;
-
-UIManager.setLayoutAnimationEnabledExperimental &&
-  UIManager.setLayoutAnimationEnabledExperimental(true);
-
-export default class App extends React.Component {
-  state = {
-    w: 100,
-    h: 100,
-  };
-
-  _onPress = () => {
-    // Animate the update
-    LayoutAnimation.spring();
-    this.setState({w: this.state.w + 15, h: this.state.h + 15})
-  }
-
-  render() {
-    return (
-      <View style={styles.container}>
-        <View style={[styles.box, {width: this.state.w, height: this.state.h}]} />
-        <TouchableOpacity onPress={this._onPress}>
-          <View style={styles.button}>
-            <Text style={styles.buttonText}>Press me!</Text>
-          </View>
-        </TouchableOpacity>
-      </View>
-    );
-  }
-}
-
-const styles = StyleSheet.create({
-  container: {
-    flex: 1,
-    alignItems: 'center',
-    justifyContent: 'center',
-  },
-  box: {
-    width: 200,
-    height: 200,
-    backgroundColor: 'red',
-  },
-  button: {
-    backgroundColor: 'black',
-    paddingHorizontal: 20,
-    paddingVertical: 15,
-    marginTop: 15,
-  },
-  buttonText: {
-    color: '#fff',
-    fontWeight: 'bold',
-  },
-});
-```
-
-This example uses a preset value, you can customize the animations as you need, see [LayoutAnimation.js](https://github.com/facebook/react-native/blob/master/Libraries/LayoutAnimation/LayoutAnimation.js) for more information.
-
-## Additional notes
-
-### `requestAnimationFrame`
-
-`requestAnimationFrame` is a polyfill from the browser that you might be familiar with. It accepts a function as its only argument and calls that function before the next repaint. It is an essential building block for animations that underlies all of the JavaScript-based animation APIs. In general, you shouldn't need to call this yourself - the animation APIs will manage frame updates for you.
-
-### `setNativeProps`
-
-As mentioned [in the Direct Manipulation section](direct-manipulation.md), `setNativeProps` allows us to modify properties of native-backed components (components that are actually backed by native views, unlike composite components) directly, without having to `setState` and re-render the component hierarchy.
-
-We could use this in the Rebound example to update the scale - this might be helpful if the component that we are updating is deeply nested and hasn't been optimized with `shouldComponentUpdate`.
-
-If you find your animations with dropping frames (performing below 60 frames per second), look into using `setNativeProps` or `shouldComponentUpdate` to optimize them. Or you could run the animations on the UI thread rather than the JavaScript thread [with the useNativeDriver option](http://facebook.github.io/react-native/blog/2017/02/14/using-native-driver-for-animated). You may also want to defer any computationally intensive work until after animations are complete, using the [InteractionManager](interactionmanager.md). You can monitor the frame rate by using the In-App Developer Menu "FPS Monitor" tool.
diff --git a/website/versioned_docs/version-0.60/app-extensions.md b/website/versioned_docs/version-0.60/app-extensions.md
deleted file mode 100644
index 63bfbd7e745..00000000000
--- a/website/versioned_docs/version-0.60/app-extensions.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-id: version-0.60-app-extensions
-title: App Extensions
-original_id: app-extensions
----
-
-App extensions let you provide custom functionality and content outside of your main app. There are different types of app extensions on iOS, and they are all covered in the [App Extension Programming Guide](https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/index.html#//apple_ref/doc/uid/TP40014214-CH20-SW1). In this guide, we'll briefly cover how you may take advantage of app extensions on iOS.
-
-## Memory use in extensions
-
-As these extensions are loaded outside of the regular app sandbox, it's highly likely that several of these app extensions will be loaded simultaneously. As you might expect, these extensions have small memory usage limits. Keep these in mind when developing your app extensions. It's always highly recommended to test your application on an actual device, and more so when developing app extensions: too frequently, developers find that their extension works just fine in the iOS Simulator, only to get user reports that their extension is not loading on actual devices.
-
-We highly recommend that you watch Conrad Kramer's talk on [Memory Use in Extensions](https://www.youtube.com/watch?v=GqXMqn6MXrM) to learn more about this topic.
-
-### Today widget
-
-The memory limit of a Today widget is 16 MB. As it happens, Today widget implementations using React Native may work unreliably because the memory usage tends to be too high. You can tell if your Today widget is exceeding the memory limit if it yields the message 'Unable to Load':
-
-![](/react-native/docs/assets/TodayWidgetUnableToLoad.jpg)
-
-Always make sure to test your app extensions in a real device, but be aware that this may not be sufficient, especially when dealing with Today widgets. Debug-configured builds are more likely to exceed the memory limits, while release-configured builds don't fail right away. We highly recommend that you use [Xcode's Instruments](https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/index.html) to analyze your real world memory usage, as it's very likely that your release-configured build is very close to the 16 MB limit. In situations like these, it is easy to go over the 16 MB limit by performing common operations, such as fetching data from an API.
-
-To experiment with the limits of React Native Today widget implementations, try extending the example project in [react-native-today-widget](https://github.com/matejkriz/react-native-today-widget/).
-
-### Other app extensions
-
-Other types of app extensions have greater memory limits than the Today widget. For instance, Custom Keyboard extensions are limited to 48 MB, and Share extensions are limited to 120 MB. Implementing such app extensions with React Native is more viable. One proof of concept example is [react-native-ios-share-extension](https://github.com/andrewsardone/react-native-ios-share-extension).
diff --git a/website/versioned_docs/version-0.60/communication-ios.md b/website/versioned_docs/version-0.60/communication-ios.md
deleted file mode 100644
index 9b9b190059f..00000000000
--- a/website/versioned_docs/version-0.60/communication-ios.md
+++ /dev/null
@@ -1,201 +0,0 @@
----
-id: version-0.60-communication-ios
-title: Communication between native and React Native
-original_id: communication-ios
----
-
-In [Integrating with Existing Apps guide](integration-with-existing-apps.md) and [Native UI Components guide](native-components-ios.md) we learn how to embed React Native in a native component and vice versa. When we mix native and React Native components, we'll eventually find a need to communicate between these two worlds. Some ways to achieve that have been already mentioned in other guides. This article summarizes available techniques.
-
-## Introduction
-
-React Native is inspired by React, so the basic idea of the information flow is similar. The flow in React is one-directional. We maintain a hierarchy of components, in which each component depends only on its parent and its own internal state. We do this with properties: data is passed from a parent to its children in a top-down manner. If an ancestor component relies on the state of its descendant, one should pass down a callback to be used by the descendant to update the ancestor.
-
-The same concept applies to React Native. As long as we are building our application purely within the framework, we can drive our app with properties and callbacks. But, when we mix React Native and native components, we need some special, cross-language mechanisms that would allow us to pass information between them.
-
-## Properties
-
-Properties are the simplest way of cross-component communication. So we need a way to pass properties both from native to React Native, and from React Native to native.
-
-### Passing properties from native to React Native
-
-In order to embed a React Native view in a native component, we use `RCTRootView`. `RCTRootView` is a `UIView` that holds a React Native app. It also provides an interface between native side and the hosted app.
-
-`RCTRootView` has an initializer that allows you to pass arbitrary properties down to the React Native app. The `initialProperties` parameter has to be an instance of `NSDictionary`. The dictionary is internally converted into a JSON object that the top-level JS component can reference.
-
-```objectivec
-NSArray *imageList = @[@"http://foo.com/bar1.png",
-                       @"http://foo.com/bar2.png"];
-
-NSDictionary *props = @{@"images" : imageList};
-
-RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
-                                                 moduleName:@"ImageBrowserApp"
-                                          initialProperties:props];
-```
-
-```jsx
-import React from 'react';
-import {View, Image} from 'react-native';
-
-export default class ImageBrowserApp extends React.Component {
-  renderImage(imgURI) {
-    return <Image source={{uri: imgURI}} />;
-  }
-  render() {
-    return <View>{this.props.images.map(this.renderImage)}</View>;
-  }
-}
-```
-
-`RCTRootView` also provides a read-write property `appProperties`. After `appProperties` is set, the React Native app is re-rendered with new properties. The update is only performed when the new updated properties differ from the previous ones.
-
-```objectivec
-NSArray *imageList = @[@"http://foo.com/bar3.png",
-                       @"http://foo.com/bar4.png"];
-
-rootView.appProperties = @{@"images" : imageList};
-```
-
-It is fine to update properties anytime. However, updates have to be performed on the main thread. You use the getter on any thread.
-
-> **_Note:_** Currently, there is a known issue where setting appProperties during the bridge startup, the change can be lost. See https://github.com/facebook/react-native/issues/20115 for more information.
-
-There is no way to update only a few properties at a time. We suggest that you build it into your own wrapper instead.
-
-> **_Note:_** Currently, JS function `componentWillUpdateProps` of the top level RN component will not be called after a prop update. However, you can access the new props in `componentDidMount` function.
-
-### Passing properties from React Native to native
-
-The problem exposing properties of native components is covered in detail in [this article](native-components-ios.md#properties). In short, export properties with `RCT_CUSTOM_VIEW_PROPERTY` macro in your custom native component, then just use them in React Native as if the component was an ordinary React Native component.
-
-### Limits of properties
-
-The main drawback of cross-language properties is that they do not support callbacks, which would allow us to handle bottom-up data bindings. Imagine you have a small RN view that you want to be removed from the native parent view as a result of a JS action. There is no way to do that with props, as the information would need to go bottom-up.
-
-Although we have a flavor of cross-language callbacks ([described here](native-modules-ios.md#callbacks)), these callbacks are not always the thing we need. The main problem is that they are not intended to be passed as properties. Rather, this mechanism allows us to trigger a native action from JS, and handle the result of that action in JS.
-
-## Other ways of cross-language interaction (events and native modules)
-
-As stated in the previous chapter, using properties comes with some limitations. Sometimes properties are not enough to drive the logic of our app and we need a solution that gives more flexibility. This chapter covers other communication techniques available in React Native. They can be used for internal communication (between JS and native layers in RN) as well as for external communication (between RN and the 'pure native' part of your app).
-
-React Native enables you to perform cross-language function calls. You can execute custom native code from JS and vice versa. Unfortunately, depending on the side we are working on, we achieve the same goal in different ways. For native - we use events mechanism to schedule an execution of a handler function in JS, while for React Native we directly call methods exported by native modules.
-
-### Calling React Native functions from native (events)
-
-Events are described in detail in [this article](native-components-ios.md#events). Note that using events gives us no guarantees about execution time, as the event is handled on a separate thread.
-
-Events are powerful, because they allow us to change React Native components without needing a reference to them. However, there are some pitfalls that you can fall into while using them:
-
-- As events can be sent from anywhere, they can introduce spaghetti-style dependencies into your project.
-- Events share namespace, which means that you may encounter some name collisions. Collisions will not be detected statically, which makes them hard to debug.
-- If you use several instances of the same React Native component and you want to distinguish them from the perspective of your event, you'll likely need to introduce identifiers and pass them along with events (you can use the native view's `reactTag` as an identifier).
-
-The common pattern we use when embedding native in React Native is to make the native component's RCTViewManager a delegate for the views, sending events back to JavaScript via the bridge. This keeps related event calls in one place.
-
-### Calling native functions from React Native (native modules)
-
-Native modules are Objective-C classes that are available in JS. Typically one instance of each module is created per JS bridge. They can export arbitrary functions and constants to React Native. They have been covered in detail in [this article](native-modules-ios.md#content).
-
-The fact that native modules are singletons limits the mechanism in the context of embedding. Let's say we have a React Native component embedded in a native view and we want to update the native, parent view. Using the native module mechanism, we would export a function that not only takes expected arguments, but also an identifier of the parent native view. The identifier would be used to retrieve a reference to the parent view to update. That said, we would need to keep a mapping from identifiers to native views in the module.
-
-Although this solution is complex, it is used in `RCTUIManager`, which is an internal React Native class that manages all React Native views.
-
-Native modules can also be used to expose existing native libraries to JS. The [Geolocation library](https://github.com/facebook/react-native/tree/master/Libraries/Geolocation) is a living example of the idea.
-
-> **_Warning_**: All native modules share the same namespace. Watch out for name collisions when creating new ones.
-
-## Layout computation flow
-
-When integrating native and React Native, we also need a way to consolidate two different layout systems. This section covers common layout problems and provides a brief description of mechanisms to address them.
-
-### Layout of a native component embedded in React Native
-
-This case is covered in [this article](native-components-ios.md#styles). Basically, as all our native react views are subclasses of `UIView`, most style and size attributes will work like you would expect out of the box.
-
-### Layout of a React Native component embedded in native
-
-#### React Native content with fixed size
-
-The simplest scenario is when we have a React Native app with a fixed size, which is known to the native side. In particular, a full-screen React Native view falls into this case. If we want a smaller root view, we can explicitly set RCTRootView's frame.
-
-For instance, to make an RN app 200 (logical) pixels high, and the hosting view's width wide, we could do:
-
-```objectivec
-// SomeViewController.m
-
-- (void)viewDidLoad
-{
-  [...]
-  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
-                                                   moduleName:appName
-                                            initialProperties:props];
-  rootView.frame = CGRectMake(0, 0, self.view.width, 200);
-  [self.view addSubview:rootView];
-}
-```
-
-When we have a fixed size root view, we need to respect its bounds on the JS side. In other words, we need to ensure that the React Native content can be contained within the fixed-size root view. The easiest way to ensure this is to use flexbox layout. If you use absolute positioning, and React components are visible outside the root view's bounds, you'll get overlap with native views, causing some features to behave unexpectedly. For instance, 'TouchableHighlight' will not highlight your touches outside the root view's bounds.
-
-It's totally fine to update root view's size dynamically by re-setting its frame property. React Native will take care of the content's layout.
-
-#### React Native content with flexible size
-
-In some cases we'd like to render content of initially unknown size. Let's say the size will be defined dynamically in JS. We have two solutions to this problem.
-
-1. You can wrap your React Native view in a `ScrollView` component. This guarantees that your content will always be available and it won't overlap with native views.
-2. React Native allows you to determine, in JS, the size of the RN app and provide it to the owner of the hosting `RCTRootView`. The owner is then responsible for re-laying out the subviews and keeping the UI consistent. We achieve this with `RCTRootView`'s flexibility modes.
-
-`RCTRootView` supports 4 different size flexibility modes:
-
-```objectivec
-// RCTRootView.h
-
-typedef NS_ENUM(NSInteger, RCTRootViewSizeFlexibility) {
-  RCTRootViewSizeFlexibilityNone = 0,
-  RCTRootViewSizeFlexibilityWidth,
-  RCTRootViewSizeFlexibilityHeight,
-  RCTRootViewSizeFlexibilityWidthAndHeight,
-};
-```
-
-`RCTRootViewSizeFlexibilityNone` is the default value, which makes a root view's size fixed (but it still can be updated with `setFrame:`). The other three modes allow us to track React Native content's size updates. For instance, setting mode to `RCTRootViewSizeFlexibilityHeight` will cause React Native to measure the content's height and pass that information back to `RCTRootView`'s delegate. An arbitrary action can be performed within the delegate, including setting the root view's frame, so the content fits. The delegate is called only when the size of the content has changed.
-
-> **_Warning:_** Making a dimension flexible in both JS and native leads to undefined behavior. For example - don't make a top-level React component's width flexible (with `flexbox`) while you're using `RCTRootViewSizeFlexibilityWidth` on the hosting `RCTRootView`.
-
-Let's look at an example.
-
-```objectivec
-// FlexibleSizeExampleView.m
-
-- (instancetype)initWithFrame:(CGRect)frame
-{
-  [...]
-
-  _rootView = [[RCTRootView alloc] initWithBridge:bridge
-  moduleName:@"FlexibilityExampleApp"
-  initialProperties:@{}];
-
-  _rootView.delegate = self;
-  _rootView.sizeFlexibility = RCTRootViewSizeFlexibilityHeight;
-  _rootView.frame = CGRectMake(0, 0, self.frame.size.width, 0);
-}
-
-#pragma mark - RCTRootViewDelegate
-- (void)rootViewDidChangeIntrinsicSize:(RCTRootView *)rootView
-{
-  CGRect newFrame = rootView.frame;
-  newFrame.size = rootView.intrinsicContentSize;
-
-  rootView.frame = newFrame;
-}
-```
-
-In the example we have a `FlexibleSizeExampleView` view that holds a root view. We create the root view, initialize it and set the delegate. The delegate will handle size updates. Then, we set the root view's size flexibility to `RCTRootViewSizeFlexibilityHeight`, which means that `rootViewDidChangeIntrinsicSize:` method will be called every time the React Native content changes its height. Finally, we set the root view's width and position. Note that we set there height as well, but it has no effect as we made the height RN-dependent.
-
-You can checkout full source code of the example [here](https://github.com/facebook/react-native/blob/master/RNTester/RNTester/NativeExampleViews/FlexibleSizeExampleView.m).
-
-It's fine to change root view's size flexibility mode dynamically. Changing flexibility mode of a root view will schedule a layout recalculation and the delegate `rootViewDidChangeIntrinsicSize:` method will be called once the content size is known.
-
-> **_Note:_** React Native layout calculation is performed on a special thread, while native UI view updates are done on the main thread. This may cause temporary UI inconsistencies between native and React Native. This is a known problem and our team is working on synchronizing UI updates coming from different sources.
-
-> **_Note:_** React Native does not perform any layout calculations until the root view becomes a subview of some other views. If you want to hide React Native view until its dimensions are known, add the root view as a subview and make it initially hidden (use `UIView`'s `hidden` property). Then change its visibility in the delegate method.
diff --git a/website/versioned_docs/version-0.60/components-and-apis.md b/website/versioned_docs/version-0.60/components-and-apis.md
deleted file mode 100644
index f9662051826..00000000000
--- a/website/versioned_docs/version-0.60/components-and-apis.md
+++ /dev/null
@@ -1,222 +0,0 @@
----
-id: version-0.60-components-and-apis
-title: Components and APIs
-original_id: components-and-apis
----
-
-React Native provides a number of built-in components. You will find a full list of components and APIs on the sidebar to the left. If you're not sure where to get started, take a look at the following categories:
-
-- [Basic Components](components-and-apis.md#basic-components)
-- [User Interface](components-and-apis.md#user-interface)
-- [List Views](components-and-apis.md#list-views)
-- [iOS-specific](components-and-apis.md#ios-components-and-apis)
-- [Android-specific](components-and-apis.md#android-components-and-apis)
-- [Others](components-and-apis.md#others)
-
-You're not limited to the components and APIs bundled with React Native. React Native is a community of thousands of developers. If you're looking for a library that does something specific, search the npm registry for packages mentioning [react-native](https://www.npmjs.com/search?q=react-native&page=1&ranking=optimal), or check out [Awesome React Native](http://www.awesome-react-native.com/) for a curated list.
-
-## Basic Components
-
-Most apps will end up using one of these basic components. You'll want to get yourself familiarized with all of these if you're new to React Native.
-
-<div class="component-grid component-grid-border">
-  <div class="component">
-    <h3><a href="./view">View</a></h3>
-    <p>The most fundamental component for building a UI.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./text">Text</a></h3>
-    <p>A component for displaying text.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./image">Image</a></h3>
-    <p>A component for displaying images.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./textinput">TextInput</a></h3>
-    <p>A component for inputting text into the app via a keyboard.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./scrollview">ScrollView</a></h3>
-    <p>Provides a scrolling container that can host multiple components and views.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./stylesheet">StyleSheet</a></h3>
-    <p>Provides an abstraction layer similar to CSS stylesheets.</p>
-  </div>
-</div>
-
-## User Interface
-
-Render common user interface controls on any platform using the following components. For platform specific components, keep reading.
-
-<div class="component-grid component-grid-border">
-  <div class="component">
-    <h3><a href="./button">Button</a></h3>
-    <p>A basic button component for handling touches that should render nicely on any platform.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./picker">Picker</a></h3>
-    <p>Renders the native picker component on iOS and Android.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./slider">Slider</a></h3>
-    <p>A component used to select a single value from a range of values.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./switch">Switch</a></h3>
-    <p>Renders a boolean input.</p>
-  </div>
-</div>
-
-## List Views
-
-Unlike the more generic `ScrollView`, the following list view components only render elements that are currently showing on the screen. This makes them a great choice for displaying long lists of data.
-
-<div class="component-grid component-grid-border">
-  <div class="component">
-    <h3><a href="./flatlist">FlatList</a></h3>
-    <p>A component for rendering performant scrollable lists.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./sectionlist">SectionList</a></h3>
-    <p>Like <code>FlatList</code>, but for sectioned lists.</p>
-  </div>
-</div>
-
-## iOS Components and APIs
-
-Many of the following components provide wrappers for commonly used UIKit classes.
-
-<div class="component-grid component-grid-border">
-  <div class="component">
-    <h3><a href="./actionsheetios">ActionSheetIOS</a></h3>
-    <p>API to display an iOS action sheet or share sheet.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./alertios">AlertIOS</a></h3>
-    <p>Create an iOS alert dialog with a message or create a prompt for user input.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./datepickerios">DatePickerIOS</a></h3>
-    <p>Renders a date/time picker (selector) on iOS.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./imagepickerios">ImagePickerIOS</a></h3>
-    <p>Renders a image picker on iOS.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./progressviewios">ProgressViewIOS</a></h3>
-    <p>Renders a <code>UIProgressView</a></code> on iOS.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./pushnotificationios">PushNotificationIOS</a></h3>
-    <p>Handle push notifications for your app, including permission handling and icon badge number.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./segmentedcontrolios">SegmentedControlIOS</a></h3>
-    <p>Renders a <code>UISegmentedControl</code> on iOS.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./tabbarios">TabBarIOS</a></h3>
-    <p>Renders a <code>UITabViewController</code> on iOS. Use with <a href="./tabbarios-item">TabBarIOS.Item</a>.</p>
-  </div>
-</div>
-
-## Android Components and APIs
-
-Many of the following components provide wrappers for commonly used Android classes.
-
-<div class="component-grid component-grid-border">
-  <div class="component">
-    <h3><a href="./backhandler">BackHandler</a></h3>
-    <p>Detect hardware button presses for back navigation.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./datepickerandroid">DatePickerAndroid</a></h3>
-    <p>Opens the standard Android date picker dialog.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./drawerlayoutandroid">DrawerLayoutAndroid</a></h3>
-    <p>Renders a <code>DrawerLayout</code> on Android.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./permissionsandroid">PermissionsAndroid</a></h3>
-    <p>Provides access to the permissions model introduced in Android M.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./progressbarandroid">ProgressBarAndroid</a></h3>
-    <p>Renders a <code>ProgressBar</code> on Android.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./timepickerandroid">TimePickerAndroid</a></h3>
-    <p>Opens the standard Android time picker dialog.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./toastandroid">ToastAndroid</a></h3>
-    <p>Create an Android Toast alert.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./toolbarandroid">ToolbarAndroid</a></h3>
-    <p>Renders a <code>Toolbar</code> on Android.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./viewpagerandroid">ViewPagerAndroid</a></h3>
-    <p>Container that allows to flip left and right between child views.</p>
-  </div>
-</div>
-
-## Others
-
-These components may come in handy for certain applications. For an exhaustive list of components and APIs, check out the sidebar to the left.
-
-<div class="component-grid">
-  <div class="component">
-    <h3><a href="./activityindicator">ActivityIndicator</a></h3>
-    <p>Displays a circular loading indicator.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./alert">Alert</a></h3>
-    <p>Launches an alert dialog with the specified title and message.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./animated">Animated</a></h3>
-    <p>A library for creating fluid, powerful animations that are easy to build and maintain.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./clipboard">Clipboard</a></h3>
-    <p>Provides an interface for setting and getting content from the clipboard on both iOS and Android.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./dimensions">Dimensions</a></h3>
-    <p>Provides an interface for getting device dimensions.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./keyboardavoidingview">KeyboardAvoidingView</a></h3>
-    <p>Provides a view that moves out of the way of the virtual keyboard automatically.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./linking">Linking</a></h3>
-    <p>Provides a general interface to interact with both incoming and outgoing app links.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./modal">Modal</a></h3>
-    <p>Provides a simple way to present content above an enclosing view.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./pixelratio">PixelRatio</a></h3>
-    <p>Provides access to the device pixel density.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./refreshcontrol">RefreshControl</a></h3>
-    <p>This component is used inside a <code>ScrollView</code> to add pull to refresh functionality.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./statusbar">StatusBar</a></h3>
-    <p>Component to control the app status bar.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./webview">WebView</a></h3>
-    <p>A component that renders web content in a native view.</p>
-  </div>
-</div>
diff --git a/website/versioned_docs/version-0.60/debugging.md b/website/versioned_docs/version-0.60/debugging.md
deleted file mode 100644
index 8e88dc372ab..00000000000
--- a/website/versioned_docs/version-0.60/debugging.md
+++ /dev/null
@@ -1,182 +0,0 @@
----
-id: version-0.60-debugging
-title: Debugging
-original_id: debugging
----
-
-## Enabling Keyboard Shortcuts
-
-React Native supports a few keyboard shortcuts in the iOS Simulator. They are described below. To enable them, open the Hardware menu, select Keyboard, and make sure that "Connect Hardware Keyboard" is checked.
-
-## Accessing the In-App Developer Menu
-
-You can access the developer menu by shaking your device or by selecting "Shake Gesture" inside the Hardware menu in the iOS Simulator. You can also use the `⌘D` keyboard shortcut when your app is running in the iOS Simulator, or `⌘M` when running in an Android emulator on Mac OS and `Ctrl+M` on Windows and Linux. Alternatively for Android, you can run the command `adb shell input keyevent 82` to open the dev menu (82 being the Menu key code).
-
-![](/react-native/docs/assets/DeveloperMenu.png)
-
-> The Developer Menu is disabled in release (production) builds.
-
-## Reloading JavaScript
-
-Instead of recompiling your app every time you make a change, you can reload your app's JavaScript code instantly. To do so, select "Reload" from the Developer Menu. You can also press `⌘R` in the iOS Simulator, or tap `R` twice on Android emulators.
-
-### Automatic reloading
-
-You can speed up your development times by having your app reload automatically any time your code changes. Automatic reloading can be enabled by selecting "Enable Live Reload" from the Developer Menu.
-
-You may even go a step further and keep your app running as new versions of your files are injected into the JavaScript bundle automatically by enabling [Hot Reloading](https://facebook.github.io/react-native/blog/2016/03/24/introducing-hot-reloading) from the Developer Menu. This will allow you to persist the app's state through reloads.
-
-> There are some instances where hot reloading cannot be implemented perfectly. If you run into any issues, use a full reload to reset your app.
-
-You will need to rebuild your app for changes to take effect in certain situations:
-
-- You have added new resources to your native app's bundle, such as an image in `Images.xcassets` on iOS or the `res/drawable` folder on Android.
-- You have modified native code (Objective-C/Swift on iOS or Java/C++ on Android).
-
-## In-app Errors and Warnings
-
-Errors and warnings are displayed inside your app in development builds.
-
-### Errors
-
-In-app errors are displayed in a full screen alert with a red background inside your app. This screen is known as a RedBox. You can use `console.error()` to manually trigger one.
-
-### Warnings
-
-Warnings will be displayed on screen with a yellow background. These alerts are known as YellowBoxes. Click on the alerts to show more information or to dismiss them.
-
-As with a RedBox, you can use `console.warn()` to trigger a YellowBox.
-
-YellowBoxes can be disabled during development by using `console.disableYellowBox = true;`. Specific warnings can be ignored programmatically by setting an array of prefixes that should be ignored:
-
-```jsx
-import {YellowBox} from 'react-native';
-YellowBox.ignoreWarnings(['Warning: ...']);
-```
-
-In CI/Xcode, YellowBoxes can also be disabled by setting the `IS_TESTING` environment variable.
-
-> RedBoxes and YellowBoxes are automatically disabled in release (production) builds.
-
-## Chrome Developer Tools
-
-To debug the JavaScript code in Chrome, select "Debug JS Remotely" from the Developer Menu. This will open a new tab at [http://localhost:8081/debugger-ui](http://localhost:8081/debugger-ui).
-
-Select `Tools → Developer Tools` from the Chrome Menu to open the [Developer Tools](https://developer.chrome.com/devtools). You may also access the DevTools using keyboard shortcuts (`⌘⌥I` on macOS, `Ctrl` `Shift` `I` on Windows). You may also want to enable [Pause On Caught Exceptions](http://stackoverflow.com/questions/2233339/javascript-is-there-a-way-to-get-chrome-to-break-on-all-errors/17324511#17324511) for a better debugging experience.
-
-> Note: the React Developer Tools Chrome extension does not work with React Native, but you can use its standalone version instead. Read [this section](debugging.md#react-developer-tools) to learn how.
-
-### Debugging using a custom JavaScript debugger
-
-To use a custom JavaScript debugger in place of Chrome Developer Tools, set the `REACT_DEBUGGER` environment variable to a command that will start your custom debugger. You can then select "Debug JS Remotely" from the Developer Menu to start debugging.
-
-The debugger will receive a list of all project roots, separated by a space. For example, if you set `REACT_DEBUGGER="node /path/to/launchDebugger.js --port 2345 --type ReactNative"`, then the command `node /path/to/launchDebugger.js --port 2345 --type ReactNative /path/to/reactNative/app` will be used to start your debugger.
-
-> Custom debugger commands executed this way should be short-lived processes, and they shouldn't produce more than 200 kilobytes of output.
-
-## Safari Developer Tools
-
-You can use Safari to debug the iOS version of your app without having to enable "Debug JS Remotely".
-
-- Enable Develop menu in Safari: `Preferences → Advanced → Select "Show Develop menu in menu bar"`
-- Select your app's JSContext: `Develop → Simulator → JSContext`
-- Safari's Web Inspector should open which has a Console and a Debugger
-
-However, there are some disadvantages:
-
-1. No sourcemaps when debugging
-2. Every time the app is reloaded (using live reload, or by manually reloading), a new JSContext is created. Choosing "Automatically Show Web Inspectors for JSContexts" saves you from having to select the latest JSContext manually.
-
-## React Developer Tools
-
-You can use [the standalone version of React Developer Tools](https://github.com/facebook/react/tree/master/packages/react-devtools) to debug the React component hierarchy. To use it, install the `react-devtools` package globally:
-
-```
-npm install -g react-devtools
-```
-
-Now run `react-devtools` from the terminal to launch the standalone DevTools app:
-
-```
-react-devtools
-```
-
-![React DevTools](/react-native/docs/assets/ReactDevTools.png)
-
-It should connect to your simulator within a few seconds.
-
-> Note: if you prefer to avoid global installations, you can add `react-devtools` as a project dependency. Add the `react-devtools` package to your project using `npm install --save-dev react-devtools`, then add `"react-devtools": "react-devtools"` to the `scripts` section in your `package.json`, and then run `npm run react-devtools` from your project folder to open the DevTools.
-
-### Integration with React Native Inspector
-
-Open the in-app developer menu and choose "Toggle Inspector". It will bring up an overlay that lets you tap on any UI element and see information about it:
-
-![React Native Inspector](/react-native/docs/assets/Inspector.gif)
-
-However, when `react-devtools` is running, Inspector will enter a special collapsed mode, and instead use the DevTools as primary UI. In this mode, clicking on something in the simulator will bring up the relevant components in the DevTools:
-
-![React DevTools Inspector Integration](/react-native/docs/assets/ReactDevToolsInspector.gif)
-
-You can choose "Toggle Inspector" in the same menu to exit this mode.
-
-### Inspecting Component Instances
-
-When debugging JavaScript in Chrome, you can inspect the props and state of the React components in the browser console.
-
-First, follow the instructions for debugging in Chrome to open the Chrome console.
-
-Make sure that the dropdown in the top left corner of the Chrome console says `debuggerWorker.js`. **This step is essential.**
-
-Then select a React component in React DevTools. There is a search box at the top that helps you find one by name. As soon as you select it, it will be available as `$r` in the Chrome console, letting you inspect its props, state, and instance properties.
-
-![React DevTools Chrome Console Integration](/react-native/docs/assets/ReactDevToolsDollarR.gif)
-
-## Performance Monitor
-
-You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
-<hr style="margin-top:25px; margin-bottom:25px;"/>
-
-# Debugging in Ejected Apps
-
-<div class="banner-crna-ejected" style="margin-top:25px">
-  <h3>Projects with Native Code Only</h3>
-  <p>
-    The remainder of this guide only applies to projects made with <code>react-native init</code>
-    or to those made with <code>expo init</code> or Create React Native App which have since ejected. For
-    more information about ejecting, please see
-    the <a href="https://github.com/react-community/create-react-native-app/blob/master/EJECTING.md" target="_blank">guide</a> on
-    the Create React Native App repository.
-  </p>
-</div>
-
-## Accessing console logs
-
-You can display the console logs for an iOS or Android app by using the following commands in a terminal while the app is running:
-
-```
-$ react-native log-ios
-$ react-native log-android
-```
-
-You may also access these through `Debug → Open System Log...` in the iOS Simulator or by running `adb logcat *:S ReactNative:V ReactNativeJS:V` in a terminal while an Android app is running on a device or emulator.
-
-> If you're using Create React Native App or Expo CLI, console logs already appear in the same terminal output as the packager.
-
-## Debugging on a device with Chrome Developer Tools
-
-> If you're using Create React Native App or Expo CLI, this is configured for you already.
-
-On iOS devices, open the file [`RCTWebSocketExecutor.m`](https://github.com/facebook/react-native/blob/master/Libraries/WebSocket/RCTWebSocketExecutor.m) and change "localhost" to the IP address of your computer, then select "Debug JS Remotely" from the Developer Menu.
-
-On Android 5.0+ devices connected via USB, you can use the [`adb` command line tool](http://developer.android.com/tools/help/adb.html) to setup port forwarding from the device to your computer:
-
-`adb reverse tcp:8081 tcp:8081`
-
-Alternatively, select "Dev Settings" from the Developer Menu, then update the "Debug server host for device" setting to match the IP address of your computer.
-
-> If you run into any issues, it may be possible that one of your Chrome extensions is interacting in unexpected ways with the debugger. Try disabling all of your extensions and re-enabling them one-by-one until you find the problematic extension.
-
-## Debugging native code
-
-When working with native code, such as when writing native modules, you can launch the app from Android Studio or Xcode and take advantage of the native debugging features (setting up breakpoints, etc.) as you would in case of building a standard native app.
diff --git a/website/versioned_docs/version-0.60/direct-manipulation.md b/website/versioned_docs/version-0.60/direct-manipulation.md
deleted file mode 100644
index 2a519d3e044..00000000000
--- a/website/versioned_docs/version-0.60/direct-manipulation.md
+++ /dev/null
@@ -1,207 +0,0 @@
----
-id: version-0.60-direct-manipulation
-title: Direct Manipulation
-original_id: direct-manipulation
----
-
-It is sometimes necessary to make changes directly to a component without using state/props to trigger a re-render of the entire subtree. When using React in the browser for example, you sometimes need to directly modify a DOM node, and the same is true for views in mobile apps. `setNativeProps` is the React Native equivalent to setting properties directly on a DOM node.
-
-> Use setNativeProps when frequent re-rendering creates a performance bottleneck
->
-> Direct manipulation will not be a tool that you reach for frequently; you will typically only be using it for creating continuous animations to avoid the overhead of rendering the component hierarchy and reconciling many views. `setNativeProps` is imperative and stores state in the native layer (DOM, UIView, etc.) and not within your React components, which makes your code more difficult to reason about. Before you use it, try to solve your problem with `setState` and [shouldComponentUpdate](https://reactjs.org/docs/optimizing-performance.html#shouldcomponentupdate-in-action).
-
-## setNativeProps with TouchableOpacity
-
-[TouchableOpacity](https://github.com/facebook/react-native/blob/master/Libraries/Components/Touchable/TouchableOpacity.js) uses `setNativeProps` internally to update the opacity of its child component:
-
-```jsx
-setOpacityTo(value) {
-  // Redacted: animation related code
-  this.refs[CHILD_REF].setNativeProps({
-    opacity: value
-  });
-},
-```
-
-This allows us to write the following code and know that the child will have its opacity updated in response to taps, without the child having any knowledge of that fact or requiring any changes to its implementation:
-
-```jsx
-<TouchableOpacity onPress={this._handlePress}>
-  <View style={styles.button}>
-    <Text>Press me!</Text>
-  </View>
-</TouchableOpacity>
-```
-
-Let's imagine that `setNativeProps` was not available. One way that we might implement it with that constraint is to store the opacity value in the state, then update that value whenever `onPress` is fired:
-
-```jsx
-constructor(props) {
-  super(props);
-  this.state = { myButtonOpacity: 1, };
-}
-
-render() {
-  return (
-    <TouchableOpacity onPress={() => this.setState({myButtonOpacity: 0.5})}
-                      onPressOut={() => this.setState({myButtonOpacity: 1})}>
-      <View style={[styles.button, {opacity: this.state.myButtonOpacity}]}>
-        <Text>Press me!</Text>
-      </View>
-    </TouchableOpacity>
-  )
-}
-```
-
-This is computationally intensive compared to the original example - React needs to re-render the component hierarchy each time the opacity changes, even though other properties of the view and its children haven't changed. Usually this overhead isn't a concern but when performing continuous animations and responding to gestures, judiciously optimizing your components can improve your animations' fidelity.
-
-If you look at the implementation of `setNativeProps` in [NativeMethodsMixin](https://github.com/facebook/react-native/blob/master/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js) you will notice that it is a wrapper around `RCTUIManager.updateView` - this is the exact same function call that results from re-rendering - see [receiveComponent in ReactNativeBaseComponent](https://github.com/facebook/react-native/blob/fb2ec1ea47c53c2e7b873acb1cb46192ac74274e/Libraries/Renderer/oss/ReactNativeRenderer-prod.js#L5793-L5813).
-
-## Composite components and setNativeProps
-
-Composite components are not backed by a native view, so you cannot call `setNativeProps` on them. Consider this example:
-
-```SnackPlayer name=setNativeProps%20with%20Composite%20Components
-import React from 'react';
-import { Text, TouchableOpacity, View } from 'react-native';
-
-class MyButton extends React.Component {
-  render() {
-    return (
-      <View>
-        <Text>{this.props.label}</Text>
-      </View>
-    )
-  }
-}
-
-export default class App extends React.Component {
-  render() {
-    return (
-      <TouchableOpacity>
-        <MyButton label="Press me!" />
-      </TouchableOpacity>
-    )
-  }
-}
-```
-
-If you run this you will immediately see this error: `Touchable child must either be native or forward setNativeProps to a native component`. This occurs because `MyButton` isn't directly backed by a native view whose opacity should be set. You can think about it like this: if you define a component with `createReactClass` you would not expect to be able to set a style prop on it and have that work - you would need to pass the style prop down to a child, unless you are wrapping a native component. Similarly, we are going to forward `setNativeProps` to a native-backed child component.
-
-#### Forward setNativeProps to a child
-
-All we need to do is provide a `setNativeProps` method on our component that calls `setNativeProps` on the appropriate child with the given arguments.
-
-```SnackPlayer name=Forwarding%20setNativeProps
-import React from 'react';
-import { Text, TouchableOpacity, View } from 'react-native';
-
-class MyButton extends React.Component {
-  setNativeProps = (nativeProps) => {
-    this._root.setNativeProps(nativeProps);
-  }
-
-  render() {
-    return (
-      <View ref={component => this._root = component} {...this.props}>
-        <Text>{this.props.label}</Text>
-      </View>
-    )
-  }
-}
-
-export default class App extends React.Component {
-  render() {
-    return (
-      <TouchableOpacity>
-        <MyButton label="Press me!" />
-      </TouchableOpacity>
-    )
-  }
-}
-```
-
-You can now use `MyButton` inside of `TouchableOpacity`! A sidenote for clarity: we used the [ref callback](https://reactjs.org/docs/refs-and-the-dom.html#adding-a-ref-to-a-dom-element) syntax here, rather than the traditional string-based ref.
-
-You may have noticed that we passed all of the props down to the child view using `{...this.props}`. The reason for this is that `TouchableOpacity` is actually a composite component, and so in addition to depending on `setNativeProps` on its child, it also requires that the child perform touch handling. To do this, it passes on [various props](view.md#onmoveshouldsetresponder) that call back to the `TouchableOpacity` component. `TouchableHighlight`, in contrast, is backed by a native view and only requires that we implement `setNativeProps`.
-
-## setNativeProps to clear TextInput value
-
-Another very common use case of `setNativeProps` is to clear the value of a TextInput. The `controlled` prop of TextInput can sometimes drop characters when the `bufferDelay` is low and the user types very quickly. Some developers prefer to skip this prop entirely and instead use `setNativeProps` to directly manipulate the TextInput value when necessary. For example, the following code demonstrates clearing the input when you tap a button:
-
-```SnackPlayer name=Clear%20text
-import React from 'react';
-import { TextInput, Text, TouchableOpacity, View } from 'react-native';
-
-export default class App extends React.Component {
-  clearText = () => {
-    this._textInput.setNativeProps({text: ''});
-  }
-
-  render() {
-    return (
-      <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
-        <TextInput
-          ref={component => this._textInput = component}
-          style={{height: 50, width: 200, marginHorizontal: 20, borderWidth: 1, borderColor: '#ccc'}}
-        />
-        <TouchableOpacity onPress={this.clearText}>
-          <Text>Clear text</Text>
-        </TouchableOpacity>
-      </View>
-    );
-  }
-}
-```
-
-## Avoiding conflicts with the render function
-
-If you update a property that is also managed by the render function, you might end up with some unpredictable and confusing bugs because anytime the component re-renders and that property changes, whatever value was previously set from `setNativeProps` will be completely ignored and overridden.
-
-## setNativeProps & shouldComponentUpdate
-
-By [intelligently applying `shouldComponentUpdate`](https://reactjs.org/docs/optimizing-performance.html#avoid-reconciliation) you can avoid the unnecessary overhead involved in reconciling unchanged component subtrees, to the point where it may be performant enough to use `setState` instead of `setNativeProps`.
-
-## Other native methods
-
-The methods described here are available on most of the default components provided by React Native. Note, however, that they are _not_ available on composite components that aren't directly backed by a native view. This will generally include most components that you define in your own app.
-
-### measure(callback)
-
-Determines the location on screen, width, and height of the given view and returns the values via an async callback. If successful, the callback will be called with the following arguments:
-
-- x
-- y
-- width
-- height
-- pageX
-- pageY
-
-Note that these measurements are not available until after the rendering has been completed in native. If you need the measurements as soon as possible, consider using the [`onLayout` prop](view.md#onlayout) instead.
-
-### measureInWindow(callback)
-
-Determines the location of the given view in the window and returns the values via an async callback. If the React root view is embedded in another native view, this will give you the absolute coordinates. If successful, the callback will be called with the following arguments:
-
-- x
-- y
-- width
-- height
-
-### measureLayout(relativeToNativeNode, onSuccess, onFail)
-
-Like `measure()`, but measures the view relative to an ancestor, specified as `relativeToNativeNode`. This means that the returned x, y are relative to the origin x, y of the ancestor view.
-
-As always, to obtain a native node handle for a component, you can use `findNodeHandle(component)`.
-
-```jsx
-import {findNodeHandle} from 'react-native';
-```
-
-### focus()
-
-Requests focus for the given input or view. The exact behavior triggered will depend on the platform and type of view.
-
-### blur()
-
-Removes focus from an input or view. This is the opposite of `focus()`.
diff --git a/website/versioned_docs/version-0.60/flexbox.md b/website/versioned_docs/version-0.60/flexbox.md
deleted file mode 100644
index bf09a6af5b7..00000000000
--- a/website/versioned_docs/version-0.60/flexbox.md
+++ /dev/null
@@ -1,229 +0,0 @@
----
-id: version-0.60-flexbox
-title: Layout with Flexbox
-original_id: flexbox
----
-
-A component can specify the layout of its children using the flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes.
-
-You will normally use a combination of `flexDirection`, `alignItems`, and `justifyContent` to achieve the right layout.
-
-> Flexbox works the same way in React Native as it does in CSS on the web, with a few exceptions. The defaults are different, with `flexDirection` defaulting to `column` instead of `row`, and the `flex` parameter only supporting a single number.
-
-### Flex
-
-[`flex`](https://facebook.github.io/react-native/docs/layout-props#flex) will define how your items are going to **“fill”** over the available space along your main axis. Space will be divided according to each element's flex property.
-
-In the following example the red, yellow and the green views are all children in the container view that has `flex: 1` set. The red view uses `flex: 1` , the yellow view uses `flex: 2` and the green view uses `flex: 3` . **1+2+3 = 6** which means that the red view will get `1/6` of the space, the yellow `2/6` of the space and the green `3/6` of the space.
-
-![Flex](https://cdn-images-1.medium.com/max/800/1*PhCFmO5tYX_sZSyCd4vO3w.png)
-
-#### Flex Direction
-
-[`flexDirection`](https://facebook.github.io/react-native/docs/layout-props#flexdirection) controls the direction in which the children of a node are laid out. This is also referred to as the _main axis_. The cross axis is the axis perpendicular to the main axis, or the axis which the wrapping lines are laid out in.
-
-- `row` Align children from left to right. If wrapping is enabled then the next line will start under the first item on the left of the container.
-
-- `column` (**default value**) Align children from top to bottom. If wrapping is enabled then the next line will start to the left first item on the top of the container.
-
-- `row-reverse` Align children from right to left. If wrapping is enabled then the next line will start under the first item on the right of the container.
-
-- `column-reverse` Align children from bottom to top. If wrapping is enabled then the next line will start to the left first item on the bottom of the container.
-
-LEARN MORE [HERE](https://yogalayout.com/docs/flex-direction)
-
-```SnackPlayer name=Flex%20Direction
-import React, { Component } from 'react';
-import { View } from 'react-native';
-
-export default class FlexDirectionBasics extends Component {
-  render() {
-    return (
-      // Try setting `flexDirection` to `column`.
-      <View style={{flex: 1, flexDirection: 'row'}}>
-        <View style={{width: 50, height: 50, backgroundColor: 'powderblue'}} />
-        <View style={{width: 50, height: 50, backgroundColor: 'skyblue'}} />
-        <View style={{width: 50, height: 50, backgroundColor: 'steelblue'}} />
-      </View>
-    );
-  }
-};
-```
-
-![Flex Direction](https://cdn-images-1.medium.com/max/800/1*rA7IbuUsJWsx6evKAsabVw.png)
-
-### Layout Direction
-
-Layout direction specifies the direction in which children and text in a hierarchy should be laid out. Layout direction also affects what edge `start` and `end` refer to. By default React Native lays out with LTR layout direction. In this mode `start` refers to left and `end` refers to right.
-
-- `LTR` (**default value**) Text and children are laid out from left to right. Margin and padding applied the start of an element are applied on the left side.
-
-- `RTL` Text and children are laid out from right to left. Margin and padding applied the start of an element are applied on the right side.
-
-#### Justify Content
-
-[`justifyContent`](https://facebook.github.io/react-native/docs/layout-props#justifycontent) describes how to align children within the main axis of their container. For example, you can use this property to center a child horizontally within a container with `flexDirection` set to `row` or vertically within a container with `flexDirection` set to `column`.
-
-- `flex-start`(**default value**) Align children of a container to the start of the container's main axis.
-
-- `flex-end` Align children of a container to the end of the container's main axis.
-
-- `center` Align children of a container in the center of the container's main axis.
-
-- `space-between` Evenly space of children across the container's main axis, distributing remaining space between the children.
-
-- `space-around` Evenly space of children across the container's main axis, distributing remaining space around the children. Compared to `space-between` using `space-around` will result in space being distributed to the beginning of the first child and end of the last child.
-
-- `space-evenly` Evenly distributed within the alignment container along the main axis. The spacing between each pair of adjacent items, the main-start edge and the first item, and the main-end edge and the last item, are all exactly the same.
-
-LEARN MORE [HERE](https://yogalayout.com/docs/justify-content)
-
-```SnackPlayer name=Justify%20Content
-import React, { Component } from 'react';
-import { View } from 'react-native';
-
-export default class JustifyContentBasics extends Component {
-  render() {
-    return (
-      // Try setting `justifyContent` to `center`.
-      // Try setting `flexDirection` to `row`.
-      <View style={{
-        flex: 1,
-        flexDirection: 'column',
-        justifyContent: 'space-between',
-      }}>
-        <View style={{width: 50, height: 50, backgroundColor: 'powderblue'}} />
-        <View style={{width: 50, height: 50, backgroundColor: 'skyblue'}} />
-        <View style={{width: 50, height: 50, backgroundColor: 'steelblue'}} />
-      </View>
-    );
-  }
-};
-```
-
-![Justify Content](https://cdn-images-1.medium.com/max/800/1*i5TVlme-TisAVvD5ax2yPA.png)
-
-#### Align Items
-
-[`alignItems`](https://facebook.github.io/react-native/docs/layout-props#alignitems) describes how to align children along the cross axis of their container. Align items is very similar to `justifyContent` but instead of applying to the main axis, `alignItems` applies to the cross axis.
-
-- `stretch` (**default value**) Stretch children of a container to match the `height` of the container's cross axis.
-
-- `flex-start` Align children of a container to the start of the container's cross axis.
-
-- `flex-end` Align children of a container to the end of the container's cross axis.
-
-- `center` Align children of a container in the center of the container's cross axis.
-
-- `baseline` Align children of a container along a common baseline. Individual children can be set to be the reference baseline for their parents.
-
-> For `stretch` to have an effect, children must not have a fixed dimension along the secondary axis. In the following example, setting `alignItems: stretch` does nothing until the `width: 50` is removed from the children.
-
-LEARN MORE [HERE](https://yogalayout.com/docs/align-items)
-
-```SnackPlayer name=Align%20Items
-import React, { Component } from 'react';
-import { View } from 'react-native';
-
-export default class AlignItemsBasics extends Component {
-  render() {
-    return (
-      // Try setting `alignItems` to 'flex-start'
-      // Try setting `justifyContent` to `flex-end`.
-      // Try setting `flexDirection` to `row`.
-      <View style={{
-        flex: 1,
-        flexDirection: 'column',
-        justifyContent: 'center',
-        alignItems: 'stretch',
-      }}>
-        <View style={{width: 50, height: 50, backgroundColor: 'powderblue'}} />
-        <View style={{height: 50, backgroundColor: 'skyblue'}} />
-        <View style={{height: 100, backgroundColor: 'steelblue'}} />
-      </View>
-    );
-  }
-};
-```
-
-![Align Items](https://cdn-images-1.medium.com/max/800/1*evkM7zfxt-9p-HJ1M0Bh2g.png)
-
-### Align Self
-
-[`alignSelf`](https://facebook.github.io/react-native/docs/layout-props#alignself) has the same options and effect as `alignItems` but instead of affecting the children within a container, you can apply this property to a single child to change its alignment within its parent. `alignSelf` overrides any option set by the parent with `alignItems`.
-
-![Align Self](https://cdn-images-1.medium.com/max/800/1*J1JCoKwLCokX9JXVBvP71g.png)
-
-### Align Content
-
-[alignContent](https://facebook.github.io/react-native/docs/layout-props#aligncontent) defines the distribution of lines along the cross-axis. This only has effect when items are wrapped to multiple lines using `flexWrap`.
-
-- `flex-start` (**default value**) Align wrapped lines to the start of the container's cross axis.
-
-- `flex-end` Align wrapped lines to the end of the container's cross axis.
-
-- `stretch` wrapped lines to match the height of the container's cross axis.
-
-- `center` Align wrapped lines in the center of the container's cross axis.
-
-- `space-between` Evenly space wrapped lines across the container's main axis, distributing remaining space between the lines.
-
-- `space-around` Evenly space wrapped lines across the container's main axis, distributing remaining space around the lines. Compared to space between using space around will result in space being distributed to the begining of the first lines and end of the last line.
-
-LEARN MORE [HERE](https://yogalayout.com/docs/align-content)
-
-![Align Content](https://cdn-images-1.medium.com/max/800/1*cC2XFyCF_igp20Ombt4wBw.png)
-
-### Flex Wrap
-
-The [`flexWrap`](https://facebook.github.io/react-native/docs/layout-props#flexwrap) property is set on containers and controls what happens when children overflow the size of the container along the main axis. By default children are forced into a single line (which can shrink elements). If wrapping is allowed items are wrapped into multiple lines along the main axis if needed.
-
-When wrapping lines `alignContent` can be used to specify how the lines are placed in the container. learn more [here](https://yogalayout.com/docs/flex-wrap)
-
-![Flex Wrap](https://cdn-images-1.medium.com/max/800/1*_7v4uQhSsuCn1cfeOMVfrA.png)
-
-### Flex Basis, Grow, and Shrink
-
-- [`flexGrow`](https://facebook.github.io/react-native/docs/layout-props#flexgrow) describes how any space within a container should be distributed among its children along the main axis. After laying out its children, a container will distribute any remaining space according to the flex grow values specified by its children.
-
-  flexGrow accepts any floating point value >= 0, with 0 being the default value. A container will distribute any remaining space among its children weighted by the child’s flex grow value.
-
-- [`flexShrink`](https://facebook.github.io/react-native/docs/layout-props#flexshrink) describes how to shrink children along the main axis in the case that the total size of the children overflow the size of the container on the main axis. Flex shrink is very similar to flex grow and can be thought of in the same way if any overflowing size is considered to be negative remaining space. These two properties also work well together by allowing children to grow and shrink as needed.
-
-  Flex shrink accepts any floating point value >= 0, with 1 being the default value. A container will shrink its children weighted by the child’s flex shrink value.
-
-- [`flexBasis`](https://facebook.github.io/react-native/docs/layout-props#flexbasis) is an axis-independent way of providing the default size of an item along the main axis. Setting the flex basis of a child is similar to setting the `width` of that child if its parent is a container with `flexDirection: row` or setting the `height` of a child if its parent is a container with `flexDirection: column`. The flex basis of an item is the default size of that item, the size of the item before any flex grow and flex shrink calculations are performed.
-
-LEARN MORE [HERE](https://yogalayout.com/docs/flex)
-
-### Width and Height
-
-The `width` property in Yoga specifies the width of the element's content area. Similarly height property specifies the `height` of the element's content area.
-
-Both `width` and `height` can take following values:
-
-- `auto` Is the **default Value**, React Native calculates the width/height for the element based on its content, whether that is other children, text, or an image.
-
-- `pixels` Defines the width/height in absolute pixels. Depending on other styles set on the component, this may or may not be the final dimension of the node.
-
-- `percentage` Defines the width or height in percentage of its parent's width or height respectively.
-
-### Absolute & Relative Layout
-
-The `position` type of an element defines how it is positioned within its parent.
-
-`relative` (**default value**) By default an element is positioned relatively. This means an element is positioned according to the normal flow of the layout, and then offset relative to that position based on the values of `top`, `right`, `bottom`, and `left`. The offset does not affect the position of any sibling or parent elements.
-
-`absolute` When positioned absolutely an element doesn't take part in the normal layout flow. It is instead laid out independent of its siblings. The position is determined based on the `top`, `right`, `bottom`, and `left` values.
-
-![Absolute & Relative Layoutp](https://cdn-images-1.medium.com/max/800/1*NlPeRQCQK3Vb5nyjL0Mqxw.png)
-
-#### Going Deeper
-
-Check out the interactive [yoga playground](https://yogalayout.com/playground) that you can use to get a better understanding of flexbox.
-
-We've covered the basics, but there are many other styles you may need for layouts. The full list of props that control layout is documented [here](./layout-props.md).
-
-We're getting close to being able to build a real application. One thing we are still missing is a way to take user input, so let's move on to [learn how to handle text input with the TextInput component](handling-text-input.md).
-
-See some examples from [Wix Engineers](https://medium.com/wix-engineering/the-full-react-native-layout-cheat-sheet-a4147802405c):
diff --git a/website/versioned_docs/version-0.60/getting-started.md b/website/versioned_docs/version-0.60/getting-started.md
deleted file mode 100644
index 958b6cb4c3b..00000000000
--- a/website/versioned_docs/version-0.60/getting-started.md
+++ /dev/null
@@ -1,560 +0,0 @@
----
-id: version-0.60-getting-started
-title: Getting Started
-original_id: getting-started
----
-
-This page will help you install and build your first React Native app. If you already have React Native installed, you can skip ahead to the [Tutorial](tutorial.md).
-
-<strong>If you are new to mobile development</strong>, the easiest way to get started is with Expo CLI. Expo is a set of tools built around React Native and, while it has many [features](https://expo.io/features), the most relevant feature for us right now is that it can get you writing a React Native app within minutes. You will only need a recent version of Node.js and a phone or emulator. If you'd like to try out React Native directly in your web browser before installing any tools, you can try out [Snack](https://snack.expo.io/).
-
-<strong>If you are already familiar with mobile development</strong>, you may want to use React Native CLI. It requires Xcode or Android Studio to get started. If you already have one of these tools installed, you should be able to get up and running within a few minutes. If they are not installed, you should expect to spend about an hour installing and configuring them.
-
-<div class="toggler">
-  <ul role="tablist" id="toggle-guide">
-    <li id="quickstart" class="button-quickstart" aria-selected="false" role="tab" tabindex="0" aria-controls="quickstarttab" onclick="displayTab('guide', 'quickstart')">
-      Expo CLI Quickstart
-    </li>
-    <li id="native" class="button-native" aria-selected="false" role="tab" tabindex="0" aria-controls="nativetab" onclick="displayTab('guide', 'native')">
-      React Native CLI Quickstart
-    </li>
-  </ul>
-</div>
-
-<block class="quickstart mac windows linux ios android" />
-
-Assuming that you have [Node 10 LTS](https://nodejs.org/en/download/) or greater installed, you can use npm to install the Expo CLI command line utility:
-
-```sh
-npm install -g expo-cli
-```
-
-Then run the following commands to create a new React Native project called "AwesomeProject":
-
-```sh
-expo init AwesomeProject
-
-cd AwesomeProject
-npm start # you can also use: expo start
-```
-
-This will start a development server for you.
-
-<h2>Running your React Native application</h2>
-
-Install the [Expo](https://expo.io) client app on your iOS or Android phone and connect to the same wireless network as your computer. On Android, use the Expo app to scan the QR code from your terminal to open your project. On iOS, follow on-screen instructions to get a link.
-
-<h3>Modifying your app</h3>
-
-Now that you have successfully run the app, let's modify it. Open `App.js` in your text editor of choice and edit some lines. The application should reload automatically once you save your changes.
-
-<h3>That's it!</h3>
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-<center><img src="/react-native/docs/assets/GettingStartedCongratulations.png" width="150"></img></center>
-
-<h2>Now what?</h3>
-
-Expo also has [docs](https://docs.expo.io) you can reference if you have questions specific to the tool. You can also ask for help at [Expo forums](https://forums.expo.io).
-
-These tools help you get started quickly, but before committing to building your app with Expo CLI, [read about the limitations](https://docs.expo.io/versions/latest/introduction/why-not-expo/).
-
-If you have a problem with Expo, before creating a new issue, please see if there's an existing issue about it:
-
-- in the [Expo CLI issues](https://github.com/expo/expo-cli/issues) (for issues related to Expo CLI), or
-- in the [Expo issues](https://github.com/expo/expo/issues) (for issues about the Expo client or SDK).
-
-If you're curious to learn more about React Native, continue on to the [Tutorial](tutorial.md).
-
-<h3>Running your app on a simulator or virtual device</h3>
-
-Expo CLI makes it really easy to run your React Native app on a physical device without setting up a development environment. If you want to run your app on the iOS Simulator or an Android Virtual Device, please refer to the instructions for "React Native CLI Quickstart" to learn how to install Xcode or set up your Android development environment.
-
-Once you've set these up, you can launch your app on an Android Virtual Device by running `npm run android`, or on the iOS Simulator by running `npm run ios` (macOS only).
-
-<h3>Caveats</h3>
-
-Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
-If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "[eject](https://docs.expo.io/versions/latest/expokit/eject)" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
-Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check [this document](https://docs.expo.io/versions/latest/sdk/#sdk-version) to find out what versions are supported.
-
-If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
-
-<block class="native mac windows linux ios android" />
-
-<p>Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from <a href="getting-started" onclick="displayTab('guide', 'quickstart')">Expo</a>, you'll need this section.</p>
-
-The instructions are a bit different depending on your development operating system, and whether you want to start developing for iOS or Android. If you want to develop for both iOS and Android, that's fine - you just have to pick one to start with, since the setup is a bit different.
-
-<div class="toggler">
-  <span>Development OS:</span>
-  <span role="tablist" id="toggle-os">
-    <button role="tab" class="button-mac" onclick="displayTab('os', 'mac')">macOS</a>
-    <button role="tab" class="button-windows" onclick="displayTab('os', 'windows')">Windows</a>
-    <button role="tab" class="button-linux" onclick="displayTab('os', 'linux')">Linux</a>
-  </span>
-</div>
-
-<div class="toggler">
-  <span>Target OS:</span>
-  <span role="tablist" id="toggle-platform">
-    <button role="tab" class="button-ios" onclick="displayTab('platform', 'ios')">iOS</a>
-    <button role="tab" class="button-android" onclick="displayTab('platform', 'android')">Android</a>
-  </span>
-</div>
-
-<block class="native linux windows ios" />
-
-<h2>Unsupported</h2>
-
-<blockquote><p>A Mac is required to build projects with native code for iOS. You can follow the <a href="getting-started" onclick="displayTab('guide', 'quickstart')">Quick Start</a> to learn how to build your app using Expo instead.</p></blockquote>
-
-<block class="native mac ios" />
-
-<h2>Installing dependencies</h2>
-
-You will need Node, Watchman, the React Native command line interface, and Xcode.
-
-While you can use any editor of your choice to develop your app, you will need to install Xcode in order to set up the necessary tooling to build your React Native app for iOS.
-
-<block class="native mac android" />
-
-<h2>Installing dependencies</h2>
-
-You will need Node, Watchman, the React Native command line interface, a JDK, and Android Studio.
-
-<block class="native linux android" />
-
-<h2>Installing dependencies</h2>
-
-You will need Node, the React Native command line interface, a JDK, and Android Studio.
-
-<block class="native windows android" />
-
-<h2>Installing dependencies</h2>
-
-You will need Node, the React Native command line interface, Python2, a JDK, and Android Studio.
-
-<block class="native mac windows linux android" />
-
-While you can use any editor of your choice to develop your app, you will need to install Android Studio in order to set up the necessary tooling to build your React Native app for Android.
-
-<block class="native mac ios android" />
-
-<h3>Node, Watchman, JDK</h3>
-
-We recommend installing Node, Watchman, and JDK using [Homebrew](http://brew.sh/). Run the following commands in a Terminal after installing Homebrew:
-
-```
-brew install yarn
-brew install node
-brew install watchman
-brew tap AdoptOpenJDK/openjdk
-brew cask install adoptopenjdk8
-```
-
-If you have already installed Node on your system, make sure it is Node 8.3 or newer.
-
-[Watchman](https://facebook.github.io/watchman) is a tool by Facebook for watching changes in the filesystem. It is highly recommended you install it for better performance.
-
-If you have already installed JDK on your system, make sure it is JDK 8 or newer.
-
-<block class="native linux android" />
-
-<h3>Node</h3>
-
-Follow the [installation instructions for your Linux distribution](https://nodejs.org/en/download/package-manager/) to install Node 8.3 or newer.
-
-<block class='native windows android' />
-
-<h3>Node, Python2, JDK</h3>
-
-We recommend installing Node and Python2 via [Chocolatey](https://chocolatey.org), a popular package manager for Windows.
-
-React Native also requires a recent version of the [Java SE Development Kit (JDK)](http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html), as well as Python 2. Both can be installed using Chocolatey.
-
-Open an Administrator Command Prompt (right click Command Prompt and select "Run as Administrator"), then run the following command:
-
-```powershell
-choco install -y nodejs.install python2 jdk8
-```
-
-If you have already installed Node on your system, make sure it is Node 8.3 or newer. If you already have a JDK on your system, make sure it is version 8 or newer.
-
-> You can find additional installation options on [Node's Downloads page](https://nodejs.org/en/download/).
-
-<block class="native mac ios android" />
-
-<h3>The React Native CLI</h3>
-
-Node comes with npm, which lets you install the React Native command line interface.
-
-Run the following command in a Terminal:
-
-```
-npm install -g react-native-cli
-```
-
-> If you get an error like `Cannot find module 'npmlog'`, try installing npm directly: `curl -0 -L https://npmjs.org/install.sh | sudo sh`.
-
-<block class="native windows linux android" />
-
-<h3>The React Native CLI</h3>
-
-Node comes with npm, which lets you install the React Native command line interface.
-
-Run the following command in a Command Prompt or shell:
-
-```powershell
-npm install -g react-native-cli
-```
-
-> If you get an error like `Cannot find module 'npmlog'`, try installing npm directly: `curl -0 -L https://npmjs.org/install.sh | sudo sh`.
-
-<block class="native mac ios" />
-
-<h3>Xcode</h3>
-
-The easiest way to install Xcode is via the [Mac App Store](https://itunes.apple.com/us/app/xcode/id497799835?mt=12). Installing Xcode will also install the iOS Simulator and all the necessary tools to build your iOS app.
-
-If you have already installed Xcode on your system, make sure it is version 9.4 or newer.
-
-<h4>Command Line Tools<h4>
-
-You will also need to install the Xcode Command Line Tools. Open Xcode, then choose "Preferences..." from the Xcode menu. Go to the Locations panel and install the tools by selecting the most recent version in the Command Line Tools dropdown.
-
-![Xcode Command Line Tools](/react-native/docs/assets/GettingStartedXcodeCommandLineTools.png)
-
-<block class="native linux android" />
-
-<h3>Java Development Kit</h3>
-
-React Native requires version 8 of the Java SE Development Kit (JDK). You may download and install [OpenJDK](http://openjdk.java.net) from [AdoptOpenJDK](https://adoptopenjdk.net/) or your system packager. You may also [Download and install Oracle JDK 8](http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html) if desired.
-
-<block class="native mac linux windows android" />
-
-<h3>Android development environment</h3>
-
-Setting up your development environment can be somewhat tedious if you're new to Android development. If you're already familiar with Android development, there are a few things you may need to configure. In either case, please make sure to carefully follow the next few steps.
-
-<block class="native mac windows linux android" />
-
-<h4>1. Install Android Studio</h4>
-
-[Download and install Android Studio](https://developer.android.com/studio/index.html). Choose a "Custom" setup when prompted to select an installation type. Make sure the boxes next to all of the following are checked:
-
-<block class="native mac windows android" />
-
-- `Android SDK`
-- `Android SDK Platform`
-- `Performance (Intel ® HAXM)` ([See here for AMD](https://android-developers.googleblog.com/2018/07/android-emulator-amd-processor-hyper-v.html))
-- `Android Virtual Device`
-
-<block class="native linux android" />
-
-- `Android SDK`
-- `Android SDK Platform`
-- `Android Virtual Device`
-
-<block class="native mac windows linux android" />
-
-Then, click "Next" to install all of these components.
-
-> If the checkboxes are grayed out, you will have a chance to install these components later on.
-
-Once setup has finalized and you're presented with the Welcome screen, proceed to the next step.
-
-<h4>2. Install the Android SDK</h4>
-
-Android Studio installs the latest Android SDK by default. Building a React Native app with native code, however, requires the `Android 9 (Pie)` SDK in particular. Additional Android SDKs can be installed through the SDK Manager in Android Studio.
-
-The SDK Manager can be accessed from the "Welcome to Android Studio" screen. Click on "Configure", then select "SDK Manager".
-
-<block class="native mac android" />
-
-![Android Studio Welcome](/react-native/docs/assets/GettingStartedAndroidStudioWelcomeMacOS.png)
-
-<block class="native windows android" />
-
-![Android Studio Welcome](/react-native/docs/assets/GettingStartedAndroidStudioWelcomeWindows.png)
-
-<block class="native mac windows linux android" />
-
-> The SDK Manager can also be found within the Android Studio "Preferences" dialog, under **Appearance & Behavior** → **System Settings** → **Android SDK**.
-
-Select the "SDK Platforms" tab from within the SDK Manager, then check the box next to "Show Package Details" in the bottom right corner. Look for and expand the `Android 9 (Pie)` entry, then make sure the following items are checked:
-
-- `Android SDK Platform 28`
-- `Intel x86 Atom_64 System Image` or `Google APIs Intel x86 Atom System Image`
-
-Next, select the "SDK Tools" tab and check the box next to "Show Package Details" here as well. Look for and expand the "Android SDK Build-Tools" entry, then make sure that `28.0.3` is selected.
-
-Finally, click "Apply" to download and install the Android SDK and related build tools.
-
-<h4>3. Configure the ANDROID_HOME environment variable</h4>
-
-The React Native tools require some environment variables to be set up in order to build apps with native code.
-
-<block class="native mac linux android" />
-
-Add the following lines to your `$HOME/.bash_profile` or `$HOME/.bashrc` config file:
-
-<block class="native mac android" />
-
-```
-export ANDROID_HOME=$HOME/Library/Android/sdk
-export PATH=$PATH:$ANDROID_HOME/emulator
-export PATH=$PATH:$ANDROID_HOME/tools
-export PATH=$PATH:$ANDROID_HOME/tools/bin
-export PATH=$PATH:$ANDROID_HOME/platform-tools
-```
-
-<block class="native linux android" />
-
-```
-export ANDROID_HOME=$HOME/Android/Sdk
-export PATH=$PATH:$ANDROID_HOME/emulator
-export PATH=$PATH:$ANDROID_HOME/tools
-export PATH=$PATH:$ANDROID_HOME/tools/bin
-export PATH=$PATH:$ANDROID_HOME/platform-tools
-```
-
-<block class="native mac linux android" />
-
-> `.bash_profile` is specific to `bash`. If you're using another shell, you will need to edit the appropriate shell-specific config file.
-
-Type `source $HOME/.bash_profile` to load the config into your current shell. Verify that ANDROID_HOME has been added to your path by running `echo $PATH`.
-
-> Please make sure you use the correct Android SDK path. You can find the actual location of the SDK in the Android Studio "Preferences" dialog, under **Appearance & Behavior** → **System Settings** → **Android SDK**.
-
-<block class="native windows android" />
-
-Open the System pane under **System and Security** in the Windows Control Panel, then click on **Change settings...**. Open the **Advanced** tab and click on **Environment Variables...**. Click on **New...** to create a new `ANDROID_HOME` user variable that points to the path to your Android SDK:
-
-![ANDROID_HOME Environment Variable](/react-native/docs/assets/GettingStartedAndroidEnvironmentVariableANDROID_HOME.png)
-
-The SDK is installed, by default, at the following location:
-
-```powershell
-c:\Users\YOUR_USERNAME\AppData\Local\Android\Sdk
-```
-
-You can find the actual location of the SDK in the Android Studio "Preferences" dialog, under **Appearance & Behavior** → **System Settings** → **Android SDK**.
-
-Open a new Command Prompt window to ensure the new environment variable is loaded before proceeding to the next step.
-
-<h4>4. Add platform-tools to Path</h4>
-
-Open the System pane under **System and Security** in the Windows Control Panel, then click on **Change settings...**. Open the **Advanced** tab and click on **Environment Variables...**. Select the **Path** variable, then click **Edit**. Click **New** and add the path to platform-tools to the list.
-
-The default location for this folder is:
-
-```powershell
-c:\Users\YOUR_USERNAME\AppData\Local\Android\Sdk\platform-tools
-```
-
-<block class="native linux android" />
-
-<h3>Watchman</h3>
-
-Follow the [Watchman installation guide](https://facebook.github.io/watchman/docs/install.html#buildinstall) to compile and install Watchman from source.
-
-> [Watchman](https://facebook.github.io/watchman/docs/install.html) is a tool by Facebook for watching changes in the filesystem. It is highly recommended you install it for better performance and increased compatibility in certain edge cases (translation: you may be able to get by without installing this, but your mileage may vary; installing this now may save you from a headache later).
-
-<block class="native mac ios" />
-
-<h2>Creating a new application</h2>
-
-Use the React Native command line interface to generate a new React Native project called "AwesomeProject":
-
-```
-react-native init AwesomeProject
-```
-
-This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Expo (or Create React Native App), or if you're adding iOS support to an existing React Native project (see [Platform Specific Code](platform-specific-code.md)). You can also use a third-party CLI to init your React Native app, such as [Ignite CLI](https://github.com/infinitered/ignite).
-
-<h3>[Optional] Using a specific version</h3>
-
-If you want to start a new project with a specific React Native version, you can use the `--version` argument:
-
-```
-react-native init AwesomeProject --version X.XX.X
-```
-
-```
-react-native init AwesomeProject --version react-native@next
-```
-
-<block class="native mac windows linux android" />
-
-<h2>Creating a new application</h2>
-
-Use the React Native command line interface to generate a new React Native project called "AwesomeProject":
-
-```
-react-native init AwesomeProject
-```
-
-This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Create React Native App, or if you're adding Android support to an existing React Native project (see [Platform Specific Code](platform-specific-code.md)). You can also use a third-party CLI to init your React Native app, such as [Ignite CLI](https://github.com/infinitered/ignite).
-
-<h3>[Optional] Using a specific version</h3>
-
-If you want to start a new project with a specific React Native version, you can use the `--version` argument:
-
-```
-react-native init AwesomeProject --version X.XX.X
-```
-
-```
-react-native init AwesomeProject --version react-native@next
-```
-
-<block class="native mac windows linux android" />
-
-<h2>Preparing the Android device</h2>
-
-You will need an Android device to run your React Native Android app. This can be either a physical Android device, or more commonly, you can use an Android Virtual Device which allows you to emulate an Android device on your computer.
-
-Either way, you will need to prepare the device to run Android apps for development.
-
-<h3>Using a physical device</h3>
-
-If you have a physical Android device, you can use it for development in place of an AVD by plugging it in to your computer using a USB cable and following the instructions [here](running-on-device.md).
-
-<h3>Using a virtual device</h3>
-
-If you use Android Studio to open `./AwesomeProject/android`, you can see the list of available Android Virtual Devices (AVDs) by opening the "AVD Manager" from within Android Studio. Look for an icon that looks like this:
-
-![Android Studio AVD Manager](/react-native/docs/assets/GettingStartedAndroidStudioAVD.png)
-
-If you have just installed Android Studio, you will likely need to [create a new AVD](https://developer.android.com/studio/run/managing-avds.html). Select "Create Virtual Device...", then pick any Phone from the list and click "Next", then select the **Pie** API Level 28 image.
-
-<block class="native linux android" />
-
-> We recommend configuring [VM acceleration](https://developer.android.com/studio/run/emulator-acceleration.html#vm-linux) on your system to improve performance. Once you've followed those instructions, go back to the AVD Manager.
-
-<block class="native windows android" />
-
-> If you don't have HAXM installed, click on "Install HAXM" or follow [these instructions](https://github.com/intel/haxm/wiki/Installation-Instructions-on-Windows) to set it up, then go back to the AVD Manager.
-
-<block class="native mac android" />
-
-> If you don't have HAXM installed, follow [these instructions](https://github.com/intel/haxm/wiki/Installation-Instructions-on-macOS) to set it up, then go back to the AVD Manager.
-
-<block class="native mac windows linux android" />
-
-Click "Next" then "Finish" to create your AVD. At this point you should be able to click on the green triangle button next to your AVD to launch it, then proceed to the next step.
-
-<block class="native mac ios" />
-
-<h2>Running your React Native application</h2>
-
-Run `react-native run-ios` inside your React Native project folder:
-
-```
-cd AwesomeProject
-react-native run-ios
-```
-
-You should see your new app running in the iOS Simulator shortly.
-
-![AwesomeProject on iOS](/react-native/docs/assets/GettingStartediOSSuccess.png)
-
-`react-native run-ios` is just one way to run your app. You can also run it directly from within Xcode.
-
-> If you can't get this to work, see the [Troubleshooting](troubleshooting.md#content) page.
-
-<h3>Running on a device</h3>
-
-The above command will automatically run your app on the iOS Simulator by default. If you want to run the app on an actual physical iOS device, please follow the instructions [here](running-on-device.md).
-
-<block class="native mac windows linux android" />
-
-<h2>Running your React Native application</h2>
-
-Run `react-native run-android` inside your React Native project folder:
-
-```
-cd AwesomeProject
-react-native run-android
-```
-
-If everything is set up correctly, you should see your new app running in your Android emulator shortly.
-
-<block class="native mac android" />
-
-![AwesomeProject on Android](/react-native/docs/assets/GettingStartedAndroidSuccessMacOS.png)
-
-<block class="native windows android" />
-
-![AwesomeProject on Android](/react-native/docs/assets/GettingStartedAndroidSuccessWindows.png)
-
-<block class="native mac windows linux android" />
-
-`react-native run-android` is just one way to run your app - you can also run it directly from within Android Studio.
-
-> If you can't get this to work, see the [Troubleshooting](troubleshooting.md#content) page.
-
-<block class="native mac ios android" />
-
-<h3>Modifying your app</h3>
-
-Now that you have successfully run the app, let's modify it.
-
-<block class="native mac ios" />
-
-- Open `App.js` in your text editor of choice and edit some lines.
-- Hit `⌘R` in your iOS Simulator to reload the app and see your changes!
-
-<block class="native mac android" />
-
-- Open `App.js` in your text editor of choice and edit some lines.
-- Press the `R` key twice or select `Reload` from the Developer Menu (`⌘M`) to see your changes!
-
-<block class="native windows linux android" />
-
-<h3>Modifying your app</h3>
-
-Now that you have successfully run the app, let's modify it.
-
-- Open `App.js` in your text editor of choice and edit some lines.
-- Press the `R` key twice or select `Reload` from the Developer Menu (`Ctrl + M`) to see your changes!
-
-<block class="native mac ios android" />
-
-<h3>That's it!</h3>
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-<center><img src="/react-native/docs/assets/GettingStartedCongratulations.png" width="150"></img></center>
-
-<block class="native windows linux android" />
-
-<h3>That's it!</h3>
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-<center><img src="/react-native/docs/assets/GettingStartedCongratulations.png" width="150"></img></center>
-
-<block class="native mac ios" />
-
-<h2>Now what?</h2>
-
-- Turn on [Live Reload](debugging.md#reloading-javascript) in the Developer Menu. Your app will now reload automatically whenever you save any changes!
-
-- If you want to add this new React Native code to an existing application, check out the [Integration guide](integration-with-existing-apps.md).
-
-If you're curious to learn more about React Native, continue on to the [Tutorial](tutorial.md).
-
-<block class="native windows linux mac android" />
-
-<h2>Now what?</h2>
-
-- Turn on [Live Reload](debugging.md#reloading-javascript) in the Developer Menu. Your app will now reload automatically whenever you save any changes!
-
-- If you want to add this new React Native code to an existing application, check out the [Integration guide](integration-with-existing-apps.md).
-
-If you're curious to learn more about React Native, continue on to the [Tutorial](tutorial.md).
diff --git a/website/versioned_docs/version-0.60/handling-text-input.md b/website/versioned_docs/version-0.60/handling-text-input.md
deleted file mode 100644
index 3790f2d002e..00000000000
--- a/website/versioned_docs/version-0.60/handling-text-input.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-id: version-0.60-handling-text-input
-title: Handling Text Input
-original_id: handling-text-input
----
-
-[`TextInput`](textinput.md#content) is a basic component that allows the user to enter text. It has an `onChangeText` prop that takes a function to be called every time the text changed, and an `onSubmitEditing` prop that takes a function to be called when the text is submitted.
-
-For example, let's say that as the user types, you're translating their words into a different language. In this new language, every single word is written the same way: 🍕. So the sentence "Hello there Bob" would be translated as "🍕🍕🍕".
-
-```SnackPlayer name=Handling%20Text%20Input
-import React, { Component } from 'react';
-import { Text, TextInput, View } from 'react-native';
-
-export default class PizzaTranslator extends Component {
-  constructor(props) {
-    super(props);
-    this.state = {text: ''};
-  }
-
-  render() {
-    return (
-      <View style={{padding: 10}}>
-        <TextInput
-          style={{height: 40}}
-          placeholder="Type here to translate!"
-          onChangeText={(text) => this.setState({text})}
-          value={this.state.text}
-        />
-        <Text style={{padding: 10, fontSize: 42}}>
-          {this.state.text.split(' ').map((word) => word && '🍕').join(' ')}
-        </Text>
-      </View>
-    );
-  }
-}
-```
-
-In this example, we store `text` in the state, because it changes over time.
-
-There are a lot more things you might want to do with a text input. For example, you could validate the text inside while the user types. For more detailed examples, see the [React docs on controlled components](https://reactjs.org/docs/forms.html#controlled-components), or the [reference docs for TextInput](textinput.md).
-
-Text input is one of the ways the user interacts with the app. Next, let's look at another type of input and [learn how to handle touches](handling-touches.md).
diff --git a/website/versioned_docs/version-0.60/headless-js-android.md b/website/versioned_docs/version-0.60/headless-js-android.md
deleted file mode 100644
index 66b5abf1081..00000000000
--- a/website/versioned_docs/version-0.60/headless-js-android.md
+++ /dev/null
@@ -1,185 +0,0 @@
----
-id: version-0.60-headless-js-android
-title: Headless JS
-original_id: headless-js-android
----
-
-Headless JS is a way to run tasks in JavaScript while your app is in the background. It can be used, for example, to sync fresh data, handle push notifications, or play music.
-
-## The JS API
-
-A task is a simple async function that you register on `AppRegistry`, similar to registering React applications:
-
-```jsx
-AppRegistry.registerHeadlessTask('SomeTaskName', () => require('SomeTaskName'));
-```
-
-Then, in `SomeTaskName.js`:
-
-```jsx
-module.exports = async (taskData) => {
-  // do stuff
-};
-```
-
-You can do anything in your task such as network requests, timers and so on, as long as it doesn't touch UI. Once your task completes (i.e. the promise is resolved), React Native will go into "paused" mode (unless there are other tasks running, or there is a foreground app).
-
-## The Java API
-
-Yes, this does still require some native code, but it's pretty thin. You need to extend `HeadlessJsTaskService` and override `getTaskConfig`, e.g.:
-
-```java
-public class MyTaskService extends HeadlessJsTaskService {
-
-  @Override
-  protected @Nullable HeadlessJsTaskConfig getTaskConfig(Intent intent) {
-    Bundle extras = intent.getExtras();
-    if (extras != null) {
-      return new HeadlessJsTaskConfig(
-          "SomeTaskName",
-          Arguments.fromBundle(extras),
-          5000, // timeout for the task
-          false // optional: defines whether or not  the task is allowed in foreground. Default is false
-        );
-    }
-    return null;
-  }
-}
-```
-
-Then add the service to your `AndroidManifest.xml` file:
-
-```
-<service android:name="com.example.MyTaskService" />
-```
-
-Now, whenever you [start your service][0], e.g. as a periodic task or in response to some system event / broadcast, JS will spin up, run your task, then spin down.
-
-Example:
-
-```java
-Intent service = new Intent(getApplicationContext(), MyTaskService.class);
-Bundle bundle = new Bundle();
-
-bundle.putString("foo", "bar");
-service.putExtras(bundle);
-
-getApplicationContext().startService(service);
-```
-
-## Retries
-
-By default, the headless JS task will not perform any retries. In order to do so, you need to create a `HeadlessJsRetryPolicy` and throw a specfic `Error`.
-
-`LinearCountingRetryPolicy` is an implementation of `HeadlessJsRetryPolicy` that allows you to specify a maximum number of retries with a fixed delay between each attempt. If that does not suit your needs then you can easily implement your own `HeadlessJsRetryPolicy`. These policies can simply be passed as an extra argument to the `HeadlessJsTaskConfig` constructor, e.g.
-
-```java
-HeadlessJsRetryPolicy retryPolicy = new LinearCountingRetryPolicy(
-  3, // Max number of retry attempts
-  1000 // Delay between each retry attempt
-);
-
-return new HeadlessJsTaskConfig(
-  'SomeTaskName',
-  Arguments.fromBundle(extras),
-  5000,
-  false,
-  retryPolicy
-);
-```
-
-A retry attempt will only be made when a specific `Error` is thrown. Inside a headless JS task, you can import the error and throw it when a retry attempt is required.
-
-Example:
-
-```jsx
-import {HeadlessJsTaskError} from 'HeadlessJsTask';
-
-module.exports = async (taskData) => {
-  const condition = ...;
-  if (!condition) {
-    throw new HeadlessJsTaskError();
-  }
-};
-```
-
-If you wish all errors to cause a retry attempt, you will need to catch them and throw the above error.
-
-## Caveats
-
-- The function passed to `setTimeout` does not always behave as expected. Instead the function is called only when the application is launched again. If you just need to wait, use the retry functionality.
-- By default, your app will crash if you try to run a task while the app is in the foreground. This is to prevent developers from shooting themselves in the foot by doing a lot of work in a task and slowing the UI. You can pass a fourth `boolean` argument to control this behaviour.
-- If you start your service from a `BroadcastReceiver`, make sure to call `HeadlessJsTaskService.acquireWakeLockNow()` before returning from `onReceive()`.
-
-## Example Usage
-
-Service can be started from Java API. First you need to decide when the service should be started and implement your solution accordingly. Here is a simple example that reacts to network connection change.
-
-Following lines shows part of Android manifest file for registering broadcast receiver.
-
-```xml
-<receiver android:name=".NetworkChangeReceiver" >
-  <intent-filter>
-    <action android:name="android.net.conn.CONNECTIVITY_CHANGE" />
-  </intent-filter>
-</receiver>
-```
-
-Broadcast receiver then handles intent that was broadcasted in onReceive function. This is a great place to check whether your app is on foreground or not. If app is not on foreground we can prepare our intent to be started, with no information or additional information bundled using `putExtra` (keep in mind bundle can handle only parcelable values). In the end service is started and wakelock is acquired.
-
-```java
-public class NetworkChangeReceiver extends BroadcastReceiver {
-
-    @Override
-    public void onReceive(final Context context, final Intent intent) {
-        /**
-          This part will be called everytime network connection is changed
-          e.g. Connected -> Not Connected
-        **/
-        if (!isAppOnForeground((context))) {
-            /**
-              We will start our service and send extra info about
-              network connections
-            **/
-            boolean hasInternet = isNetworkAvailable(context);
-            Intent serviceIntent = new Intent(context, MyTaskService.class);
-            serviceIntent.putExtra("hasInternet", hasInternet);
-            context.startService(serviceIntent);
-            HeadlessJsTaskService.acquireWakeLockNow(context);
-        }
-    }
-
-    private boolean isAppOnForeground(Context context) {
-        /**
-          We need to check if app is in foreground otherwise the app will crash.
-         http://stackoverflow.com/questions/8489993/check-android-application-is-in-foreground-or-not
-        **/
-        ActivityManager activityManager = (ActivityManager) context.getSystemService(Context.ACTIVITY_SERVICE);
-        List<ActivityManager.RunningAppProcessInfo> appProcesses =
-        activityManager.getRunningAppProcesses();
-        if (appProcesses == null) {
-            return false;
-        }
-        final String packageName = context.getPackageName();
-        for (ActivityManager.RunningAppProcessInfo appProcess : appProcesses) {
-            if (appProcess.importance ==
-            ActivityManager.RunningAppProcessInfo.IMPORTANCE_FOREGROUND &&
-             appProcess.processName.equals(packageName)) {
-                return true;
-            }
-        }
-        return false;
-    }
-
-    public static boolean isNetworkAvailable(Context context) {
-        ConnectivityManager cm = (ConnectivityManager)
-        context.getSystemService(Context.CONNECTIVITY_SERVICE);
-        NetworkInfo netInfo = cm.getActiveNetworkInfo();
-        return (netInfo != null && netInfo.isConnected());
-    }
-
-
-}
-```
-
-[0]: https://developer.android.com/reference/android/content/Context.html#startService(android.content.Intent)
diff --git a/website/versioned_docs/version-0.60/height-and-width.md b/website/versioned_docs/version-0.60/height-and-width.md
deleted file mode 100644
index ed0f86dc8c6..00000000000
--- a/website/versioned_docs/version-0.60/height-and-width.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-id: version-0.60-height-and-width
-title: Height and Width
-original_id: height-and-width
----
-
-A component's height and width determine its size on the screen.
-
-## Fixed Dimensions
-
-The simplest way to set the dimensions of a component is by adding a fixed `width` and `height` to style. All dimensions in React Native are unitless, and represent density-independent pixels.
-
-```SnackPlayer name=Height%20and%20Width
-import React, { Component } from 'react';
-import { View } from 'react-native';
-
-export default class FixedDimensionsBasics extends Component {
-  render() {
-    return (
-      <View>
-        <View style={{width: 50, height: 50, backgroundColor: 'powderblue'}} />
-        <View style={{width: 100, height: 100, backgroundColor: 'skyblue'}} />
-        <View style={{width: 150, height: 150, backgroundColor: 'steelblue'}} />
-      </View>
-    );
-  }
-}
-```
-
-Setting dimensions this way is common for components that should always render at exactly the same size, regardless of screen dimensions.
-
-## Flex Dimensions
-
-Use `flex` in a component's style to have the component expand and shrink dynamically based on available space. Normally you will use `flex: 1`, which tells a component to fill all available space, shared evenly amongst other components with the same parent. The larger the `flex` given, the higher the ratio of space a component will take compared to its siblings.
-
-> A component can only expand to fill available space if its parent has dimensions greater than 0. If a parent does not have either a fixed `width` and `height` or `flex`, the parent will have dimensions of 0 and the `flex` children will not be visible.
-
-````SnackPlayer name=Flex%20Dimensions
-import React, { Component } from 'react';
-import { View } from 'react-native';
-
-export default class FlexDimensionsBasics extends Component {
-  render() {
-    return (
-      // Try removing the `flex: 1` on the parent View.
-      // The parent will not have dimensions, so the children can't expand.
-      // What if you add `height: 300` instead of `flex: 1`?
-      <View style={{flex: 1}}>
-        <View style={{flex: 1, backgroundColor: 'powderblue'}} />
-        <View style={{flex: 2, backgroundColor: 'skyblue'}} />
-        <View style={{flex: 3, backgroundColor: 'steelblue'}} />
-      </View>
-    );
-  }
-}
-```
-
-After you can control a component's size, the next step is to [learn how to lay it out on the screen](flexbox.md).
-````
diff --git a/website/versioned_docs/version-0.60/images.md b/website/versioned_docs/version-0.60/images.md
deleted file mode 100644
index 5392c803970..00000000000
--- a/website/versioned_docs/version-0.60/images.md
+++ /dev/null
@@ -1,223 +0,0 @@
----
-id: version-0.60-images
-title: Images
-original_id: images
----
-
-## Static Image Resources
-
-React Native provides a unified way of managing images and other media assets in your iOS and Android apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
-
-```jsx
-<Image source={require('./my-icon.png')} />
-```
-
-The image name is resolved the same way JS modules are resolved. In the example above, the packager will look for `my-icon.png` in the same folder as the component that requires it. Also, if you have `my-icon.ios.png` and `my-icon.android.png`, the packager will pick the correct file for the platform.
-
-You can also use the `@2x` and `@3x` suffixes to provide images for different screen densities. If you have the following file structure:
-
-```
-.
-├── button.js
-└── img
-    ├── check.png
-    ├── check@2x.png
-    └── check@3x.png
-```
-
-...and `button.js` code contains:
-
-```jsx
-<Image source={require('./img/check.png')} />
-```
-
-...the packager will bundle and serve the image corresponding to device's screen density. For example, `check@2x.png`, will be used on an iPhone 7, while`check@3x.png` will be used on an iPhone 7 Plus or a Nexus 5. If there is no image matching the screen density, the closest best option will be selected.
-
-On Windows, you might need to restart the packager if you add new images to your project.
-
-Here are some benefits that you get:
-
-1. Same system on iOS and Android.
-2. Images live in the same folder as your JavaScript code. Components are self-contained.
-3. No global namespace, i.e. you don't have to worry about name collisions.
-4. Only the images that are actually used will be packaged into your app.
-5. Adding and changing images doesn't require app recompilation, just refresh the simulator as you normally do.
-6. The packager knows the image dimensions, no need to duplicate it in the code.
-7. Images can be distributed via [npm](https://www.npmjs.com/) packages.
-
-In order for this to work, the image name in `require` has to be known statically.
-
-```jsx
-// GOOD
-<Image source={require('./my-icon.png')} />;
-
-// BAD
-var icon = this.props.active ? 'my-icon-active' : 'my-icon-inactive';
-<Image source={require('./' + icon + '.png')} />;
-
-// GOOD
-var icon = this.props.active
-  ? require('./my-icon-active.png')
-  : require('./my-icon-inactive.png');
-<Image source={icon} />;
-```
-
-Note that image sources required this way include size (width, height) info for the Image. If you need to scale the image dynamically (i.e. via flex), you may need to manually set `{ width: undefined, height: undefined }` on the style attribute.
-
-## Static Non-Image Resources
-
-The `require` syntax described above can be used to statically include audio, video or document files in your project as well. Most common file types are supported including `.mp3`, `.wav`, `.mp4`, `.mov`, `.html` and `.pdf`. See [packager defaults](https://github.com/facebook/metro/blob/master/packages/metro-config/src/defaults/defaults.js#L14-L44) for the full list.
-
-You can add support for other types by adding an [`assetExts` resolver option](https://facebook.github.io/metro/docs/en/configuration#assetexts) in your [Metro configuration](https://facebook.github.io/metro/docs/en/configuration).
-
-A caveat is that videos must use absolute positioning instead of `flexGrow`, since size info is not currently passed for non-image assets. This limitation doesn't occur for videos that are linked directly into Xcode or the Assets folder for Android.
-
-## Images From Hybrid App's Resources
-
-If you are building a hybrid app (some UIs in React Native, some UIs in platform code) you can still use images that are already bundled into the app.
-
-For images included via Xcode asset catalogs or in the Android drawable folder, use the image name without the extension:
-
-```jsx
-<Image source={{uri: 'app_icon'}} style={{width: 40, height: 40}} />
-```
-
-For images in the Android assets folder, use the `asset:/` scheme:
-
-```jsx
-<Image source={{uri: 'asset:/app_icon.png'}} style={{width: 40, height: 40}} />
-```
-
-These approaches provide no safety checks. It's up to you to guarantee that those images are available in the application. Also you have to specify image dimensions manually.
-
-## Network Images
-
-Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](running-on-device.md#app-transport-security) requirements on iOS.
-
-```jsx
-// GOOD
-<Image source={{uri: 'https://facebook.github.io/react/logo-og.png'}}
-       style={{width: 400, height: 400}} />
-
-// BAD
-<Image source={{uri: 'https://facebook.github.io/react/logo-og.png'}} />
-```
-
-### Network Requests for Images
-
-If you would like to set such things as the HTTP-Verb, Headers or a Body along with the image request, you may do this by defining these properties on the source object:
-
-```jsx
-<Image
-  source={{
-    uri: 'https://facebook.github.io/react/logo-og.png',
-    method: 'POST',
-    headers: {
-      Pragma: 'no-cache',
-    },
-    body: 'Your Body goes here',
-  }}
-  style={{width: 400, height: 400}}
-/>
-```
-
-## Uri Data Images
-
-Sometimes, you might be getting encoded image data from a REST API call. You can use the `'data:'` uri scheme to use these images. Same as for network resources, _you will need to manually specify the dimensions of your image_.
-
-> This is recommended for very small and dynamic images only, like icons in a list from a DB.
-
-```jsx
-// include at least width and height!
-<Image
-  style={{
-    width: 51,
-    height: 51,
-    resizeMode: 'contain',
-  }}
-  source={{
-    uri:
-      'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADMAAAAzCAYAAAA6oTAqAAAAEXRFWHRTb2Z0d2FyZQBwbmdjcnVzaEB1SfMAAABQSURBVGje7dSxCQBACARB+2/ab8BEeQNhFi6WSYzYLYudDQYGBgYGBgYGBgYGBgYGBgZmcvDqYGBgmhivGQYGBgYGBgYGBgYGBgYGBgbmQw+P/eMrC5UTVAAAAABJRU5ErkJggg==',
-  }}
-/>
-```
-
-### Cache Control (iOS Only)
-
-In some cases you might only want to display an image if it is already in the local cache, i.e. a low resolution placeholder until a higher resolution is available. In other cases you do not care if the image is outdated and are willing to display an outdated image to save bandwidth. The `cache` source property gives you control over how the network layer interacts with the cache.
-
-- `default`: Use the native platforms default strategy.
-- `reload`: The data for the URL will be loaded from the originating source. No existing cache data should be used to satisfy a URL load request.
-- `force-cache`: The existing cached data will be used to satisfy the request, regardless of its age or expiration date. If there is no existing data in the cache corresponding the request, the data is loaded from the originating source.
-- `only-if-cached`: The existing cache data will be used to satisfy a request, regardless of its age or expiration date. If there is no existing data in the cache corresponding to a URL load request, no attempt is made to load the data from the originating source, and the load is considered to have failed.
-
-```jsx
-<Image
-  source={{
-    uri: 'https://facebook.github.io/react/logo-og.png',
-    cache: 'only-if-cached',
-  }}
-  style={{width: 400, height: 400}}
-/>
-```
-
-## Local Filesystem Images
-
-See [CameraRoll](https://github.com/react-native-community/react-native-cameraroll) for an example of using local resources that are outside of `Images.xcassets`.
-
-### Best Camera Roll Image
-
-iOS saves multiple sizes for the same image in your Camera Roll, it is very important to pick the one that's as close as possible for performance reasons. You wouldn't want to use the full quality 3264x2448 image as source when displaying a 200x200 thumbnail. If there's an exact match, React Native will pick it, otherwise it's going to use the first one that's at least 50% bigger in order to avoid blur when resizing from a close size. All of this is done by default so you don't have to worry about writing the tedious (and error prone) code to do it yourself.
-
-## Why Not Automatically Size Everything?
-
-_In the browser_ if you don't give a size to an image, the browser is going to render a 0x0 element, download the image, and then render the image based with the correct size. The big issue with this behavior is that your UI is going to jump all around as images load, this makes for a very bad user experience.
-
-_In React Native_ this behavior is intentionally not implemented. It is more work for the developer to know the dimensions (or aspect ratio) of the remote image in advance, but we believe that it leads to a better user experience. Static images loaded from the app bundle via the `require('./my-icon.png')` syntax _can be automatically sized_ because their dimensions are available immediately at the time of mounting.
-
-For example, the result of `require('./my-icon.png')` might be:
-
-```jsx
-{"__packager_asset":true,"uri":"my-icon.png","width":591,"height":573}
-```
-
-## Source as an object
-
-In React Native, one interesting decision is that the `src` attribute is named `source` and doesn't take a string but an object with a `uri` attribute.
-
-```jsx
-<Image source={{uri: 'something.jpg'}} />
-```
-
-On the infrastructure side, the reason is that it allows us to attach metadata to this object. For example if you are using `require('./my-icon.png')`, then we add information about its actual location and size (don't rely on this fact, it might change in the future!). This is also future proofing, for example we may want to support sprites at some point, instead of outputting `{uri: ...}`, we can output `{uri: ..., crop: {left: 10, top: 50, width: 20, height: 40}}` and transparently support spriting on all the existing call sites.
-
-On the user side, this lets you annotate the object with useful attributes such as the dimension of the image in order to compute the size it's going to be displayed in. Feel free to use it as your data structure to store more information about your image.
-
-## Background Image via Nesting
-
-A common feature request from developers familiar with the web is `background-image`. To handle this use case, you can use the `<ImageBackground>` component, which has the same props as `<Image>`, and add whatever children to it you would like to layer on top of it.
-
-You might not want to use `<ImageBackground>` in some cases, since the implementation is very simple. Refer to `<ImageBackground>`'s [documentation](imagebackground.md) for more insight, and create your own custom component when needed.
-
-```jsx
-return (
-  <ImageBackground source={...} style={{width: '100%', height: '100%'}}>
-    <Text>Inside</Text>
-  </ImageBackground>
-);
-```
-
-Note that you must specify some width and height style attributes.
-
-## iOS Border Radius Styles
-
-Please note that the following corner specific, border radius style properties are currently ignored by iOS's image component:
-
-- `borderTopLeftRadius`
-- `borderTopRightRadius`
-- `borderBottomLeftRadius`
-- `borderBottomRightRadius`
-
-## Off-thread Decoding
-
-Image decoding can take more than a frame-worth of time. This is one of the major sources of frame drops on the web because decoding is done in the main thread. In React Native, image decoding is done in a different thread. In practice, you already need to handle the case when the image is not downloaded yet, so displaying the placeholder for a few more frames while it is decoding does not require any code change.
diff --git a/website/versioned_docs/version-0.60/integration-with-existing-apps.md b/website/versioned_docs/version-0.60/integration-with-existing-apps.md
deleted file mode 100644
index 75e1345a4de..00000000000
--- a/website/versioned_docs/version-0.60/integration-with-existing-apps.md
+++ /dev/null
@@ -1,799 +0,0 @@
----
-id: version-0.60-integration-with-existing-apps
-title: Integration with Existing Apps
-original_id: integration-with-existing-apps
----
-
-React Native is great when you are starting a new mobile app from scratch. However, it also works well for adding a single view or user flow to existing native applications. With a few steps, you can add new React Native based features, screens, views, etc.
-
-The specific steps are different depending on what platform you're targeting.
-
-<div class="toggler">
-  <ul role="tablist" id="toggle-language" >
-    <li id="objc" class="button-objc" aria-selected="false" role="tab" tabindex="0" aria-controls="objctab" onclick="displayTab('language', 'objc')">
-      iOS (Objective-C)
-    </li>
-    <li id="swift" class="button-swift" aria-selected="false" role="tab" tabindex="0" aria-controls="swifttab" onclick="displayTab('language', 'swift')">
-      iOS (Swift)
-    </li>
-    <li id="android" class="button-android" aria-selected="false" role="tab" tabindex="0" aria-controls="androidtab" onclick="displayTab('language', 'android')">
-      Android (Java)
-    </li>
-  </ul>
-</div>
-
-<block class="objc swift android" />
-
-## Key Concepts
-
-<block class="objc swift" />
-
-The keys to integrating React Native components into your iOS application are to:
-
-1. Set up React Native dependencies and directory structure.
-2. Understand what React Native components you will use in your app.
-3. Add these components as dependencies using CocoaPods.
-4. Develop your React Native components in JavaScript.
-5. Add a `RCTRootView` to your iOS app. This view will serve as the container for your React Native component.
-6. Start the React Native server and run your native application.
-7. Verify that the React Native aspect of your application works as expected.
-
-<block class="android" />
-
-The keys to integrating React Native components into your Android application are to:
-
-1. Set up React Native dependencies and directory structure.
-2. Develop your React Native components in JavaScript.
-3. Add a `ReactRootView` to your Android app. This view will serve as the container for your React Native component.
-4. Start the React Native server and run your native application.
-5. Verify that the React Native aspect of your application works as expected.
-
-<block class="objc swift android" />
-
-## Prerequisites
-
-<block class="objc swift" />
-
-Follow the instructions for building apps with native code from the [Getting Started guide](getting-started.md) to configure your development environment for building React Native apps for iOS.
-
-### 1. Set up directory structure
-
-To ensure a smooth experience, create a new folder for your integrated React Native project, then copy your existing iOS project to a `/ios` subfolder.
-
-<block class="android" />
-
-Follow the instructions for building apps with native code from the [Getting Started guide](getting-started.md) to configure your development environment for building React Native apps for Android.
-
-### 1. Set up directory structure
-
-To ensure a smooth experience, create a new folder for your integrated React Native project, then copy your existing Android project to an `/android` subfolder.
-
-<block class="objc swift android" />
-
-### 2. Install JavaScript dependencies
-
-Go to the root directory for your project and create a new `package.json` file with the following contents:
-
-```
-{
-  "name": "MyReactNativeApp",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "yarn react-native start"
-  }
-}
-```
-
-Next, make sure you have [installed the yarn package manager](https://yarnpkg.com/lang/en/docs/install/).
-
-Install the `react` and `react-native` packages. Open a terminal or command prompt, then navigate to the directory with your `package.json` file and run:
-
-```
-$ yarn add react-native
-```
-
-This will print a message similar to the following (scroll up in the yarn output to see it):
-
-> warning "react-native@0.52.2" has unmet peer dependency "react@16.2.0".
-
-This is OK, it means we also need to install React:
-
-```
-$ yarn add react@version_printed_above
-```
-
-Yarn has created a new `/node_modules` folder. This folder stores all the JavaScript dependencies required to build your project.
-
-Add `node_modules/` to your `.gitignore` file.
-
-<block class="objc swift" />
-
-### 3. Install CocoaPods
-
-[CocoaPods](http://cocoapods.org) is a package management tool for iOS and macOS development. We use it to add the actual React Native framework code locally into your current project.
-
-We recommend installing CocoaPods using [Homebrew](http://brew.sh/).
-
-```
-$ brew install cocoapods
-```
-
-> It is technically possible not to use CocoaPods, but that would require manual library and linker additions that would overly complicate this process.
-
-<block class="objc swift" />
-
-## Adding React Native to your app
-
-<block class="objc" />
-
-Assume the [app for integration](https://github.com/JoelMarcey/iOS-2048) is a [2048](https://en.wikipedia.org/wiki/2048_%28video_game%29) game. Here is what the main menu of the native application looks like without React Native.
-
-<block class="swift" />
-
-Assume the [app for integration](https://github.com/JoelMarcey/swift-2048) is a [2048](https://en.wikipedia.org/wiki/2048_%28video_game%29) game. Here is what the main menu of the native application looks like without React Native.
-
-<block class="objc swift" />
-
-![Before RN Integration](/react-native/docs/assets/react-native-existing-app-integration-ios-before.png)
-
-### Command Line Tools for Xcode
-
-Install the Command Line Tools. Choose "Preferences..." in the Xcode menu. Go to the Locations panel and install the tools by selecting the most recent version in the Command Line Tools dropdown.
-
-![Xcode Command Line Tools](/react-native/docs/assets/GettingStartedXcodeCommandLineTools.png)
-
-### Configuring CocoaPods dependencies
-
-Before you integrate React Native into your application, you will want to decide what parts of the React Native framework you would like to integrate. We will use CocoaPods to specify which of these "subspecs" your app will depend on.
-
-The list of supported `subspec`s is available in [`/node_modules/react-native/React.podspec`](https://github.com/facebook/react-native/blob/master/React.podspec). They are generally named by functionality. For example, you will generally always want the `Core` `subspec`. That will get you the `AppRegistry`, `StyleSheet`, `View` and other core React Native libraries. If you want to add the React Native `Text` library (e.g., for `<Text>` elements), then you will need the `RCTText` `subspec`. If you want the `Image` library (e.g., for `<Image>` elements), then you will need the `RCTImage` `subspec`.
-
-You can specify which `subspec`s your app will depend on in a `Podfile` file. The easiest way to create a `Podfile` is by running the CocoaPods `init` command in the `/ios` subfolder of your project:
-
-```
-$ pod init
-```
-
-The `Podfile` will contain a boilerplate setup that you will tweak for your integration purposes. In the end, `Podfile` should look something similar to this:
-
-<block class="objc" />
-
-```
-# The target name is most likely the name of your project.
-target 'NumberTileGame' do
-
-  # Your 'node_modules' directory is probably in the root of your project,
-  # but if not, adjust the `:path` accordingly
-  pod 'React', :path => '../node_modules/react-native/'
-  pod 'React-Core', :path => '../node_modules/react-native/React'
-  pod 'React-DevSupport', :path => '../node_modules/react-native/React'
-  pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
-  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
-  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
-  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
-  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
-  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
-  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
-  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
-  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
-  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
-  pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'
-
-  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
-  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
-  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
-  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
-  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
-
-  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
-  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
-  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
-end
-```
-
-<block class="swift" />
-
-```
-source 'https://github.com/CocoaPods/Specs.git'
-
-# Required for Swift apps
-platform :ios, '8.0'
-use_frameworks!
-
-# The target name is most likely the name of your project.
-target 'swift-2048' do
-
-  # Your 'node_modules' directory is probably in the root of your project,
-  # but if not, adjust the `:path` accordingly
-  pod 'React', :path => '../node_modules/react-native', :subspecs => [
-    'Core',
-    'CxxBridge', # Include this for RN >= 0.47
-    'DevSupport', # Include this to enable In-App Devmenu if RN >= 0.43
-    'RCTText',
-    'RCTNetwork',
-    'RCTWebSocket', # needed for debugging
-    # Add any other subspecs you want to use in your project
-  ]
-  # Explicitly include Yoga if you are using RN >= 0.42.0
-  pod "yoga", :path => "../node_modules/react-native/ReactCommon/yoga"
-
-  # Third party deps podspec link
-  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
-  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
-  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
-
-end
-```
-
-<block class="objc swift" />
-
-After you have created your `Podfile`, you are ready to install the React Native pod.
-
-```
-$ pod install
-```
-
-You should see output such as:
-
-```
-Analyzing dependencies
-Fetching podspec for `React` from `../node_modules/react-native`
-Downloading dependencies
-Installing React (0.26.0)
-Generating Pods project
-Integrating client project
-Sending stats
-Pod installation complete! There are 3 dependencies from the Podfile and 1 total pod installed.
-```
-
-> If this fails with errors mentioning `xcrun`, make sure that in Xcode in Preferences > Locations the Command Line Tools are assigned.
-
-<block class="swift" />
-
-> If you get a warning such as "_The `swift-2048 [Debug]` target overrides the `FRAMEWORK_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-swift-2048/Pods-swift-2048.debug.xcconfig`. This can lead to problems with the CocoaPods installation_", then make sure the `Framework Search Paths` in `Build Settings` for both `Debug` and `Release` only contain `$(inherited)`.
-
-<block class="objc swift" />
-
-### Code integration
-
-Now we will actually modify the native iOS application to integrate React Native. For our 2048 sample app, we will add a "High Score" screen in React Native.
-
-#### The React Native component
-
-The first bit of code we will write is the actual React Native code for the new "High Score" screen that will be integrated into our application.
-
-##### 1. Create a `index.js` file
-
-First, create an empty `index.js` file in the root of your React Native project.
-
-`index.js` is the starting point for React Native applications, and it is always required. It can be a small file that `require`s other file that are part of your React Native component or application, or it can contain all the code that is needed for it. In our case, we will just put everything in `index.js`.
-
-##### 2. Add your React Native code
-
-In your `index.js`, create your component. In our sample here, we will add simple `<Text>` component within a styled `<View>`
-
-```jsx
-import React from 'react';
-import {AppRegistry, StyleSheet, Text, View} from 'react-native';
-
-class RNHighScores extends React.Component {
-  render() {
-    var contents = this.props['scores'].map((score) => (
-      <Text key={score.name}>
-        {score.name}:{score.value}
-        {'\n'}
-      </Text>
-    ));
-    return (
-      <View style={styles.container}>
-        <Text style={styles.highScoresTitle}>2048 High Scores!</Text>
-        <Text style={styles.scores}>{contents}</Text>
-      </View>
-    );
-  }
-}
-
-const styles = StyleSheet.create({
-  container: {
-    flex: 1,
-    justifyContent: 'center',
-    alignItems: 'center',
-    backgroundColor: '#FFFFFF',
-  },
-  highScoresTitle: {
-    fontSize: 20,
-    textAlign: 'center',
-    margin: 10,
-  },
-  scores: {
-    textAlign: 'center',
-    color: '#333333',
-    marginBottom: 5,
-  },
-});
-
-// Module name
-AppRegistry.registerComponent('RNHighScores', () => RNHighScores);
-```
-
-> `RNHighScores` is the name of your module that will be used when you add a view to React Native from within your iOS application.
-
-#### The Magic: `RCTRootView`
-
-Now that your React Native component is created via `index.js`, you need to add that component to a new or existing `ViewController`. The easiest path to take is to optionally create an event path to your component and then add that component to an existing `ViewController`.
-
-We will tie our React Native component with a new native view in the `ViewController` that will actually host it called `RCTRootView` .
-
-##### 1. Create an Event Path
-
-You can add a new link on the main game menu to go to the "High Score" React Native page.
-
-![Event Path](/react-native/docs/assets/react-native-add-react-native-integration-link.png)
-
-##### 2. Event Handler
-
-We will now add an event handler from the menu link. A method will be added to the main `ViewController` of your application. This is where `RCTRootView` comes into play.
-
-When you build a React Native application, you use the React Native packager to create an `index.bundle` that will be served by the React Native server. Inside `index.bundle` will be our `RNHighScore` module. So, we need to point our `RCTRootView` to the location of the `index.bundle` resource (via `NSURL`) and tie it to the module.
-
-We will, for debugging purposes, log that the event handler was invoked. Then, we will create a string with the location of our React Native code that exists inside the `index.bundle`. Finally, we will create the main `RCTRootView`. Notice how we provide `RNHighScores` as the `moduleName` that we created [above](#the-react-native-component) when writing the code for our React Native component.
-
-<block class="objc" />
-
-First `import` the `RCTRootView` header.
-
-```objectivec
-#import <React/RCTRootView.h>
-```
-
-> The `initialProperties` are here for illustration purposes so we have some data for our high score screen. In our React Native component, we will use `this.props` to get access to that data.
-
-```objectivec
-- (IBAction)highScoreButtonPressed:(id)sender {
-    NSLog(@"High Score Button Pressed");
-    NSURL *jsCodeLocation = [NSURL URLWithString:@"http://localhost:8081/index.bundle?platform=ios"];
-
-    RCTRootView *rootView =
-      [[RCTRootView alloc] initWithBundleURL: jsCodeLocation
-                                  moduleName: @"RNHighScores"
-                           initialProperties:
-                             @{
-                               @"scores" : @[
-                                 @{
-                                   @"name" : @"Alex",
-                                   @"value": @"42"
-                                  },
-                                 @{
-                                   @"name" : @"Joel",
-                                   @"value": @"10"
-                                 }
-                               ]
-                             }
-                               launchOptions: nil];
-    UIViewController *vc = [[UIViewController alloc] init];
-    vc.view = rootView;
-    [self presentViewController:vc animated:YES completion:nil];
-}
-```
-
-> Note that `RCTRootView initWithURL` starts up a new JSC VM. To save resources and simplify the communication between RN views in different parts of your native app, you can have multiple views powered by React Native that are associated with a single JS runtime. To do that, instead of using `[RCTRootView alloc] initWithURL`, use [`RCTBridge initWithBundleURL`](https://github.com/facebook/react-native/blob/master/React/Base/RCTBridge.h#L93) to create a bridge and then use `RCTRootView initWithBridge`.
-
-<block class="swift" />
-
-First `import` the `React` library.
-
-```jsx
-import React
-```
-
-> The `initialProperties` are here for illustration purposes so we have some data for our high score screen. In our React Native component, we will use `this.props` to get access to that data.
-
-```swift
-@IBAction func highScoreButtonTapped(sender : UIButton) {
-  NSLog("Hello")
-  let jsCodeLocation = URL(string: "http://localhost:8081/index.bundle?platform=ios")
-  let mockData:NSDictionary = ["scores":
-      [
-          ["name":"Alex", "value":"42"],
-          ["name":"Joel", "value":"10"]
-      ]
-  ]
-
-  let rootView = RCTRootView(
-      bundleURL: jsCodeLocation,
-      moduleName: "RNHighScores",
-      initialProperties: mockData as [NSObject : AnyObject],
-      launchOptions: nil
-  )
-  let vc = UIViewController()
-  vc.view = rootView
-  self.present(vc, animated: true, completion: nil)
-}
-```
-
-> Note that `RCTRootView bundleURL` starts up a new JSC VM. To save resources and simplify the communication between RN views in different parts of your native app, you can have multiple views powered by React Native that are associated with a single JS runtime. To do that, instead of using `RCTRootView bundleURL`, use [`RCTBridge initWithBundleURL`](https://github.com/facebook/react-native/blob/master/React/Base/RCTBridge.h#L89) to create a bridge and then use `RCTRootView initWithBridge`.
-
-<block class="objc" />
-
-> When moving your app to production, the `NSURL` can point to a pre-bundled file on disk via something like `[[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];`. You can use the `react-native-xcode.sh` script in `node_modules/react-native/scripts/` to generate that pre-bundled file.
-
-<block class="swift" />
-
-> When moving your app to production, the `NSURL` can point to a pre-bundled file on disk via something like `let mainBundle = NSBundle(URLForResource: "main" withExtension:"jsbundle")`. You can use the `react-native-xcode.sh` script in `node_modules/react-native/scripts/` to generate that pre-bundled file.
-
-<block class="objc swift" />
-
-##### 3. Wire Up
-
-Wire up the new link in the main menu to the newly added event handler method.
-
-![Event Path](/react-native/docs/assets/react-native-add-react-native-integration-wire-up.png)
-
-> One of the easier ways to do this is to open the view in the storyboard and right click on the new link. Select something such as the `Touch Up Inside` event, drag that to the storyboard and then select the created method from the list provided.
-
-### Test your integration
-
-You have now done all the basic steps to integrate React Native with your current application. Now we will start the React Native packager to build the `index.bundle` package and the server running on `localhost` to serve it.
-
-##### 1. Add App Transport Security exception
-
-Apple has blocked implicit cleartext HTTP resource loading. So we need to add the following our project's `Info.plist` (or equivalent) file.
-
-```xml
-<key>NSAppTransportSecurity</key>
-<dict>
-    <key>NSExceptionDomains</key>
-    <dict>
-        <key>localhost</key>
-        <dict>
-            <key>NSTemporaryExceptionAllowsInsecureHTTPLoads</key>
-            <true/>
-        </dict>
-    </dict>
-</dict>
-```
-
-> App Transport Security is good for your users. Make sure to re-enable it prior to releasing your app for production.
-
-##### 2. Run the packager
-
-To run your app, you need to first start the development server. To do this, simply run the following command in the root directory of your React Native project:
-
-```
-$ npm start
-```
-
-##### 3. Run the app
-
-If you are using Xcode or your favorite editor, build and run your native iOS application as normal. Alternatively, you can run the app from the command line using:
-
-```
-# From the root of your project
-$ react-native run-ios
-```
-
-In our sample application, you should see the link to the "High Scores" and then when you click on that you will see the rendering of your React Native component.
-
-Here is the _native_ application home screen:
-
-![Home Screen](/react-native/docs/assets/react-native-add-react-native-integration-example-home-screen.png)
-
-Here is the _React Native_ high score screen:
-
-![High Scores](/react-native/docs/assets/react-native-add-react-native-integration-example-high-scores.png)
-
-> If you are getting module resolution issues when running your application please see [this GitHub issue](https://github.com/facebook/react-native/issues/4968) for information and possible resolution. [This comment](https://github.com/facebook/react-native/issues/4968#issuecomment-220941717) seemed to be the latest possible resolution.
-
-### See the Code
-
-<block class="objc" />
-
-You can examine the code that added the React Native screen to our sample app on [GitHub](https://github.com/JoelMarcey/iOS-2048/commit/9ae70c7cdd53eb59f5f7c7daab382b0300ed3585).
-
-<block class="swift" />
-
-You can examine the code that added the React Native screen to our sample app on [GitHub](https://github.com/JoelMarcey/swift-2048/commit/13272a31ee6dd46dc68b1dcf4eaf16c1a10f5229).
-
-<block class="android" />
-
-## Adding React Native to your app
-
-### Configuring maven
-
-Add the React Native dependency to your app's `build.gradle` file:
-
-```gradle
-dependencies {
-    implementation 'com.android.support:appcompat-v7:27.1.1'
-    ...
-    implementation "com.facebook.react:react-native:+" // From node_modules
-}
-```
-
-> If you want to ensure that you are always using a specific React Native version in your native build, replace `+` with an actual React Native version you've downloaded from `npm`.
-
-Add an entry for the local React Native maven directory to `build.gradle`. Be sure to add it to the "allprojects" block, above other maven repositories:
-
-```gradle
-allprojects {
-    repositories {
-        maven {
-            // All of React Native (JS, Android binaries) is installed from npm
-            url "$rootDir/../node_modules/react-native/android"
-        }
-        ...
-    }
-    ...
-}
-```
-
-> Make sure that the path is correct! You shouldn’t run into any “Failed to resolve: com.facebook.react:react-native:0.x.x" errors after running Gradle sync in Android Studio.
-
-### Configuring permissions
-
-Next, make sure you have the Internet permission in your `AndroidManifest.xml`:
-
-    <uses-permission android:name="android.permission.INTERNET" />
-
-If you need to access to the `DevSettingsActivity` add to your `AndroidManifest.xml`:
-
-    <activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
-
-This is only used in dev mode when reloading JavaScript from the development server, so you can strip this in release builds if you need to.
-
-### Cleartext Traffic (API level 28+)
-
-> Starting with Android 9 (API level 28), cleartext traffic is disabled by default; this prevents your application from connecting to the React Native packager. The changes below allow cleartext traffic in debug builds.
-
-#### 1. Apply the `usesCleartextTraffic` option to your Debug `AndroidManifest.xml`
-
-```xml
-<!-- ... -->
-<application
-  android:usesCleartextTraffic="true" tools:targetApi="28" >
-  <!-- ... -->
-</application>
-<!-- ... -->
-```
-
-This is not required for Release builds.
-
-To learn more about Network Security Config and the cleartext traffic policy [see this link](https://developer.android.com/training/articles/security-config#CleartextTrafficPermitted).
-
-### Code integration
-
-Now we will actually modify the native Android application to integrate React Native.
-
-#### The React Native component
-
-The first bit of code we will write is the actual React Native code for the new "High Score" screen that will be integrated into our application.
-
-##### 1. Create a `index.js` file
-
-First, create an empty `index.js` file in the root of your React Native project.
-
-`index.js` is the starting point for React Native applications, and it is always required. It can be a small file that `require`s other file that are part of your React Native component or application, or it can contain all the code that is needed for it. In our case, we will just put everything in `index.js`.
-
-##### 2. Add your React Native code
-
-In your `index.js`, create your component. In our sample here, we will add simple `<Text>` component within a styled `<View>`:
-
-```jsx
-import React from 'react';
-import {AppRegistry, StyleSheet, Text, View} from 'react-native';
-
-class HelloWorld extends React.Component {
-  render() {
-    return (
-      <View style={styles.container}>
-        <Text style={styles.hello}>Hello, World</Text>
-      </View>
-    );
-  }
-}
-var styles = StyleSheet.create({
-  container: {
-    flex: 1,
-    justifyContent: 'center',
-  },
-  hello: {
-    fontSize: 20,
-    textAlign: 'center',
-    margin: 10,
-  },
-});
-
-AppRegistry.registerComponent('MyReactNativeApp', () => HelloWorld);
-```
-
-##### 3. Configure permissions for development error overlay
-
-If your app is targeting the Android `API level 23` or greater, make sure you have the permission `android.permission.SYSTEM_ALERT_WINDOW` enabled for the development build. You can check this with `Settings.canDrawOverlays(this);`. This is required in dev builds because React Native development errors must be displayed above all the other windows. Due to the new permissions system introduced in the API level 23 (Android M), the user needs to approve it. This can be achieved by adding the following code to your Activity's in `onCreate()` method.
-
-```java
-private final int OVERLAY_PERMISSION_REQ_CODE = 1;  // Choose any value
-
-...
-
-if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
-    if (!Settings.canDrawOverlays(this)) {
-        Intent intent = new Intent(Settings.ACTION_MANAGE_OVERLAY_PERMISSION,
-                                   Uri.parse("package:" + getPackageName()));
-        startActivityForResult(intent, OVERLAY_PERMISSION_REQ_CODE);
-    }
-}
-```
-
-Finally, the `onActivityResult()` method (as shown in the code below) has to be overridden to handle the permission Accepted or Denied cases for consistent UX. Also, for integrating Native Modules which use `startActivityForResult`, we need to pass the result to the `onActivityResult` method of our `ReactInstanceManager` instance.
-
-```java
-@Override
-protected void onActivityResult(int requestCode, int resultCode, Intent data) {
-    if (requestCode == OVERLAY_PERMISSION_REQ_CODE) {
-        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
-            if (!Settings.canDrawOverlays(this)) {
-                // SYSTEM_ALERT_WINDOW permission not granted
-            }
-        }
-    }
-    mReactInstanceManager.onActivityResult( this, requestCode, resultCode, data );
-}
-```
-
-#### The Magic: `ReactRootView`
-
-Let's add some native code in order to start the React Native runtime and tell it to render our JS component. To do this, we're going to create an `Activity` that creates a `ReactRootView`, starts a React application inside it and sets it as the main content view.
-
-> If you are targetting Android version <5, use the `AppCompatActivity` class from the `com.android.support:appcompat` package instead of `Activity`.
-
-```java
-public class MyReactActivity extends Activity implements DefaultHardwareBackBtnHandler {
-    private ReactRootView mReactRootView;
-    private ReactInstanceManager mReactInstanceManager;
-
-    @Override
-    protected void onCreate(Bundle savedInstanceState) {
-        super.onCreate(savedInstanceState);
-
-        mReactRootView = new ReactRootView(this);
-        mReactInstanceManager = ReactInstanceManager.builder()
-                .setApplication(getApplication())
-                .setCurrentActivity(this)
-                .setBundleAssetName("index.android.bundle")
-                .setJSMainModulePath("index")
-                .addPackage(new MainReactPackage())
-                .setUseDeveloperSupport(BuildConfig.DEBUG)
-                .setInitialLifecycleState(LifecycleState.RESUMED)
-                .build();
-        // The string here (e.g. "MyReactNativeApp") has to match
-        // the string in AppRegistry.registerComponent() in index.js
-        mReactRootView.startReactApplication(mReactInstanceManager, "MyReactNativeApp", null);
-
-        setContentView(mReactRootView);
-    }
-
-    @Override
-    public void invokeDefaultOnBackPressed() {
-        super.onBackPressed();
-    }
-}
-```
-
-> If you are using a starter kit for React Native, replace the "HelloWorld" string with the one in your index.js file (it’s the first argument to the `AppRegistry.registerComponent()` method).
-
-If you are using Android Studio, use `Alt + Enter` to add all missing imports in your MyReactActivity class. Be careful to use your package’s `BuildConfig` and not the one from the `facebook` package.
-
-We need set the theme of `MyReactActivity` to `Theme.AppCompat.Light.NoActionBar` because some React Native UI components rely on this theme.
-
-```xml
-<activity
-  android:name=".MyReactActivity"
-  android:label="@string/app_name"
-  android:theme="@style/Theme.AppCompat.Light.NoActionBar">
-</activity>
-```
-
-> A `ReactInstanceManager` can be shared by multiple activities and/or fragments. You will want to make your own `ReactFragment` or `ReactActivity` and have a singleton _holder_ that holds a `ReactInstanceManager`. When you need the `ReactInstanceManager` (e.g., to hook up the `ReactInstanceManager` to the lifecycle of those Activities or Fragments) use the one provided by the singleton.
-
-Next, we need to pass some activity lifecycle callbacks to the `ReactInstanceManager` and `ReactRootView`:
-
-```java
-@Override
-protected void onPause() {
-    super.onPause();
-
-    if (mReactInstanceManager != null) {
-        mReactInstanceManager.onHostPause(this);
-    }
-}
-
-@Override
-protected void onResume() {
-    super.onResume();
-
-    if (mReactInstanceManager != null) {
-        mReactInstanceManager.onHostResume(this, this);
-    }
-}
-
-@Override
-protected void onDestroy() {
-    super.onDestroy();
-
-    if (mReactInstanceManager != null) {
-        mReactInstanceManager.onHostDestroy(this);
-    }
-    if (mReactRootView != null) {
-        mReactRootView.unmountReactApplication();
-    }
-}
-```
-
-We also need to pass back button events to React Native:
-
-```java
-@Override
- public void onBackPressed() {
-    if (mReactInstanceManager != null) {
-        mReactInstanceManager.onBackPressed();
-    } else {
-        super.onBackPressed();
-    }
-}
-```
-
-This allows JavaScript to control what happens when the user presses the hardware back button (e.g. to implement navigation). When JavaScript doesn't handle the back button press, your `invokeDefaultOnBackPressed` method will be called. By default this simply finishes your `Activity`.
-
-Finally, we need to hook up the dev menu. By default, this is activated by (rage) shaking the device, but this is not very useful in emulators. So we make it show when you press the hardware menu button (use `Ctrl + M` if you're using Android Studio emulator):
-
-```java
-@Override
-public boolean onKeyUp(int keyCode, KeyEvent event) {
-    if (keyCode == KeyEvent.KEYCODE_MENU && mReactInstanceManager != null) {
-        mReactInstanceManager.showDevOptionsDialog();
-        return true;
-    }
-    return super.onKeyUp(keyCode, event);
-}
-```
-
-Now your activity is ready to run some JavaScript code.
-
-### Test your integration
-
-You have now done all the basic steps to integrate React Native with your current application. Now we will start the React Native packager to build the `index.bundle` package and the server running on localhost to serve it.
-
-##### 1. Run the packager
-
-To run your app, you need to first start the development server. To do this, simply run the following command in the root directory of your React Native project:
-
-```
-$ yarn start
-```
-
-##### 2. Run the app
-
-Now build and run your Android app as normal.
-
-Once you reach your React-powered activity inside the app, it should load the JavaScript code from the development server and display:
-
-![Screenshot](/react-native/docs/assets/EmbeddedAppAndroid.png)
-
-### Creating a release build in Android Studio
-
-You can use Android Studio to create your release builds too! It’s as easy as creating release builds of your previously-existing native Android app. There’s just one additional step, which you’ll have to do before every release build. You need to execute the following to create a React Native bundle, which will be included with your native Android app:
-
-```
-$ react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/com/your-company-name/app-package-name/src/main/assets/index.android.bundle --assets-dest android/com/your-company-name/app-package-name/src/main/res/
-```
-
-> Don’t forget to replace the paths with correct ones and create the assets folder if it doesn’t exist.
-
-Now just create a release build of your native app from within Android Studio as usual and you should be good to go!
-
-<block class="objc swift android" />
-
-### Now what?
-
-At this point you can continue developing your app as usual. Refer to our [debugging](debugging.md) and [deployment](running-on-device.md) docs to learn more about working with React Native.
diff --git a/website/versioned_docs/version-0.60/javascript-environment.md b/website/versioned_docs/version-0.60/javascript-environment.md
deleted file mode 100644
index 25473b10a9e..00000000000
--- a/website/versioned_docs/version-0.60/javascript-environment.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-id: version-0.60-javascript-environment
-title: JavaScript Environment
-original_id: javascript-environment
----
-
-## JavaScript Runtime
-
-When using React Native, you're going to be running your JavaScript code in two environments:
-
-- In most cases, React Native will use [JavaScriptCore](http://trac.webkit.org/wiki/JavaScriptCore), the JavaScript engine that powers Safari. Note that on iOS, JavaScriptCore does not use JIT due to the absence of writable executable memory in iOS apps.
-- When using Chrome debugging, all JavaScript code runs within Chrome itself, communicating with native code via WebSockets. Chrome uses [V8](https://v8.dev/) as its JavaScript engine.
-
-While both environments are very similar, you may end up hitting some inconsistencies. We're likely going to experiment with other JavaScript engines in the future, so it's best to avoid relying on specifics of any runtime.
-
-## JavaScript Syntax Transformers
-
-Syntax transformers make writing code more enjoyable by allowing you to use new JavaScript syntax without having to wait for support on all interpreters.
-
-React Native ships with the [Babel JavaScript compiler](https://babeljs.io). Check [Babel documentation](https://babeljs.io/docs/plugins/#transform-plugins) on its supported transformations for more details.
-
-A full list of React Native's enabled transformations can be found in [metro-react-native-babel-preset](https://github.com/facebook/metro/tree/master/packages/metro-react-native-babel-preset).
-
-ES5
-
-- Reserved Words: `promise.catch(function() { });`
-
-ES6
-
-- [Arrow functions](http://babeljs.io/docs/learn-es2015/#arrows): `<C onPress={() => this.setState({pressed: true})} />`
-- [Block scoping](https://babeljs.io/docs/learn-es2015/#let-const): `let greeting = 'hi';`
-- [Call spread](http://babeljs.io/docs/learn-es2015/#default-rest-spread): `Math.max(...array);`
-- [Classes](http://babeljs.io/docs/learn-es2015/#classes): `class C extends React.Component { render() { return <View />; } }`
-- [Constants](https://babeljs.io/docs/learn-es2015/#let-const): `const answer = 42;`
-- [Destructuring](http://babeljs.io/docs/learn-es2015/#destructuring): `var {isActive, style} = this.props;`
-- [for...of](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for...of): `for (var num of [1, 2, 3]) {};`
-- [Modules](http://babeljs.io/docs/learn-es2015/#modules): `import React, { Component } from 'react';`
-- [Computed Properties](http://babeljs.io/docs/learn-es2015/#enhanced-object-literals): `var key = 'abc'; var obj = {[key]: 10};`
-- [Object Concise Method](http://babeljs.io/docs/learn-es2015/#enhanced-object-literals): `var obj = { method() { return 10; } };`
-- [Object Short Notation](http://babeljs.io/docs/learn-es2015/#enhanced-object-literals): `var name = 'vjeux'; var obj = { name };`
-- [Rest Params](https://github.com/sebmarkbage/ecmascript-rest-spread): `function(type, ...args) {};`
-- [Template Literals](http://babeljs.io/docs/learn-es2015/#template-strings): `` var who = 'world'; var str = `Hello ${who}`; ``
-
-ES8
-
-- [Function Trailing Comma](https://github.com/jeffmo/es-trailing-function-commas): `function f(a, b, c,) {};`
-- [Async Functions](https://github.com/tc39/ecmascript-asyncawait): `async function doStuffAsync() { const foo = await doOtherStuffAsync(); };`
-
-Stage 3
-
-- [Object Spread](https://github.com/tc39/proposal-object-rest-spread): `var extended = { ...obj, a: 10 };`
-- [Static class fields](https://github.com/tc39/proposal-static-class-features): `class CustomDate { static epoch = new CustomDate(0); }`
-- [Optional Chaining](https://github.com/tc39/proposal-optional-chaining): `var name = obj.user?.name;`
-
-Specific
-
-- [JSX](https://reactjs.org/docs/jsx-in-depth.html): `<View style={{color: 'red'}} />`
-- [Flow](https://flowtype.org/): `function foo(x: ?number): string {};`
-- [TypeScript](https://flowtype.org/): `function foo(x: number | undefined): string {};`
-- [Babel Template](https://babeljs.io/docs/en/babel-template): allows AST templating
-
-## Polyfills
-
-Many standards functions are also available on all the supported JavaScript runtimes.
-
-Browser
-
-- [console.{log, warn, error, info, trace, table, group, groupEnd}](https://developer.chrome.com/devtools/docs/console-api)
-- [CommonJS require](https://nodejs.org/docs/latest/api/modules.html)
-- [XMLHttpRequest, fetch](network.md#content)
-- [{set, clear}{Timeout, Interval, Immediate}, {request, cancel}AnimationFrame](timers.md#content)
-
-ES6
-
-- [Object.assign](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/assign)
-- String.prototype.{[startsWith](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/startsWith), [endsWith](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/endsWith), [repeat](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/repeat), [includes](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/includes)}
-- [Array.from](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/from)
-- Array.prototype.{[find](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/find), [findIndex](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/findIndex)}
-
-ES7
-
-- Array.prototype.{[includes](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/includes)}
-
-ES8
-
-- Object.{[entries](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/entries), [values](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/values)}
-
-Specific
-
-- `__DEV__`
diff --git a/website/versioned_docs/version-0.60/more-resources.md b/website/versioned_docs/version-0.60/more-resources.md
deleted file mode 100644
index c2061248e6a..00000000000
--- a/website/versioned_docs/version-0.60/more-resources.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-id: version-0.60-more-resources
-title: More Resources
-original_id: more-resources
----
-
-If you just read through this website, you should be able to build a pretty cool React Native app. But React Native isn't just a product made by one company - it's a community of thousands of developers. So if you're interested in React Native, here's some related stuff you might want to check out.
-
-## Popular Libraries
-
-If you're using React Native, you probably already know about [React](https://facebook.github.io/react/). So I feel a bit silly mentioning this. But if you haven't, check out React - it's the best way to build a modern website.
-
-One common question is how to handle the "state" of your React Native application. The most popular library for this is [Redux](http://redux.js.org/). Don't be afraid of how often Redux uses the word "reducer" - it's a pretty simple library, and there's also a nice [series of videos](https://egghead.io/courses/getting-started-with-redux) explaining it.
-
-If you're looking for a library that does a specific thing, check out [Awesome React Native](http://www.awesome-react-native.com/), a curated list of components that also has demos, articles, and other stuff.
-
-## Examples
-
-Try out apps from the [Showcase](/react-native/showcase/) to see what React Native is capable of! There are also some [example apps on GitHub](https://github.com/ReactNativeNews/React-Native-Apps). You can run the apps on a simulator or device, and you can see the source code for these apps, which is neat.
-
-The folks who built the app for Facebook's F8 conference also [open-sourced the code](https://github.com/fbsamples/f8app) and wrote up a [detailed series of tutorials](http://makeitopen.com/). This is useful if you want a more in-depth example that's more realistic than most sample apps out there.
-
-## Extending React Native
-
-- Fellow developers write and publish React Native modules to npm and open source them on GitHub.
-- Making modules helps grow the React Native ecosystem and community. We recommend writing modules for your use cases and sharing them on npm.
-- Read the guides on Native Modules ([iOS](native-modules-ios.md), [Android](native-modules-android.md)) and Native UI Components ([iOS](native-components-ios.md), [Android](native-components-android.md)) if you are interested in extending native functionality.
-- Looking for a pre-built component? Check [JS.coach](https://js.coach/react-native) or [Native Directory](https://www.native.directory) to find what the community has been creating.
-
-## Development Tools
-
-[Nuclide](https://nuclide.io/) is the IDE that Facebook uses internally for JavaScript development. The killer feature of Nuclide is its debugging ability. It also has great inline Flow support. [VS Code](https://code.visualstudio.com/) is another IDE that is popular with JavaScript developers.
-
-[Ignite](https://github.com/infinitered/ignite) is a starter kit that uses Redux and a few different common UI libraries. It has a CLI to generate apps, components, and containers. If you like all of the individual tech choices, Ignite could be perfect for you.
-
-[App Center](https://appcenter.ms/) is a service from Microsoft that makes it easy to deploy live updates to your React Native app. If you don't like going through the app store process to deploy little tweaks, and you also don't like setting up your own backend, give App Center a try.
-
-[Expo](https://docs.expo.io) is a development environment plus application that focuses on letting you build React Native apps in the Expo development environment, without ever touching Xcode or Android Studio. If you wish React Native was even more JavaScripty and webby, check out Expo.
-
-[Yoga](https://yogalayout.com/) is a stand-alone layout engine that extends beyond React Native and allows product engineers to build layouts quickly for multiple platforms with a highly optimized open source layout engine designed with speed, size, and ease of use in mind.
-
-[Bugsnag](https://www.bugsnag.com/), [Microsoft App Center](https://appcenter.ms/), and [Sentry](https://sentry.io/welcome/) all provide excellent crash and error monitoring services for React and React Native apps. These services allow you to proactively monitor crashes and issues occurring on your apps in real time so you can fix them quickly and improve user experience.
-
-The [React Developer Tools](debugging.md#react-developer-tools) are great for debugging React and React Native apps.
diff --git a/website/versioned_docs/version-0.60/native-components-ios.md b/website/versioned_docs/version-0.60/native-components-ios.md
deleted file mode 100644
index d1457705995..00000000000
--- a/website/versioned_docs/version-0.60/native-components-ios.md
+++ /dev/null
@@ -1,512 +0,0 @@
----
-id: version-0.60-native-components-ios
-title: Native UI Components
-original_id: native-components-ios
----
-
-There are tons of native UI widgets out there ready to be used in the latest apps - some of them are part of the platform, others are available as third-party libraries, and still more might be in use in your very own portfolio. React Native has several of the most critical platform components already wrapped, like `ScrollView` and `TextInput`, but not all of them, and certainly not ones you might have written yourself for a previous app. Fortunately, it's quite easy to wrap up these existing components for seamless integration with your React Native application.
-
-Like the native module guide, this too is a more advanced guide that assumes you are somewhat familiar with iOS programming. This guide will show you how to build a native UI component, walking you through the implementation of a subset of the existing `MapView` component available in the core React Native library.
-
-## iOS MapView example
-
-Let's say we want to add an interactive Map to our app - might as well use [`MKMapView`](https://developer.apple.com/library/prerelease/mac/documentation/MapKit/Reference/MKMapView_Class/index.html), we just need to make it usable from JavaScript.
-
-Native views are created and manipulated by subclasses of `RCTViewManager`. These subclasses are similar in function to view controllers, but are essentially singletons - only one instance of each is created by the bridge. They expose native views to the `RCTUIManager`, which delegates back to them to set and update the properties of the views as necessary. The `RCTViewManager`s are also typically the delegates for the views, sending events back to JavaScript via the bridge.
-
-Exposing a view is simple:
-
-- Subclass `RCTViewManager` to create a manager for your component.
-- Add the `RCT_EXPORT_MODULE()` marker macro.
-- Implement the `-(UIView *)view` method.
-
-```objectivec
-// RNTMapManager.m
-#import <MapKit/MapKit.h>
-
-#import <React/RCTViewManager.h>
-
-@interface RNTMapManager : RCTViewManager
-@end
-
-@implementation RNTMapManager
-
-RCT_EXPORT_MODULE(RNTMap)
-
-- (UIView *)view
-{
-  return [[MKMapView alloc] init];
-}
-
-@end
-```
-
-**Note:** Do not attempt to set the `frame` or `backgroundColor` properties on the `UIView` instance that you expose through the `-view` method. React Native will overwrite the values set by your custom class in order to match your JavaScript component's layout props. If you need this granularity of control it might be better to wrap the `UIView` instance you want to style in another `UIView` and return the wrapper `UIView` instead. See [Issue 2948](https://github.com/facebook/react-native/issues/2948) for more context.
-
-> In the example above, we prefixed our class name with `RNT`. Prefixes are used to avoid name collisions with other frameworks. Apple frameworks use two-letter prefixes, and React Native uses `RCT` as a prefix. In order to avoid name collisions, we recommend using a three-letter prefix other than `RCT` in your own classes.
-
-Then you just need a little bit of JavaScript to make this a usable React component:
-
-```jsx
-// MapView.js
-
-import { requireNativeComponent } from 'react-native';
-
-// requireNativeComponent automatically resolves 'RNTMap' to 'RNTMapManager'
-module.exports = requireNativeComponent('RNTMap');
-
-// MyApp.js
-
-import MapView from './MapView.js';
-
-...
-
-render() {
-  return <MapView style={{ flex: 1 }} />;
-}
-```
-
-Make sure to use `RNTMap` here. We want to require the manager here, which will expose the view of our manager for use in Javascript.
-
-**Note:** When rendering, don't forget to stretch the view, otherwise you'll be staring at a blank screen.
-
-```jsx
-  render() {
-    return <MapView style={{flex: 1}} />;
-  }
-```
-
-This is now a fully-functioning native map view component in JavaScript, complete with pinch-zoom and other native gesture support. We can't really control it from JavaScript yet, though :(
-
-## Properties
-
-The first thing we can do to make this component more usable is to bridge over some native properties. Let's say we want to be able to disable zooming and specify the visible region. Disabling zoom is a simple boolean, so we add this one line:
-
-```objectivec
-// RNTMapManager.m
-RCT_EXPORT_VIEW_PROPERTY(zoomEnabled, BOOL)
-```
-
-Note that we explicitly specify the type as `BOOL` - React Native uses `RCTConvert` under the hood to convert all sorts of different data types when talking over the bridge, and bad values will show convenient "RedBox" errors to let you know there is an issue ASAP. When things are straightforward like this, the whole implementation is taken care of for you by this macro.
-
-Now to actually disable zooming, we set the property in JS:
-
-```jsx
-// MyApp.js
-<MapView zoomEnabled={false} style={{flex: 1}} />
-```
-
-To document the properties (and which values they accept) of our MapView component we'll add a wrapper component and document the interface with React `PropTypes`:
-
-```jsx
-// MapView.js
-import PropTypes from 'prop-types';
-import React from 'react';
-import {requireNativeComponent} from 'react-native';
-
-class MapView extends React.Component {
-  render() {
-    return <RNTMap {...this.props} />;
-  }
-}
-
-MapView.propTypes = {
-  /**
-   * A Boolean value that determines whether the user may use pinch
-   * gestures to zoom in and out of the map.
-   */
-  zoomEnabled: PropTypes.bool,
-};
-
-var RNTMap = requireNativeComponent('RNTMap', MapView);
-
-module.exports = MapView;
-```
-
-Now we have a nicely documented wrapper component that is easy to work with. Note that we changed `requireNativeComponent`'s second argument from `null` to the new `MapView` wrapper component. This allows the infrastructure to verify that the propTypes match the native props in order to reduce the chances of mismatches between the Objective-C and JavaScript code.
-
-Next, let's add the more complex `region` prop. We start by adding the native code:
-
-```objectivec
-// RNTMapManager.m
-RCT_CUSTOM_VIEW_PROPERTY(region, MKCoordinateRegion, MKMapView)
-{
-  [view setRegion:json ? [RCTConvert MKCoordinateRegion:json] : defaultView.region animated:YES];
-}
-```
-
-Ok, this is more complicated than the simple `BOOL` case we had before. Now we have a `MKCoordinateRegion` type that needs a conversion function, and we have custom code so that the view will animate when we set the region from JS. Within the function body that we provide, `json` refers to the raw value that has been passed from JS. There is also a `view` variable which gives us access to the manager's view instance, and a `defaultView` that we use to reset the property back to the default value if JS sends us a null sentinel.
-
-You could write any conversion function you want for your view - here is the implementation for `MKCoordinateRegion` via a category on `RCTConvert`. It uses an already existing category of ReactNative `RCTConvert+CoreLocation`:
-
-```objectivec
-// RNTMapManager.m
-
-#import "RCTConvert+Mapkit.m"
-
-// RCTConvert+Mapkit.h
-
-#import <MapKit/MapKit.h>
-#import <React/RCTConvert.h>
-#import <CoreLocation/CoreLocation.h>
-#import <React/RCTConvert+CoreLocation.h>
-
-@interface RCTConvert (Mapkit)
-
-+ (MKCoordinateSpan)MKCoordinateSpan:(id)json;
-+ (MKCoordinateRegion)MKCoordinateRegion:(id)json;
-
-@end
-
-@implementation RCTConvert(MapKit)
-
-+ (MKCoordinateSpan)MKCoordinateSpan:(id)json
-{
-  json = [self NSDictionary:json];
-  return (MKCoordinateSpan){
-    [self CLLocationDegrees:json[@"latitudeDelta"]],
-    [self CLLocationDegrees:json[@"longitudeDelta"]]
-  };
-}
-
-+ (MKCoordinateRegion)MKCoordinateRegion:(id)json
-{
-  return (MKCoordinateRegion){
-    [self CLLocationCoordinate2D:json],
-    [self MKCoordinateSpan:json]
-  };
-}
-
-@end
-```
-
-These conversion functions are designed to safely process any JSON that the JS might throw at them by displaying "RedBox" errors and returning standard initialization values when missing keys or other developer errors are encountered.
-
-To finish up support for the `region` prop, we need to document it in `propTypes` (or we'll get an error that the native prop is undocumented), then we can set it just like any other prop:
-
-```jsx
-// MapView.js
-
-MapView.propTypes = {
-  /**
-   * A Boolean value that determines whether the user may use pinch
-   * gestures to zoom in and out of the map.
-   */
-  zoomEnabled: PropTypes.bool,
-
-  /**
-   * The region to be displayed by the map.
-   *
-   * The region is defined by the center coordinates and the span of
-   * coordinates to display.
-   */
-  region: PropTypes.shape({
-    /**
-     * Coordinates for the center of the map.
-     */
-    latitude: PropTypes.number.isRequired,
-    longitude: PropTypes.number.isRequired,
-
-    /**
-     * Distance between the minimum and the maximum latitude/longitude
-     * to be displayed.
-     */
-    latitudeDelta: PropTypes.number.isRequired,
-    longitudeDelta: PropTypes.number.isRequired,
-  }),
-};
-
-// MyApp.js
-
-render() {
-  var region = {
-    latitude: 37.48,
-    longitude: -122.16,
-    latitudeDelta: 0.1,
-    longitudeDelta: 0.1,
-  };
-  return (
-    <MapView
-      region={region}
-      zoomEnabled={false}
-      style={{ flex: 1 }}
-    />
-  );
-}
-```
-
-Here you can see that the shape of the region is explicit in the JS documentation - ideally we could codegen some of this stuff, but that's not happening yet.
-
-Sometimes your native component will have some special properties that you don't want to be part of the API for the associated React component. For example, `Switch` has a custom `onChange` handler for the raw native event, and exposes an `onValueChange` handler property that is invoked with just the boolean value rather than the raw event. Since you don't want these native only properties to be part of the API, you don't want to put them in `propTypes`, but if you don't you'll get an error. The solution is simply to add them to the `nativeOnly` option, e.g.
-
-```jsx
-var RCTSwitch = requireNativeComponent('RCTSwitch', Switch, {
-  nativeOnly: {onChange: true},
-});
-```
-
-## Events
-
-So now we have a native map component that we can control easily from JS, but how do we deal with events from the user, like pinch-zooms or panning to change the visible region?
-
-Until now we've just returned a `MKMapView` instance from our manager's `-(UIView *)view` method. We can't add new properties to `MKMapView` so we have to create a new subclass from `MKMapView` which we use for our View. We can then add a `onRegionChange` callback on this subclass:
-
-```objectivec
-// RNTMapView.h
-
-#import <MapKit/MapKit.h>
-
-#import <React/RCTComponent.h>
-
-@interface RNTMapView: MKMapView
-
-@property (nonatomic, copy) RCTBubblingEventBlock onRegionChange;
-
-@end
-
-// RNTMapView.m
-
-#import "RNTMapView.h"
-
-@implementation RNTMapView
-
-@end
-```
-
-Note that all `RCTBubblingEventBlock` must be prefixed with `on`. Next, declare an event handler property on `RNTMapManager`, make it a delegate for all the views it exposes, and forward events to JS by calling the event handler block from the native view.
-
-```objectivec{9,17,31-48}
-// RNTMapManager.m
-
-#import <MapKit/MapKit.h>
-#import <React/RCTViewManager.h>
-
-#import "RNTMapView.h"
-#import "RCTConvert+Mapkit.m"
-
-@interface RNTMapManager : RCTViewManager <MKMapViewDelegate>
-@end
-
-@implementation RNTMapManager
-
-RCT_EXPORT_MODULE()
-
-RCT_EXPORT_VIEW_PROPERTY(zoomEnabled, BOOL)
-RCT_EXPORT_VIEW_PROPERTY(onRegionChange, RCTBubblingEventBlock)
-
-RCT_CUSTOM_VIEW_PROPERTY(region, MKCoordinateRegion, MKMapView)
-{
-	[view setRegion:json ? [RCTConvert MKCoordinateRegion:json] : defaultView.region animated:YES];
-}
-
-- (UIView *)view
-{
-  RNTMapView *map = [RNTMapView new];
-  map.delegate = self;
-  return map;
-}
-
-#pragma mark MKMapViewDelegate
-
-- (void)mapView:(RNTMapView *)mapView regionDidChangeAnimated:(BOOL)animated
-{
-  if (!mapView.onRegionChange) {
-    return;
-  }
-
-  MKCoordinateRegion region = mapView.region;
-  mapView.onRegionChange(@{
-    @"region": @{
-      @"latitude": @(region.center.latitude),
-      @"longitude": @(region.center.longitude),
-      @"latitudeDelta": @(region.span.latitudeDelta),
-      @"longitudeDelta": @(region.span.longitudeDelta),
-    }
-  });
-}
-@end
-```
-
-In the delegate method `-mapView:regionDidChangeAnimated:` the event handler block is called on the corresponding view with the region data. Calling the `onRegionChange` event handler block results in calling the same callback prop in JavaScript. This callback is invoked with the raw event, which we typically process in the wrapper component to make a simpler API:
-
-```jsx
-// MapView.js
-
-class MapView extends React.Component {
-  _onRegionChange = (event) => {
-    if (!this.props.onRegionChange) {
-      return;
-    }
-
-    // process raw event...
-    this.props.onRegionChange(event.nativeEvent);
-  }
-  render() {
-    return (
-      <RNTMap
-        {...this.props}
-        onRegionChange={this._onRegionChange}
-      />
-    );
-  }
-}
-MapView.propTypes = {
-  /**
-   * Callback that is called continuously when the user is dragging the map.
-   */
-  onRegionChange: PropTypes.func,
-  ...
-};
-
-// MyApp.js
-
-class MyApp extends React.Component {
-  onRegionChange(event) {
-    // Do stuff with event.region.latitude, etc.
-  }
-
-  render() {
-    var region = {
-      latitude: 37.48,
-      longitude: -122.16,
-      latitudeDelta: 0.1,
-      longitudeDelta: 0.1,
-    };
-    return (
-      <MapView
-        region={region}
-        zoomEnabled={false}
-        onRegionChange={this.onRegionChange}
-      />
-    );
-  }
-}
-```
-
-## Handling multiple native views
-
-A React Native view can have more than one child view in the view tree eg.
-
-```jsx
-<View>
-  <MyNativeView />
-  <MyNativeView />
-  <Button />
-</View>
-```
-
-In this example, the class `MyNativeView` is a wrapper for a `NativeComponent` and exposes methods, which will be called on the iOS platform. `MyNativeView` is defined in `MyNativeView.ios.js` and contains proxy methods of `NativeComponent`.
-
-When the user interacts with the component, like clicking the button, the `backgroundColor` of `MyNativeView` changes. In this case `UIManager` would not know which `MyNativeView` should be handled and which one should change `backgroundColor`. Below you will find a solution to this problem:
-
-```jsx
-<View>
-  <MyNativeView ref={this.myNativeReference}>/>
-  <MyNativeView ref={this.myNativeReference2}>/>
-  <Button onPress={() => { this.myNativeReference.callNativeMethod() }}/>
-</View>
-```
-
-Now the above component has a reference to a particular `MyNativeView` which allows us to use a specific instance of `MyNativeView`. Now the button can control which `MyNativeView` should change its `backgroundColor`. In this example let's assume that `callNativeMethod` changes `backgroundColor`.
-
-`MyNativeView.ios.js` contains code as follow:
-
-```jsx
-class MyNativeView extends React.Component<> {
-  callNativeMethod = () => {
-    UIManager.dispatchViewManagerCommand(
-      ReactNative.findNodeHandle(this),
-      UIManager.getViewManagerConfig('RNCMyNativeView').Commands
-        .callNativeMethod,
-      [],
-    );
-  };
-
-  render() {
-    return <NativeComponent ref={NATIVE_COMPONENT_REF} />;
-  }
-}
-```
-
-`callNativeMethod` is our custom iOS method which for example changes the `backgroundColor` which is exposed through `MyNativeView`. This method uses `UIManager.dispatchViewManagerCommand` which needs 3 parameters:
-
-- (nonnull NSNumber \*)reactTag  -  id of react view.
-- commandID:(NSInteger)commandID  -  Id of the native method that should be called
-- commandArgs:(NSArray<id> \*)commandArgs  -  Args of the native method that we can pass from JS to native.
-
-`RNCMyNativeViewManager.m`
-
-```objectivec
-#import <React/RCTViewManager.h>
-#import <React/RCTUIManager.h>
-#import <React/RCTLog.h>
-
-RCT_EXPORT_METHOD(callNativeMethod:(nonnull NSNumber*) reactTag) {
-    [self.bridge.uiManager addUIBlock:^(RCTUIManager *uiManager, NSDictionary<NSNumber *,UIView *> *viewRegistry) {
-        NativeView *view = viewRegistry[reactTag];
-        if (!view || ![view isKindOfClass:[NativeView class]]) {
-            RCTLogError(@"Cannot find NativeView with tag #%@", reactTag);
-            return;
-        }
-        [view callNativeMethod];
-    }];
-
-}
-```
-
-Here the `callNativeMethod` is defined in the `RNCMyNativeViewManager.m` file and contains only one parameter which is `(nonnull NSNumber*) reactTag`. This exported function will find a particular view using `addUIBlock` which contains the `viewRegistry` parameter and returns the component based on `reactTag` allowing it to call the method on the correct component.
-
-## Styles
-
-Since all our native react views are subclasses of `UIView`, most style attributes will work like you would expect out of the box. Some components will want a default style, however, for example `UIDatePicker` which is a fixed size. This default style is important for the layout algorithm to work as expected, but we also want to be able to override the default style when using the component. `DatePickerIOS` does this by wrapping the native component in an extra view, which has flexible styling, and using a fixed style (which is generated with constants passed in from native) on the inner native component:
-
-```jsx
-// DatePickerIOS.ios.js
-
-import { UIManager } from 'react-native';
-var RCTDatePickerIOSConsts = UIManager.RCTDatePicker.Constants;
-...
-  render: function() {
-    return (
-      <View style={this.props.style}>
-        <RCTDatePickerIOS
-          ref={DATEPICKER}
-          style={styles.rkDatePickerIOS}
-          ...
-        />
-      </View>
-    );
-  }
-});
-
-var styles = StyleSheet.create({
-  rkDatePickerIOS: {
-    height: RCTDatePickerIOSConsts.ComponentHeight,
-    width: RCTDatePickerIOSConsts.ComponentWidth,
-  },
-});
-```
-
-The `RCTDatePickerIOSConsts` constants are exported from native by grabbing the actual frame of the native component like so:
-
-```objectivec
-// RCTDatePickerManager.m
-
-- (NSDictionary *)constantsToExport
-{
-  UIDatePicker *dp = [[UIDatePicker alloc] init];
-  [dp layoutIfNeeded];
-
-  return @{
-    @"ComponentHeight": @(CGRectGetHeight(dp.frame)),
-    @"ComponentWidth": @(CGRectGetWidth(dp.frame)),
-    @"DatePickerModes": @{
-      @"time": @(UIDatePickerModeTime),
-      @"date": @(UIDatePickerModeDate),
-      @"datetime": @(UIDatePickerModeDateAndTime),
-    }
-  };
-}
-```
-
-This guide covered many of the aspects of bridging over custom native components, but there is even more you might need to consider, such as custom hooks for inserting and laying out subviews. If you want to go even deeper, check out the [source code](https://github.com/facebook/react-native/blob/master/React/Views) of some of the implemented components.
diff --git a/website/versioned_docs/version-0.60/native-modules-android.md b/website/versioned_docs/version-0.60/native-modules-android.md
deleted file mode 100644
index f87bee63fb7..00000000000
--- a/website/versioned_docs/version-0.60/native-modules-android.md
+++ /dev/null
@@ -1,484 +0,0 @@
----
-id: version-0.60-native-modules-android
-title: Native Modules
-original_id: native-modules-android
----
-
-Sometimes an app needs access to a platform API that React Native doesn't have a corresponding module for yet. Maybe you want to reuse some existing Java code without having to reimplement it in JavaScript, or write some high performance, multi-threaded code such as for image processing, a database, or any number of advanced extensions.
-
-We designed React Native such that it is possible for you to write real native code and have access to the full power of the platform. This is a more advanced feature and we don't expect it to be part of the usual development process, however it is essential that it exists. If React Native doesn't support a native feature that you need, you should be able to build it yourself.
-
-## Native Module Setup
-
-Native modules are usually distributed as npm packages, apart from the typical javascript files and resources they will contain an Android library project. This project is, from NPM's perspective just like any other media asset, meaning there isn't anything special about it from this point of view. To get the basic scaffolding make sure to read [Native Modules Setup](native-modules-setup) guide first.
-
-### Enable Gradle
-
-If you plan to make changes in Java code, we recommend enabling [Gradle Daemon](https://docs.gradle.org/2.9/userguide/gradle_daemon.html) to speed up builds.
-
-## The Toast Module
-
-This guide will use the [Toast](http://developer.android.com/reference/android/widget/Toast.html) example. Let's say we would like to be able to create a toast message from JavaScript.
-
-We start by creating a native module. A native module is a Java class that usually extends the `ReactContextBaseJavaModule` class and implements the functionality required by the JavaScript. Our goal here is to be able to write `ToastExample.show('Awesome', ToastExample.SHORT);` from JavaScript to display a short toast on the screen.
-
-Create a new Java Class named `ToastModule.java` inside `android/app/src/main/java/com/your-app-name/` folder with the content below:
-
-```java
-// ToastModule.java
-
-package com.your-app-name;
-
-import android.widget.Toast;
-
-import com.facebook.react.bridge.NativeModule;
-import com.facebook.react.bridge.ReactApplicationContext;
-import com.facebook.react.bridge.ReactContext;
-import com.facebook.react.bridge.ReactContextBaseJavaModule;
-import com.facebook.react.bridge.ReactMethod;
-
-import java.util.Map;
-import java.util.HashMap;
-
-public class ToastModule extends ReactContextBaseJavaModule {
-
-  private static final String DURATION_SHORT_KEY = "SHORT";
-  private static final String DURATION_LONG_KEY = "LONG";
-
-  ToastModule(ReactApplicationContext reactContext) {
-    super(reactContext);
-  }
-}
-```
-
-`ReactContextBaseJavaModule` requires that a method called `getName` is implemented. The purpose of this method is to return the string name of the `NativeModule` which represents this class in JavaScript. So here we will call this `ToastExample` so that we can access it through `React.NativeModules.ToastExample` in JavaScript.
-
-```java
-  @Override
-  public String getName() {
-    return "ToastExample";
-  }
-```
-
-An optional method called `getConstants` returns the constant values exposed to JavaScript. Its implementation is not required but is very useful to key pre-defined values that need to be communicated from JavaScript to Java in sync.
-
-```java
-  @Override
-  public Map<String, Object> getConstants() {
-    final Map<String, Object> constants = new HashMap<>();
-    constants.put(DURATION_SHORT_KEY, Toast.LENGTH_SHORT);
-    constants.put(DURATION_LONG_KEY, Toast.LENGTH_LONG);
-    return constants;
-  }
-```
-
-To expose a method to JavaScript a Java method must be annotated using `@ReactMethod`. The return type of bridge methods is always `void`. React Native bridge is asynchronous, so the only way to pass a result to JavaScript is by using callbacks or emitting events (see below).
-
-```java
-  @ReactMethod
-  public void show(String message, int duration) {
-    Toast.makeText(getReactApplicationContext(), message, duration).show();
-  }
-```
-
-### Argument Types
-
-The following argument types are supported for methods annotated with `@ReactMethod` and they directly map to their JavaScript equivalents
-
-```
-Boolean -> Bool
-Integer -> Number
-Double -> Number
-Float -> Number
-String -> String
-Callback -> function
-ReadableMap -> Object
-ReadableArray -> Array
-```
-
-Read more about [ReadableMap](https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/bridge/ReadableMap.java) and [ReadableArray](https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/bridge/ReadableArray.java)
-
-### Register the Module
-
-The last step within Java is to register the Module; this happens in the `createNativeModules` of your apps package. If a module is not registered it will not be available from JavaScript.
-
-create a new Java Class named `CustomToastPackage.java` inside `android/app/src/main/java/com/your-app-name/` folder with the content below:
-
-```java
-// CustomToastPackage.java
-
-package com.your-app-name;
-
-import com.facebook.react.ReactPackage;
-import com.facebook.react.bridge.NativeModule;
-import com.facebook.react.bridge.ReactApplicationContext;
-import com.facebook.react.uimanager.ViewManager;
-
-import java.util.ArrayList;
-import java.util.Collections;
-import java.util.List;
-
-public class CustomToastPackage implements ReactPackage {
-
-  @Override
-  public List<ViewManager> createViewManagers(ReactApplicationContext reactContext) {
-    return Collections.emptyList();
-  }
-
-  @Override
-  public List<NativeModule> createNativeModules(
-                              ReactApplicationContext reactContext) {
-    List<NativeModule> modules = new ArrayList<>();
-
-    modules.add(new ToastModule(reactContext));
-
-    return modules;
-  }
-
-}
-```
-
-The package needs to be provided in the `getPackages` method of the `MainApplication.java` file. This file exists under the android folder in your react-native application directory. The path to this file is: `android/app/src/main/java/com/your-app-name/MainApplication.java`.
-
-```java
-// MainApplication.java
-
-...
-import com.your-app-name.CustomToastPackage; // <-- Add this line with your package name.
-...
-
-protected List<ReactPackage> getPackages() {
-  @SuppressWarnings("UnnecessaryLocalVariable")
-  List<ReactPackage> packages = new PackageList(this).getPackages();
-  // Packages that cannot be autolinked yet can be added manually here, for example:
-  // packages.add(new MyReactNativePackage());
-  packages.add(new CustomToastPackage()); // <-- Add this line with your package name.
-  return packages;
-}
-```
-
-To make it simpler to access your new functionality from JavaScript, it is common to wrap the native module in a JavaScript module. This is not necessary but saves the consumers of your library the need to pull it off of `NativeModules` each time. This JavaScript file also becomes a good location for you to add any JavaScript side functionality.
-
-Create a new JavaScript file named `ToastExample.js` with the content below:
-
-```jsx
-/**
- * This exposes the native ToastExample module as a JS module. This has a
- * function 'show' which takes the following parameters:
- *
- * 1. String message: A string with the text to toast
- * 2. int duration: The duration of the toast. May be ToastExample.SHORT or
- *    ToastExample.LONG
- */
-import {NativeModules} from 'react-native';
-module.exports = NativeModules.ToastExample;
-```
-
-Now, from your other JavaScript file you can call the method like this:
-
-```jsx
-import ToastExample from './ToastExample';
-
-ToastExample.show('Awesome', ToastExample.SHORT);
-```
-
-Please make sure this JavaScript is in the same hierarchy as `ToastExample.js`.
-
-## Beyond Toasts
-
-### Callbacks
-
-Native modules also support a special kind of argument - a callback. In most cases it is used to provide the function call result to JavaScript.
-
-```java
-import com.facebook.react.bridge.Callback;
-
-public class UIManagerModule extends ReactContextBaseJavaModule {
-
-...
-
-  @ReactMethod
-  public void measureLayout(
-      int tag,
-      int ancestorTag,
-      Callback errorCallback,
-      Callback successCallback) {
-    try {
-      measureLayout(tag, ancestorTag, mMeasureBuffer);
-      float relativeX = PixelUtil.toDIPFromPixel(mMeasureBuffer[0]);
-      float relativeY = PixelUtil.toDIPFromPixel(mMeasureBuffer[1]);
-      float width = PixelUtil.toDIPFromPixel(mMeasureBuffer[2]);
-      float height = PixelUtil.toDIPFromPixel(mMeasureBuffer[3]);
-      successCallback.invoke(relativeX, relativeY, width, height);
-    } catch (IllegalViewOperationException e) {
-      errorCallback.invoke(e.getMessage());
-    }
-  }
-
-...
-```
-
-This method would be accessed in JavaScript using:
-
-```jsx
-UIManager.measureLayout(
-  100,
-  100,
-  (msg) => {
-    console.log(msg);
-  },
-  (x, y, width, height) => {
-    console.log(x + ':' + y + ':' + width + ':' + height);
-  },
-);
-```
-
-A native module is supposed to invoke its callback only once. It can, however, store the callback and invoke it later.
-
-It is very important to highlight that the callback is not invoked immediately after the native function completes - remember that bridge communication is asynchronous, and this too is tied to the run loop.
-
-### Promises
-
-Native modules can also fulfill a promise, which can simplify your JavaScript, especially when using ES2016's `async/await` syntax. When the last parameter of a bridged native method is a `Promise`, its corresponding JS method will return a JS Promise object.
-
-Refactoring the above code to use a promise instead of callbacks looks like this:
-
-```java
-import com.facebook.react.bridge.Promise;
-
-public class UIManagerModule extends ReactContextBaseJavaModule {
-
-...
-  private static final String E_LAYOUT_ERROR = "E_LAYOUT_ERROR";
-  @ReactMethod
-  public void measureLayout(
-      int tag,
-      int ancestorTag,
-      Promise promise) {
-    try {
-      measureLayout(tag, ancestorTag, mMeasureBuffer);
-
-      WritableMap map = Arguments.createMap();
-
-      map.putDouble("relativeX", PixelUtil.toDIPFromPixel(mMeasureBuffer[0]));
-      map.putDouble("relativeY", PixelUtil.toDIPFromPixel(mMeasureBuffer[1]));
-      map.putDouble("width", PixelUtil.toDIPFromPixel(mMeasureBuffer[2]));
-      map.putDouble("height", PixelUtil.toDIPFromPixel(mMeasureBuffer[3]));
-
-      promise.resolve(map);
-    } catch (IllegalViewOperationException e) {
-      promise.reject(E_LAYOUT_ERROR, e);
-    }
-  }
-
-...
-```
-
-The JavaScript counterpart of this method returns a Promise. This means you can use the `await` keyword within an async function to call it and wait for its result:
-
-```jsx
-async function measureLayout() {
-  try {
-    var {relativeX, relativeY, width, height} = await UIManager.measureLayout(
-      100,
-      100,
-    );
-
-    console.log(relativeX + ':' + relativeY + ':' + width + ':' + height);
-  } catch (e) {
-    console.error(e);
-  }
-}
-
-measureLayout();
-```
-
-### Threading
-
-Native modules should not have any assumptions about what thread they are being called on, as the current assignment is subject to change in the future. If a blocking call is required, the heavy work should be dispatched to an internally managed worker thread, and any callbacks distributed from there.
-
-### Sending Events to JavaScript
-
-Native modules can signal events to JavaScript without being invoked directly. The easiest way to do this is to use the `RCTDeviceEventEmitter` which can be obtained from the `ReactContext` as in the code snippet below.
-
-```java
-...
-import com.facebook.react.modules.core.DeviceEventManagerModule;
-...
-private void sendEvent(ReactContext reactContext,
-                       String eventName,
-                       @Nullable WritableMap params) {
-  reactContext
-      .getJSModule(DeviceEventManagerModule.RCTDeviceEventEmitter.class)
-      .emit(eventName, params);
-}
-...
-WritableMap params = Arguments.createMap();
-...
-sendEvent(reactContext, "keyboardWillShow", params);
-```
-
-JavaScript modules can then register to receive events by `addListenerOn` using the `Subscribable` mixin.
-
-```jsx
-import { DeviceEventEmitter } from 'react-native';
-...
-
-var ScrollResponderMixin = {
-  mixins: [Subscribable.Mixin],
-
-
-  componentDidMount() {
-    ...
-    this.addListenerOn(DeviceEventEmitter,
-                       'keyboardWillShow',
-                       this.scrollResponderKeyboardWillShow);
-    ...
-  },
-  scrollResponderKeyboardWillShow:function(e: Event) {
-    this.keyboardWillOpenTo = e;
-    this.props.onKeyboardWillShow && this.props.onKeyboardWillShow(e);
-  },
-```
-
-You can also directly use the `DeviceEventEmitter` module to listen for events.
-
-```jsx
-...
-componentDidMount() {
-  this.subscription = DeviceEventEmitter.addListener('keyboardWillShow', function(e: Event) {
-    // handle event
-  });
-}
-
-componentWillUnmount() {
-  // When you want to stop listening to new events, simply call .remove() on the subscription
-  this.subscription.remove();
-}
-...
-```
-
-### Getting activity result from `startActivityForResult`
-
-You'll need to listen to `onActivityResult` if you want to get results from an activity you started with `startActivityForResult`. To do this, you must extend `BaseActivityEventListener` or implement `ActivityEventListener`. The former is preferred as it is more resilient to API changes. Then, you need to register the listener in the module's constructor,
-
-```java
-reactContext.addActivityEventListener(mActivityResultListener);
-```
-
-Now you can listen to `onActivityResult` by implementing the following method:
-
-```java
-@Override
-public void onActivityResult(
-  final Activity activity,
-  final int requestCode,
-  final int resultCode,
-  final Intent intent) {
-  // Your logic here
-}
-```
-
-We will implement a simple image picker to demonstrate this. The image picker will expose the method `pickImage` to JavaScript, which will return the path of the image when called.
-
-```java
-public class ImagePickerModule extends ReactContextBaseJavaModule {
-
-  private static final int IMAGE_PICKER_REQUEST = 467081;
-  private static final String E_ACTIVITY_DOES_NOT_EXIST = "E_ACTIVITY_DOES_NOT_EXIST";
-  private static final String E_PICKER_CANCELLED = "E_PICKER_CANCELLED";
-  private static final String E_FAILED_TO_SHOW_PICKER = "E_FAILED_TO_SHOW_PICKER";
-  private static final String E_NO_IMAGE_DATA_FOUND = "E_NO_IMAGE_DATA_FOUND";
-
-  private Promise mPickerPromise;
-
-  private final ActivityEventListener mActivityEventListener = new BaseActivityEventListener() {
-
-    @Override
-    public void onActivityResult(Activity activity, int requestCode, int resultCode, Intent intent) {
-      if (requestCode == IMAGE_PICKER_REQUEST) {
-        if (mPickerPromise != null) {
-          if (resultCode == Activity.RESULT_CANCELED) {
-            mPickerPromise.reject(E_PICKER_CANCELLED, "Image picker was cancelled");
-          } else if (resultCode == Activity.RESULT_OK) {
-            Uri uri = intent.getData();
-
-            if (uri == null) {
-              mPickerPromise.reject(E_NO_IMAGE_DATA_FOUND, "No image data found");
-            } else {
-              mPickerPromise.resolve(uri.toString());
-            }
-          }
-
-          mPickerPromise = null;
-        }
-      }
-    }
-  };
-
-  ImagePickerModule(ReactApplicationContext reactContext) {
-    super(reactContext);
-
-    // Add the listener for `onActivityResult`
-    reactContext.addActivityEventListener(mActivityEventListener);
-  }
-
-  @Override
-  public String getName() {
-    return "ImagePickerModule";
-  }
-
-  @ReactMethod
-  public void pickImage(final Promise promise) {
-    Activity currentActivity = getCurrentActivity();
-
-    if (currentActivity == null) {
-      promise.reject(E_ACTIVITY_DOES_NOT_EXIST, "Activity doesn't exist");
-      return;
-    }
-
-    // Store the promise to resolve/reject when picker returns data
-    mPickerPromise = promise;
-
-    try {
-      final Intent galleryIntent = new Intent(Intent.ACTION_PICK);
-
-      galleryIntent.setType("image/*");
-
-      final Intent chooserIntent = Intent.createChooser(galleryIntent, "Pick an image");
-
-      currentActivity.startActivityForResult(chooserIntent, IMAGE_PICKER_REQUEST);
-    } catch (Exception e) {
-      mPickerPromise.reject(E_FAILED_TO_SHOW_PICKER, e);
-      mPickerPromise = null;
-    }
-  }
-}
-```
-
-### Listening to LifeCycle events
-
-Listening to the activity's LifeCycle events such as `onResume`, `onPause` etc. is very similar to how we implemented `ActivityEventListener`. The module must implement `LifecycleEventListener`. Then, you need to register a listener in the module's constructor,
-
-```java
-reactContext.addLifecycleEventListener(this);
-```
-
-Now you can listen to the activity's LifeCycle events by implementing the following methods:
-
-```java
-@Override
-public void onHostResume() {
-    // Activity `onResume`
-}
-
-@Override
-public void onHostPause() {
-    // Activity `onPause`
-}
-
-@Override
-public void onHostDestroy() {
-    // Activity `onDestroy`
-}
-```
diff --git a/website/versioned_docs/version-0.60/native-modules-setup.md b/website/versioned_docs/version-0.60/native-modules-setup.md
deleted file mode 100644
index edf819853bc..00000000000
--- a/website/versioned_docs/version-0.60/native-modules-setup.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-id: version-0.60-native-modules-setup
-title: Native Modules Setup
-original_id: native-modules-setup
----
-
-Native modules are usually distributed as npm packages, except that on top of the usual Javascript they will include some native code per platform. To understand more about npm packages you may find [this guide](https://docs.npmjs.com/getting-started/publishing-npm-packages) useful.
-
-To get set up with the basic project structure for a native module we will use a third party tool [create-react-native-module](https://github.com/brodybits/create-react-native-module). You can go ahead further and dive deep into how that library works, for our needs we will just need:
-
-```
-$ yarn global add create-react-native-module
-$ create-react-native-module MyLibrary
-```
-
-Where MyLibrary is the name you would like for the new module. After doing this you will navigate into `MyLibrary` folder and install the npm package to be locally available for your computer by doing:
-
-```
-$ yarn install
-```
-
-After this is done you can go to your main react app folder (which you created by doing `react-native init MyApp`)
-
-- add your newly created module as a dependency in your package.json
-- run `yarn install` to bring it along from your local npm repository.
-
-After this, you will be able to continue to [Native Modules (iOS)](native-modules-ios) or [Native Modules (Android)](native-modules-android) to add in some code. Make sure to read the README.md within your `MyLibrary` Directory for platform-specific instructions on how to include the project.
diff --git a/website/versioned_docs/version-0.60/navigation.md b/website/versioned_docs/version-0.60/navigation.md
deleted file mode 100644
index 80ea44cad42..00000000000
--- a/website/versioned_docs/version-0.60/navigation.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: version-0.60-navigation
-title: Navigating Between Screens
-original_id: navigation
----
-
-Mobile apps are rarely made up of a single screen. Managing the presentation of, and transition between, multiple screens is typically handled by what is known as a navigator.
-
-This guide covers the various navigation components available in React Native. If you are just getting started with navigation, you will probably want to use [React Navigation](navigation.md#react-navigation). React Navigation provides an easy to use navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both iOS and Android.
-
-If you'd like to achieve a native look and feel on both iOS and Android, or you're integrating React Native into an app that already manages navigation natively, the following library provides native navigation on both platforms: [react-native-navigation](https://github.com/wix/react-native-navigation).
-
-## React Navigation
-
-The community solution to navigation is a standalone library that allows developers to set up the screens of an app with just a few lines of code.
-
-The first step is to install in your project:
-
-```
-npm install --save react-navigation
-```
-
-The second step is to install react-native-gesture-handler
-
-```
-yarn add react-native-gesture-handler
-# or with npm
-# npm install --save react-native-gesture-handler
-```
-
-Then you can quickly create an app with a home screen and a profile screen:
-
-```jsx
-import {createStackNavigator, createAppContainer} from 'react-navigation';
-
-const MainNavigator = createStackNavigator({
-  Home: {screen: HomeScreen},
-  Profile: {screen: ProfileScreen},
-});
-
-const App = createAppContainer(MainNavigator);
-
-export default App;
-```
-
-Each screen component can set navigation options such as the header title. It can use action creators on the `navigation` prop to link to other screens:
-
-```jsx
-class HomeScreen extends React.Component {
-  static navigationOptions = {
-    title: 'Welcome',
-  };
-  render() {
-    const {navigate} = this.props.navigation;
-    return (
-      <Button
-        title="Go to Jane's profile"
-        onPress={() => navigate('Profile', {name: 'Jane'})}
-      />
-    );
-  }
-}
-```
-
-React Navigation routers make it easy to override navigation logic. Because routers can be nested inside each other, developers can override navigation logic for one area of the app without making widespread changes.
-
-The views in React Navigation use native components and the [`Animated`](animated.md) library to deliver 60fps animations that are run on the native thread. Plus, the animations and gestures can be easily customized.
-
-For a complete intro to React Navigation, follow the [React Navigation Getting Started Guide](https://reactnavigation.org/docs/getting-started.html), or browse other docs such as the [Intro to Navigators](https://expo.io/@react-navigation/NavigationPlayground).
diff --git a/website/versioned_docs/version-0.60/network.md b/website/versioned_docs/version-0.60/network.md
deleted file mode 100644
index a521146002c..00000000000
--- a/website/versioned_docs/version-0.60/network.md
+++ /dev/null
@@ -1,193 +0,0 @@
----
-id: version-0.60-network
-title: Networking
-original_id: network
----
-
-Many mobile apps need to load resources from a remote URL. You may want to make a POST request to a REST API, or you may simply need to fetch a chunk of static content from another server.
-
-## Using Fetch
-
-React Native provides the [Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) for your networking needs. Fetch will seem familiar if you have used `XMLHttpRequest` or other networking APIs before. You may refer to MDN's guide on [Using Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch) for additional information.
-
-#### Making requests
-
-In order to fetch content from an arbitrary URL, just pass the URL to fetch:
-
-```jsx
-fetch('https://mywebsite.com/mydata.json');
-```
-
-Fetch also takes an optional second argument that allows you to customize the HTTP request. You may want to specify additional headers, or make a POST request:
-
-```jsx
-fetch('https://mywebsite.com/endpoint/', {
-  method: 'POST',
-  headers: {
-    Accept: 'application/json',
-    'Content-Type': 'application/json',
-  },
-  body: JSON.stringify({
-    firstParam: 'yourValue',
-    secondParam: 'yourOtherValue',
-  }),
-});
-```
-
-Take a look at the [Fetch Request docs](https://developer.mozilla.org/en-US/docs/Web/API/Request) for a full list of properties.
-
-#### Handling the response
-
-The above examples show how you can make a request. In many cases, you will want to do something with the response.
-
-Networking is an inherently asynchronous operation. Fetch methods will return a [Promise](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) that makes it straightforward to write code that works in an asynchronous manner:
-
-```jsx
-function getMoviesFromApiAsync() {
-  return fetch('https://facebook.github.io/react-native/movies.json')
-    .then((response) => response.json())
-    .then((responseJson) => {
-      return responseJson.movies;
-    })
-    .catch((error) => {
-      console.error(error);
-    });
-}
-```
-
-You can also use the proposed ES2017 `async`/`await` syntax in a React Native app:
-
-```jsx
-async function getMoviesFromApi() {
-  try {
-    let response = await fetch(
-      'https://facebook.github.io/react-native/movies.json',
-    );
-    let responseJson = await response.json();
-    return responseJson.movies;
-  } catch (error) {
-    console.error(error);
-  }
-}
-```
-
-Don't forget to catch any errors that may be thrown by `fetch`, otherwise they will be dropped silently.
-
-```SnackPlayer name=Fetch%20Example
-import React from 'react';
-import { FlatList, ActivityIndicator, Text, View  } from 'react-native';
-
-export default class FetchExample extends React.Component {
-
-  constructor(props){
-    super(props);
-    this.state ={ isLoading: true}
-  }
-
-  componentDidMount(){
-    return fetch('https://facebook.github.io/react-native/movies.json')
-      .then((response) => response.json())
-      .then((responseJson) => {
-
-        this.setState({
-          isLoading: false,
-          dataSource: responseJson.movies,
-        }, function(){
-
-        });
-
-      })
-      .catch((error) =>{
-        console.error(error);
-      });
-  }
-
-
-
-  render(){
-
-    if(this.state.isLoading){
-      return(
-        <View style={{flex: 1, padding: 20}}>
-          <ActivityIndicator/>
-        </View>
-      )
-    }
-
-    return(
-      <View style={{flex: 1, paddingTop:20}}>
-        <FlatList
-          data={this.state.dataSource}
-          renderItem={({item}) => <Text>{item.title}, {item.releaseYear}</Text>}
-          keyExtractor={({id}, index) => id}
-        />
-      </View>
-    );
-  }
-}
-```
-
-> By default, iOS will block any request that's not encrypted using [SSL](https://hosting.review/web-hosting-glossary/#12). If you need to fetch from a cleartext URL (one that begins with `http`) you will first need to [add an App Transport Security exception](integration-with-existing-apps.md#test-your-integration). If you know ahead of time what domains you will need access to, it is more secure to add exceptions just for those domains; if the domains are not known until runtime you can [disable ATS completely](integration-with-existing-apps.md#app-transport-security). Note however that from January 2017, [Apple's App Store review will require reasonable justification for disabling ATS](https://forums.developer.apple.com/thread/48979). See [Apple's documentation](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW33) for more information.
-
-### Using Other Networking Libraries
-
-The [XMLHttpRequest API](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest) is built into React Native. This means that you can use third party libraries such as [frisbee](https://github.com/niftylettuce/frisbee) or [axios](https://github.com/mzabriskie/axios) that depend on it, or you can use the XMLHttpRequest API directly if you prefer.
-
-```jsx
-var request = new XMLHttpRequest();
-request.onreadystatechange = (e) => {
-  if (request.readyState !== 4) {
-    return;
-  }
-
-  if (request.status === 200) {
-    console.log('success', request.responseText);
-  } else {
-    console.warn('error');
-  }
-};
-
-request.open('GET', 'https://mywebsite.com/endpoint/');
-request.send();
-```
-
-> The security model for XMLHttpRequest is different than on web as there is no concept of [CORS](http://en.wikipedia.org/wiki/Cross-origin_resource_sharing) in native apps.
-
-## WebSocket Support
-
-React Native also supports [WebSockets](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket), a protocol which provides full-duplex communication channels over a single TCP connection.
-
-```jsx
-var ws = new WebSocket('ws://host.com/path');
-
-ws.onopen = () => {
-  // connection opened
-  ws.send('something'); // send a message
-};
-
-ws.onmessage = (e) => {
-  // a message was received
-  console.log(e.data);
-};
-
-ws.onerror = (e) => {
-  // an error occurred
-  console.log(e.message);
-};
-
-ws.onclose = (e) => {
-  // connection closed
-  console.log(e.code, e.reason);
-};
-```
-
-## Known Issues with `fetch` and cookie based authentication
-
-The following options are currently not working with `fetch`
-
-- `redirect:manual`
-- `credentials:omit`
-
-* Having same name headers on Android will result in only the latest one being present. A temporary solution can be found here: https://github.com/facebook/react-native/issues/18837#issuecomment-398779994.
-* Cookie based authentication is currently unstable. You can view some of the issues raised here: https://github.com/facebook/react-native/issues/23185
-* As a minimum on iOS, when redirected through a `302`, if a `Set-Cookie` header is present, the cookie is not set properly. Since the redirect cannot be handled manually this might cause a scenario where infinite requests occur if the redirect is the result of an expired session.
diff --git a/website/versioned_docs/version-0.60/performance.md b/website/versioned_docs/version-0.60/performance.md
deleted file mode 100644
index 40de416545e..00000000000
--- a/website/versioned_docs/version-0.60/performance.md
+++ /dev/null
@@ -1,431 +0,0 @@
----
-id: version-0.60-performance
-title: Performance
-original_id: performance
----
-
-A compelling reason for using React Native instead of WebView-based tools is to achieve 60 frames per second and a native look and feel to your apps. Where possible, we would like for React Native to do the right thing and help you to focus on your app instead of performance optimization, but there are areas where we're not quite there yet, and others where React Native (similar to writing native code directly) cannot possibly determine the best way to optimize for you and so manual intervention will be necessary. We try our best to deliver buttery-smooth UI performance by default, but sometimes that just isn't possible.
-
-This guide is intended to teach you some basics to help you to [troubleshoot performance issues](performance.md#profiling), as well as discuss [common sources of problems and their suggested solutions](performance.md#common-sources-of-performance-problems).
-
-## What you need to know about frames
-
-Your grandparents' generation called movies ["moving pictures"](https://www.youtube.com/watch?v=F1i40rnpOsA) for a reason: realistic motion in video is an illusion created by quickly changing static images at a consistent speed. We refer to each of these images as frames. The number of frames that is displayed each second has a direct impact on how smooth and ultimately life-like a video (or user interface) seems to be. iOS devices display 60 frames per second, which gives you and the UI system about 16.67ms to do all of the work needed to generate the static image (frame) that the user will see on the screen for that interval. If you are unable to do the work necessary to generate that frame within the allotted 16.67ms, then you will "drop a frame" and the UI will appear unresponsive.
-
-Now to confuse the matter a little bit, open up the developer menu in your app and toggle `Show Perf Monitor`. You will notice that there are two different frame rates.
-
-![](/react-native/docs/assets/PerfUtil.png)
-
-### JS frame rate (JavaScript thread)
-
-For most React Native applications, your business logic will run on the JavaScript thread. This is where your React application lives, API calls are made, touch events are processed, etc... Updates to native-backed views are batched and sent over to the native side at the end of each iteration of the event loop, before the frame deadline (if all goes well). If the JavaScript thread is unresponsive for a frame, it will be considered a dropped frame. For example, if you were to call `this.setState` on the root component of a complex application and it resulted in re-rendering computationally expensive component subtrees, it's conceivable that this might take 200ms and result in 12 frames being dropped. Any animations controlled by JavaScript would appear to freeze during that time. If anything takes longer than 100ms, the user will feel it.
-
-This often happens during `Navigator` transitions: when you push a new route, the JavaScript thread needs to render all of the components necessary for the scene in order to send over the proper commands to the native side to create the backing views. It's common for the work being done here to take a few frames and cause [jank](http://jankfree.org/) because the transition is controlled by the JavaScript thread. Sometimes components will do additional work on `componentDidMount`, which might result in a second stutter in the transition.
-
-Another example is responding to touches: if you are doing work across multiple frames on the JavaScript thread, you might notice a delay in responding to `TouchableOpacity`, for example. This is because the JavaScript thread is busy and cannot process the raw touch events sent over from the main thread. As a result, `TouchableOpacity` cannot react to the touch events and command the native view to adjust its opacity.
-
-### UI frame rate (main thread)
-
-Many people have noticed that performance of `NavigatorIOS` is better out of the box than `Navigator`. The reason for this is that the animations for the transitions are done entirely on the main thread, and so they are not interrupted by frame drops on the JavaScript thread.
-
-Similarly, you can happily scroll up and down through a `ScrollView` when the JavaScript thread is locked up because the `ScrollView` lives on the main thread. The scroll events are dispatched to the JS thread, but their receipt is not necessary for the scroll to occur.
-
-## Common sources of performance problems
-
-### Running in development mode (`dev=true`)
-
-JavaScript thread performance suffers greatly when running in dev mode. This is unavoidable: a lot more work needs to be done at runtime to provide you with good warnings and error messages, such as validating propTypes and various other assertions. Always make sure to test performance in [release builds](running-on-device.md#building-your-app-for-production).
-
-### Using `console.log` statements
-
-When running a bundled app, these statements can cause a big bottleneck in the JavaScript thread. This includes calls from debugging libraries such as [redux-logger](https://github.com/evgenyrodionov/redux-logger), so make sure to remove them before bundling. You can also use this [babel plugin](https://babeljs.io/docs/plugins/transform-remove-console/) that removes all the `console.*` calls. You need to install it first with `npm i babel-plugin-transform-remove-console --save-dev`, and then edit the `.babelrc` file under your project directory like this:
-
-```jsxon
-{
-  "env": {
-    "production": {
-      "plugins": ["transform-remove-console"]
-    }
-  }
-}
-```
-
-This will automatically remove all `console.*` calls in the release (production) versions of your project.
-
-### `ListView` initial rendering is too slow or scroll performance is bad for large lists
-
-Use the new [`FlatList`](flatlist.md) or [`SectionList`](sectionlist.md) component instead. Besides simplifying the API, the new list components also have significant performance enhancements, the main one being nearly constant memory usage for any number of rows.
-
-If your [`FlatList`](flatlist.md) is rendering slow, be sure that you've implemented [`getItemLayout`](https://facebook.github.io/react-native/docs/flatlist.html#getitemlayout) to optimize rendering speed by skipping measurement of the rendered items.
-
-### JS FPS plunges when re-rendering a view that hardly changes
-
-If you are using a ListView, you must provide a `rowHasChanged` function that can reduce a lot of work by quickly determining whether or not a row needs to be re-rendered. If you are using immutable data structures, this would be as simple as a reference equality check.
-
-Similarly, you can implement `shouldComponentUpdate` and indicate the exact conditions under which you would like the component to re-render. If you write pure components (where the return value of the render function is entirely dependent on props and state), you can leverage PureComponent to do this for you. Once again, immutable data structures are useful to keep this fast -- if you have to do a deep comparison of a large list of objects, it may be that re-rendering your entire component would be quicker, and it would certainly require less code.
-
-### Dropping JS thread FPS because of doing a lot of work on the JavaScript thread at the same time
-
-"Slow Navigator transitions" is the most common manifestation of this, but there are other times this can happen. Using InteractionManager can be a good approach, but if the user experience cost is too high to delay work during an animation, then you might want to consider LayoutAnimation.
-
-The Animated API currently calculates each keyframe on-demand on the JavaScript thread unless you [set `useNativeDriver: true`](https://facebook.github.io/react-native/blog/2017/02/14/using-native-driver-for-animated.html#how-do-i-use-this-in-my-app), while LayoutAnimation leverages Core Animation and is unaffected by JS thread and main thread frame drops.
-
-One case where I have used this is for animating in a modal (sliding down from top and fading in a translucent overlay) while initializing and perhaps receiving responses for several network requests, rendering the contents of the modal, and updating the view where the modal was opened from. See the Animations guide for more information about how to use LayoutAnimation.
-
-Caveats:
-
-- LayoutAnimation only works for fire-and-forget animations ("static" animations) -- if it must be interruptible, you will need to use `Animated`.
-
-### Moving a view on the screen (scrolling, translating, rotating) drops UI thread FPS
-
-This is especially true when you have text with a transparent background positioned on top of an image, or any other situation where alpha compositing would be required to re-draw the view on each frame. You will find that enabling `shouldRasterizeIOS` or `renderToHardwareTextureAndroid` can help with this significantly.
-
-Be careful not to overuse this or your memory usage could go through the roof. Profile your performance and memory usage when using these props. If you don't plan to move a view anymore, turn this property off.
-
-### Animating the size of an image drops UI thread FPS
-
-On iOS, each time you adjust the width or height of an Image component it is re-cropped and scaled from the original image. This can be very expensive, especially for large images. Instead, use the `transform: [{scale}]` style property to animate the size. An example of when you might do this is when you tap an image and zoom it in to full screen.
-
-### My TouchableX view isn't very responsive
-
-Sometimes, if we do an action in the same frame that we are adjusting the opacity or highlight of a component that is responding to a touch, we won't see that effect until after the `onPress` function has returned. If `onPress` does a `setState` that results in a lot of work and a few frames dropped, this may occur. A solution to this is to wrap any action inside of your `onPress` handler in `requestAnimationFrame`:
-
-```jsx
-handleOnPress() {
-  requestAnimationFrame(() => {
-    this.doExpensiveAction();
-  });
-}
-```
-
-### Slow navigator transitions
-
-As mentioned above, `Navigator` animations are controlled by the JavaScript thread. Imagine the "push from right" scene transition: each frame, the new scene is moved from the right to left, starting offscreen (let's say at an x-offset of 320) and ultimately settling when the scene sits at an x-offset of
-
-0. Each frame during this transition, the JavaScript thread needs to send a new x-offset to the main thread. If the JavaScript thread is locked up, it cannot do this and so no update occurs on that frame and the animation stutters.
-
-One solution to this is to allow for JavaScript-based animations to be offloaded to the main thread. If we were to do the same thing as in the above example with this approach, we might calculate a list of all x-offsets for the new scene when we are starting the transition and send them to the main thread to execute in an optimized way. Now that the JavaScript thread is freed of this responsibility, it's not a big deal if it drops a few frames while rendering the scene -- you probably won't even notice because you will be too distracted by the pretty transition.
-
-Solving this is one of the main goals behind the new [React Navigation](navigation.md) library. The views in React Navigation use native components and the [`Animated`](animated.md) library to deliver 60 FPS animations that are run on the native thread.
-
-## Profiling
-
-Use the built-in profiler to get detailed information about work done in the JavaScript thread and main thread side-by-side. Access it by selecting Perf Monitor from the Debug menu.
-
-For iOS, Instruments is an invaluable tool, and on Android you should learn to use [`systrace`](performance.md#profiling-android-ui-performance-with-systrace).
-
-But first, [**make sure that Development Mode is OFF!**](performance.md#running-in-development-mode-dev-true) You should see `__DEV__ === false, development-level warning are OFF, performance optimizations are ON` in your application logs.
-
-Another way to profile JavaScript is to use the Chrome profiler while debugging. This won't give you accurate results as the code is running in Chrome but will give you a general idea of where bottlenecks might be. Run the profiler under Chrome's `Performance` tab. A flame graph will appear under `User Timing`. To view more details in tabular format, click at the `Bottom Up` tab below and then select `DedicatedWorker Thread` at the top left menu.
-
-### Profiling Android UI Performance with `systrace`
-
-Android supports 10k+ different phones and is generalized to support software rendering: the framework architecture and need to generalize across many hardware targets unfortunately means you get less for free relative to iOS. But sometimes, there are things you can improve -- and many times it's not native code's fault at all!
-
-The first step for debugging this jank is to answer the fundamental question of where your time is being spent during each 16ms frame. For that, we'll be using a standard Android profiling tool called `systrace`.
-
-`systrace` is a standard Android marker-based profiling tool (and is installed when you install the Android platform-tools package). Profiled code blocks are surrounded by start/end markers which are then visualized in a colorful chart format. Both the Android SDK and React Native framework provide standard markers that you can visualize.
-
-#### 1. Collecting a trace
-
-First, connect a device that exhibits the stuttering you want to investigate to your computer via USB and get it to the point right before the navigation/animation you want to profile. Run `systrace` as follows:
-
-```
-$ <path_to_android_sdk>/platform-tools/systrace/systrace.py --time=10 -o trace.html sched gfx view -a <your_package_name>
-```
-
-A quick breakdown of this command:
-
-- `time` is the length of time the trace will be collected in seconds
-- `sched`, `gfx`, and `view` are the android SDK tags (collections of markers) we care about: `sched` gives you information about what's running on each core of your phone, `gfx` gives you graphics info such as frame boundaries, and `view` gives you information about measure, layout, and draw passes
-- `-a <your_package_name>` enables app-specific markers, specifically the ones built into the React Native framework. `your_package_name` can be found in the `AndroidManifest.xml` of your app and looks like `com.example.app`
-
-Once the trace starts collecting, perform the animation or interaction you care about. At the end of the trace, systrace will give you a link to the trace which you can open in your browser.
-
-#### 2. Reading the trace
-
-After opening the trace in your browser (preferably Chrome), you should see something like this:
-
-![Example](/react-native/docs/assets/SystraceExample.png)
-
-> **HINT**: Use the WASD keys to strafe and zoom
-
-If your trace .html file isn't opening correctly, check your browser console for the following:
-
-![ObjectObserveError](/react-native/docs/assets/ObjectObserveError.png)
-
-Since `Object.observe` was deprecated in recent browsers, you may have to open the file from the Google Chrome Tracing tool. You can do so by:
-
-- Opening tab in chrome chrome://tracing
-- Selecting load
-- Selecting the html file generated from the previous command.
-
-> **Enable VSync highlighting**
->
-> Check this checkbox at the top right of the screen to highlight the 16ms frame boundaries:
->
-> ![Enable VSync Highlighting](/react-native/docs/assets/SystraceHighlightVSync.png)
->
-> You should see zebra stripes as in the screenshot above. If you don't, try profiling on a different device: Samsung has been known to have issues displaying vsyncs while the Nexus series is generally pretty reliable.
-
-#### 3. Find your process
-
-Scroll until you see (part of) the name of your package. In this case, I was profiling `com.facebook.adsmanager`, which shows up as `book.adsmanager` because of silly thread name limits in the kernel.
-
-On the left side, you'll see a set of threads which correspond to the timeline rows on the right. There are a few threads we care about for our purposes: the UI thread (which has your package name or the name UI Thread), `mqt_js`, and `mqt_native_modules`. If you're running on Android 5+, we also care about the Render Thread.
-
-- **UI Thread.** This is where standard android measure/layout/draw happens. The thread name on the right will be your package name (in my case book.adsmanager) or UI Thread. The events that you see on this thread should look something like this and have to do with `Choreographer`, `traversals`, and `DispatchUI`:
-
-  ![UI Thread Example](/react-native/docs/assets/SystraceUIThreadExample.png)
-
-- **JS Thread.** This is where JavaScript is executed. The thread name will be either `mqt_js` or `<...>` depending on how cooperative the kernel on your device is being. To identify it if it doesn't have a name, look for things like `JSCall`, `Bridge.executeJSCall`, etc:
-
-  ![JS Thread Example](/react-native/docs/assets/SystraceJSThreadExample.png)
-
-- **Native Modules Thread.** This is where native module calls (e.g. the `UIManager`) are executed. The thread name will be either `mqt_native_modules` or `<...>`. To identify it in the latter case, look for things like `NativeCall`, `callJavaModuleMethod`, and `onBatchComplete`:
-
-  ![Native Modules Thread Example](/react-native/docs/assets/SystraceNativeModulesThreadExample.png)
-
-- **Bonus: Render Thread.** If you're using Android L (5.0) and up, you will also have a render thread in your application. This thread generates the actual OpenGL commands used to draw your UI. The thread name will be either `RenderThread` or `<...>`. To identify it in the latter case, look for things like `DrawFrame` and `queueBuffer`:
-
-  ![Render Thread Example](/react-native/docs/assets/SystraceRenderThreadExample.png)
-
-#### Identifying a culprit
-
-A smooth animation should look something like the following:
-
-![Smooth Animation](/react-native/docs/assets/SystraceWellBehaved.png)
-
-Each change in color is a frame -- remember that in order to display a frame, all our UI work needs to be done by the end of that 16ms period. Notice that no thread is working close to the frame boundary. An application rendering like this is rendering at 60 FPS.
-
-If you noticed chop, however, you might see something like this:
-
-![Choppy Animation from JS](/react-native/docs/assets/SystraceBadJS.png)
-
-Notice that the JS thread is executing basically all the time, and across frame boundaries! This app is not rendering at 60 FPS. In this case, **the problem lies in JS**.
-
-You might also see something like this:
-
-![Choppy Animation from UI](/react-native/docs/assets/SystraceBadUI.png)
-
-In this case, the UI and render threads are the ones that have work crossing frame boundaries. The UI that we're trying to render on each frame is requiring too much work to be done. In this case, **the problem lies in the native views being rendered**.
-
-At this point, you'll have some very helpful information to inform your next steps.
-
-#### Resolving JavaScript issues
-
-If you identified a JS problem, look for clues in the specific JS that you're executing. In the scenario above, we see `RCTEventEmitter` being called multiple times per frame. Here's a zoom-in of the JS thread from the trace above:
-
-![Too much JS](/react-native/docs/assets/SystraceBadJS2.png)
-
-This doesn't seem right. Why is it being called so often? Are they actually different events? The answers to these questions will probably depend on your product code. And many times, you'll want to look into [shouldComponentUpdate](https://reactjs.org/docs/react-component.html#shouldcomponentupdate).
-
-#### Resolving native UI Issues
-
-If you identified a native UI problem, there are usually two scenarios:
-
-1. the UI you're trying to draw each frame involves too much work on the GPU, or
-2. You're constructing new UI during the animation/interaction (e.g. loading in new content during a scroll).
-
-##### Too much GPU work
-
-In the first scenario, you'll see a trace that has the UI thread and/or Render Thread looking like this:
-
-![Overloaded GPU](/react-native/docs/assets/SystraceBadUI.png)
-
-Notice the long amount of time spent in `DrawFrame` that crosses frame boundaries. This is time spent waiting for the GPU to drain its command buffer from the previous frame.
-
-To mitigate this, you should:
-
-- investigate using `renderToHardwareTextureAndroid` for complex, static content that is being animated/transformed (e.g. the `Navigator` slide/alpha animations)
-- make sure that you are **not** using `needsOffscreenAlphaCompositing`, which is disabled by default, as it greatly increases the per-frame load on the GPU in most cases.
-
-If these don't help and you want to dig deeper into what the GPU is actually doing, you can check out [Tracer for OpenGL ES](http://www.androiddocs.com/tools/help/gltracer.html).
-
-##### Creating new views on the UI thread
-
-In the second scenario, you'll see something more like this:
-
-![Creating Views](/react-native/docs/assets/SystraceBadCreateUI.png)
-
-Notice that first the JS thread thinks for a bit, then you see some work done on the native modules thread, followed by an expensive traversal on the UI thread.
-
-There isn't an easy way to mitigate this unless you're able to postpone creating new UI until after the interaction, or you are able to simplify the UI you're creating. The react native team is working on an infrastructure level solution for this that will allow new UI to be created and configured off the main thread, allowing the interaction to continue smoothly.
-
-## RAM bundles + inline requires
-
-If you have a large app you may want to consider the Random Access Modules (RAM) bundle format, and using inline requires. This is useful for apps that have a large number of screens which may not ever be opened during a typical usage of the app. Generally it is useful to apps that have large amounts of code that are not needed for a while after startup. For instance the app includes complicated profile screens or lesser used features, but most sessions only involve visiting the main screen of the app for updates. We can optimize the loading of the bundle by using the RAM format and requiring those features and screens inline (when they are actually used).
-
-### Loading JavaScript
-
-Before react-native can execute JS code, that code must be loaded into memory and parsed. With a standard bundle if you load a 50mb bundle, all 50mb must be loaded and parsed before any of it can be executed. The optimization behind RAM bundles is that you can load only the portion of the 50mb that you actually need at startup, and progressively load more of the bundle as those sections are needed.
-
-### Inline Requires
-
-Inline requires delay the requiring of a module or file until that file is actually needed. A basic example would look like this:
-
-#### VeryExpensive.js
-
-```
-import React, { Component } from 'react';
-import { Text } from 'react-native';
-// ... import some very expensive modules
-
-// You may want to log at the file level to verify when this is happening
-console.log('VeryExpensive component loaded');
-
-export default class VeryExpensive extends Component {
-  // lots and lots of code
-  render() {
-    return <Text>Very Expensive Component</Text>;
-  }
-}
-```
-
-#### Optimized.js
-
-```
-import React, { Component } from 'react';
-import { TouchableOpacity, View, Text } from 'react-native';
-
-let VeryExpensive = null;
-
-export default class Optimized extends Component {
-  state = { needsExpensive: false };
-
-  didPress = () => {
-    if (VeryExpensive == null) {
-      VeryExpensive = require('./VeryExpensive').default;
-    }
-
-    this.setState(() => ({
-      needsExpensive: true,
-    }));
-  };
-
-  render() {
-    return (
-      <View style={{ marginTop: 20 }}>
-        <TouchableOpacity onPress={this.didPress}>
-          <Text>Load</Text>
-        </TouchableOpacity>
-        {this.state.needsExpensive ? <VeryExpensive /> : null}
-      </View>
-    );
-  }
-}
-```
-
-Even without the RAM format, inline requires can lead to startup time improvements, because the code within VeryExpensive.js will only execute once it is required for the first time.
-
-### Enable the RAM format
-
-On iOS using the RAM format will create a single indexed file that react native will load one module at a time. On Android, by default it will create a set of files for each module. You can force Android to create a single file, like iOS, but using multiple files can be more performant and requires less memory.
-
-Enable the RAM format in Xcode by editing the build phase "Bundle React Native code and images". Before `../node_modules/react-native/scripts/react-native-xcode.sh` add `export BUNDLE_COMMAND="ram-bundle"`:
-
-```
-export BUNDLE_COMMAND="ram-bundle"
-export NODE_BINARY=node
-../node_modules/react-native/scripts/react-native-xcode.sh
-```
-
-On Android enable the RAM format by editing your `android/app/build.gradle` file. Before the line `apply from: "../../node_modules/react-native/react.gradle"` add or amend the `project.ext.react` block:
-
-```
-project.ext.react = [
-  bundleCommand: "ram-bundle",
-]
-```
-
-Use the following lines on Android if you want to use a single indexed file:
-
-```
-project.ext.react = [
-  bundleCommand: "ram-bundle",
-  extraPackagerArgs: ["--indexed-ram-bundle"]
-]
-```
-
-> **_Note_**: If you are using [Hermes JS Engine](https://github.com/facebook/hermes), you do not need RAM bundles. When loading the bytecode, `mmap` ensures that the entire file is not loaded.
-
-### Configure Preloading and Inline Requires
-
-Now that we have a RAM bundle, there is overhead for calling `require`. `require` now needs to send a message over the bridge when it encounters a module it has not loaded yet. This will impact startup the most, because that is where the largest number of require calls are likely to take place while the app loads the initial module. Luckily we can configure a portion of the modules to be preloaded. In order to do this, you will need to implement some form of inline require.
-
-### Investigating the Loaded Modules
-
-In your root file (index.(ios|android).js) you can add the following after the initial imports:
-
-```
-const modules = require.getModules();
-const moduleIds = Object.keys(modules);
-const loadedModuleNames = moduleIds
-  .filter(moduleId => modules[moduleId].isInitialized)
-  .map(moduleId => modules[moduleId].verboseName);
-const waitingModuleNames = moduleIds
-  .filter(moduleId => !modules[moduleId].isInitialized)
-  .map(moduleId => modules[moduleId].verboseName);
-
-// make sure that the modules you expect to be waiting are actually waiting
-console.log(
-  'loaded:',
-  loadedModuleNames.length,
-  'waiting:',
-  waitingModuleNames.length
-);
-
-// grab this text blob, and put it in a file named packager/modulePaths.js
-console.log(`module.exports = ${JSON.stringify(loadedModuleNames.sort())};`);
-```
-
-When you run your app, you can look in the console and see how many modules have been loaded, and how many are waiting. You may want to read the moduleNames and see if there are any surprises. Note that inline requires are invoked the first time the imports are referenced. You may need to investigate and refactor to ensure only the modules you want are loaded on startup. Note that you can change the Systrace object on require to help debug problematic requires.
-
-```
-require.Systrace.beginEvent = (message) => {
-  if(message.includes(problematicModule)) {
-    throw new Error();
-  }
-}
-```
-
-Every app is different, but it may make sense to only load the modules you need for the very first screen. When you are satisfied, put the output of the loadedModuleNames into a file named `packager/modulePaths.js`.
-
-### Updating the metro.config.js
-
-We now need to update `metro.config.js` in the root of the project to use our newly generated `modulePaths.js` file:
-
-```
-const modulePaths = require('./packager/modulePaths');
-const resolve = require('path').resolve;
-const fs = require('fs');
-
-// Update the following line if the root folder of your app is somewhere else.
-const ROOT_FOLDER = resolve(__dirname, '..');
-
-const config = {
-  transformer: {
-    getTransformOptions: () => {
-      const moduleMap = {};
-      modulePaths.forEach(path => {
-        if (fs.existsSync(path)) {
-          moduleMap[resolve(path)] = true;
-        }
-      });
-      return {
-        preloadedModules: moduleMap,
-        transform: { inlineRequires: { blacklist: moduleMap } },
-      };
-    },
-  },
-  projectRoot:ROOT_FOLDER,
-};
-
-module.exports = config;
-```
-
-The `preloadedModules` entry in the config indicates which modules should be marked as preloaded when building a RAM bundle. When the bundle is loaded, those modules are immediately loaded, before any requires have even executed. The blacklist entry indicates that those modules should not be required inline. Because they are preloaded, there is no performance benefit from using an inline require. In fact the javascript spends extra time resolving the inline require every time the imports are referenced.
-
-### Test and Measure Improvements
-
-You should now be ready to build your app using the RAM format and inline requires. Make sure you measure the before and after startup times.
diff --git a/website/versioned_docs/version-0.60/props.md b/website/versioned_docs/version-0.60/props.md
deleted file mode 100644
index 29ba4cdc89c..00000000000
--- a/website/versioned_docs/version-0.60/props.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: version-0.60-props
-title: Props
-original_id: props
----
-
-Most components can be customized when they are created, with different parameters. These creation parameters are called `props`, short for properties.
-
-For example, one basic React Native component is the `Image`. When you create an image, you can use a prop named `source` to control what image it shows.
-
-```SnackPlayer name=Props
-import React, { Component } from 'react';
-import { Image } from 'react-native';
-
-export default class Bananas extends Component {
-  render() {
-    let pic = {
-      uri: 'https://upload.wikimedia.org/wikipedia/commons/d/de/Bananavarieties.jpg'
-    };
-    return (
-      <Image source={pic} style={{width: 193, height: 110}}/>
-    );
-  }
-}
-```
-
-Notice the braces surrounding `{pic}` - these embed the variable `pic` into JSX. You can put any JavaScript expression inside braces in JSX.
-
-Your own components can also use `props`. This lets you make a single component that is used in many different places in your app, with slightly different properties in each place. Just refer to `this.props` in your `render` function. Here's an example:
-
-```SnackPlayer name=Props
-import React, { Component } from 'react';
-import { Text, View } from 'react-native';
-
-class Greeting extends Component {
-  render() {
-    return (
-      <View style={{alignItems: 'center'}}>
-        <Text>Hello {this.props.name}!</Text>
-      </View>
-    );
-  }
-}
-
-export default class LotsOfGreetings extends Component {
-  render() {
-    return (
-      <View style={{alignItems: 'center', top: 50}}>
-        <Greeting name='Rexxar' />
-        <Greeting name='Jaina' />
-        <Greeting name='Valeera' />
-      </View>
-    );
-  }
-}
-```
-
-Using `name` as a prop lets us customize the `Greeting` component, so we can reuse that component for each of our greetings. This example also uses the `Greeting` component in JSX, just like the built-in components. The power to do this is what makes React so cool - if you find yourself wishing that you had a different set of UI primitives to work with, you just invent new ones.
-
-The other new thing going on here is the [`View`](view.md) component. A [`View`](view.md) is useful as a container for other components, to help control style and layout.
-
-With `props` and the basic [`Text`](text.md), [`Image`](image.md), and [`View`](view.md) components, you can build a wide variety of static screens. To learn how to make your app change over time, you need to [learn about State](state.md).
diff --git a/website/versioned_docs/version-0.60/removing-default-permissions.md b/website/versioned_docs/version-0.60/removing-default-permissions.md
deleted file mode 100644
index c2c6074424a..00000000000
--- a/website/versioned_docs/version-0.60/removing-default-permissions.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-id: version-0.60-removing-default-permissions
-title: Removing Default Permissions
-original_id: removing-default-permissions
----
-
-By default, some permissions are added to your Android APK.
-
-The default permissions that get added are:
-
-- android.permission.INTERNET - Required for debug mode.
-- android.permission.SYSTEM_ALERT_WINDOW - Required for debug mode.
-- android.permission.READ_PHONE_STATE - Not required for debug or production.
-- android.permission.WRITE_EXTERNAL_STORAGE - Not required for debug or production.
-- android.permission.READ_EXTERNAL_STORAGE - Not required for debug or production.
-
-1. Let's start by removing `READ_PHONE_STATE`, `WRITE_EXTERNAL_STORAGE`, and `READ_EXTERNAL_STORAGE` from both production and debug APKs, as it is not required in either. These storage permissions are still not needed if `AsyncStorage` module is in use, so it is safe to remove from both production and debug.
-2. Open your `android/app/src/main/AndroidManifest.xml` file.
-3. Even though these three permissions are not listed in the manifest they get added in. We add the three permissions with `tools:node="remove"` attribute, to make sure it gets removed during build. Note that the package identifier will be different, for below it is "com.myapp" because the project was created with `react-native init myapp`.
-
-   ```diff
-   <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-       package="com.myappid"
-   +   xmlns:tools="http://schemas.android.com/tools"
-       >
-
-       <uses-permission android:name="android.permission.INTERNET" />
-       <uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW" />
-   +   <uses-permission tools:node="remove" android:name="android.permission.READ_PHONE_STATE" />
-   +   <uses-permission tools:node="remove" android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
-   +   <uses-permission tools:node="remove" android:name="android.permission.READ_EXTERNAL_STORAGE" />
-
-       <application
-         android:name=".MainApplication"
-         android:label="@string/app_name"
-         android:icon="@mipmap/ic_launcher"
-         android:allowBackup="false"
-         android:theme="@style/AppTheme">
-         <activity
-           android:name=".MainActivity"
-           android:label="@string/app_name"
-           android:configChanges="keyboard|keyboardHidden|orientation|screenSize"
-           android:windowSoftInputMode="adjustResize">
-           <intent-filter>
-               <action android:name="android.intent.action.MAIN" />
-               <category android:name="android.intent.category.LAUNCHER" />
-           </intent-filter>
-         </activity>
-         <activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
-       </application>
-
-   </manifest>
-   ```
-
-That's it. We did not remove the `INTERNET` permission as pretty much all apps use it. Now whenever you create a production APK, these 3 permissions will be removed. When you create a debug APK (`react-native run-android`) it will install the APK with these permissions added.
diff --git a/website/versioned_docs/version-0.60/running-on-simulator-ios.md b/website/versioned_docs/version-0.60/running-on-simulator-ios.md
deleted file mode 100644
index 2de6d9abf93..00000000000
--- a/website/versioned_docs/version-0.60/running-on-simulator-ios.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-id: version-0.60-running-on-simulator-ios
-title: Running On Simulator
-original_id: running-on-simulator-ios
----
-
-## Starting the simulator
-
-Once you have your React Native project initialized, you can run `react-native run-ios` inside the newly created project directory. If everything is set up correctly, you should see your new app running in the iOS Simulator shortly.
-
-## Specifying a device
-
-You can specify the device the simulator should run with the `--simulator` flag, followed by the device name as a string. The default is `"iPhone X"`. If you wish to run your app on an iPhone 5s, just run `react-native run-ios --simulator="iPhone 5s"`.
-
-The device names correspond to the list of devices available in Xcode. You can check your available devices by running `xcrun simctl list devices` from the console.
diff --git a/website/versioned_docs/version-0.60/signed-apk-android.md b/website/versioned_docs/version-0.60/signed-apk-android.md
deleted file mode 100644
index a8266bd5a13..00000000000
--- a/website/versioned_docs/version-0.60/signed-apk-android.md
+++ /dev/null
@@ -1,145 +0,0 @@
----
-id: version-0.60-signed-apk-android
-title: Publishing to Google Play Store
-original_id: signed-apk-android
----
-
-Android requires that all apps be digitally signed with a certificate before they can be installed. In order to distribute your Android application via [Google Play store](https://play.google.com/store) it needs to be signed with a release key that then needs to be used for all future updates. Since 2017 it is possible for Google Play to manage signing releases automatically thanks to [App Signing by Google Play](https://developer.android.com/studio/publish/app-signing#app-signing-google-play) functionality. However, before your application binary is uploaded to Google Play it needs to be signed with an upload key. The [Signing Your Applications](https://developer.android.com/tools/publishing/app-signing.html) page on Android Developers documentation describes the topic in detail. This guide covers the process in brief, as well as lists the steps required to package the JavaScript bundle.
-
-### Generating an upload key
-
-You can generate a private signing key using `keytool`. On Windows `keytool` must be run from `C:\Program Files\Java\jdkx.x.x_x\bin`.
-
-    $ keytool -genkeypair -v -keystore my-upload-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000
-
-This command prompts you for passwords for the keystore and key and for the Distinguished Name fields for your key. It then generates the keystore as a file called `my-upload-key.keystore`.
-
-The keystore contains a single key, valid for 10000 days. The alias is a name that you will use later when signing your app, so remember to take note of the alias.
-
-On Mac, if you're not sure where your JDK bin folder is, then perform the following command to find it:
-
-    $ /usr/libexec/java_home
-
-It will output the directory of the JDK, which will look something like this:
-
-    /Library/Java/JavaVirtualMachines/jdkX.X.X_XXX.jdk/Contents/Home
-
-Navigate to that directory by using the command `$ cd /your/jdk/path` and use the keytool command with sudo permission as shown below.
-
-    $ sudo keytool -genkey -v -keystore my-upload-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000
-
-_Note: Remember to keep the keystore file private. In case you've lost upload key or it's been compromised you should [follow these instructions](https://support.google.com/googleplay/android-developer/answer/7384423#reset)._
-
-### Setting up Gradle variables
-
-1. Place the `my-upload-key.keystore` file under the `android/app` directory in your project folder.
-2. Edit the file `~/.gradle/gradle.properties` or `android/gradle.properties`, and add the following (replace `*****` with the correct keystore password, alias and key password),
-
-```
-MYAPP_UPLOAD_STORE_FILE=my-upload-key.keystore
-MYAPP_UPLOAD_KEY_ALIAS=my-key-alias
-MYAPP_UPLOAD_STORE_PASSWORD=*****
-MYAPP_UPLOAD_KEY_PASSWORD=*****
-```
-
-These are going to be global Gradle variables, which we can later use in our Gradle config to sign our app.
-
-_Note about security: If you are not keen on storing your passwords in plaintext, and you are running OSX, you can also [store your credentials in the Keychain Access app](https://pilloxa.gitlab.io/posts/safer-passwords-in-gradle/). Then you can skip the two last rows in `~/.gradle/gradle.properties`._
-
-### Adding signing config to your app's Gradle config
-
-The last configuration step that needs to be done is to setup release builds to be signed using upload key. Edit the file `android/app/build.gradle` in your project folder, and add the signing config,
-
-```gradle
-...
-android {
-    ...
-    defaultConfig { ... }
-    signingConfigs {
-        release {
-            if (project.hasProperty('MYAPP_UPLOAD_STORE_FILE')) {
-                storeFile file(MYAPP_UPLOAD_STORE_FILE)
-                storePassword MYAPP_UPLOAD_STORE_PASSWORD
-                keyAlias MYAPP_UPLOAD_KEY_ALIAS
-                keyPassword MYAPP_UPLOAD_KEY_PASSWORD
-            }
-        }
-    }
-    buildTypes {
-        release {
-            ...
-            signingConfig signingConfigs.release
-        }
-    }
-}
-...
-```
-
-### Generating the release APK
-
-Simply run the following in a terminal:
-
-```sh
-$ cd android
-$ ./gradlew bundleRelease
-```
-
-Gradle's `bundleRelease` will bundle all the JavaScript needed to run your app into the AAB ([Android App Bundle](https://developer.android.com/guide/app-bundle)). If you need to change the way the JavaScript bundle and/or drawable resources are bundled (e.g. if you changed the default file/folder names or the general structure of the project), have a look at `android/app/build.gradle` to see how you can update it to reflect these changes.
-
-> Note: Make sure gradle.properties does not include _org.gradle.configureondemand=true_ as that will make the release build skip bundling JS and assets into the app binary.
-
-The generated AAB can be found under `android/app/build/outputs/bundle/release/app.aab`, and is ready to be uploaded to Google Play.
-
-_Note: In order for Google Play to accept AAB format the App Signing by Google Play needs to be configured for your application on the Google Play Console. If you are updating an existing app that doesn't use App Signing by Google Play, please check our [migration section](#migrating-old-android-react-native-apps-to-use-app-signing-by-google-play) to learn how to perform that configuration change._
-
-### Testing the release build of your app
-
-Before uploading the release build to the Play Store, make sure you test it thoroughly. First uninstall any previous version of the app you already have installed. Install it on the device using:
-
-```sh
-$ react-native run-android --variant=release
-```
-
-Note that `--variant=release` is only available if you've set up signing as described above.
-
-You can kill any running packager instances, since all your framework and JavaScript code is bundled in the APK's assets.
-
-### Publishing to other stores
-
-By default, the generated APK has the native code for both x86 and ARMv7a CPU architectures. This makes it easier to share APKs that run on almost all Android devices. However, this has the downside that there will be some unused native code on any device, leading to unnecessarily bigger APKs.
-
-You can create an APK for each CPU by changing the following line in android/app/build.gradle:
-
-```diff
-- ndk {
--   abiFilters "armeabi-v7a", "x86"
-- }
-- def enableSeparateBuildPerCPUArchitecture = false
-+ def enableSeparateBuildPerCPUArchitecture = true
-```
-
-Upload both these files to markets which support device targeting, such as [Google Play](https://developer.android.com/google/play/publishing/multiple-apks.html) and [Amazon AppStore](https://developer.amazon.com/docs/app-submission/device-filtering-and-compatibility.html), and the users will automatically get the appropriate APK. If you want to upload to other markets, such as [APKFiles](https://www.apkfiles.com/), which do not support multiple APKs for a single app, change the following line as well to create the default universal APK with binaries for both CPUs.
-
-```diff
-- universalApk false  // If true, also generate a universal APK
-+ universalApk true  // If true, also generate a universal APK
-```
-
-### Enabling Proguard to reduce the size of the APK (optional)
-
-Proguard is a tool that can slightly reduce the size of the APK. It does this by stripping parts of the React Native Java bytecode (and its dependencies) that your app is not using.
-
-_**IMPORTANT**: Make sure to thoroughly test your app if you've enabled Proguard. Proguard often requires configuration specific to each native library you're using. See `app/proguard-rules.pro`._
-
-To enable Proguard, edit `android/app/build.gradle`:
-
-```gradle
-/**
- * Run Proguard to shrink the Java bytecode in release builds.
- */
-def enableProguardInReleaseBuilds = true
-```
-
-### Migrating old Android React Native apps to use App Signing by Google Play
-
-If you are migrating from previous version of React Native chances are your app does not use App Signing by Google Play feature. We recommend you enable that in order to take advantage from things like automatic app splitting. In order to migrate from the old way of signing you need to start by [generating new upload key](#generating-an-upload-key) and then replacing release signing config in `android/app/build.gradle` to use the upload key instead of the release one (see section about [adding signing config to gradle](#adding-signing-config-to-your-app-s-gradle-config)). Once that's done you should follow the [instructions from Google Play Help website](https://support.google.com/googleplay/android-developer/answer/7384423) in order to send your original release key to Google Play.
diff --git a/website/versioned_docs/version-0.60/state.md b/website/versioned_docs/version-0.60/state.md
deleted file mode 100644
index 55f7791064d..00000000000
--- a/website/versioned_docs/version-0.60/state.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-id: version-0.60-state
-title: State
-original_id: state
----
-
-There are two types of data that control a component: `props` and `state`. `props` are set by the parent and they are fixed throughout the lifetime of a component. For data that is going to change, we have to use `state`.
-
-In general, you should initialize `state` in the constructor, and then call `setState` when you want to change it.
-
-For example, let's say we want to make text that blinks all the time. The text itself gets set once when the blinking component gets created, so the text itself is a `prop`. The "whether the text is currently on or off" changes over time, so that should be kept in `state`.
-
-```SnackPlayer name=State
-import React, { Component } from 'react';
-import { Text, View } from 'react-native';
-
-class Blink extends Component {
-
-  componentDidMount(){
-    // Toggle the state every second
-    setInterval(() => (
-      this.setState(previousState => (
-        { isShowingText: !previousState.isShowingText }
-      ))
-    ), 1000);
-  }
-
-  //state object
-  state = { isShowingText: true };
-
-  render() {
-    if (!this.state.isShowingText) {
-      return null;
-    }
-
-    return (
-      <Text>{this.props.text}</Text>
-    );
-  }
-}
-
-export default class BlinkApp extends Component {
-  render() {
-    return (
-      <View>
-        <Blink text='I love to blink' />
-        <Blink text='Yes blinking is so great' />
-        <Blink text='Why did they ever take this out of HTML' />
-        <Blink text='Look at me look at me look at me' />
-      </View>
-    );
-  }
-}
-```
-
-In a real application, you probably won't be setting state with a timer. You might set state when you have new data from the server, or from user input. You can also use a state container like [Redux](https://redux.js.org/) or [Mobx](https://mobx.js.org/) to control your data flow. In that case you would use Redux or Mobx to modify your state rather than calling `setState` directly.
-
-When setState is called, BlinkApp will re-render its Component. By calling setState within the Timer, the component will re-render every time the Timer ticks.
-
-State works the same way as it does in React, so for more details on handling state, you can look at the [React.Component API](https://reactjs.org/docs/react-component.html#setstate). At this point, you might be annoyed that most of our examples so far use boring default black text. To make things more beautiful, you will have to [learn about Style](style.md).
diff --git a/website/versioned_docs/version-0.60/style.md b/website/versioned_docs/version-0.60/style.md
deleted file mode 100644
index 845bb61f626..00000000000
--- a/website/versioned_docs/version-0.60/style.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-id: version-0.60-style
-title: Style
-original_id: style
----
-
-With React Native, you don't use a special language or syntax for defining styles. You just style your application using JavaScript. All of the core components accept a prop named `style`. The style names and [values](colors.md) usually match how CSS works on the web, except names are written using camel casing, e.g. `backgroundColor` rather than `background-color`.
-
-The `style` prop can be a plain old JavaScript object. That's the simplest and what we usually use for example code. You can also pass an array of styles - the last style in the array has precedence, so you can use this to inherit styles.
-
-As a component grows in complexity, it is often cleaner to use `StyleSheet.create` to define several styles in one place. Here's an example:
-
-```SnackPlayer name=Style
-import React, { Component } from 'react';
-import { StyleSheet, Text, View } from 'react-native';
-
-const styles = StyleSheet.create({
-  bigBlue: {
-    color: 'blue',
-    fontWeight: 'bold',
-    fontSize: 30,
-  },
-  red: {
-    color: 'red',
-  },
-});
-
-export default class LotsOfStyles extends Component {
-  render() {
-    return (
-      <View>
-        <Text style={styles.red}>just red</Text>
-        <Text style={styles.bigBlue}>just bigBlue</Text>
-        <Text style={[styles.bigBlue, styles.red]}>bigBlue, then red</Text>
-        <Text style={[styles.red, styles.bigBlue]}>red, then bigBlue</Text>
-      </View>
-    );
-  }
-}
-```
-
-One common pattern is to make your component accept a `style` prop which in turn is used to style subcomponents. You can use this to make styles "cascade" the way they do in CSS.
-
-There are a lot more ways to customize text style. Check out the [Text component reference](text.md) for a complete list.
-
-Now you can make your text beautiful. The next step in becoming a style master is to [learn how to control component size](height-and-width.md).
diff --git a/website/versioned_docs/version-0.60/timers.md b/website/versioned_docs/version-0.60/timers.md
deleted file mode 100644
index 8759429fc1b..00000000000
--- a/website/versioned_docs/version-0.60/timers.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-id: version-0.60-timers
-title: Timers
-original_id: timers
----
-
-Timers are an important part of an application and React Native implements the [browser timers](https://developer.mozilla.org/en-US/Add-ons/Code_snippets/Timers).
-
-## Timers
-
-- setTimeout, clearTimeout
-- setInterval, clearInterval
-- setImmediate, clearImmediate
-- requestAnimationFrame, cancelAnimationFrame
-
-`requestAnimationFrame(fn)` is not the same as `setTimeout(fn, 0)` - the former will fire after all the frame has flushed, whereas the latter will fire as quickly as possible (over 1000x per second on a iPhone 5S).
-
-`setImmediate` is executed at the end of the current JavaScript execution block, right before sending the batched response back to native. Note that if you call `setImmediate` within a `setImmediate` callback, it will be executed right away, it won't yield back to native in between.
-
-The `Promise` implementation uses `setImmediate` as its asynchronicity primitive.
-
-## InteractionManager
-
-One reason why well-built native apps feel so smooth is by avoiding expensive operations during interactions and animations. In React Native, we currently have a limitation that there is only a single JS execution thread, but you can use `InteractionManager` to make sure long-running work is scheduled to start after any interactions/animations have completed.
-
-Applications can schedule tasks to run after interactions with the following:
-
-```jsx
-InteractionManager.runAfterInteractions(() => {
-  // ...long-running synchronous task...
-});
-```
-
-Compare this to other scheduling alternatives:
-
-- requestAnimationFrame(): for code that animates a view over time.
-- setImmediate/setTimeout/setInterval(): run code later, note this may delay animations.
-- runAfterInteractions(): run code later, without delaying active animations.
-
-The touch handling system considers one or more active touches to be an 'interaction' and will delay `runAfterInteractions()` callbacks until all touches have ended or been cancelled.
-
-InteractionManager also allows applications to register animations by creating an interaction 'handle' on animation start, and clearing it upon completion:
-
-```jsx
-var handle = InteractionManager.createInteractionHandle();
-// run animation... (`runAfterInteractions` tasks are queued)
-// later, on animation completion:
-InteractionManager.clearInteractionHandle(handle);
-// queued tasks run if all handles were cleared
-```
diff --git a/website/versioned_docs/version-0.60/troubleshooting.md b/website/versioned_docs/version-0.60/troubleshooting.md
deleted file mode 100644
index 52ecf3974ba..00000000000
--- a/website/versioned_docs/version-0.60/troubleshooting.md
+++ /dev/null
@@ -1,111 +0,0 @@
----
-id: version-0.60-troubleshooting
-title: Troubleshooting
-original_id: troubleshooting
----
-
-These are some common issues you may run into while setting up React Native. If you encounter something that is not listed here, try [searching for the issue in GitHub](https://github.com/facebook/react-native/issues/).
-
-### Port already in use
-
-The React Native packager runs on port 8081. If another process is already using that port, you can either terminate that process, or change the port that the packager uses.
-
-#### Terminating a process on port 8081
-
-Run the following command to find the id for the process that is listening on port 8081:
-
-```
-$ sudo lsof -i :8081
-```
-
-Then run the following to terminate the process:
-
-```
-$ kill -9 <PID>
-```
-
-On Windows you can find the process using port 8081 using [Resource Monitor](https://stackoverflow.com/questions/48198/how-can-you-find-out-which-process-is-listening-on-a-port-on-windows) and stop it using Task Manager.
-
-#### Using a port other than 8081
-
-You can configure the packager to use a port other than 8081 by using the `port` parameter:
-
-```
-$ react-native start --port=8088
-```
-
-You will also need to update your applications to load the JavaScript bundle from the new port. If running on device from Xcode, you can do this by updating occurrences of `8081` to your chosen port in the `node_modules/react-native/React/React.xcodeproj/project.pbxproj` file.
-
-### NPM locking error
-
-If you encounter an error such as `npm WARN locking Error: EACCES` while using the React Native CLI, try running the following:
-
-```
-sudo chown -R $USER ~/.npm
-sudo chown -R $USER /usr/local/lib/node_modules
-```
-
-### Missing libraries for React
-
-If you added React Native manually to your project, make sure you have included all the relevant dependencies that you are using, like `RCTText.xcodeproj`, `RCTImage.xcodeproj`. Next, the binaries built by these dependencies have to be linked to your app binary. Use the `Linked Frameworks and Binaries` section in the Xcode project settings. More detailed steps are here: [Linking Libraries](linking-libraries-ios.md#content).
-
-If you are using CocoaPods, verify that you have added React along with the subspecs to the `Podfile`. For example, if you were using the `<Text />`, `<Image />` and `fetch()` APIs, you would need to add these in your `Podfile`:
-
-```
-pod 'React', :path => '../node_modules/react-native', :subspecs => [
-  'RCTText',
-  'RCTImage',
-  'RCTNetwork',
-  'RCTWebSocket',
-]
-```
-
-Next, make sure you have run `pod install` and that a `Pods/` directory has been created in your project with React installed. CocoaPods will instruct you to use the generated `.xcworkspace` file henceforth to be able to use these installed dependencies.
-
-#### React Native does not compile when being used as a CocoaPod
-
-There is a CocoaPods plugin called [cocoapods-fix-react-native](https://github.com/orta/cocoapods-fix-react-native) which handles any potential post-fixing of the source code due to differences when using a dependency manager.
-
-#### Argument list too long: recursive header expansion failed
-
-In the project's build settings, `User Search Header Paths` and `Header Search Paths` are two configs that specify where Xcode should look for `#import` header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.
-
-To revert the `User Search Header Paths` and `Header Search Paths` build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.
-
-### No transports available
-
-React Native implements a polyfill for WebSockets. These [polyfills](https://github.com/facebook/react-native/blob/master/Libraries/Core/InitializeCore.js) are initialized as part of the react-native module that you include in your application through `import React from 'react'`. If you load another module that requires WebSockets, such as [Firebase](https://github.com/facebook/react-native/issues/3645), be sure to load/require it after react-native:
-
-```
-import React from 'react';
-import Firebase from 'firebase';
-```
-
-## Shell Command Unresponsive Exception
-
-If you encounter a ShellCommandUnresponsiveException exception such as:
-
-```
-Execution failed for task ':app:installDebug'.
-  com.android.builder.testing.api.DeviceException: com.android.ddmlib.ShellCommandUnresponsiveException
-```
-
-Try [downgrading your Gradle version to 1.2.3](https://github.com/facebook/react-native/issues/2720) in `android/build.gradle`.
-
-## react-native init hangs
-
-If you run into issues where running `react-native init` hangs in your system, try running it again in verbose mode and referring to [#2797](https://github.com/facebook/react-native/issues/2797) for common causes:
-
-```
-react-native init --verbose
-```
-
-## Unable to start react-native package manager (on Linux)
-
-### Case 1: Error "code":"ENOSPC","errno":"ENOSPC"
-
-Issue caused by the number of directories [inotify](https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers) (used by watchman on Linux) can monitor. To solve it, just run this command in your terminal window
-
-```
-echo fs.inotify.max_user_watches=582222 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
-```
diff --git a/website/versioned_docs/version-0.60/tutorial.md b/website/versioned_docs/version-0.60/tutorial.md
deleted file mode 100644
index 1bcd95c784c..00000000000
--- a/website/versioned_docs/version-0.60/tutorial.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-id: version-0.60-tutorial
-title: Learn the Basics
-original_id: tutorial
----
-
-React Native is like React, but it uses native components instead of web components as building blocks. So to understand the basic structure of a React Native app, you need to understand some of the basic React concepts, like JSX, components, `state`, and `props`. If you already know React, you still need to learn some React-Native-specific stuff, like the native components. This tutorial is aimed at all audiences, whether you have React experience or not.
-
-Let's do this thing.
-
-## Hello World
-
-In accordance with the ancient traditions of our people, we must first build an app that does nothing except say "Hello, world!". Here it is:
-
-```SnackPlayer name=Hello%20World
-import React, { Component } from 'react';
-import { Text, View } from 'react-native';
-
-export default class HelloWorldApp extends Component {
-  render() {
-    return (
-      <View style={{ flex: 1, justifyContent: "center", alignItems: "center" }}>
-        <Text>Hello, world!</Text>
-      </View>
-    );
-  }
-}
-```
-
-If you are feeling curious, you can play around with sample code directly in the web simulators. You can also paste it into your `App.js` file to create a real app on your local machine.
-
-## What's going on here?
-
-Some of the things in here might not look like JavaScript to you. Don't panic. _This is the future_.
-
-First of all, ES2015 (also known as ES6) is a set of improvements to JavaScript that is now part of the official standard, but not yet supported by all browsers, so often it isn't used yet in web development. React Native ships with ES2015 support, so you can use this stuff without worrying about compatibility. `import`, `from`, `class`, and `extends` in the example above are all ES2015 features. If you aren't familiar with ES2015, you can probably pick it up just by reading through sample code like this tutorial has. If you want, [this page](https://babeljs.io/learn-es2015/) has a good overview of ES2015 features.
-
-The other unusual thing in this code example is `<View><Text>Hello world!</Text></View>`. This is JSX - a syntax for embedding XML within JavaScript. Many frameworks use a special templating language which lets you embed code inside markup language. In React, this is reversed. JSX lets you write your markup language inside code. It looks like HTML on the web, except instead of web things like `<div>` or `<span>`, you use React components. In this case, `<Text>` is a built-in component that just displays some text and `View` is like the `<div>` or `<span>`.
-
-## Components
-
-So this code is defining `HelloWorldApp`, a new `Component`. When you're building a React Native app, you'll be making new components a lot. Anything you see on the screen is some sort of component. A component can be pretty simple - the only thing that's required is a `render` function which returns some JSX to render.
-
-## This app doesn't do very much
-
-Good point. To make components do more interesting things, you need to [learn about Props](props.md).
diff --git a/website/versioned_docs/version-0.60/upgrading.md b/website/versioned_docs/version-0.60/upgrading.md
deleted file mode 100644
index 2078642f64e..00000000000
--- a/website/versioned_docs/version-0.60/upgrading.md
+++ /dev/null
@@ -1,124 +0,0 @@
----
-id: version-0.60-upgrading
-title: Upgrading to new React Native versions
-original_id: upgrading
----
-
-Upgrading to new versions of React Native will give you access to more APIs, views, developer tools and other goodies. Upgrading requires a small amount of effort, but we try to make it easy for you.
-
-## Expo projects
-
-Upgrading your Expo project to a new version of React Native requires updating the `react-native`, `react`, and `expo` package versions in your `package.json` file. Please refer to [this list](https://docs.expo.io/versions/latest/sdk/#sdk-version) to find out what versions are supported. You will also need to set the correct `sdkVersion` in your `app.json` file.
-
-See the [Upgrading Expo SDK Walkthrough](https://docs.expo.io/versions/latest/workflow/upgrading-expo-sdk-walkthrough) for up-to-date information about upgrading your project.
-
-## React Native projects
-
-Because typical React Native projects are essentially made up of an Android project, an iOS project, and a JavaScript project, upgrading can be rather tricky. There's currently two ways for upgrading your React Native project: by using [React Native CLI](https://github.com/react-native-community/cli) or manually with [Upgrade Helper](https://github.com/react-native-community/upgrade-helper).
-
-### React Native CLI
-
-The [React Native CLI](https://github.com/react-native-community/cli) comes with `upgrade` command that provides a one-step operation to upgrade the source files with a minimum of conflicts, it internally uses [rn-diff-purge](https://github.com/react-native-community/rn-diff-purge) project to find out which files need to be created, removed or modified.
-
-#### 1. Run the `upgrade` command
-
-> The `upgrade` command works on top of Git by using `git apply` with 3-way merge, therefore it's required to use Git in order for this to work, if you don't use Git but still want to use this solution then you can check out how to do it in the [Troubleshooting](#i-want-to-upgrade-with-react-native-cli-but-i-don-t-use-git) section.
-
-Run the following command to start the process of upgrading to the latest version:
-
-```sh
-react-native upgrade
-```
-
-You may specify a React Native version by passing an argument, e.g. to upgrade to `0.61.0-rc.0` run:
-
-```sh
-react-native upgrade 0.61.0-rc.0
-```
-
-The project is upgraded using `git apply` with 3-way merge, it may happen that you'll need to resolve a few conflicts after it's finished.
-
-#### 2. Resolve the conflicts
-
-Conflicted files include delimiters which make very clear where the changes come from. For example:
-
-```
-13B07F951A680F5B00A75B9A /* Release */ = {
-  isa = XCBuildConfiguration;
-  buildSettings = {
-    ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
-<<<<<<< ours
-    CODE_SIGN_IDENTITY = "iPhone Developer";
-    FRAMEWORK_SEARCH_PATHS = (
-      "$(inherited)",
-      "$(PROJECT_DIR)/HockeySDK.embeddedframework",
-      "$(PROJECT_DIR)/HockeySDK-iOS/HockeySDK.embeddedframework",
-    );
-=======
-    CURRENT_PROJECT_VERSION = 1;
->>>>>>> theirs
-    HEADER_SEARCH_PATHS = (
-      "$(inherited)",
-      /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include,
-      "$(SRCROOT)/../node_modules/react-native/React/**",
-      "$(SRCROOT)/../node_modules/react-native-code-push/ios/CodePush/**",
-    );
-```
-
-You can think of "ours" as "your team" and "theirs" as "the React Native development team".
-
-### Upgrade Helper
-
-The [Upgrade Helper](https://react-native-community.github.io/upgrade-helper/) is a web tool to help you out when upgrading your apps by providing the full set of changes happening between any two versions. It also shows comments on specific files to help understanding why that change is needed.
-
-#### 1. Select the versions
-
-You first need to select from and to which version you wish to upgrade, by default the latest major versions are selected. After selecting you can click the button "Show me how to upgrade".
-
-💡 Major updates will show an "useful content" section on the top with links to help you out when upgrading.
-
-#### 2. Upgrade dependencies
-
-The first file that is shown is the `package.json`, it's good to update the dependencies that are showing in there. For example, if `react-native` and `react` appears as changes then you can install it in your project by running `yarn add`:
-
-```sh
-# {{VERSION}} and {{REACT_VERSION}} are the release versions showing in the diff
-yarn add react-native@{{VERSION}}
-yarn add react@{{REACT_VERSION}}
-```
-
-#### 3. Upgrade your project files
-
-The new release may contain updates to other files that are generated when you run `react-native init`, those files are listed after the `package.json` in the Upgrade Helper page. If there aren't other changes then you can just rebuild the project and continue developing.
-
-In case there are changes then you can either update them manually by copying and pasting from the changes in the page or you can do it with the React Native CLI upgrade command by running:
-
-```sh
-react-native upgrade
-```
-
-This will check your files against the latest template and perform the following:
-
-- If there is a new file in the template, it is simply created.
-- If a file in the template is identical to your file, it is skipped.
-- If a file is different in your project than the template, you will be prompted; you have options to keep your file or overwrite it with the template version.
-
-> Some upgrades won't be done automatically with the React Native CLI and require manual work, e.g. `0.28` to `0.29`, or `0.56` to `0.57`. Make sure to check the [release notes](https://github.com/facebook/react-native/releases) when upgrading so that you can identify any manual changes your particular project may require.
-
-### Troubleshooting
-
-#### I want to upgrade with React Native CLI but I don't use Git
-
-While your project does not have to be handled by the Git versioning system -- you can use Mercurial, SVN, or nothing -- you will still need to [install Git](https://git-scm.com/downloads) on your system in order to use `react-native upgrade`. Git will also need to be available in the `PATH`. If your project doesn't use Git, initialize it and commit:
-
-```sh
-git init # Initialize a Git repository
-git add . # Stage all the current files
-git commit -m "Upgrade react-native" # Save the current files in a commit
-```
-
-After you finish upgrading you may remove the `.git` directory.
-
-#### I have done all the changes but my app is still using an old version
-
-These sort of errors are usually related to caching, it's recommended to install [react-native-clean-project](https://github.com/pmadruga/react-native-clean-project) to clear all your project's cache and then you can run it again.
diff --git a/website/versioned_docs/version-0.60/using-a-scrollview.md b/website/versioned_docs/version-0.60/using-a-scrollview.md
deleted file mode 100644
index 74fcec9cbe1..00000000000
--- a/website/versioned_docs/version-0.60/using-a-scrollview.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-id: version-0.60-using-a-scrollview
-title: Using a ScrollView
-original_id: using-a-scrollview
----
-
-The [ScrollView](scrollview.md) is a generic scrolling container that can host multiple components and views. The scrollable items need not be homogeneous, and you can scroll both vertically and horizontally (by setting the `horizontal` property).
-
-This example creates a vertical `ScrollView` with both images and text mixed together.
-
-```SnackPlayer name=Using%20ScrollView
-import React, { Component } from 'react';
-import { ScrollView, Image, Text } from 'react-native';
-
-export default class IScrolledDownAndWhatHappenedNextShockedMe extends Component {
-  render() {
-      return (
-        <ScrollView>
-          <Text style={{fontSize:96}}>Scroll me plz</Text>
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Text style={{fontSize:96}}>If you like</Text>
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Text style={{fontSize:96}}>Scrolling down</Text>
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Text style={{fontSize:96}}>What's the best</Text>
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Text style={{fontSize:96}}>Framework around?</Text>
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Image source={{uri: "https://facebook.github.io/react-native/img/tiny_logo.png", width: 64, height: 64}} />
-          <Text style={{fontSize:80}}>React Native</Text>
-        </ScrollView>
-    );
-  }
-}
-```
-
-ScrollViews can be configured to allow paging through views using swiping gestures by using the `pagingEnabled` props. Swiping horizontally between views can also be implemented on Android using the [ViewPager](https://github.com/react-native-community/react-native-viewpager) component.
-
-On iOS a ScrollView with a single item can be used to allow the user to zoom content. Set up the `maximumZoomScale` and `minimumZoomScale` props and your user will be able to use pinch and expand gestures to zoom in and out.
-
-The ScrollView works best to present a small amount of things of a limited size. All the elements and views of a `ScrollView` are rendered, even if they are not currently shown on the screen. If you have a long list of more items than can fit on the screen, you should use a `FlatList` instead. So let's [learn about list views](using-a-listview.md) next.

From 6a3c4f2b8bd1816304b974a77d2e6ef09e0f2d53 Mon Sep 17 00:00:00 2001
From: Nicolas Charpentier <nicolas.charpentier079@gmail.com>
Date: Fri, 13 Sep 2019 13:53:23 -0400
Subject: [PATCH 06/26] Update dependencies (#1226)

* Update dependencies

* Fix CSS selector as .container has been removed
---
 website/core/RemarkablePlugins.js |    3 +-
 website/package.json              |    6 +-
 website/static/css/toc.css        |    2 +-
 website/yarn.lock                 | 1386 ++++++++++++++++++++---------
 4 files changed, 971 insertions(+), 426 deletions(-)

diff --git a/website/core/RemarkablePlugins.js b/website/core/RemarkablePlugins.js
index 7fd68a19290..9e9f36031be 100644
--- a/website/core/RemarkablePlugins.js
+++ b/website/core/RemarkablePlugins.js
@@ -1,7 +1,8 @@
 'use strict';
 
 const hljs = require('highlight.js');
-const escapeHtml = require('remarkable').utils.escapeHtml;
+const {utils} = require('remarkable');
+const {escapeHtml} = utils;
 
 // Remove leading "SnackPlayer", "ReactNativeWebPlayer"
 function cleanParams(params) {
diff --git a/website/package.json b/website/package.json
index 7d31728d19d..0176093bda5 100644
--- a/website/package.json
+++ b/website/package.json
@@ -36,9 +36,9 @@
     }
   },
   "dependencies": {
-    "docusaurus": "1.11.1",
-    "highlight.js": "^9.12.0",
-    "remarkable": "^1.7.1"
+    "docusaurus": "1.12.0",
+    "highlight.js": "^9.15.10",
+    "remarkable": "^2.0.0"
   },
   "devDependencies": {
     "front-matter": "^2.3.0",
diff --git a/website/static/css/toc.css b/website/static/css/toc.css
index 26667d8f5e0..755f9c492af 100644
--- a/website/static/css/toc.css
+++ b/website/static/css/toc.css
@@ -35,7 +35,7 @@
   }
 }
 
-.container.docsNavContainer {
+.docsNavContainer {
   overflow: visible;
   flex: 0 0 280px;
   margin-right: 0;
diff --git a/website/yarn.lock b/website/yarn.lock
index 38a55c8743c..c4d9572a729 100644
--- a/website/yarn.lock
+++ b/website/yarn.lock
@@ -2,6 +2,13 @@
 # yarn lockfile v1
 
 
+"@babel/code-frame@7.5.5", "@babel/code-frame@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.5.5.tgz#bc0782f6d69f7b7d49531219699b988f669a8f9d"
+  integrity sha512-27d4lZoomVyo51VegxI20xZPuSHusqbQag/ztrBC7wegWoQ1nLREPVSKSW8byhTlzTKyNE4ifaTA6lCp7JjpFw==
+  dependencies:
+    "@babel/highlight" "^7.0.0"
+
 "@babel/code-frame@^7.0.0":
   version "7.0.0"
   resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.0.0.tgz#06e2ab19bdb535385559aabb5ba59729482800f8"
@@ -9,22 +16,22 @@
   dependencies:
     "@babel/highlight" "^7.0.0"
 
-"@babel/core@^7.0.0":
-  version "7.4.5"
-  resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.4.5.tgz#081f97e8ffca65a9b4b0fdc7e274e703f000c06a"
-  integrity sha512-OvjIh6aqXtlsA8ujtGKfC7LYWksYSX8yQcM8Ay3LuvVeQ63lcOKgoZWVqcpFwkd29aYU9rVx7jxhfhiEDV9MZA==
+"@babel/core@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.5.5.tgz#17b2686ef0d6bc58f963dddd68ab669755582c30"
+  integrity sha512-i4qoSr2KTtce0DmkuuQBV4AuQgGPUcPXMr9L5MyYAtk06z068lQ10a4O009fe5OB/DfNV+h+qqT7ddNV8UnRjg==
   dependencies:
-    "@babel/code-frame" "^7.0.0"
-    "@babel/generator" "^7.4.4"
-    "@babel/helpers" "^7.4.4"
-    "@babel/parser" "^7.4.5"
+    "@babel/code-frame" "^7.5.5"
+    "@babel/generator" "^7.5.5"
+    "@babel/helpers" "^7.5.5"
+    "@babel/parser" "^7.5.5"
     "@babel/template" "^7.4.4"
-    "@babel/traverse" "^7.4.5"
-    "@babel/types" "^7.4.4"
+    "@babel/traverse" "^7.5.5"
+    "@babel/types" "^7.5.5"
     convert-source-map "^1.1.0"
     debug "^4.1.0"
     json5 "^2.1.0"
-    lodash "^4.17.11"
+    lodash "^4.17.13"
     resolve "^1.3.2"
     semver "^5.4.1"
     source-map "^0.5.0"
@@ -40,6 +47,17 @@
     source-map "^0.5.0"
     trim-right "^1.0.1"
 
+"@babel/generator@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/generator/-/generator-7.5.5.tgz#873a7f936a3c89491b43536d12245b626664e3cf"
+  integrity sha512-ETI/4vyTSxTzGnU2c49XHv2zhExkv9JHLTwDAFz85kmcwuShvYG2H08FwgIguQf4JC75CBnXAUM5PqeF4fj0nQ==
+  dependencies:
+    "@babel/types" "^7.5.5"
+    jsesc "^2.5.1"
+    lodash "^4.17.13"
+    source-map "^0.5.0"
+    trim-right "^1.0.1"
+
 "@babel/helper-annotate-as-pure@^7.0.0":
   version "7.0.0"
   resolved "https://registry.yarnpkg.com/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7.0.0.tgz#323d39dd0b50e10c7c06ca7d7638e6864d8c5c32"
@@ -72,26 +90,26 @@
     "@babel/traverse" "^7.4.4"
     "@babel/types" "^7.4.4"
 
-"@babel/helper-create-class-features-plugin@^7.4.4":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.4.4.tgz#fc3d690af6554cc9efc607364a82d48f58736dba"
-  integrity sha512-UbBHIa2qeAGgyiNR9RszVF7bUHEdgS4JAUNT8SiqrAN6YJVxlOxeLr5pBzb5kan302dejJ9nla4RyKcR1XT6XA==
+"@babel/helper-create-class-features-plugin@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.5.5.tgz#401f302c8ddbc0edd36f7c6b2887d8fa1122e5a4"
+  integrity sha512-ZsxkyYiRA7Bg+ZTRpPvB6AbOFKTFFK4LrvTet8lInm0V468MWCaSYJE+I7v2z2r8KNLtYiV+K5kTCnR7dvyZjg==
   dependencies:
     "@babel/helper-function-name" "^7.1.0"
-    "@babel/helper-member-expression-to-functions" "^7.0.0"
+    "@babel/helper-member-expression-to-functions" "^7.5.5"
     "@babel/helper-optimise-call-expression" "^7.0.0"
     "@babel/helper-plugin-utils" "^7.0.0"
-    "@babel/helper-replace-supers" "^7.4.4"
+    "@babel/helper-replace-supers" "^7.5.5"
     "@babel/helper-split-export-declaration" "^7.4.4"
 
-"@babel/helper-define-map@^7.4.4":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/helper-define-map/-/helper-define-map-7.4.4.tgz#6969d1f570b46bdc900d1eba8e5d59c48ba2c12a"
-  integrity sha512-IX3Ln8gLhZpSuqHJSnTNBWGDE9kdkTEWl21A/K7PQ00tseBwbqCHTvNLHSBd9M0R5rER4h5Rsvj9vw0R5SieBg==
+"@babel/helper-define-map@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/helper-define-map/-/helper-define-map-7.5.5.tgz#3dec32c2046f37e09b28c93eb0b103fd2a25d369"
+  integrity sha512-fTfxx7i0B5NJqvUOBBGREnrqbTxRh7zinBANpZXAVDlsZxYdclDp467G1sQ8VZYMnAURY3RpBUAgOYT9GfzHBg==
   dependencies:
     "@babel/helper-function-name" "^7.1.0"
-    "@babel/types" "^7.4.4"
-    lodash "^4.17.11"
+    "@babel/types" "^7.5.5"
+    lodash "^4.17.13"
 
 "@babel/helper-explode-assignable-expression@^7.1.0":
   version "7.1.0"
@@ -124,12 +142,12 @@
   dependencies:
     "@babel/types" "^7.4.4"
 
-"@babel/helper-member-expression-to-functions@^7.0.0":
-  version "7.0.0"
-  resolved "https://registry.yarnpkg.com/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.0.0.tgz#8cd14b0a0df7ff00f009e7d7a436945f47c7a16f"
-  integrity sha512-avo+lm/QmZlv27Zsi0xEor2fKcqWG56D5ae9dzklpIaY7cQMK5N8VSpaNVPPagiqmy7LrEjK1IWdGMOqPu5csg==
+"@babel/helper-member-expression-to-functions@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.5.5.tgz#1fb5b8ec4453a93c439ee9fe3aeea4a84b76b590"
+  integrity sha512-5qZ3D1uMclSNqYcXqiHoA0meVdv+xUEex9em2fqMnrk/scphGlGgg66zjMrPJESPwrFJ6sbfFQYUSa0Mz7FabA==
   dependencies:
-    "@babel/types" "^7.0.0"
+    "@babel/types" "^7.5.5"
 
 "@babel/helper-module-imports@^7.0.0":
   version "7.0.0"
@@ -180,15 +198,15 @@
     "@babel/traverse" "^7.1.0"
     "@babel/types" "^7.0.0"
 
-"@babel/helper-replace-supers@^7.1.0", "@babel/helper-replace-supers@^7.4.4":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/helper-replace-supers/-/helper-replace-supers-7.4.4.tgz#aee41783ebe4f2d3ab3ae775e1cc6f1a90cefa27"
-  integrity sha512-04xGEnd+s01nY1l15EuMS1rfKktNF+1CkKmHoErDppjAAZL+IUBZpzT748x262HF7fibaQPhbvWUl5HeSt1EXg==
+"@babel/helper-replace-supers@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/helper-replace-supers/-/helper-replace-supers-7.5.5.tgz#f84ce43df031222d2bad068d2626cb5799c34bc2"
+  integrity sha512-XvRFWrNnlsow2u7jXDuH4jDDctkxbS7gXssrP4q2nUD606ukXHRvydj346wmNg+zAgpFx4MWf4+usfC93bElJg==
   dependencies:
-    "@babel/helper-member-expression-to-functions" "^7.0.0"
+    "@babel/helper-member-expression-to-functions" "^7.5.5"
     "@babel/helper-optimise-call-expression" "^7.0.0"
-    "@babel/traverse" "^7.4.4"
-    "@babel/types" "^7.4.4"
+    "@babel/traverse" "^7.5.5"
+    "@babel/types" "^7.5.5"
 
 "@babel/helper-simple-access@^7.1.0":
   version "7.1.0"
@@ -215,14 +233,14 @@
     "@babel/traverse" "^7.1.0"
     "@babel/types" "^7.2.0"
 
-"@babel/helpers@^7.4.4":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/helpers/-/helpers-7.4.4.tgz#868b0ef59c1dd4e78744562d5ce1b59c89f2f2a5"
-  integrity sha512-igczbR/0SeuPR8RFfC7tGrbdTbFL3QTvH6D+Z6zNxnTe//GyqmtHmDkzrqDmyZ3eSwPqB/LhyKoU5DXsp+Vp2A==
+"@babel/helpers@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/helpers/-/helpers-7.5.5.tgz#63908d2a73942229d1e6685bc2a0e730dde3b75e"
+  integrity sha512-nRq2BUhxZFnfEn/ciJuhklHvFOqjJUD5wpx+1bxUF2axL9C+v4DE/dmp5sT2dKnpOs4orZWzpAZqlCy8QqE/7g==
   dependencies:
     "@babel/template" "^7.4.4"
-    "@babel/traverse" "^7.4.4"
-    "@babel/types" "^7.4.4"
+    "@babel/traverse" "^7.5.5"
+    "@babel/types" "^7.5.5"
 
 "@babel/highlight@^7.0.0":
   version "7.0.0"
@@ -238,6 +256,11 @@
   resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.4.5.tgz#04af8d5d5a2b044a2a1bffacc1e5e6673544e872"
   integrity sha512-9mUqkL1FF5T7f0WDFfAoDdiMVPWsdD1gZYzSnaXsxUCUqzuch/8of9G3VUSNiZmMBoRxT3neyVsqeiL/ZPcjew==
 
+"@babel/parser@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.5.5.tgz#02f077ac8817d3df4a832ef59de67565e71cca4b"
+  integrity sha512-E5BN68cqR7dhKan1SfqgPGhQ178bkVKpXTPEXnFJBrEt8/DKRZlybmy+IgYLTeN7tp1R5Ccmbm2rBk17sHYU3g==
+
 "@babel/plugin-proposal-async-generator-functions@^7.2.0":
   version "7.2.0"
   resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.2.0.tgz#b289b306669dce4ad20b0252889a15768c9d417e"
@@ -247,13 +270,21 @@
     "@babel/helper-remap-async-to-generator" "^7.1.0"
     "@babel/plugin-syntax-async-generators" "^7.2.0"
 
-"@babel/plugin-proposal-class-properties@^7.0.0":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-class-properties/-/plugin-proposal-class-properties-7.4.4.tgz#93a6486eed86d53452ab9bab35e368e9461198ce"
-  integrity sha512-WjKTI8g8d5w1Bc9zgwSz2nfrsNQsXcCf9J9cdCvrJV6RF56yztwm4TmJC0MgJ9tvwO9gUA/mcYe89bLdGfiXFg==
+"@babel/plugin-proposal-class-properties@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-class-properties/-/plugin-proposal-class-properties-7.5.5.tgz#a974cfae1e37c3110e71f3c6a2e48b8e71958cd4"
+  integrity sha512-AF79FsnWFxjlaosgdi421vmYG6/jg79bVD0dpD44QdgobzHKuLZ6S3vl8la9qIeSwGi8i1fS0O1mfuDAAdo1/A==
+  dependencies:
+    "@babel/helper-create-class-features-plugin" "^7.5.5"
+    "@babel/helper-plugin-utils" "^7.0.0"
+
+"@babel/plugin-proposal-dynamic-import@^7.5.0":
+  version "7.5.0"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-dynamic-import/-/plugin-proposal-dynamic-import-7.5.0.tgz#e532202db4838723691b10a67b8ce509e397c506"
+  integrity sha512-x/iMjggsKTFHYC6g11PL7Qy58IK8H5zqfm9e6hu4z1iH2IRyAp9u9dL80zA6R76yFovETFLKz2VJIC2iIPBuFw==
   dependencies:
-    "@babel/helper-create-class-features-plugin" "^7.4.4"
     "@babel/helper-plugin-utils" "^7.0.0"
+    "@babel/plugin-syntax-dynamic-import" "^7.2.0"
 
 "@babel/plugin-proposal-json-strings@^7.2.0":
   version "7.2.0"
@@ -263,10 +294,10 @@
     "@babel/helper-plugin-utils" "^7.0.0"
     "@babel/plugin-syntax-json-strings" "^7.2.0"
 
-"@babel/plugin-proposal-object-rest-spread@^7.0.0", "@babel/plugin-proposal-object-rest-spread@^7.4.4":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.4.4.tgz#1ef173fcf24b3e2df92a678f027673b55e7e3005"
-  integrity sha512-dMBG6cSPBbHeEBdFXeQ2QLc5gUpg4Vkaz8octD4aoW/ISO+jBOcsuxYL7bsb5WSu8RLP6boxrBIALEHgoHtO9g==
+"@babel/plugin-proposal-object-rest-spread@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.5.5.tgz#61939744f71ba76a3ae46b5eea18a54c16d22e58"
+  integrity sha512-F2DxJJSQ7f64FyTVl5cw/9MWn6naXGdk3Q3UhDbFEEHv+EilCPoeRD3Zh/Utx1CJz4uyKlQ4uH+bJPbEhMV7Zw==
   dependencies:
     "@babel/helper-plugin-utils" "^7.0.0"
     "@babel/plugin-syntax-object-rest-spread" "^7.2.0"
@@ -295,6 +326,13 @@
   dependencies:
     "@babel/helper-plugin-utils" "^7.0.0"
 
+"@babel/plugin-syntax-dynamic-import@^7.2.0":
+  version "7.2.0"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-dynamic-import/-/plugin-syntax-dynamic-import-7.2.0.tgz#69c159ffaf4998122161ad8ebc5e6d1f55df8612"
+  integrity sha512-mVxuJ0YroI/h/tbFTPGZR8cv6ai+STMKNBq0f8hFxsxWjl94qqhsb+wXbpNMDPU3cfR1TIsVFzU3nXyZMqyK4w==
+  dependencies:
+    "@babel/helper-plugin-utils" "^7.0.0"
+
 "@babel/plugin-syntax-json-strings@^7.2.0":
   version "7.2.0"
   resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-json-strings/-/plugin-syntax-json-strings-7.2.0.tgz#72bd13f6ffe1d25938129d2a186b11fd62951470"
@@ -330,10 +368,10 @@
   dependencies:
     "@babel/helper-plugin-utils" "^7.0.0"
 
-"@babel/plugin-transform-async-to-generator@^7.4.4":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.4.4.tgz#a3f1d01f2f21cadab20b33a82133116f14fb5894"
-  integrity sha512-YiqW2Li8TXmzgbXw+STsSqPBPFnGviiaSp6CYOq55X8GQ2SGVLrXB6pNid8HkqkZAzOH6knbai3snhP7v0fNwA==
+"@babel/plugin-transform-async-to-generator@^7.5.0":
+  version "7.5.0"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.5.0.tgz#89a3848a0166623b5bc481164b5936ab947e887e"
+  integrity sha512-mqvkzwIGkq0bEF1zLRRiTdjfomZJDV33AH3oQzHVGkI2VzEmXLpKKOBvEVaFZBJdN0XTyH38s9j/Kiqr68dggg==
   dependencies:
     "@babel/helper-module-imports" "^7.0.0"
     "@babel/helper-plugin-utils" "^7.0.0"
@@ -346,25 +384,25 @@
   dependencies:
     "@babel/helper-plugin-utils" "^7.0.0"
 
-"@babel/plugin-transform-block-scoping@^7.4.4":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.4.4.tgz#c13279fabf6b916661531841a23c4b7dae29646d"
-  integrity sha512-jkTUyWZcTrwxu5DD4rWz6rDB5Cjdmgz6z7M7RLXOJyCUkFBawssDGcGh8M/0FTSB87avyJI1HsTwUXp9nKA1PA==
+"@babel/plugin-transform-block-scoping@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.5.5.tgz#a35f395e5402822f10d2119f6f8e045e3639a2ce"
+  integrity sha512-82A3CLRRdYubkG85lKwhZB0WZoHxLGsJdux/cOVaJCJpvYFl1LVzAIFyRsa7CvXqW8rBM4Zf3Bfn8PHt5DP0Sg==
   dependencies:
     "@babel/helper-plugin-utils" "^7.0.0"
-    lodash "^4.17.11"
+    lodash "^4.17.13"
 
-"@babel/plugin-transform-classes@^7.4.4":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-classes/-/plugin-transform-classes-7.4.4.tgz#0ce4094cdafd709721076d3b9c38ad31ca715eb6"
-  integrity sha512-/e44eFLImEGIpL9qPxSRat13I5QNRgBLu2hOQJCF7VLy/otSM/sypV1+XaIw5+502RX/+6YaSAPmldk+nhHDPw==
+"@babel/plugin-transform-classes@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-classes/-/plugin-transform-classes-7.5.5.tgz#d094299d9bd680a14a2a0edae38305ad60fb4de9"
+  integrity sha512-U2htCNK/6e9K7jGyJ++1p5XRU+LJjrwtoiVn9SzRlDT2KubcZ11OOwy3s24TjHxPgxNwonCYP7U2K51uVYCMDg==
   dependencies:
     "@babel/helper-annotate-as-pure" "^7.0.0"
-    "@babel/helper-define-map" "^7.4.4"
+    "@babel/helper-define-map" "^7.5.5"
     "@babel/helper-function-name" "^7.1.0"
     "@babel/helper-optimise-call-expression" "^7.0.0"
     "@babel/helper-plugin-utils" "^7.0.0"
-    "@babel/helper-replace-supers" "^7.4.4"
+    "@babel/helper-replace-supers" "^7.5.5"
     "@babel/helper-split-export-declaration" "^7.4.4"
     globals "^11.1.0"
 
@@ -375,10 +413,10 @@
   dependencies:
     "@babel/helper-plugin-utils" "^7.0.0"
 
-"@babel/plugin-transform-destructuring@^7.4.4":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.4.4.tgz#9d964717829cc9e4b601fc82a26a71a4d8faf20f"
-  integrity sha512-/aOx+nW0w8eHiEHm+BTERB2oJn5D127iye/SUQl7NjHy0lf+j7h4MKMMSOwdazGq9OxgiNADncE+SRJkCxjZpQ==
+"@babel/plugin-transform-destructuring@^7.5.0":
+  version "7.5.0"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.5.0.tgz#f6c09fdfe3f94516ff074fe877db7bc9ef05855a"
+  integrity sha512-YbYgbd3TryYYLGyC7ZR+Tq8H/+bCmwoaxHfJHupom5ECstzbRLTch6gOQbhEY9Z4hiCNHEURgq06ykFv9JZ/QQ==
   dependencies:
     "@babel/helper-plugin-utils" "^7.0.0"
 
@@ -391,10 +429,10 @@
     "@babel/helper-regex" "^7.4.4"
     regexpu-core "^4.5.4"
 
-"@babel/plugin-transform-duplicate-keys@^7.2.0":
-  version "7.2.0"
-  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.2.0.tgz#d952c4930f312a4dbfff18f0b2914e60c35530b3"
-  integrity sha512-q+yuxW4DsTjNceUiTzK0L+AfQ0zD9rWaTLiUqHA8p0gxx7lu1EylenfzjeIWNkPy6e/0VG/Wjw9uf9LueQwLOw==
+"@babel/plugin-transform-duplicate-keys@^7.5.0":
+  version "7.5.0"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.5.0.tgz#c5dbf5106bf84cdf691222c0974c12b1df931853"
+  integrity sha512-igcziksHizyQPlX9gfSjHkE2wmoCH3evvD2qR5w29/Dk0SMKE/eOI7f1HhBdNhR/zxJDqrgpoDTq5YSLH/XMsQ==
   dependencies:
     "@babel/helper-plugin-utils" "^7.0.0"
 
@@ -435,30 +473,33 @@
   dependencies:
     "@babel/helper-plugin-utils" "^7.0.0"
 
-"@babel/plugin-transform-modules-amd@^7.2.0":
-  version "7.2.0"
-  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.2.0.tgz#82a9bce45b95441f617a24011dc89d12da7f4ee6"
-  integrity sha512-mK2A8ucqz1qhrdqjS9VMIDfIvvT2thrEsIQzbaTdc5QFzhDjQv2CkJJ5f6BXIkgbmaoax3zBr2RyvV/8zeoUZw==
+"@babel/plugin-transform-modules-amd@^7.5.0":
+  version "7.5.0"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.5.0.tgz#ef00435d46da0a5961aa728a1d2ecff063e4fb91"
+  integrity sha512-n20UsQMKnWrltocZZm24cRURxQnWIvsABPJlw/fvoy9c6AgHZzoelAIzajDHAQrDpuKFFPPcFGd7ChsYuIUMpg==
   dependencies:
     "@babel/helper-module-transforms" "^7.1.0"
     "@babel/helper-plugin-utils" "^7.0.0"
+    babel-plugin-dynamic-import-node "^2.3.0"
 
-"@babel/plugin-transform-modules-commonjs@^7.4.4":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.4.4.tgz#0bef4713d30f1d78c2e59b3d6db40e60192cac1e"
-  integrity sha512-4sfBOJt58sEo9a2BQXnZq+Q3ZTSAUXyK3E30o36BOGnJ+tvJ6YSxF0PG6kERvbeISgProodWuI9UVG3/FMY6iw==
+"@babel/plugin-transform-modules-commonjs@^7.5.0":
+  version "7.5.0"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.5.0.tgz#425127e6045231360858eeaa47a71d75eded7a74"
+  integrity sha512-xmHq0B+ytyrWJvQTc5OWAC4ii6Dhr0s22STOoydokG51JjWhyYo5mRPXoi+ZmtHQhZZwuXNN+GG5jy5UZZJxIQ==
   dependencies:
     "@babel/helper-module-transforms" "^7.4.4"
     "@babel/helper-plugin-utils" "^7.0.0"
     "@babel/helper-simple-access" "^7.1.0"
+    babel-plugin-dynamic-import-node "^2.3.0"
 
-"@babel/plugin-transform-modules-systemjs@^7.4.4":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.4.4.tgz#dc83c5665b07d6c2a7b224c00ac63659ea36a405"
-  integrity sha512-MSiModfILQc3/oqnG7NrP1jHaSPryO6tA2kOMmAQApz5dayPxWiHqmq4sWH2xF5LcQK56LlbKByCd8Aah/OIkQ==
+"@babel/plugin-transform-modules-systemjs@^7.5.0":
+  version "7.5.0"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.5.0.tgz#e75266a13ef94202db2a0620977756f51d52d249"
+  integrity sha512-Q2m56tyoQWmuNGxEtUyeEkm6qJYFqs4c+XyXH5RAuYxObRNz9Zgj/1g2GMnjYp2EUyEy7YTrxliGCXzecl/vJg==
   dependencies:
     "@babel/helper-hoist-variables" "^7.4.4"
     "@babel/helper-plugin-utils" "^7.0.0"
+    babel-plugin-dynamic-import-node "^2.3.0"
 
 "@babel/plugin-transform-modules-umd@^7.2.0":
   version "7.2.0"
@@ -482,13 +523,13 @@
   dependencies:
     "@babel/helper-plugin-utils" "^7.0.0"
 
-"@babel/plugin-transform-object-super@^7.2.0":
-  version "7.2.0"
-  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.2.0.tgz#b35d4c10f56bab5d650047dad0f1d8e8814b6598"
-  integrity sha512-VMyhPYZISFZAqAPVkiYb7dUe2AsVi2/wCT5+wZdsNO31FojQJa9ns40hzZ6U9f50Jlq4w6qwzdBB2uwqZ00ebg==
+"@babel/plugin-transform-object-super@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.5.5.tgz#c70021df834073c65eb613b8679cc4a381d1a9f9"
+  integrity sha512-un1zJQAhSosGFBduPgN/YFNvWVpRuHKU7IHBglLoLZsGmruJPOo6pbInneflUdmq7YvSVqhpPs5zdBvLnteltQ==
   dependencies:
     "@babel/helper-plugin-utils" "^7.0.0"
-    "@babel/helper-replace-supers" "^7.1.0"
+    "@babel/helper-replace-supers" "^7.5.5"
 
 "@babel/plugin-transform-parameters@^7.4.4":
   version "7.4.4"
@@ -598,7 +639,7 @@
     "@babel/helper-regex" "^7.4.4"
     regexpu-core "^4.5.4"
 
-"@babel/polyfill@^7.0.0":
+"@babel/polyfill@^7.4.4":
   version "7.4.4"
   resolved "https://registry.yarnpkg.com/@babel/polyfill/-/polyfill-7.4.4.tgz#78801cf3dbe657844eeabf31c1cae3828051e893"
   integrity sha512-WlthFLfhQQhh+A2Gn5NSFl0Huxz36x86Jn+E9OW7ibK8edKPq+KLy4apM1yDpQ8kJOVi1OVjpP4vSDLdrI04dg==
@@ -606,43 +647,45 @@
     core-js "^2.6.5"
     regenerator-runtime "^0.13.2"
 
-"@babel/preset-env@^7.0.0":
-  version "7.4.5"
-  resolved "https://registry.yarnpkg.com/@babel/preset-env/-/preset-env-7.4.5.tgz#2fad7f62983d5af563b5f3139242755884998a58"
-  integrity sha512-f2yNVXM+FsR5V8UwcFeIHzHWgnhXg3NpRmy0ADvALpnhB0SLbCvrCRr4BLOUYbQNLS+Z0Yer46x9dJXpXewI7w==
+"@babel/preset-env@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/preset-env/-/preset-env-7.5.5.tgz#bc470b53acaa48df4b8db24a570d6da1fef53c9a"
+  integrity sha512-GMZQka/+INwsMz1A5UEql8tG015h5j/qjptpKY2gJ7giy8ohzU710YciJB5rcKsWGWHiW3RUnHib0E5/m3Tp3A==
   dependencies:
     "@babel/helper-module-imports" "^7.0.0"
     "@babel/helper-plugin-utils" "^7.0.0"
     "@babel/plugin-proposal-async-generator-functions" "^7.2.0"
+    "@babel/plugin-proposal-dynamic-import" "^7.5.0"
     "@babel/plugin-proposal-json-strings" "^7.2.0"
-    "@babel/plugin-proposal-object-rest-spread" "^7.4.4"
+    "@babel/plugin-proposal-object-rest-spread" "^7.5.5"
     "@babel/plugin-proposal-optional-catch-binding" "^7.2.0"
     "@babel/plugin-proposal-unicode-property-regex" "^7.4.4"
     "@babel/plugin-syntax-async-generators" "^7.2.0"
+    "@babel/plugin-syntax-dynamic-import" "^7.2.0"
     "@babel/plugin-syntax-json-strings" "^7.2.0"
     "@babel/plugin-syntax-object-rest-spread" "^7.2.0"
     "@babel/plugin-syntax-optional-catch-binding" "^7.2.0"
     "@babel/plugin-transform-arrow-functions" "^7.2.0"
-    "@babel/plugin-transform-async-to-generator" "^7.4.4"
+    "@babel/plugin-transform-async-to-generator" "^7.5.0"
     "@babel/plugin-transform-block-scoped-functions" "^7.2.0"
-    "@babel/plugin-transform-block-scoping" "^7.4.4"
-    "@babel/plugin-transform-classes" "^7.4.4"
+    "@babel/plugin-transform-block-scoping" "^7.5.5"
+    "@babel/plugin-transform-classes" "^7.5.5"
     "@babel/plugin-transform-computed-properties" "^7.2.0"
-    "@babel/plugin-transform-destructuring" "^7.4.4"
+    "@babel/plugin-transform-destructuring" "^7.5.0"
     "@babel/plugin-transform-dotall-regex" "^7.4.4"
-    "@babel/plugin-transform-duplicate-keys" "^7.2.0"
+    "@babel/plugin-transform-duplicate-keys" "^7.5.0"
     "@babel/plugin-transform-exponentiation-operator" "^7.2.0"
     "@babel/plugin-transform-for-of" "^7.4.4"
     "@babel/plugin-transform-function-name" "^7.4.4"
     "@babel/plugin-transform-literals" "^7.2.0"
     "@babel/plugin-transform-member-expression-literals" "^7.2.0"
-    "@babel/plugin-transform-modules-amd" "^7.2.0"
-    "@babel/plugin-transform-modules-commonjs" "^7.4.4"
-    "@babel/plugin-transform-modules-systemjs" "^7.4.4"
+    "@babel/plugin-transform-modules-amd" "^7.5.0"
+    "@babel/plugin-transform-modules-commonjs" "^7.5.0"
+    "@babel/plugin-transform-modules-systemjs" "^7.5.0"
     "@babel/plugin-transform-modules-umd" "^7.2.0"
     "@babel/plugin-transform-named-capturing-groups-regex" "^7.4.5"
     "@babel/plugin-transform-new-target" "^7.4.4"
-    "@babel/plugin-transform-object-super" "^7.2.0"
+    "@babel/plugin-transform-object-super" "^7.5.5"
     "@babel/plugin-transform-parameters" "^7.4.4"
     "@babel/plugin-transform-property-literals" "^7.2.0"
     "@babel/plugin-transform-regenerator" "^7.4.5"
@@ -653,7 +696,7 @@
     "@babel/plugin-transform-template-literals" "^7.4.4"
     "@babel/plugin-transform-typeof-symbol" "^7.2.0"
     "@babel/plugin-transform-unicode-regex" "^7.4.4"
-    "@babel/types" "^7.4.4"
+    "@babel/types" "^7.5.5"
     browserslist "^4.6.0"
     core-js-compat "^3.1.1"
     invariant "^2.2.2"
@@ -671,14 +714,14 @@
     "@babel/plugin-transform-react-jsx-self" "^7.0.0"
     "@babel/plugin-transform-react-jsx-source" "^7.0.0"
 
-"@babel/register@^7.0.0":
-  version "7.4.4"
-  resolved "https://registry.yarnpkg.com/@babel/register/-/register-7.4.4.tgz#370a68ba36f08f015a8b35d4864176c6b65d7a23"
-  integrity sha512-sn51H88GRa00+ZoMqCVgOphmswG4b7mhf9VOB0LUBAieykq2GnRFerlN+JQkO/ntT7wz4jaHNSRPg9IdMPEUkA==
+"@babel/register@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/register/-/register-7.5.5.tgz#40fe0d474c8c8587b28d6ae18a03eddad3dac3c1"
+  integrity sha512-pdd5nNR+g2qDkXZlW1yRCWFlNrAn2PPdnZUB72zjX4l1Vv4fMRRLwyf+n/idFCLI1UgVGboUU8oVziwTBiyNKQ==
   dependencies:
     core-js "^3.0.0"
     find-cache-dir "^2.0.0"
-    lodash "^4.17.11"
+    lodash "^4.17.13"
     mkdirp "^0.5.1"
     pirates "^4.0.0"
     source-map-support "^0.5.9"
@@ -692,7 +735,7 @@
     "@babel/parser" "^7.4.4"
     "@babel/types" "^7.4.4"
 
-"@babel/traverse@^7.0.0", "@babel/traverse@^7.1.0", "@babel/traverse@^7.4.4", "@babel/traverse@^7.4.5":
+"@babel/traverse@^7.1.0", "@babel/traverse@^7.4.4":
   version "7.4.5"
   resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.4.5.tgz#4e92d1728fd2f1897dafdd321efbff92156c3216"
   integrity sha512-Vc+qjynwkjRmIFGxy0KYoPj4FdVDxLej89kMHFsWScq999uX+pwcX4v9mWRjW0KcAYTPAuVQl2LKP1wEVLsp+A==
@@ -707,7 +750,22 @@
     globals "^11.1.0"
     lodash "^4.17.11"
 
-"@babel/types@^7.0.0", "@babel/types@^7.1.2", "@babel/types@^7.2.0", "@babel/types@^7.3.0", "@babel/types@^7.4.4":
+"@babel/traverse@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.5.5.tgz#f664f8f368ed32988cd648da9f72d5ca70f165bb"
+  integrity sha512-MqB0782whsfffYfSjH4TM+LMjrJnhCNEDMDIjeTpl+ASaUvxcjoiVCo/sM1GhS1pHOXYfWVCYneLjMckuUxDaQ==
+  dependencies:
+    "@babel/code-frame" "^7.5.5"
+    "@babel/generator" "^7.5.5"
+    "@babel/helper-function-name" "^7.1.0"
+    "@babel/helper-split-export-declaration" "^7.4.4"
+    "@babel/parser" "^7.5.5"
+    "@babel/types" "^7.5.5"
+    debug "^4.1.0"
+    globals "^11.1.0"
+    lodash "^4.17.13"
+
+"@babel/types@^7.0.0", "@babel/types@^7.2.0", "@babel/types@^7.3.0", "@babel/types@^7.4.4":
   version "7.4.4"
   resolved "https://registry.yarnpkg.com/@babel/types/-/types-7.4.4.tgz#8db9e9a629bb7c29370009b4b779ed93fe57d5f0"
   integrity sha512-dOllgYdnEFOebhkKCjzSVFqw/PmmB8pH6RGOWkY4GsboQNd47b1fBThBSwlHAq9alF9vc1M3+6oqR47R50L0tQ==
@@ -716,6 +774,15 @@
     lodash "^4.17.11"
     to-fast-properties "^2.0.0"
 
+"@babel/types@^7.5.5":
+  version "7.5.5"
+  resolved "https://registry.yarnpkg.com/@babel/types/-/types-7.5.5.tgz#97b9f728e182785909aa4ab56264f090a028d18a"
+  integrity sha512-s63F9nJioLqOlW3UkyMd+BYhXt44YuaFm/VV0VwuteqjYwRrObkU7ra9pY4wAJR3oXi8hJrMcrcJdO/HH33vtw==
+  dependencies:
+    esutils "^2.0.2"
+    lodash "^4.17.13"
+    to-fast-properties "^2.0.0"
+
 "@mrmlnc/readdir-enhanced@^2.2.1":
   version "2.2.1"
   resolved "https://registry.yarnpkg.com/@mrmlnc/readdir-enhanced/-/readdir-enhanced-2.2.1.tgz#524af240d1a360527b730475ecfa1344aa540dde"
@@ -751,6 +818,11 @@
   resolved "https://registry.yarnpkg.com/@types/q/-/q-1.5.2.tgz#690a1475b84f2a884fd07cd797c00f5f31356ea8"
   integrity sha512-ce5d3q03Ex0sy4R14722Rmt6MT07Ua+k4FwDfdcToYJcMKNtRVQvJ6JCAPdAmAnbRb6CsX6aYb9m96NGod9uTw==
 
+abbrev@1:
+  version "1.1.1"
+  resolved "https://registry.yarnpkg.com/abbrev/-/abbrev-1.1.1.tgz#f8f2c887ad10bf67f634f005b6987fed3179aac8"
+  integrity sha512-nne9/IiQ/hzIhY6pdDnbBtz7DjPTKrY00P/zvPSm5pOFkl6xuGrGnXn/VtTNNfNtAfZ9/1RtehkszU9qcTii0Q==
+
 accepts@~1.3.7:
   version "1.3.7"
   resolved "https://registry.yarnpkg.com/accepts/-/accepts-1.3.7.tgz#531bc726517a3b2b41f850021c6cc15eaab507cd"
@@ -759,12 +831,7 @@ accepts@~1.3.7:
     mime-types "~2.1.24"
     negotiator "0.6.2"
 
-address@1.0.3:
-  version "1.0.3"
-  resolved "https://registry.yarnpkg.com/address/-/address-1.0.3.tgz#b5f50631f8d6cec8bd20c963963afb55e06cbce9"
-  integrity sha512-z55ocwKBRLryBs394Sm3ushTtBeg6VAeuku7utSoSnsJKvKcnXFIyC6vh27n3rXyxSgkJBBCAvyOn7gSUcTYjg==
-
-address@^1.0.1:
+address@1.1.0, address@^1.0.1:
   version "1.1.0"
   resolved "https://registry.yarnpkg.com/address/-/address-1.1.0.tgz#ef8e047847fcd2c5b6f50c16965f924fd99fe709"
   integrity sha512-4diPfzWbLEIElVG4AnqP+00SULlPzNuyJFNnmMrLgyaxG6tZXJ1sn7mjBu4fHrJE+Yp/jgylOweJn2xsLMFggQ==
@@ -784,7 +851,7 @@ alphanum-sort@^1.0.0:
   resolved "https://registry.yarnpkg.com/alphanum-sort/-/alphanum-sort-1.0.2.tgz#97a1119649b211ad33691d9f9f486a8ec9fbe0a3"
   integrity sha1-l6ERlkmyEa0zaR2fn0hqjsn74KM=
 
-ansi-escapes@^3.0.0:
+ansi-escapes@^3.2.0:
   version "3.2.0"
   resolved "https://registry.yarnpkg.com/ansi-escapes/-/ansi-escapes-3.2.0.tgz#8780b98ff9dbf5638152d1f1fe5c1d7b4442976b"
   integrity sha512-cBhpre4ma+U0T1oM5fXg7Dy1Jw7zzwv7lt/GoCpr+hDQJoYnKVPLL4dCvSEFMmQurOQvSrwT7SL/DAlhBI97RQ==
@@ -806,6 +873,11 @@ ansi-regex@^3.0.0:
   resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-3.0.0.tgz#ed0317c322064f79466c02966bddb605ab37d998"
   integrity sha1-7QMXwyIGT3lGbAKWa922Bas32Zg=
 
+ansi-regex@^4.1.0:
+  version "4.1.0"
+  resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-4.1.0.tgz#8b9f8f08cf1acb843756a839ca8c7e3168c51997"
+  integrity sha512-1apePfXM1UOSqw0o9IiFAovVz9M5S1Dg+4TrDwfMewQ6p/rmMueb7tWZjQ1rx4Loy1ArBggoqGpfqqdI4rondg==
+
 ansi-styles@^2.2.1:
   version "2.2.1"
   resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-2.2.1.tgz#b432dd3358b634cf75e1e4664368240533c1ddbe"
@@ -823,6 +895,14 @@ ansi-wrap@0.1.0:
   resolved "https://registry.yarnpkg.com/ansi-wrap/-/ansi-wrap-0.1.0.tgz#a82250ddb0015e9a27ca82e82ea603bbfa45efaf"
   integrity sha1-qCJQ3bABXponyoLoLqYDu/pF768=
 
+anymatch@^2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/anymatch/-/anymatch-2.0.0.tgz#bcb24b4f37934d9aa7ac17b4adaf89e7c76ef2eb"
+  integrity sha512-5teOsQWABXHHBFP9y3skS5P3d/WfWXpv3FUpy+LorMrNYaT9pI4oLMQX7jzQ2KklNpGpWHzdCXTDT2Y3XGlZBw==
+  dependencies:
+    micromatch "^3.1.4"
+    normalize-path "^2.1.1"
+
 anymatch@^3.0.1:
   version "3.0.2"
   resolved "https://registry.yarnpkg.com/anymatch/-/anymatch-3.0.2.tgz#ddb3a8495d44875423af7b919aace11e91732a41"
@@ -831,6 +911,11 @@ anymatch@^3.0.1:
     normalize-path "^3.0.0"
     picomatch "^2.0.4"
 
+aproba@^1.0.3:
+  version "1.2.0"
+  resolved "https://registry.yarnpkg.com/aproba/-/aproba-1.2.0.tgz#6802e6264efd18c790a1b0d517f0f2627bf2c94a"
+  integrity sha512-Y9J6ZjXtoYh8RnXVCMOU/ttDmk1aBjunq9vO0ta5x85WDQiQfUF9sIPBITdbiiIVcBo03Hi3jMxigBtsddlXRw==
+
 arch@^2.1.0:
   version "2.1.1"
   resolved "https://registry.yarnpkg.com/arch/-/arch-2.1.1.tgz#8f5c2731aa35a30929221bb0640eed65175ec84e"
@@ -843,7 +928,15 @@ archive-type@^4.0.0:
   dependencies:
     file-type "^4.2.0"
 
-argparse@^1.0.7:
+are-we-there-yet@~1.1.2:
+  version "1.1.5"
+  resolved "https://registry.yarnpkg.com/are-we-there-yet/-/are-we-there-yet-1.1.5.tgz#4b35c2944f062a8bfcda66410760350fe9ddfc21"
+  integrity sha512-5hYdAkZlcG8tOLujVDTgCT+uPX0VnpAH28gWsLfzpXYm7wP6mp5Q/gYyR7YQ0cKVJcXJnl3j2kpBan13PtQf6w==
+  dependencies:
+    delegates "^1.0.0"
+    readable-stream "^2.0.6"
+
+argparse@^1.0.10, argparse@^1.0.7:
   version "1.0.10"
   resolved "https://registry.yarnpkg.com/argparse/-/argparse-1.0.10.tgz#bcd6791ea5ae09725e17e5ad988134cd40b3d911"
   integrity sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==
@@ -947,7 +1040,7 @@ assign-symbols@^1.0.0:
   resolved "https://registry.yarnpkg.com/assign-symbols/-/assign-symbols-1.0.0.tgz#59667f41fadd4f20ccbc2bb96b8d4f7f78ec0367"
   integrity sha1-WWZ/QfrdTyDMvCu5a41Pf3jsA2c=
 
-async-each@^1.0.3:
+async-each@^1.0.1:
   version "1.0.3"
   resolved "https://registry.yarnpkg.com/async-each/-/async-each-1.0.3.tgz#b727dbf87d7651602f06f4d4ac387f47d91b0cbf"
   integrity sha512-z/WhQ5FPySLdvREByI2vZiTWwCnF0moMJ1hK9YQwDTHKh6I7/uSckMetoRGb5UBZPC1z0jlw+n/XCgjeH7y1AQ==
@@ -967,6 +1060,13 @@ atob@^2.1.1:
   resolved "https://registry.yarnpkg.com/atob/-/atob-2.1.2.tgz#6d9517eb9e030d2436666651e86bd9f6f13533c9"
   integrity sha512-Wm6ukoaOGJi/73p/cl2GvLjTI5JM1k/O14isD73YML8StrH/7/lRFgmg8nICZgD3bZZvjwCGxtMOD3wWNAu8cg==
 
+autolinker@^3.11.0:
+  version "3.11.0"
+  resolved "https://registry.yarnpkg.com/autolinker/-/autolinker-3.11.0.tgz#209c4632550eed32285058eaac51f1382dae023a"
+  integrity sha512-VMTEjE3jeBK5MinTZiuVE07O4wMVmXhpzmc5sCc8cap6exsVzjmQJgtH8NqHsFru58ujUieBA9Dmwiz+E5KWEA==
+  dependencies:
+    tslib "^1.9.3"
+
 autolinker@~0.15.0:
   version "0.15.3"
   resolved "https://registry.yarnpkg.com/autolinker/-/autolinker-0.15.3.tgz#342417d8f2f3461b14cf09088d5edf8791dc9832"
@@ -995,7 +1095,7 @@ aws4@^1.8.0:
   resolved "https://registry.yarnpkg.com/aws4/-/aws4-1.8.0.tgz#f0e003d9ca9e7f59c7a508945d7b2ef9a04a542f"
   integrity sha512-ReZxvNHIOv88FlT7rxcXIIC0fPt4KZqZbOlivyWtXLt8ESx84zd3kMC6iK5jVeS2qt+g7ftS7ye4fi06X5rtRQ==
 
-babel-code-frame@6.26.0:
+babel-code-frame@^6.22.0:
   version "6.26.0"
   resolved "https://registry.yarnpkg.com/babel-code-frame/-/babel-code-frame-6.26.0.tgz#63fd43f7dc1e3bb7ce35947db8fe369a3f58c74b"
   integrity sha1-Y/1D99weO7fONZR9uP42mj9Yx0s=
@@ -1004,7 +1104,14 @@ babel-code-frame@6.26.0:
     esutils "^2.0.2"
     js-tokens "^3.0.2"
 
-babylon@^6.17.4:
+babel-plugin-dynamic-import-node@^2.3.0:
+  version "2.3.0"
+  resolved "https://registry.yarnpkg.com/babel-plugin-dynamic-import-node/-/babel-plugin-dynamic-import-node-2.3.0.tgz#f00f507bdaa3c3e3ff6e7e5e98d90a7acab96f7f"
+  integrity sha512-o6qFkpeQEBxcqt0XYlWzAVxNCSCZdUgcR8IRlhD/8DylxjjO4foPcvTW0GGKa/cVt3rvxZ7o5ippJ+/0nvLhlQ==
+  dependencies:
+    object.assign "^4.1.0"
+
+babylon@^6.18.0:
   version "6.18.0"
   resolved "https://registry.yarnpkg.com/babylon/-/babylon-6.18.0.tgz#af2f3b88fa6f5c1e4c634d1a0f8eac4f55b395e3"
   integrity sha512-q/UEjfGJ2Cm3oKV71DJz9d25TPnq5rhBVL2Q4fA5wcC3jcrdn7+SssEybFIxwAvvP+YCsCYNKughoF33GxgycQ==
@@ -1039,6 +1146,11 @@ bcrypt-pbkdf@^1.0.0:
   dependencies:
     tweetnacl "^0.14.3"
 
+big.js@^5.2.2:
+  version "5.2.2"
+  resolved "https://registry.yarnpkg.com/big.js/-/big.js-5.2.2.tgz#65f0af382f578bcdc742bd9c281e9cb2d7768328"
+  integrity sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==
+
 bin-build@^3.0.0:
   version "3.0.0"
   resolved "https://registry.yarnpkg.com/bin-build/-/bin-build-3.0.0.tgz#c5780a25a8a9f966d8244217e6c1f5082a143861"
@@ -1087,6 +1199,11 @@ bin-wrapper@^4.0.0:
     os-filter-obj "^2.0.0"
     pify "^4.0.1"
 
+binary-extensions@^1.0.0:
+  version "1.13.1"
+  resolved "https://registry.yarnpkg.com/binary-extensions/-/binary-extensions-1.13.1.tgz#598afe54755b2868a5330d2aff9d4ebb53209b65"
+  integrity sha512-Un7MIEDdUC5gNpcGDV97op1Ywk748MpHcFTHoYs6qnj1Z3j7I53VG3nwZhKzoBZmbdRNnb6WRdFlwl7tSDuZGw==
+
 binary-extensions@^2.0.0:
   version "2.0.0"
   resolved "https://registry.yarnpkg.com/binary-extensions/-/binary-extensions-2.0.0.tgz#23c0df14f6a88077f5f986c0d167ec03c3d5537c"
@@ -1131,7 +1248,7 @@ boolbase@^1.0.0, boolbase@~1.0.0:
   resolved "https://registry.yarnpkg.com/boolbase/-/boolbase-1.0.0.tgz#68dff5fbe60c51eb37725ea9e3ed310dcc1e776e"
   integrity sha1-aN/1++YMUes3cl6p4+0xDcwed24=
 
-brace-expansion@^1.0.0, brace-expansion@^1.1.7:
+brace-expansion@^1.1.7:
   version "1.1.11"
   resolved "https://registry.yarnpkg.com/brace-expansion/-/brace-expansion-1.1.11.tgz#3c7fcbf529d87226f3d2f52b966ff5271eb441dd"
   integrity sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==
@@ -1139,7 +1256,7 @@ brace-expansion@^1.0.0, brace-expansion@^1.1.7:
     balanced-match "^1.0.0"
     concat-map "0.0.1"
 
-braces@^2.3.1:
+braces@^2.3.1, braces@^2.3.2:
   version "2.3.2"
   resolved "https://registry.yarnpkg.com/braces/-/braces-2.3.2.tgz#5979fd3f14cd531565e5fa2df1abfff1dfaee729"
   integrity sha512-aNdbnj9P8PjdXU4ybaWLK2IF3jc/EoDYbC7AazW6to3TRsfXxscC9UXOB5iDiEQrkyIbWp2SLQda4+QAa7nc3w==
@@ -1162,6 +1279,15 @@ braces@^3.0.2:
   dependencies:
     fill-range "^7.0.1"
 
+browserslist@4.6.6:
+  version "4.6.6"
+  resolved "https://registry.yarnpkg.com/browserslist/-/browserslist-4.6.6.tgz#6e4bf467cde520bc9dbdf3747dafa03531cec453"
+  integrity sha512-D2Nk3W9JL9Fp/gIcWei8LrERCS+eXu9AM5cfXA8WEZ84lFks+ARnZ0q/R69m2SV3Wjma83QDDPxsNKXUwdIsyA==
+  dependencies:
+    caniuse-lite "^1.0.30000984"
+    electron-to-chromium "^1.3.191"
+    node-releases "^1.1.25"
+
 browserslist@^4.0.0, browserslist@^4.6.0, browserslist@^4.6.1, browserslist@^4.6.2:
   version "4.6.3"
   resolved "https://registry.yarnpkg.com/browserslist/-/browserslist-4.6.3.tgz#0530cbc6ab0c1f3fc8c819c72377ba55cf647f05"
@@ -1297,6 +1423,11 @@ caniuse-lite@^1.0.0, caniuse-lite@^1.0.30000971, caniuse-lite@^1.0.30000975:
   resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30000979.tgz#92f16d00186a6cf20d6c5711bb6e042a3d667029"
   integrity sha512-gcu45yfq3B7Y+WB05fOMfr0EiSlq+1u+m6rPHyJli/Wy3PVQNGaU7VA4bZE5qw+AU2UVOBR/N5g1bzADUqdvFw==
 
+caniuse-lite@^1.0.30000984:
+  version "1.0.30000989"
+  resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30000989.tgz#b9193e293ccf7e4426c5245134b8f2a56c0ac4b9"
+  integrity sha512-vrMcvSuMz16YY6GSVZ0dWDTJP8jqk3iFQ/Aq5iqblPwxSVVZI+zxDyTX0VPqtQsDnfdrBDcsmhgTEOh5R8Lbpw==
+
 caseless@~0.12.0:
   version "0.12.0"
   resolved "https://registry.yarnpkg.com/caseless/-/caseless-0.12.0.tgz#1b681c21ff84033c826543090689420d187151dc"
@@ -1312,7 +1443,16 @@ caw@^2.0.0, caw@^2.0.1:
     tunnel-agent "^0.6.0"
     url-to-options "^1.0.1"
 
-chalk@1.1.3, chalk@^1.0.0, chalk@^1.1.3:
+chalk@2.4.2, chalk@^2.0.0, chalk@^2.4.1, chalk@^2.4.2:
+  version "2.4.2"
+  resolved "https://registry.yarnpkg.com/chalk/-/chalk-2.4.2.tgz#cd42541677a54333cf541a49108c1432b44c9424"
+  integrity sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==
+  dependencies:
+    ansi-styles "^3.2.1"
+    escape-string-regexp "^1.0.5"
+    supports-color "^5.3.0"
+
+chalk@^1.0.0, chalk@^1.1.3:
   version "1.1.3"
   resolved "https://registry.yarnpkg.com/chalk/-/chalk-1.1.3.tgz#a8115c55e4a702fe4d150abd3872822a7e09fc98"
   integrity sha1-qBFcVeSnAv5NFQq9OHKCKn4J/Jg=
@@ -1323,15 +1463,6 @@ chalk@1.1.3, chalk@^1.0.0, chalk@^1.1.3:
     strip-ansi "^3.0.0"
     supports-color "^2.0.0"
 
-chalk@^2.0.0, chalk@^2.4.1, chalk@^2.4.2:
-  version "2.4.2"
-  resolved "https://registry.yarnpkg.com/chalk/-/chalk-2.4.2.tgz#cd42541677a54333cf541a49108c1432b44c9424"
-  integrity sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==
-  dependencies:
-    ansi-styles "^3.2.1"
-    escape-string-regexp "^1.0.5"
-    supports-color "^5.3.0"
-
 chalk@^2.3.0:
   version "2.4.1"
   resolved "https://registry.yarnpkg.com/chalk/-/chalk-2.4.1.tgz#18c49ab16a037b6eb0152cc83e3471338215b66e"
@@ -1341,10 +1472,10 @@ chalk@^2.3.0:
     escape-string-regexp "^1.0.5"
     supports-color "^5.3.0"
 
-chardet@^0.4.0:
-  version "0.4.2"
-  resolved "https://registry.yarnpkg.com/chardet/-/chardet-0.4.2.tgz#b5473b33dc97c424e5d98dc87d55d4d8a29c8bf2"
-  integrity sha1-tUc7M9yXxCTl2Y3IfVXU2KKci/I=
+chardet@^0.7.0:
+  version "0.7.0"
+  resolved "https://registry.yarnpkg.com/chardet/-/chardet-0.7.0.tgz#90094849f0937f2eedc2425d0d28a9e5f0cbad9e"
+  integrity sha512-mT8iDcrh03qDGRRmoA2hmBJnxpllMR+0/0qlzjqZES6NdiWDcZkCNAk4rPFZ9Q85r27unkiNNg8ZOiwZXBHwcA==
 
 cheerio@0.22.0:
   version "0.22.0"
@@ -1368,22 +1499,45 @@ cheerio@0.22.0:
     lodash.reject "^4.4.0"
     lodash.some "^4.4.0"
 
-chokidar@^3.0.1:
-  version "3.0.1"
-  resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-3.0.1.tgz#98fe9aa476c55d9aea7841d6325ffdb30e95b40c"
-  integrity sha512-2ww34sJWehnbpV0Q4k4V5Hh7juo7po6z7LUWkcIQnSGN1lHOL8GGtLtfwabKvLFQw/hbSUQ0u6V7OgGYgBzlkQ==
+chokidar@^2.0.4:
+  version "2.1.8"
+  resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-2.1.8.tgz#804b3a7b6a99358c3c5c61e71d8728f041cff917"
+  integrity sha512-ZmZUazfOzf0Nve7duiCKD23PFSCs4JPoYyccjUFF3aQkQadqBhfzhjkwBH2mNOG9cTBwhamM37EIsIkZw3nRgg==
+  dependencies:
+    anymatch "^2.0.0"
+    async-each "^1.0.1"
+    braces "^2.3.2"
+    glob-parent "^3.1.0"
+    inherits "^2.0.3"
+    is-binary-path "^1.0.0"
+    is-glob "^4.0.0"
+    normalize-path "^3.0.0"
+    path-is-absolute "^1.0.0"
+    readdirp "^2.2.1"
+    upath "^1.1.1"
+  optionalDependencies:
+    fsevents "^1.2.7"
+
+chokidar@^3.0.2:
+  version "3.0.2"
+  resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-3.0.2.tgz#0d1cd6d04eb2df0327446188cd13736a3367d681"
+  integrity sha512-c4PR2egjNjI1um6bamCQ6bUNPDiyofNQruHvKgHQ4gDUP/ITSVSzNsiI5OWtHOsX323i5ha/kk4YmOZ1Ktg7KA==
   dependencies:
     anymatch "^3.0.1"
-    async-each "^1.0.3"
     braces "^3.0.2"
     glob-parent "^5.0.0"
     is-binary-path "^2.1.0"
     is-glob "^4.0.1"
     normalize-path "^3.0.0"
-    readdirp "^3.0.2"
+    readdirp "^3.1.1"
   optionalDependencies:
     fsevents "^2.0.6"
 
+chownr@^1.1.1:
+  version "1.1.2"
+  resolved "https://registry.yarnpkg.com/chownr/-/chownr-1.1.2.tgz#a18f1e0b269c8a6a5d3c86eb298beb14c3dd7bf6"
+  integrity sha512-GkfeAQh+QNy3wquu9oIZr6SS5x7wGdSgNQvD10X3r+AZr1Oys22HW8kAmDMvNg2+Dm0TeGaEuO8gFwdBXxwO8A==
+
 ci-info@^2.0.0:
   version "2.0.0"
   resolved "https://registry.yarnpkg.com/ci-info/-/ci-info-2.0.0.tgz#67a9e964be31a51e15e5010d58e6f12834002f46"
@@ -1441,6 +1595,11 @@ coa@^2.0.2:
     chalk "^2.4.1"
     q "^1.1.2"
 
+code-point-at@^1.0.0:
+  version "1.1.0"
+  resolved "https://registry.yarnpkg.com/code-point-at/-/code-point-at-1.1.0.tgz#0d070b4d043a5bea33a2f1a40e2edb3d9a4ccf77"
+  integrity sha1-DQcLTQQ6W+ozovGkDi7bPZpMz3c=
+
 coffee-script@^1.12.4:
   version "1.12.7"
   resolved "https://registry.yarnpkg.com/coffee-script/-/coffee-script-1.12.7.tgz#c05dae0cb79591d05b3070a8433a98c9a89ccc53"
@@ -1547,6 +1706,11 @@ config-chain@^1.1.11:
     ini "^1.3.4"
     proto-list "~1.2.1"
 
+console-control-strings@^1.0.0, console-control-strings@~1.1.0:
+  version "1.1.0"
+  resolved "https://registry.yarnpkg.com/console-control-strings/-/console-control-strings-1.1.0.tgz#3d7cf4464db6446ea644bf4b39507f9851008e8e"
+  integrity sha1-PXz0Rk22RG6mRL9LOVB/mFEAjo4=
+
 console-stream@^0.1.1:
   version "0.1.1"
   resolved "https://registry.yarnpkg.com/console-stream/-/console-stream-0.1.1.tgz#a095fe07b20465955f2fafd28b5d72bccd949d44"
@@ -1640,16 +1804,7 @@ cosmiconfig@^5.0.7:
     js-yaml "^3.13.0"
     parse-json "^4.0.0"
 
-cross-spawn@5.1.0, cross-spawn@^5.0.1:
-  version "5.1.0"
-  resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-5.1.0.tgz#e8bd0efee58fcff6f8f94510a0a554bbfa235449"
-  integrity sha1-6L0O/uWPz/b4+UUQoKVUu/ojVEk=
-  dependencies:
-    lru-cache "^4.0.1"
-    shebang-command "^1.2.0"
-    which "^1.2.9"
-
-cross-spawn@^6.0.0, cross-spawn@^6.0.5:
+cross-spawn@6.0.5, cross-spawn@^6.0.0, cross-spawn@^6.0.5:
   version "6.0.5"
   resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-6.0.5.tgz#4a5ec7c64dfae22c3a14124dbacdee846d80cbc4"
   integrity sha512-eTVLrBSt7fjbDygz805pMnstIs2VTBNkRm0qxZd+M7A5XDdxVRWO5MxGBXZhjY4cqLYLdtrGqRf8mBPmzwSpWQ==
@@ -1660,6 +1815,15 @@ cross-spawn@^6.0.0, cross-spawn@^6.0.5:
     shebang-command "^1.2.0"
     which "^1.2.9"
 
+cross-spawn@^5.0.1:
+  version "5.1.0"
+  resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-5.1.0.tgz#e8bd0efee58fcff6f8f94510a0a554bbfa235449"
+  integrity sha1-6L0O/uWPz/b4+UUQoKVUu/ojVEk=
+  dependencies:
+    lru-cache "^4.0.1"
+    shebang-command "^1.2.0"
+    which "^1.2.9"
+
 crowdin-cli@^0.3.0:
   version "0.3.0"
   resolved "https://registry.yarnpkg.com/crowdin-cli/-/crowdin-cli-0.3.0.tgz#eac9989a6fe7feaaf33090397afc187c67b46191"
@@ -1832,19 +1996,21 @@ dashdash@^1.12.0:
   dependencies:
     assert-plus "^1.0.0"
 
-debug@0.7.4:
-  version "0.7.4"
-  resolved "https://registry.yarnpkg.com/debug/-/debug-0.7.4.tgz#06e1ea8082c2cb14e39806e22e2f6f757f92af39"
-  integrity sha1-BuHqgILCyxTjmAbiLi9vdX+Srzk=
-
-debug@2.6.9, debug@^2.2.0, debug@^2.3.3, debug@^2.6.0, debug@^2.6.6:
+debug@2.6.9, debug@^2.2.0, debug@^2.3.3, debug@^2.6.0:
   version "2.6.9"
   resolved "https://registry.yarnpkg.com/debug/-/debug-2.6.9.tgz#5d128515df134ff327e90a4c93f4e077a536341f"
   integrity sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==
   dependencies:
     ms "2.0.0"
 
-debug@^3.1.0:
+debug@4.1.0:
+  version "4.1.0"
+  resolved "https://registry.yarnpkg.com/debug/-/debug-4.1.0.tgz#373687bffa678b38b1cd91f861b63850035ddc87"
+  integrity sha512-heNPJUJIqC+xB6ayLAMHaIrmN9HKa7aQO8MGqKpvCA+uJYVcvR6l5kgdrhRuwPFHU7P5/A1w0BjByPHwpfTDKg==
+  dependencies:
+    ms "^2.1.1"
+
+debug@^3.1.0, debug@^3.2.5, debug@^3.2.6:
   version "3.2.6"
   resolved "https://registry.yarnpkg.com/debug/-/debug-3.2.6.tgz#e83d17de16d8a7efb7717edbe5fb10135eee629b"
   integrity sha512-mel+jf7nrtEl5Pn1Qx46zARXKDpBbvzezse7p7LqINmdoIk8PYP5SySaxEmYv6TZ0JyEKA1hsCId6DIhgITtWQ==
@@ -1928,10 +2094,15 @@ decompress@^4.0.0, decompress@^4.2.0:
     pify "^2.3.0"
     strip-dirs "^2.0.0"
 
-deep-is@0.1.2:
-  version "0.1.2"
-  resolved "https://registry.yarnpkg.com/deep-is/-/deep-is-0.1.2.tgz#9ced65ea0bc0b09f42a6d79c1b1903f9d913cc18"
-  integrity sha1-nO1l6gvAsJ9CptecGxkD+dkTzBg=
+deep-extend@^0.6.0:
+  version "0.6.0"
+  resolved "https://registry.yarnpkg.com/deep-extend/-/deep-extend-0.6.0.tgz#c4fa7c95404a17a9c3e8ca7e1537312b736330ac"
+  integrity sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA==
+
+deep-is@^0.1.3:
+  version "0.1.3"
+  resolved "https://registry.yarnpkg.com/deep-is/-/deep-is-0.1.3.tgz#b369d6fb5dbc13eecf524f91b070feedc357cf34"
+  integrity sha1-s2nW+128E+7PUk+RsHD+7cNXzzQ=
 
 define-properties@^1.1.2, define-properties@^1.1.3:
   version "1.1.3"
@@ -1972,6 +2143,11 @@ delegate@^3.1.2:
   resolved "https://registry.yarnpkg.com/delegate/-/delegate-3.2.0.tgz#b66b71c3158522e8ab5744f720d8ca0c2af59166"
   integrity sha512-IofjkYBZaZivn0V8nnsMJGBr4jVLxHDheKSW88PyxS5QC4Vo9ZbZVvhzlSxY87fVq3STR6r+4cGepyHkcWOQSw==
 
+delegates@^1.0.0:
+  version "1.0.0"
+  resolved "https://registry.yarnpkg.com/delegates/-/delegates-1.0.0.tgz#84c6e159b81904fdca59a0ef44cd870d31250f9a"
+  integrity sha1-hMbhWbgZBP3KWaDvRM2HDTElD5o=
+
 depd@~1.1.2:
   version "1.1.2"
   resolved "https://registry.yarnpkg.com/depd/-/depd-1.1.2.tgz#9bcd52e14c097763e749b274c4346ed2e560b5a9"
@@ -1982,6 +2158,11 @@ destroy@~1.0.4:
   resolved "https://registry.yarnpkg.com/destroy/-/destroy-1.0.4.tgz#978857442c44749e4206613e37946205826abd80"
   integrity sha1-l4hXRCxEdJ5CBmE+N5RiBYJqvYA=
 
+detect-libc@^1.0.2:
+  version "1.0.3"
+  resolved "https://registry.yarnpkg.com/detect-libc/-/detect-libc-1.0.3.tgz#fa137c4bd698edf55cd5cd02ac559f91a4c4ba9b"
+  integrity sha1-+hN8S9aY7fVc1c0CrFWfkaTEups=
+
 detect-port-alt@1.1.6:
   version "1.1.6"
   resolved "https://registry.yarnpkg.com/detect-port-alt/-/detect-port-alt-1.1.6.tgz#24707deabe932d4a3cf621302027c2b266568275"
@@ -2003,56 +2184,56 @@ dir-glob@2.0.0:
     arrify "^1.0.1"
     path-type "^3.0.0"
 
-docusaurus@1.11.1:
-  version "1.11.1"
-  resolved "https://registry.yarnpkg.com/docusaurus/-/docusaurus-1.11.1.tgz#786bae93946bc21ab7ef457c5672e2e2bd930b25"
-  integrity sha512-oIdftD4E8dnzXcNohTdE6MICsiJIR1pAmKa/sRHDiG3T3v8f2eiq9nt88CidSIPpyEw50TbCr3bOoExHS90UGg==
-  dependencies:
-    "@babel/core" "^7.0.0"
-    "@babel/plugin-proposal-class-properties" "^7.0.0"
-    "@babel/plugin-proposal-object-rest-spread" "^7.0.0"
-    "@babel/polyfill" "^7.0.0"
-    "@babel/preset-env" "^7.0.0"
+docusaurus@1.12.0:
+  version "1.12.0"
+  resolved "https://registry.yarnpkg.com/docusaurus/-/docusaurus-1.12.0.tgz#c2b626b95e8b8e5a39b597801c260746ca32fb16"
+  integrity sha512-C8HUDctWn72JOxqwnP6/+fUUQFADIjNw9Tvgw9CBlXLVN6CUhuTrk3YShM5EjZILjIrcmReoHcy6lCDkCa2X8Q==
+  dependencies:
+    "@babel/core" "^7.5.5"
+    "@babel/plugin-proposal-class-properties" "^7.5.5"
+    "@babel/plugin-proposal-object-rest-spread" "^7.5.5"
+    "@babel/polyfill" "^7.4.4"
+    "@babel/preset-env" "^7.5.5"
     "@babel/preset-react" "^7.0.0"
-    "@babel/register" "^7.0.0"
-    "@babel/traverse" "^7.0.0"
-    "@babel/types" "^7.1.2"
+    "@babel/register" "^7.5.5"
+    "@babel/traverse" "^7.5.5"
+    "@babel/types" "^7.5.5"
     autoprefixer "^9.6.0"
-    babylon "^6.17.4"
+    babylon "^6.18.0"
     chalk "^2.4.2"
-    chokidar "^3.0.1"
+    chokidar "^3.0.2"
     classnames "^2.2.6"
     color "^2.0.1"
     commander "^2.20.0"
     cross-spawn "^6.0.5"
     crowdin-cli "^0.3.0"
     cssnano "^4.1.0"
-    escape-string-regexp "^1.0.5"
+    escape-string-regexp "^2.0.0"
     express "^4.17.1"
     feed "^1.1.0"
-    fs-extra "^5.0.0"
-    gaze "^1.1.2"
+    fs-extra "^8.1.0"
+    gaze "^1.1.3"
     glob "^7.1.3"
-    highlight.js "^9.12.0"
+    highlight.js "^9.15.8"
     imagemin "^6.0.0"
     imagemin-gifsicle "^6.0.1"
     imagemin-jpegtran "^6.0.0"
     imagemin-optipng "^6.0.0"
     imagemin-svgo "^7.0.0"
-    lodash "^4.17.11"
+    lodash "^4.17.14"
     markdown-toc "^1.2.0"
     mkdirp "^0.5.1"
-    portfinder "^1.0.17"
-    postcss "^7.0.1"
-    prismjs "^1.15.0"
-    react "^16.5.0"
-    react-dev-utils "^5.0.2"
-    react-dom "^16.5.0"
+    portfinder "^1.0.21"
+    postcss "^7.0.17"
+    prismjs "^1.16.0"
+    react "^16.8.4"
+    react-dev-utils "^9.0.1"
+    react-dom "^16.8.4"
     remarkable "^1.7.1"
-    request "^2.87.0"
+    request "^2.88.0"
     shelljs "^0.8.3"
-    sitemap "^1.13.0"
-    tcp-port-used "^0.1.2"
+    sitemap "^3.2.2"
+    tcp-port-used "^1.0.1"
     tiny-lr "^1.1.1"
     tree-node-cli "^1.2.5"
     truncate-html "^1.0.1"
@@ -2163,6 +2344,16 @@ electron-to-chromium@^1.3.164:
   resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.3.181.tgz#1c538401af8f3eb285db893b66e43f4bea72fd83"
   integrity sha512-xf1dCoc6FSCVcNQu8VGiMSH55rOT/ov6U7UpMgw4Erg5KfD1LHTXqm34/IGp55TLX4WqwuT4IIeJWhdGhO8mYw==
 
+electron-to-chromium@^1.3.191:
+  version "1.3.252"
+  resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.3.252.tgz#5b6261965b564a0f4df0f1c86246487897017f52"
+  integrity sha512-NWJ5TztDnjExFISZHFwpoJjMbLUifsNBnx7u2JI0gCw6SbKyQYYWWtBHasO/jPtHym69F4EZuTpRNGN11MT/jg==
+
+emojis-list@^2.0.0:
+  version "2.1.0"
+  resolved "https://registry.yarnpkg.com/emojis-list/-/emojis-list-2.1.0.tgz#4daa4d9db00f9819880c79fa457ae5b09a1fd389"
+  integrity sha1-TapNnbAPmBmIDHn6RXrlsJof04k=
+
 encodeurl@~1.0.2:
   version "1.0.2"
   resolved "https://registry.yarnpkg.com/encodeurl/-/encodeurl-1.0.2.tgz#ad3ff4c86ec2d029322f5a02c3a9a606c95b3f59"
@@ -2233,6 +2424,11 @@ escape-string-regexp@1.0.5, escape-string-regexp@^1.0.2, escape-string-regexp@^1
   resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz#1b61c0562190a8dff6ae3bb2cf0200ca130b86d4"
   integrity sha1-G2HAViGQqN/2rjuyzwIAyhMLhtQ=
 
+escape-string-regexp@^2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-2.0.0.tgz#a30304e99daa32e23b2fd20f51babd07cffca344"
+  integrity sha512-UpzcLCXolUWcNu5HtVMHYdXJjArjsF9C0aNnquZYY4uW/Vu0miy5YoWvbV345HauVvcAUnpRuhMMcqTcGOY2+w==
+
 esprima@^4.0.0:
   version "4.0.1"
   resolved "https://registry.yarnpkg.com/esprima/-/esprima-4.0.1.tgz#13b04cdb3e6c5d19df91ab6987a8695619b0aa71"
@@ -2248,12 +2444,12 @@ etag@~1.8.1:
   resolved "https://registry.yarnpkg.com/etag/-/etag-1.8.1.tgz#41ae2eeb65efa62268aebfea83ac7d79299b0887"
   integrity sha1-Qa4u62XvpiJorr/qg6x9eSmbCIc=
 
-eventsource@0.1.6:
-  version "0.1.6"
-  resolved "https://registry.yarnpkg.com/eventsource/-/eventsource-0.1.6.tgz#0acede849ed7dd1ccc32c811bb11b944d4f29232"
-  integrity sha1-Cs7ehJ7X3RzMMsgRuxG5RNTykjI=
+eventsource@^1.0.7:
+  version "1.0.7"
+  resolved "https://registry.yarnpkg.com/eventsource/-/eventsource-1.0.7.tgz#8fbc72c93fcd34088090bc0a4e64f4b5cee6d8d0"
+  integrity sha512-4Ln17+vVT0k8aWq+t/bF5arcS3EpT9gYtW66EPacdj/mAFevznsnyoHLPy2BA8gbIQeIHoPsvwmfBftfcG//BQ==
   dependencies:
-    original ">=0.0.5"
+    original "^1.0.0"
 
 exec-buffer@^3.0.0:
   version "3.2.0"
@@ -2332,13 +2528,6 @@ expand-range@^1.8.1:
   dependencies:
     fill-range "^2.1.0"
 
-expand-tilde@^2.0.0, expand-tilde@^2.0.2:
-  version "2.0.2"
-  resolved "https://registry.yarnpkg.com/expand-tilde/-/expand-tilde-2.0.2.tgz#97e801aa052df02454de46b02bf621642cdc8502"
-  integrity sha1-l+gBqgUt8CRU3kawK/YhZCzchQI=
-  dependencies:
-    homedir-polyfill "^1.0.1"
-
 express@^4.17.1:
   version "4.17.1"
   resolved "https://registry.yarnpkg.com/express/-/express-4.17.1.tgz#4491fc38605cf51f8629d39c2b5d026f98a4c134"
@@ -2410,13 +2599,13 @@ extend@~3.0.2:
   resolved "https://registry.yarnpkg.com/extend/-/extend-3.0.2.tgz#f8b1136b4071fbd8eb140aff858b1019ec2915fa"
   integrity sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==
 
-external-editor@^2.0.4:
-  version "2.2.0"
-  resolved "https://registry.yarnpkg.com/external-editor/-/external-editor-2.2.0.tgz#045511cfd8d133f3846673d1047c154e214ad3d5"
-  integrity sha512-bSn6gvGxKt+b7+6TKEv1ZycHleA7aHhRHyAqJyp5pbUFuYYNIzpZnQDk7AsYckyWdEnTeAnay0aCy2aV6iTk9A==
+external-editor@^3.0.3:
+  version "3.1.0"
+  resolved "https://registry.yarnpkg.com/external-editor/-/external-editor-3.1.0.tgz#cb03f740befae03ea4d283caed2741a83f335495"
+  integrity sha512-hMQ4CX1p1izmuLYyZqLMO/qGNw10wSv9QDCPfzXfyFrOaCSSoRfqE1Kf1s5an66J5JZC62NewG+mK49jOCtQew==
   dependencies:
-    chardet "^0.4.0"
-    iconv-lite "^0.4.17"
+    chardet "^0.7.0"
+    iconv-lite "^0.4.24"
     tmp "^0.0.33"
 
 extglob@^2.0.4:
@@ -2472,7 +2661,7 @@ faye-websocket@~0.10.0:
   dependencies:
     websocket-driver ">=0.5.1"
 
-faye-websocket@~0.11.0:
+faye-websocket@~0.11.1:
   version "0.11.3"
   resolved "https://registry.yarnpkg.com/faye-websocket/-/faye-websocket-0.11.3.tgz#5c0e9a8968e8912c286639fde977a8b209f2508e"
   integrity sha512-D2y4bovYpzziGgbHYtGCMjlJM36vAl/y+xUyn1C+FVx8szd1E+86KwVw6XvYSzOP8iMpm1X0I4xJD+QtUb36OA==
@@ -2552,10 +2741,10 @@ filenamify@^2.0.0:
     strip-outer "^1.0.0"
     trim-repeated "^1.0.0"
 
-filesize@3.5.11:
-  version "3.5.11"
-  resolved "https://registry.yarnpkg.com/filesize/-/filesize-3.5.11.tgz#1919326749433bb3cf77368bd158caabcc19e9ee"
-  integrity sha512-ZH7loueKBoDb7yG9esn1U+fgq7BzlzW6NRi5/rMdxIZ05dj7GFD/Xc5rq2CDt5Yq86CyfSYVyx4242QQNZbx1g==
+filesize@3.6.1:
+  version "3.6.1"
+  resolved "https://registry.yarnpkg.com/filesize/-/filesize-3.6.1.tgz#090bb3ee01b6f801a8a8be99d31710b3422bb317"
+  integrity sha512-7KjR1vv6qnicaPMi1iiTcI85CyYwRO/PSFCu6SvqL8jN2Wjt/NIYQTFtFs7fSDCYOstUkEWIQGFUg5YZQfjlcg==
 
 fill-range@^2.1.0:
   version "2.2.4"
@@ -2607,6 +2796,13 @@ find-cache-dir@^2.0.0:
     make-dir "^2.0.0"
     pkg-dir "^3.0.0"
 
+find-up@3.0.0, find-up@^3.0.0:
+  version "3.0.0"
+  resolved "https://registry.yarnpkg.com/find-up/-/find-up-3.0.0.tgz#49169f1d7993430646da61ecc5ae355c21c97b73"
+  integrity sha512-1yD6RmLI1XBfxugvORwlck6f75tYL+iR0jqwsOrOxMZyGYqUuDhJ0l4AXdO1iX/FTs9cBAMEk1gWSEx1kSbylg==
+  dependencies:
+    locate-path "^3.0.0"
+
 find-up@^1.0.0:
   version "1.1.2"
   resolved "https://registry.yarnpkg.com/find-up/-/find-up-1.1.2.tgz#6b2e9822b1a2ce0a60ab64d610eccad53cb24d0f"
@@ -2622,13 +2818,6 @@ find-up@^2.1.0:
   dependencies:
     locate-path "^2.0.0"
 
-find-up@^3.0.0:
-  version "3.0.0"
-  resolved "https://registry.yarnpkg.com/find-up/-/find-up-3.0.0.tgz#49169f1d7993430646da61ecc5ae355c21c97b73"
-  integrity sha512-1yD6RmLI1XBfxugvORwlck6f75tYL+iR0jqwsOrOxMZyGYqUuDhJ0l4AXdO1iX/FTs9cBAMEk1gWSEx1kSbylg==
-  dependencies:
-    locate-path "^3.0.0"
-
 find-versions@^3.0.0:
   version "3.1.0"
   resolved "https://registry.yarnpkg.com/find-versions/-/find-versions-3.1.0.tgz#10161f29cf3eb4350dec10a29bdde75bff0df32d"
@@ -2647,6 +2836,20 @@ forever-agent@~0.6.1:
   resolved "https://registry.yarnpkg.com/forever-agent/-/forever-agent-0.6.1.tgz#fbc71f0c41adeb37f96c577ad1ed42d8fdacca91"
   integrity sha1-+8cfDEGt6zf5bFd60e1C2P2sypE=
 
+fork-ts-checker-webpack-plugin@1.5.0:
+  version "1.5.0"
+  resolved "https://registry.yarnpkg.com/fork-ts-checker-webpack-plugin/-/fork-ts-checker-webpack-plugin-1.5.0.tgz#ce1d77190b44d81a761b10b6284a373795e41f0c"
+  integrity sha512-zEhg7Hz+KhZlBhILYpXy+Beu96gwvkROWJiTXOCyOOMMrdBIRPvsBpBqgTI4jfJGrJXcqGwJR8zsBGDmzY0jsA==
+  dependencies:
+    babel-code-frame "^6.22.0"
+    chalk "^2.4.1"
+    chokidar "^2.0.4"
+    micromatch "^3.1.10"
+    minimatch "^3.0.4"
+    semver "^5.6.0"
+    tapable "^1.0.0"
+    worker-rpc "^0.1.0"
+
 form-data@~2.3.2:
   version "2.3.3"
   resolved "https://registry.yarnpkg.com/form-data/-/form-data-2.3.3.tgz#dcce52c05f644f298c6a7ab936bd724ceffbf3a6"
@@ -2702,11 +2905,35 @@ fs-extra@^5.0.0:
     jsonfile "^4.0.0"
     universalify "^0.1.0"
 
+fs-extra@^8.1.0:
+  version "8.1.0"
+  resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-8.1.0.tgz#49d43c45a88cd9677668cb7be1b46efdb8d2e1c0"
+  integrity sha512-yhlQgA6mnOJUKOsRUFsgJdQCvkKhcz8tlZG5HBQfReYZy46OwLcY+Zia0mtdHsOo9y/hP+CxMN0TU9QxoOtG4g==
+  dependencies:
+    graceful-fs "^4.2.0"
+    jsonfile "^4.0.0"
+    universalify "^0.1.0"
+
+fs-minipass@^1.2.5:
+  version "1.2.6"
+  resolved "https://registry.yarnpkg.com/fs-minipass/-/fs-minipass-1.2.6.tgz#2c5cc30ded81282bfe8a0d7c7c1853ddeb102c07"
+  integrity sha512-crhvyXcMejjv3Z5d2Fa9sf5xLYVCF5O1c71QxbVnbLsmYMBEvDAftewesN/HhY03YRoA7zOMxjNGrF5svGaaeQ==
+  dependencies:
+    minipass "^2.2.1"
+
 fs.realpath@^1.0.0:
   version "1.0.0"
   resolved "https://registry.yarnpkg.com/fs.realpath/-/fs.realpath-1.0.0.tgz#1504ad2523158caa40db4a2787cb01411994ea4f"
   integrity sha1-FQStJSMVjKpA20onh8sBQRmU6k8=
 
+fsevents@^1.2.7:
+  version "1.2.9"
+  resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-1.2.9.tgz#3f5ed66583ccd6f400b5a00db6f7e861363e388f"
+  integrity sha512-oeyj2H3EjjonWcFjD5NvZNE9Rqe4UW+nQBU2HNeKw0koVLEFIhtyETyAakeAM3de7Z/SW5kcA+fZUait9EApnw==
+  dependencies:
+    nan "^2.12.1"
+    node-pre-gyp "^0.12.0"
+
 fsevents@^2.0.6:
   version "2.0.7"
   resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-2.0.7.tgz#382c9b443c6cbac4c57187cdda23aa3bf1ccfc2a"
@@ -2717,7 +2944,21 @@ function-bind@^1.1.1:
   resolved "https://registry.yarnpkg.com/function-bind/-/function-bind-1.1.1.tgz#a56899d3ea3c9bab874bb9773b7c5ede92f4895d"
   integrity sha512-yIovAzMX49sF8Yl58fSCWJ5svSLuaibPxXQJFLmBObTuCr0Mf1KiPopGM9NiFjiYBCbfaa2Fh6breQ6ANVTI0A==
 
-gaze@^1.1.2:
+gauge@~2.7.3:
+  version "2.7.4"
+  resolved "https://registry.yarnpkg.com/gauge/-/gauge-2.7.4.tgz#2c03405c7538c39d7eb37b317022e325fb018bf7"
+  integrity sha1-LANAXHU4w51+s3sxcCLjJfsBi/c=
+  dependencies:
+    aproba "^1.0.3"
+    console-control-strings "^1.0.0"
+    has-unicode "^2.0.0"
+    object-assign "^4.1.0"
+    signal-exit "^3.0.0"
+    string-width "^1.0.1"
+    strip-ansi "^3.0.1"
+    wide-align "^1.1.0"
+
+gaze@^1.1.3:
   version "1.1.3"
   resolved "https://registry.yarnpkg.com/gaze/-/gaze-1.1.3.tgz#c441733e13b927ac8c0ff0b4c3b033f28812924a"
   integrity sha512-BRdNm8hbWzFzWHERTrejLqwHDfS4GibPoq5wjTPIoJHoBtKGPg3xAFfxmM+9ztbXelxcf2hwQcaz1PtmFeue8g==
@@ -2832,32 +3073,28 @@ glob@^7.1.2:
     once "^1.3.0"
     path-is-absolute "^1.0.0"
 
-global-modules@1.0.0, global-modules@^1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/global-modules/-/global-modules-1.0.0.tgz#6d770f0eb523ac78164d72b5e71a8877265cc3ea"
-  integrity sha512-sKzpEkf11GpOFuw0Zzjzmt4B4UZwjOcG757PPvrfhxcLFbq0wpsgpOqxpxtxFiCG4DtG93M6XRVbF2oGdev7bg==
+global-modules@2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/global-modules/-/global-modules-2.0.0.tgz#997605ad2345f27f51539bea26574421215c7780"
+  integrity sha512-NGbfmJBp9x8IxyJSd1P+otYK8vonoJactOogrVfFRIAEY1ukil8RSKDz2Yo7wh1oihl51l/r6W4epkeKJHqL8A==
   dependencies:
-    global-prefix "^1.0.1"
-    is-windows "^1.0.1"
-    resolve-dir "^1.0.0"
+    global-prefix "^3.0.0"
 
-global-prefix@^1.0.1:
-  version "1.0.2"
-  resolved "https://registry.yarnpkg.com/global-prefix/-/global-prefix-1.0.2.tgz#dbf743c6c14992593c655568cb66ed32c0122ebe"
-  integrity sha1-2/dDxsFJklk8ZVVoy2btMsASLr4=
+global-prefix@^3.0.0:
+  version "3.0.0"
+  resolved "https://registry.yarnpkg.com/global-prefix/-/global-prefix-3.0.0.tgz#fc85f73064df69f50421f47f883fe5b913ba9b97"
+  integrity sha512-awConJSVCHVGND6x3tmMaKcQvwXLhjdkmomy2W+Goaui8YPgYgXJZewhg3fWC+DlfqqQuWg8AwqjGTD2nAPVWg==
   dependencies:
-    expand-tilde "^2.0.2"
-    homedir-polyfill "^1.0.1"
-    ini "^1.3.4"
-    is-windows "^1.0.1"
-    which "^1.2.14"
+    ini "^1.3.5"
+    kind-of "^6.0.2"
+    which "^1.3.1"
 
 globals@^11.1.0:
   version "11.12.0"
   resolved "https://registry.yarnpkg.com/globals/-/globals-11.12.0.tgz#ab8795338868a0babd8525758018c2a7eb95c42e"
   integrity sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==
 
-globby@^8.0.1:
+globby@8.0.2, globby@^8.0.1:
   version "8.0.2"
   resolved "https://registry.yarnpkg.com/globby/-/globby-8.0.2.tgz#5697619ccd95c5275dbb2d6faa42087c1a941d8d"
   integrity sha512-yTzMmKygLp8RUpG1Ymu2VXPSJQZjNAZPD4ywgYEaG7e4tBJeUQBO8OpXrf1RCNcEs5alsoJYPAMiIHP0cmeC7w==
@@ -2934,6 +3171,11 @@ graceful-fs@^4.1.10, graceful-fs@^4.1.2:
   resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.0.tgz#8d8fdc73977cb04104721cb53666c1ca64cd328b"
   integrity sha512-jpSvDPV4Cq/bgtpndIWbI5hmYxhQGHPC4d4cqBPb4DLniCfhJokdXhwhaDuLBGLQdvvRum/UiX6ECVIPvDXqdg==
 
+graceful-fs@^4.1.11, graceful-fs@^4.2.0:
+  version "4.2.2"
+  resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.2.tgz#6f0952605d0140c1cfdb138ed005775b92d67b02"
+  integrity sha512-IItsdsea19BoLC7ELy13q1iJFNmd7ofZH5+X/pJr90/nRoPEX0DJo1dHDbgtYWOhJhcCgMDTOw84RZ72q6lB+Q==
+
 graceful-fs@^4.1.6:
   version "4.1.11"
   resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.1.11.tgz#0e8bdfe4d1ddb8854d64e04ea7c00e2a026e5658"
@@ -2955,12 +3197,13 @@ gray-matter@^2.1.0:
     js-yaml "^3.8.1"
     toml "^2.3.2"
 
-gzip-size@3.0.0:
-  version "3.0.0"
-  resolved "https://registry.yarnpkg.com/gzip-size/-/gzip-size-3.0.0.tgz#546188e9bdc337f673772f81660464b389dce520"
-  integrity sha1-VGGI6b3DN/Zzdy+BZgRks4nc5SA=
+gzip-size@5.1.1:
+  version "5.1.1"
+  resolved "https://registry.yarnpkg.com/gzip-size/-/gzip-size-5.1.1.tgz#cb9bee692f87c0612b232840a873904e4c135274"
+  integrity sha512-FNHi6mmoHvs1mxZAds4PpdCS6QG8B4C1krxJsMutgxl5t3+GlRTzzI3NEkifXx2pVsOvJdOGSmIgDhQ55FwdPA==
   dependencies:
     duplexer "^0.1.1"
+    pify "^4.0.1"
 
 har-schema@^2.0.0:
   version "2.0.0"
@@ -3004,6 +3247,11 @@ has-to-string-tag-x@^1.2.0:
   dependencies:
     has-symbol-support-x "^1.4.1"
 
+has-unicode@^2.0.0:
+  version "2.0.1"
+  resolved "https://registry.yarnpkg.com/has-unicode/-/has-unicode-2.0.1.tgz#e0e6fe6a28cf51138855e086d1691e771de2a8b9"
+  integrity sha1-4Ob+aijPUROIVeCG0Wkedx3iqLk=
+
 has-value@^0.3.1:
   version "0.3.1"
   resolved "https://registry.yarnpkg.com/has-value/-/has-value-0.3.1.tgz#7b1f58bada62ca827ec0a2078025654845995e1f"
@@ -3047,17 +3295,10 @@ hex-color-regex@^1.1.0:
   resolved "https://registry.yarnpkg.com/hex-color-regex/-/hex-color-regex-1.1.0.tgz#4c06fccb4602fe2602b3c93df82d7e7dbf1a8a8e"
   integrity sha512-l9sfDFsuqtOqKDsQdqrMRk0U85RZc0RtOR9yPI7mRVOa4FsR/BVnZ0shmQRM96Ji99kYZP/7hn1cedc1+ApsTQ==
 
-highlight.js@^9.12.0:
-  version "9.12.0"
-  resolved "https://registry.yarnpkg.com/highlight.js/-/highlight.js-9.12.0.tgz#e6d9dbe57cbefe60751f02af336195870c90c01e"
-  integrity sha1-5tnb5Xy+/mB1HwKvM2GVhwyQwB4=
-
-homedir-polyfill@^1.0.1:
-  version "1.0.3"
-  resolved "https://registry.yarnpkg.com/homedir-polyfill/-/homedir-polyfill-1.0.3.tgz#743298cef4e5af3e194161fbadcc2151d3a058e8"
-  integrity sha512-eSmmWE5bZTK2Nou4g0AI3zZ9rswp7GRKoKXS1BLUkvPviOqs4YTN1djQIqrXy9k5gEtdLPy86JjRwsNM9tnDcA==
-  dependencies:
-    parse-passwd "^1.0.0"
+highlight.js@^9.15.10, highlight.js@^9.15.8:
+  version "9.15.10"
+  resolved "https://registry.yarnpkg.com/highlight.js/-/highlight.js-9.15.10.tgz#7b18ed75c90348c045eef9ed08ca1319a2219ad2"
+  integrity sha512-RoV7OkQm0T3os3Dd2VHLNMoaoDVx77Wygln3n9l5YV172XonWG6rgQD3XnF/BuFFZw9A0TJgmMSO8FEWQgvcXw==
 
 hosted-git-info@^2.1.4:
   version "2.7.1"
@@ -3148,7 +3389,7 @@ husky@^1.3.1:
     run-node "^1.0.0"
     slash "^2.0.0"
 
-iconv-lite@0.4.24, iconv-lite@^0.4.17:
+iconv-lite@0.4.24, iconv-lite@^0.4.24, iconv-lite@^0.4.4:
   version "0.4.24"
   resolved "https://registry.yarnpkg.com/iconv-lite/-/iconv-lite-0.4.24.tgz#2022b4b25fbddc21d2f524974a474aafe733908b"
   integrity sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==
@@ -3160,6 +3401,13 @@ ieee754@^1.1.4:
   resolved "https://registry.yarnpkg.com/ieee754/-/ieee754-1.1.13.tgz#ec168558e95aa181fd87d37f55c32bbcb6708b84"
   integrity sha512-4vf7I2LYV/HaWerSo3XmlMkp5eZ83i+/CDluXi/IGTs/O1sejBNhTtnxzmRZfvOUqj7lZjqHkeTvpgSFDlWZTg==
 
+ignore-walk@^3.0.1:
+  version "3.0.1"
+  resolved "https://registry.yarnpkg.com/ignore-walk/-/ignore-walk-3.0.1.tgz#a83e62e7d272ac0e3b551aaa82831a19b69f82f8"
+  integrity sha512-DTVlMx3IYPe0/JJcYP7Gxg7ttZZu3IInhuEhbchuqneY9wWe5Ojy2mXLBaQFUQmo0AW2r3qG7m1mg86js+gnlQ==
+  dependencies:
+    minimatch "^3.0.4"
+
 ignore@^3.3.5, ignore@^3.3.7:
   version "3.3.10"
   resolved "https://registry.yarnpkg.com/ignore/-/ignore-3.3.10.tgz#0a97fb876986e8081c631160f8f9f389157f0043"
@@ -3212,6 +3460,11 @@ imagemin@^6.0.0:
     pify "^4.0.1"
     replace-ext "^1.0.0"
 
+immer@1.10.0:
+  version "1.10.0"
+  resolved "https://registry.yarnpkg.com/immer/-/immer-1.10.0.tgz#bad67605ba9c810275d91e1c2a47d4582e98286d"
+  integrity sha512-O3sR1/opvCDGLEVcvrGTMtLac8GJ5IwZC4puPrLuRj3l7ICKvkmA0vGuU9OW8mV9WIBRnaxp5GJh9IEAaNOoYg==
+
 import-fresh@^2.0.0:
   version "2.0.0"
   resolved "https://registry.yarnpkg.com/import-fresh/-/import-fresh-2.0.0.tgz#d81355c15612d386c61f9ddd3922d4304822a546"
@@ -3260,29 +3513,28 @@ inherits@2.0.3:
   resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.3.tgz#633c2c83e3da42a502f52466022480f4208261de"
   integrity sha1-Yzwsg+PaQqUC9SRmAiSA9CCCYd4=
 
-ini@^1.3.4:
+ini@^1.3.4, ini@^1.3.5, ini@~1.3.0:
   version "1.3.5"
   resolved "https://registry.yarnpkg.com/ini/-/ini-1.3.5.tgz#eee25f56db1c9ec6085e0c22778083f596abf927"
   integrity sha512-RZY5huIKCMRWDUqZlEi72f/lmXKMvuszcMBduliQ3nnWbx9X/ZBQO7DijMEYS9EhHBb2qacRUMtC7svLwe0lcw==
 
-inquirer@3.3.0:
-  version "3.3.0"
-  resolved "https://registry.yarnpkg.com/inquirer/-/inquirer-3.3.0.tgz#9dd2f2ad765dcab1ff0443b491442a20ba227dc9"
-  integrity sha512-h+xtnyk4EwKvFWHrUYsWErEVR+igKtLdchu+o0Z1RL7VU/jVMFbYir2bp6bAj8efFNxWqHX0dIss6fJQ+/+qeQ==
+inquirer@6.5.0:
+  version "6.5.0"
+  resolved "https://registry.yarnpkg.com/inquirer/-/inquirer-6.5.0.tgz#2303317efc9a4ea7ec2e2df6f86569b734accf42"
+  integrity sha512-scfHejeG/lVZSpvCXpsB4j/wQNPM5JC8kiElOI0OUTwmc1RTpXr4H32/HOlQHcZiYl2z2VElwuCVDRG8vFmbnA==
   dependencies:
-    ansi-escapes "^3.0.0"
-    chalk "^2.0.0"
+    ansi-escapes "^3.2.0"
+    chalk "^2.4.2"
     cli-cursor "^2.1.0"
     cli-width "^2.0.0"
-    external-editor "^2.0.4"
+    external-editor "^3.0.3"
     figures "^2.0.0"
-    lodash "^4.3.0"
+    lodash "^4.17.12"
     mute-stream "0.0.7"
     run-async "^2.2.0"
-    rx-lite "^4.0.8"
-    rx-lite-aggregates "^4.0.8"
+    rxjs "^6.4.0"
     string-width "^2.1.0"
-    strip-ansi "^4.0.0"
+    strip-ansi "^5.1.0"
     through "^2.3.6"
 
 interpret@^1.0.0:
@@ -3305,6 +3557,11 @@ invariant@^2.2.2:
   dependencies:
     loose-envify "^1.0.0"
 
+ip-regex@^2.1.0:
+  version "2.1.0"
+  resolved "https://registry.yarnpkg.com/ip-regex/-/ip-regex-2.1.0.tgz#fa78bf5d2e6913c911ce9f819ee5146bb6d844e9"
+  integrity sha1-+ni/XS5pE8kRzp+BnuUUa7bYROk=
+
 ipaddr.js@1.9.0:
   version "1.9.0"
   resolved "https://registry.yarnpkg.com/ipaddr.js/-/ipaddr.js-1.9.0.tgz#37df74e430a0e47550fe54a2defe30d8acd95f65"
@@ -3339,6 +3596,13 @@ is-arrayish@^0.3.1:
   resolved "https://registry.yarnpkg.com/is-arrayish/-/is-arrayish-0.3.2.tgz#4574a2ae56f7ab206896fb431eaeed066fdf8f03"
   integrity sha512-eVRqCvVlZbuw3GrM63ovNSNAeA1K16kaR/LRY/92w0zxQ5/1YzwblUX652i4Xs9RwAGjW9d9y6X88t8OaAJfWQ==
 
+is-binary-path@^1.0.0:
+  version "1.0.1"
+  resolved "https://registry.yarnpkg.com/is-binary-path/-/is-binary-path-1.0.1.tgz#75f16642b480f187a711c814161fd3a4a7655898"
+  integrity sha1-dfFmQrSA8YenEcgUFh/TpKdlWJg=
+  dependencies:
+    binary-extensions "^1.0.0"
+
 is-binary-path@^2.1.0:
   version "2.1.0"
   resolved "https://registry.yarnpkg.com/is-binary-path/-/is-binary-path-2.1.0.tgz#ea1f7f3b80f064236e83470f86c09c254fb45b09"
@@ -3441,6 +3705,13 @@ is-finite@^1.0.0:
   dependencies:
     number-is-nan "^1.0.0"
 
+is-fullwidth-code-point@^1.0.0:
+  version "1.0.0"
+  resolved "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz#ef9e31386f031a7f0d643af82fde50c457ef00cb"
+  integrity sha1-754xOG8DGn8NZDr4L95QxFfvAMs=
+  dependencies:
+    number-is-nan "^1.0.0"
+
 is-fullwidth-code-point@^2.0.0:
   version "2.0.0"
   resolved "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-2.0.0.tgz#a3b30a5c4f199183167aaab93beefae3ddfb654f"
@@ -3550,10 +3821,10 @@ is-retry-allowed@^1.0.0, is-retry-allowed@^1.1.0:
   resolved "https://registry.yarnpkg.com/is-retry-allowed/-/is-retry-allowed-1.1.0.tgz#11a060568b67339444033d0125a61a20d564fb34"
   integrity sha1-EaBgVotnM5REAz0BJaYaINVk+zQ=
 
-is-root@1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/is-root/-/is-root-1.0.0.tgz#07b6c233bc394cd9d02ba15c966bd6660d6342d5"
-  integrity sha1-B7bCM7w5TNnQK6FclmvWZg1jQtU=
+is-root@2.1.0:
+  version "2.1.0"
+  resolved "https://registry.yarnpkg.com/is-root/-/is-root-2.1.0.tgz#809e18129cf1129644302a4f8544035d51984a9c"
+  integrity sha512-AGOriNp96vNBd3HtU+RzFEc75FfR5ymiYv8E553I71SCeXBiMsVDUtdio1OEFvrPyLIQ9tVR5RxXIFe5PUFjMg==
 
 is-stream@^1.0.0, is-stream@^1.1.0:
   version "1.1.0"
@@ -3579,12 +3850,17 @@ is-typedarray@~1.0.0:
   resolved "https://registry.yarnpkg.com/is-typedarray/-/is-typedarray-1.0.0.tgz#e479c80858df0c1b11ddda6940f96011fcda4a9a"
   integrity sha1-5HnICFjfDBsR3dppQPlgEfzaSpo=
 
+is-url@^1.2.2:
+  version "1.2.4"
+  resolved "https://registry.yarnpkg.com/is-url/-/is-url-1.2.4.tgz#04a4df46d28c4cff3d73d01ff06abeb318a1aa52"
+  integrity sha512-ITvGim8FhRiYe4IQ5uHSkj7pVaPDrCTkNd3yq3cV7iZAcJdHTUMPMEHcqSOy9xZ9qFenQCvi+2wjH9a1nXqHww==
+
 is-utf8@^0.2.0:
   version "0.2.1"
   resolved "https://registry.yarnpkg.com/is-utf8/-/is-utf8-0.2.1.tgz#4b0da1442104d1b336340e80797e865cf39f7d72"
   integrity sha1-Sw2hRCEE0bM2NA6AeX6GXPOffXI=
 
-is-windows@^1.0.1, is-windows@^1.0.2:
+is-windows@^1.0.2:
   version "1.0.2"
   resolved "https://registry.yarnpkg.com/is-windows/-/is-windows-1.0.2.tgz#d1850eb9791ecd18e6182ce12a30f396634bb19d"
   integrity sha512-eXK1UInq2bPmjyX6e3VHIzMLobc4J94i4AWn+Hpq3OU5KkrRC96OAcR3PRJ/pGu6m8TRnBHP9dkXQVsT/COVIA==
@@ -3594,12 +3870,14 @@ is-wsl@^1.1.0:
   resolved "https://registry.yarnpkg.com/is-wsl/-/is-wsl-1.1.0.tgz#1f16e4aa22b04d1336b66188a66af3c600c3a66d"
   integrity sha1-HxbkqiKwTRM2tmGIpmrzxgDDpm0=
 
-is2@0.0.9:
-  version "0.0.9"
-  resolved "https://registry.yarnpkg.com/is2/-/is2-0.0.9.tgz#119556d1d1651a41ba105af803267c80b299f629"
-  integrity sha1-EZVW0dFlGkG6EFr4AyZ8gLKZ9ik=
+is2@2.0.1:
+  version "2.0.1"
+  resolved "https://registry.yarnpkg.com/is2/-/is2-2.0.1.tgz#8ac355644840921ce435d94f05d3a94634d3481a"
+  integrity sha512-+WaJvnaA7aJySz2q/8sLjMb2Mw14KTplHmSwcSpZ/fWJPkUmqw3YTzSWbPJ7OAwRvdYTWF2Wg+yYJ1AdP5Z8CA==
   dependencies:
-    deep-is "0.1.2"
+    deep-is "^0.1.3"
+    ip-regex "^2.1.0"
+    is-url "^1.2.2"
 
 isarray@1.0.0, isarray@~1.0.0:
   version "1.0.0"
@@ -3721,6 +3999,13 @@ json3@^3.3.2:
   resolved "https://registry.yarnpkg.com/json3/-/json3-3.3.3.tgz#7fc10e375fc5ae42c4705a5cc0aa6f62be305b81"
   integrity sha512-c7/8mbUsKigAbLkD5B010BK4D9LZm7A1pNItkEwiUZRpIN66exu/e7YQWysGun+TRKaJp8MhemM+VkfWv42aCA==
 
+json5@^1.0.1:
+  version "1.0.1"
+  resolved "https://registry.yarnpkg.com/json5/-/json5-1.0.1.tgz#779fb0018604fa854eacbf6252180d83543e3dbe"
+  integrity sha512-aKS4WQjPenRxiQsC93MNfjx+nbF4PAdYzmd/1JIj8HYzqfbu86beTuNgXDzPknWk0n0uARlyewZo4s++ES36Ow==
+  dependencies:
+    minimist "^1.2.0"
+
 json5@^2.1.0:
   version "2.1.0"
   resolved "https://registry.yarnpkg.com/json5/-/json5-2.1.0.tgz#e7a0c62c48285c628d20a10b85c89bb807c32850"
@@ -3814,6 +4099,15 @@ load-json-file@^1.0.0:
     pinkie-promise "^2.0.0"
     strip-bom "^2.0.0"
 
+loader-utils@1.2.3:
+  version "1.2.3"
+  resolved "https://registry.yarnpkg.com/loader-utils/-/loader-utils-1.2.3.tgz#1ff5dc6911c9f0a062531a4c04b609406108c2c7"
+  integrity sha512-fkpz8ejdnEMG3s37wGL07iSBDg99O9D5yflE9RGNH3hRdx9SOwYfnGYdZOUIZitN8E+E2vkq3MUMYMvPYl5ZZA==
+  dependencies:
+    big.js "^5.2.2"
+    emojis-list "^2.0.0"
+    json5 "^1.0.1"
+
 locate-path@^2.0.0:
   version "2.0.0"
   resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-2.0.0.tgz#2b568b265eec944c6d9c0de9c3dbbbca0354cd8e"
@@ -3840,6 +4134,11 @@ lodash.bind@^4.1.4:
   resolved "https://registry.yarnpkg.com/lodash.bind/-/lodash.bind-4.2.1.tgz#7ae3017e939622ac31b7d7d7dcb1b34db1690d35"
   integrity sha1-euMBfpOWIqwxt9fX3LGzTbFpDTU=
 
+lodash.chunk@^4.2.0:
+  version "4.2.0"
+  resolved "https://registry.yarnpkg.com/lodash.chunk/-/lodash.chunk-4.2.0.tgz#66e5ce1f76ed27b4303d8c6512e8d1216e8106bc"
+  integrity sha1-ZuXOH3btJ7QwPYxlEujRIW6BBrw=
+
 lodash.defaults@^4.0.1:
   version "4.2.0"
   resolved "https://registry.yarnpkg.com/lodash.defaults/-/lodash.defaults-4.2.0.tgz#d09178716ffea4dde9e5fb7b37f6f0802274580c"
@@ -3875,6 +4174,11 @@ lodash.merge@^4.4.0:
   resolved "https://registry.yarnpkg.com/lodash.merge/-/lodash.merge-4.6.1.tgz#adc25d9cb99b9391c59624f379fbba60d7111d54"
   integrity sha512-AOYza4+Hf5z1/0Hztxpm2/xiPZgi/cjMqdnKTUWTBSKchJlxXXuUSxCCl8rJlf4g6yww/j6mA8nC8Hw/EZWxKQ==
 
+lodash.padstart@^4.6.1:
+  version "4.6.1"
+  resolved "https://registry.yarnpkg.com/lodash.padstart/-/lodash.padstart-4.6.1.tgz#d2e3eebff0d9d39ad50f5cbd1b52a7bce6bb611b"
+  integrity sha1-0uPuv/DZ05rVD1y9G1KnvOa7YRs=
+
 lodash.pick@^4.2.1:
   version "4.4.0"
   resolved "https://registry.yarnpkg.com/lodash.pick/-/lodash.pick-4.4.0.tgz#52f05610fff9ded422611441ed1fc123a03001b3"
@@ -3895,16 +4199,26 @@ lodash.some@^4.4.0:
   resolved "https://registry.yarnpkg.com/lodash.some/-/lodash.some-4.6.0.tgz#1bb9f314ef6b8baded13b549169b2a945eb68e4d"
   integrity sha1-G7nzFO9ri63tE7VJFpsqlF62jk0=
 
+lodash.sortby@^4.7.0:
+  version "4.7.0"
+  resolved "https://registry.yarnpkg.com/lodash.sortby/-/lodash.sortby-4.7.0.tgz#edd14c824e2cc9c1e0b0a1b42bb5210516a42438"
+  integrity sha1-7dFMgk4sycHgsKG0K7UhBRakJDg=
+
 lodash.uniq@^4.5.0:
   version "4.5.0"
   resolved "https://registry.yarnpkg.com/lodash.uniq/-/lodash.uniq-4.5.0.tgz#d0225373aeb652adc1bc82e4945339a842754773"
   integrity sha1-0CJTc662Uq3BvILklFM5qEJ1R3M=
 
-lodash@^4.17.11, lodash@^4.3.0, lodash@~4.17.10:
+lodash@^4.17.11, lodash@~4.17.10:
   version "4.17.11"
   resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.11.tgz#b39ea6229ef607ecd89e2c8df12536891cac9b8d"
   integrity sha512-cQKh8igo5QUhZ7lg38DYWAxMvjSAKG0A8wGSVimP07SIUEK2UO+arSRKbRZWtelMtN5V0Hkwh5ryOto/SshYIg==
 
+lodash@^4.17.12, lodash@^4.17.13, lodash@^4.17.14:
+  version "4.17.15"
+  resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.15.tgz#b447f6670a0455bbfeedd11392eff330ea097548"
+  integrity sha512-8xOcRHvCjnocdS5cpwXQXVzmmh5e5+saE2QGoeQmbKmRS6J3VQppPOIt0MnmE+4xlZoumy0GPG0D0MVIQbNA1A==
+
 logalot@^2.0.0:
   version "2.1.0"
   resolved "https://registry.yarnpkg.com/logalot/-/logalot-2.1.0.tgz#5f8e8c90d304edf12530951a5554abb8c5e3f552"
@@ -4062,7 +4376,12 @@ methods@~1.1.2:
   resolved "https://registry.yarnpkg.com/methods/-/methods-1.1.2.tgz#5529a4d67654134edcc5266656835b0f851afcee"
   integrity sha1-VSmk1nZUE07cxSZmVoNbD4Ua/O4=
 
-micromatch@^3.1.10:
+microevent.ts@~0.1.1:
+  version "0.1.1"
+  resolved "https://registry.yarnpkg.com/microevent.ts/-/microevent.ts-0.1.1.tgz#70b09b83f43df5172d0205a63025bce0f7357fa0"
+  integrity sha512-jo1OfR4TaEwd5HOrt5+tAZ9mqT4jmpNAusXtyfNzqVm9uiSYFZlKM1wYL4oU7azZW/PxQW53wM0S6OR1JHNa2g==
+
+micromatch@^3.1.10, micromatch@^3.1.4:
   version "3.1.10"
   resolved "https://registry.yarnpkg.com/micromatch/-/micromatch-3.1.10.tgz#70859bc95c9840952f359a068a3fc49f9ecfac23"
   integrity sha512-MWikgl9n9M3w+bpsY3He8L+w9eF9338xRl8IAO5viDizwSzziFEyUzo2xrrloB64ADbTf8uA8vRqqttDTOmccg==
@@ -4108,14 +4427,7 @@ mimic-response@^1.0.0:
   resolved "https://registry.yarnpkg.com/mimic-response/-/mimic-response-1.0.1.tgz#4923538878eef42063cb8a3e3b0798781487ab1b"
   integrity sha512-j5EctnkH7amfV/q5Hgmoal1g2QHFJRraOtmx0JpIqkxhBhI/lJSl1nMpQ45hVarwNETOoWEimndZ4QK0RHxuxQ==
 
-minimatch@3.0.3:
-  version "3.0.3"
-  resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-3.0.3.tgz#2a4e4090b96b2db06a9d7df01055a62a77c9b774"
-  integrity sha1-Kk5AkLlrLbBqnX3wEFWmKnfJt3Q=
-  dependencies:
-    brace-expansion "^1.0.0"
-
-minimatch@^3.0.4, minimatch@~3.0.2:
+minimatch@3.0.4, minimatch@^3.0.4, minimatch@~3.0.2:
   version "3.0.4"
   resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-3.0.4.tgz#5166e286457f03306064be5497e8dbb0c3d32083"
   integrity sha512-yJHVQEhyqPLUTgt9B83PXu6W3rx4MvvHvSUvToogpwoGDOUQ+yDrR0HRot+yOCdCO7u4hX3pWft6kWBBcqh0UA==
@@ -4132,6 +4444,21 @@ minimist@^1.1.3, minimist@^1.2.0:
   resolved "https://registry.yarnpkg.com/minimist/-/minimist-1.2.0.tgz#a35008b20f41383eec1fb914f4cd5df79a264284"
   integrity sha1-o1AIsg9BOD7sH7kU9M1d95omQoQ=
 
+minipass@^2.2.1, minipass@^2.3.5:
+  version "2.5.0"
+  resolved "https://registry.yarnpkg.com/minipass/-/minipass-2.5.0.tgz#dddb1d001976978158a05badfcbef4a771612857"
+  integrity sha512-9FwMVYhn6ERvMR8XFdOavRz4QK/VJV8elU1x50vYexf9lslDcWe/f4HBRxCPd185ekRSjU6CfYyJCECa/CQy7Q==
+  dependencies:
+    safe-buffer "^5.1.2"
+    yallist "^3.0.0"
+
+minizlib@^1.2.1:
+  version "1.2.1"
+  resolved "https://registry.yarnpkg.com/minizlib/-/minizlib-1.2.1.tgz#dd27ea6136243c7c880684e8672bb3a45fd9b614"
+  integrity sha512-7+4oTUOWKg7AuL3vloEWekXY2/D20cevzsrNT2kGWm+39J9hGTCBv8VI5Pm5lXZ/o3/mdR4f8rflAPhnQb8mPA==
+  dependencies:
+    minipass "^2.2.1"
+
 mixin-deep@^1.1.3, mixin-deep@^1.2.0:
   version "1.3.2"
   resolved "https://registry.yarnpkg.com/mixin-deep/-/mixin-deep-1.3.2.tgz#1120b43dc359a785dce65b55b82e257ccf479566"
@@ -4140,7 +4467,7 @@ mixin-deep@^1.1.3, mixin-deep@^1.2.0:
     for-in "^1.0.2"
     is-extendable "^1.0.1"
 
-mkdirp@0.5.x, mkdirp@^0.5.1, mkdirp@~0.5.1:
+mkdirp@0.5.x, mkdirp@^0.5.0, mkdirp@^0.5.1, mkdirp@~0.5.1:
   version "0.5.1"
   resolved "https://registry.yarnpkg.com/mkdirp/-/mkdirp-0.5.1.tgz#30057438eac6cf7f8c4767f38648d6697d75c903"
   integrity sha1-MAV0OOrGz3+MR2fzhkjWaX11yQM=
@@ -4182,6 +4509,11 @@ mute-stream@0.0.7:
   resolved "https://registry.yarnpkg.com/mute-stream/-/mute-stream-0.0.7.tgz#3075ce93bc21b8fab43e1bc4da7e8115ed1e7bab"
   integrity sha1-MHXOk7whuPq0PhvE2n6BFe0ee6s=
 
+nan@^2.12.1:
+  version "2.14.0"
+  resolved "https://registry.yarnpkg.com/nan/-/nan-2.14.0.tgz#7818f722027b2459a86f0295d434d1fc2336c52c"
+  integrity sha512-INOFj37C7k3AfaNTtX8RhsTw7qRy7eLET14cROi9+5HAVbbHuIWUHEauBv5qT4Av2tWasiTY1Jw6puUNqRJXQg==
+
 nanomatch@^1.2.9:
   version "1.2.13"
   resolved "https://registry.yarnpkg.com/nanomatch/-/nanomatch-1.2.13.tgz#b87a8aa4fc0de8fe6be88895b38983ff265bd119"
@@ -4199,6 +4531,15 @@ nanomatch@^1.2.9:
     snapdragon "^0.8.1"
     to-regex "^3.0.1"
 
+needle@^2.2.1:
+  version "2.4.0"
+  resolved "https://registry.yarnpkg.com/needle/-/needle-2.4.0.tgz#6833e74975c444642590e15a750288c5f939b57c"
+  integrity sha512-4Hnwzr3mi5L97hMYeNl8wRW/Onhy4nUKR/lVemJ8gJedxxUyBLm9kkrDColJvoSfwi0jCNhD+xCdOtiGDQiRZg==
+  dependencies:
+    debug "^3.2.6"
+    iconv-lite "^0.4.4"
+    sax "^1.2.4"
+
 negotiator@0.6.2:
   version "0.6.2"
   resolved "https://registry.yarnpkg.com/negotiator/-/negotiator-0.6.2.tgz#feacf7ccf525a77ae9634436a64883ffeca346fb"
@@ -4219,6 +4560,22 @@ node-modules-regexp@^1.0.0:
   resolved "https://registry.yarnpkg.com/node-modules-regexp/-/node-modules-regexp-1.0.0.tgz#8d9dbe28964a4ac5712e9131642107c71e90ec40"
   integrity sha1-jZ2+KJZKSsVxLpExZCEHxx6Q7EA=
 
+node-pre-gyp@^0.12.0:
+  version "0.12.0"
+  resolved "https://registry.yarnpkg.com/node-pre-gyp/-/node-pre-gyp-0.12.0.tgz#39ba4bb1439da030295f899e3b520b7785766149"
+  integrity sha512-4KghwV8vH5k+g2ylT+sLTjy5wmUOb9vPhnM8NHvRf9dHmnW/CndrFXy2aRPaPST6dugXSdHXfeaHQm77PIz/1A==
+  dependencies:
+    detect-libc "^1.0.2"
+    mkdirp "^0.5.1"
+    needle "^2.2.1"
+    nopt "^4.0.1"
+    npm-packlist "^1.1.6"
+    npmlog "^4.0.2"
+    rc "^1.2.7"
+    rimraf "^2.6.1"
+    semver "^5.3.0"
+    tar "^4"
+
 node-releases@^1.1.23:
   version "1.1.24"
   resolved "https://registry.yarnpkg.com/node-releases/-/node-releases-1.1.24.tgz#2fb494562705c01bfb81a7af9f8584c4d56311b4"
@@ -4226,6 +4583,21 @@ node-releases@^1.1.23:
   dependencies:
     semver "^5.3.0"
 
+node-releases@^1.1.25:
+  version "1.1.29"
+  resolved "https://registry.yarnpkg.com/node-releases/-/node-releases-1.1.29.tgz#86a57c6587a30ecd6726449e5d293466b0a0bb86"
+  integrity sha512-R5bDhzh6I+tpi/9i2hrrvGJ3yKPYzlVOORDkXhnZuwi5D3q1I5w4vYy24PJXTcLk9Q0kws9TO77T75bcK8/ysQ==
+  dependencies:
+    semver "^5.3.0"
+
+nopt@^4.0.1:
+  version "4.0.1"
+  resolved "https://registry.yarnpkg.com/nopt/-/nopt-4.0.1.tgz#d0d4685afd5415193c8c7505602d0d17cd64474d"
+  integrity sha1-0NRoWv1UFRk8jHUFYC0NF81kR00=
+  dependencies:
+    abbrev "1"
+    osenv "^0.1.4"
+
 normalize-package-data@^2.3.2, normalize-package-data@^2.3.4:
   version "2.5.0"
   resolved "https://registry.yarnpkg.com/normalize-package-data/-/normalize-package-data-2.5.0.tgz#e66db1838b200c1dfc233225d12cb36520e234a8"
@@ -4236,6 +4608,13 @@ normalize-package-data@^2.3.2, normalize-package-data@^2.3.4:
     semver "2 || 3 || 4 || 5"
     validate-npm-package-license "^3.0.1"
 
+normalize-path@^2.1.1:
+  version "2.1.1"
+  resolved "https://registry.yarnpkg.com/normalize-path/-/normalize-path-2.1.1.tgz#1ab28b556e198363a8c1a6f7e6fa20137fe6aed9"
+  integrity sha1-GrKLVW4Zg2Oowab35vogE3/mrtk=
+  dependencies:
+    remove-trailing-separator "^1.0.1"
+
 normalize-path@^3.0.0:
   version "3.0.0"
   resolved "https://registry.yarnpkg.com/normalize-path/-/normalize-path-3.0.0.tgz#0dcd69ff23a1c9b11fd0978316644a0388216a65"
@@ -4260,6 +4639,11 @@ normalize-url@^3.0.0:
   resolved "https://registry.yarnpkg.com/normalize-url/-/normalize-url-3.3.0.tgz#b2e1c4dc4f7c6d57743df733a4f5978d18650559"
   integrity sha512-U+JJi7duF1o+u2pynbp2zXDW2/PADgC30f0GsHZtRh+HOcXHnw137TrNlyxxRvWW5fjKd3bcLHPxofWuCjaeZg==
 
+npm-bundled@^1.0.1:
+  version "1.0.6"
+  resolved "https://registry.yarnpkg.com/npm-bundled/-/npm-bundled-1.0.6.tgz#e7ba9aadcef962bb61248f91721cd932b3fe6bdd"
+  integrity sha512-8/JCaftHwbd//k6y2rEWp6k1wxVfpFzB6t1p825+cUb7Ym2XQfhwIC5KwhrvzZRJu+LtDE585zVaS32+CGtf0g==
+
 npm-conf@^1.1.0:
   version "1.1.3"
   resolved "https://registry.yarnpkg.com/npm-conf/-/npm-conf-1.1.3.tgz#256cc47bd0e218c259c4e9550bf413bc2192aff9"
@@ -4268,6 +4652,14 @@ npm-conf@^1.1.0:
     config-chain "^1.1.11"
     pify "^3.0.0"
 
+npm-packlist@^1.1.6:
+  version "1.4.4"
+  resolved "https://registry.yarnpkg.com/npm-packlist/-/npm-packlist-1.4.4.tgz#866224233850ac534b63d1a6e76050092b5d2f44"
+  integrity sha512-zTLo8UcVYtDU3gdeaFu2Xu0n0EvelfHDGuqtNIn5RO7yQj4H1TqNdBc/yZjxnWA0PVB8D3Woyp0i5B43JwQ6Vw==
+  dependencies:
+    ignore-walk "^3.0.1"
+    npm-bundled "^1.0.1"
+
 npm-run-path@^2.0.0:
   version "2.0.2"
   resolved "https://registry.yarnpkg.com/npm-run-path/-/npm-run-path-2.0.2.tgz#35a9232dfa35d7067b4cb2ddf2357b1871536c5f"
@@ -4275,6 +4667,16 @@ npm-run-path@^2.0.0:
   dependencies:
     path-key "^2.0.0"
 
+npmlog@^4.0.2:
+  version "4.1.2"
+  resolved "https://registry.yarnpkg.com/npmlog/-/npmlog-4.1.2.tgz#08a7f2a8bf734604779a9efa4ad5cc717abb954b"
+  integrity sha512-2uUqazuKlTaSI/dC8AzicUck7+IrEaOnN/e0jd3Xtt1KcGpwx30v50mL7oPyr/h9bL3E4aZccVwpwP+5W9Vjkg==
+  dependencies:
+    are-we-there-yet "~1.1.2"
+    console-control-strings "~1.1.0"
+    gauge "~2.7.3"
+    set-blocking "~2.0.0"
+
 nth-check@^1.0.2, nth-check@~1.0.1:
   version "1.0.2"
   resolved "https://registry.yarnpkg.com/nth-check/-/nth-check-1.0.2.tgz#b2bd295c37e3dd58a3bf0700376663ba4d9cf05c"
@@ -4311,7 +4713,7 @@ object-copy@^0.1.0:
     define-property "^0.2.5"
     kind-of "^3.0.3"
 
-object-keys@^1.0.12:
+object-keys@^1.0.11, object-keys@^1.0.12:
   version "1.1.1"
   resolved "https://registry.yarnpkg.com/object-keys/-/object-keys-1.1.1.tgz#1c47f272df277f3b1daf061677d9c82e2322c60e"
   integrity sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==
@@ -4323,6 +4725,16 @@ object-visit@^1.0.0:
   dependencies:
     isobject "^3.0.0"
 
+object.assign@^4.1.0:
+  version "4.1.0"
+  resolved "https://registry.yarnpkg.com/object.assign/-/object.assign-4.1.0.tgz#968bf1100d7956bb3ca086f006f846b3bc4008da"
+  integrity sha512-exHJeq6kBKj58mqGyTQ9DFvrZC/eR6OwxzoM9YRoGBqrXYonaFyGiFMuc9VZrXf7DarreEwMpurG3dd+CNyW5w==
+  dependencies:
+    define-properties "^1.1.2"
+    function-bind "^1.1.1"
+    has-symbols "^1.0.0"
+    object-keys "^1.0.11"
+
 object.getownpropertydescriptors@^2.0.3:
   version "2.0.3"
   resolved "https://registry.yarnpkg.com/object.getownpropertydescriptors/-/object.getownpropertydescriptors-2.0.3.tgz#8758c846f5b407adab0f236e0986f14b051caa16"
@@ -4369,10 +4781,10 @@ onetime@^2.0.0:
   dependencies:
     mimic-fn "^1.0.0"
 
-opn@5.2.0:
-  version "5.2.0"
-  resolved "https://registry.yarnpkg.com/opn/-/opn-5.2.0.tgz#71fdf934d6827d676cecbea1531f95d354641225"
-  integrity sha512-Jd/GpzPyHF4P2/aNOVmS3lfMSWV9J7cOhCG1s08XCEAsPkB7lp6ddiU0J7XzyQRDUh8BqJ7PchfINjR8jyofRQ==
+open@^6.3.0:
+  version "6.4.0"
+  resolved "https://registry.yarnpkg.com/open/-/open-6.4.0.tgz#5c13e96d0dc894686164f18965ecfe889ecfc8a9"
+  integrity sha512-IFenVPgF70fSm1keSd2iDBIDIBZkroLeuffXq+wKTzTJlBpesFWojV9lb8mzOfaAzM1sr7HQHuO0vtV0zYekGg==
   dependencies:
     is-wsl "^1.1.0"
 
@@ -4385,7 +4797,7 @@ optipng-bin@^5.0.0:
     bin-wrapper "^4.0.0"
     logalot "^2.0.0"
 
-original@>=0.0.5:
+original@^1.0.0:
   version "1.0.2"
   resolved "https://registry.yarnpkg.com/original/-/original-1.0.2.tgz#e442a61cffe1c5fd20a65f3261c26663b303f25f"
   integrity sha512-hyBVl6iqqUOJ8FqRe+l/gS8H+kKYjrEndd5Pm1MfBtsEKA038HkkdbAl/72EAXGyonD/PFsvmVG+EvcIpliMBg==
@@ -4399,11 +4811,24 @@ os-filter-obj@^2.0.0:
   dependencies:
     arch "^2.1.0"
 
-os-tmpdir@~1.0.2:
+os-homedir@^1.0.0:
+  version "1.0.2"
+  resolved "https://registry.yarnpkg.com/os-homedir/-/os-homedir-1.0.2.tgz#ffbc4988336e0e833de0c168c7ef152121aa7fb3"
+  integrity sha1-/7xJiDNuDoM94MFox+8VISGqf7M=
+
+os-tmpdir@^1.0.0, os-tmpdir@~1.0.2:
   version "1.0.2"
   resolved "https://registry.yarnpkg.com/os-tmpdir/-/os-tmpdir-1.0.2.tgz#bbe67406c79aa85c5cfec766fe5734555dfa1274"
   integrity sha1-u+Z0BseaqFxc/sdm/lc0VV36EnQ=
 
+osenv@^0.1.4:
+  version "0.1.5"
+  resolved "https://registry.yarnpkg.com/osenv/-/osenv-0.1.5.tgz#85cdfafaeb28e8677f416e287592b5f3f49ea410"
+  integrity sha512-0CWcCECdMVc2Rw3U5w9ZjqX6ga6ubk1xDVKxtBQPK7wis/0F2r9T6k4ydGYhecl7YUBxBVxhL5oisPsNxAPe2g==
+  dependencies:
+    os-homedir "^1.0.0"
+    os-tmpdir "^1.0.0"
+
 p-cancelable@^0.3.0:
   version "0.3.0"
   resolved "https://registry.yarnpkg.com/p-cancelable/-/p-cancelable-0.3.0.tgz#b9e123800bcebb7ac13a479be195b507b98d30fa"
@@ -4522,11 +4947,6 @@ parse-json@^4.0.0:
     error-ex "^1.3.1"
     json-parse-better-errors "^1.0.1"
 
-parse-passwd@^1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/parse-passwd/-/parse-passwd-1.0.0.tgz#6d5b934a456993b23d37f40a382d6f1666a8e5c6"
-  integrity sha1-bVuTSkVpk7I9N/QKOC1vFmao5cY=
-
 parseurl@~1.3.3:
   version "1.3.3"
   resolved "https://registry.yarnpkg.com/parseurl/-/parseurl-1.3.3.tgz#9da19e7bee8d12dff0513ed5b76957793bc2e8d4"
@@ -4654,6 +5074,13 @@ pkg-dir@^3.0.0:
   dependencies:
     find-up "^3.0.0"
 
+pkg-up@2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/pkg-up/-/pkg-up-2.0.0.tgz#c819ac728059a461cab1c3889a2be3c49a004d7f"
+  integrity sha1-yBmscoBZpGHKscOImivjxJoATX8=
+  dependencies:
+    find-up "^2.1.0"
+
 please-upgrade-node@^3.1.1:
   version "3.1.1"
   resolved "https://registry.yarnpkg.com/please-upgrade-node/-/please-upgrade-node-3.1.1.tgz#ed320051dfcc5024fae696712c8288993595e8ac"
@@ -4661,10 +5088,10 @@ please-upgrade-node@^3.1.1:
   dependencies:
     semver-compare "^1.0.0"
 
-portfinder@^1.0.17:
-  version "1.0.20"
-  resolved "https://registry.yarnpkg.com/portfinder/-/portfinder-1.0.20.tgz#bea68632e54b2e13ab7b0c4775e9b41bf270e44a"
-  integrity sha512-Yxe4mTyDzTd59PZJY4ojZR8F+E5e97iq2ZOHPz3HDgSvYC5siNad2tLooQ5y5QHyQhc3xVqvyk/eNA3wuoa7Sw==
+portfinder@^1.0.21:
+  version "1.0.23"
+  resolved "https://registry.yarnpkg.com/portfinder/-/portfinder-1.0.23.tgz#894db4bcc5daf02b6614517ce89cd21a38226b82"
+  integrity sha512-B729mL/uLklxtxuiJKfQ84WPxNw5a7Yhx3geQZdcA4GjNjZSTSSMMWyoennMVnTWSmAR0lMdzWYN0JLnHrg1KQ==
   dependencies:
     async "^1.5.2"
     debug "^2.2.0"
@@ -4946,7 +5373,7 @@ postcss-value-parser@^3.0.0, postcss-value-parser@^3.3.1:
   resolved "https://registry.yarnpkg.com/postcss-value-parser/-/postcss-value-parser-3.3.1.tgz#9ff822547e2893213cf1c30efa51ac5fd1ba8281"
   integrity sha512-pISE66AbVkp4fDQ7VHBwRNXzAAKJjw4Vw7nWI/+Q3vuly7SNfgYXvm6i5IgFylHGK5sP/xHAbB7N49OS4gWNyQ==
 
-postcss@^7.0.0, postcss@^7.0.1, postcss@^7.0.16, postcss@^7.0.5:
+postcss@^7.0.0, postcss@^7.0.1, postcss@^7.0.16, postcss@^7.0.17, postcss@^7.0.5:
   version "7.0.17"
   resolved "https://registry.yarnpkg.com/postcss/-/postcss-7.0.17.tgz#4da1bdff5322d4a0acaab4d87f3e782436bad31f"
   integrity sha512-546ZowA+KZ3OasvQZHsbuEpysvwTZNGJv9EfyCQdsIDltPSWHAeTQ5fQy/Npi2ZDtLI3zs7Ps/p6wThErhm9fQ==
@@ -4982,10 +5409,10 @@ pretty-quick@^1.10.0:
     mri "^1.1.0"
     multimatch "^3.0.0"
 
-prismjs@^1.15.0:
-  version "1.16.0"
-  resolved "https://registry.yarnpkg.com/prismjs/-/prismjs-1.16.0.tgz#406eb2c8aacb0f5f0f1167930cb83835d10a4308"
-  integrity sha512-OA4MKxjFZHSvZcisLGe14THYsug/nF6O1f0pAJc0KN0wTyAcLqmsbE+lTGKSpyh+9pEW57+k6pg2AfYR+coyHA==
+prismjs@^1.16.0:
+  version "1.17.1"
+  resolved "https://registry.yarnpkg.com/prismjs/-/prismjs-1.17.1.tgz#e669fcbd4cdd873c35102881c33b14d0d68519be"
+  integrity sha512-PrEDJAFdUGbOP6xK/UsfkC5ghJsPJviKgnQOoxaDbBjwc8op68Quupwt1DeAFoG8GImPhiKXAvvsH7wDSLsu1Q==
   optionalDependencies:
     clipboard "^2.0.0"
 
@@ -5054,11 +5481,6 @@ punycode@^2.1.0:
   resolved "https://registry.yarnpkg.com/punycode/-/punycode-2.1.1.tgz#b58b010ac40c22c5657616c8d2c2c02c7bf479ec"
   integrity sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==
 
-q@0.9.7:
-  version "0.9.7"
-  resolved "https://registry.yarnpkg.com/q/-/q-0.9.7.tgz#4de2e6cb3b29088c9e4cbc03bf9d42fb96ce2f75"
-  integrity sha1-TeLmyzspCIyeTLwDv51C+5bOL3U=
-
 q@^1.1.2:
   version "1.5.1"
   resolved "https://registry.yarnpkg.com/q/-/q-1.5.1.tgz#7e32f75b41381291d04611f1bf14109ac00651d7"
@@ -5120,59 +5542,75 @@ raw-body@~1.1.0:
     bytes "1"
     string_decoder "0.10"
 
-react-dev-utils@^5.0.2:
-  version "5.0.3"
-  resolved "https://registry.yarnpkg.com/react-dev-utils/-/react-dev-utils-5.0.3.tgz#92f97668f03deb09d7fa11ea288832a8c756e35e"
-  integrity sha512-Mvs6ofsc2xTjeZIrMaIfbXfsPVrbdVy/cVqq6SAacnqfMlcBpDuivhWZ1ODGeJ8HgmyWTLH971PYjj/EPCDVAw==
+rc@^1.2.7:
+  version "1.2.8"
+  resolved "https://registry.yarnpkg.com/rc/-/rc-1.2.8.tgz#cd924bf5200a075b83c188cd6b9e211b7fc0d3ed"
+  integrity sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw==
   dependencies:
-    address "1.0.3"
-    babel-code-frame "6.26.0"
-    chalk "1.1.3"
-    cross-spawn "5.1.0"
+    deep-extend "^0.6.0"
+    ini "~1.3.0"
+    minimist "^1.2.0"
+    strip-json-comments "~2.0.1"
+
+react-dev-utils@^9.0.1:
+  version "9.0.3"
+  resolved "https://registry.yarnpkg.com/react-dev-utils/-/react-dev-utils-9.0.3.tgz#7607455587abb84599451460eb37cef0b684131a"
+  integrity sha512-OyInhcwsvycQ3Zr2pQN+HV4gtRXrky5mJXIy4HnqrWa+mI624xfYfqGuC9dYbxp4Qq3YZzP8GSGQjv0AgNU15w==
+  dependencies:
+    "@babel/code-frame" "7.5.5"
+    address "1.1.0"
+    browserslist "4.6.6"
+    chalk "2.4.2"
+    cross-spawn "6.0.5"
     detect-port-alt "1.1.6"
     escape-string-regexp "1.0.5"
-    filesize "3.5.11"
-    global-modules "1.0.0"
-    gzip-size "3.0.0"
-    inquirer "3.3.0"
-    is-root "1.0.0"
-    opn "5.2.0"
-    react-error-overlay "^4.0.1"
-    recursive-readdir "2.2.1"
+    filesize "3.6.1"
+    find-up "3.0.0"
+    fork-ts-checker-webpack-plugin "1.5.0"
+    global-modules "2.0.0"
+    globby "8.0.2"
+    gzip-size "5.1.1"
+    immer "1.10.0"
+    inquirer "6.5.0"
+    is-root "2.1.0"
+    loader-utils "1.2.3"
+    open "^6.3.0"
+    pkg-up "2.0.0"
+    react-error-overlay "^6.0.1"
+    recursive-readdir "2.2.2"
     shell-quote "1.6.1"
-    sockjs-client "1.1.5"
-    strip-ansi "3.0.1"
+    sockjs-client "1.3.0"
+    strip-ansi "5.2.0"
     text-table "0.2.0"
 
-react-dom@^16.5.0:
-  version "16.8.6"
-  resolved "https://registry.yarnpkg.com/react-dom/-/react-dom-16.8.6.tgz#71d6303f631e8b0097f56165ef608f051ff6e10f"
-  integrity sha512-1nL7PIq9LTL3fthPqwkvr2zY7phIPjYrT0jp4HjyEQrEROnw4dG41VVwi/wfoCneoleqrNX7iAD+pXebJZwrwA==
+react-dom@^16.8.4:
+  version "16.9.0"
+  resolved "https://registry.yarnpkg.com/react-dom/-/react-dom-16.9.0.tgz#5e65527a5e26f22ae3701131bcccaee9fb0d3962"
+  integrity sha512-YFT2rxO9hM70ewk9jq0y6sQk8cL02xm4+IzYBz75CQGlClQQ1Bxq0nhHF6OtSbit+AIahujJgb/CPRibFkMNJQ==
   dependencies:
     loose-envify "^1.1.0"
     object-assign "^4.1.1"
     prop-types "^15.6.2"
-    scheduler "^0.13.6"
+    scheduler "^0.15.0"
 
-react-error-overlay@^4.0.1:
-  version "4.0.1"
-  resolved "https://registry.yarnpkg.com/react-error-overlay/-/react-error-overlay-4.0.1.tgz#417addb0814a90f3a7082eacba7cee588d00da89"
-  integrity sha512-xXUbDAZkU08aAkjtUvldqbvI04ogv+a1XdHxvYuHPYKIVk/42BIOD0zSKTHAWV4+gDy3yGm283z2072rA2gdtw==
+react-error-overlay@^6.0.1:
+  version "6.0.1"
+  resolved "https://registry.yarnpkg.com/react-error-overlay/-/react-error-overlay-6.0.1.tgz#b8d3cf9bb991c02883225c48044cb3ee20413e0f"
+  integrity sha512-V9yoTr6MeZXPPd4nV/05eCBvGH9cGzc52FN8fs0O0TVQ3HYYf1n7EgZVtHbldRq5xU9zEzoXIITjYNIfxDDdUw==
 
 react-is@^16.8.1:
   version "16.8.6"
   resolved "https://registry.yarnpkg.com/react-is/-/react-is-16.8.6.tgz#5bbc1e2d29141c9fbdfed456343fe2bc430a6a16"
   integrity sha512-aUk3bHfZ2bRSVFFbbeVS4i+lNPZr3/WM5jT2J5omUVV1zzcs1nAaf3l51ctA5FFvCRbhrH0bdAsRRQddFJZPtA==
 
-react@^16.5.0:
-  version "16.8.6"
-  resolved "https://registry.yarnpkg.com/react/-/react-16.8.6.tgz#ad6c3a9614fd3a4e9ef51117f54d888da01f2bbe"
-  integrity sha512-pC0uMkhLaHm11ZSJULfOBqV4tIZkx87ZLvbbQYunNixAAvjnC+snJCg0XQXn9VIsttVsbZP/H/ewzgsd5fxKXw==
+react@^16.8.4:
+  version "16.9.0"
+  resolved "https://registry.yarnpkg.com/react/-/react-16.9.0.tgz#40ba2f9af13bc1a38d75dbf2f4359a5185c4f7aa"
+  integrity sha512-+7LQnFBwkiw+BobzOF6N//BdoNw0ouwmSJTEm9cglOOmsg/TMiFHZLe2sEoN5M7LgJTj9oHH0gxklfnQe66S1w==
   dependencies:
     loose-envify "^1.1.0"
     object-assign "^4.1.1"
     prop-types "^15.6.2"
-    scheduler "^0.13.6"
 
 read-pkg-up@^1.0.1:
   version "1.0.1"
@@ -5200,7 +5638,7 @@ read-pkg@^4.0.1:
     parse-json "^4.0.0"
     pify "^3.0.0"
 
-readable-stream@^2.0.0, readable-stream@^2.2.2, readable-stream@^2.3.0, readable-stream@^2.3.5:
+readable-stream@^2.0.0, readable-stream@^2.0.2, readable-stream@^2.0.6, readable-stream@^2.2.2, readable-stream@^2.3.0, readable-stream@^2.3.5:
   version "2.3.6"
   resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-2.3.6.tgz#b11c27d88b8ff1fbe070643cf94b0c79ae1b0aaf"
   integrity sha512-tQtKA9WIAhBF3+VLAseyMqZeBjW0AHJoxOtYqSUZNJxauErmLbVm2FW1y+J/YA9dUrAC39ITejlZWhVIwawkKw==
@@ -5222,10 +5660,19 @@ readable-stream@^3.1.1:
     string_decoder "^1.1.1"
     util-deprecate "^1.0.1"
 
-readdirp@^3.0.2:
-  version "3.0.2"
-  resolved "https://registry.yarnpkg.com/readdirp/-/readdirp-3.0.2.tgz#cba63348e9e42fc1bd334b1d2ef895b6a043cbd6"
-  integrity sha512-LbyJYv48eywrhOlScq16H/VkCiGKGPC2TpOdZCJ7QXnYEjn3NN/Oblh8QEU3vqfSRBB7OGvh5x45NKiVeNujIQ==
+readdirp@^2.2.1:
+  version "2.2.1"
+  resolved "https://registry.yarnpkg.com/readdirp/-/readdirp-2.2.1.tgz#0e87622a3325aa33e892285caf8b4e846529a525"
+  integrity sha512-1JU/8q+VgFZyxwrJ+SVIOsh+KywWGpds3NTqikiKpDMZWScmAYyKIgqkO+ARvNWJfXeXR1zxz7aHF4u4CyH6vQ==
+  dependencies:
+    graceful-fs "^4.1.11"
+    micromatch "^3.1.10"
+    readable-stream "^2.0.2"
+
+readdirp@^3.1.1:
+  version "3.1.2"
+  resolved "https://registry.yarnpkg.com/readdirp/-/readdirp-3.1.2.tgz#fa85d2d14d4289920e4671dead96431add2ee78a"
+  integrity sha512-8rhl0xs2cxfVsqzreYCvs8EwBfn/DhVdqtoLmw19uI3SC5avYX9teCurlErfpPXGmYtMHReGaP2RsLnFvz/lnw==
   dependencies:
     picomatch "^2.0.4"
 
@@ -5236,12 +5683,12 @@ rechoir@^0.6.2:
   dependencies:
     resolve "^1.1.6"
 
-recursive-readdir@2.2.1:
-  version "2.2.1"
-  resolved "https://registry.yarnpkg.com/recursive-readdir/-/recursive-readdir-2.2.1.tgz#90ef231d0778c5ce093c9a48d74e5c5422d13a99"
-  integrity sha1-kO8jHQd4xc4JPJpI105cVCLROpk=
+recursive-readdir@2.2.2:
+  version "2.2.2"
+  resolved "https://registry.yarnpkg.com/recursive-readdir/-/recursive-readdir-2.2.2.tgz#9946fb3274e1628de6e36b2f6714953b4845094f"
+  integrity sha512-nRCcW9Sj7NuZwa2XvH9co8NPeXUBhZP7CRKJtU+cS6PW9FpCIFoI5ib0NT1ZrbNuPoRy0ylyCaUL8Gih4LSyFg==
   dependencies:
-    minimatch "3.0.3"
+    minimatch "3.0.4"
 
 redent@^1.0.0:
   version "1.0.0"
@@ -5320,6 +5767,19 @@ remarkable@^1.7.1:
     argparse "~0.1.15"
     autolinker "~0.15.0"
 
+remarkable@^2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/remarkable/-/remarkable-2.0.0.tgz#795f965bede8300362ce51a716edc322d9e7a4ca"
+  integrity sha512-3gvKFAgL4xmmVRKAMNm6UzDo/rO2gPVkZrWagp6AXEA4JvCcMcRx9aapYbb7AJAmLLvi/u06+EhzqoS7ha9qOg==
+  dependencies:
+    argparse "^1.0.10"
+    autolinker "^3.11.0"
+
+remove-trailing-separator@^1.0.1:
+  version "1.1.0"
+  resolved "https://registry.yarnpkg.com/remove-trailing-separator/-/remove-trailing-separator-1.1.0.tgz#c24bce2a283adad5bc3f58e0d48249b92379d8ef"
+  integrity sha1-wkvOKig62tW8P1jg1IJJuSN52O8=
+
 repeat-element@^1.1.2:
   version "1.1.3"
   resolved "https://registry.yarnpkg.com/repeat-element/-/repeat-element-1.1.3.tgz#782e0d825c0c5a3bb39731f84efee6b742e6b1ce"
@@ -5342,7 +5802,7 @@ replace-ext@^1.0.0:
   resolved "https://registry.yarnpkg.com/replace-ext/-/replace-ext-1.0.0.tgz#de63128373fcbf7c3ccfa4de5a480c45a67958eb"
   integrity sha1-3mMSg3P8v3w8z6TeWkgMRaZ5WOs=
 
-request@^2.53.0, request@^2.87.0:
+request@^2.53.0, request@^2.88.0:
   version "2.88.0"
   resolved "https://registry.yarnpkg.com/request/-/request-2.88.0.tgz#9c2fca4f7d35b592efe57c7f0a55e81052124fef"
   integrity sha512-NAqBSrijGLZdM0WZNsInLJpkJokL72XYjUpnB0iwsRgxh7dB6COrHnTBNwN0E+lHDAJzu7kLAkDeY08z2/A0hg==
@@ -5373,14 +5833,6 @@ requires-port@^1.0.0:
   resolved "https://registry.yarnpkg.com/requires-port/-/requires-port-1.0.0.tgz#925d2601d39ac485e091cf0da5c6e694dc3dcaff"
   integrity sha1-kl0mAdOaxIXgkc8NpcbmlNw9yv8=
 
-resolve-dir@^1.0.0:
-  version "1.0.1"
-  resolved "https://registry.yarnpkg.com/resolve-dir/-/resolve-dir-1.0.1.tgz#79a40644c362be82f26effe739c9bb5382046f43"
-  integrity sha1-eaQGRMNivoLybv/nOcm7U4IEb0M=
-  dependencies:
-    expand-tilde "^2.0.0"
-    global-modules "^1.0.0"
-
 resolve-from@^3.0.0:
   version "3.0.0"
   resolved "https://registry.yarnpkg.com/resolve-from/-/resolve-from-3.0.0.tgz#b22c7af7d9d6881bc8b6e653335eebcb0a188748"
@@ -5435,6 +5887,13 @@ rimraf@^2.5.4:
   dependencies:
     glob "^7.1.3"
 
+rimraf@^2.6.1:
+  version "2.7.1"
+  resolved "https://registry.yarnpkg.com/rimraf/-/rimraf-2.7.1.tgz#35797f13a7fdadc566142c29d4f07ccad483e3ec"
+  integrity sha512-uWjbaKIK3T1OSVptzX7Nl6PvQ3qAGtKEtVRjRuazjfL3Bx5eI409VZSqgND+4UNnmzLVdPj9FqFJNPqBZFve4w==
+  dependencies:
+    glob "^7.1.3"
+
 run-async@^2.2.0:
   version "2.3.0"
   resolved "https://registry.yarnpkg.com/run-async/-/run-async-2.3.0.tgz#0371ab4ae0bdd720d4166d7dfda64ff7a445a6c0"
@@ -5447,17 +5906,12 @@ run-node@^1.0.0:
   resolved "https://registry.yarnpkg.com/run-node/-/run-node-1.0.0.tgz#46b50b946a2aa2d4947ae1d886e9856fd9cabe5e"
   integrity sha512-kc120TBlQ3mih1LSzdAJXo4xn/GWS2ec0l3S+syHDXP9uRr0JAT8Qd3mdMuyjqCzeZktgP3try92cEgf9Nks8A==
 
-rx-lite-aggregates@^4.0.8:
-  version "4.0.8"
-  resolved "https://registry.yarnpkg.com/rx-lite-aggregates/-/rx-lite-aggregates-4.0.8.tgz#753b87a89a11c95467c4ac1626c4efc4e05c67be"
-  integrity sha1-dTuHqJoRyVRnxKwWJsTvxOBcZ74=
+rxjs@^6.4.0:
+  version "6.5.3"
+  resolved "https://registry.yarnpkg.com/rxjs/-/rxjs-6.5.3.tgz#510e26317f4db91a7eb1de77d9dd9ba0a4899a3a"
+  integrity sha512-wuYsAYYFdWTAnAaPoKGNhfpWwKZbJW+HgAJ+mImp+Epl7BG8oNWBCTyRM8gba9k4lk8BgWdoYm21Mo/RYhhbgA==
   dependencies:
-    rx-lite "*"
-
-rx-lite@*, rx-lite@^4.0.8:
-  version "4.0.8"
-  resolved "https://registry.yarnpkg.com/rx-lite/-/rx-lite-4.0.8.tgz#0b1e11af8bc44836f04a6407e92da42467b79444"
-  integrity sha1-Cx4Rr4vESDbwSmQH6S2kJGe3lEQ=
+    tslib "^1.9.0"
 
 safe-buffer@5.1.2, safe-buffer@>=5.1.0, safe-buffer@^5.0.1, safe-buffer@^5.1.1, safe-buffer@^5.1.2, safe-buffer@~5.1.0, safe-buffer@~5.1.1:
   version "5.1.2"
@@ -5481,15 +5935,15 @@ safe-regex@^1.1.0:
   resolved "https://registry.yarnpkg.com/safer-buffer/-/safer-buffer-2.1.2.tgz#44fa161b0187b9549dd84bb91802f9bd8385cd6a"
   integrity sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==
 
-sax@~1.2.4:
+sax@^1.2.4, sax@~1.2.4:
   version "1.2.4"
   resolved "https://registry.yarnpkg.com/sax/-/sax-1.2.4.tgz#2816234e2378bddc4e5354fab5caa895df7100d9"
   integrity sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw==
 
-scheduler@^0.13.6:
-  version "0.13.6"
-  resolved "https://registry.yarnpkg.com/scheduler/-/scheduler-0.13.6.tgz#466a4ec332467b31a91b9bf74e5347072e4cd889"
-  integrity sha512-IWnObHt413ucAYKsD9J1QShUKkbKLQQHdxRyw73sw4FN26iWr3DY/H34xGPe4nmL1DwXyWmSWmMrA9TfQbE/XQ==
+scheduler@^0.15.0:
+  version "0.15.0"
+  resolved "https://registry.yarnpkg.com/scheduler/-/scheduler-0.15.0.tgz#6bfcf80ff850b280fed4aeecc6513bc0b4f17f8e"
+  integrity sha512-xAefmSfN6jqAa7Kuq7LIJY0bwAPG3xlCj0HMEBQk1lxYiDKZscY2xJ5U/61ZTrYbmNQbXa+gc7czPkVo11tnCg==
   dependencies:
     loose-envify "^1.1.0"
     object-assign "^4.1.1"
@@ -5562,6 +6016,11 @@ serve-static@1.14.1:
     parseurl "~1.3.3"
     send "0.17.1"
 
+set-blocking@~2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/set-blocking/-/set-blocking-2.0.0.tgz#045f9782d011ae9a6803ddd382b24392b3d890f7"
+  integrity sha1-BF+XgtARrppoA93TgrJDkrPYkPc=
+
 set-getter@^0.1.0:
   version "0.1.0"
   resolved "https://registry.yarnpkg.com/set-getter/-/set-getter-0.1.0.tgz#d769c182c9d5a51f409145f2fba82e5e86e80376"
@@ -5627,13 +6086,15 @@ simple-swizzle@^0.2.2:
   dependencies:
     is-arrayish "^0.3.1"
 
-sitemap@^1.13.0:
-  version "1.13.0"
-  resolved "https://registry.yarnpkg.com/sitemap/-/sitemap-1.13.0.tgz#569cbe2180202926a62a266cd3de09c9ceb43f83"
-  integrity sha1-Vpy+IYAgKSamKiZs094Jyc60P4M=
+sitemap@^3.2.2:
+  version "3.2.2"
+  resolved "https://registry.yarnpkg.com/sitemap/-/sitemap-3.2.2.tgz#3f77c358fa97b555c879e457098e39910095c62b"
+  integrity sha512-TModL/WU4m2q/mQcrDgNANn0P4LwprM9MMvG4hu5zP4c6IIKs2YLTu6nXXnNr8ODW/WFtxKggiJ1EGn2W0GNmg==
   dependencies:
-    underscore "^1.7.0"
-    url-join "^1.1.0"
+    lodash.chunk "^4.2.0"
+    lodash.padstart "^4.6.1"
+    whatwg-url "^7.0.0"
+    xmlbuilder "^13.0.0"
 
 slash@^1.0.0:
   version "1.0.0"
@@ -5675,17 +6136,17 @@ snapdragon@^0.8.1:
     source-map-resolve "^0.5.0"
     use "^3.1.0"
 
-sockjs-client@1.1.5:
-  version "1.1.5"
-  resolved "https://registry.yarnpkg.com/sockjs-client/-/sockjs-client-1.1.5.tgz#1bb7c0f7222c40f42adf14f4442cbd1269771a83"
-  integrity sha1-G7fA9yIsQPQq3xT0RCy9Eml3GoM=
+sockjs-client@1.3.0:
+  version "1.3.0"
+  resolved "https://registry.yarnpkg.com/sockjs-client/-/sockjs-client-1.3.0.tgz#12fc9d6cb663da5739d3dc5fb6e8687da95cb177"
+  integrity sha512-R9jxEzhnnrdxLCNln0xg5uGHqMnkhPSTzUZH2eXcR03S/On9Yvoq2wyUZILRUhZCNVu2PmwWVoyuiPz8th8zbg==
   dependencies:
-    debug "^2.6.6"
-    eventsource "0.1.6"
-    faye-websocket "~0.11.0"
-    inherits "^2.0.1"
+    debug "^3.2.5"
+    eventsource "^1.0.7"
+    faye-websocket "~0.11.1"
+    inherits "^2.0.3"
     json3 "^3.3.2"
-    url-parse "^1.1.8"
+    url-parse "^1.4.3"
 
 sort-keys-length@^1.0.0:
   version "1.0.1"
@@ -5832,7 +6293,16 @@ string-template@~0.2.1:
   resolved "https://registry.yarnpkg.com/string-template/-/string-template-0.2.1.tgz#42932e598a352d01fc22ec3367d9d84eec6c9add"
   integrity sha1-QpMuWYo1LQH8IuwzZ9nYTuxsmt0=
 
-string-width@^2.1.0:
+string-width@^1.0.1:
+  version "1.0.2"
+  resolved "https://registry.yarnpkg.com/string-width/-/string-width-1.0.2.tgz#118bdf5b8cdc51a2a7e70d211e07e2b0b9b107d3"
+  integrity sha1-EYvfW4zcUaKn5w0hHgfisLmxB9M=
+  dependencies:
+    code-point-at "^1.0.0"
+    is-fullwidth-code-point "^1.0.0"
+    strip-ansi "^3.0.0"
+
+"string-width@^1.0.2 || 2", string-width@^2.1.0:
   version "2.1.1"
   resolved "https://registry.yarnpkg.com/string-width/-/string-width-2.1.1.tgz#ab93f27a8dc13d28cac815c462143a6d9012ae9e"
   integrity sha512-nOqH59deCq9SRHlxq1Aw85Jnt4w6KvLKqWVik6oA9ZklXLNIOlqg4F2yrT1MVaTjAqvVwdfeZ7w7aCvJD7ugkw==
@@ -5859,7 +6329,14 @@ string_decoder@~1.1.1:
   dependencies:
     safe-buffer "~5.1.0"
 
-strip-ansi@3.0.1, strip-ansi@^3.0.0:
+strip-ansi@5.2.0, strip-ansi@^5.1.0:
+  version "5.2.0"
+  resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-5.2.0.tgz#8c9a536feb6afc962bdfa5b104a5091c1ad9c0ae"
+  integrity sha512-DuRs1gKbBqsMKIZlrffwlug8MHkcnpjs5VPmL1PAh+mA30U0DTotfDZ0d2UUsXpPmPmMMJ6W773MaA3J+lbiWA==
+  dependencies:
+    ansi-regex "^4.1.0"
+
+strip-ansi@^3.0.0, strip-ansi@^3.0.1:
   version "3.0.1"
   resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-3.0.1.tgz#6a385fb8853d952d5ff05d0e8aaf94278dc63dcf"
   integrity sha1-ajhfuIU9lS1f8F0Oiq+UJ43GPc8=
@@ -5904,6 +6381,11 @@ strip-indent@^1.0.1:
   dependencies:
     get-stdin "^4.0.1"
 
+strip-json-comments@~2.0.1:
+  version "2.0.1"
+  resolved "https://registry.yarnpkg.com/strip-json-comments/-/strip-json-comments-2.0.1.tgz#3c531942e908c2697c0ec344858c286c7ca0a60a"
+  integrity sha1-PFMZQukIwml8DsNEhYwobHygpgo=
+
 strip-outer@^1.0.0:
   version "1.0.1"
   resolved "https://registry.yarnpkg.com/strip-outer/-/strip-outer-1.0.1.tgz#b2fd2abf6604b9d1e6013057195df836b8a9d631"
@@ -5959,6 +6441,11 @@ svgo@^1.0.0, svgo@^1.0.5:
     unquote "~1.1.1"
     util.promisify "~1.0.0"
 
+tapable@^1.0.0:
+  version "1.1.3"
+  resolved "https://registry.yarnpkg.com/tapable/-/tapable-1.1.3.tgz#a1fccc06b58db61fd7a45da2da44f5f3a3e67ba2"
+  integrity sha512-4WK/bYZmj8xLr+HUCODHGF1ZFzsYffasLUgEiMBY4fgtltdO6B4WJtlSbPaDTLpYTcGVwM2qLnFTICEcNxs3kA==
+
 tar-stream@^1.5.2:
   version "1.6.2"
   resolved "https://registry.yarnpkg.com/tar-stream/-/tar-stream-1.6.2.tgz#8ea55dab37972253d9a9af90fdcd559ae435c555"
@@ -5972,14 +6459,26 @@ tar-stream@^1.5.2:
     to-buffer "^1.1.1"
     xtend "^4.0.0"
 
-tcp-port-used@^0.1.2:
-  version "0.1.2"
-  resolved "https://registry.yarnpkg.com/tcp-port-used/-/tcp-port-used-0.1.2.tgz#9450e8768c83b416fd4d1a6a9449eeccbf496c29"
-  integrity sha1-lFDodoyDtBb9TRpqlEnuzL9JbCk=
+tar@^4:
+  version "4.4.10"
+  resolved "https://registry.yarnpkg.com/tar/-/tar-4.4.10.tgz#946b2810b9a5e0b26140cf78bea6b0b0d689eba1"
+  integrity sha512-g2SVs5QIxvo6OLp0GudTqEf05maawKUxXru104iaayWA09551tFCTI8f1Asb4lPfkBr91k07iL4c11XO3/b0tA==
   dependencies:
-    debug "0.7.4"
-    is2 "0.0.9"
-    q "0.9.7"
+    chownr "^1.1.1"
+    fs-minipass "^1.2.5"
+    minipass "^2.3.5"
+    minizlib "^1.2.1"
+    mkdirp "^0.5.0"
+    safe-buffer "^5.1.2"
+    yallist "^3.0.3"
+
+tcp-port-used@^1.0.1:
+  version "1.0.1"
+  resolved "https://registry.yarnpkg.com/tcp-port-used/-/tcp-port-used-1.0.1.tgz#46061078e2d38c73979a2c2c12b5a674e6689d70"
+  integrity sha512-rwi5xJeU6utXoEIiMvVBMc9eJ2/ofzB+7nLOdnZuFTmNCLqRiQh2sMG9MqCxHU/69VC/Fwp5dV9306Qd54ll1Q==
+  dependencies:
+    debug "4.1.0"
+    is2 "2.0.1"
 
 temp-dir@^1.0.0:
   version "1.0.0"
@@ -6098,6 +6597,13 @@ tough-cookie@~2.4.3:
     psl "^1.1.24"
     punycode "^1.4.1"
 
+tr46@^1.0.1:
+  version "1.0.1"
+  resolved "https://registry.yarnpkg.com/tr46/-/tr46-1.0.1.tgz#a8b13fd6bfd2489519674ccde55ba3693b706d09"
+  integrity sha1-qLE/1r/SSJUZZ0zN5VujaTtwbQk=
+  dependencies:
+    punycode "^2.1.0"
+
 tree-node-cli@^1.2.5:
   version "1.2.5"
   resolved "https://registry.yarnpkg.com/tree-node-cli/-/tree-node-cli-1.2.5.tgz#afd75437976bbf2cc0c52b9949798e7530e8fd8c"
@@ -6130,6 +6636,11 @@ truncate-html@^1.0.1:
     "@types/cheerio" "^0.22.8"
     cheerio "0.22.0"
 
+tslib@^1.9.0, tslib@^1.9.3:
+  version "1.10.0"
+  resolved "https://registry.yarnpkg.com/tslib/-/tslib-1.10.0.tgz#c3c19f95973fb0a62973fb09d90d961ee43e5c8a"
+  integrity sha512-qOebF53frne81cf0S9B41ByenJ3/IuH8yJKngAX35CmiZySA0khhkovshKK+jGCaMnVomla7gVlIcc3EvKPbTQ==
+
 tunnel-agent@^0.6.0:
   version "0.6.0"
   resolved "https://registry.yarnpkg.com/tunnel-agent/-/tunnel-agent-0.6.0.tgz#27a5dea06b36b04a0a9966774b290868f0fc40fd"
@@ -6168,11 +6679,6 @@ underscore.string@~2.4.0:
   resolved "https://registry.yarnpkg.com/underscore.string/-/underscore.string-2.4.0.tgz#8cdd8fbac4e2d2ea1e7e2e8097c42f442280f85b"
   integrity sha1-jN2PusTi0uoefi6Al8QvRCKA+Fs=
 
-underscore@^1.7.0:
-  version "1.9.1"
-  resolved "https://registry.yarnpkg.com/underscore/-/underscore-1.9.1.tgz#06dce34a0e68a7babc29b365b8e74b8925203961"
-  integrity sha512-5/4etnCkd9c8gwgowi5/om/mYO5ajCaOgdzj/oW+0eQV9WxKBDZw5+ycmKmeaTXjInS/W0BzpGLo2xR2aBwZdg==
-
 underscore@~1.7.0:
   version "1.7.0"
   resolved "https://registry.yarnpkg.com/underscore/-/underscore-1.7.0.tgz#6bbaf0877500d36be34ecaa584e0db9fef035209"
@@ -6244,6 +6750,11 @@ unset-value@^1.0.0:
     has-value "^0.3.1"
     isobject "^3.0.0"
 
+upath@^1.1.1:
+  version "1.2.0"
+  resolved "https://registry.yarnpkg.com/upath/-/upath-1.2.0.tgz#8f66dbcd55a883acdae4408af8b035a5044c1894"
+  integrity sha512-aZwGpamFO61g3OlfT7OQCHqhGnW43ieH9WZeP7QxN/G/jS4jfqUkZxoryvJgVPEcrl5NL/ggHsSmLMHuH64Lhg==
+
 uri-js@^4.2.2:
   version "4.2.2"
   resolved "https://registry.yarnpkg.com/uri-js/-/uri-js-4.2.2.tgz#94c540e1ff772956e2299507c010aea6c8838eb0"
@@ -6256,11 +6767,6 @@ urix@^0.1.0:
   resolved "https://registry.yarnpkg.com/urix/-/urix-0.1.0.tgz#da937f7a62e21fec1fd18d49b35c2935067a6c72"
   integrity sha1-2pN/emLiH+wf0Y1Js1wpNQZ6bHI=
 
-url-join@^1.1.0:
-  version "1.1.0"
-  resolved "https://registry.yarnpkg.com/url-join/-/url-join-1.1.0.tgz#741c6c2f4596c4830d6718460920d0c92202dc78"
-  integrity sha1-dBxsL0WWxIMNZxhGCSDQySIC3Hg=
-
 url-parse-lax@^1.0.0:
   version "1.0.0"
   resolved "https://registry.yarnpkg.com/url-parse-lax/-/url-parse-lax-1.0.0.tgz#7af8f303645e9bd79a272e7a14ac68bc0609da73"
@@ -6275,7 +6781,7 @@ url-parse-lax@^3.0.0:
   dependencies:
     prepend-http "^2.0.0"
 
-url-parse@^1.1.8, url-parse@^1.4.3:
+url-parse@^1.4.3:
   version "1.4.7"
   resolved "https://registry.yarnpkg.com/url-parse/-/url-parse-1.4.7.tgz#a8a83535e8c00a316e403a5db4ac1b9b853ae278"
   integrity sha512-d3uaVyzDB9tQoSXFvuSUNFibTd9zxd2bkVrDRvF5TmvWWQwqE4lgYJ5m+x1DbecWkw+LK4RNl2CU1hHuOKPVlg==
@@ -6350,6 +6856,11 @@ verror@1.10.0:
     core-util-is "1.0.2"
     extsprintf "^1.2.0"
 
+webidl-conversions@^4.0.2:
+  version "4.0.2"
+  resolved "https://registry.yarnpkg.com/webidl-conversions/-/webidl-conversions-4.0.2.tgz#a855980b1f0b6b359ba1d5d9fb39ae941faa63ad"
+  integrity sha512-YQ+BmxuTgd6UXZW3+ICGfyqRyHXVlD5GtQr5+qjiNW7bF0cqrzX500HVXPBOvgXb5YnzDd+h0zqyv61KUD7+Sg==
+
 websocket-driver@>=0.5.1:
   version "0.7.3"
   resolved "https://registry.yarnpkg.com/websocket-driver/-/websocket-driver-0.7.3.tgz#a2d4e0d4f4f116f1e6297eba58b05d430100e9f9"
@@ -6364,18 +6875,41 @@ websocket-extensions@>=0.1.1:
   resolved "https://registry.yarnpkg.com/websocket-extensions/-/websocket-extensions-0.1.3.tgz#5d2ff22977003ec687a4b87073dfbbac146ccf29"
   integrity sha512-nqHUnMXmBzT0w570r2JpJxfiSD1IzoI+HGVdd3aZ0yNi3ngvQ4jv1dtHt5VGxfI2yj5yqImPhOK4vmIh2xMbGg==
 
-which@^1.2.14, which@^1.2.9:
+whatwg-url@^7.0.0:
+  version "7.0.0"
+  resolved "https://registry.yarnpkg.com/whatwg-url/-/whatwg-url-7.0.0.tgz#fde926fa54a599f3adf82dff25a9f7be02dc6edd"
+  integrity sha512-37GeVSIJ3kn1JgKyjiYNmSLP1yzbpb29jdmwBSgkD9h40/hyrR/OifpVUndji3tmwGgD8qpw7iQu3RSbCrBpsQ==
+  dependencies:
+    lodash.sortby "^4.7.0"
+    tr46 "^1.0.1"
+    webidl-conversions "^4.0.2"
+
+which@^1.2.9, which@^1.3.1:
   version "1.3.1"
   resolved "https://registry.yarnpkg.com/which/-/which-1.3.1.tgz#a45043d54f5805316da8d62f9f50918d3da70b0a"
   integrity sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==
   dependencies:
     isexe "^2.0.0"
 
+wide-align@^1.1.0:
+  version "1.1.3"
+  resolved "https://registry.yarnpkg.com/wide-align/-/wide-align-1.1.3.tgz#ae074e6bdc0c14a431e804e624549c633b000457"
+  integrity sha512-QGkOQc8XL6Bt5PwnsExKBPuMKBxnGxWWW3fU55Xt4feHozMUhdUMaBCk290qpm/wG5u/RSKzwdAC4i51YigihA==
+  dependencies:
+    string-width "^1.0.2 || 2"
+
 wordwrap@0.0.2:
   version "0.0.2"
   resolved "https://registry.yarnpkg.com/wordwrap/-/wordwrap-0.0.2.tgz#b79669bb42ecb409f83d583cad52ca17eaa1643f"
   integrity sha1-t5Zpu0LstAn4PVg8rVLKF+qhZD8=
 
+worker-rpc@^0.1.0:
+  version "0.1.1"
+  resolved "https://registry.yarnpkg.com/worker-rpc/-/worker-rpc-0.1.1.tgz#cb565bd6d7071a8f16660686051e969ad32f54d5"
+  integrity sha512-P1WjMrUB3qgJNI9jfmpZ/htmBEjFh//6l/5y8SD9hg1Ef5zTTVVoRjTrTEzPrNBQvmhMxkoTsjOXN10GWU7aCg==
+  dependencies:
+    microevent.ts "~0.1.1"
+
 wrappy@1:
   version "1.0.2"
   resolved "https://registry.yarnpkg.com/wrappy/-/wrappy-1.0.2.tgz#b5243d8f3ec1aa35f1364605bc0d1036e30ab69f"
@@ -6386,6 +6920,11 @@ xml@^1.0.1:
   resolved "https://registry.yarnpkg.com/xml/-/xml-1.0.1.tgz#78ba72020029c5bc87b8a81a3cfcd74b4a2fc1e5"
   integrity sha1-eLpyAgApxbyHuKgaPPzXS0ovweU=
 
+xmlbuilder@^13.0.0:
+  version "13.0.2"
+  resolved "https://registry.yarnpkg.com/xmlbuilder/-/xmlbuilder-13.0.2.tgz#02ae33614b6a047d1c32b5389c1fdacb2bce47a7"
+  integrity sha512-Eux0i2QdDYKbdbA6AM6xE4m6ZTZr4G4xF9kahI2ukSEMCzwce2eX9WlTI5J3s+NU7hpasFsr8hWIONae7LluAQ==
+
 xtend@^4.0.0, xtend@~4.0.0:
   version "4.0.1"
   resolved "https://registry.yarnpkg.com/xtend/-/xtend-4.0.1.tgz#a5c6d532be656e23db820efb943a1f04998d63af"
@@ -6396,6 +6935,11 @@ yallist@^2.1.2:
   resolved "https://registry.yarnpkg.com/yallist/-/yallist-2.1.2.tgz#1c11f9218f076089a47dd512f93c6699a6a81d52"
   integrity sha1-HBH5IY8HYImkfdUS+TxmmaaoHVI=
 
+yallist@^3.0.0, yallist@^3.0.3:
+  version "3.0.3"
+  resolved "https://registry.yarnpkg.com/yallist/-/yallist-3.0.3.tgz#b4b049e314be545e3ce802236d6cd22cd91c3de9"
+  integrity sha512-S+Zk8DEWE6oKpV+vI3qWkaK+jSbIK86pCwe2IF/xwIpQ8jEuxpw9NyaGjmp9+BoJv5FV2piqCDcoCtStppiq2A==
+
 yamljs@^0.2.1:
   version "0.2.10"
   resolved "https://registry.yarnpkg.com/yamljs/-/yamljs-0.2.10.tgz#481cc7c25ca73af59f591f0c96e3ce56c757a40f"

From 63be01fe12af6900cb9ee7dc253410a1c4afd80b Mon Sep 17 00:00:00 2001
From: Kacper Wiszczuk <kacperwiszczuk@gmail.com>
Date: Fri, 13 Sep 2019 19:59:26 +0200
Subject: [PATCH 07/26] imp: snack example for RefreshControl, SafeAreaView and
 ScrollView (#1242)

* imp: snack example for components

* revert pretter stuff
---
 docs/refreshcontrol.md | 81 ++++++++++++++++++++++++++----------------
 docs/safeareaview.md   | 23 ++++++++----
 docs/scrollview.md     | 40 +++++++++++++++++++++
 3 files changed, 107 insertions(+), 37 deletions(-)

diff --git a/docs/refreshcontrol.md b/docs/refreshcontrol.md
index 25361415174..beac784b065 100644
--- a/docs/refreshcontrol.md
+++ b/docs/refreshcontrol.md
@@ -5,41 +5,60 @@ title: RefreshControl
 
 This component is used inside a ScrollView or ListView to add pull to refresh functionality. When the ScrollView is at `scrollY: 0`, swiping down triggers an `onRefresh` event.
 
-### Usage example
-
-```jsx
-import { ScrollView, RefreshControl } from 'react-native';
-
-class RefreshableList extends Component {
-  constructor(props) {
-    super(props);
-    this.state = {
-      refreshing: false,
-    };
-  }
-
-  _onRefresh = () => {
-    this.setState({refreshing: true});
-    fetchData().then(() => {
-      this.setState({refreshing: false});
-    });
-  }
-
-  render() {
-    return (
+### Example
+
+```SnackPlayer name=RefreshControl
+import React from 'react';
+import {
+  ScrollView,
+  RefreshControl,
+  StyleSheet,
+  Text,
+  SafeAreaView,
+} from 'react-native';
+import Constants from 'expo-constants';
+
+function wait(timeout) {
+  return new Promise(resolve => {
+    setTimeout(resolve, timeout);
+  });
+}
+
+export default function App() {
+  const [refreshing, setRefreshing] = React.useState(false);
+
+  const onRefresh = React.useCallback(() => {
+    setRefreshing(true);
+
+    wait(2000).then(() => setRefreshing(false));
+  }, [refreshing]);
+
+  return (
+    <SafeAreaView style={styles.container}>
       <ScrollView
+        contentContainerStyle={styles.scrollView}
         refreshControl={
-          <RefreshControl
-            refreshing={this.state.refreshing}
-            onRefresh={this._onRefresh}
-          />
+          <RefreshControl refreshing={refreshing} onRefresh={onRefresh} />
         }
-        ...
-      />
-    );
-  }
-  ...
+      >
+        <Text>Pull down to see RefreshControl indicator</Text>
+      </ScrollView>
+    </SafeAreaView>
+  );
 }
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+    marginTop: Constants.statusBarHeight,
+  },
+  scrollView: {
+    flex: 1,
+    backgroundColor: 'pink',
+    alignItems: 'center',
+    justifyContent: 'center',
+  },
+});
 ```
 
 **Note:** `refreshing` is a controlled prop, this is why it needs to be set to true in the `onRefresh` function otherwise the refresh indicator will stop immediately.
diff --git a/docs/safeareaview.md b/docs/safeareaview.md
index e913464f268..10324ebd639 100644
--- a/docs/safeareaview.md
+++ b/docs/safeareaview.md
@@ -11,12 +11,23 @@ The purpose of `SafeAreaView` is to render content within the safe area boundari
 
 Simply wrap your top level view with a `SafeAreaView` with a `flex: 1` style applied to it. You may also want to use a background color that matches your application's design.
 
-```jsx
-<SafeAreaView style={{flex: 1, backgroundColor: '#fff'}}>
-  <View style={{flex: 1}}>
-    <Text>Hello World!</Text>
-  </View>
-</SafeAreaView>
+```SnackPlayer name=SafeAreaView
+import React from 'react';
+import { StyleSheet, Text, SafeAreaView } from 'react-native';
+
+export default function App() {
+  return (
+    <SafeAreaView style={styles.container}>
+      <Text>Page content</Text>
+    </SafeAreaView>
+  );
+}
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+  },
+});
 ```
 
 ---
diff --git a/docs/scrollview.md b/docs/scrollview.md
index 1f60a60fb1d..110c2eba596 100644
--- a/docs/scrollview.md
+++ b/docs/scrollview.md
@@ -19,6 +19,46 @@ This is where `FlatList` comes into play. `FlatList` renders items lazily, just
 
 `FlatList` is also handy if you want to render separators between your items, multiple columns, infinite scroll loading, or any number of other features it supports out of the box.
 
+### Example
+
+```SnackPlayer name=ScrollView
+import React from 'react';
+import { StyleSheet, Text, SafeAreaView, ScrollView } from 'react-native';
+import Constants from 'expo-constants';
+
+export default function App() {
+  return (
+    <SafeAreaView style={styles.container}>
+      <ScrollView style={styles.scrollView}>
+        <Text style={styles.text}>
+          Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do
+          eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad
+          minim veniam, quis nostrud exercitation ullamco laboris nisi ut
+          aliquip ex ea commodo consequat. Duis aute irure dolor in
+          reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla
+          pariatur. Excepteur sint occaecat cupidatat non proident, sunt in
+          culpa qui officia deserunt mollit anim id est laborum.
+        </Text>
+      </ScrollView>
+    </SafeAreaView>
+  );
+}
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+    marginTop: Constants.statusBarHeight,
+  },
+  scrollView: {
+    backgroundColor: 'pink',
+    marginHorizontal: 20,
+  },
+  text: {
+    fontSize: 42,
+  },
+});
+```
+
 ---
 
 # Reference

From 1e28632ae32ee6a944516f12e48b04932148d83b Mon Sep 17 00:00:00 2001
From: Anurag Kyal <anuragkyal2008@gmail.com>
Date: Fri, 13 Sep 2019 14:00:05 -0400
Subject: [PATCH 08/26] Fix 2nd code block rendering (#1243)

---
 docs/height-and-width.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/height-and-width.md b/docs/height-and-width.md
index 08d9cadeec1..35dc5459e96 100644
--- a/docs/height-and-width.md
+++ b/docs/height-and-width.md
@@ -34,7 +34,7 @@ Use `flex` in a component's style to have the component expand and shrink dynami
 
 > A component can only expand to fill available space if its parent has dimensions greater than 0. If a parent does not have either a fixed `width` and `height` or `flex`, the parent will have dimensions of 0 and the `flex` children will not be visible.
 
-````SnackPlayer name=Flex%20Dimensions
+```SnackPlayer name=Flex%20Dimensions
 import React, { Component } from 'react';
 import { View } from 'react-native';
 
@@ -55,4 +55,3 @@ export default class FlexDimensionsBasics extends Component {
 ```
 
 After you can control a component's size, the next step is to [learn how to lay it out on the screen](flexbox.md).
-````

From 703cc58719ef29cdee12cee0003cb559f382d9f6 Mon Sep 17 00:00:00 2001
From: Will Holen <46539685+willholen@users.noreply.github.com>
Date: Fri, 13 Sep 2019 11:03:01 -0700
Subject: [PATCH 09/26] Explicitly mention how to upgrade RN when switching to
 Hermes (#1245)

---
 docs/hermes.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/hermes.md b/docs/hermes.md
index edfb31e2f9b..29472d204dd 100644
--- a/docs/hermes.md
+++ b/docs/hermes.md
@@ -9,7 +9,9 @@ title: Using Hermes
 
 [Hermes](https://hermesengine.dev) is an open-source JavaScript engine optimized for running React Native apps on Android. For many apps, simply enabling Hermes will result in improved start-up time, decreased memory usage, and smaller app size. At this time Hermes is an **opt-in** React Native feature, and this guide explains how to enable it.
 
-First, ensure you're using at least version 0.60.4 of React Native. If you're upgrading an existing app ensure everything works before trying to switch to Hermes.
+First, ensure you're using at least version 0.60.4 of React Native.
+
+If you have an existing app based on an earlier version of React Native, you will have to upgrade it first. See [Upgrading to new React Native Versions](/react-native/docs/upgrading) for how to do this. Make especially sure that all changes to `android/app/build.gradle` have been applied, as detailed by the [React Native upgrade helper](https://react-native-community.github.io/upgrade-helper/?from=0.59.0). After upgrading the app, make sure everything works before trying to switch to Hermes.
 
 > ## Note for Windows users.
 >

From 5edea43cabdb2820215c35c40a1dbe8545527a66 Mon Sep 17 00:00:00 2001
From: Kacper Wiszczuk <kacperwiszczuk@gmail.com>
Date: Fri, 13 Sep 2019 20:04:00 +0200
Subject: [PATCH 10/26] imp: Snack example for SectionList (#1247)

* imp: Snack example for SectionList

* Revert prettier mess
---
 docs/sectionlist.md | 101 ++++++++++++++++++++++++++++++++------------
 1 file changed, 73 insertions(+), 28 deletions(-)

diff --git a/docs/sectionlist.md b/docs/sectionlist.md
index 7f6b659f1b1..caec8271de2 100644
--- a/docs/sectionlist.md
+++ b/docs/sectionlist.md
@@ -20,34 +20,79 @@ If you don't need section support and want a simpler interface, use [`<FlatList>
 
 Simple Examples:
 
-```jsx
-// Example 1 (Homogeneous Rendering)
-<SectionList
-  renderItem={({item, index, section}) => <Text key={index}>{item}</Text>}
-  renderSectionHeader={({section: {title}}) => (
-    <Text style={{fontWeight: 'bold'}}>{title}</Text>
-  )}
-  sections={[
-    {title: 'Title1', data: ['item1', 'item2']},
-    {title: 'Title2', data: ['item3', 'item4']},
-    {title: 'Title3', data: ['item5', 'item6']},
-  ]}
-  keyExtractor={(item, index) => item + index}
-/>
-```
-
-```jsx
-// Example 2 (Heterogeneous Rendering / No Section Headers)
-const overrideRenderItem = ({ item, index, section: { title, data } }) => <Text key={index}>Override{item}</Text>
-
-<SectionList
-  renderItem={({ item, index, section }) => <Text key={index}>{item}</Text>}
-  sections={[
-    { title: 'Title1', data: ['item1', 'item2'], renderItem: overrideRenderItem },
-    { title: 'Title2', data: ['item3', 'item4'] },
-    { title: 'Title3', data: ['item5', 'item6'] },
-  ]}
-/>
+### Example
+
+```SnackPlayer name=SectionList
+import React from 'react';
+import {
+  StyleSheet,
+  Text,
+  View,
+  SafeAreaView,
+  SectionList,
+} from 'react-native';
+import Constants from 'expo-constants';
+
+const DATA = [
+  {
+    title: 'Main dishes',
+    data: ['Pizza', 'Burger', 'Risotto'],
+  },
+  {
+    title: 'Sides',
+    data: ['French Fries', 'Onion Rings', 'Fried Shrimps'],
+  },
+  {
+    title: 'Drinks',
+    data: ['Water', 'Coke', 'Beer'],
+  },
+  {
+    title: 'Desserts',
+    data: ['Cheese Cake', 'Ice Cream'],
+  },
+];
+
+function Item({ title }) {
+  return (
+    <View style={styles.item}>
+      <Text style={styles.title}>{title}</Text>
+    </View>
+  );
+}
+
+export default function App() {
+  return (
+    <SafeAreaView style={styles.container}>
+      <SectionList
+        sections={DATA}
+        keyExtractor={(item, index) => item + index}
+        renderItem={({ item }) => <Item title={item} />}
+        renderSectionHeader={({ section: { title } }) => (
+          <Text style={styles.header}>{title}</Text>
+        )}
+      />
+    </SafeAreaView>
+  );
+}
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+    marginTop: Constants.statusBarHeight,
+    marginHorizontal: 16,
+  },
+  item: {
+    backgroundColor: '#f9c2ff',
+    padding: 20,
+    marginVertical: 8,
+  },
+  header: {
+    fontSize: 32,
+  },
+  title: {
+    fontSize: 24,
+  },
+});
 ```
 
 This is a convenience wrapper around [`<VirtualizedList>`](virtualizedlist.md), and thus inherits its props (as well as those of [`<ScrollView>`](scrollview.md) that aren't explicitly listed here, along with the following caveats:

From d796c2dda051379fda2c40025abe6045be7cdd4d Mon Sep 17 00:00:00 2001
From: Chris Brody <chris@brody.consulting>
Date: Fri, 13 Sep 2019 14:05:38 -0400
Subject: [PATCH 11/26] Add react-native-community/react-native-tvos (#1250)

to out-of-tree-platforms.md
---
 docs/out-of-tree-platforms.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/out-of-tree-platforms.md b/docs/out-of-tree-platforms.md
index ac7bd91f176..ed6639f31c0 100644
--- a/docs/out-of-tree-platforms.md
+++ b/docs/out-of-tree-platforms.md
@@ -10,6 +10,7 @@ React Native is not just for Android and iOS - there are community-supported pro
 - [React Native Turbolinks](https://github.com/lazaronixon/react-native-turbolinks) - React Native adapter for building hybrid apps with Turbolinks 5.
 - [React Native Desktop](https://github.com/status-im/react-native-desktop) - A project aiming to bring React Native to the Desktop with Qt's QML. A fork of [React Native Ubuntu](https://github.com/CanonicalLtd/react-native/), which is no longer maintained.
 - [React Native macOS](https://github.com/ptmt/react-native-macos) - An experimental React Native fork targeting macOS and Cocoa
+- [React Native tvOS](https://github.com/react-native-community/react-native-tvos) - adaptation of React Native for Apple tvOS
 - [alita](https://github.com/areslabs/alita) - An experimental, comprehensive port of React Native to mini-program(微信小程序).
 
 ## Creating your own React Native platform

From e817b5e444b4f56e9d02025526468094d486c86a Mon Sep 17 00:00:00 2001
From: ibenge Uforo <benjamin.uforo@gmail.com>
Date: Fri, 13 Sep 2019 19:31:41 +0100
Subject: [PATCH 12/26] Update navigation.md (#1258)

* Update navigation.md

createStackNavigator has been moved to react-navigation-stack in  react-navigation 4.x docs

* Update navigation.md
---
 docs/navigation.md | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/docs/navigation.md b/docs/navigation.md
index 046ddba857b..5bedc57ca32 100644
--- a/docs/navigation.md
+++ b/docs/navigation.md
@@ -27,10 +27,19 @@ yarn add react-native-gesture-handler
 # npm install --save react-native-gesture-handler
 ```
 
+The third step is to install react-navigation-stack
+
+```
+yarn add react-navigation-stack
+# or with npm
+# npm install --save react-navigation-stack
+```
+
 Then you can quickly create an app with a home screen and a profile screen:
 
 ```jsx
-import {createStackNavigator, createAppContainer} from 'react-navigation';
+import {createAppContainer} from 'react-navigation';
+import {createStackNavigator} from 'react-navigation-stack'
 
 const MainNavigator = createStackNavigator({
   Home: {screen: HomeScreen},

From 339bf7a6562f9700b696ddf185097a9d002dc949 Mon Sep 17 00:00:00 2001
From: Alister Norris <alnorris@users.noreply.github.com>
Date: Fri, 13 Sep 2019 19:40:04 +0100
Subject: [PATCH 13/26] Update event emitter code examples for Android (#1261)

---
 docs/native-modules-android.md | 48 +++++++++++-----------------------
 1 file changed, 15 insertions(+), 33 deletions(-)

diff --git a/docs/native-modules-android.md b/docs/native-modules-android.md
index 806360bdd51..5932c3a1c8e 100644
--- a/docs/native-modules-android.md
+++ b/docs/native-modules-android.md
@@ -40,12 +40,14 @@ import java.util.Map;
 import java.util.HashMap;
 
 public class ToastModule extends ReactContextBaseJavaModule {
+  private static ReactApplicationContext reactContext;
 
   private static final String DURATION_SHORT_KEY = "SHORT";
   private static final String DURATION_LONG_KEY = "LONG";
 
-  ToastModule(ReactApplicationContext reactContext) {
-    super(reactContext);
+  ToastModule(ReactApplicationContext context) {
+    super(context);
+    reactContext = context;
   }
 }
 ```
@@ -303,6 +305,8 @@ Native modules can signal events to JavaScript without being invoked directly. T
 ```java
 ...
 import com.facebook.react.modules.core.DeviceEventManagerModule;
+import com.facebook.react.bridge.WritableMap;
+import com.facebook.react.bridge.Arguments;
 ...
 private void sendEvent(ReactContext reactContext,
                        String eventName,
@@ -313,49 +317,27 @@ private void sendEvent(ReactContext reactContext,
 }
 ...
 WritableMap params = Arguments.createMap();
+params.putString("eventProperty", "someValue");
 ...
-sendEvent(reactContext, "keyboardWillShow", params);
+sendEvent(reactContext, "EventReminder", params);
 ```
 
-JavaScript modules can then register to receive events by `addListenerOn` using the `Subscribable` mixin.
+JavaScript modules can then register to receive events by `addListener` on the NativeEventEmitter class.
 
 ```jsx
-import { DeviceEventEmitter } from 'react-native';
+import { NativeEventEmitter, NativeModules } from 'react-native';
 ...
 
-var ScrollResponderMixin = {
-  mixins: [Subscribable.Mixin],
-
-
   componentDidMount() {
     ...
-    this.addListenerOn(DeviceEventEmitter,
-                       'keyboardWillShow',
-                       this.scrollResponderKeyboardWillShow);
+    const eventEmitter = new NativeEventEmitter(NativeModules.ToastExample);
+    eventEmitter.addListener('EventReminder', (event) => {
+       console.log(event.eventProperty) // "someValue"
+    }
     ...
-  },
-  scrollResponderKeyboardWillShow:function(e: Event) {
-    this.keyboardWillOpenTo = e;
-    this.props.onKeyboardWillShow && this.props.onKeyboardWillShow(e);
-  },
+  }
 ```
 
-You can also directly use the `DeviceEventEmitter` module to listen for events.
-
-```jsx
-...
-componentDidMount() {
-  this.subscription = DeviceEventEmitter.addListener('keyboardWillShow', function(e: Event) {
-    // handle event
-  });
-}
-
-componentWillUnmount() {
-  // When you want to stop listening to new events, simply call .remove() on the subscription
-  this.subscription.remove();
-}
-...
-```
 
 ### Getting activity result from `startActivityForResult`
 

From 5aa09fdedfa2c6e426e98e6818ba9d0555d81a97 Mon Sep 17 00:00:00 2001
From: Nicolas Charpentier <nicolas.charpentier079@gmail.com>
Date: Fri, 13 Sep 2019 14:40:43 -0400
Subject: [PATCH 14/26] s/fadeAdmin/fadeAnim (#1265)

---
 docs/animations.md                               | 6 +++---
 website/versioned_docs/version-0.5/animations.md | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/animations.md b/docs/animations.md
index ce154a63364..d90ac7947b7 100644
--- a/docs/animations.md
+++ b/docs/animations.md
@@ -20,11 +20,11 @@ import React, { useState, useEffect } from 'react';
 import { Animated, Text, View } from 'react-native';
 
 const FadeInView = (props) => {
-  const [fadeAdmin] = useState(new Animated.Value(0))  // Initial value for opacity: 0
+  const [fadeAnim] = useState(new Animated.Value(0))  // Initial value for opacity: 0
 
   React.useEffect(() => {
     Animated.timing(
-      fadeAdmin,
+      fadeAnim,
       {
         toValue: 1,
         duration: 10000,
@@ -36,7 +36,7 @@ const FadeInView = (props) => {
     <Animated.View                 // Special animatable View
       style={{
         ...props.style,
-        opacity: fadeAdnim,         // Bind opacity to animated value
+        opacity: fadeAnim,         // Bind opacity to animated value
       }}
     >
       {props.children}
diff --git a/website/versioned_docs/version-0.5/animations.md b/website/versioned_docs/version-0.5/animations.md
index 7b73d696aed..85245e3a1b8 100644
--- a/website/versioned_docs/version-0.5/animations.md
+++ b/website/versioned_docs/version-0.5/animations.md
@@ -21,11 +21,11 @@ import React, { useState, useEffect } from 'react';
 import { Animated, Text, View } from 'react-native';
 
 const FadeInView = (props) => {
-  const [fadeAdmin] = useState(new Animated.Value(0))  // Initial value for opacity: 0
+  const [fadeAnim] = useState(new Animated.Value(0))  // Initial value for opacity: 0
 
   React.useEffect(() => {
     Animated.timing(
-      fadeAdmin,
+      fadeAnim,
       {
         toValue: 1,
         duration: 10000,
@@ -37,7 +37,7 @@ const FadeInView = (props) => {
     <Animated.View                 // Special animatable View
       style={{
         ...props.style,
-        opacity: fadeAdnim,         // Bind opacity to animated value
+        opacity: fadeAnim,         // Bind opacity to animated value
       }}
     >
       {props.children}

From f52abd3614634d48f0f3aa345aea9380b2969e56 Mon Sep 17 00:00:00 2001
From: Nicolas Charpentier <nicolas.charpentier079@gmail.com>
Date: Fri, 13 Sep 2019 15:07:35 -0400
Subject: [PATCH 15/26] Improve Optimizing FlatList page (#1266)

---
 docs/optimizing-flatlist-configuration.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/optimizing-flatlist-configuration.md b/docs/optimizing-flatlist-configuration.md
index 1a1633f5b8e..abf912a5660 100644
--- a/docs/optimizing-flatlist-configuration.md
+++ b/docs/optimizing-flatlist-configuration.md
@@ -5,7 +5,7 @@ title: Optimizing Flatlist Configuration
 
 ## Terms
 
-- **VirtualizedList:** The component behind `FlatList` (React Native's implementation of the '[Virtual List](https://bvaughn.github.io/react-virtualized/#/components/List)' concept.)
+- **VirtualizedList:** The component behind `FlatList` (React Native's implementation of the [`Virtual List`](https://bvaughn.github.io/react-virtualized/#/components/List) concept.)
 
 - **Memory consumption:** How much information about your list is being stored in memory, which could lead to an app crash.
 
@@ -110,9 +110,9 @@ The heavier your components are, the slower they render. Avoid heavy images (use
 Implement update verification to your components. React's `PureComponent` implement a [`shouldComponentUpdate`](https://reactjs.org/docs/react-component.html#shouldcomponentupdate) with shallow comparison. This is expensive here because it need to check all your props. If you want a good bit-level performance, create the strictest rules for your list item components, checking only props that could potentially change. If your list is simple enough, you could even use
 
 ```jsx
-    shouldComponentUpdate() {
-      return false
-    }
+shouldComponentUpdate() {
+  return false
+}
 ```
 
 ### Use cached optimized images

From f899dbd837a5091865a9df1c65c7db29ca1036b7 Mon Sep 17 00:00:00 2001
From: Nicolas Charpentier <nicolas.charpentier079@gmail.com>
Date: Fri, 13 Sep 2019 15:07:47 -0400
Subject: [PATCH 16/26] Remove WebView from components-and-apis (#1267)

---
 docs/components-and-apis.md | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/docs/components-and-apis.md b/docs/components-and-apis.md
index 663c43254ca..2c88beb504f 100644
--- a/docs/components-and-apis.md
+++ b/docs/components-and-apis.md
@@ -288,10 +288,4 @@ These components may come in handy for certain applications. For an exhaustive l
       <p>Component to control the app status bar.</p>
     </a>
   </div>
-  <div class="component">
-    <a href="./webview">
-      <h3>WebView</h3>
-      <p>A component that renders web content in a native view.</p>
-    </a>
-  </div>
 </div>

From b38aa9363fa46bac76fd06a8349e257785e7411e Mon Sep 17 00:00:00 2001
From: Nicolas Charpentier <nicolas.charpentier079@gmail.com>
Date: Fri, 13 Sep 2019 15:08:08 -0400
Subject: [PATCH 17/26] Change the order of Optimizing FlatList (#1268)

---
 website/sidebars.json                                 | 2 +-
 website/versioned_sidebars/version-0.60-sidebars.json | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/sidebars.json b/website/sidebars.json
index e8c50f84953..86b071aa38a 100644
--- a/website/sidebars.json
+++ b/website/sidebars.json
@@ -16,7 +16,6 @@
       "more-resources"
     ],
     "Guides": [
-      "optimizing-flatlist-configuration",
       "components-and-apis",
       "platform-specific-code",
       "navigation",
@@ -24,6 +23,7 @@
       "animations",
       "accessibility",
       "improvingux",
+      "optimizing-flatlist-configuration",
       "timers",
       "debugging",
       "performance",
diff --git a/website/versioned_sidebars/version-0.60-sidebars.json b/website/versioned_sidebars/version-0.60-sidebars.json
index ece917fd2dc..002566899bf 100644
--- a/website/versioned_sidebars/version-0.60-sidebars.json
+++ b/website/versioned_sidebars/version-0.60-sidebars.json
@@ -16,7 +16,6 @@
       "version-0.60-more-resources"
     ],
     "Guides": [
-      "version-0.60-optimizing-flatlist-configuration",
       "version-0.60-components-and-apis",
       "version-0.60-platform-specific-code",
       "version-0.60-navigation",
@@ -24,6 +23,7 @@
       "version-0.60-animations",
       "version-0.60-accessibility",
       "version-0.60-improvingux",
+      "version-0.60-optimizing-flatlist-configuration",
       "version-0.60-timers",
       "version-0.60-debugging",
       "version-0.60-performance",

From 535f87ad8996742934c1c8b988400eedd6a6d5d7 Mon Sep 17 00:00:00 2001
From: Nicolas Charpentier <nicolas.charpentier079@gmail.com>
Date: Fri, 13 Sep 2019 15:10:47 -0400
Subject: [PATCH 18/26] Replace tag ending with </button> (#1269)

---
 docs/getting-started.md                               | 10 +++++-----
 website/versioned_docs/version-0.5/getting-started.md | 10 +++++-----
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/getting-started.md b/docs/getting-started.md
index f23f4250a78..ae4553671d4 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -91,17 +91,17 @@ The instructions are a bit different depending on your development operating sys
 <div class="toggler">
   <span>Development OS:</span>
   <span role="tablist" id="toggle-os">
-    <button role="tab" class="button-mac" onclick="displayTab('os', 'mac')">macOS</a>
-    <button role="tab" class="button-windows" onclick="displayTab('os', 'windows')">Windows</a>
-    <button role="tab" class="button-linux" onclick="displayTab('os', 'linux')">Linux</a>
+    <button role="tab" class="button-mac" onclick="displayTab('os', 'mac')">macOS</button>
+    <button role="tab" class="button-windows" onclick="displayTab('os', 'windows')">Windows</button>
+    <button role="tab" class="button-linux" onclick="displayTab('os', 'linux')">Linux</button>
   </span>
 </div>
 
 <div class="toggler">
   <span>Target OS:</span>
   <span role="tablist" id="toggle-platform">
-    <button role="tab" class="button-ios" onclick="displayTab('platform', 'ios')">iOS</a>
-    <button role="tab" class="button-android" onclick="displayTab('platform', 'android')">Android</a>
+    <button role="tab" class="button-ios" onclick="displayTab('platform', 'ios')">iOS</button>
+    <button role="tab" class="button-android" onclick="displayTab('platform', 'android')">Android</button>
   </span>
 </div>
 
diff --git a/website/versioned_docs/version-0.5/getting-started.md b/website/versioned_docs/version-0.5/getting-started.md
index c2e04056c11..d3d0c8ac85d 100644
--- a/website/versioned_docs/version-0.5/getting-started.md
+++ b/website/versioned_docs/version-0.5/getting-started.md
@@ -92,17 +92,17 @@ The instructions are a bit different depending on your development operating sys
 <div class="toggler">
   <span>Development OS:</span>
   <span role="tablist" id="toggle-os">
-    <button role="tab" class="button-mac" onclick="displayTab('os', 'mac')">macOS</a>
-    <button role="tab" class="button-windows" onclick="displayTab('os', 'windows')">Windows</a>
-    <button role="tab" class="button-linux" onclick="displayTab('os', 'linux')">Linux</a>
+    <button role="tab" class="button-mac" onclick="displayTab('os', 'mac')">macOS</button>
+    <button role="tab" class="button-windows" onclick="displayTab('os', 'windows')">Windows</button>
+    <button role="tab" class="button-linux" onclick="displayTab('os', 'linux')">Linux</button>
   </span>
 </div>
 
 <div class="toggler">
   <span>Target OS:</span>
   <span role="tablist" id="toggle-platform">
-    <button role="tab" class="button-ios" onclick="displayTab('platform', 'ios')">iOS</a>
-    <button role="tab" class="button-android" onclick="displayTab('platform', 'android')">Android</a>
+    <button role="tab" class="button-ios" onclick="displayTab('platform', 'ios')">iOS</button>
+    <button role="tab" class="button-android" onclick="displayTab('platform', 'android')">Android</button>
   </span>
 </div>
 

From 2ed6793299ac9f2054eac13bc2f35ec7db83a8cf Mon Sep 17 00:00:00 2001
From: Nicolas Charpentier <nicolas.charpentier079@gmail.com>
Date: Fri, 13 Sep 2019 16:10:06 -0400
Subject: [PATCH 19/26] Republish 0.60 (#1270)

* Republish 0.60

* Prettify
---
 docs/native-modules-android.md                |   1 -
 docs/navigation.md                            |   2 +-
 website/versionedDocsBlacklist.json           |   3 +-
 .../version-0.5/components-and-apis.md        | 244 +++++++++++-------
 .../version-0.5/height-and-width.md           |   3 +-
 .../version-0.5/native-modules-android.md     |  49 ++--
 .../versioned_docs/version-0.5/navigation.md  |  11 +-
 .../optimizing-flatlist-configuration.md      |  10 +-
 website/versioned_docs/version-0.60/hermes.md |   4 +-
 .../version-0.60/inputaccessoryview.md        |   2 +-
 .../version-0.60/out-of-tree-platforms.md     |   1 +
 .../version-0.60/refreshcontrol.md            |  81 +++---
 .../version-0.60/safeareaview.md              |  23 +-
 .../versioned_docs/version-0.60/scrollview.md |  40 +++
 .../version-0.60/sectionlist.md               | 101 ++++++--
 15 files changed, 376 insertions(+), 199 deletions(-)
 rename website/versioned_docs/{version-0.60 => version-0.5}/optimizing-flatlist-configuration.md (96%)

diff --git a/docs/native-modules-android.md b/docs/native-modules-android.md
index 5932c3a1c8e..82d5fca3ddd 100644
--- a/docs/native-modules-android.md
+++ b/docs/native-modules-android.md
@@ -338,7 +338,6 @@ import { NativeEventEmitter, NativeModules } from 'react-native';
   }
 ```
 
-
 ### Getting activity result from `startActivityForResult`
 
 You'll need to listen to `onActivityResult` if you want to get results from an activity you started with `startActivityForResult`. To do this, you must extend `BaseActivityEventListener` or implement `ActivityEventListener`. The former is preferred as it is more resilient to API changes. Then, you need to register the listener in the module's constructor,
diff --git a/docs/navigation.md b/docs/navigation.md
index 5bedc57ca32..651f8d3a24b 100644
--- a/docs/navigation.md
+++ b/docs/navigation.md
@@ -39,7 +39,7 @@ Then you can quickly create an app with a home screen and a profile screen:
 
 ```jsx
 import {createAppContainer} from 'react-navigation';
-import {createStackNavigator} from 'react-navigation-stack'
+import {createStackNavigator} from 'react-navigation-stack';
 
 const MainNavigator = createStackNavigator({
   Home: {screen: HomeScreen},
diff --git a/website/versionedDocsBlacklist.json b/website/versionedDocsBlacklist.json
index 3652422625a..21be57b3d29 100644
--- a/website/versionedDocsBlacklist.json
+++ b/website/versionedDocsBlacklist.json
@@ -43,5 +43,6 @@
   "native-components-android",
   "headless-js-android",
   "signed-apk-android",
-  "removing-default-permissions"
+  "removing-default-permissions",
+  "optimizing-flatlist-configuration"
 ]
diff --git a/website/versioned_docs/version-0.5/components-and-apis.md b/website/versioned_docs/version-0.5/components-and-apis.md
index af38cd9a26a..202fbafa327 100644
--- a/website/versioned_docs/version-0.5/components-and-apis.md
+++ b/website/versioned_docs/version-0.5/components-and-apis.md
@@ -21,28 +21,40 @@ Most apps will end up using one of these basic components. You'll want to get yo
 
 <div class="component-grid component-grid-border">
   <div class="component">
-    <h3><a href="./view">View</a></h3>
-    <p>The most fundamental component for building a UI.</p>
+    <a href="./view">
+      <h3>View</h3>
+      <p>The most fundamental component for building a UI.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./text">Text</a></h3>
-    <p>A component for displaying text.</p>
+    <a href="./text">
+      <h3>Text</h3>
+      <p>A component for displaying text.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./image">Image</a></h3>
-    <p>A component for displaying images.</p>
+    <a href="./image">
+      <h3>Image</h3>
+      <p>A component for displaying images.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./textinput">TextInput</a></h3>
-    <p>A component for inputting text into the app via a keyboard.</p>
+    <a href="./textinput">
+      <h3>TextInput</h3>
+      <p>A component for inputting text into the app via a keyboard.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./scrollview">ScrollView</a></h3>
-    <p>Provides a scrolling container that can host multiple components and views.</p>
+    <a href="./scrollview">
+      <h3>ScrollView</h3>
+      <p>Provides a scrolling container that can host multiple components and views.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./stylesheet">StyleSheet</a></h3>
-    <p>Provides an abstraction layer similar to CSS stylesheets.</p>
+    <a href="./stylesheet">
+      <h3>StyleSheet</h3>
+      <p>Provides an abstraction layer similar to CSS stylesheets.</p>
+    </a>
   </div>
 </div>
 
@@ -52,35 +64,47 @@ Render common user interface controls on any platform using the following compon
 
 <div class="component-grid component-grid-border">
   <div class="component">
-    <h3><a href="./button">Button</a></h3>
-    <p>A basic button component for handling touches that should render nicely on any platform.</p>
+    <a href="./button">
+      <h3>Button</h3>
+      <p>A basic button component for handling touches that should render nicely on any platform.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./picker">Picker</a></h3>
-    <p>Renders the native picker component on iOS and Android.</p>
+    <a href="./picker">
+      <h3>Picker</h3>
+      <p>Renders the native picker component on iOS and Android.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./slider">Slider</a></h3>
-    <p>A component used to select a single value from a range of values.</p>
+    <a href="./slider">
+      <h3>Slider</h3>
+      <p>A component used to select a single value from a range of values.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./switch">Switch</a></h3>
-    <p>Renders a boolean input.</p>
+    <a href="./switch">
+      <h3>Switch</h3>
+      <p>Renders a boolean input.</p>
+    </a>
   </div>
 </div>
 
 ## List Views
 
-Unlike the more generic `ScrollView`, the following list view components only render elements that are currently showing on the screen. This makes them a great choice for displaying long lists of data.
+Unlike the more generic [`ScrollView`](./scrollview.md), the following list view components only render elements that are currently showing on the screen. This makes them a great choice for displaying long lists of data.
 
 <div class="component-grid component-grid-border">
   <div class="component">
-    <h3><a href="./flatlist">FlatList</a></h3>
-    <p>A component for rendering performant scrollable lists.</p>
+    <a href="./flatlist">
+      <h3>FlatList</h3>
+      <p>A component for rendering performant scrollable lists.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./sectionlist">SectionList</a></h3>
-    <p>Like <code>FlatList</code>, but for sectioned lists.</p>
+    <a href="./sectionlist">
+      <h3>SectionList</h3>
+      <p>Like <code>FlatList</code>, but for sectioned lists.</p>
+    </a>
   </div>
 </div>
 
@@ -90,36 +114,46 @@ Many of the following components provide wrappers for commonly used UIKit classe
 
 <div class="component-grid component-grid-border">
   <div class="component">
-    <h3><a href="./actionsheetios">ActionSheetIOS</a></h3>
-    <p>API to display an iOS action sheet or share sheet.</p>
+    <a href="./actionsheetios">
+      <h3>ActionSheetIOS</h3>
+      <p>API to display an iOS action sheet or share sheet.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./alertios">AlertIOS</a></h3>
-    <p>Create an iOS alert dialog with a message or create a prompt for user input.</p>
+    <a href="./alertios">
+      <h3>AlertIOS</h3>
+      <p>Create an iOS alert dialog with a message or create a prompt for user input.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./datepickerios">DatePickerIOS</a></h3>
-    <p>Renders a date/time picker (selector) on iOS.</p>
+    <a href="./datepickerios">
+      <h3>DatePickerIOS</h3>
+      <p>Renders a date/time picker (selector) on iOS.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./imagepickerios">ImagePickerIOS</a></h3>
-    <p>Renders a image picker on iOS.</p>
+    <a href="./imagepickerios">
+      <h3>ImagePickerIOS</h3>
+      <p>Renders a image picker on iOS.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./progressviewios">ProgressViewIOS</a></h3>
-    <p>Renders a <code>UIProgressView</a></code> on iOS.</p>
+    <a href="./progressviewios">
+      <h3>ProgressViewIOS</h3>
+      <p>Renders a <code>UIProgressView</code> on iOS.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./pushnotificationios">PushNotificationIOS</a></h3>
-    <p>Handle push notifications for your app, including permission handling and icon badge number.</p>
+    <a href="./pushnotificationios">
+      <h3>PushNotificationIOS</h3>
+      <p>Handle push notifications for your app, including permission handling and icon badge number.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./segmentedcontrolios">SegmentedControlIOS</a></h3>
-    <p>Renders a <code>UISegmentedControl</code> on iOS.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./tabbarios">TabBarIOS</a></h3>
-    <p>Renders a <code>UITabViewController</code> on iOS. Use with <a href="./tabbarios-item">TabBarIOS.Item</a>.</p>
+    <a href="./segmentedcontrolios">
+      <h3>SegmentedControlIOS</h3>
+      <p>Renders a <code>UISegmentedControl</code> on iOS.</p>
+    </a>
   </div>
 </div>
 
@@ -129,40 +163,58 @@ Many of the following components provide wrappers for commonly used Android clas
 
 <div class="component-grid component-grid-border">
   <div class="component">
-    <h3><a href="./backhandler">BackHandler</a></h3>
-    <p>Detect hardware button presses for back navigation.</p>
+    <a href="./backhandler">
+      <h3>BackHandler</a></h3>
+      <p>Detect hardware button presses for back navigation.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./datepickerandroid">DatePickerAndroid</a></h3>
-    <p>Opens the standard Android date picker dialog.</p>
+    <a href="./datepickerandroid">
+      <h3>DatePickerAndroid</h3>
+      <p>Opens the standard Android date picker dialog.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./drawerlayoutandroid">DrawerLayoutAndroid</a></h3>
-    <p>Renders a <code>DrawerLayout</code> on Android.</p>
+    <a href="./drawerlayoutandroid">
+      <h3>DrawerLayoutAndroid</h3>
+      <p>Renders a <code>DrawerLayout</code> on Android.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./permissionsandroid">PermissionsAndroid</a></h3>
-    <p>Provides access to the permissions model introduced in Android M.</p>
+    <a href="./permissionsandroid">
+      <h3>PermissionsAndroid</a></h3>
+      <p>Provides access to the permissions model introduced in Android M.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./progressbarandroid">ProgressBarAndroid</a></h3>
-    <p>Renders a <code>ProgressBar</code> on Android.</p>
+    <a href="./progressbarandroid">
+      <h3>ProgressBarAndroid</h3>
+      <p>Renders a <code>ProgressBar</code> on Android.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./timepickerandroid">TimePickerAndroid</a></h3>
-    <p>Opens the standard Android time picker dialog.</p>
+    <a href="./timepickerandroid">
+      <h3>TimePickerAndroid</h3>
+      <p>Opens the standard Android time picker dialog.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./toastandroid">ToastAndroid</a></h3>
-    <p>Create an Android Toast alert.</p>
+    <a href="./toastandroid">
+      <h3>ToastAndroid</h3>
+      <p>Create an Android Toast alert.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./toolbarandroid">ToolbarAndroid</a></h3>
-    <p>Renders a <code>Toolbar</code> on Android.</p>
+    <a href="./toolbarandroid">
+      <h3>ToolbarAndroid</h3>
+      <p>Renders a <code>Toolbar</code> on Android.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./viewpagerandroid">ViewPagerAndroid</a></h3>
-    <p>Container that allows to flip left and right between child views.</p>
+    <a href="./viewpagerandroid">
+      <h3>ViewPagerAndroid</h3>
+      <p>Container that allows to flip left and right between child views.</p>
+    </a>
   </div>
 </div>
 
@@ -172,51 +224,69 @@ These components may come in handy for certain applications. For an exhaustive l
 
 <div class="component-grid">
   <div class="component">
-    <h3><a href="./activityindicator">ActivityIndicator</a></h3>
-    <p>Displays a circular loading indicator.</p>
-  </div>
-  <div class="component">
-    <h3><a href="./alert">Alert</a></h3>
-    <p>Launches an alert dialog with the specified title and message.</p>
+    <a href="./activityindicator">
+      <h3>ActivityIndicator</h3>
+      <p>Displays a circular loading indicator.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./animated">Animated</a></h3>
-    <p>A library for creating fluid, powerful animations that are easy to build and maintain.</p>
+    <a href="./alert">
+      <h3>Alert</h3>
+      <p>Launches an alert dialog with the specified title and message.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./clipboard">Clipboard</a></h3>
-    <p>Provides an interface for setting and getting content from the clipboard on both iOS and Android.</p>
+    <a href="./animated">
+      <h3>Animated</h3>
+      <p>A library for creating fluid, powerful animations that are easy to build and maintain.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./dimensions">Dimensions</a></h3>
-    <p>Provides an interface for getting device dimensions.</p>
+    <a href="./clipboard">
+      <h3>Clipboard</h3>
+      <p>Provides an interface for setting and getting content from the clipboard on both iOS and Android.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./keyboardavoidingview">KeyboardAvoidingView</a></h3>
-    <p>Provides a view that moves out of the way of the virtual keyboard automatically.</p>
+    <a href="./dimensions">
+      <h3>Dimensions</h3>
+      <p>Provides an interface for getting device dimensions.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./linking">Linking</a></h3>
-    <p>Provides a general interface to interact with both incoming and outgoing app links.</p>
+    <a href="./keyboardavoidingview">
+      <h3>KeyboardAvoidingView</h3>
+      <p>Provides a view that moves out of the way of the virtual keyboard automatically.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./modal">Modal</a></h3>
-    <p>Provides a simple way to present content above an enclosing view.</p>
+    <a href="./linking">
+      <h3>Linking</h3>
+      <p>Provides a general interface to interact with both incoming and outgoing app links.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./pixelratio">PixelRatio</a></h3>
-    <p>Provides access to the device pixel density.</p>
+    <a href="./modal">
+      <h3>Modal</h3>
+      <p>Provides a simple way to present content above an enclosing view.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./refreshcontrol">RefreshControl</a></h3>
-    <p>This component is used inside a <code>ScrollView</code> to add pull to refresh functionality.</p>
+    <a href="./pixelratio">
+      <h3>PixelRatio</h3>
+      <p>Provides access to the device pixel density.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./statusbar">StatusBar</a></h3>
-    <p>Component to control the app status bar.</p>
+    <a href="./refreshcontrol">
+      <h3>RefreshControl</h3>
+      <p>This component is used inside a <code>ScrollView</code> to add pull to refresh functionality.</p>
+    </a>
   </div>
   <div class="component">
-    <h3><a href="./webview">WebView</a></h3>
-    <p>A component that renders web content in a native view.</p>
+    <a href="./statusbar">
+      <h3>StatusBar</h3>
+      <p>Component to control the app status bar.</p>
+    </a>
   </div>
 </div>
diff --git a/website/versioned_docs/version-0.5/height-and-width.md b/website/versioned_docs/version-0.5/height-and-width.md
index e478ba61d9a..29b63956bf6 100644
--- a/website/versioned_docs/version-0.5/height-and-width.md
+++ b/website/versioned_docs/version-0.5/height-and-width.md
@@ -35,7 +35,7 @@ Use `flex` in a component's style to have the component expand and shrink dynami
 
 > A component can only expand to fill available space if its parent has dimensions greater than 0. If a parent does not have either a fixed `width` and `height` or `flex`, the parent will have dimensions of 0 and the `flex` children will not be visible.
 
-````SnackPlayer name=Flex%20Dimensions
+```SnackPlayer name=Flex%20Dimensions
 import React, { Component } from 'react';
 import { View } from 'react-native';
 
@@ -56,4 +56,3 @@ export default class FlexDimensionsBasics extends Component {
 ```
 
 After you can control a component's size, the next step is to [learn how to lay it out on the screen](flexbox.md).
-````
diff --git a/website/versioned_docs/version-0.5/native-modules-android.md b/website/versioned_docs/version-0.5/native-modules-android.md
index 6f9e3488886..d5ec5ca9045 100644
--- a/website/versioned_docs/version-0.5/native-modules-android.md
+++ b/website/versioned_docs/version-0.5/native-modules-android.md
@@ -41,12 +41,14 @@ import java.util.Map;
 import java.util.HashMap;
 
 public class ToastModule extends ReactContextBaseJavaModule {
+  private static ReactApplicationContext reactContext;
 
   private static final String DURATION_SHORT_KEY = "SHORT";
   private static final String DURATION_LONG_KEY = "LONG";
 
-  ToastModule(ReactApplicationContext reactContext) {
-    super(reactContext);
+  ToastModule(ReactApplicationContext context) {
+    super(context);
+    reactContext = context;
   }
 }
 ```
@@ -304,6 +306,8 @@ Native modules can signal events to JavaScript without being invoked directly. T
 ```java
 ...
 import com.facebook.react.modules.core.DeviceEventManagerModule;
+import com.facebook.react.bridge.WritableMap;
+import com.facebook.react.bridge.Arguments;
 ...
 private void sendEvent(ReactContext reactContext,
                        String eventName,
@@ -314,48 +318,25 @@ private void sendEvent(ReactContext reactContext,
 }
 ...
 WritableMap params = Arguments.createMap();
+params.putString("eventProperty", "someValue");
 ...
-sendEvent(reactContext, "keyboardWillShow", params);
+sendEvent(reactContext, "EventReminder", params);
 ```
 
-JavaScript modules can then register to receive events by `addListenerOn` using the `Subscribable` mixin.
+JavaScript modules can then register to receive events by `addListener` on the NativeEventEmitter class.
 
 ```jsx
-import { DeviceEventEmitter } from 'react-native';
+import { NativeEventEmitter, NativeModules } from 'react-native';
 ...
 
-var ScrollResponderMixin = {
-  mixins: [Subscribable.Mixin],
-
-
   componentDidMount() {
     ...
-    this.addListenerOn(DeviceEventEmitter,
-                       'keyboardWillShow',
-                       this.scrollResponderKeyboardWillShow);
+    const eventEmitter = new NativeEventEmitter(NativeModules.ToastExample);
+    eventEmitter.addListener('EventReminder', (event) => {
+       console.log(event.eventProperty) // "someValue"
+    }
     ...
-  },
-  scrollResponderKeyboardWillShow:function(e: Event) {
-    this.keyboardWillOpenTo = e;
-    this.props.onKeyboardWillShow && this.props.onKeyboardWillShow(e);
-  },
-```
-
-You can also directly use the `DeviceEventEmitter` module to listen for events.
-
-```jsx
-...
-componentDidMount() {
-  this.subscription = DeviceEventEmitter.addListener('keyboardWillShow', function(e: Event) {
-    // handle event
-  });
-}
-
-componentWillUnmount() {
-  // When you want to stop listening to new events, simply call .remove() on the subscription
-  this.subscription.remove();
-}
-...
+  }
 ```
 
 ### Getting activity result from `startActivityForResult`
diff --git a/website/versioned_docs/version-0.5/navigation.md b/website/versioned_docs/version-0.5/navigation.md
index a752c40b0cb..70a52e73108 100644
--- a/website/versioned_docs/version-0.5/navigation.md
+++ b/website/versioned_docs/version-0.5/navigation.md
@@ -28,10 +28,19 @@ yarn add react-native-gesture-handler
 # npm install --save react-native-gesture-handler
 ```
 
+The third step is to install react-navigation-stack
+
+```
+yarn add react-navigation-stack
+# or with npm
+# npm install --save react-navigation-stack
+```
+
 Then you can quickly create an app with a home screen and a profile screen:
 
 ```jsx
-import {createStackNavigator, createAppContainer} from 'react-navigation';
+import {createAppContainer} from 'react-navigation';
+import {createStackNavigator} from 'react-navigation-stack';
 
 const MainNavigator = createStackNavigator({
   Home: {screen: HomeScreen},
diff --git a/website/versioned_docs/version-0.60/optimizing-flatlist-configuration.md b/website/versioned_docs/version-0.5/optimizing-flatlist-configuration.md
similarity index 96%
rename from website/versioned_docs/version-0.60/optimizing-flatlist-configuration.md
rename to website/versioned_docs/version-0.5/optimizing-flatlist-configuration.md
index 421524f1202..b0bcaad2f01 100644
--- a/website/versioned_docs/version-0.60/optimizing-flatlist-configuration.md
+++ b/website/versioned_docs/version-0.5/optimizing-flatlist-configuration.md
@@ -1,12 +1,12 @@
 ---
-id: version-0.60-optimizing-flatlist-configuration
+id: version-0.5-optimizing-flatlist-configuration
 title: Optimizing Flatlist Configuration
 original_id: optimizing-flatlist-configuration
 ---
 
 ## Terms
 
-- **VirtualizedList:** The component behind `FlatList` (React Native's implementation of the '[Virtual List](https://bvaughn.github.io/react-virtualized/#/components/List)' concept.)
+- **VirtualizedList:** The component behind `FlatList` (React Native's implementation of the [`Virtual List`](https://bvaughn.github.io/react-virtualized/#/components/List) concept.)
 
 - **Memory consumption:** How much information about your list is being stored in memory, which could lead to an app crash.
 
@@ -111,9 +111,9 @@ The heavier your components are, the slower they render. Avoid heavy images (use
 Implement update verification to your components. React's `PureComponent` implement a [`shouldComponentUpdate`](https://reactjs.org/docs/react-component.html#shouldcomponentupdate) with shallow comparison. This is expensive here because it need to check all your props. If you want a good bit-level performance, create the strictest rules for your list item components, checking only props that could potentially change. If your list is simple enough, you could even use
 
 ```jsx
-    shouldComponentUpdate() {
-      return false
-    }
+shouldComponentUpdate() {
+  return false
+}
 ```
 
 ### Use cached optimized images
diff --git a/website/versioned_docs/version-0.60/hermes.md b/website/versioned_docs/version-0.60/hermes.md
index f5073e6fd78..e5e81c0e78b 100644
--- a/website/versioned_docs/version-0.60/hermes.md
+++ b/website/versioned_docs/version-0.60/hermes.md
@@ -10,7 +10,9 @@ original_id: hermes
 
 [Hermes](https://hermesengine.dev) is an open-source JavaScript engine optimized for running React Native apps on Android. For many apps, simply enabling Hermes will result in improved start-up time, decreased memory usage, and smaller app size. At this time Hermes is an **opt-in** React Native feature, and this guide explains how to enable it.
 
-First, ensure you're using at least version 0.60.4 of React Native. If you're upgrading an existing app ensure everything works before trying to switch to Hermes.
+First, ensure you're using at least version 0.60.4 of React Native.
+
+If you have an existing app based on an earlier version of React Native, you will have to upgrade it first. See [Upgrading to new React Native Versions](/react-native/docs/upgrading) for how to do this. Make especially sure that all changes to `android/app/build.gradle` have been applied, as detailed by the [React Native upgrade helper](https://react-native-community.github.io/upgrade-helper/?from=0.59.0). After upgrading the app, make sure everything works before trying to switch to Hermes.
 
 > ## Note for Windows users.
 >
diff --git a/website/versioned_docs/version-0.60/inputaccessoryview.md b/website/versioned_docs/version-0.60/inputaccessoryview.md
index a1f096229a3..e8543bf2f33 100644
--- a/website/versioned_docs/version-0.60/inputaccessoryview.md
+++ b/website/versioned_docs/version-0.60/inputaccessoryview.md
@@ -45,7 +45,7 @@ export default class UselessTextInput extends Component {
 }
 ```
 
-This component can also be used to create sticky text inputs (text inputs which are anchored to the top of the keyboard). To do this, wrap a `TextInput` with the `InputAccessoryView` component, and don't set a `nativeID`. For an example, look at [InputAccessoryViewExample.js](https://github.com/facebook/react-native/blob/master/RNTester/js/InputAccessoryViewExample.js).
+This component can also be used to create sticky text inputs (text inputs which are anchored to the top of the keyboard). To do this, wrap a `TextInput` with the `InputAccessoryView` component, and don't set a `nativeID`. For an example, look at [InputAccessoryViewExample.js](https://github.com/facebook/react-native/blob/master/RNTester/js/examples/InputAccessoryView/InputAccessoryViewExample.js).
 
 ---
 
diff --git a/website/versioned_docs/version-0.60/out-of-tree-platforms.md b/website/versioned_docs/version-0.60/out-of-tree-platforms.md
index 43731ddbcad..d79a023f421 100644
--- a/website/versioned_docs/version-0.60/out-of-tree-platforms.md
+++ b/website/versioned_docs/version-0.60/out-of-tree-platforms.md
@@ -11,6 +11,7 @@ React Native is not just for Android and iOS - there are community-supported pro
 - [React Native Turbolinks](https://github.com/lazaronixon/react-native-turbolinks) - React Native adapter for building hybrid apps with Turbolinks 5.
 - [React Native Desktop](https://github.com/status-im/react-native-desktop) - A project aiming to bring React Native to the Desktop with Qt's QML. A fork of [React Native Ubuntu](https://github.com/CanonicalLtd/react-native/), which is no longer maintained.
 - [React Native macOS](https://github.com/ptmt/react-native-macos) - An experimental React Native fork targeting macOS and Cocoa
+- [React Native tvOS](https://github.com/react-native-community/react-native-tvos) - adaptation of React Native for Apple tvOS
 - [alita](https://github.com/areslabs/alita) - An experimental, comprehensive port of React Native to mini-program(微信小程序).
 
 ## Creating your own React Native platform
diff --git a/website/versioned_docs/version-0.60/refreshcontrol.md b/website/versioned_docs/version-0.60/refreshcontrol.md
index 2ace228bc77..b9692b9f7ec 100644
--- a/website/versioned_docs/version-0.60/refreshcontrol.md
+++ b/website/versioned_docs/version-0.60/refreshcontrol.md
@@ -6,41 +6,60 @@ original_id: refreshcontrol
 
 This component is used inside a ScrollView or ListView to add pull to refresh functionality. When the ScrollView is at `scrollY: 0`, swiping down triggers an `onRefresh` event.
 
-### Usage example
-
-```jsx
-import { ScrollView, RefreshControl } from 'react-native';
-
-class RefreshableList extends Component {
-  constructor(props) {
-    super(props);
-    this.state = {
-      refreshing: false,
-    };
-  }
-
-  _onRefresh = () => {
-    this.setState({refreshing: true});
-    fetchData().then(() => {
-      this.setState({refreshing: false});
-    });
-  }
-
-  render() {
-    return (
+### Example
+
+```SnackPlayer name=RefreshControl
+import React from 'react';
+import {
+  ScrollView,
+  RefreshControl,
+  StyleSheet,
+  Text,
+  SafeAreaView,
+} from 'react-native';
+import Constants from 'expo-constants';
+
+function wait(timeout) {
+  return new Promise(resolve => {
+    setTimeout(resolve, timeout);
+  });
+}
+
+export default function App() {
+  const [refreshing, setRefreshing] = React.useState(false);
+
+  const onRefresh = React.useCallback(() => {
+    setRefreshing(true);
+
+    wait(2000).then(() => setRefreshing(false));
+  }, [refreshing]);
+
+  return (
+    <SafeAreaView style={styles.container}>
       <ScrollView
+        contentContainerStyle={styles.scrollView}
         refreshControl={
-          <RefreshControl
-            refreshing={this.state.refreshing}
-            onRefresh={this._onRefresh}
-          />
+          <RefreshControl refreshing={refreshing} onRefresh={onRefresh} />
         }
-        ...
-      />
-    );
-  }
-  ...
+      >
+        <Text>Pull down to see RefreshControl indicator</Text>
+      </ScrollView>
+    </SafeAreaView>
+  );
 }
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+    marginTop: Constants.statusBarHeight,
+  },
+  scrollView: {
+    flex: 1,
+    backgroundColor: 'pink',
+    alignItems: 'center',
+    justifyContent: 'center',
+  },
+});
 ```
 
 **Note:** `refreshing` is a controlled prop, this is why it needs to be set to true in the `onRefresh` function otherwise the refresh indicator will stop immediately.
diff --git a/website/versioned_docs/version-0.60/safeareaview.md b/website/versioned_docs/version-0.60/safeareaview.md
index 412ff12117c..eff80c75e2b 100644
--- a/website/versioned_docs/version-0.60/safeareaview.md
+++ b/website/versioned_docs/version-0.60/safeareaview.md
@@ -12,12 +12,23 @@ The purpose of `SafeAreaView` is to render content within the safe area boundari
 
 Simply wrap your top level view with a `SafeAreaView` with a `flex: 1` style applied to it. You may also want to use a background color that matches your application's design.
 
-```jsx
-<SafeAreaView style={{flex: 1, backgroundColor: '#fff'}}>
-  <View style={{flex: 1}}>
-    <Text>Hello World!</Text>
-  </View>
-</SafeAreaView>
+```SnackPlayer name=SafeAreaView
+import React from 'react';
+import { StyleSheet, Text, SafeAreaView } from 'react-native';
+
+export default function App() {
+  return (
+    <SafeAreaView style={styles.container}>
+      <Text>Page content</Text>
+    </SafeAreaView>
+  );
+}
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+  },
+});
 ```
 
 ---
diff --git a/website/versioned_docs/version-0.60/scrollview.md b/website/versioned_docs/version-0.60/scrollview.md
index da975227c32..76273bc3da2 100644
--- a/website/versioned_docs/version-0.60/scrollview.md
+++ b/website/versioned_docs/version-0.60/scrollview.md
@@ -20,6 +20,46 @@ This is where `FlatList` comes into play. `FlatList` renders items lazily, just
 
 `FlatList` is also handy if you want to render separators between your items, multiple columns, infinite scroll loading, or any number of other features it supports out of the box.
 
+### Example
+
+```SnackPlayer name=ScrollView
+import React from 'react';
+import { StyleSheet, Text, SafeAreaView, ScrollView } from 'react-native';
+import Constants from 'expo-constants';
+
+export default function App() {
+  return (
+    <SafeAreaView style={styles.container}>
+      <ScrollView style={styles.scrollView}>
+        <Text style={styles.text}>
+          Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do
+          eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad
+          minim veniam, quis nostrud exercitation ullamco laboris nisi ut
+          aliquip ex ea commodo consequat. Duis aute irure dolor in
+          reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla
+          pariatur. Excepteur sint occaecat cupidatat non proident, sunt in
+          culpa qui officia deserunt mollit anim id est laborum.
+        </Text>
+      </ScrollView>
+    </SafeAreaView>
+  );
+}
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+    marginTop: Constants.statusBarHeight,
+  },
+  scrollView: {
+    backgroundColor: 'pink',
+    marginHorizontal: 20,
+  },
+  text: {
+    fontSize: 42,
+  },
+});
+```
+
 ---
 
 # Reference
diff --git a/website/versioned_docs/version-0.60/sectionlist.md b/website/versioned_docs/version-0.60/sectionlist.md
index 390745f0cbb..92c7381c696 100644
--- a/website/versioned_docs/version-0.60/sectionlist.md
+++ b/website/versioned_docs/version-0.60/sectionlist.md
@@ -21,34 +21,79 @@ If you don't need section support and want a simpler interface, use [`<FlatList>
 
 Simple Examples:
 
-```jsx
-// Example 1 (Homogeneous Rendering)
-<SectionList
-  renderItem={({item, index, section}) => <Text key={index}>{item}</Text>}
-  renderSectionHeader={({section: {title}}) => (
-    <Text style={{fontWeight: 'bold'}}>{title}</Text>
-  )}
-  sections={[
-    {title: 'Title1', data: ['item1', 'item2']},
-    {title: 'Title2', data: ['item3', 'item4']},
-    {title: 'Title3', data: ['item5', 'item6']},
-  ]}
-  keyExtractor={(item, index) => item + index}
-/>
-```
-
-```jsx
-// Example 2 (Heterogeneous Rendering / No Section Headers)
-const overrideRenderItem = ({ item, index, section: { title, data } }) => <Text key={index}>Override{item}</Text>
-
-<SectionList
-  renderItem={({ item, index, section }) => <Text key={index}>{item}</Text>}
-  sections={[
-    { title: 'Title1', data: ['item1', 'item2'], renderItem: overrideRenderItem },
-    { title: 'Title2', data: ['item3', 'item4'] },
-    { title: 'Title3', data: ['item5', 'item6'] },
-  ]}
-/>
+### Example
+
+```SnackPlayer name=SectionList
+import React from 'react';
+import {
+  StyleSheet,
+  Text,
+  View,
+  SafeAreaView,
+  SectionList,
+} from 'react-native';
+import Constants from 'expo-constants';
+
+const DATA = [
+  {
+    title: 'Main dishes',
+    data: ['Pizza', 'Burger', 'Risotto'],
+  },
+  {
+    title: 'Sides',
+    data: ['French Fries', 'Onion Rings', 'Fried Shrimps'],
+  },
+  {
+    title: 'Drinks',
+    data: ['Water', 'Coke', 'Beer'],
+  },
+  {
+    title: 'Desserts',
+    data: ['Cheese Cake', 'Ice Cream'],
+  },
+];
+
+function Item({ title }) {
+  return (
+    <View style={styles.item}>
+      <Text style={styles.title}>{title}</Text>
+    </View>
+  );
+}
+
+export default function App() {
+  return (
+    <SafeAreaView style={styles.container}>
+      <SectionList
+        sections={DATA}
+        keyExtractor={(item, index) => item + index}
+        renderItem={({ item }) => <Item title={item} />}
+        renderSectionHeader={({ section: { title } }) => (
+          <Text style={styles.header}>{title}</Text>
+        )}
+      />
+    </SafeAreaView>
+  );
+}
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+    marginTop: Constants.statusBarHeight,
+    marginHorizontal: 16,
+  },
+  item: {
+    backgroundColor: '#f9c2ff',
+    padding: 20,
+    marginVertical: 8,
+  },
+  header: {
+    fontSize: 32,
+  },
+  title: {
+    fontSize: 24,
+  },
+});
 ```
 
 This is a convenience wrapper around [`<VirtualizedList>`](virtualizedlist.md), and thus inherits its props (as well as those of [`<ScrollView>`](scrollview.md) that aren't explicitly listed here, along with the following caveats:

From 31e1a9105f139ef04702a9465c2440cdee9519bf Mon Sep 17 00:00:00 2001
From: Rick Hanlon <rickhanlonii@fb.com>
Date: Wed, 18 Sep 2019 16:10:45 +0100
Subject: [PATCH 20/26] Add 0.61 blog post

---
 website/blog/2019-09-18-version-0.61.md | 57 +++++++++++++++++++++++++
 1 file changed, 57 insertions(+)
 create mode 100644 website/blog/2019-09-18-version-0.61.md

diff --git a/website/blog/2019-09-18-version-0.61.md b/website/blog/2019-09-18-version-0.61.md
new file mode 100644
index 00000000000..c9b0d8c423f
--- /dev/null
+++ b/website/blog/2019-09-18-version-0.61.md
@@ -0,0 +1,57 @@
+---
+title: Announcing React Native 0.61 with Fast Refresh
+author: Dan Abramov
+authorTitle: React Core at Facebook
+authorURL: https://twitter.com/dan_abramov
+authorImageURL: https://avatars1.githubusercontent.com/u/810438?s=460&v=4
+authorTwitter: dan_abramov
+category: announcements
+---
+
+We’re excited to announce React Native 0.61, which includes a new reloading experience we’re calling Fast Refresh.
+
+## Fast Refresh
+
+When we asked the React Native community about [common pain points](https://github.com/react-native-community/discussions-and-proposals/issues/64), one of the top answers was that the “hot reloading” feature was broken. It didn’t work reliably for function components, often failed to update the screen, and wasn’t resilient to typos and mistakes. We heard that most people turned it off because it was too unreliable.
+
+In React Native 0.61, **we’re unifying the existing “live reloading” (reload on save) and “hot reloading” features into a single new feature called “Fast Refresh”**. Fast Refresh was implemented from scratch with the following principles:
+
+- Fast Refresh **fully supports modern React**, including function components and Hooks.
+- Fast Refresh **gracefully recovers after typos** and other mistakes, and falls back to a full reload when needed.
+- Fast Refresh **doesn’t perform invasive code transformations** so it’s reliable enough to be on by default.
+
+To see Fast Refresh in action, check out this video:
+
+<p style="text-align: center">
+<video width="700" controls="controls" autoplay>
+  <source type="video/mp4" src="https://facebook.github.io/react-native/img/homepage/ReactRefresh.mp4"></source>
+</video>
+</p>
+
+Give it a try, and let us know what you think! If you prefer, you can turn it off in the Dev Menu (Cmd+D on iOS, Cmd+M or Ctrl+M on Android). Turning it on and off is instant so you can do it any time.
+
+Here are a few Fast Refresh tips:
+
+- Fast Refresh preserves React local state in function components (and Hooks!) by default.
+- If you need to reset the React state on every edit, you can add a special `// @refresh reset` comment to the file with that component.
+- Fast Refresh always remounts class components without preserving state. This ensures it works reliably.
+- We all make mistakes in the code! Fast Refresh automatically retries rendering after you save a file. You don't need to reload the app manually after fixing a syntax or a runtime error.
+- Adding a `console.log` or a `debugger` statement during edits is a neat debugging technique.
+
+Please report any issues with Fast Refresh on GitHub, and we’ll look into them.
+
+## Other Improvements
+
+- **Fixed use_frameworks! CocoaPods support.** In 0.60 we made some updates to integrate CocoaPods by default. Unfortunately, this broke builds using [use_frameworks!](https://guides.cocoapods.org/syntax/podfile.html#use_frameworks_bang). This is [fixed in 0.61](https://github.com/facebook/react-native/pull/25619), making it easier to integrate React Native into your iOS projects that require building with dynamic frameworks.
+- **Add useWindowDimensions Hook. **This new Hook automatically provides and subscribes to dimension updates, and can be used instead of the Dimensions API in most cases. See [x] for more information.
+- **React was upgraded to 16.9.** This version deprecates old names for the UNSAFE\_ lifecycle methods, contains improvements to `act`, and more. See the [React 16.9 blog post](https://reactjs.org/blog/2019/08/08/react-v16.9.0.html) for an automated migration script and more information.
+
+## Breaking Changes
+
+- **Remove React .xcodeproj.** In 0.60, we introduced auto-linking support via CocoaPods. We have also integrated CocoaPods into the e2e tests runs, so that from now on, we have a unified standard way of integrating RN into iOS apps. This effectively deprecates the React .xcodeproj support, and the file has been removed starting 0.61. Note: if you use 0.60 auto-linking already, you shouldn't be affected.
+
+## Thanks
+
+Thanks to all of the contributors that helped make 0.61 possible!
+
+To see all the updates, take a look at the 0.61 changelog.

From 8db7d81b09c19c2e22800bcba56d416ba3c36294 Mon Sep 17 00:00:00 2001
From: Rick Hanlon <rickhanlonii@fb.com>
Date: Wed, 18 Sep 2019 17:16:20 +0100
Subject: [PATCH 21/26] Fix from review

---
 website/blog/2019-09-18-version-0.61.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/blog/2019-09-18-version-0.61.md b/website/blog/2019-09-18-version-0.61.md
index c9b0d8c423f..c73ba7969a6 100644
--- a/website/blog/2019-09-18-version-0.61.md
+++ b/website/blog/2019-09-18-version-0.61.md
@@ -43,7 +43,7 @@ Please report any issues with Fast Refresh on GitHub, and we’ll look into them
 ## Other Improvements
 
 - **Fixed use_frameworks! CocoaPods support.** In 0.60 we made some updates to integrate CocoaPods by default. Unfortunately, this broke builds using [use_frameworks!](https://guides.cocoapods.org/syntax/podfile.html#use_frameworks_bang). This is [fixed in 0.61](https://github.com/facebook/react-native/pull/25619), making it easier to integrate React Native into your iOS projects that require building with dynamic frameworks.
-- **Add useWindowDimensions Hook. **This new Hook automatically provides and subscribes to dimension updates, and can be used instead of the Dimensions API in most cases. See [x] for more information.
+- **Add useWindowDimensions Hook.** This new Hook automatically provides and subscribes to dimension updates, and can be used instead of the Dimensions API in most cases.
 - **React was upgraded to 16.9.** This version deprecates old names for the UNSAFE\_ lifecycle methods, contains improvements to `act`, and more. See the [React 16.9 blog post](https://reactjs.org/blog/2019/08/08/react-v16.9.0.html) for an automated migration script and more information.
 
 ## Breaking Changes

From 6b180a4ea6e76cd152609ab2623864231db577e4 Mon Sep 17 00:00:00 2001
From: Rachel Nabors <rnabors@fb.com>
Date: Thu, 19 Sep 2019 18:48:33 +0100
Subject: [PATCH 22/26] Adding DEV and Spectrum to communities footer

---
 website/core/Footer.js | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/website/core/Footer.js b/website/core/Footer.js
index a81fc25b970..efbf77bfb96 100644
--- a/website/core/Footer.js
+++ b/website/core/Footer.js
@@ -47,6 +47,14 @@ class Footer extends React.Component {
             <a href="https://github.com/facebook/react-native/blob/master/CONTRIBUTING.md">
               Contributor Guide
             </a>
+            <a href="https://dev.to/t/reactnative" target="_blank">
+              DEV Community
+            </a>
+            <a
+              href="https://spectrum.chat/react-native?tab=posts"
+              target="_blank">
+              Spectrum Chat
+            </a>
           </div>
           <div>
             <h5>More Resources</h5>

From 4ddf860b62caf8580578c702187b656312fd0cea Mon Sep 17 00:00:00 2001
From: Ricky <rickhanlonii@gmail.com>
Date: Fri, 20 Sep 2019 10:28:07 +0100
Subject: [PATCH 23/26] Only add DEV

---
 website/core/Footer.js | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/core/Footer.js b/website/core/Footer.js
index efbf77bfb96..783c74b6edc 100644
--- a/website/core/Footer.js
+++ b/website/core/Footer.js
@@ -50,11 +50,6 @@ class Footer extends React.Component {
             <a href="https://dev.to/t/reactnative" target="_blank">
               DEV Community
             </a>
-            <a
-              href="https://spectrum.chat/react-native?tab=posts"
-              target="_blank">
-              Spectrum Chat
-            </a>
           </div>
           <div>
             <h5>More Resources</h5>

From 0016e2cdfc7587ef0684eac7f4f5fc9e1cea804f Mon Sep 17 00:00:00 2001
From: Ricky <rickhanlonii@gmail.com>
Date: Fri, 20 Sep 2019 18:04:45 +0100
Subject: [PATCH 24/26] Add changelog link

Co-Authored-By: Lorenzo Sciandra <kelset@users.noreply.github.com>
---
 website/blog/2019-09-18-version-0.61.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/blog/2019-09-18-version-0.61.md b/website/blog/2019-09-18-version-0.61.md
index c73ba7969a6..534e39739a6 100644
--- a/website/blog/2019-09-18-version-0.61.md
+++ b/website/blog/2019-09-18-version-0.61.md
@@ -54,4 +54,4 @@ Please report any issues with Fast Refresh on GitHub, and we’ll look into them
 
 Thanks to all of the contributors that helped make 0.61 possible!
 
-To see all the updates, take a look at the 0.61 changelog.
+To see all the updates, take a look at the [0.61 changelog](https://github.com/react-native-community/releases/blob/master/CHANGELOG.md).

From 42beca1138f37bcd57c37c5cba74b134d7ad9bac Mon Sep 17 00:00:00 2001
From: Ricky <rickhanlonii@gmail.com>
Date: Wed, 25 Sep 2019 14:12:33 +0100
Subject: [PATCH 25/26] Add guide for Fast Refresh (#1282)

* Add guide for Fast Refresh

* Remove URL

* Better wording for "fall", remove bang

* Update debugging.md

Adding a reference here to Fast Refresh. Section still needs intro paragraph. But that seemed tangential to this commit in light of upcoming sectional changes.
---
 docs/debugging.md     |  21 ++----
 docs/fast-refresh.md  |  38 +++++++++++
 website/i18n/en.json  | 145 +++++++++++++++++++++---------------------
 website/sidebars.json |   1 +
 4 files changed, 114 insertions(+), 91 deletions(-)
 create mode 100644 docs/fast-refresh.md

diff --git a/docs/debugging.md b/docs/debugging.md
index 602fe0deb2b..12862d9a224 100644
--- a/docs/debugging.md
+++ b/docs/debugging.md
@@ -3,10 +3,6 @@ id: debugging
 title: Debugging
 ---
 
-## Enabling Keyboard Shortcuts
-
-React Native supports a few keyboard shortcuts in the iOS Simulator. They are described below. To enable them, open the Hardware menu, select Keyboard, and make sure that "Connect Hardware Keyboard" is checked.
-
 ## Accessing the In-App Developer Menu
 
 You can access the developer menu by shaking your device or by selecting "Shake Gesture" inside the Hardware menu in the iOS Simulator. You can also use the `⌘D` keyboard shortcut when your app is running in the iOS Simulator, or `⌘M` when running in an Android emulator on Mac OS and `Ctrl+M` on Windows and Linux. Alternatively for Android, you can run the command `adb shell input keyevent 82` to open the dev menu (82 being the Menu key code).
@@ -15,22 +11,13 @@ You can access the developer menu by shaking your device or by selecting "Shake
 
 > The Developer Menu is disabled in release (production) builds.
 
-## Reloading JavaScript
-
-Instead of recompiling your app every time you make a change, you can reload your app's JavaScript code instantly. To do so, select "Reload" from the Developer Menu. You can also press `⌘R` in the iOS Simulator, or tap `R` twice on Android emulators.
+## Enabling Fast Refresh
 
-### Automatic reloading
+Fast Refresh is a React Native feature that allows you to get near-instant feedback for changes in your React components. While debugging, it can help to have [Fast Refresh](fast-refresh.md) enabled.  Fast Refresh is enabled by default, and you can toggle "Enable Fast Refresh" in the React Native developer menu. When enabled, most of your edits should be visible within a second or two.
 
-You can speed up your development times by having your app reload automatically any time your code changes. Automatic reloading can be enabled by selecting "Enable Live Reload" from the Developer Menu.
-
-You may even go a step further and keep your app running as new versions of your files are injected into the JavaScript bundle automatically by enabling [Hot Reloading](https://facebook.github.io/react-native/blog/2016/03/24/introducing-hot-reloading) from the Developer Menu. This will allow you to persist the app's state through reloads.
-
-> There are some instances where hot reloading cannot be implemented perfectly. If you run into any issues, use a full reload to reset your app.
-
-You will need to rebuild your app for changes to take effect in certain situations:
+## Enabling Keyboard Shortcuts
 
-- You have added new resources to your native app's bundle, such as an image in `Images.xcassets` on iOS or the `res/drawable` folder on Android.
-- You have modified native code (Objective-C/Swift on iOS or Java/C++ on Android).
+React Native supports a few keyboard shortcuts in the iOS Simulator. They are described below. To enable them, open the Hardware menu, select Keyboard, and make sure that "Connect Hardware Keyboard" is checked.
 
 ## In-app Errors and Warnings
 
diff --git a/docs/fast-refresh.md b/docs/fast-refresh.md
new file mode 100644
index 00000000000..79dc1326f89
--- /dev/null
+++ b/docs/fast-refresh.md
@@ -0,0 +1,38 @@
+---
+id: fast-refresh
+title: Fast Refresh
+---
+
+Fast Refresh is a React Native feature that allows you to get near-instant feedback for changes in your React components. Fast Refresh is enabled by default, and you can toggle "Enable Fast Refresh" in the React Native developer menu. With Fast Refresh enabled, most edits should be visible within a second or two.
+
+## How It Works
+
+- If you edit a module that **only exports React component(s)**, Fast Refresh will update the code just for that module, and re-render your component. You can edit anything in that file, including styles, rendering logic, event handlers, or effects.
+- If you edit a module with exports that _aren't_ React components, Fast Refresh will re-run both that module, and the other modules importing it. So if both `Button.js` and `Modal.js` import `Theme.js`, editing `Theme.js` will update both components.
+- Finally, if you **edit a file** that's **imported by modules outside of the React tree**, Fast Refresh **will fall back to doing a full reload**. You might have a file which renders a React component but also exports a value that is imported by a **non-React component**. For example, maybe your component also exports a constant, and a non-React utility module imports it. In that case, consider migrating the query to a separate file and importing it into both files. This will re-enable Fast Refresh to work. Other cases can usually be solved in a similar way.
+
+## Error Resilience
+
+If you make a **syntax error** during a Fast Refresh session, you can fix it and save the file again. The redbox will disappear. Modules with syntax errors are prevented from running, so you won't need to reload the app.
+
+If you make a **runtime error during the module initialization** (for example, typing `Style.create` instead of `StyleSheet.create`), the Fast Refresh session will continue once you fix the error. The redbox will disappear, and the module will be updated.
+
+If you make a mistake that leads to a **runtime error inside your component**, the Fast Refresh session will _also_ continue after you fix the error. In that case, React will remount your application using the updated code.
+
+If you have [error boundaries](https://reactjs.org/docs/error-boundaries.html) in your app (which is a good idea for graceful failures in production), they will retry rendering on the next edit after a redbox. In that sense, having an error boundary can prevent you from always getting kicked out to the root app screen. However, keep in mind that error boundaries shouldn't be _too_ granular. They are used by React in production, and should always be designed intentionally.
+
+## Limitations
+
+Fast Refresh tries to preserve local React state in the component you're editing, but only if it's safe to do so. Here's a few reasons why you might see local state being reset on every edit to a file:
+
+- Local state is not preserved for class components (only function components and Hooks preserve state).
+- The module you're editing might have _other_ exports in addition to a React component.
+- Sometimes, a module would export the result of calling higher-order component like `createNavigationContainer(MyScreen)`. If the returned component is a class, state will be reset.
+
+In longer term, as more of your codebase moves to function components and Hooks, you can expect state to be preserved in more cases.
+
+## Tips
+
+- Fast Refresh preserves React local state in function components (and Hooks) by default.
+- Sometimes you might want to _force_ the state to be reset, and a component to be remounted. For example, this can be handy if you're tweaking an animation that only happens on mount. To do this, you can add `// @refresh reset` anywhere in the file you're editing. This directive is local to the file, and instructs Fast Refresh to remount components defined in that file on every edit.
+- You can put `console.log` or `debugger;` into the components you edit during a Fast Refresh session.
diff --git a/website/i18n/en.json b/website/i18n/en.json
index 3dcd2b62d1f..8a84f330730 100644
--- a/website/i18n/en.json
+++ b/website/i18n/en.json
@@ -101,6 +101,9 @@
       "easing": {
         "title": "Easing"
       },
+      "fast-refresh": {
+        "title": "Fast Refresh"
+      },
       "flatlist": {
         "title": "FlatList"
       },
@@ -353,6 +356,9 @@
       "tutorial": {
         "title": "Learn the Basics"
       },
+      "typescript": {
+        "title": "Using TypeScript with React Native"
+      },
       "upgrading": {
         "title": "Upgrading to new React Native versions"
       },
@@ -2243,6 +2249,9 @@
       "version-0.5/version-0.5-network": {
         "title": "Networking"
       },
+      "version-0.5/version-0.5-optimizing-flatlist-configuration": {
+        "title": "Optimizing Flatlist Configuration"
+      },
       "version-0.5/version-0.5-panresponder": {
         "title": "PanResponder"
       },
@@ -2313,7 +2322,7 @@
         "title": "Share"
       },
       "version-0.5/version-0.5-signed-apk-android": {
-        "title": "Generating Signed APK"
+        "title": "Publishing to Google Play Store"
       },
       "version-0.5/version-0.5-slider": {
         "title": "Slider"
@@ -3083,9 +3092,6 @@
       "version-0.59/version-0.59-image-style-props": {
         "title": "Image Style Props"
       },
-      "version-0.59/version-0.59-images": {
-        "title": "Images"
-      },
       "version-0.59/version-0.59-imagestore": {
         "title": "ImageStore"
       },
@@ -3164,9 +3170,6 @@
       "version-0.6/version-0.6-touchablewithoutfeedback": {
         "title": "TouchableWithoutFeedback"
       },
-      "version-0.60/version-0.60-accessibility": {
-        "title": "Accessibility"
-      },
       "version-0.60/version-0.60-accessibilityinfo": {
         "title": "AccessibilityInfo"
       },
@@ -3179,44 +3182,44 @@
       "version-0.60/version-0.60-alert": {
         "title": "Alert"
       },
+      "version-0.60/version-0.60-alertios": {
+        "title": "AlertIOS"
+      },
       "version-0.60/version-0.60-animated": {
         "title": "Animated"
       },
-      "version-0.60/version-0.60-animations": {
-        "title": "Animations"
-      },
-      "version-0.60/version-0.60-app-extensions": {
-        "title": "App Extensions"
-      },
       "version-0.60/version-0.60-appregistry": {
         "title": "AppRegistry"
       },
       "version-0.60/version-0.60-appstate": {
         "title": "AppState"
       },
+      "version-0.60/version-0.60-asyncstorage": {
+        "title": "AsyncStorage"
+      },
       "version-0.60/version-0.60-backhandler": {
         "title": "BackHandler"
       },
       "version-0.60/version-0.60-button": {
         "title": "Button"
       },
+      "version-0.60/version-0.60-clipboard": {
+        "title": "Clipboard"
+      },
       "version-0.60/version-0.60-communication-android": {
         "title": "Communication between native and React Native"
       },
-      "version-0.60/version-0.60-components-and-apis": {
-        "title": "Components and APIs"
+      "version-0.60/version-0.60-datepickerandroid": {
+        "title": "DatePickerAndroid"
       },
       "version-0.60/version-0.60-datepickerios": {
         "title": "DatePickerIOS"
       },
-      "version-0.60/version-0.60-debugging": {
-        "title": "Debugging"
-      },
       "version-0.60/version-0.60-dimensions": {
         "title": "Dimensions"
       },
-      "version-0.60/version-0.60-direct-manipulation": {
-        "title": "Direct Manipulation"
+      "version-0.60/version-0.60-drawerlayoutandroid": {
+        "title": "DrawerLayoutAndroid"
       },
       "version-0.60/version-0.60-easing": {
         "title": "Easing"
@@ -3224,32 +3227,29 @@
       "version-0.60/version-0.60-flatlist": {
         "title": "FlatList"
       },
-      "version-0.60/version-0.60-flexbox": {
-        "title": "Layout with Flexbox"
-      },
-      "version-0.60/version-0.60-getting-started": {
-        "title": "Getting Started"
-      },
-      "version-0.60/version-0.60-handling-text-input": {
-        "title": "Handling Text Input"
-      },
-      "version-0.60/version-0.60-headless-js-android": {
-        "title": "Headless JS"
-      },
       "version-0.60/version-0.60-hermes": {
         "title": "Using Hermes"
       },
+      "version-0.60/version-0.60-image-style-props": {
+        "title": "Image Style Props"
+      },
       "version-0.60/version-0.60-image": {
         "title": "Image"
       },
+      "version-0.60/version-0.60-imagebackground": {
+        "title": "ImageBackground"
+      },
+      "version-0.60/version-0.60-imageeditor": {
+        "title": "ImageEditor"
+      },
       "version-0.60/version-0.60-imagepickerios": {
         "title": "ImagePickerIOS"
       },
-      "version-0.60/version-0.60-images": {
-        "title": "Images"
+      "version-0.60/version-0.60-inputaccessoryview": {
+        "title": "InputAccessoryView"
       },
-      "version-0.60/version-0.60-javascript-environment": {
-        "title": "JavaScript Environment"
+      "version-0.60/version-0.60-interactionmanager": {
+        "title": "InteractionManager"
       },
       "version-0.60/version-0.60-keyboard": {
         "title": "Keyboard"
@@ -3269,44 +3269,35 @@
       "version-0.60/version-0.60-modal": {
         "title": "Modal"
       },
-      "version-0.60/version-0.60-more-resources": {
-        "title": "More Resources"
-      },
-      "version-0.60/version-0.60-native-components-ios": {
-        "title": "Native UI Components"
-      },
-      "version-0.60/version-0.60-native-modules-android": {
-        "title": "Native Modules"
-      },
-      "version-0.60/version-0.60-navigation": {
-        "title": "Navigating Between Screens"
-      },
-      "version-0.60/version-0.60-optimizing-flatlist-configuration": {
-        "title": "Optimizing Flatlist Configuration"
-      },
       "version-0.60/version-0.60-out-of-tree-platforms": {
         "title": "Out-of-Tree Platforms"
       },
       "version-0.60/version-0.60-panresponder": {
         "title": "PanResponder"
       },
-      "version-0.60/version-0.60-performance": {
-        "title": "Performance"
+      "version-0.60/version-0.60-permissionsandroid": {
+        "title": "PermissionsAndroid"
+      },
+      "version-0.60/version-0.60-picker": {
+        "title": "Picker"
       },
       "version-0.60/version-0.60-pickerios": {
         "title": "PickerIOS"
       },
+      "version-0.60/version-0.60-pixelratio": {
+        "title": "PixelRatio"
+      },
       "version-0.60/version-0.60-progressbarandroid": {
         "title": "ProgressBarAndroid"
       },
+      "version-0.60/version-0.60-progressviewios": {
+        "title": "ProgressViewIOS"
+      },
       "version-0.60/version-0.60-pushnotificationios": {
         "title": "PushNotificationIOS"
       },
-      "version-0.60/version-0.60-removing-default-permissions": {
-        "title": "Removing Default Permissions"
-      },
-      "version-0.60/version-0.60-running-on-simulator-ios": {
-        "title": "Running On Simulator"
+      "version-0.60/version-0.60-refreshcontrol": {
+        "title": "RefreshControl"
       },
       "version-0.60/version-0.60-safeareaview": {
         "title": "SafeAreaView"
@@ -3317,23 +3308,26 @@
       "version-0.60/version-0.60-sectionlist": {
         "title": "SectionList"
       },
+      "version-0.60/version-0.60-segmentedcontrolios": {
+        "title": "SegmentedControlIOS"
+      },
       "version-0.60/version-0.60-settings": {
         "title": "Settings"
       },
-      "version-0.60/version-0.60-signed-apk-android": {
-        "title": "Publishing to Google Play Store"
+      "version-0.60/version-0.60-shadow-props": {
+        "title": "Shadow Props"
+      },
+      "version-0.60/version-0.60-share": {
+        "title": "Share"
       },
       "version-0.60/version-0.60-slider": {
         "title": "Slider"
       },
-      "version-0.60/version-0.60-state": {
-        "title": "State"
-      },
       "version-0.60/version-0.60-statusbar": {
         "title": "StatusBar"
       },
-      "version-0.60/version-0.60-style": {
-        "title": "Style"
+      "version-0.60/version-0.60-statusbarios": {
+        "title": "StatusBarIOS"
       },
       "version-0.60/version-0.60-stylesheet": {
         "title": "StyleSheet"
@@ -3353,8 +3347,11 @@
       "version-0.60/version-0.60-textinput": {
         "title": "TextInput"
       },
-      "version-0.60/version-0.60-timers": {
-        "title": "Timers"
+      "version-0.60/version-0.60-timepickerandroid": {
+        "title": "TimePickerAndroid"
+      },
+      "version-0.60/version-0.60-toastandroid": {
+        "title": "ToastAndroid"
       },
       "version-0.60/version-0.60-toolbarandroid": {
         "title": "ToolbarAndroid"
@@ -3374,14 +3371,11 @@
       "version-0.60/version-0.60-transforms": {
         "title": "Transforms"
       },
-      "version-0.60/version-0.60-troubleshooting": {
-        "title": "Troubleshooting"
-      },
-      "version-0.60/version-0.60-upgrading": {
-        "title": "Upgrading to new React Native versions"
+      "version-0.60/version-0.60-typescript": {
+        "title": "Using TypeScript with React Native"
       },
-      "version-0.60/version-0.60-using-a-scrollview": {
-        "title": "Using a ScrollView"
+      "version-0.60/version-0.60-vibration": {
+        "title": "Vibration"
       },
       "version-0.60/version-0.60-view-style-props": {
         "title": "View Style Props"
@@ -3389,6 +3383,9 @@
       "version-0.60/version-0.60-view": {
         "title": "View"
       },
+      "version-0.60/version-0.60-viewpagerandroid": {
+        "title": "ViewPagerAndroid"
+      },
       "version-0.60/version-0.60-virtualizedlist": {
         "title": "VirtualizedList"
       },
diff --git a/website/sidebars.json b/website/sidebars.json
index 86b071aa38a..69f701d1c04 100644
--- a/website/sidebars.json
+++ b/website/sidebars.json
@@ -16,6 +16,7 @@
       "more-resources"
     ],
     "Guides": [
+      "fast-refresh",
       "components-and-apis",
       "platform-specific-code",
       "navigation",

From 83f7e3d1d4ad2a1f04fb8b42a4ef24e31cd27b4e Mon Sep 17 00:00:00 2001
From: Rachel Nabors <rachelnabors@users.noreply.github.com>
Date: Wed, 25 Sep 2019 15:09:02 +0100
Subject: [PATCH 26/26] Add 0.61 docs (#1287)

---
 website/i18n/en.json                          |   6 +
 .../versioned_docs/version-0.61/debugging.md  | 169 ++++++++++++++++++
 .../version-0.61/fast-refresh.md              |  39 ++++
 .../version-0.61-sidebars.json                | 139 ++++++++++++++
 website/versions.json                         |   1 +
 5 files changed, 354 insertions(+)
 create mode 100644 website/versioned_docs/version-0.61/debugging.md
 create mode 100644 website/versioned_docs/version-0.61/fast-refresh.md
 create mode 100644 website/versioned_sidebars/version-0.61-sidebars.json

diff --git a/website/i18n/en.json b/website/i18n/en.json
index 8a84f330730..65ec2e7c60a 100644
--- a/website/i18n/en.json
+++ b/website/i18n/en.json
@@ -3389,6 +3389,12 @@
       "version-0.60/version-0.60-virtualizedlist": {
         "title": "VirtualizedList"
       },
+      "version-0.61/version-0.61-debugging": {
+        "title": "Debugging"
+      },
+      "version-0.61/version-0.61-fast-refresh": {
+        "title": "Fast Refresh"
+      },
       "version-0.7/version-0.7-pushnotificationios": {
         "title": "PushNotificationIOS"
       },
diff --git a/website/versioned_docs/version-0.61/debugging.md b/website/versioned_docs/version-0.61/debugging.md
new file mode 100644
index 00000000000..ad18313325f
--- /dev/null
+++ b/website/versioned_docs/version-0.61/debugging.md
@@ -0,0 +1,169 @@
+---
+id: version-0.61-debugging
+title: Debugging
+original_id: debugging
+---
+
+## Accessing the In-App Developer Menu
+
+You can access the developer menu by shaking your device or by selecting "Shake Gesture" inside the Hardware menu in the iOS Simulator. You can also use the `⌘D` keyboard shortcut when your app is running in the iOS Simulator, or `⌘M` when running in an Android emulator on Mac OS and `Ctrl+M` on Windows and Linux. Alternatively for Android, you can run the command `adb shell input keyevent 82` to open the dev menu (82 being the Menu key code).
+
+![](/react-native/docs/assets/DeveloperMenu.png)
+
+> The Developer Menu is disabled in release (production) builds.
+
+## Enabling Fast Refresh
+
+Fast Refresh is a React Native feature that allows you to get near-instant feedback for changes in your React components. While debugging, it can help to have [Fast Refresh](fast-refresh.md) enabled. Fast Refresh is enabled by default, and you can toggle "Enable Fast Refresh" in the React Native developer menu. When enabled, most of your edits should be visible within a second or two.
+
+## Enabling Keyboard Shortcuts
+
+React Native supports a few keyboard shortcuts in the iOS Simulator. They are described below. To enable them, open the Hardware menu, select Keyboard, and make sure that "Connect Hardware Keyboard" is checked.
+
+## In-app Errors and Warnings
+
+Errors and warnings are displayed inside your app in development builds.
+
+### Errors
+
+In-app errors are displayed in a full screen alert with a red background inside your app. This screen is known as a RedBox. You can use `console.error()` to manually trigger one.
+
+### Warnings
+
+Warnings will be displayed on screen with a yellow background. These alerts are known as YellowBoxes. Click on the alerts to show more information or to dismiss them.
+
+As with a RedBox, you can use `console.warn()` to trigger a YellowBox.
+
+YellowBoxes can be disabled during development by using `console.disableYellowBox = true;`. Specific warnings can be ignored programmatically by setting an array of prefixes that should be ignored:
+
+```jsx
+import {YellowBox} from 'react-native';
+YellowBox.ignoreWarnings(['Warning: ...']);
+```
+
+In CI/Xcode, YellowBoxes can also be disabled by setting the `IS_TESTING` environment variable.
+
+> RedBoxes and YellowBoxes are automatically disabled in release (production) builds.
+
+## Chrome Developer Tools
+
+To debug the JavaScript code in Chrome, select "Debug JS Remotely" from the Developer Menu. This will open a new tab at [http://localhost:8081/debugger-ui](http://localhost:8081/debugger-ui).
+
+Select `Tools → Developer Tools` from the Chrome Menu to open the [Developer Tools](https://developer.chrome.com/devtools). You may also access the DevTools using keyboard shortcuts (`⌘⌥I` on macOS, `Ctrl` `Shift` `I` on Windows). You may also want to enable [Pause On Caught Exceptions](http://stackoverflow.com/questions/2233339/javascript-is-there-a-way-to-get-chrome-to-break-on-all-errors/17324511#17324511) for a better debugging experience.
+
+> Note: the React Developer Tools Chrome extension does not work with React Native, but you can use its standalone version instead. Read [this section](debugging.md#react-developer-tools) to learn how.
+
+### Debugging using a custom JavaScript debugger
+
+To use a custom JavaScript debugger in place of Chrome Developer Tools, set the `REACT_DEBUGGER` environment variable to a command that will start your custom debugger. You can then select "Debug JS Remotely" from the Developer Menu to start debugging.
+
+The debugger will receive a list of all project roots, separated by a space. For example, if you set `REACT_DEBUGGER="node /path/to/launchDebugger.js --port 2345 --type ReactNative"`, then the command `node /path/to/launchDebugger.js --port 2345 --type ReactNative /path/to/reactNative/app` will be used to start your debugger.
+
+> Custom debugger commands executed this way should be short-lived processes, and they shouldn't produce more than 200 kilobytes of output.
+
+## Safari Developer Tools
+
+You can use Safari to debug the iOS version of your app without having to enable "Debug JS Remotely".
+
+- Enable Develop menu in Safari: `Preferences → Advanced → Select "Show Develop menu in menu bar"`
+- Select your app's JSContext: `Develop → Simulator → JSContext`
+- Safari's Web Inspector should open which has a Console and a Debugger
+
+However, there are some disadvantages:
+
+1. No sourcemaps when debugging
+2. Every time the app is reloaded (using live reload, or by manually reloading), a new JSContext is created. Choosing "Automatically Show Web Inspectors for JSContexts" saves you from having to select the latest JSContext manually.
+
+## React Developer Tools
+
+You can use [the standalone version of React Developer Tools](https://github.com/facebook/react/tree/master/packages/react-devtools) to debug the React component hierarchy. To use it, install the `react-devtools` package globally:
+
+```
+npm install -g react-devtools
+```
+
+Now run `react-devtools` from the terminal to launch the standalone DevTools app:
+
+```
+react-devtools
+```
+
+![React DevTools](/react-native/docs/assets/ReactDevTools.png)
+
+It should connect to your simulator within a few seconds.
+
+> Note: if you prefer to avoid global installations, you can add `react-devtools` as a project dependency. Add the `react-devtools` package to your project using `npm install --save-dev react-devtools`, then add `"react-devtools": "react-devtools"` to the `scripts` section in your `package.json`, and then run `npm run react-devtools` from your project folder to open the DevTools.
+
+### Integration with React Native Inspector
+
+Open the in-app developer menu and choose "Toggle Inspector". It will bring up an overlay that lets you tap on any UI element and see information about it:
+
+![React Native Inspector](/react-native/docs/assets/Inspector.gif)
+
+However, when `react-devtools` is running, Inspector will enter a special collapsed mode, and instead use the DevTools as primary UI. In this mode, clicking on something in the simulator will bring up the relevant components in the DevTools:
+
+![React DevTools Inspector Integration](/react-native/docs/assets/ReactDevToolsInspector.gif)
+
+You can choose "Toggle Inspector" in the same menu to exit this mode.
+
+### Inspecting Component Instances
+
+When debugging JavaScript in Chrome, you can inspect the props and state of the React components in the browser console.
+
+First, follow the instructions for debugging in Chrome to open the Chrome console.
+
+Make sure that the dropdown in the top left corner of the Chrome console says `debuggerWorker.js`. **This step is essential.**
+
+Then select a React component in React DevTools. There is a search box at the top that helps you find one by name. As soon as you select it, it will be available as `$r` in the Chrome console, letting you inspect its props, state, and instance properties.
+
+![React DevTools Chrome Console Integration](/react-native/docs/assets/ReactDevToolsDollarR.gif)
+
+## Performance Monitor
+
+You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
+
+<hr style="margin-top:25px; margin-bottom:25px;"/>
+
+# Debugging in Ejected Apps
+
+<div class="banner-crna-ejected" style="margin-top:25px">
+  <h3>Projects with Native Code Only</h3>
+  <p>
+    The remainder of this guide only applies to projects made with <code>react-native init</code>
+    or to those made with <code>expo init</code> or Create React Native App which have since ejected. For
+    more information about ejecting, please see
+    the <a href="https://github.com/react-community/create-react-native-app/blob/master/EJECTING.md" target="_blank">guide</a> on
+    the Create React Native App repository.
+  </p>
+</div>
+
+## Accessing console logs
+
+You can display the console logs for an iOS or Android app by using the following commands in a terminal while the app is running:
+
+```
+$ react-native log-ios
+$ react-native log-android
+```
+
+You may also access these through `Debug → Open System Log...` in the iOS Simulator or by running `adb logcat *:S ReactNative:V ReactNativeJS:V` in a terminal while an Android app is running on a device or emulator.
+
+> If you're using Create React Native App or Expo CLI, console logs already appear in the same terminal output as the packager.
+
+## Debugging on a device with Chrome Developer Tools
+
+> If you're using Create React Native App or Expo CLI, this is configured for you already.
+
+On iOS devices, open the file [`RCTWebSocketExecutor.m`](https://github.com/facebook/react-native/blob/master/Libraries/WebSocket/RCTWebSocketExecutor.m) and change "localhost" to the IP address of your computer, then select "Debug JS Remotely" from the Developer Menu.
+
+On Android 5.0+ devices connected via USB, you can use the [`adb` command line tool](http://developer.android.com/tools/help/adb.html) to setup port forwarding from the device to your computer:
+
+`adb reverse tcp:8081 tcp:8081`
+
+Alternatively, select "Dev Settings" from the Developer Menu, then update the "Debug server host for device" setting to match the IP address of your computer.
+
+> If you run into any issues, it may be possible that one of your Chrome extensions is interacting in unexpected ways with the debugger. Try disabling all of your extensions and re-enabling them one-by-one until you find the problematic extension.
+
+## Debugging native code
+
+When working with native code, such as when writing native modules, you can launch the app from Android Studio or Xcode and take advantage of the native debugging features (setting up breakpoints, etc.) as you would in case of building a standard native app.
diff --git a/website/versioned_docs/version-0.61/fast-refresh.md b/website/versioned_docs/version-0.61/fast-refresh.md
new file mode 100644
index 00000000000..f986938d74f
--- /dev/null
+++ b/website/versioned_docs/version-0.61/fast-refresh.md
@@ -0,0 +1,39 @@
+---
+id: version-0.61-fast-refresh
+title: Fast Refresh
+original_id: fast-refresh
+---
+
+Fast Refresh is a React Native feature that allows you to get near-instant feedback for changes in your React components. Fast Refresh is enabled by default, and you can toggle "Enable Fast Refresh" in the React Native developer menu. With Fast Refresh enabled, most edits should be visible within a second or two.
+
+## How It Works
+
+- If you edit a module that **only exports React component(s)**, Fast Refresh will update the code just for that module, and re-render your component. You can edit anything in that file, including styles, rendering logic, event handlers, or effects.
+- If you edit a module with exports that _aren't_ React components, Fast Refresh will re-run both that module, and the other modules importing it. So if both `Button.js` and `Modal.js` import `Theme.js`, editing `Theme.js` will update both components.
+- Finally, if you **edit a file** that's **imported by modules outside of the React tree**, Fast Refresh **will fall back to doing a full reload**. You might have a file which renders a React component but also exports a value that is imported by a **non-React component**. For example, maybe your component also exports a constant, and a non-React utility module imports it. In that case, consider migrating the query to a separate file and importing it into both files. This will re-enable Fast Refresh to work. Other cases can usually be solved in a similar way.
+
+## Error Resilience
+
+If you make a **syntax error** during a Fast Refresh session, you can fix it and save the file again. The redbox will disappear. Modules with syntax errors are prevented from running, so you won't need to reload the app.
+
+If you make a **runtime error during the module initialization** (for example, typing `Style.create` instead of `StyleSheet.create`), the Fast Refresh session will continue once you fix the error. The redbox will disappear, and the module will be updated.
+
+If you make a mistake that leads to a **runtime error inside your component**, the Fast Refresh session will _also_ continue after you fix the error. In that case, React will remount your application using the updated code.
+
+If you have [error boundaries](https://reactjs.org/docs/error-boundaries.html) in your app (which is a good idea for graceful failures in production), they will retry rendering on the next edit after a redbox. In that sense, having an error boundary can prevent you from always getting kicked out to the root app screen. However, keep in mind that error boundaries shouldn't be _too_ granular. They are used by React in production, and should always be designed intentionally.
+
+## Limitations
+
+Fast Refresh tries to preserve local React state in the component you're editing, but only if it's safe to do so. Here's a few reasons why you might see local state being reset on every edit to a file:
+
+- Local state is not preserved for class components (only function components and Hooks preserve state).
+- The module you're editing might have _other_ exports in addition to a React component.
+- Sometimes, a module would export the result of calling higher-order component like `createNavigationContainer(MyScreen)`. If the returned component is a class, state will be reset.
+
+In longer term, as more of your codebase moves to function components and Hooks, you can expect state to be preserved in more cases.
+
+## Tips
+
+- Fast Refresh preserves React local state in function components (and Hooks) by default.
+- Sometimes you might want to _force_ the state to be reset, and a component to be remounted. For example, this can be handy if you're tweaking an animation that only happens on mount. To do this, you can add `// @refresh reset` anywhere in the file you're editing. This directive is local to the file, and instructs Fast Refresh to remount components defined in that file on every edit.
+- You can put `console.log` or `debugger;` into the components you edit during a Fast Refresh session.
diff --git a/website/versioned_sidebars/version-0.61-sidebars.json b/website/versioned_sidebars/version-0.61-sidebars.json
new file mode 100644
index 00000000000..7cb623a90a5
--- /dev/null
+++ b/website/versioned_sidebars/version-0.61-sidebars.json
@@ -0,0 +1,139 @@
+{
+  "version-0.61-docs": {
+    "The Basics": [
+      "version-0.61-getting-started",
+      "version-0.61-tutorial",
+      "version-0.61-props",
+      "version-0.61-state",
+      "version-0.61-style",
+      "version-0.61-height-and-width",
+      "version-0.61-flexbox",
+      "version-0.61-handling-text-input",
+      "version-0.61-handling-touches",
+      "version-0.61-using-a-scrollview",
+      "version-0.61-using-a-listview",
+      "version-0.61-network",
+      "version-0.61-more-resources"
+    ],
+    "Guides": [
+      "version-0.61-fast-refresh",
+      "version-0.61-components-and-apis",
+      "version-0.61-platform-specific-code",
+      "version-0.61-navigation",
+      "version-0.61-images",
+      "version-0.61-animations",
+      "version-0.61-accessibility",
+      "version-0.61-improvingux",
+      "version-0.61-optimizing-flatlist-configuration",
+      "version-0.61-timers",
+      "version-0.61-debugging",
+      "version-0.61-performance",
+      "version-0.61-gesture-responder-system",
+      "version-0.61-javascript-environment",
+      "version-0.61-typescript",
+      "version-0.61-direct-manipulation",
+      "version-0.61-colors",
+      "version-0.61-integration-with-existing-apps",
+      "version-0.61-building-for-apple-tv",
+      "version-0.61-running-on-device",
+      "version-0.61-upgrading",
+      "version-0.61-troubleshooting",
+      "version-0.61-native-modules-setup",
+      "version-0.61-out-of-tree-platforms"
+    ],
+    "Guides (iOS)": [
+      "version-0.61-native-modules-ios",
+      "version-0.61-native-components-ios",
+      "version-0.61-linking-libraries-ios",
+      "version-0.61-running-on-simulator-ios",
+      "version-0.61-communication-ios",
+      "version-0.61-app-extensions"
+    ],
+    "Guides (Android)": [
+      "version-0.61-native-modules-android",
+      "version-0.61-native-components-android",
+      "version-0.61-headless-js-android",
+      "version-0.61-signed-apk-android",
+      "version-0.61-removing-default-permissions",
+      "version-0.61-hermes"
+    ]
+  },
+  "version-0.61-api": {
+    "Components": [
+      "version-0.61-activityindicator",
+      "version-0.61-button",
+      "version-0.61-datepickerios",
+      "version-0.61-drawerlayoutandroid",
+      "version-0.61-flatlist",
+      "version-0.61-image",
+      "version-0.61-imagebackground",
+      "version-0.61-inputaccessoryview",
+      "version-0.61-keyboardavoidingview",
+      "version-0.61-maskedviewios",
+      "version-0.61-modal",
+      "version-0.61-picker",
+      "version-0.61-pickerios",
+      "version-0.61-progressbarandroid",
+      "version-0.61-progressviewios",
+      "version-0.61-refreshcontrol",
+      "version-0.61-safeareaview",
+      "version-0.61-scrollview",
+      "version-0.61-sectionlist",
+      "version-0.61-segmentedcontrolios",
+      "version-0.61-slider",
+      "version-0.61-statusbar",
+      "version-0.61-switch",
+      "version-0.61-tabbarios",
+      "version-0.61-tabbarios-item",
+      "version-0.61-text",
+      "version-0.61-textinput",
+      "version-0.61-toolbarandroid",
+      "version-0.61-touchablehighlight",
+      "version-0.61-touchablenativefeedback",
+      "version-0.61-touchableopacity",
+      "version-0.61-touchablewithoutfeedback",
+      "version-0.61-view",
+      "version-0.61-viewpagerandroid",
+      "version-0.61-virtualizedlist"
+    ],
+    "APIs": [
+      "version-0.61-accessibilityinfo",
+      "version-0.61-actionsheetios",
+      "version-0.61-alert",
+      "version-0.61-alertios",
+      "version-0.61-animated",
+      "version-0.61-appregistry",
+      "version-0.61-appstate",
+      "version-0.61-asyncstorage",
+      "version-0.61-backhandler",
+      "version-0.61-clipboard",
+      "version-0.61-datepickerandroid",
+      "version-0.61-dimensions",
+      "version-0.61-easing",
+      "version-0.61-imageeditor",
+      "version-0.61-imagepickerios",
+      "version-0.61-image-style-props",
+      "version-0.61-interactionmanager",
+      "version-0.61-keyboard",
+      "version-0.61-layout-props",
+      "version-0.61-layoutanimation",
+      "version-0.61-linking",
+      "version-0.61-panresponder",
+      "version-0.61-permissionsandroid",
+      "version-0.61-pixelratio",
+      "version-0.61-pushnotificationios",
+      "version-0.61-settings",
+      "version-0.61-shadow-props",
+      "version-0.61-share",
+      "version-0.61-statusbarios",
+      "version-0.61-stylesheet",
+      "version-0.61-systrace",
+      "version-0.61-text-style-props",
+      "version-0.61-timepickerandroid",
+      "version-0.61-toastandroid",
+      "version-0.61-transforms",
+      "version-0.61-vibration",
+      "version-0.61-view-style-props"
+    ]
+  }
+}
diff --git a/website/versions.json b/website/versions.json
index 4b2e05a6182..88a1bfd1081 100644
--- a/website/versions.json
+++ b/website/versions.json
@@ -1,4 +1,5 @@
 [
+  "0.61",
   "0.60",
   "0.59",
   "0.58",