diff --git a/website/src/pages/versions.js b/website/src/pages/versions.js
index ad2f2485e74..bfdfece266d 100644
--- a/website/src/pages/versions.js
+++ b/website/src/pages/versions.js
@@ -7,11 +7,12 @@
import React from 'react';
import Layout from '@theme/Layout';
-
import useBaseUrl from '@docusaurus/useBaseUrl';
const versions = require('../../versions.json');
+// The versionsArchived mapping is a custom feature, NOT a Docusaurus feature
+const versionsArchived = require('../../versionsArchived.json');
-const VersionItem = ({version, currentVersion}) => {
+const VersionItem = ({version, archivedDocumentationUrl, currentVersion}) => {
const versionName = version === 'next' ? 'Master' : version;
const isCurrentVersion = currentVersion === version;
@@ -19,14 +20,13 @@ const VersionItem = ({version, currentVersion}) => {
const isRC = version.toUpperCase().indexOf('-RC') !== -1;
const latestMajorVersion = versions[0].toUpperCase().replace('-RC', '');
- const documentationLink = (
-
- Documentation
-
+
+ const documentationUrl = useBaseUrl(
+ archivedDocumentationUrl ??
+ `/docs/${isCurrentVersion ? '' : version + '/'}getting-started`
);
+ const documentationLink = Documentation ;
+
let releaseNotesURL = 'https://github.com/facebook/react-native/releases';
let releaseNotesTitle = 'Changelog';
if (isNext) {
@@ -125,6 +125,20 @@ const Versions = () => {
Archived versions
+
+
+ {Object.entries(versionsArchived).map(
+ ([version, archivedDocumentationUrl]) => (
+
+
The documentation for versions below 0.60 can be found on
the separate website called{' '}
diff --git a/website/src/theme/NavbarItem/DocsVersionDropdownNavbarItem.js b/website/src/theme/NavbarItem/DocsVersionDropdownNavbarItem.js
index a12269bf63d..868b8bd7ef0 100644
--- a/website/src/theme/NavbarItem/DocsVersionDropdownNavbarItem.js
+++ b/website/src/theme/NavbarItem/DocsVersionDropdownNavbarItem.js
@@ -6,105 +6,15 @@
*/
import React from 'react';
-import DefaultNavbarItem from '@theme/NavbarItem/DefaultNavbarItem';
-import DropdownNavbarItem from '@theme/NavbarItem/DropdownNavbarItem';
-import {
- useVersions,
- useLatestVersion,
- useActiveDocContext,
-} from '@docusaurus/plugin-content-docs/client';
-import {useDocsPreferredVersion} from '@docusaurus/theme-common';
-import {useDocsVersionCandidates} from '@docusaurus/theme-common/internal';
-import {translate} from '@docusaurus/Translate';
-import {useLocation} from '@docusaurus/router';
-
-const getVersionMainDoc = version =>
- version.docs.find(doc => doc.id === version.mainDocId);
-export default function DocsVersionDropdownNavbarItem({
- mobile,
- docsPluginId,
- dropdownActiveClassDisabled,
- dropdownItemsBefore,
- dropdownItemsAfter,
- ...props
-}) {
- const {search, hash} = useLocation();
- const activeDocContext = useActiveDocContext(docsPluginId);
- const versions = useVersions(docsPluginId);
- const latestVersion = useLatestVersion(docsPluginId);
- const {preferredVersion, savePreferredVersionName} =
- useDocsPreferredVersion(docsPluginId);
+import DocsVersionDropdownNavbarItem from '@theme-original/NavbarItem/DocsVersionDropdownNavbarItem';
+import {useActiveDocContext} from '@docusaurus/plugin-content-docs/client';
+export default function DocsVersionDropdownNavbarItemWrapper(props) {
// (CUSTOM) Hide version dropdown on non-versioned pages
+ const activeDocContext = useActiveDocContext(props.docsPluginId);
if (!activeDocContext.activeDoc) {
return null;
}
- // (CUSTOM) Show only `next` and last 5 versions in the dropdown
- const reducedVersions = versions.slice(0, 6);
-
- const versionLinks = reducedVersions.map(version => {
- // We try to link to the same doc, in another version
- // When not possible, fallback to the "main doc" of the version
- const versionDoc =
- activeDocContext?.alternateDocVersions[version.name] ??
- getVersionMainDoc(version);
- return {
- label: version.label,
- // preserve ?search#hash suffix on version switches
- to: `${versionDoc.path}${search}${hash}`,
- isActive: () => version === activeDocContext?.activeVersion,
- onClick: () => savePreferredVersionName(version.name),
- };
- });
-
- const items = [
- ...dropdownItemsBefore,
- ...versionLinks,
- ...dropdownItemsAfter,
- ];
-
- const dropdownVersion = useDocsVersionCandidates(docsPluginId)[0];
-
- // Mobile dropdown is handled a bit differently
- const dropdownLabel =
- mobile && items.length > 1
- ? translate({
- id: 'theme.navbar.mobileVersionsDropdown.label',
- message: 'Versions',
- description:
- 'The label for the navbar versions dropdown on mobile view',
- })
- : dropdownVersion.label;
- const dropdownTo =
- mobile && items.length > 1
- ? undefined
- : getVersionMainDoc(dropdownVersion).path;
-
- // We don't want to render a version dropdown with 0 or 1 item. If we build
- // the site with a single docs version (onlyIncludeVersions: ['1.0.0']),
- // We'd rather render a button instead of a dropdown
-
- if (items.length <= 1) {
- return (
- false : undefined}
- />
- );
- }
-
- return (
- false : undefined}
- />
- );
+ return Node
-
-Follow the [installation instructions for your Linux distribution](https://nodejs.org/en/download/package-manager/) to install Node 10 or newer.
-
-Java Development Kit
-
-React Native requires at least the 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 14](https://www.oracle.com/java/technologies/javase-jdk14-downloads.html) if desired.
-
-Android development environment
-
-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.
-
-1. Install Android Studio
-
-[Download and install Android Studio](https://developer.android.com/studio/index.html). While on Android Studio installation wizard, make sure the boxes next to all of the following items are checked:
-
-- `Android SDK`
-- `Android SDK Platform`
-- `Android Virtual Device`
-
-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.
-
-2. Install the Android SDK
-
-Android Studio installs the latest Android SDK by default. Building a React Native app with native code, however, requires the `Android 10 (Q)` SDK in particular. Additional Android SDKs can be installed through the SDK Manager in Android Studio.
-
-To do that, open Android Studio, click on "Configure" button and select "SDK Manager".
-
-> 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 10 (Q)` entry, then make sure the following items are checked:
-
-- `Android SDK Platform 29`
-- `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 `29.0.2` is selected.
-
-Finally, click "Apply" to download and install the Android SDK and related build tools.
-
-3. Configure the ANDROID_HOME environment variable
-
-The React Native tools require some environment variables to be set up in order to build apps with native code.
-
-Add the following lines to your `$HOME/.bash_profile` or `$HOME/.bashrc` (if you are using `zsh` then `~/.zprofile` or `~/.zshrc`) config file:
-
-```shell
-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
-```
-
-> `.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` for `bash` or `source $HOME/.zprofile` to load the config into your current shell. Verify that ANDROID_HOME has been set by running `echo $ANDROID_HOME` and the appropriate directories have 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**.
-
-Watchman
-
-Follow the [Watchman installation guide](https://facebook.github.io/watchman/docs/install/#buildinstall) to compile and install Watchman from source.
-
-> [Watchman](https://facebook.github.io/watchman/docs/install/) 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).
-
-React Native Command Line Interface
-
-React Native has a built-in command line interface. Rather than install and manage a specific version of the CLI globally, we recommend you access the current version at runtime using `npx`, which ships with Node.js. With `npx react-native `, the current stable version of the CLI will be downloaded and executed at the time the command is run.
-
-Creating a new application
-
-> If you previously installed a global `react-native-cli` package, please remove it as it may cause unexpected issues.
-
-React Native has a built-in command line interface, which you can use to generate a new project. You can access it without installing anything globally using `npx`, which ships with Node.js. Let's create a new React Native project called "AwesomeProject":
-
-```shell
-npx react-native init AwesomeProject
-```
-
-This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Expo, 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 or template
-
-If you want to start a new project with a specific React Native version, you can use the `--version` argument:
-
-```shell
-npx react-native init AwesomeProject --version X.XX.X
-```
-
-You can also start a project with a custom React Native template, like TypeScript, with `--template` argument:
-
-```shell
-npx react-native init AwesomeTSProject --template react-native-template-typescript
-```
-
-Preparing the Android device
-
-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
-
-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
-
-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:
-
-
-
-If you have recently 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 **Q** API Level 29 image.
-
-> 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.
-
-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.
-
-Running your React Native application
-
-Step 1: Start Metro
-
-First, you will need to start Metro, the JavaScript bundler that ships with React Native. Metro "takes in an entry file and various options, and returns a single JavaScript file that includes all your code and its dependencies."—[Metro Docs](https://facebook.github.io/metro/docs/concepts)
-
-To start Metro, run `npx react-native start` inside your React Native project folder:
-
-```shell
-npx react-native start
-```
-
-`react-native start` starts Metro Bundler.
-
-> If you use the Yarn package manager, you can use `yarn` instead of `npx` when running React Native commands inside an existing project.
-
-> If you're familiar with web development, Metro is a lot like webpack—for React Native apps. Unlike Kotlin or Java, JavaScript isn't compiled—and neither is React Native. Bundling isn't the same as compiling, but it can help improve startup performance and translate some platform-specific JavaScript into more JavaScript.
-
-Step 2: Start your application
-
-Let Metro Bundler run in its own terminal. Open a new terminal inside your React Native project folder. Run the following:
-
-```shell
-npx react-native run-android
-```
-
-If everything is set up correctly, you should see your new app running in your Android emulator shortly.
-
-`npx react-native run-android` is 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.
-
-Modifying your app
-
-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!
-
-That's it!
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-Now what?
-
-- 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, check out the [Introduction to React Native](getting-started).
diff --git a/website/versioned_docs/version-0.60/_getting-started-macos-android.md b/website/versioned_docs/version-0.60/_getting-started-macos-android.md
deleted file mode 100644
index a435135dd14..00000000000
--- a/website/versioned_docs/version-0.60/_getting-started-macos-android.md
+++ /dev/null
@@ -1,191 +0,0 @@
-## Installing dependencies
-
-You will need Node, Watchman, the React Native command line interface, a JDK, and Android Studio.
-
-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.
-
-Node & Watchman
-
-We recommend installing Node and Watchman using [Homebrew](http://brew.sh/). Run the following commands in a Terminal after installing Homebrew:
-
-```shell
-brew install node
-brew install watchman
-```
-
-If you have already installed Node on your system, make sure it is Node 10 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.
-
-Java Development Kit
-
-We recommend installing JDK using [Homebrew](http://brew.sh/). Run the following commands in a Terminal after installing Homebrew:
-
-```shell
-brew install --cask adoptopenjdk/openjdk/adoptopenjdk8
-```
-
-If you have already installed JDK on your system, make sure it is JDK 8 or newer.
-
-Android development environment
-
-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.
-
-1. Install Android Studio
-
-[Download and install Android Studio](https://developer.android.com/studio/index.html). While on Android Studio installation wizard, make sure the boxes next to all of the following items are checked:
-
-- `Android SDK`
-- `Android SDK Platform`
-- `Android Virtual Device`
-- If you are not already using Hyper-V: `Performance (Intel ® HAXM)` ([See here for AMD or Hyper-V](https://android-developers.googleblog.com/2018/07/android-emulator-amd-processor-hyper-v.html))
-
-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.
-
-2. Install the Android SDK
-
-Android Studio installs the latest Android SDK by default. Building a React Native app with native code, however, requires the `Android 10 (Q)` SDK in particular. Additional Android SDKs can be installed through the SDK Manager in Android Studio.
-
-To do that, open Android Studio, click on "More Actions" button and select "SDK Manager".
-
-
-
-> 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 10 (Q)` entry, then make sure the following items are checked:
-
-- `Android SDK Platform 29`
-- `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 `29.0.2` is selected.
-
-Finally, click "Apply" to download and install the Android SDK and related build tools.
-
-3. Configure the ANDROID_HOME environment variable
-
-The React Native tools require some environment variables to be set up in order to build apps with native code.
-
-Add the following lines to your `$HOME/.bash_profile` or `$HOME/.bashrc` (if you are using `zsh` then `~/.zprofile` or `~/.zshrc`) config file:
-
-```shell
-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
-```
-
-> `.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` for `bash` or `source $HOME/.zprofile` to load the config into your current shell. Verify that ANDROID_HOME has been set by running `echo $ANDROID_HOME` and the appropriate directories have 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**.
-
-React Native Command Line Interface
-
-React Native has a built-in command line interface. Rather than install and manage a specific version of the CLI globally, we recommend you access the current version at runtime using `npx`, which ships with Node.js. With `npx react-native `, the current stable version of the CLI will be downloaded and executed at the time the command is run.
-
-Creating a new application
-
-> If you previously installed a global `react-native-cli` package, please remove it as it may cause unexpected issues.
-
-React Native has a built-in command line interface, which you can use to generate a new project. You can access it without installing anything globally using `npx`, which ships with Node.js. Let's create a new React Native project called "AwesomeProject":
-
-```shell
-npx react-native init AwesomeProject
-```
-
-This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Expo, 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 or template
-
-If you want to start a new project with a specific React Native version, you can use the `--version` argument:
-
-```shell
-npx react-native init AwesomeProject --version X.XX.X
-```
-
-You can also start a project with a custom React Native template, like TypeScript, with `--template` argument:
-
-```shell
-npx react-native init AwesomeTSProject --template react-native-template-typescript
-```
-
-Preparing the Android device
-
-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
-
-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
-
-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:
-
-
-
-If you have recently 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 **Q** API Level 29 image.
-
-> 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.
-
-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.
-
-Running your React Native application
-
-Step 1: Start Metro
-
-First, you will need to start Metro, the JavaScript bundler that ships with React Native. Metro "takes in an entry file and various options, and returns a single JavaScript file that includes all your code and its dependencies."—[Metro Docs](https://facebook.github.io/metro/docs/concepts)
-
-To start Metro, run `npx react-native start` inside your React Native project folder:
-
-```shell
-npx react-native start
-```
-
-`react-native start` starts Metro Bundler.
-
-> If you use the Yarn package manager, you can use `yarn` instead of `npx` when running React Native commands inside an existing project.
-
-> If you're familiar with web development, Metro is a lot like webpack—for React Native apps. Unlike Kotlin or Java, JavaScript isn't compiled—and neither is React Native. Bundling isn't the same as compiling, but it can help improve startup performance and translate some platform-specific JavaScript into more JavaScript.
-
-Step 2: Start your application
-
-Let Metro Bundler run in its own terminal. Open a new terminal inside your React Native project folder. Run the following:
-
-```shell
-npx react-native run-android
-```
-
-If everything is set up correctly, you should see your new app running in your Android emulator shortly.
-
-
-
-`npx react-native run-android` is 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.
-
-Modifying your app
-
-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 (`⌘M`) to see your changes!
-
-That's it!
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-Now what?
-
-- 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, check out the [Introduction to React Native](getting-started).
diff --git a/website/versioned_docs/version-0.60/_getting-started-macos-ios.md b/website/versioned_docs/version-0.60/_getting-started-macos-ios.md
deleted file mode 100644
index eba4bed9c53..00000000000
--- a/website/versioned_docs/version-0.60/_getting-started-macos-ios.md
+++ /dev/null
@@ -1,135 +0,0 @@
-## Installing dependencies
-
-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.
-
-### Node & Watchman
-
-We recommend installing Node and Watchman using [Homebrew](http://brew.sh/). Run the following commands in a Terminal after installing Homebrew:
-
-```shell
-brew install node
-brew install watchman
-```
-
-If you have already installed Node on your system, make sure it is Node 10 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.
-
-### Xcode & CocoaPods
-
-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
-
-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.
-
-
-
-#### Installing an iOS Simulator in Xcode
-
-To install a simulator, open Xcode > Preferences... and select the Components tab. Select a simulator with the corresponding version of iOS you wish to use.
-
-#### CocoaPods
-
-[CocoaPods](https://cocoapods.org/) is built with Ruby and it will be installable with the default Ruby available on macOS. You can use a Ruby Version manager, however we recommend that you use the standard Ruby available on macOS unless you know what you're doing.
-
-Using the default Ruby install will require you to use `sudo` when installing gems. (This is only an issue for the duration of the gem installation, though.)
-
-```shell
-sudo gem install cocoapods
-```
-
-For more information, please visit [CocoaPods Getting Started guide](https://guides.cocoapods.org/using/getting-started.html).
-
-### React Native Command Line Interface
-
-React Native has a built-in command line interface. Rather than install and manage a specific version of the CLI globally, we recommend you access the current version at runtime using `npx`, which ships with Node.js. With `npx react-native `, the current stable version of the CLI will be downloaded and executed at the time the command is run.
-
-## Creating a new application
-
-> If you previously installed a global `react-native-cli` package, please remove it as it may cause unexpected issues.
-
-You can use React Native's built-in command line interface to generate a new project. Let's create a new React Native project called "AwesomeProject":
-
-```shell
-npx react-native init AwesomeProject
-```
-
-This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Expo, 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 or template
-
-If you want to start a new project with a specific React Native version, you can use the `--version` argument:
-
-```shell
-npx react-native init AwesomeProject --version X.XX.X
-```
-
-You can also start a project with a custom React Native template, like TypeScript, with `--template` argument:
-
-```shell
-npx react-native init AwesomeTSProject --template react-native-template-typescript
-```
-
-> **Note** If the above command is failing, you may have old version of `react-native` or `react-native-cli` installed globally on your pc. Try uninstalling the cli and run the cli using `npx`.
-
-## Running your React Native application
-
-### Step 1: Start Metro
-
-First, you will need to start Metro, the JavaScript bundler that ships with React Native. Metro "takes in an entry file and various options, and returns a single JavaScript file that includes all your code and its dependencies."—[Metro Docs](https://facebook.github.io/metro/docs/concepts)
-
-To start Metro, run `npx react-native start` inside your React Native project folder:
-
-```shell
-npx react-native start
-```
-
-`react-native start` starts Metro Bundler.
-
-> If you use the Yarn package manager, you can use `yarn` instead of `npx` when running React Native commands inside an existing project.
-
-> If you're familiar with web development, Metro is a lot like webpack—for React Native apps. Unlike Kotlin or Java, JavaScript isn't compiled—and neither is React Native. Bundling isn't the same as compiling, but it can help improve startup performance and translate some platform-specific JavaScript into more JavaScript.
-
-### Step 2: Start your application
-
-Let Metro Bundler run in its own terminal. Open a new terminal inside your React Native project folder. Run the following:
-
-```shell
-npx react-native run-ios
-```
-
-You should see your new app running in the iOS Simulator shortly.
-
-
-
-`npx react-native run-ios` is 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
-
-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).
-
-### Modifying your app
-
-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.
-- Hit `⌘R` in your iOS Simulator to reload the app and see your changes!
-
-### That's it!
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-Installing dependencies
-
-You will need Node, the React Native command line interface, Python2, a JDK, and Android Studio.
-
-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.
-
-Node, Python2, JDK
-
-We recommend installing Node and Python2 via [Chocolatey](https://chocolatey.org), a popular package manager for Windows.
-
-React Native also requires [Java SE Development Kit (JDK)](https://openjdk.java.net/projects/jdk8/), as well as Python2. 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 openjdk8
-```
-
-If you have already installed Node on your system, make sure it is Node 10 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/).
-
-> If you're using the latest version of Java Development Kit, you'll need to change the Gradle version of your project so it can recognize the JDK. You can do that by going to `{project root folder}\android\gradle\wrapper\gradle-wrapper.properties` and changing the `distributionUrl` value to upgrade the Gradle version. You can check out [here the latest releases of Gradle](https://gradle.org/releases/).
-
-Android development environment
-
-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.
-
-1. Install Android Studio
-
-[Download and install Android Studio](https://developer.android.com/studio/index.html). While on Android Studio installation wizard, make sure the boxes next to all of the following items are checked:
-
-- `Android SDK`
-- `Android SDK Platform`
-- `Android Virtual Device`
-- If you are not already using Hyper-V: `Performance (Intel ® HAXM)` ([See here for AMD or Hyper-V](https://android-developers.googleblog.com/2018/07/android-emulator-amd-processor-hyper-v.html))
-
-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.
-
-2. Install the Android SDK
-
-Android Studio installs the latest Android SDK by default. Building a React Native app with native code, however, requires the `Android 10 (Q)` SDK in particular. Additional Android SDKs can be installed through the SDK Manager in Android Studio.
-
-To do that, open Android Studio, click on "More Actions" button and select "SDK Manager".
-
-
-
-> 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 10 (Q)` entry, then make sure the following items are checked:
-
-- `Android SDK Platform 29`
-- `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 `29.0.2` is selected.
-
-Finally, click "Apply" to download and install the Android SDK and related build tools.
-
-3. Configure the ANDROID_HOME environment variable
-
-The React Native tools require some environment variables to be set up in order to build apps with native code.
-
-1. Open the **Windows Control Panel.**
-2. Click on **User Accounts,** then click **User Accounts** again
-3. Click on **Change my environment variables**
-4. Click on **New...** to create a new `ANDROID_HOME` user variable that points to the path to your Android SDK:
-
-
-
-The SDK is installed, by default, at the following location:
-
-```powershell
-%LOCALAPPDATA%\Android\Sdk
-```
-
-You can find the actual location of the SDK in the Android Studio "Settings" 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.
-
-1. Open powershell
-2. Copy and paste **Get-ChildItem -Path Env:\\** into powershell
-3. Verify `ANDROID_HOME` has been added
-
-4. Add platform-tools to Path
-
-1. Open the **Windows Control Panel.**
-2. Click on **User Accounts,** then click **User Accounts** again
-3. Click on **Change my environment variables**
-4. Select the **Path** variable.
-5. Click **Edit.**
-6. Click **New** and add the path to platform-tools to the list.
-
-The default location for this folder is:
-
-```powershell
-%LOCALAPPDATA%\Android\Sdk\platform-tools
-```
-
-React Native Command Line Interface
-
-React Native has a built-in command line interface. Rather than install and manage a specific version of the CLI globally, we recommend you access the current version at runtime using `npx`, which ships with Node.js. With `npx react-native `, the current stable version of the CLI will be downloaded and executed at the time the command is run.
-
-Creating a new application
-
-> If you previously installed a global `react-native-cli` package, please remove it as it may cause unexpected issues.
-
-React Native has a built-in command line interface, which you can use to generate a new project. You can access it without installing anything globally using `npx`, which ships with Node.js. Let's create a new React Native project called "AwesomeProject":
-
-```shell
-npx react-native init AwesomeProject
-```
-
-This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Expo, 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 or template
-
-If you want to start a new project with a specific React Native version, you can use the `--version` argument:
-
-```shell
-npx react-native init AwesomeProject --version X.XX.X
-```
-
-You can also start a project with a custom React Native template, like TypeScript, with `--template` argument:
-
-```shell
-npx react-native init AwesomeTSProject --template react-native-template-typescript
-```
-
-Preparing the Android device
-
-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
-
-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
-
-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:
-
-
-
-If you have recently 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 **Q** API Level 29 image.
-
-> 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.
-
-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.
-
-Running your React Native application
-
-Step 1: Start Metro
-
-First, you will need to start Metro, the JavaScript bundler that ships with React Native. Metro "takes in an entry file and various options, and returns a single JavaScript file that includes all your code and its dependencies."—[Metro Docs](https://facebook.github.io/metro/docs/concepts)
-
-To start Metro, run `npx react-native start` inside your React Native project folder:
-
-```shell
-npx react-native start
-```
-
-`react-native start` starts Metro Bundler.
-
-> If you use the Yarn package manager, you can use `yarn` instead of `npx` when running React Native commands inside an existing project.
-
-> If you're familiar with web development, Metro is a lot like webpack—for React Native apps. Unlike Kotlin or Java, JavaScript isn't compiled—and neither is React Native. Bundling isn't the same as compiling, but it can help improve startup performance and translate some platform-specific JavaScript into more JavaScript.
-
-Step 2: Start your application
-
-Let Metro Bundler run in its own terminal. Open a new terminal inside your React Native project folder. Run the following:
-
-```shell
-npx react-native run-android
-```
-
-If everything is set up correctly, you should see your new app running in your Android emulator shortly.
-
-
-
-`npx react-native run-android` is 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.
-
-Modifying your app
-
-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!
-
-That's it!
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-Now what?
-
-- 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, check out the [Introduction to React Native](getting-started).
diff --git a/website/versioned_docs/version-0.60/_integration-with-existing-apps-java.md b/website/versioned_docs/version-0.60/_integration-with-existing-apps-java.md
deleted file mode 100644
index c84c29d9d13..00000000000
--- a/website/versioned_docs/version-0.60/_integration-with-existing-apps-java.md
+++ /dev/null
@@ -1,385 +0,0 @@
-## Key Concepts
-
-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.
-
-## Prerequisites
-
-Follow the React Native CLI Quickstart in the [environment setup guide](/docs/environment-setup) 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.
-
-### 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:
-
-```shell
-$ 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:
-
-```shell
-$ 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.
-
-## Adding React Native to your app
-
-### Configuring maven
-
-Add the React Native and JSC 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
- implementation "org.webkit:android-jsc:+"
-}
-```
-
-> 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 and JSC maven directories to the top-level `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"
- }
- maven {
- // Android JSC is installed from npm
- url("$rootDir/../node_modules/jsc-android/dist")
- }
- ...
- }
- ...
-}
-```
-
-> 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.
-
-### Enable native modules autolinking
-
-To use the power of [autolinking](https://github.com/react-native-community/cli/blob/master/docs/autolinking.md), we have to apply it a few places. First add the following entry to `settings.gradle`:
-
-```gradle
-apply from: file("../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesSettingsGradle(settings)
-```
-
-Next add the following entry at the very bottom of the `app/build.gradle`:
-
-```gradle
-apply from: file("../../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesAppBuildGradle(project)
-```
-
-### Configuring permissions
-
-Next, make sure you have the Internet permission in your `AndroidManifest.xml`:
-
-
-
-
-
-```
-
-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 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 a `` component within a styled ``:
-
-```jsx
-import React from 'react';
-import {AppRegistry, StyleSheet, Text, View} from 'react-native';
-
-class HelloWorld extends React.Component {
- render() {
- return (
-
- Hello, World
-
- );
- }
-}
-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 targeting 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);
- SoLoader.init(this, false);
-
- mReactRootView = new ReactRootView(this);
- List packages = new PackageList(getApplication()).getPackages();
- // Packages that cannot be autolinked yet can be added manually here, for example:
- // packages.add(new MyReactNativePackage());
- // Remember to include them in `settings.gradle` and `app/build.gradle` too.
-
- mReactInstanceManager = ReactInstanceManager.builder()
- .setApplication(getApplication())
- .setCurrentActivity(this)
- .setBundleAssetName("index.android.bundle")
- .setJSMainModulePath("index")
- .addPackages(packages)
- .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).
-
-Perform a “Sync Project files with Gradle” operation.
-
-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
-
-
-```
-
-> 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 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 [Metro bundler][metro] 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, run the following command in the root directory of your React Native project:
-
-```shell
-$ 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:
-
-
-
-### Creating a release build in Android Studio
-
-You can use Android Studio to create your release builds too! It’s as quick as creating release builds of your previously-existing native Android app. There’s 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:
-
-```shell
-$ npx 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, create a release build of your native app from within Android Studio as usual and you should be good to go!
-
-### Now what?
-
-At this point you can continue developing your app as usual. Refer to our [debugging](debugging) and [deployment](running-on-device) docs to learn more about working with React Native.
-
-[metro]: https://facebook.github.io/metro/
diff --git a/website/versioned_docs/version-0.60/_integration-with-existing-apps-objc.md b/website/versioned_docs/version-0.60/_integration-with-existing-apps-objc.md
deleted file mode 100644
index f364f00df3f..00000000000
--- a/website/versioned_docs/version-0.60/_integration-with-existing-apps-objc.md
+++ /dev/null
@@ -1,356 +0,0 @@
-## Key Concepts
-
-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.
-
-## Prerequisites
-
-Follow the React Native CLI Quickstart in the [environment setup guide](/docs/environment-setup) 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.
-
-### 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:
-
-```shell
-$ 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:
-
-```shell
-$ 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.
-
-### 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/).
-
-```shell
-$ 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.
-
-## Adding React Native to your app
-
-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.
-
-
-
-### 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.
-
-
-
-### 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/0.60-stable/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 `` elements), then you will need the `RCTText` `subspec`. If you want the `Image` library (e.g., for `` 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:
-
-```shell
-$ pod init
-```
-
-The `Podfile` will contain a boilerplate setup that you will tweak for your integration purposes.
-
-> The `Podfile` version changes depending on your version of `react-native`. Refer to https://react-native-community.github.io/upgrade-helper/ for the specific version of `Podfile` you should be using.
-
-Ultimately, your `Podfile` should look something similar to this:
-
-```
-# 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 'FBLazyVector', :path => "../node_modules/react-native/Libraries/FBLazyVector"
- pod 'FBReactNativeSpec', :path => "../node_modules/react-native/Libraries/FBReactNativeSpec"
- pod 'RCTRequired', :path => "../node_modules/react-native/Libraries/RCTRequired"
- pod 'RCTTypeSafety', :path => "../node_modules/react-native/Libraries/TypeSafety"
- pod 'React', :path => '../node_modules/react-native/'
- pod 'React-Core', :path => '../node_modules/react-native/'
- pod 'React-CoreModules', :path => '../node_modules/react-native/React/CoreModules'
- pod 'React-Core/DevSupport', :path => '../node_modules/react-native/'
- 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-Core/RCTWebSocket', :path => '../node_modules/react-native/'
-
- 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 'ReactCommon/callinvoker', :path => "../node_modules/react-native/ReactCommon"
- pod 'ReactCommon/turbomodule/core', :path => "../node_modules/react-native/ReactCommon"
- 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
-```
-
-After you have created your `Podfile`, you are ready to install the React Native pod.
-
-```shell
-$ pod install
-```
-
-You should see output such as:
-
-```
-Analyzing dependencies
-Fetching podspec for `React` from `../node_modules/react-native`
-Downloading dependencies
-Installing React (0.62.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.
-
-### 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 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 a `` component within a styled ``
-
-```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 => (
-
- {score.name}:{score.value}
- {'\n'}
-
- ));
- return (
-
-
- 2048 High Scores!
-
- {contents}
-
- );
- }
-}
-
-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 contain 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.
-
-
-
-##### 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 [Metro bundler][metro] 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.
-
-First `import` the `RCTRootView` header.
-
-```objectivec
-#import
-```
-
-> 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/0.60-stable/React/Base/RCTBridge.h#L93) to create a bridge and then use `RCTRootView initWithBridge`.
-
-> 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.
-
-##### 3. Wire Up
-
-Wire up the new link in the main menu to the newly added event handler method.
-
-
-
-> 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 [Metro bundler][metro] 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
-NSAppTransportSecurity
-
- NSExceptionDomains
-
- localhost
-
- NSTemporaryExceptionAllowsInsecureHTTPLoads
-
-
-
-```
-
-> 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, run the following command in the root directory of your React Native project:
-
-```shell
-$ 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
-$ npx 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:
-
-
-
-Here is the _React Native_ high score screen:
-
-
-
-> 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
-
-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).
-
-### Now what?
-
-At this point you can continue developing your app as usual. Refer to our [debugging](debugging) and [deployment](running-on-device) docs to learn more about working with React Native.
-
-[metro]: https://facebook.github.io/metro/
diff --git a/website/versioned_docs/version-0.60/_integration-with-existing-apps-swift.md b/website/versioned_docs/version-0.60/_integration-with-existing-apps-swift.md
deleted file mode 100644
index 2945c965a84..00000000000
--- a/website/versioned_docs/version-0.60/_integration-with-existing-apps-swift.md
+++ /dev/null
@@ -1,345 +0,0 @@
-## Key Concepts
-
-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.
-
-## Prerequisites
-
-Follow the React Native CLI Quickstart in the [environment setup guide](/docs/environment-setup) 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.
-
-### 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:
-
-```shell
-$ 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:
-
-```shell
-$ 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.
-
-### 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/).
-
-```shell
-$ 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.
-
-## Adding React Native to your app
-
-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.
-
-
-
-### 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.
-
-
-
-### 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/0.60-stable/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 `` elements), then you will need the `RCTText` `subspec`. If you want the `Image` library (e.g., for `` 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:
-
-```shell
-$ pod init
-```
-
-The `Podfile` will contain a boilerplate setup that you will tweak for your integration purposes.
-
-> The `Podfile` version changes depending on your version of `react-native`. Refer to https://react-native-community.github.io/upgrade-helper/ for the specific version of `Podfile` you should be using.
-
-Ultimately, your `Podfile` should look something similar to this:
-
-```
-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
-```
-
-After you have created your `Podfile`, you are ready to install the React Native pod.
-
-```shell
-$ pod install
-```
-
-You should see output such as:
-
-```
-Analyzing dependencies
-Fetching podspec for `React` from `../node_modules/react-native`
-Downloading dependencies
-Installing React (0.62.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.
-
-> 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)`.
-
-### 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 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 a `` component within a styled ``
-
-```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 => (
-
- {score.name}:{score.value}
- {'\n'}
-
- ));
- return (
-
-
- 2048 High Scores!
-
- {contents}
-
- );
- }
-}
-
-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 contain 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.
-
-
-
-##### 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 [Metro bundler][metro] 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.
-
-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/0.60-stable/React/Base/RCTBridge.h#L89) to create a bridge and then use `RCTRootView initWithBridge`.
-
-> 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.
-
-##### 3. Wire Up
-
-Wire up the new link in the main menu to the newly added event handler method.
-
-
-
-> 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 [Metro bundler][metro] 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
-NSAppTransportSecurity
-
- NSExceptionDomains
-
- localhost
-
- NSTemporaryExceptionAllowsInsecureHTTPLoads
-
-
-
-```
-
-> 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, run the following command in the root directory of your React Native project:
-
-```shell
-$ 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
-$ npx 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:
-
-
-
-Here is the _React Native_ high score screen:
-
-
-
-> 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
-
-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).
-
-### Now what?
-
-At this point you can continue developing your app as usual. Refer to our [debugging](debugging) and [deployment](running-on-device) docs to learn more about working with React Native.
-
-[metro]: https://facebook.github.io/metro/
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 66de1067452..00000000000
--- a/website/versioned_docs/version-0.60/accessibility.md
+++ /dev/null
@@ -1,293 +0,0 @@
----
-id: accessibility
-title: Accessibility
----
-
-Both Android and iOS provide APIs for integrating apps with assistive technologies like the bundled screen readers VoiceOver (iOS) and TalkBack (Android). React Native has complimentary APIs that let your app accommodate all users.
-
-> Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
-
-## Accessibility properties
-
-### `accessible` (Android, iOS)
-
-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
-
- text one
- text two
-
-```
-
-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` (Android, iOS)
-
-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
-
-
- Press me!
-
-
-```
-
-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` (Android, iOS)
-
-An accessibility hint helps users understand what will happen when they perform an action on the accessibility element when that result is not clear from the accessibility label.
-
-To use, set the `accessibilityHint` property to a custom string on your View, Text or Touchable:
-
-```jsx
-
-
- Back
-
-
-```
-
-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` (Android, iOS)
-
-`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).
-
-### `accessibilityState` (Android, iOS)
-
-Describes the current state of a component to the user of an assistive technology.
-
-`accessibilityState` is an object. It contains the following fields:
-
-| Name | Description | Type | Required |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | -------- |
-| disabled | Indicates whether the element is disabled or not. | boolean | No |
-| selected | Indicates whether a selectable element is currently selected or not. | boolean | No |
-| checked | Indicates the state of a checkable element. This field can either take a boolean or the "mixed" string to represent mixed checkboxes. | boolean or 'mixed' | No |
-| busy | Indicates whether an element is currently busy or not. | boolean | No |
-| expanded | Indicates whether an expandable element is currently expanded or collapsed. | boolean | No |
-
-To use, set the `accessibilityState` to an object with a specific definition.
-
-### `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` (Android, 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
-
-
- Click me
-
-
-
- Clicked {count} times
-
-```
-
-In the above example method `addOne` changes the state variable `count`. 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
-
-
- First layout
-
-
- Second layout
-
-
-```
-
-In the above example, the `yellow` layout and its descendants are completely invisible to TalkBack and all other accessibility services. So we can 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
- {
- 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) 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 set accessibility focus to a view). Native UIManager module exposes a method ‘sendAccessibilityEvent’ for this purpose. It takes two arguments: view tag and a type of an event. The supported event types are `typeWindowStateChanged`, `typeViewFocused` and `typeViewClicked`.
-
-```jsx
-import {Platform, UIManager, findNodeHandle} from 'react-native';
-
-if (Platform.OS === 'android') {
- UIManager.sendAccessibilityEvent(
- findNodeHandle(this),
- UIManager.AccessibilityEventTypes.typeViewFocused,
- );
-}
-```
-
-## 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:
-
-```shell
-# 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
-```
-
-## Additional Resources
-
-- [Making React Native Apps Accessible](https://engineering.fb.com/ios/making-react-native-apps-accessible/)
diff --git a/website/versioned_docs/version-0.60/accessibilityinfo.md b/website/versioned_docs/version-0.60/accessibilityinfo.md
deleted file mode 100644
index 8b4fd5c8853..00000000000
--- a/website/versioned_docs/version-0.60/accessibilityinfo.md
+++ /dev/null
@@ -1,184 +0,0 @@
----
-id: accessibilityinfo
-title: AccessibilityInfo
----
-
-Sometimes it's useful to know whether or not the device has a screen reader that is currently active. The `AccessibilityInfo` API is designed for this purpose. You can use it to query the current state of the screen reader as well as to register to be notified when the state of the screen reader changes.
-
-Here's a small example illustrating how to use `AccessibilityInfo`:
-
-```jsx
-class AccessibilityStatusExample extends React.Component {
- state = {
- reduceMotionEnabled: false,
- screenReaderEnabled: false,
- };
-
- componentDidMount() {
- AccessibilityInfo.addEventListener(
- 'reduceMotionChanged',
- this._handleReduceMotionToggled,
- );
- AccessibilityInfo.addEventListener(
- 'screenReaderChanged',
- this._handleScreenReaderToggled,
- );
-
- AccessibilityInfo.isReduceMotionEnabled().then(
- reduceMotionEnabled => {
- this.setState({reduceMotionEnabled});
- },
- );
- AccessibilityInfo.isScreenReaderEnabled().then(
- screenReaderEnabled => {
- this.setState({screenReaderEnabled});
- },
- );
- }
-
- componentWillUnmount() {
- AccessibilityInfo.removeEventListener(
- 'reduceMotionChanged',
- this._handleReduceMotionToggled,
- );
-
- AccessibilityInfo.removeEventListener(
- 'screenReaderChanged',
- this._handleScreenReaderToggled,
- );
- }
-
- _handleReduceMotionToggled = reduceMotionEnabled => {
- this.setState({reduceMotionEnabled});
- };
-
- _handleScreenReaderToggled = screenReaderEnabled => {
- this.setState({screenReaderEnabled});
- };
-
- render() {
- return (
-
-
- The reduce motion is{' '}
- {this.state.reduceMotionEnabled
- ? 'enabled'
- : 'disabled'}
- .
-
-
- The screen reader is{' '}
- {this.state.screenReaderEnabled
- ? 'enabled'
- : 'disabled'}
- .
-
-
- );
- }
-}
-```
-
----
-
-# Reference
-
-## Methods
-
-### `isBoldTextEnabled()`
-
-```jsx
-static isBoldTextEnabled()
-```
-
-**iOS-Only.** Query whether a bold text is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when bold text is enabled and `false` otherwise.
-
-### `isGrayscaleEnabled()`
-
-```jsx
-static isGrayscaleEnabled()
-```
-
-**iOS-Only.** Query whether grayscale is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when grayscale is enabled and `false` otherwise.
-
-### `isInvertColorsEnabled()`
-
-```jsx
-static isInvertColorsEnabled()
-```
-
-**iOS-Only.** Query whether invert colors is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when invert colors is enabled and `false` otherwise.
-
-### `isReduceMotionEnabled()`
-
-```jsx
-static isReduceMotionEnabled()
-```
-
-Query whether reduce motion is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when reduce motion is enabled and `false` otherwise.
-
-### `isReduceTransparencyEnabled()`
-
-```jsx
-static isReduceTransparencyEnabled()
-```
-
-**iOS-Only.** Query whether reduce transparency is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when a reduce transparency is enabled and `false` otherwise.
-
-### `isScreenReaderEnabled()`
-
-```jsx
-static isScreenReaderEnabled()
-```
-
-Query whether a screen reader is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when a screen reader is enabled and `false` otherwise.
-
----
-
-### `addEventListener()`
-
-```jsx
-static addEventListener(eventName, handler)
-```
-
-Add an event handler. Supported events:
-
-- `boldTextChanged`: iOS-only event. Fires when the state of the bold text toggle changes. The argument to the event handler is a boolean. The boolean is `true` when bold text is enabled and `false` otherwise.
-- `grayscaleChanged`: iOS-only event. Fires when the state of the gray scale toggle changes. The argument to the event handler is a boolean. The boolean is `true` when a gray scale is enabled and `false` otherwise.
-- `invertColorsChanged`: iOS-only event. Fires when the state of the invert colors toggle changes. The argument to the event handler is a boolean. The boolean is `true` when invert colors is enabled and `false` otherwise.
-- `reduceMotionChanged`: Fires when the state of the reduce motion toggle changes. The argument to the event handler is a boolean. The boolean is `true` when a reduce motion is enabled (or when "Transition Animation Scale" in "Developer options" is "Animation off") and `false` otherwise.
-- `screenReaderChanged`: Fires when the state of the screen reader changes. The argument to the event handler is a boolean. The boolean is `true` when a screen reader is enabled and `false` otherwise.
-- `reduceTransparencyChanged`: iOS-only event. Fires when the state of the reduce transparency toggle changes. The argument to the event handler is a boolean. The boolean is `true` when reduce transparency is enabled and `false` otherwise.
-- `announcementFinished`: iOS-only event. Fires when the screen reader has finished making an announcement. The argument to the event handler is a dictionary with these keys:
- - `announcement`: The string announced by the screen reader.
- - `success`: A boolean indicating whether the announcement was successfully made.
-
----
-
-### `setAccessibilityFocus()`
-
-```jsx
-static setAccessibilityFocus(reactTag)
-```
-
-Set accessibility focus to a React component. On Android, this is equivalent to `UIManager.sendAccessibilityEvent(reactTag, UIManager.AccessibilityEventTypes.typeViewFocused);`.
-
----
-
-### `announceForAccessibility()`
-
-```jsx
-static announceForAccessibility(announcement)
-```
-
-Post a string to be announced by the screen reader.
-
----
-
-### `removeEventListener()`
-
-```jsx
-static removeEventListener(eventName, handler)
-```
-
-Remove an event handler.
diff --git a/website/versioned_docs/version-0.60/actionsheetios.md b/website/versioned_docs/version-0.60/actionsheetios.md
deleted file mode 100644
index 9d55bd16baa..00000000000
--- a/website/versioned_docs/version-0.60/actionsheetios.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-id: actionsheetios
-title: ActionSheetIOS
----
-
-# Reference
-
-## Methods
-
-### `showActionSheetWithOptions()`
-
-```jsx
-static showActionSheetWithOptions(options, callback)
-```
-
-Display an iOS action sheet. The `options` object must contain one or more of:
-
-- `options` (array of strings) - a list of button titles (required)
-- `cancelButtonIndex` (int) - index of cancel button in `options`
-- `destructiveButtonIndex` (int) - index of destructive button in `options`
-- `title` (string) - a title to show above the action sheet
-- `message` (string) - a message to show below the title
-- `anchor` (number) - the node to which the action sheet should be anchored (used for iPad)
-- `tintColor` (string) - the [color](colors.md) used for non-destructive button titles
-
-The 'callback' function takes one parameter, the zero-based index of the selected item.
-
-Minimal example:
-
-```jsx
-ActionSheetIOS.showActionSheetWithOptions(
- {
- options: ['Cancel', 'Remove'],
- destructiveButtonIndex: 1,
- cancelButtonIndex: 0,
- },
- buttonIndex => {
- if (buttonIndex === 1) {
- /* destructive action */
- }
- },
-);
-```
-
----
-
-### `showShareActionSheetWithOptions()`
-
-```jsx
-static showShareActionSheetWithOptions(options, failureCallback, successCallback)
-```
-
-Display the iOS share sheet. The `options` object should contain one or both of `message` and `url` and can additionally have a `subject` or `excludedActivityTypes`:
-
-- `url` (string) - a URL to share
-- `message` (string) - a message to share
-- `subject` (string) - a subject for the message
-- `excludedActivityTypes` (array) - the activities to exclude from the ActionSheet
-
-NOTE: if `url` points to a local file, or is a base64-encoded uri, the file it points to will be loaded and shared directly. In this way, you can share images, videos, PDF files, etc.
-
-The 'failureCallback' function takes one parameter, an error object. The only property defined on this object is an optional `stack` property of type `string`.
-
-The 'successCallback' function takes two parameters:
-
-- a boolean value signifying success or failure
-- a string that, in the case of success, indicates the method of sharing
diff --git a/website/versioned_docs/version-0.60/activityindicator.md b/website/versioned_docs/version-0.60/activityindicator.md
deleted file mode 100644
index ca2fe6bdb81..00000000000
--- a/website/versioned_docs/version-0.60/activityindicator.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-id: activityindicator
-title: ActivityIndicator
----
-
-Displays a circular loading indicator.
-
-### Example
-
-```SnackPlayer name=activityindicator
-import React, { Component } from 'react'
-import {
- ActivityIndicator,
- StyleSheet,
- Text,
- View,
-} from 'react-native'
-
-export default class App extends Component {
- render() {
- return (
-
-
- )
- }
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- justifyContent: 'center'
- },
- horizontal: {
- flexDirection: 'row',
- justifyContent: 'space-around',
- padding: 10
- }
-})
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `animating`
-
-Whether to show the indicator (true, the default) or hide it (false).
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `color`
-
-The foreground color of the spinner (default is gray on iOS and dark cyan on Android).
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `hidesWhenStopped`
-
-Whether the indicator should hide when not animating (true by default).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `size`
-
-Size of the indicator (default is 'small'). Passing a number to the size prop is only supported on Android.
-
-| Type | Required |
-| ------------------------------ | -------- |
-| enum('small', 'large'), number | No |
diff --git a/website/versioned_docs/version-0.60/alert.md b/website/versioned_docs/version-0.60/alert.md
deleted file mode 100644
index f731ece5a71..00000000000
--- a/website/versioned_docs/version-0.60/alert.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-id: alert
-title: Alert
----
-
-Launches an alert dialog with the specified title and message.
-
-Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
-
-This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see `AlertIOS`; entering text in an alert is common on iOS only.
-
-## Example
-
-
-
- iOS
- Android
-
-
-
-
-
-
-
-
-
-## iOS
-
-On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.
-
-## Android
-
-On Android at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
-
-- If you specify one button, it will be the 'positive' one (such as 'OK')
-- Two buttons mean 'negative', 'positive' (such as 'Cancel', 'OK')
-- Three buttons mean 'neutral', 'negative', 'positive' (such as 'Later', 'Cancel', 'OK')
-
-By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
-
-Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }
-
-Example usage:
-
-```jsx
-// Works on both Android and iOS
-Alert.alert(
- 'Alert Title',
- 'My Alert Msg',
- [
- {
- text: 'Ask me later',
- onPress: () => console.log('Ask me later pressed'),
- },
- {
- text: 'Cancel',
- onPress: () => console.log('Cancel Pressed'),
- style: 'cancel',
- },
- {text: 'OK', onPress: () => console.log('OK Pressed')},
- ],
- {cancelable: false},
-);
-```
-
----
-
-# Reference
-
-## Methods
-
-### `alert()`
-
-```jsx
-static alert(title, message?, buttons?, options? type?)
-```
diff --git a/website/versioned_docs/version-0.60/alertios.md b/website/versioned_docs/version-0.60/alertios.md
deleted file mode 100644
index c15902662b4..00000000000
--- a/website/versioned_docs/version-0.60/alertios.md
+++ /dev/null
@@ -1,190 +0,0 @@
----
-id: alertios
-title: AlertIOS
----
-
-> **Deprecated.** `AlertIOS` has been moved to [`Alert`](alert.md)
-
-`AlertIOS` provides functionality to create an iOS alert dialog with a message or create a prompt for user input.
-
-Creating an iOS alert:
-
-```jsx
-AlertIOS.alert(
- 'Sync Complete',
- 'All your data are belong to us.',
-);
-```
-
-Creating an iOS prompt:
-
-```jsx
-AlertIOS.prompt('Enter a value', null, text =>
- console.log('You entered ' + text),
-);
-```
-
-We recommend using the [`Alert.alert`](alert.md) method for cross-platform support if you don't need to create iOS-only prompts.
-
----
-
-# Reference
-
-## Methods
-
-### `alert()`
-
-```jsx
-static alert(title: string, [message]: string, [callbackOrButtons]: ?(() => void), ButtonsArray, [type]: AlertType): [object Object]
-```
-
-Create and display a popup alert.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----------------- | ------------------------------------------------------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| title | string | Yes | The dialog's title. Passing null or '' will hide the title. |
-| message | string | No | An optional message that appears below the dialog's title. |
-| callbackOrButtons | ?(() => void),[ButtonsArray](alertios.md#buttonsarray) | No | This optional argument should be either a single-argument function or an array of buttons. If passed a function, it will be called when the user taps 'OK'. If passed an array of button configurations, each button should include a `text` key, as well as optional `onPress` and `style` keys. `style` should be one of 'default', 'cancel' or 'destructive'. |
-| type | [AlertType](alertios.md#alerttype) | No | Deprecated, do not use. |
-
-Example with custom buttons:
-
-```jsx
-AlertIOS.alert(
- 'Update available',
- 'Keep your app up to date to enjoy the latest features',
- [
- {
- text: 'Cancel',
- onPress: () => console.log('Cancel Pressed'),
- style: 'cancel',
- },
- {
- text: 'Install',
- onPress: () => console.log('Install Pressed'),
- },
- ],
-);
-```
-
----
-
-### `prompt()`
-
-```jsx
-static prompt(title: string, [message]: string, [callbackOrButtons]: ?((text: string) => void), ButtonsArray, [type]: AlertType, [defaultValue]: string, [keyboardType]: string): [object Object]
-```
-
-Create and display a prompt to enter some text.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----------------- | ------------------------------------------------------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| title | string | Yes | The dialog's title. |
-| message | string | No | An optional message that appears above the text input. |
-| callbackOrButtons | ?((text: string) => void),[ButtonsArray](alertios.md#buttonsarray) | No | This optional argument should be either a single-argument function or an array of buttons. If passed a function, it will be called with the prompt's value when the user taps 'OK'. If passed an array of button configurations, each button should include a `text` key, as well as optional `onPress` and `style` keys (see example). `style` should be one of 'default', 'cancel' or 'destructive'. |
-| type | [AlertType](alertios.md#alerttype) | No | This configures the text input. One of 'plain-text', 'secure-text' or 'login-password'. |
-| defaultValue | string | No | The default text in text input. |
-| keyboardType | string | No | The keyboard type of first text field(if exists). One of 'default', 'email-address', 'numeric', 'phone-pad', 'ascii-capable', 'numbers-and-punctuation', 'url', 'number-pad', 'name-phone-pad', 'decimal-pad', 'twitter' or 'web-search'. |
-
-Example with custom buttons:
-
-```jsx
-AlertIOS.prompt(
- 'Enter password',
- 'Enter your password to claim your $1.5B in lottery winnings',
- [
- {
- text: 'Cancel',
- onPress: () => console.log('Cancel Pressed'),
- style: 'cancel',
- },
- {
- text: 'OK',
- onPress: password =>
- console.log('OK Pressed, password: ' + password),
- },
- ],
- 'secure-text',
-);
-```
-
-,
-
-Example with the default button and a custom callback:
-
-```jsx
-AlertIOS.prompt(
- 'Update username',
- null,
- text => console.log('Your username is ' + text),
- null,
- 'default',
-);
-```
-
-## Type Definitions
-
-### AlertType
-
-An Alert button type
-
-| Type |
-| ------ |
-| \$Enum |
-
-**Constants:**
-
-| Value | Description |
-| -------------- | ---------------------------- |
-| default | Default alert with no inputs |
-| plain-text | Plain text input alert |
-| secure-text | Secure text input alert |
-| login-password | Login and password alert |
-
----
-
-### AlertButtonStyle
-
-An Alert button style
-
-| Type |
-| ------ |
-| \$Enum |
-
-**Constants:**
-
-| Value | Description |
-| ----------- | ------------------------ |
-| default | Default button style |
-| cancel | Cancel button style |
-| destructive | Destructive button style |
-
----
-
-### ButtonsArray
-
-Array or buttons
-
-| Type |
-| ----- |
-| Array |
-
-**Properties:**
-
-| Name | Type | Description |
-| --------- | ------------------------------------------------ | ------------------------------------- |
-| [text] | string | Button label |
-| [onPress] | function | Callback function when button pressed |
-| [style] | [AlertButtonStyle](alertios.md#alertbuttonstyle) | Button style |
-
-**Constants:**
-
-| Value | Description |
-| ------- | ------------------------------------- |
-| text | Button label |
-| onPress | Callback function when button pressed |
-| style | Button style |
diff --git a/website/versioned_docs/version-0.60/animated.md b/website/versioned_docs/version-0.60/animated.md
deleted file mode 100644
index 12a1ba07180..00000000000
--- a/website/versioned_docs/version-0.60/animated.md
+++ /dev/null
@@ -1,391 +0,0 @@
----
-id: animated
-title: Animated
----
-
-The `Animated` library is designed to make animations fluid, powerful, and painless to build and maintain. `Animated` focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and `start`/`stop` methods to control time-based animation execution.
-
-The most basic workflow for creating an animation is to create an `Animated.Value`, hook it up to one or more style attributes of an animated component, and then drive updates via animations using `Animated.timing()`:
-
-```jsx
-Animated.timing(
- // Animate value over time
- this.state.fadeAnim, // The value to drive
- {
- toValue: 1, // Animate to final value of 1
- },
-).start(); // Start the animation
-```
-
-Refer to the [Animations](animations.md#animated-api) guide to see additional examples of `Animated` in action.
-
-## Overview
-
-There are two value types you can use with `Animated`:
-
-- [`Animated.Value()`](animated.md#value) for single values
-- [`Animated.ValueXY()`](animated.md#valuexy) for vectors
-
-`Animated.Value` can bind to style properties or other props, and can be interpolated as well. A single `Animated.Value` can drive any number of properties.
-
-### Configuring animations
-
-`Animated` provides three types of animation types. Each animation type provides a particular animation curve that controls how your values animate from their initial value to the final value:
-
-- [`Animated.decay()`](animated.md#decay) starts with an initial velocity and gradually slows to a stop.
-- [`Animated.spring()`](animated.md#spring) provides a basic spring physics model.
-- [`Animated.timing()`](animated.md#timing) animates a value over time using [easing functions](easing.md).
-
-In most cases, you will be using `timing()`. By default, it uses a symmetric easeInOut curve that conveys the gradual acceleration of an object to full speed and concludes by gradually decelerating to a stop.
-
-### Working with animations
-
-Animations are started by calling `start()` on your animation. `start()` takes a completion callback that will be called when the animation is done. If the animation finished running normally, the completion callback will be invoked with `{finished: true}`. If the animation is done because `stop()` was called on it before it could finish (e.g. because it was interrupted by a gesture or another animation), then it will receive `{finished: false}`.
-
-### Using the native driver
-
-By using the native driver, 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.
-
-You can use the native driver by specifying `useNativeDriver: true` in your animation configuration. See the [Animations](animations.md#using-the-native-driver) guide to learn more.
-
-### Animatable components
-
-Only animatable components can be animated. These unique components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.
-
-- [`createAnimatedComponent()`](animated.md#createanimatedcomponent) can be used to make a component animatable.
-
-`Animated` exports the following animatable components using the above wrapper:
-
-- `Animated.Image`
-- `Animated.ScrollView`
-- `Animated.Text`
-- `Animated.View`
-- `Animated.FlatList`
-- `Animated.SectionList`
-
-### Composing animations
-
-Animations can also be combined in complex ways using composition functions:
-
-- [`Animated.delay()`](animated.md#delay) starts an animation after a given delay.
-- [`Animated.parallel()`](animated.md#parallel) starts a number of animations at the same time.
-- [`Animated.sequence()`](animated.md#sequence) starts the animations in order, waiting for each to complete before starting the next.
-- [`Animated.stagger()`](animated.md#stagger) starts animations in order and in parallel, but with successive delays.
-
-Animations can also be chained together by setting the `toValue` of one animation to be another `Animated.Value`. See [Tracking dynamic values](animations.md#tracking-dynamic-values) in the Animations guide.
-
-By default, if one animation is stopped or interrupted, then all other animations in the group are also stopped.
-
-### Combining animated values
-
-You can combine two animated values via addition, subtraction, multiplication, division, or modulo to make a new animated value:
-
-- [`Animated.add()`](animated.md#add)
-- [`Animated.subtract()`](animated.md#subtract)
-- [`Animated.divide()`](animated.md#divide)
-- [`Animated.modulo()`](animated.md#modulo)
-- [`Animated.multiply()`](animated.md#multiply)
-
-### Interpolation
-
-The `interpolate()` function allows input ranges to map to different output ranges. By default, it will extrapolate the curve beyond the ranges given, but you can also have it clamp the output value. It uses linear interpolation by default but also supports easing functions.
-
-- [`interpolate()`](animated.md#interpolate)
-
-Read more about interpolation in the [Animation](animations.md#interpolation) guide.
-
-### Handling gestures and other events
-
-Gestures, like panning or scrolling, and other events can map directly to animated values using `Animated.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.
-
-- [`Animated.event()`](animated.md#event)
-
-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
- }
- }
- }]
- )}
-```
-
----
-
-# Reference
-
-## Methods
-
-When the given value is a ValueXY instead of a Value, each config option may be a vector of the form `{x: ..., y: ...}` instead of a scalar.
-
-### `decay()`
-
-```jsx
-static decay(value, config)
-```
-
-Animates a value from an initial velocity to zero based on a decay coefficient.
-
-Config is an object that may have the following options:
-
-- `velocity`: Initial velocity. Required.
-- `deceleration`: Rate of decay. Default 0.997.
-- `isInteraction`: Whether or not this animation creates an "interaction handle" on the `InteractionManager`. Default true.
-- `useNativeDriver`: Uses the native driver when true. Default false.
-
----
-
-### `timing()`
-
-```jsx
-static timing(value, config)
-```
-
-Animates a value along a timed easing curve. The [`Easing`](easing.md) module has tons of predefined curves, or you can use your own function.
-
-Config is an object that may have the following options:
-
-- `duration`: Length of animation (milliseconds). Default 500.
-- `easing`: Easing function to define curve. Default is `Easing.inOut(Easing.ease)`.
-- `delay`: Start the animation after delay (milliseconds). Default 0.
-- `isInteraction`: Whether or not this animation creates an "interaction handle" on the `InteractionManager`. Default true.
-- `useNativeDriver`: Uses the native driver when true. Default false.
-
----
-
-### `spring()`
-
-```jsx
-static spring(value, config)
-```
-
-Animates a value according to an analytical spring model based on [damped harmonic oscillation](https://en.wikipedia.org/wiki/Harmonic_oscillator#Damped_harmonic_oscillator). Tracks velocity state to create fluid motions as the `toValue` updates, and can be chained together.
-
-Config is an object that may have the following options.
-
-Note that you can only define one of bounciness/speed, tension/friction, or stiffness/damping/mass, but not more than one:
-
-The friction/tension or bounciness/speed options match the spring model in [`Facebook Pop`](https://github.com/facebook/pop), [Rebound](https://github.com/facebookarchive/rebound), and [Origami](http://origami.design/).
-
-- `friction`: Controls "bounciness"/overshoot. Default 7.
-- `tension`: Controls speed. Default 40.
-- `speed`: Controls speed of the animation. Default 12.
-- `bounciness`: Controls bounciness. Default 8.
-
-Specifying stiffness/damping/mass as parameters makes `Animated.spring` use an analytical spring model based on the motion equations of a [damped harmonic oscillator](https://en.wikipedia.org/wiki/Harmonic_oscillator#Damped_harmonic_oscillator). This behavior is slightly more precise and faithful to the physics behind spring dynamics, and closely mimics the implementation in iOS's CASpringAnimation.
-
-- `stiffness`: The spring stiffness coefficient. Default 100.
-- `damping`: Defines how the spring’s motion should be damped due to the forces of friction. Default 10.
-- `mass`: The mass of the object attached to the end of the spring. Default 1.
-
-Other configuration options are as follows:
-
-- `velocity`: The initial velocity of the object attached to the spring. Default 0 (object is at rest).
-- `overshootClamping`: Boolean indicating whether the spring should be clamped and not bounce. Default false.
-- `restDisplacementThreshold`: The threshold of displacement from rest below which the spring should be considered at rest. Default 0.001.
-- `restSpeedThreshold`: The speed at which the spring should be considered at rest in pixels per second. Default 0.001.
-- `delay`: Start the animation after delay (milliseconds). Default 0.
-- `isInteraction`: Whether or not this animation creates an "interaction handle" on the `InteractionManager`. Default true.
-- `useNativeDriver`: Uses the native driver when true. Default false.
-
----
-
-### `add()`
-
-```jsx
-static add(a, b)
-```
-
-Creates a new Animated value composed from two Animated values added together.
-
----
-
-### `subtract()`
-
-```jsx
-static subtract(a, b)
-```
-
-Creates a new Animated value composed by subtracting the second Animated value from the first Animated value.
-
----
-
-### `divide()`
-
-```jsx
-static divide(a, b)
-```
-
-Creates a new Animated value composed by dividing the first Animated value by the second Animated value.
-
----
-
-### `multiply()`
-
-```jsx
-static multiply(a, b)
-```
-
-Creates a new Animated value composed from two Animated values multiplied together.
-
----
-
-### `modulo()`
-
-```jsx
-static modulo(a, modulus)
-```
-
-Creates a new Animated value that is the (non-negative) modulo of the provided Animated value
-
----
-
-### `diffClamp()`
-
-```jsx
-static diffClamp(a, min, max)
-```
-
-Create a new Animated value that is limited between 2 values. It uses the difference between the last value so even if the value is far from the bounds it will start changing when the value starts getting closer again. (`value = clamp(value + diff, min, max)`).
-
-This is useful with scroll events, for example, to show the navbar when scrolling up and to hide it when scrolling down.
-
----
-
-### `delay()`
-
-```jsx
-static delay(time)
-```
-
-Starts an animation after the given delay.
-
----
-
-### `sequence()`
-
-```jsx
-static sequence(animations)
-```
-
-Starts an array of animations in order, waiting for each to complete before starting the next. If the current running animation is stopped, no following animations will be started.
-
----
-
-### `parallel()`
-
-```jsx
-static parallel(animations, config?)
-```
-
-Starts an array of animations all at the same time. By default, if one of the animations is stopped, they will all be stopped. You can override this with the `stopTogether` flag.
-
----
-
-### `stagger()`
-
-```jsx
-static stagger(time, animations)
-```
-
-Array of animations may run in parallel (overlap), but are started in sequence with successive delays. Nice for doing trailing effects.
-
----
-
-### `loop()`
-
-```jsx
-static loop(animation, config?)
-```
-
-Loops a given animation continuously, so that each time it reaches the end, it resets and begins again from the start. Will loop without blocking the UI thread if the child animation is set to `useNativeDriver: true`. In addition, loops can prevent `VirtualizedList`-based components from rendering more rows while the animation is running. You can pass `isInteraction: false` in the child animation config to fix this.
-
-Config is an object that may have the following options:
-
-- `iterations`: Number of times the animation should loop. Default `-1` (infinite).
-
----
-
-### `event()`
-
-```jsx
-static event(argMapping, config?)
-```
-
-Takes an array of mappings and extracts values from each arg accordingly, then calls `setValue` on the mapped outputs. e.g.
-
-```jsx
- onScroll={Animated.event(
- [{nativeEvent: {contentOffset: {x: this._scrollX}}}],
- {listener: (event) => console.log(event)}, // Optional async listener
- )}
- ...
- onPanResponderMove: Animated.event([
- null, // raw event arg ignored
- {dx: this._panX}], // gestureState arg
-{listener: (event, gestureState) => console.log(event, gestureState)}, // Optional async listener
- ),
-```
-
-Config is an object that may have the following options:
-
-- `listener`: Optional async listener.
-- `useNativeDriver`: Uses the native driver when true. Default false.
-
----
-
-### `forkEvent()`
-
-```jsx
-static forkEvent(event, listener)
-```
-
-Advanced imperative API for snooping on animated events that are passed in through props. It permits to add a new javascript listener to an existing `AnimatedEvent`. If `animatedEvent` is a javascript listener, it will merge the 2 listeners into a single one, and if `animatedEvent` is null/undefined, it will assign the javascript listener directly. Use values directly where possible.
-
----
-
-### `unforkEvent()`
-
-```jsx
-static unforkEvent(event, listener)
-```
-
-## Properties
-
-### `Value`
-
-Standard value class for driving animations. Typically initialized with `new Animated.Value(0);`
-
----
-
-### `ValueXY`
-
-2D value class for driving 2D animations, such as pan gestures.
-
----
-
-### `Interpolation`
-
-Exported to use the Interpolation type in flow.
-
----
-
-### `Node`
-
-Exported for ease of type checking. All animated values derive from this class.
-
----
-
-### `createAnimatedComponent`
-
-Make any React component Animatable. Used to create `Animated.View`, etc.
-
----
-
-### `attachNativeEvent`
-
-Imperative API to attach an animated value to an event on a view. Prefer using `Animated.event` with `useNativeDrive: true` if possible.
diff --git a/website/versioned_docs/version-0.60/animatedvalue.md b/website/versioned_docs/version-0.60/animatedvalue.md
deleted file mode 100644
index 6cbc745484c..00000000000
--- a/website/versioned_docs/version-0.60/animatedvalue.md
+++ /dev/null
@@ -1,228 +0,0 @@
----
-id: animatedvalue
-title: AnimatedValue
----
-
-Standard value for driving animations. One `Animated.Value` can drive multiple properties in a synchronized fashion, but can only be driven by one mechanism at a time. Using a new mechanism (e.g. starting a new animation, or calling `setValue`) will stop any previous ones.
-
-Typically initialized with `new Animated.Value(0);`
-
-See also [`Animated`](animated.md).
-
-### Methods
-
-- [`setValue`](animatedvalue.md#setvalue)
-- [`setOffset`](animatedvalue.md#setoffset)
-- [`flattenOffset`](animatedvalue.md#flattenoffset)
-- [`extractOffset`](animatedvalue.md#extractoffset)
-- [`addListener`](animatedvalue.md#addlistener)
-- [`removeListener`](animatedvalue.md#removelistener)
-- [`removeAllListeners`](animatedvalue.md#removealllisteners)
-- [`stopAnimation`](animatedvalue.md#stopanimation)
-- [`resetAnimation`](animatedvalue.md#resetanimation)
-- [`interpolate`](animatedvalue.md#interpolate)
-- [`animate`](animatedvalue.md#animate)
-- [`stopTracking`](animatedvalue.md#stoptracking)
-- [`track`](animatedvalue.md#track)
-
----
-
-# Reference
-
-## Methods
-
-### `setValue()`
-
-```jsx
-setValue(value);
-```
-
-Directly set the value. This will stop any animations running on the value and update all the bound properties.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----- | ------ | -------- | ----------- |
-| value | number | Yes | Value |
-
----
-
-### `setOffset()`
-
-```jsx
-setOffset(offset);
-```
-
-Sets an offset that is applied on top of whatever value is set, whether via `setValue`, an animation, or `Animated.event`. Useful for compensating things like the start of a pan gesture.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ------------ |
-| offset | number | Yes | Offset value |
-
----
-
-### `flattenOffset()`
-
-```jsx
-flattenOffset();
-```
-
-Merges the offset value into the base value and resets the offset to zero. The final output of the value is unchanged.
-
----
-
-### `extractOffset()`
-
-```jsx
-extractOffset();
-```
-
-Sets the offset value to the base value, and resets the base value to zero. The final output of the value is unchanged.
-
----
-
-### `addListener()`
-
-```jsx
-addListener(callback);
-```
-
-Adds an asynchronous listener to the value so you can observe updates from animations. This is useful because there is no way to synchronously read the value because it might be driven natively.
-
-Returns a string that serves as an identifier for the listener.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | ------------------------------------------------------------------------------------------- |
-| callback | function | Yes | The callback function which will receive an object with a `value` key set to the new value. |
-
----
-
-### `removeListener()`
-
-```jsx
-removeListener(id);
-```
-
-Unregister a listener. The `id` param shall match the identifier previously returned by `addListener()`.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ---- | ------ | -------- | ---------------------------------- |
-| id | string | Yes | Id for the listener being removed. |
-
----
-
-### `removeAllListeners()`
-
-```jsx
-removeAllListeners();
-```
-
-Remove all registered listeners.
-
----
-
-### `stopAnimation()`
-
-```jsx
-stopAnimation([callback]);
-```
-
-Stops any running animation or tracking. `callback` is invoked with the final value after stopping the animation, which is useful for updating state to match the animation position with layout.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | --------------------------------------------- |
-| callback | function | No | A function that will receive the final value. |
-
----
-
-### `resetAnimation()`
-
-```jsx
-resetAnimation([callback]);
-```
-
-Stops any animation and resets the value to its original.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | ------------------------------------------------ |
-| callback | function | No | A function that will receive the original value. |
-
----
-
-### `interpolate()`
-
-```jsx
-interpolate(config);
-```
-
-Interpolates the value before updating the property, e.g. mapping 0-1 to 0-10.
-
-See `AnimatedInterpolation.js`
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ----------- |
-| config | object | Yes | See below. |
-
-The `config` object is composed of the following keys:
-
-- `inputRange`: an array of numbers
-- `outputRange`: an array of numbers or strings
-- `easing` (optional): a function that returns a number, given an input number
-- `extrapolate` (optional): a string such as 'extend', 'identity', or 'clamp'
-- `extrapolateLeft` (optional): a string such as 'extend', 'identity', or 'clamp'
-- `extrapolateRight` (optional): a string such as 'extend', 'identity', or 'clamp'
-
----
-
-### `animate()`
-
-```jsx
-animate(animation, callback);
-```
-
-Typically only used internally, but could be used by a custom Animation class.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| --------- | --------- | -------- | ------------------- |
-| animation | Animation | Yes | See `Animation.js`. |
-| callback | function | Yes | Callback function. |
-
----
-
-### `stopTracking()`
-
-```jsx
-stopTracking();
-```
-
-Typically only used internally.
-
----
-
-### `track()`
-
-```jsx
-track(tracking);
-```
-
-Typically only used internally.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ------------ | -------- | --------------------- |
-| tracking | AnimatedNode | Yes | See `AnimatedNode.js` |
diff --git a/website/versioned_docs/version-0.60/animatedvaluexy.md b/website/versioned_docs/version-0.60/animatedvaluexy.md
deleted file mode 100644
index f89a4403120..00000000000
--- a/website/versioned_docs/version-0.60/animatedvaluexy.md
+++ /dev/null
@@ -1,222 +0,0 @@
----
-id: animatedvaluexy
-title: AnimatedValueXY
----
-
-2D Value for driving 2D animations, such as pan gestures. Almost identical API to normal [`Animated.Value`](animatedvalue.md), but multiplexed. Contains two regular `Animated.Value`s under the hood.
-
-See also [`Animated`](animated.md).
-
-## Example
-
-```jsx
-class DraggableView extends React.Component {
- constructor(props) {
- super(props);
- this.state = {
- pan: new Animated.ValueXY(), // inits to zero
- };
- this.state.panResponder = PanResponder.create({
- onStartShouldSetPanResponder: () => true,
- onPanResponderMove: Animated.event([
- null,
- {
- dx: this.state.pan.x, // x,y are Animated.Value
- dy: this.state.pan.y,
- },
- ]),
- onPanResponderRelease: () => {
- Animated.spring(
- this.state.pan, // Auto-multiplexed
- {toValue: {x: 0, y: 0}}, // Back to zero
- ).start();
- },
- });
- }
- render() {
- return (
-
- {this.props.children}
-
- );
- }
-}
-```
-
-### Methods
-
-- [`setValue`](animatedvaluexy.md#setvalue)
-- [`setOffset`](animatedvaluexy.md#setoffset)
-- [`flattenOffset`](animatedvaluexy.md#flattenoffset)
-- [`extractOffset`](animatedvaluexy.md#extractoffset)
-- [`addListener`](animatedvaluexy.md#addlistener)
-- [`removeListener`](animatedvaluexy.md#removelistener)
-- [`removeAllListeners`](animatedvaluexy.md#removealllisteners)
-- [`stopAnimation`](animatedvaluexy.md#stopanimation)
-- [`resetAnimation`](animatedvaluexy.md#resetanimation)
-- [`getLayout`](animatedvaluexy.md#getlayout)
-- [`getTranslateTransform`](animatedvaluexy.md#gettranslatetransform)
-
----
-
-# Reference
-
-## Methods
-
-### `setValue()`
-
-```jsx
-setValue(value);
-```
-
-Directly set the value. This will stop any animations running on the value and update all the bound properties.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----- | ------ | -------- | ----------- |
-| value | number | Yes | |
-
----
-
-### `setOffset()`
-
-```jsx
-setOffset(offset);
-```
-
-Sets an offset that is applied on top of whatever value is set, whether via `setValue`, an animation, or `Animated.event`. Useful for compensating things like the start of a pan gesture.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ----------- |
-| offset | number | Yes | |
-
----
-
-### `flattenOffset()`
-
-```jsx
-flattenOffset();
-```
-
-Merges the offset value into the base value and resets the offset to zero. The final output of the value is unchanged.
-
----
-
-### `extractOffset()`
-
-```jsx
-extractOffset();
-```
-
-Sets the offset value to the base value, and resets the base value to zero. The final output of the value is unchanged.
-
----
-
-### `addListener()`
-
-```jsx
-addListener(callback);
-```
-
-Adds an asynchronous listener to the value so you can observe updates from animations. This is useful because there is no way to synchronously read the value because it might be driven natively.
-
-Returns a string that serves as an identifier for the listener.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | ------------------------------------------------------------------------------------------- |
-| callback | function | Yes | The callback function which will receive an object with a `value` key set to the new value. |
-
----
-
-### `removeListener()`
-
-```jsx
-removeListener(id);
-```
-
-Unregister a listener. The `id` param shall match the identifier previously returned by `addListener()`.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ---- | ------ | -------- | ---------------------------------- |
-| id | string | Yes | Id for the listener being removed. |
-
----
-
-### `removeAllListeners()`
-
-```jsx
-removeAllListeners();
-```
-
-Remove all registered listeners.
-
----
-
-### `stopAnimation()`
-
-```jsx
-stopAnimation([callback]);
-```
-
-Stops any running animation or tracking. `callback` is invoked with the final value after stopping the animation, which is useful for updating state to match the animation position with layout.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | --------------------------------------------- |
-| callback | function | No | A function that will receive the final value. |
-
----
-
-### `resetAnimation()`
-
-```jsx
-resetAnimation([callback]);
-```
-
-Stops any animation and resets the value to its original.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | ------------------------------------------------ |
-| callback | function | No | A function that will receive the original value. |
-
----
-
-### `getLayout()`
-
-```jsx
-getLayout();
-```
-
-Converts `{x, y}` into `{left, top}` for use in style, e.g.
-
-```jsx
-style={this.state.anim.getLayout()}
-```
-
----
-
-### `getTranslateTransform()`
-
-```jsx
-getTranslateTransform();
-```
-
-Converts `{x, y}` into a useable translation transform, e.g.
-
-```jsx
-style={{
- transform: this.state.anim.getTranslateTransform()
-}}
-```
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 b1a8e6e0389..00000000000
--- a/website/versioned_docs/version-0.60/animations.md
+++ /dev/null
@@ -1,408 +0,0 @@
----
-id: animations
-title: 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 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 `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 [fadeAnim] = useState(new Animated.Value(0)) // Initial value for opacity: 0
-
- React.useEffect(() => {
- Animated.timing(
- fadeAnim,
- {
- toValue: 1,
- duration: 10000,
- }
- ).start();
- }, [])
-
- return (
-
- {props.children}
-
- );
-}
-
-// You can then use your `FadeInView` in place of a `View` in your components:
-export default () => {
- return (
-
-
- Fading in
-
-
- )
-}
-```
-
-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, only 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 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 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 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. 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 wrapper that 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 clear 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](/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.
-
-To use the native driver for normal animations 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
-
- {content}
-
-```
-
-You can see the native driver in action by running the [RNTester app](https://github.com/facebook/react-native/tree/0.60-stable/packages/rn-tester/), then loading the Native Animated Example. You can also take a look at the [source code](https://github.com/facebook/react-native/blob/0.60-stable/packages/rn-tester/js/examples/NativeAnimation/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
-
-
-
- Press me!
-
-
-
- );
- }
-}
-
-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/0.60-stable/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](/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 809cacfe1dd..00000000000
--- a/website/versioned_docs/version-0.60/app-extensions.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-id: app-extensions
-title: 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 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':
-
-
-
-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, you can quickly 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/appregistry.md b/website/versioned_docs/version-0.60/appregistry.md
deleted file mode 100644
index 0a1474b6b57..00000000000
--- a/website/versioned_docs/version-0.60/appregistry.md
+++ /dev/null
@@ -1,173 +0,0 @@
----
-id: appregistry
-title: AppRegistry
----
-
-
-
Project with Native Code Required
-
- This API only works in projects made with react-native init
- or in those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Expo documentation..
-
-
Current state is: {this.state.appState} ;
- }
-}
-```
-
-This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state, and the null state will happen only momentarily.
-
----
-
-# Reference
-
-## Events
-
-### `change`
-
-This even is received when the app state has changed. The listener is called with one of [the current app state values](appstate.md#app-states).
-
-### `focus`
-
-[Android only] Received when the app gains focus (the user is interacting with the app).
-
-### `blur`
-
-[Android only] Received when the user is not actively interacting with the app. Useful in situations when the user pulls down the [notification drawer](https://developer.android.com/guide/topics/ui/notifiers/notifications#bar-and-drawer). `AppState` won't change but the `blur` event will get fired.
-
-## Methods
-
-### `addEventListener()`
-
-```jsx
-addEventListener(type, handler);
-```
-
-Add a handler to AppState changes by listening to the `change` event type and providing the handler
-
-
-
----
-
-### `removeEventListener()`
-
-```jsx
-removeEventListener(type, handler);
-```
-
-Remove a handler by passing the `change` event type and the handler
-
-## Properties
-
-### `currentState`
-
-```jsx
-AppState.currentState;
-```
diff --git a/website/versioned_docs/version-0.60/asyncstorage.md b/website/versioned_docs/version-0.60/asyncstorage.md
deleted file mode 100644
index c233373ac06..00000000000
--- a/website/versioned_docs/version-0.60/asyncstorage.md
+++ /dev/null
@@ -1,365 +0,0 @@
----
-id: asyncstorage
-title: AsyncStorage
----
-
-> **Deprecated.** Use [react-native-community/react-native-async-storage](https://github.com/react-native-community/react-native-async-storage) instead.
-
-`AsyncStorage` is an unencrypted, asynchronous, persistent, key-value storage system that is global to the app. It should be used instead of LocalStorage.
-
-It is recommended that you use an abstraction on top of `AsyncStorage` instead of `AsyncStorage` directly for anything more than light usage since it operates globally.
-
-On iOS, `AsyncStorage` is backed by native code that stores small values in a serialized dictionary and larger values in separate files. On Android, `AsyncStorage` will use either [RocksDB](http://rocksdb.org/) or SQLite based on what is available.
-
-The `AsyncStorage` JavaScript code is a facade that provides a clear JavaScript API, real `Error` objects, and non-multi functions. Each method in the API returns a `Promise` object.
-
-Importing the `AsyncStorage` library:
-
-```jsx
-import {AsyncStorage} from 'react-native';
-```
-
-Persisting data:
-
-```jsx
-_storeData = async () => {
- try {
- await AsyncStorage.setItem(
- '@MySuperStore:key',
- 'I like to save it.',
- );
- } catch (error) {
- // Error saving data
- }
-};
-```
-
-Fetching data:
-
-```jsx
-_retrieveData = async () => {
- try {
- const value = await AsyncStorage.getItem('TASKS');
- if (value !== null) {
- // We have data!!
- console.log(value);
- }
- } catch (error) {
- // Error retrieving data
- }
-};
-```
-
----
-
-# Reference
-
-## Methods
-
-### `getItem()`
-
-```jsx
-static getItem(key: string, [callback]: ?(error: ?Error, result: ?string) => void)
-```
-
-Fetches an item for a `key` and invokes a callback upon completion. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ------------------------------------------- | -------- | ----------------------------------------------------------------- |
-| key | string | Yes | Key of the item to fetch. |
-| callback | `?(error: ?Error, result: ?string) => void` | No | Function that will be called with a result if found or any error. |
-
----
-
-### `setItem()`
-
-```jsx
-static setItem(key: string, value: string, [callback]: ?(error: ?Error) => void)
-```
-
-Sets the value for a `key` and invokes a callback upon completion. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------------------------- | -------- | -------------------------------------------- |
-| key | string | Yes | Key of the item to set. |
-| value | string | Yes | Value to set for the `key`. |
-| callback | `?(error: ?Error) => void` | No | Function that will be called with any error. |
-
----
-
-### `removeItem()`
-
-```jsx
-static removeItem(key: string, [callback]: ?(error: ?Error) => void)
-```
-
-Removes an item for a `key` and invokes a callback upon completion. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------------------------- | -------- | -------------------------------------------- |
-| key | string | Yes | Key of the item to remove. |
-| callback | `?(error: ?Error) => void` | No | Function that will be called with any error. |
-
----
-
-### `mergeItem()`
-
-```jsx
-static mergeItem(key: string, value: string, [callback]: ?(error: ?Error) => void)
-```
-
-Merges an existing `key` value with an input value, assuming both values are stringified JSON. Returns a `Promise` object.
-
-**NOTE:** This is not supported by all native implementations.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------------------------- | -------- | -------------------------------------------- |
-| key | string | Yes | Key of the item to modify. |
-| value | string | Yes | New value to merge for the `key`. |
-| callback | `?(error: ?Error) => void` | No | Function that will be called with any error. |
-
-Example:
-
-```jsx
-let UID123_object = {
- name: 'Chris',
- age: 30,
- traits: {hair: 'brown', eyes: 'brown'},
-};
-// You only need to define what will be added or updated
-let UID123_delta = {
- age: 31,
- traits: {eyes: 'blue', shoe_size: 10},
-};
-
-AsyncStorage.setItem(
- 'UID123',
- JSON.stringify(UID123_object),
- () => {
- AsyncStorage.mergeItem(
- 'UID123',
- JSON.stringify(UID123_delta),
- () => {
- AsyncStorage.getItem('UID123', (err, result) => {
- console.log(result);
- });
- },
- );
- },
-);
-
-// Console log result:
-// => {'name':'Chris','age':31,'traits':
-// {'shoe_size':10,'hair':'brown','eyes':'blue'}}
-```
-
----
-
-### `clear()`
-
-```jsx
-static clear([callback]: ?(error: ?Error) => void)
-```
-
-Erases _all_ `AsyncStorage` for all clients, libraries, etc. You probably don't want to call this; use `removeItem` or `multiRemove` to clear only your app's keys. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------------------------- | -------- | -------------------------------------------- |
-| callback | `?(error: ?Error) => void` | No | Function that will be called with any error. |
-
----
-
-### `getAllKeys()`
-
-```jsx
-static getAllKeys([callback]: ?(error: ?Error, keys: ?Array) => void)
-```
-
-Gets _all_ keys known to your app; for all callers, libraries, etc. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ------------------------------------------------ | -------- | --------------------------------------------------------------- |
-| callback | `?(error: ?Error, keys: ?Array) => void` | No | Function that will be called with all keys found and any error. |
-
----
-
-### `flushGetRequests()`
-
-```jsx
-static flushGetRequests(): [object Object]
-```
-
-Flushes any pending requests using a single batch call to get the data.
-
----
-
-### `multiGet()`
-
-```jsx
-static multiGet(keys: Array, [callback]: ?(errors: ?Array, result: ?Array>) => void)
-```
-
-This allows you to batch the fetching of items given an array of `key` inputs. Your callback will be invoked with an array of corresponding key-value pairs found:
-
-```
-multiGet(['k1', 'k2'], cb) -> cb([['k1', 'val1'], ['k2', 'val2']])
-```
-
-The method returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ----------------------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------- |
-| keys | `Array` | Yes | Array of key for the items to get. |
-| callback | `?(errors: ?Array, result: ?Array>) => void` | No | Function that will be called with a key-value array of the results, plus an array of any key-specific errors found. |
-
-Example:
-
-```jsx
-AsyncStorage.getAllKeys((err, keys) => {
- AsyncStorage.multiGet(keys, (err, stores) => {
- stores.map((result, i, store) => {
- // get at each store's key/value so you can work with it
- let key = store[i][0];
- let value = store[i][1];
- });
- });
-});
-```
-
----
-
-### `multiSet()`
-
-```jsx
-static multiSet(keyValuePairs: Array>, [callback]: ?(errors: ?Array) => void)
-```
-
-Use this as a batch operation for storing multiple key-value pairs. When the operation completes you'll get a single callback with any errors:
-
-```
-multiSet([['k1', 'val1'], ['k2', 'val2']], cb);
-```
-
-The method returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------------- | ---------------------------------- | -------- | ---------------------------------------------------------------------------- |
-| keyValuePairs | `Array>` | Yes | Array of key-value array for the items to set. |
-| callback | `?(errors: ?Array) => void` | No | Function that will be called with an array of any key-specific errors found. |
-
----
-
-### `multiRemove()`
-
-```jsx
-static multiRemove(keys: Array, [callback]: ?(errors: ?Array) => void)
-```
-
-Call this to batch the deletion of all keys in the `keys` array. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ---------------------------------- | -------- | ----------------------------------------------------------------------- |
-| keys | `Array` | Yes | Array of key for the items to delete. |
-| callback | `?(errors: ?Array) => void` | No | Function that will be called an array of any key-specific errors found. |
-
-Example:
-
-```jsx
-let keys = ['k1', 'k2'];
-AsyncStorage.multiRemove(keys, err => {
- // keys k1 & k2 removed, if they existed
- // do most stuff after removal (if you want)
-});
-```
-
----
-
-### `multiMerge()`
-
-```jsx
-static multiMerge(keyValuePairs: Array>, [callback]: ?(errors: ?Array) => void)
-```
-
-Batch operation to merge in existing and new values for a given set of keys. This assumes that the values are stringified JSON. Returns a `Promise` object.
-
-**NOTE**: This is not supported by all native implementations.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------------- | ---------------------------------- | -------- | ---------------------------------------------------------------------------- |
-| keyValuePairs | `Array>` | Yes | Array of key-value array for the items to merge. |
-| callback | `?(errors: ?Array) => void` | No | Function that will be called with an array of any key-specific errors found. |
-
-Example:
-
-```jsx
-// first user, initial values
-let UID234_object = {
- name: 'Chris',
- age: 30,
- traits: {hair: 'brown', eyes: 'brown'},
-};
-
-// first user, delta values
-let UID234_delta = {
- age: 31,
- traits: {eyes: 'blue', shoe_size: 10},
-};
-
-// second user, initial values
-let UID345_object = {
- name: 'Marge',
- age: 25,
- traits: {hair: 'blonde', eyes: 'blue'},
-};
-
-// second user, delta values
-let UID345_delta = {
- age: 26,
- traits: {eyes: 'green', shoe_size: 6},
-};
-
-let multi_set_pairs = [
- ['UID234', JSON.stringify(UID234_object)],
- ['UID345', JSON.stringify(UID345_object)],
-];
-let multi_merge_pairs = [
- ['UID234', JSON.stringify(UID234_delta)],
- ['UID345', JSON.stringify(UID345_delta)],
-];
-
-AsyncStorage.multiSet(multi_set_pairs, err => {
- AsyncStorage.multiMerge(multi_merge_pairs, err => {
- AsyncStorage.multiGet(['UID234', 'UID345'], (err, stores) => {
- stores.map((result, i, store) => {
- let key = store[i][0];
- let val = store[i][1];
- console.log(key, val);
- });
- });
- });
-});
-
-// Console log results:
-// => UID234 {"name":"Chris","age":31,"traits":{"shoe_size":10,"hair":"brown","eyes":"blue"}}
-// => UID345 {"name":"Marge","age":26,"traits":{"shoe_size":6,"hair":"blonde","eyes":"green"}}
-```
diff --git a/website/versioned_docs/version-0.60/backandroid.md b/website/versioned_docs/version-0.60/backandroid.md
deleted file mode 100644
index f8b7a3f6832..00000000000
--- a/website/versioned_docs/version-0.60/backandroid.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-id: backandroid
-title: BackAndroid
----
-
-Deprecated. Use BackHandler instead.
-
-### Methods
-
-- [`exitApp`](backandroid.md#exitapp)
-- [`addEventListener`](backandroid.md#addeventlistener)
-- [`removeEventListener`](backandroid.md#removeeventlistener)
-
----
-
-# Reference
-
-## Methods
-
-### `exitApp()`
-
-```jsx
-static exitApp()
-```
-
----
-
-### `addEventListener()`
-
-```jsx
-static addEventListener(eventName, handler)
-```
-
----
-
-### `removeEventListener()`
-
-```jsx
-static removeEventListener(eventName, handler)
-```
diff --git a/website/versioned_docs/version-0.60/backhandler.md b/website/versioned_docs/version-0.60/backhandler.md
deleted file mode 100644
index 2c9fc9db060..00000000000
--- a/website/versioned_docs/version-0.60/backhandler.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-id: backhandler
-title: BackHandler
----
-
-Detect hardware button presses for back navigation.
-
-Android: Detect hardware back button presses, and programmatically invoke the default back button functionality to exit the app if there are no listeners or if none of the listeners return true.
-
-tvOS: Detect presses of the menu button on the TV remote. (Still to be implemented: programmatically disable menu button handling functionality to exit the app if there are no listeners or if none of the listeners return true.)
-
-iOS: Not applicable.
-
-The event subscriptions are called in reverse order (i.e. last registered subscription first), and if one subscription returns true then subscriptions registered earlier will not be called. Beware: If your app shows an opened `Modal`, BackHandler will not publish any events ([see `Modal` docs](/docs/modal#onrequestclose)).
-
-Example:
-
-```jsx
-BackHandler.addEventListener('hardwareBackPress', function () {
- // this.onMainScreen and this.goBack are just examples, you need to use your own implementation here
- // Typically you would use the navigator here to go to the last state.
-
- if (!this.onMainScreen()) {
- this.goBack();
- return true;
- }
- return false;
-});
-```
-
-Lifecycle example:
-
-```jsx
- componentDidMount() {
- this.backHandler = BackHandler.addEventListener('hardwareBackPress', this.handleBackPress);
- }
-
- componentWillUnmount() {
- this.backHandler.remove()
- }
-
- handleBackPress = () => {
- this.goBack(); // works best when the goBack is async
- return true;
- }
-```
-
-Lifecycle alternative:
-
-```jsx
- componentDidMount() {
- this.backHandler = BackHandler.addEventListener('hardwareBackPress', () => {
- this.goBack(); // works best when the goBack is async
- return true;
- });
- }
-
- componentWillUnmount() {
- this.backHandler.remove();
- }
-```
-
----
-
-# Reference
-
-## Methods
-
-### `addEventListener()`
-
-```jsx
-static addEventListener(eventName, handler)
-```
-
----
-
-### `exitApp()`
-
-```jsx
-static exitApp()
-```
-
----
-
-### `removeEventListener()`
-
-```jsx
-static removeEventListener(eventName, handler)
-```
diff --git a/website/versioned_docs/version-0.60/building-for-tv.md b/website/versioned_docs/version-0.60/building-for-tv.md
deleted file mode 100644
index bc50241af3b..00000000000
--- a/website/versioned_docs/version-0.60/building-for-tv.md
+++ /dev/null
@@ -1,187 +0,0 @@
----
-id: building-for-tv
-title: Building For TV Devices
-hide_table_of_contents: true
----
-
-import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
-
-TV devices support has been implemented with the intention of making existing React Native applications work on Apple TV and Android TV, with few or no changes needed in the JavaScript code for the applications.
-
-
-
-
-
-## Build changes
-
-- _Native layer_: To run React Native project on Android TV make sure to make the following changes to `AndroidManifest.xml`
-
-```xml
-
-
- ...
-
- ...
-
-
- ...
-
-```
-
-- _JavaScript layer_: Support for Android TV has been added to `Platform.android.js`. You can check whether code is running on Android TV by doing
-
-```js
-var Platform = require('Platform');
-var running_on_android_tv = Platform.isTV;
-```
-
-## Code changes
-
-- _Access to touchable controls_: When running on Android TV the Android framework will automatically apply a directional navigation scheme based on relative position of focusable elements in your views. The `Touchable` mixin has code added to detect focus changes and use existing methods to style the components properly and initiate the proper actions when the view is selected using the TV remote, so `TouchableWithoutFeedback`, `TouchableHighlight`, `TouchableOpacity` and `TouchableNativeFeedback` will work as expected. In particular:
-
- - `onFocus` will be executed when the touchable view goes into focus
- - `onBlur` will be executed when the touchable view goes out of focus
- - `onPress` will be executed when the touchable view is actually selected by pressing the "select" button on the TV remote.
-
-- _TV remote/keyboard input_: A new native class, `ReactAndroidTVRootViewHelper`, sets up key events handlers for TV remote events. When TV remote events occur, this class fires a JS event. This event will be picked up by instances of the `TVEventHandler` JavaScript object. Application code that needs to implement custom handling of TV remote events can create an instance of `TVEventHandler` and listen for these events, as in the following code:
-
-```jsx
-var TVEventHandler = require('TVEventHandler');
-
-class Game2048 extends React.Component {
- _tvEventHandler: any;
-
- _enableTVEventHandler() {
- this._tvEventHandler = new TVEventHandler();
- this._tvEventHandler.enable(this, function (cmp, evt) {
- if (evt && evt.eventType === 'right') {
- cmp.setState({board: cmp.state.board.move(2)});
- } else if (evt && evt.eventType === 'up') {
- cmp.setState({board: cmp.state.board.move(1)});
- } else if (evt && evt.eventType === 'left') {
- cmp.setState({board: cmp.state.board.move(0)});
- } else if (evt && evt.eventType === 'down') {
- cmp.setState({board: cmp.state.board.move(3)});
- } else if (evt && evt.eventType === 'playPause') {
- cmp.restartGame();
- }
- });
- }
-
- _disableTVEventHandler() {
- if (this._tvEventHandler) {
- this._tvEventHandler.disable();
- delete this._tvEventHandler;
- }
- }
-
- componentDidMount() {
- this._enableTVEventHandler();
- }
-
- componentWillUnmount() {
- this._disableTVEventHandler();
- }
-}
-```
-
-- _Dev Menu support_: On the simulator, cmd-M will bring up the developer menu, similar to Android. To bring it up on a real Android TV device, press the menu button or long press the fast-forward button on the remote. (Please do not shake the Android TV device, that will not work :) )
-
-- _Known issues_:
-
- - `InputText` components do not work for now (i.e. they cannot receive focus).
-
-
-
-
-> **Deprecated.** Use [react-native-tvos](https://github.com/react-native-community/react-native-tvos) instead. For the details please check the [0.62 release blog post](https://reactnative.dev/blog/#moving-apple-tv-to-react-native-tvos).
-
-## Build changes
-
-- _Native layer_: React Native Xcode projects all now have Apple TV build targets, with names ending in the string '-tvOS'.
-
-- _react-native init_: New React Native projects created with `react-native init` will have Apple TV target automatically created in their XCode projects.
-
-- _JavaScript layer_: Support for Apple TV has been added to `Platform.ios.js`. You can check whether code is running on AppleTV by doing
-
-```jsx
-var Platform = require('Platform');
-var running_on_tv = Platform.isTV;
-
-// If you want to be more specific and only detect devices running tvOS
-// (but no Android TV devices) you can use:
-var running_on_apple_tv = Platform.isTVOS;
-```
-
-## Code changes
-
-- _General support for tvOS_: Apple TV specific changes in native code are all wrapped by the TARGET_OS_TV define. These include changes to suppress APIs that are not supported on tvOS (e.g. web views, sliders, switches, status bar, etc.), and changes to support user input from the TV remote or keyboard.
-
-- _Common codebase_: Since tvOS and iOS share most Objective-C and JavaScript code in common, most documentation for iOS applies equally to tvOS.
-
-- _Access to touchable controls_: When running on Apple TV, the native view class is `RCTTVView`, which has additional methods to make use of the tvOS focus engine. The `Touchable` mixin has code added to detect focus changes and use existing methods to style the components properly and initiate the proper actions when the view is selected using the TV remote, so `TouchableWithoutFeedback`, `TouchableHighlight` and `TouchableOpacity` will work as expected. In particular:
-
- - `onFocus` will be executed when the touchable view goes into focus
- - `onBlur` will be executed when the touchable view goes out of focus
- - `onPress` will be executed when the touchable view is actually selected by pressing the "select" button on the TV remote.
-
-- _TV remote/keyboard input_: A new native class, `RCTTVRemoteHandler`, sets up gesture recognizers for TV remote events. When TV remote events occur, this class fires notifications that are picked up by `RCTTVNavigationEventEmitter` (a subclass of `RCTEventEmitter`), that fires a JS event. This event will be picked up by instances of the `TVEventHandler` JavaScript object. Application code that needs to implement custom handling of TV remote events can create an instance of `TVEventHandler` and listen for these events, as in the following code:
-
-```jsx
-var TVEventHandler = require('TVEventHandler');
-
-class Game2048 extends React.Component {
- _tvEventHandler: any;
-
- _enableTVEventHandler() {
- this._tvEventHandler = new TVEventHandler();
- this._tvEventHandler.enable(this, function (cmp, evt) {
- if (evt && evt.eventType === 'right') {
- cmp.setState({board: cmp.state.board.move(2)});
- } else if (evt && evt.eventType === 'up') {
- cmp.setState({board: cmp.state.board.move(1)});
- } else if (evt && evt.eventType === 'left') {
- cmp.setState({board: cmp.state.board.move(0)});
- } else if (evt && evt.eventType === 'down') {
- cmp.setState({board: cmp.state.board.move(3)});
- } else if (evt && evt.eventType === 'playPause') {
- cmp.restartGame();
- }
- });
- }
-
- _disableTVEventHandler() {
- if (this._tvEventHandler) {
- this._tvEventHandler.disable();
- delete this._tvEventHandler;
- }
- }
-
- componentDidMount() {
- this._enableTVEventHandler();
- }
-
- componentWillUnmount() {
- this._disableTVEventHandler();
- }
-}
-```
-
-- _Dev Menu support_: On the simulator, cmd-D will bring up the developer menu, similar to iOS. To bring it up on a real Apple TV device, make a long press on the play/pause button on the remote. (Please do not shake the Apple TV device, that will not work :) )
-
-- _TV remote animations_: `RCTTVView` native code implements Apple-recommended parallax animations to help guide the eye as the user navigates through views. The animations can be disabled or adjusted with new optional view properties.
-
-- _Back navigation with the TV remote menu button_: The `BackHandler` component, originally written to support the Android back button, now also supports back navigation on the Apple TV using the menu button on the TV remote.
-
-- _TabBarIOS behavior_: The `TabBarIOS` component wraps the native `UITabBar` API, which works differently on Apple TV. To avoid jittery re-rendering of the tab bar in tvOS (see [this issue](https://github.com/facebook/react-native/issues/15081)), the selected tab bar item can only be set from JavaScript on initial render, and is controlled after that by the user through native code.
-
-- _Known issues_:
-
- - [ListView scrolling](https://github.com/facebook/react-native/issues/12793). The issue can be worked around by setting `removeClippedSubviews` to false in ListView and similar components. For more discussion of this issue, see [this PR](https://github.com/facebook/react-native/pull/12944).
-
-
-
diff --git a/website/versioned_docs/version-0.60/button.md b/website/versioned_docs/version-0.60/button.md
deleted file mode 100644
index b2d33dc3262..00000000000
--- a/website/versioned_docs/version-0.60/button.md
+++ /dev/null
@@ -1,237 +0,0 @@
----
-id: button
-title: Button
----
-
-A basic button component that should render nicely on any platform. Supports a minimal level of customization.
-
-If this button doesn't look right for your app, you can build your own button using [TouchableOpacity](touchableopacity.md) or [TouchableNativeFeedback](touchablenativefeedback.md). For inspiration, look at the [source code for this button component](https://github.com/facebook/react-native/blob/0.60-stable/Libraries/Components/Button.js). Or, take a look at the [wide variety of button components built by the community](https://js.coach/?menu%5Bcollections%5D=React%20Native&page=1&query=button).
-
-### Example
-
-```SnackPlayer name=rn-buttons
-import React from 'react';
-import {
- StyleSheet,
- Button,
- View,
- SafeAreaView,
- Text,
- Alert,
-} from 'react-native';
-import Constants from 'expo-constants';
-
-function Separator() {
- return
-
-
- The title and onPress handler are required. It is recommended to set
- accessibilityLabel to help make your app usable by everyone.
-
- Alert.alert('Simple Button pressed')}
- />
-
-
-
- Adjust the color in a way that looks standard on each platform. On
- iOS, the color prop controls the color of the text. On Android, the
- color adjusts the backgroud color of the button.
-
- Alert.alert('Button with adjusted color pressed')}
- />
-
-
-
- All interaction for the component are disabled.
-
- Alert.alert('Cannot press this one')}
- />
-
-
-
- This layout strategy lets the title define the width of the button.
-
-
- Alert.alert('Left button pressed')}
- />
- Alert.alert('Right button pressed')}
- />
-
-
-
- );
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- marginTop: Constants.statusBarHeight,
- marginHorizontal: 16,
- },
- title: {
- textAlign: 'center',
- marginVertical: 8,
- },
- fixToText: {
- flexDirection: 'row',
- justifyContent: 'space-between',
- },
- separator: {
- marginVertical: 8,
- borderBottomColor: '#737373',
- borderBottomWidth: StyleSheet.hairlineWidth,
- },
-});
-```
-
----
-
-# Reference
-
-## Props
-
-### `onPress`
-
-Handler to be called when the user taps the button
-
-| Type | Required |
-| -------- | -------- |
-| function | Yes |
-
----
-
-### `title`
-
-Text to display inside the button
-
-| Type | Required |
-| ------ | -------- |
-| string | Yes |
-
----
-
-### `accessibilityLabel`
-
-Text to display for blindness accessibility features
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `color`
-
-Color of the text (iOS), or background color of the button (Android)
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `disabled`
-
-If true, disable all interactions for this component.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `testID`
-
-Used to locate this view in end-to-end tests.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `hasTVPreferredFocus`
-
-_(Apple TV only)_ TV preferred focus (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
-### `nextFocusDown`
-
-Designates the next view to receive focus when the user navigates down. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusDown).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusForward`
-
-Designates the next view to receive focus when the user navigates forward. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusForward).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusLeft`
-
-Designates the next view to receive focus when the user navigates left. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusLeft).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusRight`
-
-Designates the next view to receive focus when the user navigates right. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusRight).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusUp`
-
-Designates the next view to receive focus when the user navigates up. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusUp).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `touchSoundDisabled`
-
-If true, doesn't play system sound on touch.
-
-| Type | Required | Platform |
-| ------- | -------- | -------- |
-| boolean | No | Android |
diff --git a/website/versioned_docs/version-0.60/cameraroll.md b/website/versioned_docs/version-0.60/cameraroll.md
deleted file mode 100644
index a2a8502b891..00000000000
--- a/website/versioned_docs/version-0.60/cameraroll.md
+++ /dev/null
@@ -1,144 +0,0 @@
----
-id: cameraroll
-title: '🚧 CameraRoll'
-
-custom_edit_url: 'https://github.com/facebook/react-native-website/edit/master/website/versioned_docs/version-0.58/cameraroll.md'
----
-
-> **Deprecated.** Use [@react-native-community/cameraroll](https://github.com/react-native-community/react-native-cameraroll) instead.
-
-`CameraRoll` provides access to the local camera roll or photo library.
-
-On iOS, the `CameraRoll` API requires the `RCTCameraRoll` library to be linked. You can refer to [Linking Libraries (iOS)](linking-libraries-ios.md) to learn more.
-
-### Permissions
-
-The user's permission is required in order to access the Camera Roll on devices running iOS 10 or later. Add the `NSPhotoLibraryUsageDescription` key in your `Info.plist` with a string that describes how your app will use this data. This key will appear as `Privacy - Photo Library Usage Description` in Xcode.
-
-If you are targeting devices running iOS 11 or later, you will also need to add the `NSPhotoLibraryAddUsageDescription` key in your `Info.plist`. Use this key to define a string that describes how your app will use this data. By adding this key to your `Info.plist`, you will be able to request write-only access permission from the user. If you try to save to the camera roll without this permission, your app will exit.
-
----
-
-# Reference
-
-## Methods
-
-### `saveToCameraRoll()`
-
-```jsx
-CameraRoll.saveToCameraRoll(tag, [type]);
-```
-
-Saves the photo or video to the camera roll or photo library.
-
-On Android, the tag must be a local image or video URI, such as `"file:///sdcard/img.png"`.
-
-On iOS, the tag can be any image URI (including local, remote asset-library and base64 data URIs) or a local video file URI (remote or data URIs are not supported for saving video at this time).
-
-If the tag has a file extension of .mov or .mp4, it will be inferred as a video. Otherwise it will be treated as a photo. To override the automatic choice, you can pass an optional `type` parameter that must be one of 'photo' or 'video'.
-
-Returns a Promise which will resolve with the new URI.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ---- | ---------------------- | -------- | ---------------------------------------------------------- |
-| tag | string | Yes | See above. |
-| type | enum('photo', 'video') | No | Overrides automatic detection based on the file extension. |
-
----
-
-### `getPhotos()`
-
-```jsx
-CameraRoll.getPhotos(params);
-```
-
-Returns a Promise with photo identifier objects from the local camera roll of the device matching shape defined by `getPhotosReturnChecker`.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ------------------------------------------------ |
-| params | object | Yes | Expects a params with the shape described below. |
-
-- `first` : {number} : The number of photos wanted in reverse order of the photo application (i.e. most recent first for SavedPhotos).
-- `after` : {string} : A cursor that matches `page_info { end_cursor }` returned from a previous call to `getPhotos`.
-- `groupTypes` : {string} : Specifies which group types to filter the results to. Valid values are:
- - `Album`
- - `All`
- - `Event`
- - `Faces`
- - `Library`
- - `PhotoStream`
- - `SavedPhotos` // default
-- `groupName` : {string} : Specifies filter on group names, like 'Recent Photos' or custom album titles.
-- `assetType` : {string} : Specifies filter on asset type. Valid values are:
- - `All`
- - `Videos`
- - `Photos` // default
-- `mimeTypes` : {Array} : Filter by mimetype (e.g. image/jpeg).
-
-Returns a Promise which when resolved will be of the following shape:
-
-- `edges` : `{Array}` An array of node objects
- - `node`: {object} An object with the following shape:
- - `type`: {string}
- - `group_name`: {string}
- - `image`: {object} : An object with the following shape:
- - `uri`: {string}
- - `height`: {number}
- - `width`: {number}
- - `isStored`: {boolean}
- - `playableDuration`: {number}
- - `timestamp`: {number}
- - `location`: {object} : An object with the following shape:
- - `latitude`: {number}
- - `longitude`: {number}
- - `altitude`: {number}
- - `heading`: {number}
- - `speed`: {number}
-- `page_info` : {object} : An object with the following shape:
- - `has_next_page`: {boolean}
- - `start_cursor`: {string}
- - `end_cursor`: {string}
-
-#### Example
-
-Loading images:
-
-```jsx
-_handleButtonPress = () => {
- CameraRoll.getPhotos({
- first: 20,
- assetType: 'Photos',
- })
- .then(r => {
- this.setState({ photos: r.edges });
- })
- .catch((err) => {
- //Error Loading Images
- });
- };
-render() {
- return (
-
-
- {this.state.photos.map((p, i) => {
- return (
-
-
- );
-}
-```
diff --git a/website/versioned_docs/version-0.60/checkbox.md b/website/versioned_docs/version-0.60/checkbox.md
deleted file mode 100644
index b095184cead..00000000000
--- a/website/versioned_docs/version-0.60/checkbox.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: checkbox
-title: CheckBox
----
-
-Renders a boolean input (Android only).
-
-This is a controlled component that requires an `onValueChange` callback that updates the `value` prop in order for the component to reflect user actions. If the `value` prop is not updated, the component will continue to render the supplied `value` prop instead of the expected result of any user actions.
-
-@keyword checkbox @keyword toggle
-
-### Props
-
-- [View props...](view.md#props)
-
-* [`disabled`](checkbox.md#disabled)
-* [`onChange`](checkbox.md#onchange)
-* [`onValueChange`](checkbox.md#onvaluechange)
-* [`testID`](checkbox.md#testid)
-* [`value`](checkbox.md#value)
-
----
-
-# Reference
-
-## Props
-
-### `disabled`
-
-If true the user won't be able to toggle the checkbox. Default value is false.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `onChange`
-
-Used in case the props change removes the component.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onValueChange`
-
-Invoked with the new value when the value changes.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `testID`
-
-Used to locate this view in end-to-end tests.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `value`
-
-The value of the checkbox. If true the checkbox will be turned on. Default value is false.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
diff --git a/website/versioned_docs/version-0.60/clipboard.md b/website/versioned_docs/version-0.60/clipboard.md
deleted file mode 100644
index 8847a77bb1c..00000000000
--- a/website/versioned_docs/version-0.60/clipboard.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-id: clipboard
-title: Clipboard
----
-
-`Clipboard` gives you an interface for setting and getting content from Clipboard on both Android and iOS
-
----
-
-# Reference
-
-## Methods
-
-### `getString()`
-
-```jsx
-static getString()
-```
-
-Get content of string type, this method returns a `Promise`, so you can use following code to get clipboard content
-
-```jsx
-async _getContent() {
- var content = await Clipboard.getString();
-}
-```
-
----
-
-### `setString()`
-
-```jsx
-static setString(content)
-```
-
-Set content of string type. You can use following code to set clipboard content
-
-```jsx
-_setContent() {
- Clipboard.setString('hello world');
-}
-```
-
-@param the content to be stored in the clipboard.
diff --git a/website/versioned_docs/version-0.60/colors.md b/website/versioned_docs/version-0.60/colors.md
deleted file mode 100644
index e02172d982f..00000000000
--- a/website/versioned_docs/version-0.60/colors.md
+++ /dev/null
@@ -1,184 +0,0 @@
----
-id: colors
-title: Color Reference
----
-
-Components in React Native are [styled using JavaScript](style.md). Color properties usually match how [CSS works on the web](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value).
-
-### Red-green-blue
-
-React Native supports `rgb()` and `rgba()` in both hexadecimal and functional notation:
-
-- `'#f0f'` (#rgb)
-- `'#ff00ff'` (#rrggbb)
-
-- `'rgb(255, 0, 255)'`
-- `'rgba(255, 255, 255, 1.0)'`
-
-- `'#f0ff'` (#rgba)
-- `'#ff00ff00'` (#rrggbbaa)
-
-### Hue-saturation-lightness
-
-`hsl()` and `hsla()` is supported in functional notation:
-
-- `'hsl(360, 100%, 100%)'`
-- `'hsla(360, 100%, 100%, 1.0)'`
-
-### `transparent`
-
-This is a shortcut for `rgba(0,0,0,0)`:
-
-- `'transparent'`
-
-### Named colors
-
-You can also use color names as values. React Native follows the [CSS3 specification](http://www.w3.org/TR/css3-color/#svg-color):
-
-
-
--  imageList = new ArrayList(Arrays.asList(
- "http://foo.com/bar1.png",
- "http://foo.com/bar2.png"
- ));
- initialProperties.putStringArrayList("images", imageList);
- return initialProperties;
- }
- };
- }
-}
-```
-
-```jsx
-import React from 'react';
-import {View, Image} from 'react-native';
-
-export default class ImageBrowserApp extends React.Component {
- renderImage(imgURI) {
- return {this.props.images.map(this.renderImage)} ;
- }
-}
-```
-
-`ReactRootView` 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.
-
-```java
-Bundle updatedProps = mReactRootView.getAppProperties();
-ArrayList imageList = new ArrayList(Arrays.asList(
- "http://foo.com/bar3.png",
- "http://foo.com/bar4.png"
-));
-updatedProps.putStringArrayList("images", imageList);
-
-mReactRootView.setAppProperties(updatedProps);
-```
-
-It is fine to update properties anytime. However, updates have to be performed on the main thread. You use the getter on any thread.
-
-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-android.md#3-expose-view-property-setters-using-reactprop-or-reactpropgroup-annotation). In short, properties that are to be reflected in JavaScript needs to be exposed as setter method annotated with `@ReactProp`, then 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-android.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-android.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).
-
-### Calling native functions from React Native (native modules)
-
-Native modules are Java 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-android.md).
-
-> **_Warning_**: All native modules share the same namespace. Watch out for name collisions when creating new ones.
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 3ed2a0277a6..00000000000
--- a/website/versioned_docs/version-0.60/communication-ios.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: communication-ios
-title: Communication between native and React Native
----
-
-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 specific, 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 {this.props.images.map(this.renderImage)} ;
- }
-}
-```
-
-`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 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/0.60-stable/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). To summarize, 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/0.60-stable/packages/rn-tester/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 separate 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 3b934df9aba..00000000000
--- a/website/versioned_docs/version-0.60/components-and-apis.md
+++ /dev/null
@@ -1,291 +0,0 @@
----
-id: components-and-apis
-title: Components and APIs
----
-
-React Native provides a number of [Core Components](intro-react-native-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.
-
-
-
-## User Interface
-
-Render common user interface controls on any platform using the following components. For platform specific components, keep reading.
-
-
-
-## List Views
-
-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.
-
-
-
-## iOS Components and APIs
-
-Many of the following components provide wrappers for commonly used UIKit classes.
-
-
-
-## Android Components and APIs
-
-Many of the following components provide wrappers for commonly used Android classes.
-
-
-
-## 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.
-
-
diff --git a/website/versioned_docs/version-0.60/custom-webview-android.md b/website/versioned_docs/version-0.60/custom-webview-android.md
deleted file mode 100644
index 6bec3b8e976..00000000000
--- a/website/versioned_docs/version-0.60/custom-webview-android.md
+++ /dev/null
@@ -1,261 +0,0 @@
----
-id: custom-webview-android
-title: Custom WebView
----
-
-While the built-in web view has a lot of features, it is not possible to handle every use-case in React Native. You can, however, extend the web view with native code without forking React Native or duplicating all the existing web view code.
-
-Before you do this, you should be familiar with the concepts in [native UI components](native-components-android). You should also familiarise yourself with the [native code for web views](https://github.com/facebook/react-native/blob/0.60-stable/ReactAndroid/src/main/java/com/facebook/react/views/webview/ReactWebViewManager.java), as you will have to use this as a reference when implementing new features—although a deep understanding is not required.
-
-## Native Code
-
-To get started, you'll need to create a subclass of `ReactWebViewManager`, `ReactWebView`, and `ReactWebViewClient`. In your view manager, you'll then need to override:
-
-- `createReactWebViewInstance`
-- `getName`
-- `addEventEmitters`
-
-```java
-@ReactModule(name = CustomWebViewManager.REACT_CLASS)
-public class CustomWebViewManager extends ReactWebViewManager {
- /* This name must match what we're referring to in JS */
- protected static final String REACT_CLASS = "RCTCustomWebView";
-
- protected static class CustomWebViewClient extends ReactWebViewClient { }
-
- protected static class CustomWebView extends ReactWebView {
- public CustomWebView(ThemedReactContext reactContext) {
- super(reactContext);
- }
- }
-
- @Override
- protected ReactWebView createReactWebViewInstance(ThemedReactContext reactContext) {
- return new CustomWebView(reactContext);
- }
-
- @Override
- public String getName() {
- return REACT_CLASS;
- }
-
- @Override
- protected void addEventEmitters(ThemedReactContext reactContext, WebView view) {
- view.setWebViewClient(new CustomWebViewClient());
- }
-}
-```
-
-You'll need to follow the usual steps to [register the module](native-modules-android.md#register-the-module).
-
-### Adding New Properties
-
-To add a new property, you'll need to add it to `CustomWebView`, and then expose it in `CustomWebViewManager`.
-
-```java
-public class CustomWebViewManager extends ReactWebViewManager {
- ...
-
- protected static class CustomWebView extends ReactWebView {
- public CustomWebView(ThemedReactContext reactContext) {
- super(reactContext);
- }
-
- protected @Nullable String mFinalUrl;
-
- public void setFinalUrl(String url) {
- mFinalUrl = url;
- }
-
- public String getFinalUrl() {
- return mFinalUrl;
- }
- }
-
- ...
-
- @ReactProp(name = "finalUrl")
- public void setFinalUrl(WebView view, String url) {
- ((CustomWebView) view).setFinalUrl(url);
- }
-}
-```
-
-### Adding New Events
-
-For events, you'll first need to make create event subclass.
-
-```java
-// NavigationCompletedEvent.java
-public class NavigationCompletedEvent extends Event {
- private WritableMap mParams;
-
- public NavigationCompletedEvent(int viewTag, WritableMap params) {
- super(viewTag);
- this.mParams = params;
- }
-
- @Override
- public String getEventName() {
- return "navigationCompleted";
- }
-
- @Override
- public void dispatch(RCTEventEmitter rctEventEmitter) {
- init(getViewTag());
- rctEventEmitter.receiveEvent(getViewTag(), getEventName(), mParams);
- }
-}
-```
-
-You can trigger the event in your web view client. You can hook existing handlers if your events are based on them.
-
-You should refer to [ReactWebViewManager.java](https://github.com/facebook/react-native/blob/0.60-stable/ReactAndroid/src/main/java/com/facebook/react/views/webview/ReactWebViewManager.java) in the React Native codebase to see what handlers are available and how they are implemented. You can extend any methods here to provide extra functionality.
-
-```java
-public class NavigationCompletedEvent extends Event {
- private WritableMap mParams;
-
- public NavigationCompletedEvent(int viewTag, WritableMap params) {
- super(viewTag);
- this.mParams = params;
- }
-
- @Override
- public String getEventName() {
- return "navigationCompleted";
- }
-
- @Override
- public void dispatch(RCTEventEmitter rctEventEmitter) {
- init(getViewTag());
- rctEventEmitter.receiveEvent(getViewTag(), getEventName(), mParams);
- }
-}
-
-// CustomWebViewManager.java
-protected static class CustomWebViewClient extends ReactWebViewClient {
- @Override
- public boolean shouldOverrideUrlLoading(WebView view, String url) {
- boolean shouldOverride = super.shouldOverrideUrlLoading(view, url);
- String finalUrl = ((CustomWebView) view).getFinalUrl();
-
- if (!shouldOverride && url != null && finalUrl != null && new String(url).equals(finalUrl)) {
- final WritableMap params = Arguments.createMap();
- dispatchEvent(view, new NavigationCompletedEvent(view.getId(), params));
- }
-
- return shouldOverride;
- }
-}
-```
-
-Finally, you'll need to expose the events in `CustomWebViewManager` through `getExportedCustomDirectEventTypeConstants`. Note that currently, the default implementation returns `null`, but this may change in the future.
-
-```java
-public class CustomWebViewManager extends ReactWebViewManager {
- ...
-
- @Override
- public @Nullable
- Map getExportedCustomDirectEventTypeConstants() {
- Map export = super.getExportedCustomDirectEventTypeConstants();
- if (export == null) {
- export = MapBuilder.newHashMap();
- }
- export.put("navigationCompleted", MapBuilder.of("registrationName", "onNavigationCompleted"));
- return export;
- }
-}
-```
-
-## JavaScript Interface
-
-To use your custom web view, you'll need to create a class for it. Your class must:
-
-- Export all the prop types from `WebView.propTypes`
-- Return a `WebView` component with the prop `nativeConfig.component` set to your native component (see below)
-
-To get your native component, you must use `requireNativeComponent`: the same as for regular custom components. However, you must pass in an extra third argument, `WebView.extraNativeComponentConfig`. This third argument contains prop types that are only required for native code.
-
-```jsx
-import React, {Component, PropTypes} from 'react';
-import {WebView, requireNativeComponent} from 'react-native';
-
-export default class CustomWebView extends Component {
- static propTypes = WebView.propTypes;
-
- render() {
- return (
-
-
-@interface RCTCustomWebView : RCTWebView
-
-@end
-
-// RCTCustomWebView.m
-#import "RCTCustomWebView.h"
-
-@interface RCTCustomWebView ()
-
-@end
-
-@implementation RCTCustomWebView { }
-
-@end
-```
-
-For the view manager, you need to make a subclass `RCTWebViewManager`. You must still include:
-
-- `(UIView *)view` that returns your custom view
-- The `RCT_EXPORT_MODULE()` tag
-
-```objc
-// RCTCustomWebViewManager.h
-#import
-
-@interface RCTCustomWebViewManager : RCTWebViewManager
-
-@end
-
-// RCTCustomWebViewManager.m
-#import "RCTCustomWebViewManager.h"
-#import "RCTCustomWebView.h"
-
-@interface RCTCustomWebViewManager ()
-
-@end
-
-@implementation RCTCustomWebViewManager { }
-
-RCT_EXPORT_MODULE()
-
-- (UIView *)view
-{
- RCTCustomWebView *webView = [RCTCustomWebView new];
- webView.delegate = self;
- return webView;
-}
-
-@end
-```
-
-### Adding New Events and Properties
-
-Adding new properties and events is the same as regular UI components. For properties, you define an `@property` in the header. For events, you define a `RCTDirectEventBlock` in the view's `@interface`.
-
-```objc
-// RCTCustomWebView.h
-@property (nonatomic, copy) NSString *finalUrl;
-
-// RCTCustomWebView.m
-@interface RCTCustomWebView ()
-
-@property (nonatomic, copy) RCTDirectEventBlock onNavigationCompleted;
-
-@end
-```
-
-Then expose it in the view manager's `@implementation`.
-
-```objc
-// RCTCustomWebViewManager.m
-RCT_EXPORT_VIEW_PROPERTY(onNavigationCompleted, RCTDirectEventBlock)
-RCT_EXPORT_VIEW_PROPERTY(finalUrl, NSString)
-```
-
-### Extending Existing Events
-
-You should refer to [RCTWebView.m](https://github.com/facebook/react-native/blob/0.60-stable/React/Views/RCTWebView.m) in the React Native codebase to see what handlers are available and how they are implemented. You can extend any methods here to provide extra functionality.
-
-By default, most methods aren't exposed from RCTWebView. If you need to expose them, you need to create an [Objective C category](https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/CustomizingExistingClasses/CustomizingExistingClasses.html), and then expose all the methods you need to use.
-
-```objc
-// RCTWebView+Custom.h
-#import
-
-@interface RCTWebView (Custom)
-- (BOOL)webView:(__unused UIWebView *)webView shouldStartLoadWithRequest:(NSURLRequest *)request navigationType:(UIWebViewNavigationType)navigationType;
-- (NSMutableDictionary *)baseEvent;
-@end
-```
-
-Once these are exposed, you can reference them in your custom web view class.
-
-```objc
-// RCTCustomWebView.m
-
-// Remember to import the category file.
-#import "RCTWebView+Custom.h"
-
-- (BOOL)webView:(__unused UIWebView *)webView shouldStartLoadWithRequest:(NSURLRequest *)request
- navigationType:(UIWebViewNavigationType)navigationType
-{
- BOOL allowed = [super webView:webView shouldStartLoadWithRequest:request navigationType:navigationType];
-
- if (allowed) {
- NSString* url = request.URL.absoluteString;
- if (url && [url isEqualToString:_finalUrl]) {
- if (_onNavigationCompleted) {
- NSMutableDictionary *event = [self baseEvent];
- _onNavigationCompleted(event);
- }
- }
- }
-
- return allowed;
-}
-```
-
-## JavaScript Interface
-
-To use your custom web view, you'll need to create a class for it. Your class must:
-
-- Export all the prop types from `WebView.propTypes`
-- Return a `WebView` component with the prop `nativeConfig.component` set to your native component (see below)
-
-To get your native component, you must use `requireNativeComponent`: the same as for regular custom components. However, you must pass in an extra third argument, `WebView.extraNativeComponentConfig`. This third argument contains prop types that are only required for native code.
-
-```jsx
-import React, {Component, PropTypes} from 'react';
-import {
- WebView,
- requireNativeComponent,
- NativeModules,
-} from 'react-native';
-const {CustomWebViewManager} = NativeModules;
-
-export default class CustomWebView extends Component {
- static propTypes = WebView.propTypes;
-
- render() {
- return (
-
-
- );
- }
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- justifyContent: 'center',
- },
-});
-```
-
-
-
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
-
-
Required
| string |
-| handler Required
| function |
-
-**Example:**
-
-```jsx
-DevSettings.addMenuItem('Show Secret Dev Screen', () => {
- Alert.alert('Showing secret dev screen!');
-});
-```
-
----
-
-### `reload()`
-
-```jsx
-static reload()
-```
-
-Reload the application. Can be invoked directly or on user interaction.
-
-**Example:**
-
-```jsx
- DevSettings.reload()} />
-```
diff --git a/website/versioned_docs/version-0.60/dimensions.md b/website/versioned_docs/version-0.60/dimensions.md
deleted file mode 100644
index 235045952a6..00000000000
--- a/website/versioned_docs/version-0.60/dimensions.md
+++ /dev/null
@@ -1,172 +0,0 @@
----
-id: dimensions
-title: Dimensions
----
-
-import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
-
-```jsx
-import {Dimensions} from 'react-native';
-```
-
-You can get the application window's width and height using below code:
-
-```jsx
-const windowWidth = Dimensions.get('window').width;
-const windowHeight = Dimensions.get('window').height;
-```
-
-> Although dimensions are available immediately, they may change (e.g due to device rotation, foldable devices etc) so any rendering logic or styles that depend on these constants should try to call this function on every render, rather than caching the value (for example, using inline styles rather than setting a value in a `StyleSheet`).
-
-If you are targeting foldable devices or devices which can change the screen size or app window size, you can use the event listener available in the Dimensions module as shown in the below example.
-
-### Example
-
-
-
-
-```SnackPlayer name=Dimensions
-import React, { useState, useEffect } from "react";
-import { View, StyleSheet, Text, Dimensions } from "react-native";
-
-const window = Dimensions.get("window");
-const screen = Dimensions.get("screen");
-
-export default function App() {
- const [dimensions, setDimensions] = useState({ window, screen });
-
- const onChange = ({ window, screen }) => {
- setDimensions({ window, screen });
- };
-
- useEffect(() => {
- Dimensions.addEventListener("change", onChange);
- return () => {
- Dimensions.removeEventListener("change", onChange);
- };
- });
-
- return (
-
- {`Window Dimensions: height - ${dimensions.window.height}, width - ${dimensions.window.width}`}
- {`Screen Dimensions: height - ${dimensions.screen.height}, width - ${dimensions.screen.width}`}
-
- );
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- justifyContent: "center",
- alignItems: "center"
- }
-});
-```
-
-
-
-
-```SnackPlayer name=Dimensions
-import React, { Component } from "react";
-import { View, StyleSheet, Text, Dimensions } from "react-native";
-
-const window = Dimensions.get("window");
-const screen = Dimensions.get("screen");
-
-export default class App extends Component {
- state = {
- dimensions: {
- window,
- screen
- }
- };
-
- onChange = ({ window, screen }) => {
- this.setState({ dimensions: { window, screen } });
- };
-
- componentDidMount() {
- Dimensions.addEventListener("change", this.onChange);
- }
-
- componentWillUnmount() {
- Dimensions.removeEventListener("change", this.onChange);
- }
-
- render() {
- const { dimensions } = this.state;
-
- return (
-
- {`Window Dimensions: height - ${dimensions.window.height}, width - ${dimensions.window.width}`}
- {`Screen Dimensions: height - ${dimensions.screen.height}, width - ${dimensions.screen.width}`}
-
- );
- }
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- justifyContent: "center",
- alignItems: "center"
- }
-});
-```
-
-
-
-
-# Reference
-
-## Methods
-
-### `addEventListener()`
-
-```jsx
-static addEventListener(type, handler)
-```
-
-Add an event handler. Supported events:
-
-- `change`: Fires when a property within the `Dimensions` object changes. The argument to the event handler is an object with `window` and `screen` properties whose values are the same as the return values of `Dimensions.get('window')` and `Dimensions.get('screen')`, respectively.
-
----
-
-### `get()`
-
-```jsx
-static get(dim)
-```
-
-Initial dimensions are set before `runApplication` is called so they should be available before any other require's are run, but may be updated later.
-
-> Note: Although dimensions are available immediately, they may change (e.g due to device rotation) so any rendering logic or styles that depend on these constants should try to call this function on every render, rather than caching the value (for example, using inline styles rather than setting a value in a `StyleSheet`).
-
-Example: `var {height, width} = Dimensions.get('window');`
-
-@param {string} dim Name of dimension as defined when calling `set`. @returns {Object?} Value for the dimension.
-
-> For Android the `window` dimension will exclude the size used by the `status bar` (if not translucent) and `bottom navigation bar`
-
----
-
-### `removeEventListener()`
-
-```jsx
-static removeEventListener(type, handler)
-```
-
-Remove an event handler.
-
----
-
-### `set()`
-
-```jsx
-static set(dims)
-```
-
-This should only be called from native code by sending the didUpdateDimensions event.
-
-@param {object} dims string-keyed object of dimensions to set
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 351debda0e0..00000000000
--- a/website/versioned_docs/version-0.60/direct-manipulation.md
+++ /dev/null
@@ -1,206 +0,0 @@
----
-id: direct-manipulation
-title: 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/0.60-stable/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
-
-
- Press me!
-
-
-```
-
-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 (
- this.setState({myButtonOpacity: 0.5})}
- onPressOut={() => this.setState({myButtonOpacity: 1})}>
-
- Press me!
-
-
- )
-}
-```
-
-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/0.60-stable/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 (
-
- {this.props.label}
-
- )
- }
-}
-
-export default class App extends React.Component {
- render() {
- return (
-
-
- )
- }
-}
-```
-
-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 (
- this._root = component} {...this.props}>
- {this.props.label}
-
- )
- }
-}
-
-export default class App extends React.Component {
- render() {
- return (
-
-
- )
- }
-}
-```
-
-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 (
-
- this._textInput = component}
- style={{height: 50, width: 200, marginHorizontal: 20, borderWidth: 1, borderColor: '#ccc'}}
- />
-
- Clear text
-
-
- );
- }
-}
-```
-
-## 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/drawerlayoutandroid.md b/website/versioned_docs/version-0.60/drawerlayoutandroid.md
deleted file mode 100644
index dd6e9927578..00000000000
--- a/website/versioned_docs/version-0.60/drawerlayoutandroid.md
+++ /dev/null
@@ -1,182 +0,0 @@
----
-id: drawerlayoutandroid
-title: DrawerLayoutAndroid
----
-
-React component that wraps the platform `DrawerLayout` (Android only). The Drawer (typically used for navigation) is rendered with `renderNavigationView` and direct children are the main view (where your content goes). The navigation view is initially not visible on the screen, but can be pulled in from the side of the window specified by the `drawerPosition` prop and its width can be set by the `drawerWidth` prop.
-
-Example:
-
-```jsx
-render: function() {
- var navigationView = (
-
- I'm in the Drawer!
-
- );
- return (
- navigationView}>
-
- Hello
- World!
-
-
- );
-},
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `renderNavigationView`
-
-The navigation view that will be rendered to the side of the screen and can be pulled in.
-
-| Type | Required |
-| -------- | -------- |
-| function | Yes |
-
----
-
-### `onDrawerClose`
-
-Function called whenever the navigation view has been closed.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `drawerPosition`
-
-Specifies the side of the screen from which the drawer will slide in.
-
-| Type | Required |
-| ------------------------------------------------------------------------- | -------- |
-| enum(DrawerConsts.DrawerPosition.Left, DrawerConsts.DrawerPosition.Right) | No |
-
----
-
-### `drawerWidth`
-
-Specifies the width of the drawer, more precisely the width of the view that be pulled in from the edge of the window.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `keyboardDismissMode`
-
-Determines whether the keyboard gets dismissed in response to a drag.
-
-- 'none' (the default), drags do not dismiss the keyboard.
-- 'on-drag', the keyboard is dismissed when a drag begins.
-
-| Type | Required |
-| ----------------------- | -------- |
-| enum('none', 'on-drag') | No |
-
----
-
-### `drawerLockMode`
-
-Specifies the lock mode of the drawer. The drawer can be locked in 3 states:
-
-- unlocked (default), meaning that the drawer will respond (open/close) to touch gestures.
-- locked-closed, meaning that the drawer will stay closed and not respond to gestures.
-- locked-open, meaning that the drawer will stay opened and not respond to gestures. The drawer may still be opened and closed programmatically (`openDrawer`/`closeDrawer`).
-
-| Type | Required |
-| ------------------------------------------------ | -------- |
-| enum('unlocked', 'locked-closed', 'locked-open') | No |
-
----
-
-### `onDrawerOpen`
-
-Function called whenever the navigation view has been opened.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onDrawerSlide`
-
-Function called whenever there is an interaction with the navigation view.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onDrawerStateChanged`
-
-Function called when the drawer state has changed. The drawer can be in 3 states:
-
-- idle, meaning there is no interaction with the navigation view happening at the time
-- dragging, meaning there is currently an interaction with the navigation view
-- settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `drawerBackgroundColor`
-
-Specifies the background color of the drawer. The default value is `white`. If you want to set the opacity of the drawer, use rgba. Example:
-
-```jsx
-return (
- `](sectionlist.md).
-
-### 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 (
-
- {title}
-
- );
-}
-
-export default function App() {
- return (
-
-
- );
-}
-
-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 `` usage for perf optimization and avoiding bugs.
-
-- 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.
-
-```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 (
- onSelect(id)}
- style={[
- styles.item,
- { backgroundColor: selected ? '#6e3b6e' : '#f9c2ff' },
- ]}
- >
- {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],
- );
-
- return (
-
- (
-
- );
-}
-
-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.md), and thus inherits its props (as well as those of [``](scrollview.md)) that aren't explicitly listed here, along with the following caveats:
-
-- Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.
-- This is a `PureComponent` which means that it will not re-render if `props` remain shallow-equal. Make sure that everything your `renderItem` function depends on is passed as a prop (e.g. `extraData`) that is not `===` after updates, otherwise your UI may not update on changes. This includes the `data` prop and parent component state.
-- In order to constrain memory and enable smooth scrolling, content is rendered asynchronously offscreen. This means it's possible to scroll faster than the fill rate and momentarily see blank content. This is a tradeoff that can be adjusted to suit the needs of each application, and we are working on improving it behind the scenes.
-- By default, the list looks for a `key` prop on each item and uses that for the React key. Alternatively, you can provide a custom `keyExtractor` prop.
-
----
-
-# Reference
-
-## Props
-
-Inherits [ScrollView Props](scrollview.md#props), unless it is nested in another FlatList of same orientation.
-
-### `renderItem`
-
-```jsx
-renderItem({item, index, separators});
-```
-
-Takes an item from `data` and renders it into the list.
-
-Provides additional metadata like `index` if you need it, as well as a more generic `separators.updateProps` function which let you set whatever props you want to change the rendering of either the leading separator or trailing separator in case the more common `highlight` and `unhighlight` (which set the `highlighted: boolean` prop) are insufficient for your use case.
-
-| Type | Required |
-| -------- | -------- |
-| function | Yes |
-
-- `item` (Object): The item from `data` being rendered.
-- `index` (number): The index corresponding to this item in the `data` array.
-- `separators` (Object)
- - `highlight` (Function)
- - `unhighlight` (Function)
- - `updateProps` (Function)
- - `select` (enum('leading', 'trailing'))
- - `newProps` (Object)
-
-Example usage:
-
-```jsx
- (
- this._onPress(item)}
- onShowUnderlay={separators.highlight}
- onHideUnderlay={separators.unhighlight}>
-
- {item.title}
-
-
- )}
-/>
-```
-
----
-
-### `data`
-
-For simplicity, data is a plain array. If you want to use something else, like an immutable list, use the underlying [`VirtualizedList`](virtualizedlist.md) directly.
-
-| Type | Required |
-| ----- | -------- |
-| array | Yes |
-
----
-
-### `ItemSeparatorComponent`
-
-Rendered in between each item, but not at the top or bottom. By default, `highlighted` and `leadingItem` props are provided. `renderItem` provides `separators.highlight`/`unhighlight` which will update the `highlighted` prop, but you can also add custom props with `separators.updateProps`.
-
-| Type | Required |
-| --------- | -------- |
-| component | No |
-
----
-
-### `ListEmptyComponent`
-
-Rendered when the list is empty. Can be a React Component (e.g. `SomeComponent`), or a React element (e.g. ` Note: Cannot scroll to locations outside the render window without specifying the `getItemLayout` prop.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ----------- |
-| params | object | Yes | See below. |
-
-Valid `params` keys are:
-
-- 'animated' (boolean) - Whether the list should do an animation while scrolling. Defaults to `true`.
-- 'index' (number) - The index to scroll to. Required.
-- 'viewOffset' (number) - A fixed number of pixels to offset the final target position.
-- 'viewPosition' (number) - A value of `0` places the item specified by index at the top, `1` at the bottom, and `0.5` centered in the middle.
-
----
-
-### `scrollToItem()`
-
-```jsx
-scrollToItem(params);
-```
-
-Requires linear scan through data - use `scrollToIndex` instead if possible.
-
-> Note: Cannot scroll to locations outside the render window without specifying the `getItemLayout` prop.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ----------- |
-| params | object | Yes | See below. |
-
-Valid `params` keys are:
-
-- 'animated' (boolean) - Whether the list should do an animation while scrolling. Defaults to `true`.
-- 'item' (object) - The item to scroll to. Required.
-- 'viewPosition' (number)
-
----
-
-### `scrollToOffset()`
-
-```jsx
-scrollToOffset(params);
-```
-
-Scroll to a specific content pixel offset in the list.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ----------- |
-| params | object | Yes | See below. |
-
-Valid `params` keys are:
-
-- 'offset' (number) - The offset to scroll to. In case of `horizontal` being true, the offset is the x-value, in any other case the offset is the y-value. Required.
-- 'animated' (boolean) - Whether the list should do an animation while scrolling. Defaults to `true`.
-
----
-
-### `recordInteraction()`
-
-```jsx
-recordInteraction();
-```
-
-Tells the list an interaction has occurred, which should trigger viewability calculations, e.g. if `waitForInteractions` is true and the user has not scrolled. This is typically called by taps on items or by navigation actions.
-
----
-
-### `flashScrollIndicators()`
-
-```jsx
-flashScrollIndicators();
-```
-
-Displays the scroll indicators momentarily.
-
----
-
-### `getScrollResponder()`
-
-```jsx
-getScrollResponder();
-```
-
-Provides a handle to the underlying scroll responder.
-
----
-
-### `getScrollableNode()`
-
-```jsx
-getScrollableNode();
-```
-
-Provides a handle to the underlying scroll node.
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 dd158b2b751..00000000000
--- a/website/versioned_docs/version-0.60/flexbox.md
+++ /dev/null
@@ -1,228 +0,0 @@
----
-id: flexbox
-title: Layout with 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`](/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 Direction
-
-[`flexDirection`](/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`.
-
-
- );
- }
-};
-```
-
-
-
-### 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`](/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`.
-
-
- );
- }
-};
-```
-
-
-
-#### Align Items
-
-[`alignItems`](/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`.
-
-
- );
- }
-};
-```
-
-
-
-### Align Self
-
-[`alignSelf`](/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 Content
-
-[alignContent](/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)
-
-
-
-### Flex Wrap
-
-The [`flexWrap`](/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 Basis, Grow, and Shrink
-
-- [`flexGrow`](/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`](/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`](/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.
-
-
-
-#### 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/geolocation.md b/website/versioned_docs/version-0.60/geolocation.md
deleted file mode 100644
index a969adfe4e6..00000000000
--- a/website/versioned_docs/version-0.60/geolocation.md
+++ /dev/null
@@ -1,171 +0,0 @@
----
-id: geolocation
-title: '🚧 Geolocation'
----
-
-> **Deprecated.** Use [@react-native-community/geolocation](https://github.com/react-native-community/react-native-geolocation) instead.
-
-The Geolocation API extends the [Geolocation web spec](https://developer.mozilla.org/en-US/docs/Web/API/Geolocation).
-
-As a browser polyfill, this API is available through the `navigator.geolocation` global - you do not need to `import` it.
-
-On Android, this uses the [android.location API](https://developer.android.com/reference/android/location/package-summary). This API is not recommended by Google because it is less accurate and slower than the recommended [Google Location Services API](https://developer.android.com/training/location/). In order to use it with React Native, use the [react-native-geolocation-service](https://github.com/Agontuk/react-native-geolocation-service) module.
-
-### Configuration and Permissions
-
-
-
Projects with Native Code Only
-
- This section only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
-
-
- Android API >= 23 Requires an additional step to check for, and request
- the ACCESS_FINE_LOCATION permission using
- the PermissionsAndroid API .
- Failure to do so may result in a hard crash.
-
-
-### Methods
-
-- [`setRNConfiguration`](#setrnconfiguration)
-- [`requestAuthorization`](#requestauthorization)
-- [`getCurrentPosition`](#getcurrentposition)
-- [`watchPosition`](#watchposition)
-- [`clearWatch`](#clearwatch)
-- [`stopObserving`](#stopobserving)
-
----
-
-# Reference
-
-## Methods
-
-### `setRNConfiguration()`
-
-```jsx
-geolocation.setRNConfiguration(config);
-```
-
-Sets configuration options that will be used in all location requests.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ----------- |
-| config | object | Yes | See below. |
-
-Supported options:
-
-- `skipPermissionRequests` (boolean, iOS-only) - Defaults to `false`. If `true`, you must request permissions before using Geolocation APIs.
-
----
-
-### `requestAuthorization()`
-
-```jsx
-geolocation.requestAuthorization();
-```
-
-Request suitable Location permission based on the key configured on pList. If NSLocationAlwaysUsageDescription is set, it will request Always authorization, although if NSLocationWhenInUseUsageDescription is set, it will request InUse authorization.
-
----
-
-### `getCurrentPosition()`
-
-```jsx
-geolocation.getCurrentPosition(
- geo_success,
- [geo_error],
- [geo_options],
-);
-```
-
-Invokes the success callback once with the latest location info.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----------- | -------- | -------- | ----------------------------------------- |
-| geo_success | function | Yes | Invoked with latest location info. |
-| geo_error | function | No | Invoked whenever an error is encountered. |
-| geo_options | object | No | See below. |
-
-Supported options:
-
-- `timeout` (ms) - Is a positive value representing the maximum length of time (in milliseconds) the device is allowed to take in order to return a position. Defaults to INFINITY.
-- `maximumAge` (ms) - Is a positive value indicating the maximum age in milliseconds of a possible cached position that is acceptable to return. If set to 0, it means that the device cannot use a cached position and must attempt to retrieve the real current position. If set to Infinity the device will always return a cached position regardless of its age. Defaults to INFINITY.
-- `enableHighAccuracy` (bool) - Is a boolean representing if to use GPS or not. If set to true, a GPS position will be requested. If set to false, a WIFI location will be requested.
-
----
-
-### `watchPosition()`
-
-```jsx
-geolocation.watchPosition(success, [error], [options]);
-```
-
-Invokes the success callback whenever the location changes. Returns a `watchId` (number).
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------- | -------- | -------- | ----------------------------------------- |
-| success | function | Yes | Invoked whenever the location changes. |
-| error | function | No | Invoked whenever an error is encountered. |
-| options | object | No | See below. |
-
-Supported options:
-
-- `timeout` (ms) - Is a positive value representing the maximum length of time (in milliseconds) the device is allowed to take in order to return a position. Defaults to INFINITY.
-- `maximumAge` (ms) - Is a positive value indicating the maximum age in milliseconds of a possible cached position that is acceptable to return. If set to 0, it means that the device cannot use a cached position and must attempt to retrieve the real current position. If set to Infinity the device will always return a cached position regardless of its age. Defaults to INFINITY.
-- `enableHighAccuracy` (bool) - Is a boolean representing if to use GPS or not. If set to true, a GPS position will be requested. If set to false, a WIFI location will be requested.
-- `distanceFilter` (m) - The minimum distance from the previous location to exceed before returning a new location. Set to 0 to not filter locations. Defaults to 100m.
-- `useSignificantChanges` (bool) - Uses the battery-efficient native significant changes APIs to return locations. Locations will only be returned when the device detects a significant distance has been breached. Defaults to FALSE.
-
----
-
-### `clearWatch()`
-
-```jsx
-geolocation.clearWatch(watchID);
-```
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------- | ------ | -------- | ------------------------------------ |
-| watchID | number | Yes | Id as returned by `watchPosition()`. |
-
----
-
-### `stopObserving()`
-
-```jsx
-geolocation.stopObserving();
-```
-
-Stops observing for device location changes. In addition, it removes all listeners previously registered.
-
-Notice that this method has only effect if the `geolocation.watchPosition(successCallback, errorCallback)` method was previously invoked.
diff --git a/website/versioned_docs/version-0.60/gesture-responder-system.md b/website/versioned_docs/version-0.60/gesture-responder-system.md
deleted file mode 100644
index ed29d81c7ca..00000000000
--- a/website/versioned_docs/version-0.60/gesture-responder-system.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: gesture-responder-system
-title: Gesture Responder System
----
-
-The gesture responder system manages the lifecycle of gestures in your app. A touch can go through several phases as the app determines what the user's intention is. For example, the app needs to determine if the touch is scrolling, sliding on a widget, or tapping. This can even change during the duration of a touch. There can also be multiple simultaneous touches.
-
-The touch responder system is needed to allow components to negotiate these touch interactions without any additional knowledge about their parent or child components.
-
-### Best Practices
-
-To make your app feel great, every action should have the following attributes:
-
-- Feedback/highlighting- show the user what is handling their touch, and what will happen when they release the gesture
-- Cancel-ability- when making an action, the user should be able to abort it mid-touch by dragging their finger away
-
-These features make users more comfortable while using an app, because it allows people to experiment and interact without fear of making mistakes.
-
-### TouchableHighlight and Touchable\*
-
-The responder system can be complicated to use. So we have provided an abstract `Touchable` implementation for things that should be "tappable". This uses the responder system and allows you to configure tap interactions declaratively. Use `TouchableHighlight` anywhere where you would use a button or link on web.
-
-## Responder Lifecycle
-
-A view can become the touch responder by implementing the correct negotiation methods. There are two methods to ask the view if it wants to become responder:
-
-- `View.props.onStartShouldSetResponder: (evt) => true,` - Does this view want to become responder on the start of a touch?
-- `View.props.onMoveShouldSetResponder: (evt) => true,` - Called for every touch move on the View when it is not the responder: does this view want to "claim" touch responsiveness?
-
-If the View returns true and attempts to become the responder, one of the following will happen:
-
-- `View.props.onResponderGrant: (evt) => {}` - The View is now responding for touch events. This is the time to highlight and show the user what is happening
-- `View.props.onResponderReject: (evt) => {}` - Something else is the responder right now and will not release it
-
-If the view is responding, the following handlers can be called:
-
-- `View.props.onResponderMove: (evt) => {}` - The user is moving their finger
-- `View.props.onResponderRelease: (evt) => {}` - Fired at the end of the touch, ie "touchUp"
-- `View.props.onResponderTerminationRequest: (evt) => true` - Something else wants to become responder. Should this view release the responder? Returning true allows release
-- `View.props.onResponderTerminate: (evt) => {}` - The responder has been taken from the View. Might be taken by other views after a call to `onResponderTerminationRequest`, or might be taken by the OS without asking (happens with control center/ notification center on iOS)
-
-`evt` is a synthetic touch event with the following form:
-
-- `nativeEvent`
- - `changedTouches` - Array of all touch events that have changed since the last event
- - `identifier` - The ID of the touch
- - `locationX` - The X position of the touch, relative to the element
- - `locationY` - The Y position of the touch, relative to the element
- - `pageX` - The X position of the touch, relative to the root element
- - `pageY` - The Y position of the touch, relative to the root element
- - `target` - The node id of the element receiving the touch event
- - `timestamp` - A time identifier for the touch, useful for velocity calculation
- - `touches` - Array of all current touches on the screen
-
-### Capture ShouldSet Handlers
-
-`onStartShouldSetResponder` and `onMoveShouldSetResponder` are called with a bubbling pattern, where the deepest node is called first. That means that the deepest component will become responder when multiple Views return true for `*ShouldSetResponder` handlers. This is desirable in most cases, because it makes sure all controls and buttons are usable.
-
-However, sometimes a parent will want to make sure that it becomes responder. This can be handled by using the capture phase. Before the responder system bubbles up from the deepest component, it will do a capture phase, firing `on*ShouldSetResponderCapture`. So if a parent View wants to prevent the child from becoming responder on a touch start, it should have a `onStartShouldSetResponderCapture` handler which returns true.
-
-- `View.props.onStartShouldSetResponderCapture: (evt) => true,`
-- `View.props.onMoveShouldSetResponderCapture: (evt) => true,`
-
-### PanResponder
-
-For higher-level gesture interpretation, check out [PanResponder](panresponder.md).
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 5981cdd0cd7..00000000000
--- a/website/versioned_docs/version-0.60/getting-started.md
+++ /dev/null
@@ -1,192 +0,0 @@
----
-id: enviroment-setup
-title: Getting Started
-hide_table_of_contents: true
----
-
-import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
-
-import GuideLinuxAndroid from './\_getting-started-linux-android.md'; import GuideMacOSAndroid from './\_getting-started-macos-android.md'; import GuideWindowsAndroid from './\_getting-started-windows-android.md'; import GuideMacOSIOS from './\_getting-started-macos-ios.md';
-
-This page will help you install and build your first React Native app.
-
-**If you are new to mobile development**, 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/).
-
-**If you are already familiar with mobile development**, 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.
-
-
-
-
-Assuming that you have [Node 12 LTS](https://nodejs.org/en/download/) or greater installed, you can use npm to install the Expo CLI command line utility:
-
-
-
-
-```shell
-npm install -g expo-cli
-```
-
-
-
-
-```shell
-yarn global add expo-cli
-```
-
-
-
-
-Then run the following commands to create a new React Native project called "AwesomeProject":
-
-
-
-
-```shell
-expo init AwesomeProject
-
-cd AwesomeProject
-npm start # you can also use: expo start
-```
-
-
-
-
-```shell
-expo init AwesomeProject
-
-cd AwesomeProject
-yarn start # you can also use: expo start
-```
-
-
-
-
-This will start a development server for you.
-
-Running your React Native application
-
-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, use the built-in QR code scanner of the Camera app.
-
-Modifying your app
-
-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!
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-Now what?
-
-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, check out the [Introduction to React Native](getting-started).
-
-Running your app on a simulator or virtual device
-
-Expo CLI allows you 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
-
-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 need to "[eject](https://docs.expo.io/versions/latest/workflow/customizing/)" 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/overview/#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.
-
-
-
-
-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 Expo, you'll need this section.
-
-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 Android and iOS, that's fine - you can pick one to start with, since the setup is a bit different.
-
-#### Development OS
-
-
-
-
-#### Target OS
-
-
-
-
-[//]: # 'macOS, Android'
-
-
-
-
-[//]: # 'macOS, iOS'
-
-
-
-
-
-
-
-#### Target OS
-
-
-
-
-[//]: # 'Windows, Android'
-
-
-
-
-[//]: # 'Windows, iOS'
-
-## Unsupported
-
-> A Mac is required to build projects with native code for iOS. You can follow the **Expo CLI Quickstart** to learn how to build your app using Expo instead.
-
-
-
-
-
-
-
-#### Target OS
-
-
-
-
-[//]: # 'Linux, Android'
-
-
-
-
-[//]: # 'Linux, iOS'
-
-## Unsupported
-
-> A Mac is required to build projects with native code for iOS. You can follow the **Expo CLI Quickstart** to learn how to build your app using Expo instead.
-
-
-
-
-
-
-
-
-
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 e45efb18f08..00000000000
--- a/website/versioned_docs/version-0.60/handling-text-input.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-id: handling-text-input
-title: Handling Text Input
----
-
-[`TextInput`](textinput#content) is a [Core Component](intro-react-native-components) 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 (
-
- this.setState({text})}
- value={this.state.text}
- />
-
- {this.state.text.split(' ').map((word) => word && '🍕').join(' ')}
-
-
- );
- }
-}
-```
-
-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/handling-touches.md b/website/versioned_docs/version-0.60/handling-touches.md
deleted file mode 100644
index c9e82a8f1be..00000000000
--- a/website/versioned_docs/version-0.60/handling-touches.md
+++ /dev/null
@@ -1,174 +0,0 @@
----
-id: handling-touches
-title: Handling Touches
----
-
-Users interact with mobile apps mainly through touch. They can use a combination of gestures, such as tapping on a button, scrolling a list, or zooming on a map. React Native provides components to handle all sorts of common gestures, as well as a comprehensive [gesture responder system](gesture-responder-system.md) to allow for more advanced gesture recognition, but the one component you will most likely be interested in is the basic Button.
-
-## Displaying a basic button
-
-[Button](button.md) provides a basic button component that is rendered nicely on all platforms. The minimal example to display a button looks like this:
-
-```jsx
- {
- alert('You tapped the button!');
- }}
- title="Press Me"
-/>
-```
-
-This will render a blue label on iOS, and a blue rounded rectangle with light text on Android. Pressing the button will call the "onPress" function, which in this case displays an alert popup. If you like, you can specify a "color" prop to change the color of your button.
-
-
-
-Go ahead and play around with the `Button` component using the example below. You can select which platform your app is previewed in by clicking on the toggle in the bottom right, then click on "Tap to Play" to preview the app.
-
-```SnackPlayer name=Button%20Basics
-import React, { Component } from 'react';
-import { Button, StyleSheet, View } from 'react-native';
-
-export default class ButtonBasics extends Component {
- _onPressButton() {
- alert('You tapped the button!')
- }
-
- render() {
- return (
-
-
-
-
-
-
-
-
- );
- }
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- justifyContent: 'center',
- },
- buttonContainer: {
- margin: 20
- },
- alternativeLayoutButtonContainer: {
- margin: 20,
- flexDirection: 'row',
- justifyContent: 'space-between'
- }
-});
-```
-
-## Touchables
-
-If the basic button doesn't look right for your app, you can build your own button using any of the "Touchable" components provided by React Native. The "Touchable" components provide the capability to capture tapping gestures, and can display feedback when a gesture is recognized. These components do not provide any default styling, however, so you will need to do a bit of work to get them looking nicely in your app.
-
-Which "Touchable" component you use will depend on what kind of feedback you want to provide:
-
-- Generally, you can use [**TouchableHighlight**](touchablehighlight.md) anywhere you would use a button or link on web. The view's background will be darkened when the user presses down on the button.
-
-- You may consider using [**TouchableNativeFeedback**](touchablenativefeedback.md) on Android to display ink surface reaction ripples that respond to the user's touch.
-
-- [**TouchableOpacity**](touchableopacity.md) can be used to provide feedback by reducing the opacity of the button, allowing the background to be seen through while the user is pressing down.
-
-- If you need to handle a tap gesture but you don't want any feedback to be displayed, use [**TouchableWithoutFeedback**](touchablewithoutfeedback.md).
-
-In some cases, you may want to detect when a user presses and holds a view for a set amount of time. These long presses can be handled by passing a function to the `onLongPress` props of any of the "Touchable" components.
-
-Let's see all of these in action:
-
-```SnackPlayer name=Touchables
-import React, { Component } from 'react';
-import { Platform, StyleSheet, Text, TouchableHighlight, TouchableOpacity, TouchableNativeFeedback, TouchableWithoutFeedback, View } from 'react-native';
-
-export default class Touchables extends Component {
- _onPressButton() {
- alert('You tapped the button!')
- }
-
- _onLongPressButton() {
- alert('You long-pressed the button!')
- }
-
-
- render() {
- return (
-
-
-
- TouchableHighlight
-
-
-
-
- TouchableOpacity
-
-
-
-
- TouchableNativeFeedback {Platform.OS !== 'android' ? '(Android only)' : ''}
-
-
-
-
- TouchableWithoutFeedback
-
-
-
-
- Touchable with Long Press
-
-
-
- );
- }
-}
-
-const styles = StyleSheet.create({
- container: {
- paddingTop: 60,
- alignItems: 'center'
- },
- button: {
- marginBottom: 30,
- width: 260,
- alignItems: 'center',
- backgroundColor: '#2196F3'
- },
- buttonText: {
- textAlign: 'center',
- padding: 20,
- color: 'white'
- }
-});
-```
-
-## Scrolling lists, swiping pages, and pinch-to-zoom
-
-Another gesture commonly used in mobile apps is the swipe or pan. This gesture allows the user to scroll through a list of items, or swipe through pages of content. In order to handle these and other gestures, we'll learn [how to use a ScrollView](using-a-scrollview.md) next.
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 08da2fbc25a..00000000000
--- a/website/versioned_docs/version-0.60/headless-js-android.md
+++ /dev/null
@@ -1,186 +0,0 @@
----
-id: headless-js-android
-title: Headless JS
----
-
-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 an 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:
-
-```
-
-
-
-
-```
-
-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 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 35dc5459e96..00000000000
--- a/website/versioned_docs/version-0.60/height-and-width.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-id: height-and-width
-title: 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 (
-
-
- );
- }
-}
-```
-
-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`?
-
-
- );
- }
-}
-```
-
-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/hermes.md b/website/versioned_docs/version-0.60/hermes.md
deleted file mode 100644
index 8f1cc5b7478..00000000000
--- a/website/versioned_docs/version-0.60/hermes.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-id: hermes
-title: Using Hermes
----
-
-
-
-
-[Hermes](https://hermesengine.dev) is an open-source JavaScript engine optimized for running React Native apps on Android. For many apps, 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.
-
-> ## Note for RN compatibility.
->
-> Each Hermes release is aimed at a specific RN version. The rule of thumb is to always follow [Hermes releases](https://github.com/facebook/hermes/releases) strictly. Version mismatch can result in instant crash of your apps in the worst case scenario.
-
-> ## Note for Windows users.
->
-> Hermes requires [Microsoft Visual C++ 2015 Redistributable](https://www.microsoft.com/en-us/download/details.aspx?id=48145)
-
-## Enabling 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](/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.
-
-Edit your `android/app/build.gradle` file and make the change illustrated below:
-
-```diff
- project.ext.react = [
- entryFile: "index.js",
-- enableHermes: false // clean and rebuild if changing
-+ enableHermes: true // clean and rebuild if changing
- ]
-```
-
-Also, if you're using ProGuard, you will need to add this rule in `proguard-rules.pro` :
-
-```
--keep class com.facebook.hermes.unicode.** { *; }
-```
-
-Next, if you've already built your app at least once, clean the build:
-
-```shellell
-$ cd android && ./gradlew clean
-```
-
-That's it! You should now be able to develop and deploy your app as normal:
-
-```shellell
-$ react-native run-android
-```
-
-## Confirming Hermes is in use
-
-If you've recently created a new app from scratch you should see if Hermes is enabled in the welcome view:
-
-
-
-A `HermesInternal` global variable will be available in JavaScript that can be used to verify that Hermes is in use:
-
-```jsx
-const isHermes = () => global.HermesInternal != null;
-```
-
-To see the benefits of Hermes, try making a release build/deployment of your app to compare. For example:
-
-```shellell
-$ react-native run-android --variant release
-```
-
-This will compile JavaScript to bytecode during build time which will improve your app's startup speed on device.
-
-## Debugging Hermes using Google Chrome's DevTools
-
-Hermes supports the Chrome debugger by implementing the Chrome inspector protocol. This means Chrome's tools can be used to directly debug JavaScript running on Hermes, on an emulator or device.
-
-Chrome connects to Hermes running on device via Metro, so you'll need to know where Metro is listening. Typically this will be on `localhost:8081`, but this is [configurable](https://facebook.github.io/metro/docs/en/configuration). When running `yarn start` the address is written to stdout on startup.
-
-Once you know where the Metro server is listening, you can connect with Chrome using the following steps:
-
-1. Navigate to `chrome://inspect` in a Chrome browser instance.
-
-2. Use the `Configure...` button to add the Metro server address (typically `localhost:8081` as described above).
-
-
-
-
-
-3. You should now see a "Hermes React Native" target with an "inspect" link which can be used to bring up debugger. If you don't see the "inspect" link, make sure the Metro server is running. 
-
-4. You can now use the Chrome debug tools. For example, to breakpoint the next time some JavaScript is run, click on the pause button and trigger an action in your app which would cause JavaScript to execute. 
diff --git a/website/versioned_docs/version-0.60/image-style-props.md b/website/versioned_docs/version-0.60/image-style-props.md
deleted file mode 100644
index 71249b4e147..00000000000
--- a/website/versioned_docs/version-0.60/image-style-props.md
+++ /dev/null
@@ -1,144 +0,0 @@
----
-id: image-style-props
-title: Image Style Props
----
-
-# Reference
-
-## Props
-
-### `borderTopRightRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `backfaceVisibility`
-
-| Type | Required |
-| ------------------------- | -------- |
-| enum('visible', 'hidden') | No |
-
----
-
-### `borderBottomLeftRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderBottomRightRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderColor`
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `borderRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderTopLeftRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `backgroundColor`
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `borderWidth`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `opacity`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `overflow`
-
-| Type | Required |
-| ------------------------- | -------- |
-| enum('visible', 'hidden') | No |
-
----
-
-### `resizeMode`
-
-Determines how to resize the image when the frame doesn't match the raw image dimensions.
-
-- `cover`: Scale the image uniformly (maintain the image's aspect ratio) so that:
-
- - Both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding)
- - At least one dimension of the scaled image will be equal to the corresponding dimension of the view (minus padding)
-
-- `contain`: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).
-
-- `stretch`: Scale width and height independently, This may change the aspect ratio of the src.
-
-- `repeat`: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio, unless it is larger than the view, in which case it will be scaled down uniformly so that it is contained in the view.
-
-- `center`: Center the image in the view along both dimensions. If the image is larger than the view, scale it down uniformly so that it is contained in the view.
-
-| Type | Required |
-| ------------------------------------------------------- | -------- |
-| enum('cover', 'contain', 'stretch', 'repeat', 'center') | No |
-
----
-
-### `tintColor`
-
-Changes the color of all the non-transparent pixels to the tintColor.
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `overlayColor`
-
-When the image has rounded corners, specifying an overlayColor will cause the remaining space in the corners to be filled with a solid color. This is useful in cases which are not supported by the Android implementation of rounded corners:
-
-- Certain resize modes, such as 'contain'
-- Animated GIFs
-
-A typical way to use this prop is with images displayed on a solid background and setting the `overlayColor` to the same color as the background.
-
-For details of how this works under the hood, see https://frescolib.org/docs/rounded-corners-and-circles.html
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| string | No | Android |
diff --git a/website/versioned_docs/version-0.60/image.md b/website/versioned_docs/version-0.60/image.md
deleted file mode 100644
index 0750dad8bc8..00000000000
--- a/website/versioned_docs/version-0.60/image.md
+++ /dev/null
@@ -1,484 +0,0 @@
----
-id: image
-title: Image
----
-
-A React component for displaying different types of images, including network images, static resources, temporary local images, and images from local disk, such as the camera roll.
-
-This example shows fetching and displaying an image from local storage as well as one from network and even from data provided in the `'data:'` uri scheme.
-
-> Note that for network and data images, you will need to manually specify the dimensions of your image!
-
-```SnackPlayer name=Image
-import React, { Component } from 'react';
-import { View, Image } from 'react-native';
-
-export default class DisplayAnImage extends Component {
- render() {
- return (
-
-
- );
- }
-}
-```
-
-You can also add `style` to an image:
-
-```SnackPlayer name=Image
-import React, { Component } from 'react';
-import { View, Image, StyleSheet } from 'react-native';
-
-const styles = StyleSheet.create({
- stretch: {
- width: 50,
- height: 200,
- resizeMode: 'stretch'
- }
-});
-
-export default class DisplayAnImageWithStyle extends Component {
- render() {
- return (
-
-
- );
- }
-}
-```
-
-### GIF and WebP support on Android
-
-When building your own native code, GIF and WebP are not supported by default on Android.
-
-You will need to add some optional modules in `android/app/build.gradle`, depending on the needs of your app.
-
-```gradle
-dependencies {
- // If your app supports Android versions before Ice Cream Sandwich (API level 14)
- implementation 'com.facebook.fresco:animated-base-support:1.3.0'
-
- // For animated GIF support
- implementation 'com.facebook.fresco:animated-gif:2.0.0'
-
- // For WebP support, including animated WebP
- implementation 'com.facebook.fresco:animated-webp:2.1.0'
- implementation 'com.facebook.fresco:webpsupport:2.0.0'
-
- // For WebP support, without animations
- implementation 'com.facebook.fresco:webpsupport:2.0.0'
-}
-```
-
----
-
-# Reference
-
-## Props
-
-### `style`
-
-`ImageResizeMode` is an `Enum` for different image resizing modes, set via the `resizeMode` style property on `Image` components. The values are `contain`, `cover`, `stretch`, `center`, `repeat`.
-
-| Type | Required |
-| ----- | -------- |
-| style | No |
-
-- [Layout Props...](layout-props.md#props)
-
-- [Shadow Props...](shadow-props.md#props)
-
-- [Transforms...](transforms.md#props)
-
-- **`borderTopRightRadius`**: number
-
-- **`backfaceVisibility`**: enum('visible', 'hidden')
-
-- **`borderBottomLeftRadius`**: number
-
-- **`borderBottomRightRadius`**: number
-
-- **`borderColor`**: [color](colors.md)
-
-- **`borderRadius`**: number
-
-- **`borderTopLeftRadius`**: number
-
-- **`backgroundColor`**: [color](colors.md)
-
-- **`borderWidth`**: number
-
-- **`opacity`**: number
-
-- **`overflow`**: enum('visible', 'hidden')
-
-- **`resizeMode`**: Object.keys(ImageResizeMode)
-
-- **`tintColor`**: [color](colors.md)
-
- Changes the color of all the non-transparent pixels to the tintColor.
-
-- **`overlayColor`**: string (_Android_)
-
- When the image has rounded corners, specifying an overlayColor will cause the remaining space in the corners to be filled with a solid color. This is useful in cases which are not supported by the Android implementation of rounded corners:
-
- - Certain resize modes, such as 'contain'
- - Animated GIFs
-
- A typical way to use this prop is with images displayed on a solid background and setting the `overlayColor` to the same color as the background.
-
- For details of how this works under the hood, see http://frescolib.org/docs/rounded-corners-and-circles.html
-
----
-
-### `blurRadius`
-
-blurRadius: the blur radius of the blur filter added to the image
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `onLayout`
-
-Invoked on mount and layout changes with `{nativeEvent: {layout: {x, y, width, height}}}`.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onLoad`
-
-Invoked when load completes successfully.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onLoadEnd`
-
-Invoked when load either succeeds or fails.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onLoadStart`
-
-Invoked on load start.
-
-e.g., `onLoadStart={(e) => this.setState({loading: true})}`
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `resizeMode`
-
-Determines how to resize the image when the frame doesn't match the raw image dimensions. Defaults to `cover`.
-
-- `cover`: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).
-
-- `contain`: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).
-
-- `stretch`: Scale width and height independently, This may change the aspect ratio of the src.
-
-- `repeat`: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio, unless it is larger than the view, in which case it will be scaled down uniformly so that it is contained in the view.
-
-- `center`: Center the image in the view along both dimensions. If the image is larger than the view, scale it down uniformly so that it is contained in the view.
-
-| Type | Required |
-| ------------------------------------------------------- | -------- |
-| enum('cover', 'contain', 'stretch', 'repeat', 'center') | No |
-
----
-
-### `source`
-
-The image source (either a remote URL or a local file resource).
-
-This prop can also contain several remote URLs, specified together with their width and height and potentially with scale/other URI arguments. The native side will then choose the best `uri` to display based on the measured size of the image container. A `cache` property can be added to control how networked request interacts with the local cache. (For more information see [Cache Control for Images](images#cache-control-ios-only)).
-
-The currently supported formats are `png`, `jpg`, `jpeg`, `bmp`, `gif`, `webp` (Android only), `psd` (iOS only). In addition, iOS supports several RAW image formats. Refer to Apple's documentation for the current list of supported camera models (for iOS 12, see https://support.apple.com/en-ca/HT208967).
-
-| Type | Required |
-| ------------------- | -------- |
-| ImageSourcePropType | No |
-
----
-
-### `loadingIndicatorSource`
-
-Similarly to `source`, this property represents the resource used to render the loading indicator for the image, displayed until image is ready to be displayed, typically after when it got downloaded from network.
-
-| Type | Required |
-| ------------------------------------- | -------- |
-| array of ImageSourcePropTypes, number | No |
-
-> Can accept a number as returned by `require('./image.jpg')`
-
----
-
-### `onError`
-
-Invoked on load error with `{nativeEvent: {error}}`.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `testID`
-
-A unique identifier for this element to be used in UI Automation testing scripts.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `resizeMethod`
-
-The mechanism that should be used to resize the image when the image's dimensions differ from the image view's dimensions. Defaults to `auto`.
-
-- `auto`: Use heuristics to pick between `resize` and `scale`.
-
-- `resize`: A software operation which changes the encoded image in memory before it gets decoded. This should be used instead of `scale` when the image is much larger than the view.
-
-- `scale`: The image gets drawn downscaled or upscaled. Compared to `resize`, `scale` is faster (usually hardware accelerated) and produces higher quality images. This should be used if the image is smaller than the view. It should also be used if the image is slightly bigger than the view.
-
-More details about `resize` and `scale` can be found at http://frescolib.org/docs/resizing.html.
-
-| Type | Required | Platform |
-| ------------------------------- | -------- | -------- |
-| enum('auto', 'resize', 'scale') | No | Android |
-
----
-
-### `accessibilityLabel`
-
-The text that's read by the screen reader when the user interacts with the image.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| string | No | iOS |
-
----
-
-### `accessible`
-
-When true, indicates the image is an accessibility element.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `capInsets`
-
-When the image is resized, the corners of the size specified by `capInsets` will stay a fixed size, but the center content and borders of the image will be stretched. This is useful for creating resizable rounded buttons, shadows, and other resizable assets. More info in the [official Apple documentation](https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIImage_Class/index.html#//apple_ref/occ/instm/UIImage/resizableImageWithCapInsets).
-
-| Type | Required | Platform |
-| ------------------------------------------------------------------ | -------- | -------- |
-| object: {top: number, left: number, bottom: number, right: number} | No | iOS |
-
----
-
-### `defaultSource`
-
-A static image to display while loading the image source.
-
-| Type | Required | Platform |
-| -------------- | -------- | -------- |
-| object, number | No | iOS |
-| number | No | Android |
-
-If passing an object, the general shape is `{uri: string, width: number, height: number, scale: number}`:
-
-- `uri` - a string representing the resource identifier for the image, which should be either a local file path or the name of a static image resource (which should be wrapped in the `require('./path/to/image.png')` function).
-- `width`, `height` - can be specified if known at build time, in which case these will be used to set the default `' }`
diff --git a/website/versioned_docs/version-0.60/imagebackground.md b/website/versioned_docs/version-0.60/imagebackground.md
deleted file mode 100644
index 432e9abb20c..00000000000
--- a/website/versioned_docs/version-0.60/imagebackground.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-id: imagebackground
-title: ImageBackground
----
-
-A common feature request from developers familiar with the web is `background-image`. To handle this use case, you can use the `` component, which has the same props as ``, and add whatever children to it you would like to layer on top of it.
-
-You might not want to use `` in some cases, since the implementation is basic. Refer to ``'s [source code](https://github.com/facebook/react-native/blob/0.60-stable/Libraries/Image/ImageBackground.js) for more insight, and create your own custom component when needed.
-
-Note that you must specify some width and height style attributes.
-
-## Example
-
-```jsx
-return (
-
- Inside
-
-);
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [Image Props](image.md#props).
-
-### `style`
-
-| Type | Required |
-| ---------------------------------- | -------- |
-| [view styles](view-style-props.md) | No |
-
-### `imageStyle`
-
-| Type | Required |
-| ------------------------------------ | -------- |
-| [image styles](image-style-props.md) | No |
-
-### `imageRef`
-
-Allows to set a reference to the inner `Image` component
-
-| Type | Required |
-| ----------------------------------------------------- | -------- |
-| [Ref](https://reactjs.org/docs/refs-and-the-dom.html) | No |
diff --git a/website/versioned_docs/version-0.60/imageeditor.md b/website/versioned_docs/version-0.60/imageeditor.md
deleted file mode 100644
index 6957fb9b4c4..00000000000
--- a/website/versioned_docs/version-0.60/imageeditor.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-id: imageeditor
-title: '🚧 ImageEditor'
----
-
-> **Deprecated.** Use one of the [community packages](https://reactnative.directory/?search=imageeditor) instead.
-
----
-
-# Reference
-
-## Methods
-
-### `cropImage()`
-
-```jsx
-static cropImage(uri, cropData, success, failure)
-```
-
-Crop the image specified by the URI param. If URI points to a remote image, it will be downloaded automatically. If the image cannot be loaded/downloaded, the `failure` callback will be called.
-
-If the cropping process is successful, the resultant cropped image will be stored in the ImageStore, and the URI returned in the `success` callback will point to the image in the store. Remember to delete the cropped image from the ImageStore when you are done with it.
-
-### cropData
-
-- `offset` - The top-left corner of the cropped image, specified in the original image's coordinate space
-- `size` - Size (dimensions) of the cropped image
-- `displaySize (optional)` - Size to which you want to scale the cropped image
-- `resizeMode (optional)` - Resizing mode to use when scaling the image
-
-```jsx
-cropData = {
- offset: {x: number, y: number},
- size: {width: number, height: number},
- displaySize: {width: number, height: number},
- resizeMode: 'contain/cover/stretch',
-};
-```
diff --git a/website/versioned_docs/version-0.60/imagepickerios.md b/website/versioned_docs/version-0.60/imagepickerios.md
deleted file mode 100644
index 028f64c919e..00000000000
--- a/website/versioned_docs/version-0.60/imagepickerios.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-id: imagepickerios
-title: ImagePickerIOS
----
-
-> **Deprecated.** Use [@react-native-community/image-picker-ios](https://github.com/react-native-community/react-native-image-picker-ios) instead.
-
----
-
-# Reference
-
-## Methods
-
-### `canRecordVideos()`
-
-```jsx
-static canRecordVideos(callback)
-```
-
----
-
-### `canUseCamera()`
-
-```jsx
-static canUseCamera(callback)
-```
-
----
-
-### `openCameraDialog()`
-
-```jsx
-static openCameraDialog(config, successCallback, cancelCallback)
-```
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| --------------- | -------- | -------- | ----------- |
-| config | object | No | See below. |
-| successCallback | function | No | See below. |
-| cancelCallback | function | No | See below. |
-
-`config` is an object containing:
-
-- `videoMode` : An optional boolean value that defaults to false.
-
-`successCallback` is an optional callback function that's invoked when the select dialog is opened successfully. It will include the following data:
-
-- `[string, number, number]`
-
-`cancelCallback` is an optional callback function that's invoked when the camera dialog is canceled.
-
----
-
-### `openSelectDialog()`
-
-```jsx
-static openSelectDialog(config, successCallback, cancelCallback)
-```
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| --------------- | -------- | -------- | ----------- |
-| config | object | No | See below. |
-| successCallback | function | No | See below. |
-| cancelCallback | function | No | See below. |
-
-`config` is an object containing:
-
-- `showImages` : An optional boolean value that defaults to false.
-- `showVideos`: An optional boolean value that defaults to false.
-
-`successCallback` is an optional callback function that's invoked when the select dialog is opened successfully. It will include the following data:
-
-- `[string, number, number]`
-
-`cancelCallback` is an optional callback function that's invoked when the select dialog is canceled.
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 4a7766483c0..00000000000
--- a/website/versioned_docs/version-0.60/images.md
+++ /dev/null
@@ -1,229 +0,0 @@
----
-id: images
-title: Images
----
-
-## Static Image Resources
-
-React Native provides a unified way of managing images and other media assets in your Android and iOS apps. To add a static image to your app, place it somewhere in your source code tree and reference it like this:
-
-```jsx
-` component, which has the same props as ``, and add whatever children to it you would like to layer on top of it.
-
-You might not want to use `` in some cases, since the implementation is basic. Refer to ``'s [documentation](imagebackground.md) for more insight, and create your own custom component when needed.
-
-```jsx
-return (
-
- Inside
-
-);
-```
-
-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/imagestore.md b/website/versioned_docs/version-0.60/imagestore.md
deleted file mode 100644
index 72daf4a8315..00000000000
--- a/website/versioned_docs/version-0.60/imagestore.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-id: imagestore
-title: '🚧 ImageStore'
----
-
-> **Deprecated.** Use [expo-file-system](https://github.com/expo/expo/tree/master/packages/expo-file-system) or [react-native-fs](https://github.com/itinance/react-native-fs) instead.
-
-### Methods
-
-- [`hasImageForTag`](imagestore.md#hasimagefortag)
-- [`removeImageForTag`](imagestore.md#removeimagefortag)
-- [`addImageFromBase64`](imagestore.md#addimagefrombase64)
-- [`getBase64ForTag`](imagestore.md#getbase64fortag)
-
----
-
-# Reference
-
-## Methods
-
-### `hasImageForTag()`
-
-```jsx
-static hasImageForTag(uri, callback)
-```
-
-Check if the ImageStore contains image data for the specified URI. @platform ios
-
----
-
-### `removeImageForTag()`
-
-```jsx
-static removeImageForTag(uri)
-```
-
-Delete an image from the ImageStore. Images are stored in memory and must be manually removed when you are finished with them, otherwise they will continue to use up RAM until the app is terminated. It is safe to call `removeImageForTag()` without first calling `hasImageForTag()`, it will fail silently. @platform ios
-
----
-
-### `addImageFromBase64()`
-
-```jsx
-static addImageFromBase64(base64ImageData, success, failure)
-```
-
-Stores a base64-encoded image in the ImageStore, and returns a URI that can be used to access or display the image later. Images are stored in memory only, and must be manually deleted when you are finished with them by calling `removeImageForTag()`.
-
-Note that it is very inefficient to transfer large quantities of binary data between JS and native code, so you should avoid calling this more than necessary. @platform ios
-
----
-
-### `getBase64ForTag()`
-
-```jsx
-static getBase64ForTag(uri, success, failure)
-```
-
-Retrieves the base64-encoded data for an image in the ImageStore. If the specified URI does not match an image in the store, the failure callback will be called.
-
-Note that it is very inefficient to transfer large quantities of binary data between JS and native code, so you should avoid calling this more than necessary. To display an image in the ImageStore, you can pass the URI to an `
-
- this.setState({text})}
- value={this.state.text}
- />
-
-
- this.setState({text: 'Placeholder Text'})}
- title="Reset Text"
- />
-
-
- );
- }
-}
-```
-
-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/0.60-stable/packages/rn-tester/js/examples/InputAccessoryView/InputAccessoryViewExample.js).
-
----
-
-# Reference
-
-## Props
-
-### `backgroundColor`
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `nativeID`
-
-An ID which is used to associate this `InputAccessoryView` to specified TextInput(s).
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `style`
-
-| Type | Required |
-| ---------------------------- | -------- |
-| [style](view-style-props.md) | No |
-
-# Known issues
-
-- [react-native#18997](https://github.com/facebook/react-native/issues/18997): Doesn't support multiline `TextInput`s
-- [react-native#20157](https://github.com/facebook/react-native/issues/20157): Can't use with a bottom tab bar
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 0d147e07a3a..00000000000
--- a/website/versioned_docs/version-0.60/integration-with-existing-apps.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-id: integration-with-existing-apps
-title: Integration with Existing Apps
-hide_table_of_contents: true
----
-
-import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem';
-
-import IntegrationJava from './\_integration-with-existing-apps-java.md'; import IntegrationObjC from './\_integration-with-existing-apps-objc.md'; import IntegrationSwift from './\_integration-with-existing-apps-swift.md';
-
-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.
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/website/versioned_docs/version-0.60/interactionmanager.md b/website/versioned_docs/version-0.60/interactionmanager.md
deleted file mode 100644
index 61a1d8058b6..00000000000
--- a/website/versioned_docs/version-0.60/interactionmanager.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-id: interactionmanager
-title: InteractionManager
----
-
-InteractionManager allows long-running work to be scheduled after any interactions/animations have completed. In particular, this allows JavaScript animations to run smoothly.
-
-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(): 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
-```
-
-`runAfterInteractions` takes either a plain callback function, or a `PromiseTask` object with a `gen` method that returns a `Promise`. If a `PromiseTask` is supplied, then it is fully resolved (including asynchronous dependencies that also schedule more tasks via `runAfterInteractions`) before starting on the next task that might have been queued up synchronously earlier.
-
-By default, queued tasks are executed together in a loop in one `setImmediate` batch. If `setDeadline` is called with a positive number, then tasks will only be executed until the deadline (in terms of js event loop run time) approaches, at which point execution will yield via setTimeout, allowing events such as touches to start interactions and block queued tasks from executing, making apps more responsive.
-
----
-
-# Reference
-
-## Methods
-
-### `runAfterInteractions()`
-
-```jsx
-static runAfterInteractions(task)
-```
-
-Schedule a function to run after all interactions have completed. Returns a cancellable "promise".
-
----
-
-### `createInteractionHandle()`
-
-```jsx
-static createInteractionHandle()
-```
-
-Notify manager that an interaction has started.
-
----
-
-### `clearInteractionHandle()`
-
-```jsx
-static clearInteractionHandle(handle)
-```
-
-Notify manager that an interaction has completed.
-
----
-
-### `setDeadline()`
-
-```jsx
-static setDeadline(deadline)
-```
-
-A positive number will use setTimeout to schedule any tasks after the eventLoopRunningTime hits the deadline value, otherwise all tasks will be executed in one setImmediate batch (default).
-
-## Properties
-
----
diff --git a/website/versioned_docs/version-0.60/intro-react-native-components.md b/website/versioned_docs/version-0.60/intro-react-native-components.md
deleted file mode 100644
index 9bdeaa586fe..00000000000
--- a/website/versioned_docs/version-0.60/intro-react-native-components.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-id: intro-react-native-components
-title: Core Components and Native Components
-
-description: 'React Native lets you compose app interfaces using Native Components. Conveniently, it comes with a set of these components for you to get started with right now—the Core Components!'
----
-
-React Native is an open source framework for building Android and iOS applications using [React](https://reactjs.org/) and the app platform’s native capabilities. With React Native, you use JavaScript to access your platform’s APIs as well as to describe the appearance and behavior of your UI using React components: bundles of reusable, nestable code. You can learn more about React in the next section. But first, let’s cover how components work in React Native.
-
-## Views and mobile development
-
-In Android and iOS development, a **view** is the basic building block of UI: a small rectangular element on the screen which can be used to display text, images, or respond to user input. Even the smallest visual elements of an app, like a line of text or a button, are kinds of views. Some kinds of views can contain other views. It’s views all the way down!
-
-
- Just a sampling of the many views used in Android and iOS apps.
-
-
-## Native Components
-
-In Android development, you write views in Kotlin or Java; in iOS development, you use Swift or Objective-C. With React Native, you can invoke these views with JavaScript using React components. At runtime, React Native creates the corresponding Android and iOS views for those components. Because React Native components are backed by the same views as Android and iOS, React Native apps look, feel, and perform like any other apps. We call these platform-backed components **Native Components.**
-
-React Native lets you to build your own Native Components for [Android](native-components-android.md) and [iOS](native-components-ios.md) to suit your app’s unique needs. We also have a thriving ecosystem of these **community-contributed components.** Check out [Native Directory](https://www.native.directory/) to find what the community has been creating.
-
-React Native also includes a set of essential, ready-to-use Native Components you can use to start building your app today. These are React Native's **Core Components**.
-
-## Core Components
-
-React Native has many Core Components for everything from form controls to activity indicators. You can find them all [documented in the API section](components-and-apis). You will mostly work with the following Core Components:
-
-| React Native UI Component | Android View | iOS View | Web Analog | Description |
-| ------------------------- | -------------- | ---------------- | ------------------------ | ----------------------------------------------------------------------------------------------------- |
-| `` | `` | `` | A non-scrollling `` | A container that supports layout with flexbox, style, some touch handling, and accessibility controls |
-| `
` | `` | `` | `` | Displays, styles, and nests strings of text and even handles touch events |
-| `` | `` | `` | `` | `` | `` | `` | A generic scrolling container that can contain multiple components and views |
-| `
` | `` | `` | `
- Some text
-
- Some more text
-
-
- );
-}
-```
-
----
-
-Because React Native uses the same API structure as React components, you’ll need to understand React component APIs to get started. The [next section](intro-react) makes for a quick introduction or refresher on the topic. However, if you’re already familiar with React, feel free to [skip ahead](handling-text-input).
-
-
-
-
-```SnackPlayer name=Your%20Cat
-import React from 'react';
-import { Text } from 'react-native';
-
-const Cat = () => {
- return (
- Hello, I am your cat!
- );
-}
-
-export default Cat;
-```
-
-Here is how you do it: To define your `Cat` component, first use JavaScript’s [`import`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import) to import React and React Native’s [`Text`](/docs/next/text) Core Component:
-
-```jsx
-import React from 'react';
-import {Text} from 'react-native';
-```
-
-Your component starts as a function:
-
-```jsx
-const Cat = () => {};
-```
-
-You can think of components as blueprints. Whatever a function component returns is rendered as a **React element.** React elements let you describe what you want to see on the screen.
-
-Here the `Cat` component will render a `` element:
-
-```jsx
-const Cat = () => {
- return Hello, I am your cat! ;
-};
-```
-
-You can export your function component with JavaScript’s [`export default`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/export) for use throughout your app like so:
-
-```jsx
-const Cat = () => {
- return Hello, I am your cat! ;
-};
-
-export default Cat;
-```
-
-
-
-
-Class components tend to be a bit more verbose than function components.
-
-```SnackPlayer name=Your%20Cat
-import React, { Component } from 'react';
-import { Text } from 'react-native';
-
-class Cat extends Component {
- render() {
- return (
- Hello, I am your cat!
- );
- }
-}
-
-export default Cat;
-```
-
-You additionally import `Component` from React:
-
-```jsx
-import React, {Component} from 'react';
-```
-
-Your component starts as a class extending `Component` instead of as a function:
-
-```jsx
-class Cat extends Component {}
-```
-
-Class components have a `render()` function. Whatever is returned inside it is rendered as a React element:
-
-```jsx
-class Cat extends Component {
- render() {
- return Hello, I am your cat! ;
- }
-}
-```
-
-And as with function components, you can export your class component:
-
-```jsx
-class Cat extends Component {
- render() {
- return Hello, I am your cat! ;
- }
-}
-
-export default Cat;
-```
-
-
-
-
-> This is one of many ways to export your component. This kind of export works well with the Snack Player. However, depending on your app’s file structure, you might need to use a different convention. This [handy cheatsheet on JavaScript imports and exports](https://medium.com/dailyjs/javascript-module-cheatsheet-7bd474f1d829) can help.
-
-Now take a closer look at that `return` statement. `Hello, I am your cat! ` is using a kind of JavaScript syntax that makes writing elements convenient: JSX.
-
-## JSX
-
-React and React Native use **JSX,** a syntax that lets you write elements inside JavaScript like so: `Hello, I am your cat! `. The React docs have [a comprehensive guide to JSX](https://reactjs.org/docs/jsx-in-depth.html) you can reference to learn even more. Because JSX is JavaScript, you can use variables inside it. Here you are declaring a name for the cat, `name`, and embedding it with curly braces inside ``.
-
-```SnackPlayer name=Curly%20Braces
-import React from 'react';
-import { Text } from 'react-native';
-
-const Cat = () => {
- const name = "Maru";
- return (
- Hello, I am {name}!
- );
-}
-
-export default Cat;
-```
-
-Any JavaScript expression will work between curly braces, including function calls like `{getFullName("Rum", "Tum", "Tugger")}`:
-
-```SnackPlayer name=Curly%20Braces
-import React from 'react';
-import { Text } from 'react-native';
-
-const getFullName = (firstName, secondName, thirdName) => {
- return firstName + " " + secondName + " " + thirdName;
-}
-
-const Cat = () => {
- return (
-
- Hello, I am {getFullName("Rum", "Tum", "Tugger")}!
-
- );
-}
-
-export default Cat;
-```
-
-You can think of curly braces as creating a portal into JS functionality in your JSX!
-
-> Because JSX is included in the React library, it won’t work if you don’t have `import React from 'react'` at the top of your file!
-
-## Custom Components
-
-You’ve already met [React Native’s Core Components](intro-react-native-components). React lets you nest these components inside each other to create new components. These nestable, reusable components are at the heart of the React paradigm.
-
-For example, you can nest [`Text`](text) and [`TextInput`](textinput) inside a [`View`](view) below, and React Native will render them together:
-
-```SnackPlayer name=Custom%20Components
-import React from 'react';
-import { Text, TextInput, View } from 'react-native';
-
-const Cat = () => {
- return (
-
- Hello, I am...
-
- );
-}
-
-export default Cat;
-```
-
-#### Developer notes
-
-
-
-
-
-> If you’re familiar with web development, `` and `` might remind you of HTML! You can think of them as the `` and `
` tags of application development.
-
-
-
-
-> On Android, you usually put your views inside `LinearLayout`, `FrameLayout`, `RelativeLayout`, etc. to define how the view’s children will be arranged on the screen. In React Native, `View` uses Flexbox for its children’s layout. You can learn more in [our guide to layout with Flexbox](flexbox).
-
-
-
-
-You can render this component multiple times and in multiple places without repeating your code by using ``:
-
-```SnackPlayer name=Multiple%20Components
-import React from 'react';
-import { Text, TextInput, View } from 'react-native';
-
-const Cat = () => {
- return (
-
- I am also a cat!
-
- );
-}
-
-const Cafe = () => {
- return (
-
- Welcome!
-
- );
-}
-
-export default Cafe;
-```
-
-Any component that renders other components is a **parent component.** Here, `Cafe` is the parent component and each `Cat` is a **child component.**
-
-You can put as many cats in your cafe as you like. Each `` renders a unique element—which you can customize with props.
-
-## Props
-
-**Props** is short for “properties.” Props let you customize React components. For example, here you pass each `` a different `name` for `Cat` to render:
-
-```SnackPlayer name=Multiple%20Props
-import React from 'react';
-import { Text, View } from 'react-native';
-
-const Cat = (props) => {
- return (
-
- Hello, I am {props.name}!
-
- );
-}
-
-const Cafe = () => {
- return (
-
-
- );
-}
-
-export default Cafe;
-```
-
-Most of React Native’s Core Components can be customized with props, too. For example, when using [`Image`](image), you pass it a prop named [`source`](image#source) to define what image it shows:
-
-```SnackPlayer name=Props
-import React from 'react';
-import { Text, View, Image } from 'react-native';
-
-const CatApp = () => {
- return (
-
- Hello, I am your cat!
-
- );
-}
-
-export default CatApp;
-```
-
-`Image` has [many different props](image#props), including [`style`](image#style), which accepts a JS object of design and layout related property-value pairs.
-
-> Notice the double curly braces `{{ }}` surrounding `style`‘s width and height. In JSX, JavaScript values are referenced with `{}`. This is handy if you are passing something other than a string as props, like an array or number: `
-
-
-You can add state to a component by calling [React’s `useState` Hook](https://reactjs.org/docs/hooks-state.html). A Hook is a kind of function that lets you “hook into” React features. For example, `useState` is a Hook that lets you add state to function components. You can learn more about [other kinds of Hooks in the React documentation.](https://reactjs.org/docs/hooks-intro.html)
-
-```SnackPlayer name=State
-import React, { useState } from "react";
-import { Button, Text, View } from "react-native";
-
-const Cat = (props) => {
- const [isHungry, setIsHungry] = useState(true);
-
- return (
-
-
- I am {props.name}, and I am {isHungry ? "hungry" : "full"}!
-
- {
- setIsHungry(false);
- }}
- disabled={!isHungry}
- title={isHungry ? "Pour me some milk, please!" : "Thank you!"}
- />
-
- );
-}
-
-const Cafe = () => {
- return (
- <>
- , ] = useState()`.
-
-Next you add the [`Button`](button) Core Component and give it an `onPress` prop:
-
-```jsx
- {
- setIsHungry(false);
- }}
- //..
-/>
-```
-
-Now, when someone presses the button, `onPress` will fire, calling the `setIsHungry(false)`. This sets the state variable `isHungry` to `false`. When `isHungry` is false, the `Button`’s `disabled` prop is set to `true` and its `title` also changes:
-
-```jsx
-
-
-
-The older class components approach is a little different when it comes to state.
-
-```SnackPlayer name=State%20and%20Class%20Components
-import React, { Component } from "react";
-import { Button, Text, View } from "react-native";
-
-class Cat extends Component {
- state = { isHungry: true };
-
- render(props) {
- return (
-
-
- I am {this.props.name}, and I am
- {this.state.isHungry ? " hungry" : " full"}!
-
- {
- this.setState({ isHungry: false });
- }}
- disabled={!this.state.isHungry}
- title={
- this.state.isHungry ? "Pour me some milk, please!" : "Thank you!"
- }
- />
-
- );
- }
-}
-
-class Cafe extends Component {
- render() {
- return (
- <>
-
- I am {this.props.name}, and I am
- {this.state.isHungry ? ' hungry' : ' full'}!
-
-```
-
-And you set individual values inside the state object by passing an object with the key value pair for state and its new value to `this.setState()`:
-
-```jsx
- {
- this.setState({ isHungry: false });
- }}
- // ..
-
-```
-
-> Do not change your component's state directly by assigning it a new value with `this.state.hunger = false`. Calling `this.setState()` allows React to track changes made to state that trigger rerendering. Setting state directly can break your app's reactivity!
-
-When `this.state.isHungry` is false, the `Button`’s `disabled` prop is set to `false` and its `title` also changes:
-
-```jsx
-
-
-
-> See the `<>` and `` above? These bits of JSX are [fragments](https://reactjs.org/docs/fragments.html). Adjacent JSX elements must be wrapped in an enclosing tag. Fragments let you do that without nesting an extra, unnecessary wrapping element like `View`.
-
----
-
-Now that you’ve covered both React and React Native’s Core Components, let’s dive deeper on some of these core components by looking at [handling ``](handling-text-input).
diff --git a/website/versioned_docs/version-0.60/introduction.md b/website/versioned_docs/version-0.60/introduction.md
deleted file mode 100644
index 94c7f8e094e..00000000000
--- a/website/versioned_docs/version-0.60/introduction.md
+++ /dev/null
@@ -1,139 +0,0 @@
----
-id: getting-started
-title: Introduction
-description: This helpful guide lays out the prerequisites for learning React Native, using these docs, and setting up your environment.
----
-
-import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
-
-
-
- Welcome to the very start of your React Native journey! If you're looking for environment setup instructions, they've moved to [their own section](/docs/environment-setup). Continue reading for an introduction to the documentation, Native Components, React, and more!
-
-
-
-
- Try editing me! 🎉
-
-
- );
-}
-
-export default YourApp;
-```
-
-The above is a Snack Player. It’s a handy tool created by Expo to embed and run React Native projects and share how they render in platforms like Android and iOS. The code is live and editable, so you can play directly with it in your browser. Go ahead and try changing the "Try editing me!" text above to "Hello, world!"
-
-> Optionally, if you want to setup a local development environment, [you can follow our guide to setting up your environment on your local machine](/docs/environment-setup) and paste the code examples into your `App.js` file there. (If you are a web developer, you may already have a local environment set up for mobile browser testing!)
-
-## Function Components and Class Components
-
-With React, you can make components using either classes or functions. Originally, class components were the only components that could have state. But since the introduction of React's Hooks API, you can add state and more to function components.
-
-[Hooks were introduced in React Native 0.59.](/blog/2019/03/12/releasing-react-native-059), and because Hooks are the future-facing way to write your React components, we wrote this introduction using function component examples. Where useful, we also cover class components under a toggle like so:
-
-
-
-
-```SnackPlayer name=Hello%20World%20Function%20Component
-import React from 'react';
-import { Text, View } from 'react-native';
-
-const HelloWorldApp = () => {
- return (
-
- Hello, world!
-
- );
-}
-
-export default HelloWorldApp;
-```
-
-
-
-
-```SnackPlayer name=Hello%20World%20Class%20Component
-import React, { Component } from 'react';
-import { Text, View } from 'react-native';
-
-class HelloWorldApp extends Component {
- render() {
- return (
-
- Hello, world!
-
- );
- }
-}
-
-export default HelloWorldApp;
-```
-
-
-
-
-You can find more examples of class components in [previous versions of this documentation](/versions).
-
-## Developer Notes
-
-People from many different development backgrounds are learning React Native. You may have experience with a range of technologies, from web to Android to iOS and more. We try to write for developers from all backgrounds. Sometimes we provide explanations specific to one platform or another like so:
-
-
-
-
-
-> Web developers may be familiar with this concept.
-
-
-
-
-> Android developers may be familiar with this concept.
-
-
-
-
-> iOS developers may be familiar with this concept.
-
-
-
-
-## Formatting
-
-Menu paths are written in bold and use carets to navigate submenus. Example: **Android Studio > Preferences**
-
----
-
-Now that you know how this guide works, it's time to get to know the foundation of React Native: [Native Components](intro-react-native-components.md).
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 434f8051f2b..00000000000
--- a/website/versioned_docs/version-0.60/javascript-environment.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-id: javascript-environment
-title: 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): ` 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
- ... your UI ...
- ;
-```
-
-### Example
-
-` equates to `flexGrow: , flexShrink: 1, flexBasis: 0`.
-
-When `flex` is 0, the component is sized according to `width` and `height` and it is inflexible.
-
-When `flex` is -1, the component is normally sized according `width` and `height`. However, if there's not enough space, the component will shrink to its `minWidth` and `minHeight`.
-
-flexGrow, flexShrink, and flexBasis work the same as in CSS.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `flexBasis`
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `flexDirection`
-
-`flexDirection` controls which directions children of a container go. `row` goes left to right, `column` goes top to bottom, and you may be able to guess what the other two do. It works like `flex-direction` in CSS, except the default is `column`. See https://developer.mozilla.org/en-US/docs/Web/CSS/flex-direction for more details.
-
-| Type | Required |
-| ------------------------------------------------------ | -------- |
-| enum('row', 'row-reverse', 'column', 'column-reverse') | No |
-
----
-
-### `flexGrow`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `flexShrink`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `flexWrap`
-
-`flexWrap` controls whether children can wrap around after they hit the end of a flex container. It works like `flex-wrap` in CSS (default: nowrap). See https://developer.mozilla.org/en-US/docs/Web/CSS/flex-wrap for more details. Note it does not work anymore with `alignItems: stretch` (the default), so you may want to use `alignItems: flex-start` for example (breaking change details: https://github.com/facebook/react-native/releases/tag/v0.28.0).
-
-| Type | Required |
-| ---------------------- | -------- |
-| enum('wrap', 'nowrap') | No |
-
----
-
-### `height`
-
-`height` sets the height of this component.
-
-It works similarly to `height` in CSS, but in React Native you must use points or percentages. Ems and other units are not supported. See https://developer.mozilla.org/en-US/docs/Web/CSS/height for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `justifyContent`
-
-`justifyContent` aligns children in the main direction. For example, if children are flowing vertically, `justifyContent` controls how they align vertically. It works like `justify-content` in CSS (default: flex-start). See https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content for more details.
-
-| Type | Required |
-| ----------------------------------------------------------------------------------------- | -------- |
-| enum('flex-start', 'flex-end', 'center', 'space-between', 'space-around', 'space-evenly') | No |
-
----
-
-### `left`
-
-`left` is the number of logical pixels to offset the left edge of this component.
-
-It works similarly to `left` in CSS, but in React Native you must use points or percentages. Ems and other units are not supported.
-
-See https://developer.mozilla.org/en-US/docs/Web/CSS/left for more details of how `left` affects layout.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `margin`
-
-Setting `margin` has the same effect as setting each of `marginTop`, `marginLeft`, `marginBottom`, and `marginRight`. See https://developer.mozilla.org/en-US/docs/Web/CSS/margin for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `marginBottom`
-
-`marginBottom` works like `margin-bottom` in CSS. See https://developer.mozilla.org/en-US/docs/Web/CSS/margin-bottom for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `marginEnd`
-
-When direction is `ltr`, `marginEnd` is equivalent to `marginRight`. When direction is `rtl`, `marginEnd` is equivalent to `marginLeft`.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `marginHorizontal`
-
-Setting `marginHorizontal` has the same effect as setting both `marginLeft` and `marginRight`.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `marginLeft`
-
-`marginLeft` works like `margin-left` in CSS. See https://developer.mozilla.org/en-US/docs/Web/CSS/margin-left for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `marginRight`
-
-`marginRight` works like `margin-right` in CSS. See https://developer.mozilla.org/en-US/docs/Web/CSS/margin-right for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `marginStart`
-
-When direction is `ltr`, `marginStart` is equivalent to `marginLeft`. When direction is `rtl`, `marginStart` is equivalent to `marginRight`.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `marginTop`
-
-`marginTop` works like `margin-top` in CSS. See https://developer.mozilla.org/en-US/docs/Web/CSS/margin-top for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `marginVertical`
-
-Setting `marginVertical` has the same effect as setting both `marginTop` and `marginBottom`.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `maxHeight`
-
-`maxHeight` is the maximum height for this component, in logical pixels.
-
-It works similarly to `max-height` in CSS, but in React Native you must use points or percentages. Ems and other units are not supported.
-
-See https://developer.mozilla.org/en-US/docs/Web/CSS/max-height for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `maxWidth`
-
-`maxWidth` is the maximum width for this component, in logical pixels.
-
-It works similarly to `max-width` in CSS, but in React Native you must use points or percentages. Ems and other units are not supported.
-
-See https://developer.mozilla.org/en-US/docs/Web/CSS/max-width for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `minHeight`
-
-`minHeight` is the minimum height for this component, in logical pixels.
-
-It works similarly to `min-height` in CSS, but in React Native you must use points or percentages. Ems and other units are not supported.
-
-See https://developer.mozilla.org/en-US/docs/Web/CSS/min-height for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `minWidth`
-
-`minWidth` is the minimum width for this component, in logical pixels.
-
-It works similarly to `min-width` in CSS, but in React Native you must use points or percentages. Ems and other units are not supported.
-
-See https://developer.mozilla.org/en-US/docs/Web/CSS/min-width for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `overflow`
-
-`overflow` controls how children are measured and displayed. `overflow: hidden` causes views to be clipped while `overflow: scroll` causes views to be measured independently of their parents main axis. It works like `overflow` in CSS (default: visible). See https://developer.mozilla.org/en/docs/Web/CSS/overflow for more details.
-
-| Type | Required |
-| ----------------------------------- | -------- |
-| enum('visible', 'hidden', 'scroll') | No |
-
----
-
-### `padding`
-
-Setting `padding` has the same effect as setting each of `paddingTop`, `paddingBottom`, `paddingLeft`, and `paddingRight`. See https://developer.mozilla.org/en-US/docs/Web/CSS/padding for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `paddingBottom`
-
-`paddingBottom` works like `padding-bottom` in CSS. See https://developer.mozilla.org/en-US/docs/Web/CSS/padding-bottom for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `paddingEnd`
-
-When direction is `ltr`, `paddingEnd` is equivalent to `paddingRight`. When direction is `rtl`, `paddingEnd` is equivalent to `paddingLeft`.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `paddingHorizontal`
-
-Setting `paddingHorizontal` is like setting both of `paddingLeft` and `paddingRight`.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `paddingLeft`
-
-`paddingLeft` works like `padding-left` in CSS. See https://developer.mozilla.org/en-US/docs/Web/CSS/padding-left for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `paddingRight`
-
-`paddingRight` works like `padding-right` in CSS. See https://developer.mozilla.org/en-US/docs/Web/CSS/padding-right for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `paddingStart`
-
-When direction is `ltr`, `paddingStart` is equivalent to `paddingLeft`. When direction is `rtl`, `paddingStart` is equivalent to `paddingRight`.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `paddingTop`
-
-`paddingTop` works like `padding-top` in CSS. See https://developer.mozilla.org/en-US/docs/Web/CSS/padding-top for more details.
-
-| Type | Required |
-| --------------- | -------- |
-| number, ,string | No |
-
----
-
-### `paddingVertical`
-
-Setting `paddingVertical` is like setting both of `paddingTop` and `paddingBottom`.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `position`
-
-`position` in React Native is similar to regular CSS, but everything is set to `relative` by default, so `absolute` positioning is always relative to the parent.
-
-If you want to position a child using specific numbers of logical pixels relative to its parent, set the child to have `absolute` position.
-
-If you want to position a child relative to something that is not its parent, don't use styles for that. Use the component tree.
-
-See https://github.com/facebook/yoga for more details on how `position` differs between React Native and CSS.
-
-| Type | Required |
-| ---------------------------- | -------- |
-| enum('absolute', 'relative') | No |
-
----
-
-### `right`
-
-`right` is the number of logical pixels to offset the right edge of this component.
-
-It works similarly to `right` in CSS, but in React Native you must use points or percentages. Ems and other units are not supported.
-
-See https://developer.mozilla.org/en-US/docs/Web/CSS/right for more details of how `right` affects layout.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `start`
-
-When the direction is `ltr`, `start` is equivalent to `left`. When the direction is `rtl`, `start` is equivalent to `right`.
-
-This style takes precedence over the `left`, `right`, and `end` styles.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `top`
-
-`top` is the number of logical pixels to offset the top edge of this component.
-
-It works similarly to `top` in CSS, but in React Native you must use points or percentages. Ems and other units are not supported.
-
-See https://developer.mozilla.org/en-US/docs/Web/CSS/top for more details of how `top` affects layout.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `width`
-
-`width` sets the width of this component.
-
-It works similarly to `width` in CSS, but in React Native you must use points or percentages. Ems and other units are not supported. See https://developer.mozilla.org/en-US/docs/Web/CSS/width for more details.
-
-| Type | Required |
-| -------------- | -------- |
-| number, string | No |
-
----
-
-### `zIndex`
-
-`zIndex` controls which components display on top of others. Normally, you don't use `zIndex`. Components render according to their order in the document tree, so later components draw over earlier ones. `zIndex` may be useful if you have animations or custom modal interfaces where you don't want this behavior.
-
-It works like the CSS `z-index` property - components with a larger `zIndex` will render on top. Think of the z-direction like it's pointing from the phone into your eyeball. See https://developer.mozilla.org/en-US/docs/Web/CSS/z-index for more details.
-
-On iOS, `zIndex` may require `View`s to be siblings of each other for it to work as expected.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
diff --git a/website/versioned_docs/version-0.60/layoutanimation.md b/website/versioned_docs/version-0.60/layoutanimation.md
deleted file mode 100644
index ff1f0042ef5..00000000000
--- a/website/versioned_docs/version-0.60/layoutanimation.md
+++ /dev/null
@@ -1,179 +0,0 @@
----
-id: layoutanimation
-title: LayoutAnimation
----
-
-Automatically animates views to their new positions when the next layout happens.
-
-A common way to use this API is to call it before calling `setState`.
-
-Note that in order to get this to work on **Android** you need to set the following flags via `UIManager`:
-
-```js
-if (Platform.OS === 'android') {
- if (UIManager.setLayoutAnimationEnabledExperimental) {
- UIManager.setLayoutAnimationEnabledExperimental(true);
- }
-}
-```
-
-Example usage:
-
-```jsx
-import React, {Component} from 'react';
-import {
- View,
- Text,
- TouchableOpacity,
- Platform,
- UIManager,
-} from 'react-native';
-
-if (
- Platform.OS === 'android' &&
- UIManager.setLayoutAnimationEnabledExperimental
-) {
- UIManager.setLayoutAnimationEnabledExperimental(true);
-}
-class AnimatedCollapsible extends React.Component {
- state = {expanded: false};
- render() {
- return (
-
- {
- LayoutAnimation.configureNext(
- LayoutAnimation.Presets.spring,
- );
- this.setState({expanded: !this.state.expanded});
- }}>
-
- Press me to{' '}
- {this.state.expanded ? 'collapse' : 'expand'}!
-
-
- {this.state.expanded && (
- I disappear sometimes!
- )}
-
- );
- }
-}
-```
-
----
-
-# Reference
-
-## Methods
-
-### `configureNext()`
-
-```jsx
-static configureNext(config, onAnimationDidEnd?)
-```
-
-Schedules an animation to happen on the next layout.
-
-#### Parameters:
-
-| Name | Type | Required | Description |
-| ----------------- | -------- | -------- | ---------------------------------------------------------- |
-| config | object | Yes | See config description below. |
-| onAnimationDidEnd | function | No | Called when the animation finished. Only supported on iOS. |
-
-The `config` parameter is an object with the keys below. [`create`](layoutanimation.md#create) returns a valid object for `config`, and the [`Presets`](layoutanimation.md#presets) objects can also all be passed as the `config`.
-
-- `duration` in milliseconds
-- `create`, optional config for animating in new views
-- `update`, optional config for animating views that have been updated
-- `delete`, optional config for animating views as they are removed
-
-The config that's passed to `create`, `update`, or `delete` has the following keys:
-
-- `type`, the [animation type](layoutanimation.md#types) to use
-- `property`, the [layout property](layoutanimation.md#properties) to animate (optional, but recommended for `create` and `delete`)
-- `springDamping` (number, optional and only for use with `type: Type.spring`)
-- `initialVelocity` (number, optional)
-- `delay` (number, optional)
-- `duration` (number, optional)
-
----
-
-### `create()`
-
-```jsx
-static create(duration, type, creationProp)
-```
-
-Helper that creates an object (with `create`, `update`, and `delete` fields) to pass into [`configureNext`](layoutanimation.md#configurenext). The `type` parameter is an [animation type](layoutanimation.md#types), and the `creationProp` parameter is a [layout property](layoutanimation.md#properties).
-
-Example usage:
-
-```js
-LayoutAnimation.configureNext(
- LayoutAnimation.create(
- 500,
- LayoutAnimation.Types.spring,
- LayoutAnimation.Properties.scaleXY,
- ),
-);
-```
-
-## Properties
-
-### Types
-
-An enumeration of animation types to be used in the [`create`](layoutanimation.md#create) method, or in the `create`/`update`/`delete` configs for [`configureNext`](layoutanimation.md#configurenext). (example usage: `LayoutAnimation.Types.easeIn`)
-
-| Types |
-| ------------- |
-| spring |
-| linear |
-| easeInEaseOut |
-| easeIn |
-| easeOut |
-| keyboard |
-
----
-
-### Properties
-
-An enumeration of layout properties to be animated to be used in the [`create`](layoutanimation.md#create) method, or in the `create`/`update`/`delete` configs for [`configureNext`](layoutanimation.md#configurenext). (example usage: `LayoutAnimation.Properties.opacity`)
-
-| Properties |
-| ---------- |
-| opacity |
-| scaleX |
-| scaleY |
-| scaleXY |
-
----
-
-### Presets
-
-A set of predefined animation configs to pass into [`configureNext`](layoutanimation.md#configurenext).
-
-| Presets | Value |
-| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| easeInEaseOut | `create(300, 'easeInEaseOut', 'opacity')` |
-| linear | `create(500, 'linear', 'opacity')` |
-| spring | `{ duration: 700, create: { type: 'linear', property: 'opacity' }, update: { type: 'spring', springDamping: 0.4 }, delete: { type: 'linear', property: 'opacity' } }` |
-
----
-
-### `easeInEaseOut()`
-
-Calls `configureNext()` with `Presets.easeInEaseOut`.
-
----
-
-### `linear()`
-
-Calls `configureNext()` with `Presets.linear`.
-
----
-
-### `spring()`
-
-Calls `configureNext()` with `Presets.spring`.
diff --git a/website/versioned_docs/version-0.60/libraries.md b/website/versioned_docs/version-0.60/libraries.md
deleted file mode 100644
index 3221eb0092d..00000000000
--- a/website/versioned_docs/version-0.60/libraries.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-id: libraries
-title: Using Libraries
-author: Brent Vatne
-authorURL: 'https://twitter.com/notbrent'
-description: This guide introduces React Native developers to finding, installing, and using third-party libraries in their apps.
----
-
-React Native provides a set of built-in [Core Components and APIs](./components-and-apis) ready to use in your app. You're not limited to the components and APIs bundled with React Native. React Native has a community of thousands of developers. If the Core Components and APIs don't have what you are looking for, you may be able to find and install a library from the community to add the functionality to your app.
-
-## Selecting a Package Manager
-
-React Native libraries are typically installed from the [npm registry](https://www.npmjs.com/) using a Node.js package manager such as [npm CLI](https://docs.npmjs.com/cli/npm) or [Yarn Classic](https://classic.yarnpkg.com/en/).
-
-If you have Node.js installed on your computer then you already have the npm CLI installed. Some developers prefer to use Yarn Classic for slightly faster install times and additional advanced features like Workspaces. Both tools work great with React Native. We will assume npm for the rest of this guide for simplicity of explanation.
-
-> 💡 The terms "library" and "package" are used interchangably in the JavaScript community.
-
-## Installing a Library
-
-To install a library in your project, navigate to your project directory in your terminal and run `npm install `. Let's try this with `react-native-webview`:
-
-```bash
-npm install react-native-webview
-```
-
-The library that we installed includes native code, and we need to link to our app before we use it.
-
-## Linking Native Code on iOS
-
-React Native uses CocoaPods to manage iOS project dependencies and most React Native libraries follow this same convention. If a library you are using does not, then please refer to their README for additional instruction. In most cases, the following instructions will apply.
-
-Run `pod install` in our `ios` directory in order to link it to our native iOS project. A shortcut for doing this without switching to the `ios` directory is to run `npx pod-install`.
-
-```bash
-npx pod-install
-```
-
-Once this is complete, re-build the app binary to start using your new library:
-
-```bash
-npx react-native run-ios
-```
-
-## Linking Native Code on Android
-
-React Native uses Gradle to manage Android project dependencies. After you install a library with native dependencies, you will need to re-build the app binary to use your new library:
-
-```bash
-npx react-native run-android
-```
-
-## Finding Libraries
-
-[React Native Directory](https://reactnative.directory) is a searchable database of libraries built specifically for React Native. This is the first place to look for a library for your React Native app.
-
-Many of the libraries you will find on the directory are from [React Native Community](https://github.com/react-native-community/) or [Expo](https://docs.expo.io/versions/latest/).
-
-Libraries built by the React Native Community are driven by volunteers and individuals at companies that depend on React Native. They often support iOS, tvOS, Android, Windows, but this varies across projects. Many of the libraries in this organization were once React Native Core Components and APIs.
-
-Libraries built by Expo are all written in TypeScript and support iOS, Android, and react-native-web wherever possible. They usually require that you first install [react-native-unimodules](https://github.com/expo/expo/tree/master/packages/react-native-unimodules) in order to use in your React Native app.
-
-After React Native Directory, the [npm registry](https://www.npmjs.com/) is the next best place if you can't find a library specifically for React Native on the directory. The npm registry is the definitive source for JavaScript libraries, but the libraries that it lists may not all be compatible with React Native. React Native is one of many JavaScript programming environments, including Node.js, web browsers, Electron, and more, and npm includes libraries that work for all of these environments.
-
-## Determining Library Compatibility
-
-### Does it work with React Native?
-
-Usually libraries built _specifically for other platforms_ will not work with React Native. Examples include `react-select` which is built for the web and specifically targets `react-dom`, and `rimraf` which is built for Node.js and interacts with your computer file system. Other libraries like `lodash` use only JavaScript language features and work in any environment. You will gain a sense for this over time, but until then the easiest way to find out is to try it yourself. You can remove packages using `npm uninstall` if it turns out that it does not work in React Native.
-
-### Does it work for the platforms that my app supports?
-
-[React Native Directory](https://reactnative.directory) allows you to filter by platform compatibility, such as iOS, Android, Web, and Windows. If the library you would like to use is not currently listed there, refer to the README for the library to learn more.
-
-### Does it work with my app version of React Native?
-
-The latest version of a library is typically compatible with the latest version of React Native. If you are using an older version, you should refer to the README to know which version of the library you should install. You can install a particular version of the library by running `npm install @`, for example: `npm install @react-native-community/netinfo@^2.0.0`.
diff --git a/website/versioned_docs/version-0.60/linking-libraries-ios.md b/website/versioned_docs/version-0.60/linking-libraries-ios.md
deleted file mode 100644
index 4862211e5f7..00000000000
--- a/website/versioned_docs/version-0.60/linking-libraries-ios.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-id: linking-libraries-ios
-title: Linking Libraries
----
-
-Not every app uses all the native capabilities, and including the code to support all those features would impact the binary size... But we still want to support these features whenever you need them.
-
-With that in mind we exposed many of these features as independent static libraries.
-
-For most of the libs it will be as quick as dragging two files, sometimes a third step will be necessary, but no more than that.
-
-_All the libraries we ship with React Native live on the `Libraries` folder in the root of the repository. Some of them are pure JavaScript, and you only need to `require` it. Other libraries also rely on some native code, in that case you'll have to add these files to your app, otherwise the app will throw an error as soon as you try to use the library._
-
-## Here are the few steps to link your libraries that contain native code
-
-### Automatic linking
-
-#### Step 1
-
-Install a library with native dependencies:
-
-```bash
-$ npm install --save
-```
-
-> **_Note:_** `--save` or `--save-dev` flag is very important for this step. React Native will link your libs based on `dependencies` and `devDependencies` in your `package.json` file.
-
-#### Step 2
-
-Link your native dependencies:
-
-```bash
-$ react-native link
-```
-
-Done! All libraries with native dependencies should be successfully linked to your iOS/Android project.
-
-> **_Note:_** If your iOS project is using CocoaPods (contains `Podfile`) and linked library has `podspec` file, then `react-native link` will link library using Podfile. To support non-trivial Podfiles add `# Add new pods below this line` comment to places where you expect pods to be added.
-
-### Manual linking
-
-#### Step 1
-
-If the library has native code, there must be an `.xcodeproj` file inside its folder. Drag this file to your project on Xcode (usually under the `Libraries` group on Xcode);
-
-
-
-#### Step 2
-
-Click on your main project file (the one that represents the `.xcodeproj`) select `Build Phases` and drag the static library from the `Products` folder inside the Library you are importing to `Link Binary With Libraries`
-
-
-
-#### Step 3
-
-Not every library will need this step, what you need to consider is:
-
-_Do I need to know the contents of the library at compile time?_
-
-What that means is, are you using this library on the native side or only in JavaScript? If you are only using it in JavaScript, you are good to go!
-
-If you do need to call it from native, then we need to know the library's headers. To achieve that you have to go to your project's file, select `Build Settings` and search for `Header Search Paths`. There you should include the path to your library. (This documentation used to recommend using `recursive`, but this is no longer recommended, as it can cause subtle build failures, especially with CocoaPods.)
-
-
diff --git a/website/versioned_docs/version-0.60/linking.md b/website/versioned_docs/version-0.60/linking.md
deleted file mode 100644
index a99c84e833e..00000000000
--- a/website/versioned_docs/version-0.60/linking.md
+++ /dev/null
@@ -1,235 +0,0 @@
----
-id: linking
-title: Linking
----
-
-
-
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
-
-
`](http://developer.android.com/guide/topics/manifest/activity-element.html) documentation for more information.
-
-```xml
-
-```
-
-NOTE: On iOS, you'll need to link `RCTLinking` to your project by following the steps described [here](linking-libraries-ios.md#manual-linking). If you also want to listen to incoming app links during your app's execution, you'll need to add the following lines to your `*AppDelegate.m`:
-
-```objectivec
-// iOS 9.x or newer
-#import
-
-- (BOOL)application:(UIApplication *)application
- openURL:(NSURL *)url
- options:(NSDictionary *)options
-{
- return [RCTLinkingManager application:application openURL:url options:options];
-}
-```
-
-If you're targeting iOS 8.x or older, you can use the following code instead:
-
-```objectivec
-// iOS 8.x or older
-#import
-
-- (BOOL)application:(UIApplication *)application openURL:(NSURL *)url
- sourceApplication:(NSString *)sourceApplication annotation:(id)annotation
-{
- return [RCTLinkingManager application:application openURL:url
- sourceApplication:sourceApplication annotation:annotation];
-}
-```
-
-If your app is using [Universal Links](https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/AppSearch/UniversalLinks.html), you'll need to add the following code as well:
-
-```objectivec
-- (BOOL)application:(UIApplication *)application continueUserActivity:(nonnull NSUserActivity *)userActivity
- restorationHandler:(nonnull void (^)(NSArray> * _Nullable))restorationHandler
-{
- return [RCTLinkingManager application:application
- continueUserActivity:userActivity
- restorationHandler:restorationHandler];
-}
-```
-
-And then on your React component you'll be able to listen to the events on `Linking` as follows:
-
-```jsx
-componentDidMount() {
- Linking.addEventListener('url', this._handleOpenURL);
-},
-componentWillUnmount() {
- Linking.removeEventListener('url', this._handleOpenURL);
-},
-_handleOpenURL(event) {
- console.log(event.url);
-}
-```
-
-#### Opening external links
-
-To start the corresponding activity for a link (web URL, email, contact etc.), call:
-
-```jsx
-Linking.openURL(url).catch(err =>
- console.error('An error occurred', err),
-);
-```
-
-If you want to check if any installed app can handle a given URL beforehand you can call:
-
-```jsx
-Linking.canOpenURL(url)
- .then(supported => {
- if (!supported) {
- console.log("Can't handle url: " + url);
- } else {
- return Linking.openURL(url);
- }
- })
- .catch(err => console.error('An error occurred', err));
-```
-
----
-
-# Reference
-
-## Methods
-
-### `constructor()`
-
-```jsx
-constructor();
-```
-
----
-
-### `addEventListener()`
-
-```jsx
-addEventListener(type, handler);
-```
-
-Add a handler to Linking changes by listening to the `url` event type and providing the handler.
-
----
-
-### `removeEventListener()`
-
-```jsx
-removeEventListener(type, handler);
-```
-
-Remove a handler by passing the `url` event type and the handler.
-
----
-
-### `openURL()`
-
-```jsx
-openURL(url);
-```
-
-Try to open the given `url` with any of the installed apps.
-
-You can use other URLs, like a location (e.g. "geo:37.484847,-122.148386" on Android or "http://maps.apple.com/?ll=37.484847,-122.148386" on iOS), a contact, or any other URL that can be opened with the installed apps.
-
-The method returns a `Promise` object. If the user confirms the open dialog or the url automatically opens, the promise is resolved. If the user cancels the open dialog or there are no registered applications for the url, the promise is rejected.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ---- | ------ | -------- | ---------------- |
-| url | string | Yes | The URL to open. |
-
-> This method will fail if the system doesn't know how to open the specified URL. If you're passing in a non-http(s) URL, it's best to check {@code canOpenURL} first.
-
-> For web URLs, the protocol ("http://", "https://") must be set accordingly!
-
----
-
-### `canOpenURL()`
-
-```jsx
-canOpenURL(url);
-```
-
-Determine whether or not an installed app can handle a given URL.
-
-The method returns a `Promise` object. When it is determined whether or not the given URL can be handled, the promise is resolved and the first parameter is whether or not it can be opened.
-
-The `Promise` will reject on Android if it was impossible to check if the URL can be opened, and on iOS if you didn't add the specific scheme in the `LSApplicationQueriesSchemes` key inside `Info.plist` (see bellow).
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ---- | ------ | -------- | ---------------- |
-| url | string | Yes | The URL to open. |
-
-> For web URLs, the protocol ("http://", "https://") must be set accordingly!
-
-> As of iOS 9, your app needs to provide the `LSApplicationQueriesSchemes` key inside `Info.plist` or canOpenURL will always return false.
-
-> This method has limitations on iOS 9+. From [the official Apple documentation](https://developer.apple.com/documentation/uikit/uiapplication/1622952-canopenurl):
-
-> If your app is linked against an earlier version of iOS but is running in iOS 9.0 or later, you can call this method up to 50 times. After reaching that limit, subsequent calls always return false. If the user reinstalls or upgrades the app, iOS resets the limit.
-
----
-
-### `openSettings()`
-
-```jsx
-openSettings();
-```
-
-Open the Settings app and displays the app’s custom settings, if it has any.
-
----
-
-### `getInitialURL()`
-
-```jsx
-getInitialURL();
-```
-
-If the app launch was triggered by an app link, it will give the link url, otherwise it will give `null`.
-
-> To support deep linking on Android, refer http://developer.android.com/training/app-indexing/deep-linking.html#handling-intents
-
----
-
-### `sendIntent()`
-
-```jsx
-sendIntent(action: string, extras?: Array<{key: string, value: string | number | boolean}>)
-```
-
-> @platform android
-
-**Android-Only.** Launch an Android intent with extras (optional)
diff --git a/website/versioned_docs/version-0.60/listview.md b/website/versioned_docs/version-0.60/listview.md
deleted file mode 100644
index e483add4494..00000000000
--- a/website/versioned_docs/version-0.60/listview.md
+++ /dev/null
@@ -1,267 +0,0 @@
----
-id: listview
-title: ListView
----
-
-DEPRECATED - use one of the new list components, such as [`FlatList`](flatlist.md) or [`SectionList`](sectionlist.md) for bounded memory use, fewer bugs, better performance, an easier to use API, and more features. Check out this [blog post](/blog/2017/03/13/better-list-views) for more details.
-
-ListView - A core component designed for efficient display of vertically scrolling lists of changing data. The minimal API is to create a [`ListView.DataSource`](/docs/0.60/listviewdatasource), populate it with a flat array of data blobs, and instantiate a `ListView` component with that data source and a `renderRow` callback which takes a blob from the data array and returns a renderable component.
-
-Minimal example:
-
-```jsx
-class MyComponent extends Component {
- constructor() {
- super();
- const ds = new ListView.DataSource({
- rowHasChanged: (r1, r2) => r1 !== r2,
- });
- this.state = {
- dataSource: ds.cloneWithRows(['row 1', 'row 2']),
- };
- }
-
- render() {
- return (
- {rowData} }
- />
- );
- }
-}
-```
-
-ListView also supports more advanced features, including sections with sticky section headers, header and footer support, callbacks on reaching the end of the available data (`onEndReached`) and on the set of rows that are visible in the device viewport change (`onChangeVisibleRows`), and several performance optimizations.
-
-There are a few performance operations designed to make ListView scroll smoothly while dynamically loading potentially very large (or conceptually infinite) data sets:
-
-- Only re-render changed rows - the rowHasChanged function provided to the data source tells the ListView if it needs to re-render a row because the source data has changed - see ListViewDataSource for more details.
-
-- Rate-limited row rendering - By default, only one row is rendered per event-loop (customizable with the `pageSize` prop). This breaks up the work into smaller chunks to reduce the chance of dropping frames while rendering rows.
-
-# Reference
-
-## Props
-
-### `dataSource`
-
-An instance of [ListView.DataSource](listviewdatasource.md) to use
-
-| Type | Required |
-| ------------------ | -------- |
-| ListViewDataSource | Yes |
-
----
-
-### `initialListSize`
-
-How many rows to render on initial component mount. Use this to make it so that the first screen worth of data appears at one time instead of over the course of multiple frames.
-
-| Type | Required |
-| ------ | -------- |
-| number | Yes |
-
----
-
-### `onEndReachedThreshold`
-
-Threshold in pixels (virtual, not physical) for calling onEndReached.
-
-| Type | Required |
-| ------ | -------- |
-| number | Yes |
-
----
-
-### `pageSize`
-
-Number of rows to render per event loop. Note: if your 'rows' are actually cells, i.e. they don't span the full width of your view (as in the ListViewGridLayoutExample), you should set the pageSize to be a multiple of the number of cells per row, otherwise you're likely to see gaps at the edge of the ListView as new pages are loaded.
-
-| Type | Required |
-| ------ | -------- |
-| number | Yes |
-
----
-
-### `renderRow`
-
-(rowData, sectionID, rowID, highlightRow) => renderable
-
-Takes a data entry from the data source and its ids and should return a renderable component to be rendered as the row. By default the data is exactly what was put into the data source, but it's also possible to provide custom extractors. ListView can be notified when a row is being highlighted by calling `highlightRow(sectionID, rowID)`. This sets a boolean value of adjacentRowHighlighted in renderSeparator, allowing you to control the separators above and below the highlighted row. The highlighted state of a row can be reset by calling highlightRow(null).
-
-| Type | Required |
-| -------- | -------- |
-| function | Yes |
-
----
-
-### `renderScrollComponent`
-
-(props) => renderable
-
-A function that returns the scrollable component in which the list rows are rendered. Defaults to returning a ScrollView with the given props.
-
-| Type | Required |
-| -------- | -------- |
-| function | Yes |
-
----
-
-### `scrollRenderAheadDistance`
-
-How early to start rendering rows before they come on screen, in pixels.
-
-| Type | Required |
-| ------ | -------- |
-| number | Yes |
-
----
-
-### `stickyHeaderIndices`
-
-An array of child indices determining which children get docked to the top of the screen when scrolling. For example, passing `stickyHeaderIndices={[0]}` will cause the first child to be fixed to the top of the scroll view. This property is not supported in conjunction with `horizontal={true}`.
-
-| Type | Required |
-| --------------- | -------- |
-| array of number | Yes |
-
----
-
-### `enableEmptySections`
-
-Flag indicating whether empty section headers should be rendered. In the future release empty section headers will be rendered by default, and the flag will be deprecated. If empty sections are not desired to be rendered their indices should be excluded from sectionID object.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `renderHeader`
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onEndReached`
-
-Called when all rows have been rendered and the list has been scrolled to within onEndReachedThreshold of the bottom. The native scroll event is provided.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `stickySectionHeadersEnabled`
-
-Makes the sections headers sticky. The sticky behavior means that it will scroll with the content at the top of the section until it reaches the top of the screen, at which point it will stick to the top until it is pushed off the screen by the next section header. This property is not supported in conjunction with `horizontal={true}`. Only enabled by default on iOS because of typical platform standards.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `renderSectionHeader`
-
-(sectionData, sectionID) => renderable
-
-If provided, a header is rendered for this section.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `renderSeparator`
-
-(sectionID, rowID, adjacentRowHighlighted) => renderable
-
-If provided, a renderable component to be rendered as the separator below each row but not the last row if there is a section header below. Take a sectionID and rowID of the row above and whether its adjacent row is highlighted.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onChangeVisibleRows`
-
-(visibleRows, changedRows) => void
-
-Called when the set of visible rows changes. `visibleRows` maps { sectionID: { rowID: true }} for all the visible rows, and `changedRows` maps { sectionID: { rowID: true | false }} for the rows that have changed their visibility, with true indicating visible, and false indicating the view has moved out of view.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `removeClippedSubviews`
-
-A performance optimization for improving scroll perf of large lists, used in conjunction with overflow: 'hidden' on the row containers. This is enabled by default.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `renderFooter`
-
-() => renderable
-
-The header and footer are always rendered (if these props are provided) on every render pass. If they are expensive to re-render, wrap them in StaticContainer or other mechanism as appropriate. Footer is always at the bottom of the list, and header at the top, on every render pass. In a horizontal ListView, the header is rendered on the left and the footer on the right.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
-## Methods
-
-### `getMetrics()`
-
-```jsx
-getMetrics();
-```
-
-Exports some data, e.g. for perf investigations or analytics.
-
----
-
-### `scrollTo()`
-
-```jsx
-scrollTo((...args: Array));
-```
-
-Scrolls to a given x, y offset, either immediately or with a smooth animation.
-
-See `ScrollView#scrollTo`.
-
----
-
-### `scrollToEnd()`
-
-```jsx
-scrollToEnd(([options]: {animated: boolean}));
-```
-
-If this is a vertical ListView scrolls to the bottom. If this is a horizontal ListView scrolls to the right.
-
-Use `scrollToEnd({animated: true})` for smooth animated scrolling, `scrollToEnd({animated: false})` for immediate scrolling. If no options are passed, `animated` defaults to true.
-
----
-
-### `flashScrollIndicators()`
-
-```jsx
-flashScrollIndicators();
-```
-
-Displays the scroll indicators momentarily.
diff --git a/website/versioned_docs/version-0.60/listviewdatasource.md b/website/versioned_docs/version-0.60/listviewdatasource.md
deleted file mode 100644
index 7e9265d23b5..00000000000
--- a/website/versioned_docs/version-0.60/listviewdatasource.md
+++ /dev/null
@@ -1,204 +0,0 @@
----
-id: listviewdatasource
-title: ListViewDataSource
----
-
-Provides efficient data processing and access to the `ListView` component. A `ListViewDataSource` is created with functions for extracting data from the input blob, and comparing elements (with default implementations for convenience). The input blob can be as flat as an array of strings, or an object with rows nested inside section objects.
-
-To update the data in the datasource, use `cloneWithRows` (or `cloneWithRowsAndSections` if you care about sections). The data in the data source is immutable, so you can't modify it directly. The clone methods take in the new data and compute a diff for each row so ListView knows whether to re-render it or not.
-
-In this example, a component receives data in chunks, handled by `_onDataArrived`, which concats the new data onto the old data and updates the data source. We use `concat` to create a new array - mutating `this._data`, e.g. with `this._data.push(newRowData)`, would be an error. `_rowHasChanged` understands the shape of the row data and knows how to efficiently compare it.
-
-```jsx
-getInitialState: function() {
- var ds = new ListView.DataSource({rowHasChanged: this._rowHasChanged});
- return {ds};
-},
-_onDataArrived(newData) {
- this._data = this._data.concat(newData);
- this.setState({
- ds: this.state.ds.cloneWithRows(this._data)
- });
-}
-```
-
-### Methods
-
-- [`constructor`](listviewdatasource.md#constructor)
-- [`cloneWithRows`](listviewdatasource.md#clonewithrows)
-- [`cloneWithRowsAndSections`](listviewdatasource.md#clonewithrowsandsections)
-- [`getRowCount`](listviewdatasource.md#getrowcount)
-- [`getRowAndSectionCount`](listviewdatasource.md#getrowandsectioncount)
-- [`rowShouldUpdate`](listviewdatasource.md#rowshouldupdate)
-- [`getRowData`](listviewdatasource.md#getrowdata)
-- [`getRowIDForFlatIndex`](listviewdatasource.md#getrowidforflatindex)
-- [`getSectionIDForFlatIndex`](listviewdatasource.md#getsectionidforflatindex)
-- [`getSectionLengths`](listviewdatasource.md#getsectionlengths)
-- [`sectionHeaderShouldUpdate`](listviewdatasource.md#sectionheadershouldupdate)
-- [`getSectionHeaderData`](listviewdatasource.md#getsectionheaderdata)
-
----
-
-# Reference
-
-## Methods
-
-### `constructor()`
-
-```jsx
-constructor(params);
-```
-
-You can provide custom extraction and `hasChanged` functions for section headers and rows. If absent, data will be extracted with the `defaultGetRowData` and `defaultGetSectionHeaderData` functions.
-
-The default extractor expects data of one of the following forms:
-
- { sectionID_1: { rowID_1: , ... }, ... }
-
-or
-
- { sectionID_1: [ , , ... ], ... }
-
-or
-
- [ [ , , ... ], ... ]
-
-The constructor takes in a params argument that can contain any of the following:
-
-- getRowData(dataBlob, sectionID, rowID);
-- getSectionHeaderData(dataBlob, sectionID);
-- rowHasChanged(prevRowData, nextRowData);
-- sectionHeaderHasChanged(prevSectionData, nextSectionData);
-
----
-
-### `cloneWithRows()`
-
-```jsx
-cloneWithRows(dataBlob, rowIdentities);
-```
-
-Clones this `ListViewDataSource` with the specified `dataBlob` and `rowIdentities`. The `dataBlob` an arbitrary blob of data. At construction an extractor to get the interesting information was defined (or the default was used).
-
-The `rowIdentities` is a 2D array of identifiers for rows. ie. [['a1', 'a2'], ['b1', 'b2', 'b3'], ...]. If not provided, it's assumed that the keys of the section data are the row identities.
-
-Note: This function does NOT clone the data in this data source. It only passes the functions defined at construction to a new data source with the data specified. If you wish to maintain the existing data you must handle merging of old and new data separately and then pass that into this function as the `dataBlob`.
-
----
-
-### `cloneWithRowsAndSections()`
-
-```jsx
-cloneWithRowsAndSections(
- dataBlob,
- sectionIdentities,
- rowIdentities,
-);
-```
-
-This performs the same function as the `cloneWithRows` function but here you also specify what your `sectionIdentities` are. If you don't care about sections you should safely be able to use `cloneWithRows`.
-
-`sectionIdentities` is an array of identifiers for sections. ie. ['s1', 's2', ...]. The identifiers should correspond to the keys or array indexes of the data you wish to include. If not provided, it's assumed that the keys of dataBlob are the section identities.
-
-Note: this returns a new object!
-
-```
-const dataSource = ds.cloneWithRowsAndSections({
- addresses: ['row 1', 'row 2'],
- phone_numbers: ['data 1', 'data 2'],
-}, ['phone_numbers']);
-```
-
----
-
-### `getRowCount()`
-
-```jsx
-getRowCount();
-```
-
-Returns the total number of rows in the data source.
-
-If you are specifying the rowIdentities or sectionIdentities, then `getRowCount` will return the number of rows in the filtered data source.
-
----
-
-### `getRowAndSectionCount()`
-
-```jsx
-getRowAndSectionCount();
-```
-
-Returns the total number of rows in the data source (see `getRowCount` for how this is calculated) plus the number of sections in the data.
-
-If you are specifying the rowIdentities or sectionIdentities, then `getRowAndSectionCount` will return the number of rows & sections in the filtered data source.
-
----
-
-### `rowShouldUpdate()`
-
-```jsx
-rowShouldUpdate(sectionIndex, rowIndex);
-```
-
-Returns if the row is dirtied and needs to be rerendered
-
----
-
-### `getRowData()`
-
-```jsx
-getRowData(sectionIndex, rowIndex);
-```
-
-Gets the data required to render the row.
-
----
-
-### `getRowIDForFlatIndex()`
-
-```jsx
-getRowIDForFlatIndex(index);
-```
-
-Gets the rowID at index provided if the dataSource arrays were flattened, or null of out of range indexes.
-
----
-
-### `getSectionIDForFlatIndex()`
-
-```jsx
-getSectionIDForFlatIndex(index);
-```
-
-Gets the sectionID at index provided if the dataSource arrays were flattened, or null for out of range indexes.
-
----
-
-### `getSectionLengths()`
-
-```jsx
-getSectionLengths();
-```
-
-Returns an array containing the number of rows in each section
-
----
-
-### `sectionHeaderShouldUpdate()`
-
-```jsx
-sectionHeaderShouldUpdate(sectionIndex);
-```
-
-Returns if the section header is dirtied and needs to be rerendered
-
----
-
-### `getSectionHeaderData()`
-
-```jsx
-getSectionHeaderData(sectionIndex);
-```
-
-Gets the data required to render the section header
diff --git a/website/versioned_docs/version-0.60/maskedviewios.md b/website/versioned_docs/version-0.60/maskedviewios.md
deleted file mode 100644
index b7b2e8ad624..00000000000
--- a/website/versioned_docs/version-0.60/maskedviewios.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-id: maskedviewios
-title: '🚧 MaskedViewIOS'
----
-
-> **Deprecated.** Use [@react-native-community/masked-view](https://github.com/react-native-community/react-native-masked-view) instead.
-
-Renders the child view with a mask specified in the `maskElement` prop.
-
-## Example
-
-```jsx
-import React from 'react';
-import {MaskedViewIOS, Text, View} from 'react-native';
-
-class MyMaskedView extends React.Component {
- render() {
- return (
- // Determines shape of the mask
-
-
- Basic Mask
-
-
- }>
- {/* Shows behind the mask, you can put anything here, such as an image */}
-
- );
- }
-}
-```
-
-The following image demonstrates that you can put almost anything behind the mask. The three examples shown are masked ``, ``, and ``.
-
-
- {
- Alert.alert('Modal has been closed.');
- }}>
-
-
- Hello World!
-
- {
- this.setModalVisible(!this.state.modalVisible);
- }}>
- Hide Modal
-
-
-
-
-
- {
- this.setModalVisible(true);
- }}>
- Show Modal
-
-
- );
- }
-}
-```
-
----
-
-# Reference
-
-## Props
-
-### `visible`
-
-The `visible` prop determines whether your modal is visible.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `supportedOrientations`
-
-The `supportedOrientations` prop allows the modal to be rotated to any of the specified orientations. On iOS, the modal is still restricted by what's specified in your app's Info.plist's UISupportedInterfaceOrientations field. When using `presentationStyle` of `pageSheet` or `formSheet`, this property will be ignored by iOS.
-
-| Type | Required | Platform |
-| --------------------------------------------------------------------------------------------------- | -------- | -------- |
-| array of enum('portrait', 'portrait-upside-down', 'landscape', 'landscape-left', 'landscape-right') | No | iOS |
-
----
-
-### `onRequestClose`
-
-The `onRequestClose` callback is called when the user taps the hardware back button on Android or the menu button on Apple TV. Because of this required prop, be aware that `BackHandler` events will not be emitted as long as the modal is open.
-
-| Type | Required | Platform |
-| -------- | -------- | ------------------------ |
-| function | Yes | Android, Platform.isTVOS |
-| function | No | (Others) |
-
----
-
-### `onShow`
-
-The `onShow` prop allows passing a function that will be called once the modal has been shown.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `transparent`
-
-The `transparent` prop determines whether your modal will fill the entire view. Setting this to `true` will render the modal over a transparent background.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `animationType`
-
-The `animationType` prop controls how the modal animates.
-
-- `slide` slides in from the bottom
-- `fade` fades into view
-- `none` appears without an animation
-
-Default is set to `none`.
-
-| Type | Required |
-| ----------------------------- | -------- |
-| enum('none', 'slide', 'fade') | No |
-
----
-
-### `hardwareAccelerated`
-
-The `hardwareAccelerated` prop controls whether to force hardware acceleration for the underlying window.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `onDismiss`
-
-The `onDismiss` prop allows passing a function that will be called once the modal has been dismissed.
-
-| Type | Required | Platform |
-| -------- | -------- | -------- |
-| function | No | iOS |
-
----
-
-### `onOrientationChange`
-
-The `onOrientationChange` callback is called when the orientation changes while the modal is being displayed. The orientation provided is only 'portrait' or 'landscape'. This callback is also called on initial render, regardless of the current orientation.
-
-| Type | Required | Platform |
-| -------- | -------- | -------- |
-| function | No | iOS |
-
----
-
-### `presentationStyle`
-
-The `presentationStyle` prop controls how the modal appears (generally on larger devices such as iPad or plus-sized iPhones). See https://developer.apple.com/reference/uikit/uimodalpresentationstyle for details.
-
-- `fullScreen` covers the screen completely
-- `pageSheet` covers portrait-width view centered (only on larger devices)
-- `formSheet` covers narrow-width view centered (only on larger devices)
-- `overFullScreen` covers the screen completely, but allows transparency
-
-Default is set to `overFullScreen` or `fullScreen` depending on `transparent` property.
-
-| Type | Required | Platform |
-| -------------------------------------------------------------- | -------- | -------- |
-| enum('fullScreen', 'pageSheet', 'formSheet', 'overFullScreen') | No | iOS |
-
----
-
-### `animated`
-
-> **Deprecated.** Use the [`animationType`](modal.md#animationtype) prop instead.
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 8cc3ef11d43..00000000000
--- a/website/versioned_docs/version-0.60/more-resources.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-id: more-resources
-title: More Resources
----
-
-If you only read through this website, you should be able to build a pretty cool React Native app. But React Native isn't 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://reactjs.org/). 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 basic 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](/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
-
-- 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/signup?utm_source=Facebook%20React%20Native&utm_medium=Azure&utm_campaign=GitHub) is a service from Microsoft that allows you 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](https://appcenter.ms/signup?utm_source=Facebook%20React%20Native&utm_medium=Azure&utm_campaign=GitHub) 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/signup?utm_source=Facebook%20React%20Native&utm_medium=Azure&utm_campaign=GitHub), 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-android.md b/website/versioned_docs/version-0.60/native-components-android.md
deleted file mode 100644
index a97f61c5ff9..00000000000
--- a/website/versioned_docs/version-0.60/native-components-android.md
+++ /dev/null
@@ -1,183 +0,0 @@
----
-id: native-components-android
-title: Native UI Components
----
-
-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, we can 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 Android SDK programming. This guide will show you how to build a native UI component, walking you through the implementation of a subset of the existing `ImageView` component available in the core React Native library.
-
-## ImageView example
-
-For this example we are going to walk through the implementation requirements to allow the use of ImageViews in JavaScript.
-
-Native views are created and manipulated by extending `ViewManager` or more commonly `SimpleViewManager` . A `SimpleViewManager` is convenient in this case because it applies common properties such as background color, opacity, and Flexbox layout.
-
-These subclasses are essentially singletons - only one instance of each is created by the bridge. They vend native views to the `NativeViewHierarchyManager`, which delegates back to them to set and update the properties of the views as necessary. The `ViewManagers` are also typically the delegates for the views, sending events back to JavaScript via the bridge.
-
-To vend a view:
-
-1. Create the ViewManager subclass.
-2. Implement the `createViewInstance` method
-3. Expose view property setters using `@ReactProp` (or `@ReactPropGroup`) annotation
-4. Register the manager in `createViewManagers` of the applications package.
-5. Implement the JavaScript module
-
-## 1. Create the `ViewManager` subclass
-
-In this example we create view manager class `ReactImageManager` that extends `SimpleViewManager` of type `ReactImageView`. `ReactImageView` is the type of object managed by the manager, this will be the custom native view. Name returned by `getName` is used to reference the native view type from JavaScript.
-
-```java
-...
-
-public class ReactImageManager extends SimpleViewManager {
-
- public static final String REACT_CLASS = "RCTImageView";
-
- @Override
- public String getName() {
- return REACT_CLASS;
- }
-```
-
-## 2. Implement method `createViewInstance`
-
-Views are created in the `createViewInstance` method, the view should initialize itself in its default state, any properties will be set via a follow up call to `updateView.`
-
-```java
- @Override
- public ReactImageView createViewInstance(ThemedReactContext context) {
- return new ReactImageView(context, Fresco.newDraweeControllerBuilder(), mCallerContext);
- }
-```
-
-## 3. Expose view property setters using `@ReactProp` (or `@ReactPropGroup`) annotation
-
-Properties that are to be reflected in JavaScript needs to be exposed as setter method annotated with `@ReactProp` (or `@ReactPropGroup`). Setter method should take view to be updated (of the current view type) as a first argument and property value as a second argument. Setter should be declared as a `void` method and should be `public`. Property type sent to JS is determined automatically based on the type of value argument of the setter. The following type of values are currently supported: `boolean`, `int`, `float`, `double`, `String`, `Boolean`, `Integer`, `ReadableArray`, `ReadableMap`.
-
-Annotation `@ReactProp` has one obligatory argument `name` of type `String`. Name assigned to the `@ReactProp` annotation linked to the setter method is used to reference the property on JS side.
-
-Except from `name`, `@ReactProp` annotation may take following optional arguments: `defaultBoolean`, `defaultInt`, `defaultFloat`. Those arguments should be of the corresponding type (accordingly `boolean`, `int`, `float`) and the value provided will be passed to the setter method in case when the property that the setter is referencing has been removed from the component. Note that "default" values are only provided for primitive types, in case when setter is of some complex type, `null` will be provided as a default value in case when corresponding property gets removed.
-
-Setter declaration requirements for methods annotated with `@ReactPropGroup` are different than for `@ReactProp`, please refer to the `@ReactPropGroup` annotation class docs for more information about it.
-
-**IMPORTANT!** in ReactJS updating the property value will result in setter method call. Note that one of the ways we can update component is by removing properties that have been set before. In that case setter method will be called as well to notify view manager that property has changed. In that case "default" value will be provided (for primitive types "default" can value can be specified using `defaultBoolean`, `defaultFloat`, etc. arguments of `@ReactProp` annotation, for complex types setter will be called with value set to `null`).
-
-```java
- @ReactProp(name = "src")
- public void setSrc(ReactImageView view, @Nullable ReadableArray sources) {
- view.setSource(sources);
- }
-
- @ReactProp(name = "borderRadius", defaultFloat = 0f)
- public void setBorderRadius(ReactImageView view, float borderRadius) {
- view.setBorderRadius(borderRadius);
- }
-
- @ReactProp(name = ViewProps.RESIZE_MODE)
- public void setResizeMode(ReactImageView view, @Nullable String resizeMode) {
- view.setScaleType(ImageResizeMode.toScaleType(resizeMode));
- }
-```
-
-## 4. Register the `ViewManager`
-
-The final Java step is to register the ViewManager to the application, this happens in a similar way to [Native Modules](native-modules-android.md), via the applications package member function `createViewManagers.`
-
-```java
- @Override
- public List createViewManagers(
- ReactApplicationContext reactContext) {
- return Arrays.asList(
- new ReactImageManager()
- );
- }
-```
-
-## 5. Implement the JavaScript module
-
-The very final step is to create the JavaScript module that defines the interface layer between Java and JavaScript for the users of your new view. It is recommended for you to document the component interface in this module (e.g. using Flow, TypeScript, or plain old comments).
-
-```jsx
-// ImageView.js
-
-import {requireNativeComponent} from 'react-native';
-
-/**
- * Composes `View`.
- *
- * - src: string
- * - borderRadius: number
- * - resizeMode: 'cover' | 'contain' | 'stretch'
- */
-module.exports = requireNativeComponent('RCTImageView');
-```
-
-The `requireNativeComponent` function takes the name of the native view. Note that if your component needs to do anything more sophisticated (e.g. custom event handling), you should wrap the native component in another React component. This is illustrated in the `MyCustomView` example below.
-
-# Events
-
-So now we know how to expose native view components that we can control freely from JS, but how do we deal with events from the user, like pinch-zooms or panning? When a native event occurs the native code should issue an event to the JavaScript representation of the View, and the two views are linked with the value returned from the `getId()` method.
-
-```java
-class MyCustomView extends View {
- ...
- public void onReceiveNativeEvent() {
- WritableMap event = Arguments.createMap();
- event.putString("message", "MyMessage");
- ReactContext reactContext = (ReactContext)getContext();
- reactContext.getJSModule(RCTEventEmitter.class).receiveEvent(
- getId(),
- "topChange",
- event);
- }
-}
-```
-
-To map the `topChange` event name to the `onChange` callback prop in JavaScript, register it by overriding the `getExportedCustomBubblingEventTypeConstants` method in your `ViewManager`:
-
-```java
-public class ReactImageManager extends SimpleViewManager {
- ...
- public Map getExportedCustomBubblingEventTypeConstants() {
- return MapBuilder.builder()
- .put(
- "topChange",
- MapBuilder.of(
- "phasedRegistrationNames",
- MapBuilder.of("bubbled", "onChange")))
- .build();
- }
-}
-```
-
-This callback is invoked with the raw event, which we typically process in the wrapper component to make a simpler API:
-
-```jsx
-// MyCustomView.js
-
-class MyCustomView extends React.Component {
- constructor(props) {
- super(props);
- this._onChange = this._onChange.bind(this);
- }
- _onChange(event: Event) {
- if (!this.props.onChangeMessage) {
- return;
- }
- this.props.onChangeMessage(event.nativeEvent.message);
- }
- render() {
- return
-
-#import
-
-@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 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
-#import
-#import
-#import
-
-@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`:
-
-```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 (
-
-
-#import
-
-@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
-#import
-
-#import "RNTMapView.h"
-#import "RCTConvert+Mapkit.m"
-
-@interface RNTMapManager : RCTViewManager
-@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 simplify 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 (
-
-
-```
-
-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
-
- {
- this.myNativeReference.callNativeMethod();
- }}
- />
-
-```
-
-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 \*)commandArgs` - Args of the native method that we can pass from JS to native.
-
-`RNCMyNativeViewManager.m`
-
-```objectivec
-#import
-#import
-#import
-
-RCT_EXPORT_METHOD(callNativeMethod:(nonnull NSNumber*) reactTag) {
- [self.bridge.uiManager addUIBlock:^(RCTUIManager *uiManager, NSDictionary *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 (
-
-
- );
- }
-});
-
-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/0.60-stable/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 66587e0f840..00000000000
--- a/website/versioned_docs/version-0.60/native-modules-android.md
+++ /dev/null
@@ -1,464 +0,0 @@
----
-id: native-modules-android
-title: Native Modules
----
-
-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 similar to any other media asset, meaning there isn't anything unique 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 ReactApplicationContext reactContext;
-
- private static final String DURATION_SHORT_KEY = "SHORT";
- private static final String DURATION_LONG_KEY = "LONG";
-
- ToastModule(ReactApplicationContext context) {
- super(context);
- reactContext = context;
- }
-}
-```
-
-`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 getConstants() {
- final Map 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/0.60-stable/ReactAndroid/src/main/java/com/facebook/react/bridge/ReadableMap.java) and [ReadableArray](https://github.com/facebook/react-native/blob/0.60-stable/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 createViewManagers(ReactApplicationContext reactContext) {
- return Collections.emptyList();
- }
-
- @Override
- public List createNativeModules(
- ReactApplicationContext reactContext) {
- List 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 getPackages() {
- @SuppressWarnings("UnnecessaryLocalVariable")
- List 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 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 unique 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;
-import com.facebook.react.bridge.WritableMap;
-import com.facebook.react.bridge.Arguments;
-...
-private void sendEvent(ReactContext reactContext,
- String eventName,
- @Nullable WritableMap params) {
- reactContext
- .getJSModule(DeviceEventManagerModule.RCTDeviceEventEmitter.class)
- .emit(eventName, params);
-}
-...
-WritableMap params = Arguments.createMap();
-params.putString("eventProperty", "someValue");
-...
-sendEvent(reactContext, "EventReminder", params);
-```
-
-JavaScript modules can then register to receive events by `addListener` on the NativeEventEmitter class.
-
-```jsx
-import { NativeEventEmitter, NativeModules } from 'react-native';
-...
-
- componentDidMount() {
- ...
- const eventEmitter = new NativeEventEmitter(NativeModules.ToastExample);
- eventEmitter.addListener('EventReminder', (event) => {
- console.log(event.eventProperty) // "someValue"
- }
- ...
- }
-```
-
-### 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 basic 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-ios.md b/website/versioned_docs/version-0.60/native-modules-ios.md
deleted file mode 100644
index 395c05edd12..00000000000
--- a/website/versioned_docs/version-0.60/native-modules-ios.md
+++ /dev/null
@@ -1,518 +0,0 @@
----
-id: native-modules-ios
-title: Native Modules
----
-
-Sometimes an app needs to access a platform API and React Native doesn't have a corresponding module yet. Maybe you want to reuse some existing Objective-C, Swift or C++ 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.
-
-This is a more advanced guide that shows how to build a native module. It assumes the reader knows Objective-C or Swift and core libraries (Foundation, UIKit).
-
-## Native Module Setup
-
-Native modules are usually distributed as npm packages, except that for them to be native modules they will contain an Xcode library project. To get the basic scaffolding make sure to read [Native Modules Setup](native-modules-setup) guide first.
-
-## iOS Calendar Module Example
-
-This guide will use the [iOS Calendar API](https://developer.apple.com/library/mac/documentation/DataManagement/Conceptual/EventKitProgGuide/Introduction/Introduction.html) example. Let's say we would like to be able to access the iOS calendar from JavaScript.
-
-A native module is an Objective-C class that implements the `RCTBridgeModule` protocol. If you are wondering, RCT is an abbreviation of ReaCT.
-
-```objectivec
-// CalendarManager.h
-#import
-
-@interface CalendarManager : NSObject
-@end
-```
-
-In addition to implementing the `RCTBridgeModule` protocol, your class must also include the `RCT_EXPORT_MODULE()` macro. This takes an optional argument that specifies the name that the module will be accessible as in your JavaScript code (more on this later). If you do not specify a name, the JavaScript module name will match the Objective-C class name. If the Objective-C class name begins with RCT, the JavaScript module name will exclude the RCT prefix.
-
-```objectivec
-// CalendarManager.m
-#import "CalendarManager.h"
-
-@implementation CalendarManager
-
-// To export a module named CalendarManager
-RCT_EXPORT_MODULE();
-
-// This would name the module AwesomeCalendarManager instead
-// RCT_EXPORT_MODULE(AwesomeCalendarManager);
-
-@end
-```
-
-React Native will not expose any methods of `CalendarManager` to JavaScript unless explicitly told to. This is done using the `RCT_EXPORT_METHOD()` macro:
-
-```objectivec
-#import "CalendarManager.h"
-#import
-
-@implementation CalendarManager
-
-RCT_EXPORT_MODULE();
-
-RCT_EXPORT_METHOD(addEvent:(NSString *)name location:(NSString *)location)
-{
- RCTLogInfo(@"Pretending to create an event %@ at %@", name, location);
-}
-
-@end
-```
-
-Now, from your JavaScript file you can call the method like this (after making sure to rebuild):
-
-```jsx
-import {NativeModules} from 'react-native';
-var CalendarManager = NativeModules.CalendarManager;
-CalendarManager.addEvent(
- 'Birthday Party',
- '4 Privet Drive, Surrey',
-);
-```
-
-> **NOTE**: JavaScript method names
->
-> The name of the method exported to JavaScript is the native method's name up to the first colon. React Native also defines a macro called `RCT_REMAP_METHOD()` to specify the JavaScript method's name. This is useful when multiple native methods are the same up to the first colon and would have conflicting JavaScript names.
-
-The CalendarManager module is instantiated on the Objective-C side using a [CalendarManager new] call. 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).
-
-## Argument Types
-
-`RCT_EXPORT_METHOD` supports all standard JSON object types, such as:
-
-- string (`NSString`)
-- number (`NSInteger`, `float`, `double`, `CGFloat`, `NSNumber`)
-- boolean (`BOOL`, `NSNumber`)
-- array (`NSArray`) of any types from this list
-- object (`NSDictionary`) with string keys and values of any type from this list
-- function (`RCTResponseSenderBlock`)
-
-But it also works with any type that is supported by the `RCTConvert` class (see [`RCTConvert`](https://github.com/facebook/react-native/blob/0.60-stable/React/Base/RCTConvert.h) for details). The `RCTConvert` helper functions all accept a JSON value as input and map it to a native Objective-C type or class.
-
-In our `CalendarManager` example, we need to pass the event date to the native method. We can't send JavaScript Date objects over the bridge, so we need to convert the date to a string or number. We could write our native function like this:
-
-```objectivec
-RCT_EXPORT_METHOD(addEvent:(NSString *)name location:(NSString *)location date:(nonnull NSNumber *)secondsSinceUnixEpoch)
-{
- NSDate *date = [RCTConvert NSDate:secondsSinceUnixEpoch];
-}
-```
-
-or like this:
-
-```objectivec
-RCT_EXPORT_METHOD(addEvent:(NSString *)name location:(NSString *)location date:(NSString *)ISO8601DateString)
-{
- NSDate *date = [RCTConvert NSDate:ISO8601DateString];
-}
-```
-
-But by using the automatic type conversion feature, we can skip the manual conversion step completely, and write:
-
-```objectivec
-RCT_EXPORT_METHOD(addEvent:(NSString *)name location:(NSString *)location date:(NSDate *)date)
-{
- // Date is ready to use!
-}
-```
-
-You would then call this from JavaScript by using either:
-
-```jsx
-CalendarManager.addEvent(
- 'Birthday Party',
- '4 Privet Drive, Surrey',
- date.getTime(),
-); // passing date as number of milliseconds since UNIX epoch
-```
-
-or
-
-```jsx
-CalendarManager.addEvent(
- 'Birthday Party',
- '4 Privet Drive, Surrey',
- date.toISOString(),
-); // passing date as ISO-8601 string
-```
-
-And both values would get converted correctly to the native `NSDate`. A bad value, like an `Array`, would generate a helpful "RedBox" error message.
-
-As `CalendarManager.addEvent` method gets more and more complex, the number of arguments will grow. Some of them might be optional. In this case it's worth considering changing the API a little bit to accept a dictionary of event attributes, like this:
-
-```objectivec
-#import
-
-RCT_EXPORT_METHOD(addEvent:(NSString *)name details:(NSDictionary *)details)
-{
- NSString *location = [RCTConvert NSString:details[@"location"]];
- NSDate *time = [RCTConvert NSDate:details[@"time"]];
- ...
-}
-```
-
-and call it from JavaScript:
-
-```jsx
-CalendarManager.addEvent('Birthday Party', {
- location: '4 Privet Drive, Surrey',
- time: date.getTime(),
- description: '...',
-});
-```
-
-> **NOTE**: About array and map
->
-> Objective-C doesn't provide any guarantees about the types of values in these structures. Your native module might expect an array of strings, but if JavaScript calls your method with an array containing numbers and strings, you'll get an `NSArray` containing a mix of `NSNumber` and `NSString`. For arrays, `RCTConvert` provides some typed collections you can use in your method declaration, such as `NSStringArray`, or `UIColorArray`. For maps, it is the developer's responsibility to check the value types individually by manually calling `RCTConvert` helper methods.
-
-## Callbacks
-
-> **WARNING**
->
-> This section is more experimental than others because we don't have a solid set of best practices around callbacks yet.
-
-Native modules also supports a unique type of argument- a callback. In most cases it is used to provide the function call result to JavaScript.
-
-```objectivec
-RCT_EXPORT_METHOD(findEvents:(RCTResponseSenderBlock)callback)
-{
- NSArray *events = ...
- callback(@[[NSNull null], events]);
-}
-```
-
-`RCTResponseSenderBlock` accepts only one argument - an array of parameters to pass to the JavaScript callback. In this case we use Node's convention to make the first parameter an error object (usually `null` when there is no error) and the rest are the results of the function.
-
-```jsx
-CalendarManager.findEvents((error, events) => {
- if (error) {
- console.error(error);
- } else {
- this.setState({events: events});
- }
-});
-```
-
-A native module should invoke its callback exactly once. It's okay to store the callback and invoke it later. This pattern is often used to wrap iOS APIs that require delegates - see [`RCTAlertManager`](https://github.com/facebook/react-native/blob/0.60-stable/React/Modules/RCTAlertManager.m) for an example. If the callback is never invoked, some memory is leaked. If both `onSuccess` and `onFail` callbacks are passed, you should only invoke one of them.
-
-If you want to pass error-like objects to JavaScript, use `RCTMakeError` from [`RCTUtils.h`](https://github.com/facebook/react-native/blob/0.60-stable/React/Base/RCTUtils.h). Right now this only passes an Error-shaped dictionary to JavaScript, but we would like to automatically generate real JavaScript `Error` objects in the future.
-
-## Promises
-
-Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's `async/await` syntax. When the last parameters of a bridged native method are an `RCTPromiseResolveBlock` and `RCTPromiseRejectBlock`, its corresponding JS method will return a JS Promise object.
-
-Refactoring the above code to use a promise instead of callbacks looks like this:
-
-```objectivec
-RCT_REMAP_METHOD(findEvents,
- findEventsWithResolver:(RCTPromiseResolveBlock)resolve
- rejecter:(RCTPromiseRejectBlock)reject)
-{
- NSArray *events = ...
- if (events) {
- resolve(events);
- } else {
- NSError *error = ...
- reject(@"no_events", @"There were no events", error);
- }
-}
-```
-
-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 updateEvents() {
- try {
- var events = await CalendarManager.findEvents();
-
- this.setState({events});
- } catch (e) {
- console.error(e);
- }
-}
-
-updateEvents();
-```
-
-## Threading
-
-The native module should not have any assumptions about what thread it is being called on. React Native invokes native modules methods on a separate serial GCD queue, but this is an implementation detail and might change. The `- (dispatch_queue_t)methodQueue` method allows the native module to specify which queue its methods should be run on. For example, if it needs to use a main-thread-only iOS API, it should specify this via:
-
-```objectivec
-- (dispatch_queue_t)methodQueue
-{
- return dispatch_get_main_queue();
-}
-```
-
-Similarly, if an operation may take a long time to complete, the native module should not block and can specify it's own queue to run operations on. For example, the `RCTAsyncLocalStorage` module creates its own queue so the React queue isn't blocked waiting on potentially slow disk access:
-
-```objectivec
-- (dispatch_queue_t)methodQueue
-{
- return dispatch_queue_create("com.facebook.React.AsyncLocalStorageQueue", DISPATCH_QUEUE_SERIAL);
-}
-```
-
-The specified `methodQueue` will be shared by all of the methods in your module. If _only one_ of your methods is long-running (or needs to be run on a different queue than the others for some reason), you can use `dispatch_async` inside the method to perform that particular method's code on another queue, without affecting the others:
-
-```objectivec
-RCT_EXPORT_METHOD(doSomethingExpensive:(NSString *)param callback:(RCTResponseSenderBlock)callback)
-{
- dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0), ^{
- // Call long-running code on background thread
- ...
- // You can invoke callback from any thread/queue
- callback(@[...]);
- });
-}
-```
-
-> **NOTE**: Sharing dispatch queues between modules
->
-> The `methodQueue` method will be called once when the module is initialized, and then retained by the bridge, so there is no need to retain the queue yourself, unless you wish to make use of it within your module. However, if you wish to share the same queue between multiple modules then you will need to ensure that you retain and return the same queue instance for each of them; merely returning a queue of the same name for each won't work.
-
-## Dependency Injection
-
-The bridge initializes any registered RCTBridgeModules automatically, however you may wish to instantiate your own module instances (so you may inject dependencies, for example).
-
-You can do this by creating a class that implements the RCTBridgeDelegate Protocol, initializing an RCTBridge with the delegate as an argument and initialising a RCTRootView with the initialized bridge.
-
-```objectivec
-id moduleInitialiser = [[classThatImplementsRCTBridgeDelegate alloc] init];
-
-RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:moduleInitialiser launchOptions:nil];
-
-RCTRootView *rootView = [[RCTRootView alloc]
- initWithBridge:bridge
- moduleName:kModuleName
- initialProperties:nil];
-```
-
-## Exporting Constants
-
-A native module can export constants that are immediately available to JavaScript at runtime. This is useful for communicating static data that would otherwise require a round-trip through the bridge.
-
-```objectivec
-- (NSDictionary *)constantsToExport
-{
- return @{ @"firstDayOfTheWeek": @"Monday" };
-}
-```
-
-JavaScript can use this value right away, synchronously:
-
-```jsx
-console.log(CalendarManager.firstDayOfTheWeek);
-```
-
-Note that the constants are exported only at initialization time, so if you change `constantsToExport` values at runtime it won't affect the JavaScript environment.
-
-### Implementing `+ requiresMainQueueSetup`
-
-If you override `- constantsToExport` then you should also implement `+ requiresMainQueueSetup` to let React Native know if your module needs to be initialized on the main thread. Otherwise you will see a warning that in the future your module may be initialized on a background thread unless you explicitly opt out with `+ requiresMainQueueSetup`:
-
-```objectivec
-+ (BOOL)requiresMainQueueSetup
-{
- return YES; // only do this if your module initialization relies on calling UIKit!
-}
-```
-
-```Swift
-//Swift
-
-// CalendarManager.swift
-
-@objc(CalendarManager)
-class CalendarManager: NSObject, RCTBridgeModule {
-
-static func moduleName() -> String! {
- return "CalendarManager";
-}
-
-static func requiresMainQueueSetup() -> Bool {
- return true
-}
-```
-
-If your module does not require access to UIKit, then you should respond to `+ requiresMainQueueSetup` with `NO`.
-
-### Enum Constants
-
-Enums that are defined via `NS_ENUM` cannot be used as method arguments without first extending RCTConvert.
-
-In order to export the following `NS_ENUM` definition:
-
-```objectivec
-typedef NS_ENUM(NSInteger, UIStatusBarAnimation) {
- UIStatusBarAnimationNone,
- UIStatusBarAnimationFade,
- UIStatusBarAnimationSlide,
-};
-```
-
-You must create a class extension of RCTConvert like so:
-
-```objectivec
-@implementation RCTConvert (StatusBarAnimation)
- RCT_ENUM_CONVERTER(UIStatusBarAnimation, (@{ @"statusBarAnimationNone" : @(UIStatusBarAnimationNone),
- @"statusBarAnimationFade" : @(UIStatusBarAnimationFade),
- @"statusBarAnimationSlide" : @(UIStatusBarAnimationSlide)}),
- UIStatusBarAnimationNone, integerValue)
-@end
-```
-
-You can then define methods and export your enum constants like this:
-
-```objectivec
-- (NSDictionary *)constantsToExport
-{
- return @{ @"statusBarAnimationNone" : @(UIStatusBarAnimationNone),
- @"statusBarAnimationFade" : @(UIStatusBarAnimationFade),
- @"statusBarAnimationSlide" : @(UIStatusBarAnimationSlide) };
-};
-
-RCT_EXPORT_METHOD(updateStatusBarAnimation:(UIStatusBarAnimation)animation
- completion:(RCTResponseSenderBlock)callback)
-```
-
-Your enum will then be automatically unwrapped using the selector provided (`integerValue` in the above example) before being passed to your exported method.
-
-## Sending Events to JavaScript
-
-The native module can signal events to JavaScript without being invoked directly. The preferred way to do this is to subclass `RCTEventEmitter`, implement `supportedEvents` and call `self sendEventWithName`:
-
-```objectivec
-// CalendarManager.h
-#import
-#import
-
-@interface CalendarManager : RCTEventEmitter
-
-@end
-```
-
-```objectivec
-// CalendarManager.m
-#import "CalendarManager.h"
-
-@implementation CalendarManager
-
-RCT_EXPORT_MODULE();
-
-- (NSArray *)supportedEvents
-{
- return @[@"EventReminder"];
-}
-
-- (void)calendarEventReminderReceived:(NSNotification *)notification
-{
- NSString *eventName = notification.userInfo[@"name"];
- [self sendEventWithName:@"EventReminder" body:@{@"name": eventName}];
-}
-
-@end
-```
-
-JavaScript code can subscribe to these events by creating a new `NativeEventEmitter` instance around your module.
-
-```jsx
-import { NativeEventEmitter, NativeModules } from 'react-native';
-const { CalendarManager } = NativeModules;
-
-const calendarManagerEmitter = new NativeEventEmitter(CalendarManager);
-
-const subscription = calendarManagerEmitter.addListener(
- 'EventReminder',
- (reminder) => console.log(reminder.name)
-);
-...
-// Don't forget to unsubscribe, typically in componentWillUnmount
-subscription.remove();
-```
-
-### Optimizing for zero listeners
-
-You will receive a warning if you expend resources unnecessarily by emitting an event while there are no listeners. To avoid this, and to optimize your module's workload (e.g. by unsubscribing from upstream notifications or pausing background tasks), you can override `startObserving` and `stopObserving` in your `RCTEventEmitter` subclass.
-
-```objectivec
-@implementation CalendarManager
-{
- bool hasListeners;
-}
-
-// Will be called when this module's first listener is added.
--(void)startObserving {
- hasListeners = YES;
- // Set up any upstream listeners or background tasks as necessary
-}
-
-// Will be called when this module's last listener is removed, or on dealloc.
--(void)stopObserving {
- hasListeners = NO;
- // Remove upstream listeners, stop unnecessary background tasks
-}
-
-- (void)calendarEventReminderReceived:(NSNotification *)notification
-{
- NSString *eventName = notification.userInfo[@"name"];
- if (hasListeners) { // Only send events if anyone is listening
- [self sendEventWithName:@"EventReminder" body:@{@"name": eventName}];
- }
-}
-```
-
-## Exporting Swift
-
-Swift doesn't have support for macros so exposing it to React Native requires a bit more setup but works relatively the same.
-
-Let's say we have the same `CalendarManager` but as a Swift class:
-
-```swift
-// CalendarManager.swift
-
-@objc(CalendarManager)
-class CalendarManager: NSObject {
-
- @objc(addEvent:location:date:)
- func addEvent(name: String, location: String, date: NSNumber) -> Void {
- // Date is ready to use!
- }
-
- @objc
- func constantsToExport() -> [String: Any]! {
- return ["someKey": "someValue"]
- }
-
-}
-```
-
-> **NOTE**: It is important to use the @objc modifiers to ensure the class and functions are exported properly to the Objective-C runtime.
-
-Then create a private implementation file that will register the required information with the React Native bridge:
-
-```objectivec
-// CalendarManagerBridge.m
-#import
-
-@interface RCT_EXTERN_MODULE(CalendarManager, NSObject)
-
-RCT_EXTERN_METHOD(addEvent:(NSString *)name location:(NSString *)location date:(nonnull NSNumber *)date)
-
-@end
-```
-
-For those of you new to Swift and Objective-C, whenever you [mix the two languages in an iOS project](https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/BuildingCocoaApps/MixandMatch.html), you will also need an additional bridging file, known as a bridging header, to expose the Objective-C files to Swift. Xcode will offer to create this header file for you if you add your Swift file to your app through the Xcode `File>New File` menu option. You will need to import `RCTBridgeModule.h` in this header file.
-
-```objectivec
-// CalendarManager-Bridging-Header.h
-#import
-```
-
-You can also use `RCT_EXTERN_REMAP_MODULE` and `_RCT_EXTERN_REMAP_METHOD` to alter the JavaScript name of the module or methods you are exporting. For more information see [`RCTBridgeModule`](https://github.com/facebook/react-native/blob/0.60-stable/React/Base/RCTBridgeModule.h).
-
-> **Important when making third party modules**: Static libraries with Swift are only supported in Xcode 9 and later. In order for the Xcode project to build when you use Swift in the iOS static library you include in the module, your main app project must contain Swift code and a bridging header itself. If your app project does not contain any Swift code, a workaround can be a single empty .swift file and an empty bridging header.
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 9c10b4a729f..00000000000
--- a/website/versioned_docs/version-0.60/native-modules-setup.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-id: native-modules-setup
-title: 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 only 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 efec97b5e99..00000000000
--- a/website/versioned_docs/version-0.60/navigation.md
+++ /dev/null
@@ -1,122 +0,0 @@
----
-id: navigation
-title: Navigating Between Screens
----
-
-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 getting started with navigation, you will probably want to use [React Navigation](navigation.md#react-navigation). React Navigation provides a straightforward navigation solution, with the ability to present common stack navigation and tabbed navigation patterns on both Android and iOS.
-
-If you'd like to achieve a native look and feel on both Android and iOS, 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 a few lines of code.
-
-### Installation and setup
-
-First, you need to install them in your project:
-
-```shell
-npm install @react-navigation/native @react-navigation/stack
-```
-
-The second step is to install the required peer dependencies. You need to run different commands depending on whether your projects is an Expo managed project or a bare React Native project.
-
-- If you have an Expo managed project, install the dependencies with `expo`:
-
- ```shell
- expo install react-native-reanimated react-native-gesture-handler react-native-screens react-native-safe-area-context @react-native-community/masked-view
- ```
-
-- If you have an bare React Native project, install the dependencies with `npm`:
-
- ```shell
- npm install react-native-reanimated react-native-gesture-handler react-native-screens react-native-safe-area-context @react-native-community/masked-view
- ```
-
- For iOS with bare React Native project, make sure you have [CocoaPods](https://cocoapods.org/) installed. Then install the pods to complete the installation:
-
- ```shell
- cd ios
- pod install
- cd ..
- ```
-
-> Note: You might get warnings related to peer dependencies after installation. They are usually caused my incorrect version ranges specified in some packages. You can safely ignore most warnings as long as your app builds.
-
-To finalize installation of `react-native-gesture-handler`, add the following at the **top** (make sure it's at the top and there's nothing else before it) of your entry file, such as `index.js` or `App.js`:
-
-```js
-import 'react-native-gesture-handler';
-```
-
-Now, you need to wrap the whole app in `NavigationContainer`. Usually you'd do this in your entry file, such as `index.js` or `App.js`:
-
-```jsx
-import 'react-native-gesture-handler';
-import * as React from 'react';
-import {NavigationContainer} from '@react-navigation/native';
-
-export default function App() {
- return (
-
- {/* Rest of your app code */}
-
- );
-}
-```
-
-Now you are ready to build and run your app on the device/simulator.
-
-### Usage
-
-Now you can create an app with a home screen and a profile screen:
-
-```jsx
-import * as React from 'react';
-import {NavigationContainer} from '@react-navigation/native';
-import {createStackNavigator} from '@react-navigation/stack';
-
-const Stack = createStackNavigator();
-
-function MyStack() {
- return (
-
-
-
-
- );
-}
-```
-
-In this example, there are 2 screens (`Home` and `Profile`) defined using the `Stack.Screen` component. Similarly, you can define as many screens as you like.
-
-You can set options such as the screen title for each screen in the `options` prop of `Stack.Screen`.
-
-Each screen takes a `component` prop that is a React component. Those components receive a prop called `navigation` which has various methods to link to other screens. For example, you can use `navigation.navigate` to go to the `Profile` screen:
-
-```jsx
-function HomeScreen({navigation}) {
- return (
-
- navigation.navigate('Profile', {name: 'Jane'})
- }
- />
- );
-}
-```
-
-The views in the stack navigator 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 customized.
-
-React Navigation also has packages for different kind of navigators such as tabs and drawer. You can use them to implement various patterns in your app.
-
-For a complete intro to React Navigation, follow the [React Navigation Getting Started Guide](https://reactnavigation.org/docs/getting-started.html).
diff --git a/website/versioned_docs/version-0.60/netinfo.md b/website/versioned_docs/version-0.60/netinfo.md
deleted file mode 100644
index 2cc848fedf6..00000000000
--- a/website/versioned_docs/version-0.60/netinfo.md
+++ /dev/null
@@ -1,176 +0,0 @@
----
-id: netinfo
-title: '🚧 NetInfo'
----
-
-> **Removed.** Use [react-native-community/react-native-netinfo](https://github.com/react-native-community/react-native-netinfo) instead.
-
-NetInfo exposes info about online/offline status
-
-```jsx
-NetInfo.getConnectionInfo().then(connectionInfo => {
- console.log(
- 'Initial, type: ' +
- connectionInfo.type +
- ', effectiveType: ' +
- connectionInfo.effectiveType,
- );
-});
-function handleFirstConnectivityChange(connectionInfo) {
- console.log(
- 'First change, type: ' +
- connectionInfo.type +
- ', effectiveType: ' +
- connectionInfo.effectiveType,
- );
- NetInfo.removeEventListener(
- 'connectionChange',
- handleFirstConnectivityChange,
- );
-}
-NetInfo.addEventListener(
- 'connectionChange',
- handleFirstConnectivityChange,
-);
-```
-
-### ConnectionType enum
-
-`ConnectionType` describes the type of connection the device is using to communicate with the network.
-
-Cross platform values for `ConnectionType`:
-
-- `none` - device is offline
-- `wifi` - device is online and connected via wifi, or is the iOS simulator
-- `cellular` - device is connected via Edge, 3G, WiMax, or LTE
-- `unknown` - error case and the network status is unknown
-
-Android-only values for `ConnectionType`:
-
-- `bluetooth` - device is connected via Bluetooth
-- `ethernet` - device is connected via Ethernet
-- `wimax` - device is connected via WiMAX
-
-### EffectiveConnectionType enum
-
-Cross platform values for `EffectiveConnectionType`:
-
-- `2g`
-- `3g`
-- `4g`
-- `unknown`
-
-### Android
-
-To request network info, you need to add the following line to your app's `AndroidManifest.xml`:
-
-`
-
- )
- }
-
- return(
-
- {item.title}, {item.releaseYear} }
- keyExtractor={({id}, index) => id}
- />
-
- );
- }
-}
-```
-
-> 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 only for those domains; if the domains are not known until runtime you can [disable ATS completely](publishing-to-app-store.md#1-enable-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/optimizing-flatlist-configuration.md b/website/versioned_docs/version-0.60/optimizing-flatlist-configuration.md
deleted file mode 100644
index 808e7379590..00000000000
--- a/website/versioned_docs/version-0.60/optimizing-flatlist-configuration.md
+++ /dev/null
@@ -1,151 +0,0 @@
----
-id: optimizing-flatlist-configuration
-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.)
-
-- **Memory consumption:** How much information about your list is being stored in memory, which could lead to an app crash.
-
-- **Responsiveness:** Application ability to respond to interactions. Low responsiveness, for instance, is when you touch on a component and it waits a bit to respond, instead of responding immediately as expected.
-
-- **Blank areas:** When `VirtualizedList` can't render your items fast enough, you may enter a part of your list with non-rendered components that appear as blank space.
-
-- **Viewport:** The visible area of content that is rendered to pixels.
-
-- **Window:** The area in which items should be mounted, which is generally much larger than the viewport.
-
-## Props
-
-Here are a list of props that can help to improve `FlatList` performance:
-
-### removeClippedSubviews
-
-| Type | Default |
-| ------- | ------- |
-| Boolean | False |
-
-If `true`, views that are outside of the viewport are detached from the native view hierarchy.
-
-**Pros:** This reduces time spent on the main thread, and thus reduces the risk of dropped frames, by excluding views outside of the viewport from the native rendering and drawing traversals.
-
-**Cons:** Be aware that this implementation can have bugs, such as missing content (mainly observed on iOS), especially if you are doing complex things with transforms and/or absolute positioning. Also note this does not save significant memory because the views are not deallocated, only detached.
-
-### maxToRenderPerBatch
-
-| Type | Default |
-| ------ | ------- |
-| Number | 10 |
-
-It is a `VirtualizedList` prop that can be passed through `FlatList`. This controls the amount of items rendered per batch, which is the next chunk of items rendered on every scroll.
-
-**Pros:** Setting a bigger number means less visual blank areas when scrolling (increases the fill rate).
-
-**Cons:** More items per batch means longer periods of JavaScript execution potentially blocking other event processing, like presses, hurting responsiveness.
-
-### updateCellsBatchingPeriod
-
-| Type | Default |
-| ------ | ------- |
-| Number | 50 |
-
-While `maxToRenderPerBatch` tells the amount of items rendered per batch, setting `updateCellsBatchingPeriod` tells your `VirtualizedList` the delay in milliseconds between batch renders (how frequently your component will be rendering the windowed items).
-
-**Pros:** Combining this prop with `maxToRenderPerBatch` gives you the power to, for example, render more items in a less frequent batch, or less items in a more frequent batch.
-
-**Cons:** Less frequent batches may cause blank areas, More frequent batches may cause responsiveness issues.
-
-### initialNumToRender
-
-| Type | Default |
-| ------ | ------- |
-| Number | 10 |
-
-The initial amount of items to render.
-
-**Pros:** Define precise number of items that would cover the screen for every device. This can be a big performance boost for the initial render.
-
-**Cons:** Setting a low `initialNumToRender` may cause blank areas, especially if it's too small to cover the viewport on initial render.
-
-### windowSize
-
-| Type | Default |
-| ------ | ------- |
-| Number | 21 |
-
-The number passed here is a measurement unit where 1 is equivalent to your viewport height. The default value is 21 (10 viewports above, 10 below, and one in between).
-
-**Pros:** Bigger `windowSize` will result in less chance of seeing blank space while scrolling. On the other hand, smaller `windowSize` will result in fewer items mounted simultaneously, saving memory.
-
-**Cons:** For a bigger `windowSize`, you will have more memory consumption. For a lower `windowSize`, you will have a bigger chance of seeing blank areas.
-
-### legacyImplementation
-
-| Type | Default |
-| ------- | ------- |
-| Boolean | False |
-
-Make `FlatList` rely on the older and deprecated `ListView` instead of `VirtualizedList`.
-
-**Pros:** No risk of seeing blank areas while scrolling. May avoid bugs in `VirtualizedList`.
-
-**Cons:** Extra memory consumption and more app crash risk in large lists (100+) with complex items. It also warns that the above tweaks will not work because now it is using `ListView`. Many other features are not supported. There may be other bugs since `ListView` is deprecated.
-
-## List items
-
-Below are some tips about list item components. They are the core of your list, so they need to be fast.
-
-### Use basic components
-
-The more complex your components are, the slower they will render. Try to avoid a lot of logic and nesting in your list items. If you are reusing this list item component a lot in your app, create a component only for your big lists and make them with as little logic and nesting as possible.
-
-### Use light components
-
-The heavier your components are, the slower they render. Avoid heavy images (use a cropped version or thumbnail for list items, as small as possible). Talk to your design team, use as little effects and interactions and information as possible in your list. Show them in your item's detail.
-
-### Use shouldComponentUpdate
-
-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 basic enough, you could even use
-
-```jsx
-shouldComponentUpdate() {
- return false
-}
-```
-
-### Use cached optimized images
-
-You can use the community packages (such as [react-native-fast-image](https://github.com/DylanVann/react-native-fast-image) from [@DylanVann](https://github.com/DylanVann)) for more performant images. Every image in your list is a `new Image()` instance. The faster it reaches the `loaded` hook, the faster your JavaScript thread will be free again.
-
-### Use getItemLayout
-
-If all your list item components have the same height (or width, for a horizontal list), providing the [getItemLayout](/docs/flatlist#getitemlayout) prop removes the need for your `FlatList` to manage async layout calculations. This is a very desirable optimization technique.
-
-If your components have dynamic size and you really need performance, consider asking your design team if they may think of a redesign in order to perform better.
-
-### Use keyExtractor or key
-
-You can set the [`keyExtractor`](/docs/flatlist#keyextractor) to your `FlatList` component. This prop is used for caching and as the React `key` to track item re-ordering.
-
-You can also use a `key` prop in your item component.
-
-### Avoid anonymous function on renderItem
-
-Move out the `renderItem` function to the outside of render function, so it won't recreate itself each time render function called.
-
-```jsx
-renderItem = ({ item }) => ({item.title} /platform-tools/systrace/systrace.py --time=10 -o trace.html sched gfx view -a
-```
-
-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 ` 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:
-
-
-
-> **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:
-
-
-
-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:
->
-> 
->
-> 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`:
-
- 
-
-- **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:
-
- 
-
-- **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`:
-
- 
-
-- **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`:
-
- 
-
-#### Identifying a culprit
-
-A smooth animation should look something like the following:
-
-
-
-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:
-
-
-
-Notice that the JS thread is executing almost 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:
-
-
-
-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:
-
-
-
-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:
-
-
-
-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:
-
-
-
-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 a quick 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 Very Expensive Component ;
- }
-}
-```
-
-#### 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 (
-
-
- Load
-
- {this.state.needsExpensive ?
- );
- }
-}
-```
-
-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/permissionsandroid.md b/website/versioned_docs/version-0.60/permissionsandroid.md
deleted file mode 100644
index 79c5cb88260..00000000000
--- a/website/versioned_docs/version-0.60/permissionsandroid.md
+++ /dev/null
@@ -1,157 +0,0 @@
----
-id: permissionsandroid
-title: PermissionsAndroid
----
-
-
-
Project with Native Code Required
-
- The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
-
-
- this.setState({language: itemValue})
- }>
-
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `onValueChange`
-
-Callback for when an item is selected. This is called with the following parameters:
-
-- `itemValue`: the `value` prop of the item that was selected
-- `itemPosition`: the index of the selected item in this picker
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `selectedValue`
-
-Value matching value of one of the items. Can be a string or an integer.
-
-| Type | Required |
-| ---- | -------- |
-| any | No |
-
----
-
-### `style`
-
-| Type | Required |
-| --------------- | -------- |
-| pickerStyleType | No |
-
----
-
-### `testID`
-
-Used to locate this view in end-to-end tests.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `enabled`
-
-If set to false, the picker will be disabled, i.e. the user will not be able to make a selection.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `mode`
-
-On Android, specifies how to display the selection items when the user taps on the picker:
-
-- 'dialog': Show a modal dialog. This is the default.
-- 'dropdown': Shows a dropdown anchored to the picker view
-
-| Type | Required | Platform |
-| -------------------------- | -------- | -------- |
-| enum('dialog', 'dropdown') | No | Android |
-
----
-
-### `prompt`
-
-Prompt string for this picker, used on Android in dialog mode as the title of the dialog.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| string | No | Android |
-
----
-
-### `itemStyle`
-
-Style to apply to each of the item labels.
-
-| Type | Required | Platform |
-| ---------------------------------- | -------- | -------- |
-| [text styles](text-style-props.md) | No | iOS |
diff --git a/website/versioned_docs/version-0.60/pickerios.md b/website/versioned_docs/version-0.60/pickerios.md
deleted file mode 100644
index 2d150597036..00000000000
--- a/website/versioned_docs/version-0.60/pickerios.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-id: pickerios
-title: PickerIOS
----
-
-> **Deprecated.** Use [Picker](picker.md) instead.
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `itemStyle`
-
-| Type | Required |
-| ---------------------------------- | -------- |
-| [text styles](text-style-props.md) | No |
-
----
-
-### `onValueChange`
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onChange`
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `selectedValue`
-
-| Type | Required |
-| ---------------- | -------- |
-| number or string | No |
diff --git a/website/versioned_docs/version-0.60/pixelratio.md b/website/versioned_docs/version-0.60/pixelratio.md
deleted file mode 100644
index c5579e19f6f..00000000000
--- a/website/versioned_docs/version-0.60/pixelratio.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-id: pixelratio
-title: PixelRatio
----
-
-PixelRatio class gives access to the device pixel density.
-
-## Fetching a correctly sized image
-
-You should get a higher resolution image if you are on a high pixel density device. A good rule of thumb is to multiply the size of the image you display by the pixel ratio.
-
-```jsx
-var image = getImage({
- width: PixelRatio.getPixelSizeForLayoutSize(200),
- height: PixelRatio.getPixelSizeForLayoutSize(100),
-});
-/platform-tools/systrace/systrace.py --time=10 -o trace.html sched gfx view -a
-```
-
-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 ` 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:
-
-
-
-> **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:
-
-
-
-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:
->
-> 
->
-> 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`:
-
- 
-
-- **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:
-
- 
-
-- **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`:
-
- 
-
-- **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`:
-
- 
-
-## Identifying a culprit
-
-A smooth animation should look something like the following:
-
-
-
-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:
-
-
-
-Notice that the JS thread is executing almost 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:
-
-
-
-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:
-
-
-
-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:
-
-
-
-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:
-
-
-
-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 a quick 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.
diff --git a/website/versioned_docs/version-0.60/progressbarandroid.md b/website/versioned_docs/version-0.60/progressbarandroid.md
deleted file mode 100644
index 4cc9238c699..00000000000
--- a/website/versioned_docs/version-0.60/progressbarandroid.md
+++ /dev/null
@@ -1,115 +0,0 @@
----
-id: progressbarandroid
-title: ProgressBarAndroid
----
-
-Android-only React component used to indicate that the app is loading or there is some activity in the app.
-
-Example:
-
-```jsx
-import React, {Component} from 'react';
-import {ProgressBarAndroid, StyleSheet, View} from 'react-native';
-
-export default class App extends Component {
- render() {
- return (
-
-
- );
- }
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- justifyContent: 'space-evenly',
- padding: 10,
- },
-});
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `animating`
-
-Whether to show the ProgressBar (true, the default) or hide it (false).
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `color`
-
-Color of the progress bar.
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `indeterminate`
-
-If the progress bar will show indeterminate progress. Note that this can only be false if styleAttr is Horizontal, and requires a `progress` value.
-
-| Type | Required |
-| ----------------- | -------- |
-| indeterminateType | No |
-
----
-
-### `progress`
-
-The progress value (between 0 and 1).
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `styleAttr`
-
-Style of the ProgressBar. One of:
-
-- Horizontal
-- Normal (default)
-- Small
-- Large
-- Inverse
-- SmallInverse
-- LargeInverse
-
-| Type | Required |
-| ----------------------------------------------------------------------------------------- | -------- |
-| enum('Horizontal', 'Normal', 'Small', 'Large', 'Inverse', 'SmallInverse', 'LargeInverse') | No |
-
----
-
-### `testID`
-
-Used to locate this view in end-to-end tests.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
diff --git a/website/versioned_docs/version-0.60/progressviewios.md b/website/versioned_docs/version-0.60/progressviewios.md
deleted file mode 100644
index b5c6a6c4cc4..00000000000
--- a/website/versioned_docs/version-0.60/progressviewios.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: progressviewios
-title: ProgressViewIOS
----
-
-Uses `ProgressViewIOS` to render a UIProgressView on iOS.
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `progress`
-
-The progress value (between 0 and 1).
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `progressImage`
-
-A stretchable image to display as the progress bar.
-
-| Type | Required |
-| ---------------------- | -------- |
-| Image.propTypes.source | No |
-
----
-
-### `progressTintColor`
-
-The tint color of the progress bar itself.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `progressViewStyle`
-
-The progress bar style.
-
-| Type | Required |
-| ---------------------- | -------- |
-| enum('default', 'bar') | No |
-
----
-
-### `trackImage`
-
-A stretchable image to display behind the progress bar.
-
-| Type | Required |
-| ---------------------- | -------- |
-| Image.propTypes.source | No |
-
----
-
-### `trackTintColor`
-
-The tint color of the progress bar track.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
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 1baa8ed470b..00000000000
--- a/website/versioned_docs/version-0.60/props.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-id: props
-title: 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 (
-
- Hello {this.props.name}!
-
- );
- }
-}
-
-export default class LotsOfGreetings extends Component {
- render() {
- return (
-
-
- );
- }
-}
-```
-
-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, similar to the [Core Components](intro-react-native-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 can 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/publishing-to-app-store.md b/website/versioned_docs/version-0.60/publishing-to-app-store.md
deleted file mode 100644
index fe8ea58c9ee..00000000000
--- a/website/versioned_docs/version-0.60/publishing-to-app-store.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-id: publishing-to-app-store
-title: Publishing to Apple App Store
----
-
-The publishing process is the same as any other native iOS app, with some additional considerations to take into account.
-
-> If you are using Expo then read the Expo Guide for [Building Standalone Apps](https://docs.expo.io/versions/latest/distribution/building-standalone-apps/).
-
-### 1. Enable App Transport Security
-
-App Transport Security is a security feature introduced in iOS 9 that rejects all HTTP requests that are not sent over HTTPS. This can result in HTTP traffic being blocked, including the developer React Native server. ATS is disabled for `localhost` by default in React Native projects in order to make development easier.
-
-You should re-enable ATS prior to building your app for production by removing the `localhost` entry from the `NSExceptionDomains` dictionary and setting `NSAllowsArbitraryLoads` to `false` in your `Info.plist` file in the `ios/` folder. You can also re-enable ATS from within Xcode by opening your target properties under the Info pane and editing the App Transport Security Settings entry.
-
-> If your application needs to access HTTP resources on production, learn how to configure ATS on your project.
-
-### 2. Configure release scheme
-
-Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Developer menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer.
-
-To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`.
-
-
-
-#### Pro Tips
-
-As your App Bundle grows in size, you may start to see a blank screen flash between your splash screen and the display of your root application view. If this is the case, you can add the following code to `AppDelegate.m` in order to keep your splash screen displayed during the transition.
-
-```objectivec
- // Place this code after "[self.window makeKeyAndVisible]" and before "return YES;"
- UIStoryboard *sb = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
- UIViewController *vc = [sb instantiateInitialViewController];
- rootView.loadingView = vc.view;
-```
-
-The static bundle is built every time you target a physical device, even in Debug. If you want to save time, turn off bundle generation in Debug by adding the following to your shell script in the Xcode Build Phase `Bundle React Native code and images`:
-
-```shell
- if [ "${CONFIGURATION}" == "Debug" ]; then
- export SKIP_BUNDLING=true
- fi
-```
-
-### 3. Build app for release
-
-You can now build your app for release by tapping `⌘B` or selecting **Product** → **Build** from the menu bar. Once built for release, you'll be able to distribute the app to beta testers and submit the app to the App Store.
-
-> You can also use the `React Native CLI` to perform this operation using the option `--configuration` with the value `Release` (e.g. `npx react-native run-ios --configuration Release`).
diff --git a/website/versioned_docs/version-0.60/publishing.md b/website/versioned_docs/version-0.60/publishing.md
deleted file mode 100644
index b2dd995bd6d..00000000000
--- a/website/versioned_docs/version-0.60/publishing.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-id: publishing-forks
-title: Publish your own version of react native
----
-
-## TL;DR
-
-There is a docker image that helps you build the required Android sources without installing any additional tooling (other than [Docker](https://docs.docker.com/install/), which can be committed to a git branch as a fully functional React Native fork release.
-
-Run this from a fork of the React Native [repo](https://github.com/facebook/react-native).
-
-```
-git checkout -d release/my-react-native-release
-docker run --rm --name rn-build -v $PWD:/pwd -w /pwd reactnativecommunity/react-native-android /bin/sh -c "./gradlew installArchives"
-git add android --force
-git commit -a -m 'my react native forked release'
-git push
-```
-
-Install it in your app project package.json.
-
-```
-"dependencies": {
- ...
- "react-native": "myName/react-native#release/my-react-native-release"
-}
-```
-
-## Rationale
-
-The recommended approach to working with React Native is to always update to the latest version. No support is provided on older versions and if you run into issues the contributors will always ask you to upgrade to the latest version before even looking at your particular issue. Sometimes, though, you are temporarily stuck on an older React Native version, but you require some changes from newer versions urgently (bugfixes) without having to do a full upgrade right now. This situation should be short lived by definition and once you have the time, the real solution is to upgrade to the latest version.
-
-With this goal of a shortlived fork of React Native in mind, you can publish your own version of React Native. The facebook/react-native repository contains all the dependencies required to be used directly as a git dependency, except for the Android React Native library binary (.aar).
-
-## Building
-
-This binary needs to become available in your project's `node_modules/react-native/android` folder or directly in your gradle dependency of your Android app. You can achieve this in one of two ways: Git dependency branch, Android binary dependency through Maven.
-
-To build the .aar React Native library, you can follow the steps to [build from source](https://github.com/facebook/react-native/wiki/Building-from-source#android) first to install all required tooling. Then to build the actual library, you can run the following in the root of your react-native checkout:
-
-```$bash
-./gradlew :ReactAndroid:installArchives --no-daemon
-```
-
-If you don't want to install the required toolchain for building from source, you can use a prebuilt docker image to create a react native binary;
-
-```
-docker run --rm --name rn-build -v $PWD:/pwd -w /pwd reactnativecommunity/react-native-android /bin/sh -c "./gradlew installArchives"
-```
-
-If you haven't used the Android NDK before or if you have a NDK version not exactly matching the required version for building React Native, this is the recommended approach.
-
-The resulting binary can be made available to app projects in one of the two ways described below.
-
-### Publishing to Maven/Nexus
-
-Upload the binaries from the `android` folder to maven and point your Android app project gradle dependency for React Native to your Maven/Nexus dependency.
-
-### Publishing to a git fork dependency
-
-Instead of uploading to Maven/Nexus, you can add the binaries built in the previous steps to git, by changing the .gitignore and committing the binaries to your forked branch. This allows you to make your fork into a functioning git dependency for React Native app projects.
-
-If you have changes that you want to actually merge to React Native, make them on another branch first and open a PR. To start making your dependency branch, make sure you are on a 'release/my-forked-release' branch, then merge any commits that you need from yourself or others into this branch. This release branch should never be merged into any other branch.
-
-```$bash
-# create .aar, then:
-git add android --force
-git commit -m 'my release commit'
-git push
-```
-
-Now you can use this branch as a git dependency in your app project, by pointing your package.json dependency to this branch:
-
-```
-"dependencies": {
- ...
- "react-native": "my-name/react-native#release/my-forked-release,
- ...
-}
-```
-
-No other modifications to your dependencies should be necessary for your native changes to be included in your project.
diff --git a/website/versioned_docs/version-0.60/pushnotificationios.md b/website/versioned_docs/version-0.60/pushnotificationios.md
deleted file mode 100644
index 1da042f4944..00000000000
--- a/website/versioned_docs/version-0.60/pushnotificationios.md
+++ /dev/null
@@ -1,513 +0,0 @@
----
-id: pushnotificationios
-title: PushNotificationIOS
----
-
-> **Deprecated.** Use [@react-native-community/push-notification-ios](https://github.com/react-native-community/react-native-push-notification-ios) instead.
-
-
-
Projects with Native Code Only
-
- This section only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Expo documentation..
-
-
`
-
-And then in your AppDelegate implementation add the following:
-
-```objectivec
- // Required to register for notifications
- - (void)application:(UIApplication *)application didRegisterUserNotificationSettings:(UIUserNotificationSettings *)notificationSettings
- {
- [RCTPushNotificationManager didRegisterUserNotificationSettings:notificationSettings];
- }
- // Required for the register event.
- - (void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken
- {
- [RCTPushNotificationManager didRegisterForRemoteNotificationsWithDeviceToken:deviceToken];
- }
- // Required for the notification event. You must call the completion handler after handling the remote notification.
- - (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo
- fetchCompletionHandler:(void (^)(UIBackgroundFetchResult))completionHandler
- {
- [RCTPushNotificationManager didReceiveRemoteNotification:userInfo fetchCompletionHandler:completionHandler];
- }
- // Required for the registrationError event.
- - (void)application:(UIApplication *)application didFailToRegisterForRemoteNotificationsWithError:(NSError *)error
- {
- [RCTPushNotificationManager didFailToRegisterForRemoteNotificationsWithError:error];
- }
- // Required for the localNotification event.
- - (void)application:(UIApplication *)application didReceiveLocalNotification:(UILocalNotification *)notification
- {
- [RCTPushNotificationManager didReceiveLocalNotification:notification];
- }
-```
-
-To show notifications while being in the foreground (available starting from iOS 10) add the following lines:
-
-At the top of your `AppDelegate.m`:
-
-`#import `
-
-And then in your AppDelegate implementation add the following:
-
-```objectivec
-- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
-{
- ...
- // Define UNUserNotificationCenter
- UNUserNotificationCenter *center = [UNUserNotificationCenter currentNotificationCenter];
- center.delegate = self;
-
- return YES;
-}
-
-//Called when a notification is delivered to a foreground app.
--(void)userNotificationCenter:(UNUserNotificationCenter *)center willPresentNotification:(UNNotification *)notification withCompletionHandler:(void (^)(UNNotificationPresentationOptions options))completionHandler
-{
- completionHandler(UNAuthorizationOptionSound | UNAuthorizationOptionAlert | UNAuthorizationOptionBadge);
-}
-```
-
-Then enable Background Modes/Remote notifications to be able to use remote notifications properly. The easiest way to do this is via the project settings. Navigate to Targets -> Your App -> Capabilities -> Background Modes and check Remote notifications. This will automatically enable the required settings.
-
----
-
-# Reference
-
-## Methods
-
-### `presentLocalNotification()`
-
-```jsx
-PushNotificationIOS.presentLocalNotification(details);
-```
-
-Schedules the localNotification for immediate presentation.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------- | ------ | -------- | ----------- |
-| details | object | Yes | See below. |
-
-details is an object containing:
-
-- `alertBody` : The message displayed in the notification alert.
-- `alertTitle` : The text displayed as the title of the notification alert.
-- `alertAction` : The "action" displayed beneath an actionable notification. Defaults to "view";
-- `soundName` : The sound played when the notification is fired (optional).
-- `isSilent` : If true, the notification will appear without sound (optional).
-- `category` : The category of this notification, required for actionable notifications (optional).
-- `userInfo` : An optional object containing additional notification data.
-- `applicationIconBadgeNumber` (optional) : The number to display as the app's icon badge. The default value of this property is 0, which means that no badge is displayed.
-
----
-
-### `scheduleLocalNotification()`
-
-```jsx
-PushNotificationIOS.scheduleLocalNotification(details);
-```
-
-Schedules the localNotification for future presentation.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------- | ------ | -------- | ----------- |
-| details | object | Yes | See below. |
-
-details is an object containing:
-
-- `fireDate` : The date and time when the system should deliver the notification.
-- `alertTitle` : The text displayed as the title of the notification alert.
-- `alertBody` : The message displayed in the notification alert.
-- `alertAction` : The "action" displayed beneath an actionable notification. Defaults to "view";
-- `soundName` : The sound played when the notification is fired (optional).
-- `isSilent` : If true, the notification will appear without sound (optional).
-- `category` : The category of this notification, required for actionable notifications (optional).
-- `userInfo` : An optional object containing additional notification data.
-- `applicationIconBadgeNumber` (optional) : The number to display as the app's icon badge. Setting the number to 0 removes the icon badge.
-- `repeatInterval` : The interval to repeat as a string. Possible values: `minute`, `hour`, `day`, `week`, `month`, `year`.
-
----
-
-### `cancelAllLocalNotifications()`
-
-```jsx
-PushNotificationIOS.cancelAllLocalNotifications();
-```
-
-Cancels all scheduled localNotifications
-
----
-
-### `removeAllDeliveredNotifications()`
-
-```jsx
-PushNotificationIOS.removeAllDeliveredNotifications();
-```
-
-Remove all delivered notifications from Notification Center
-
----
-
-### `getDeliveredNotifications()`
-
-```jsx
-PushNotificationIOS.getDeliveredNotifications(callback);
-```
-
-Provides you with a list of the app’s notifications that are still displayed in Notification Center
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | ----------------------------------------------------------- |
-| callback | function | Yes | Function which receive an array of delivered notifications. |
-
-A delivered notification is an object containing:
-
-- `identifier` : The identifier of this notification.
-- `title` : The title of this notification.
-- `body` : The body of this notification.
-- `category` : The category of this notification, if has one.
-- `userInfo` : An optional object containing additional notification data.
-- `thread-id` : The thread identifier of this notification, if has one.
-
----
-
-### `removeDeliveredNotifications()`
-
-```jsx
-PushNotificationIOS.removeDeliveredNotifications(identifiers);
-```
-
-Removes the specified notifications from Notification Center
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----------- | ----- | -------- | ---------------------------------- |
-| identifiers | array | Yes | Array of notification identifiers. |
-
----
-
-### `setApplicationIconBadgeNumber()`
-
-```jsx
-PushNotificationIOS.setApplicationIconBadgeNumber(number);
-```
-
-Sets the badge number for the app icon on the home screen
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ------------------------------ |
-| number | number | Yes | Badge number for the app icon. |
-
----
-
-### `getApplicationIconBadgeNumber()`
-
-```jsx
-PushNotificationIOS.getApplicationIconBadgeNumber(callback);
-```
-
-Gets the current badge number for the app icon on the home screen
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | -------------------------------------------------------- |
-| callback | function | Yes | A function that will be passed the current badge number. |
-
----
-
-### `cancelLocalNotifications()`
-
-```jsx
-PushNotificationIOS.cancelLocalNotifications(userInfo);
-```
-
-Cancel local notifications.
-
-Optionally restricts the set of canceled notifications to those notifications whose `userInfo` fields match the corresponding fields in the `userInfo` argument.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ------ | -------- | ----------- |
-| userInfo | object | No | |
-
----
-
-### `getScheduledLocalNotifications()`
-
-```jsx
-PushNotificationIOS.getScheduledLocalNotifications(callback);
-```
-
-Gets the local notifications that are currently scheduled.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | ---------------------------------------------------------------------------------- |
-| callback | function | Yes | A function that will be passed an array of objects describing local notifications. |
-
----
-
-### `addEventListener()`
-
-```jsx
-PushNotificationIOS.addEventListener(type, handler);
-```
-
-Attaches a listener to remote or local notification events while the app is running in the foreground or the background.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------- | -------- | -------- | ----------- |
-| type | string | Yes | Event type. |
-| handler | function | Yes | Listener. |
-
-Valid events are:
-
-- `notification` : Fired when a remote notification is received. The handler will be invoked with an instance of `PushNotificationIOS`.
-- `localNotification` : Fired when a local notification is received. The handler will be invoked with an instance of `PushNotificationIOS`.
-- `register`: Fired when the user registers for remote notifications. The handler will be invoked with a hex string representing the deviceToken.
-- `registrationError`: Fired when the user fails to register for remote notifications. Typically occurs when APNS is having issues, or the device is a simulator. The handler will be invoked with {message: string, code: number, details: any}.
-
----
-
-### `removeEventListener()`
-
-```jsx
-PushNotificationIOS.removeEventListener(type, handler);
-```
-
-Removes the event listener. Do this in `componentWillUnmount` to prevent memory leaks
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------- | -------- | -------- | ----------- |
-| type | string | Yes | Event type. |
-| handler | function | Yes | Listener. |
-
----
-
-### `requestPermissions()`
-
-```jsx
-PushNotificationIOS.requestPermissions([permissions]);
-```
-
-Requests notification permissions from iOS, prompting the user's dialog box. By default, it will request all notification permissions, but a subset of these can be requested by passing a map of requested permissions. The following permissions are supported:
-
-- `alert`
-- `badge`
-- `sound`
-
-If a map is provided to the method, only the permissions with truthy values will be requested.
-
-This method returns a promise that will resolve when the user accepts, rejects, or if the permissions were previously rejected. The promise resolves to the current state of the permission.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----------- | ----- | -------- | ---------------------- |
-| permissions | array | No | alert, badge, or sound |
-
----
-
-### `abandonPermissions()`
-
-```jsx
-PushNotificationIOS.abandonPermissions();
-```
-
-Unregister for all remote notifications received via Apple Push Notification service.
-
-You should call this method in rare circumstances only, such as when a new version of the app removes support for all types of remote notifications. Users can temporarily prevent apps from receiving remote notifications through the Notifications section of the Settings app. Apps unregistered through this method can always re-register.
-
----
-
-### `checkPermissions()`
-
-```jsx
-PushNotificationIOS.checkPermissions(callback);
-```
-
-See what push permissions are currently enabled.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | ----------- |
-| callback | function | Yes | See below. |
-
-`callback` will be invoked with a `permissions` object:
-
-- `alert` :boolean
-- `badge` :boolean
-- `sound` :boolean
-
----
-
-### `getInitialNotification()`
-
-```jsx
-PushNotificationIOS.getInitialNotification();
-```
-
-This method returns a promise. If the app was launched by a push notification, this promise resolves to an object of type `PushNotificationIOS`. Otherwise, it resolves to `null`.
-
----
-
-### `constructor()`
-
-```jsx
-constructor(nativeNotif);
-```
-
-You will never need to instantiate `PushNotificationIOS` yourself. Listening to the `notification` event and invoking `getInitialNotification` is sufficient.
-
----
-
-### `finish()`
-
-```jsx
-finish(fetchResult);
-```
-
-This method is available for remote notifications that have been received via: `application:didReceiveRemoteNotification:fetchCompletionHandler:` https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIApplicationDelegate_Protocol/#//apple_ref/occ/intfm/UIApplicationDelegate/application:didReceiveRemoteNotification:fetchCompletionHandler:
-
-Call this to execute when the remote notification handling is complete. When calling this block, pass in the fetch result value that best describes the results of your operation. You _must_ call this handler and should do so as soon as possible. For a list of possible values, see `PushNotificationIOS.FetchResult`.
-
-If you do not call this method your background remote notifications could be throttled, to read more about it see the above documentation link.
-
----
-
-### `getMessage()`
-
-```jsx
-getMessage();
-```
-
-An alias for `getAlert` to get the notification's main message string
-
----
-
-### `getSound()`
-
-```jsx
-getSound();
-```
-
-Gets the sound string from the `aps` object
-
----
-
-### `getCategory()`
-
-```jsx
-getCategory();
-```
-
-Gets the category string from the `aps` object
-
----
-
-### `getAlert()`
-
-```jsx
-getAlert();
-```
-
-Gets the notification's main message from the `aps` object
-
----
-
-### `getContentAvailable()`
-
-```jsx
-getContentAvailable();
-```
-
-Gets the content-available number from the `aps` object
-
----
-
-### `getBadgeCount()`
-
-```jsx
-getBadgeCount();
-```
-
-Gets the badge count number from the `aps` object
-
----
-
-### `getData()`
-
-```jsx
-getData();
-```
-
-Gets the data object on the notification
-
----
-
-### `getThreadID()`
-
-```jsx
-getThreadID();
-```
-
-Gets the thread ID on the notification
diff --git a/website/versioned_docs/version-0.60/ram-bundles-inline-requires.md b/website/versioned_docs/version-0.60/ram-bundles-inline-requires.md
deleted file mode 100644
index 7f3a4dfe3b5..00000000000
--- a/website/versioned_docs/version-0.60/ram-bundles-inline-requires.md
+++ /dev/null
@@ -1,186 +0,0 @@
----
-id: ram-bundles-inline-requires
-title: RAM Bundles and 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
-
-```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 Very Expensive Component ;
- }
-}
-```
-
-### Optimized.js
-
-```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 (
-
-
- Load
-
- {this.state.needsExpensive ?
- );
- }
-}
-```
-
-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:
-
-```js
-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(),
- null,
- 2,
- )};`,
-);
-```
-
-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.
-
-```js
-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:
-
-```js
-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/react-node.md b/website/versioned_docs/version-0.60/react-node.md
deleted file mode 100644
index d703d1c1429..00000000000
--- a/website/versioned_docs/version-0.60/react-node.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-id: react-node
-title: React Node Object Type
----
-
-A React Node is one of the following types:
-
-- Boolean (which is ignored)
-- `null` or `undefined` (which is ignored)
-- Number
-- String
-- A React element (result of JSX)
-- An array of any of the above, possibly a nested one
diff --git a/website/versioned_docs/version-0.60/refreshcontrol.md b/website/versioned_docs/version-0.60/refreshcontrol.md
deleted file mode 100644
index 244b99e2450..00000000000
--- a/website/versioned_docs/version-0.60/refreshcontrol.md
+++ /dev/null
@@ -1,170 +0,0 @@
----
-id: refreshcontrol
-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.
-
-### Example
-
-```SnackPlayer name=RefreshControl&supportedPlatforms=ios,android
-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 (
-
- Pull down to see RefreshControl indicator
-
-
- );
-}
-
-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.
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `refreshing`
-
-Whether the view should be indicating an active refresh.
-
-| Type | Required |
-| ---- | -------- |
-| bool | Yes |
-
----
-
-### `onRefresh`
-
-Called when the view starts refreshing.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `colors`
-
-The colors (at least one) that will be used to draw the refresh indicator.
-
-| Type | Required | Platform |
-| --------------------------- | -------- | -------- |
-| array of [color](colors.md) | No | Android |
-
----
-
-### `enabled`
-
-Whether the pull to refresh functionality is enabled.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `progressBackgroundColor`
-
-The background color of the refresh indicator.
-
-| Type | Required | Platform |
-| ------------------ | -------- | -------- |
-| [color](colors.md) | No | Android |
-
----
-
-### `progressViewOffset`
-
-Progress view top offset
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `size`
-
-Size of the refresh indicator, see RefreshControl.SIZE.
-
-| Type | Required | Platform |
-| ---------------------------------------------------------------------- | -------- | -------- |
-| enum(RefreshLayoutConsts.SIZE.DEFAULT, RefreshLayoutConsts.SIZE.LARGE) | No | Android |
-
----
-
-### `tintColor`
-
-The color of the refresh indicator.
-
-| Type | Required | Platform |
-| ------------------ | -------- | -------- |
-| [color](colors.md) | No | iOS |
-
----
-
-### `title`
-
-The title displayed under the refresh indicator.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| string | No | iOS |
-
----
-
-### `titleColor`
-
-Title color.
-
-| Type | Required | Platform |
-| ------------------ | -------- | -------- |
-| [color](colors.md) | No | iOS |
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 bec6a1fd106..00000000000
--- a/website/versioned_docs/version-0.60/removing-default-permissions.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-id: removing-default-permissions
-title: 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
-
-
-
-
-
-
-
-
-
-
- ```
-
-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-device.md b/website/versioned_docs/version-0.60/running-on-device.md
deleted file mode 100644
index ddc31d44e5e..00000000000
--- a/website/versioned_docs/version-0.60/running-on-device.md
+++ /dev/null
@@ -1,411 +0,0 @@
----
-id: running-on-device
-title: Running On Device
-hide_table_of_contents: true
----
-
-import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
-
-It's always a good idea to test your app on an actual device before releasing it to your users. This document will guide you through the necessary steps to run your React Native app on a device and to get it ready for production.
-
-If you used Expo CLI or Create React Native App to set up your project, you can preview your app on a device by scanning the QR code with the Expo app—but in order to build and run your app on a device, you will need to eject and install the native code dependencies from the [environment setup guide](/docs/environment-setup).
-
-
-
-
-## Running your app on Android devices
-
-#### Development OS
-
-
-
-
-[//]: # 'macOS, Android'
-
-### 1. Enable Debugging over USB
-
-Most Android devices can only install and run apps downloaded from Google Play, by default. You will need to enable USB Debugging on your device in order to install your app during development.
-
-To enable USB debugging on your device, you will first need to enable the "Developer options" menu by going to **Settings** → **About phone** → **Software information** and then tapping the `Build number` row at the bottom seven times. You can then go back to **Settings** → **Developer options** to enable "USB debugging".
-
-### 2. Plug in your device via USB
-
-Let's now set up an Android device to run our React Native projects. Go ahead and plug in your device via USB to your development machine.
-
-Now check that your device is properly connecting to ADB, the Android Debug Bridge, by running `adb devices`.
-
-```shell
-$ adb devices
-List of devices attached
-emulator-5554 offline # Google emulator
-14ed2fcc device # Physical device
-```
-
-Seeing `device` in the right column means the device is connected. You must have **only one device connected** at a time.
-
-### 3. Run your app
-
-Type the following in your command prompt to install and launch your app on the device:
-
-```shell
-$ npx react-native run-android
-```
-
-> If you get a "bridge configuration isn't available" error, see [Using adb reverse](running-on-device.md#method-1-using-adb-reverse-recommended).
-
-> Hint: You can also use the `React Native CLI` to generate and run a `Release` build (e.g. `npx react-native run-android --variant=release`).
-
-Connecting to the development server
-
-You can also iterate quickly on a device by connecting to the development server running on your development machine. There are several ways of accomplishing this, depending on whether you have access to a USB cable or a Wi-Fi network.
-
-### Method 1: Using adb reverse (recommended)
-
-You can use this method if your device is running Android 5.0 (Lollipop) or newer, it has USB debugging enabled, and it is connected via USB to your development machine.
-
-Run the following in a command prompt:
-
-```shell
-$ adb -s reverse tcp:8081 tcp:8081
-```
-
-To find the device name, run the following adb command:
-
-```shell
-$ adb devices
-```
-
-You can now enable Live reloading from the [Developer menu](debugging.md#accessing-the-in-app-developer-menu). Your app will reload whenever your JavaScript code has changed.
-
-### Method 2: Connect via Wi-Fi
-
-You can also connect to the development server over Wi-Fi. You'll first need to install the app on your device using a USB cable, but once that has been done you can debug wirelessly by following these instructions. You'll need your development machine's current IP address before proceeding.
-
-You can find the IP address in **System Preferences** → **Network**.
-
-1. Make sure your laptop and your phone are on the **same** Wi-Fi network.
-2. Open your React Native app on your device.
-3. You'll see a [red screen with an error](debugging.md#in-app-errors-and-warnings). This is OK. The following steps will fix that.
-4. Open the in-app [Developer menu](debugging.md#accessing-the-in-app-developer-menu).
-5. Go to **Dev Settings** → **Debug server host & port for device**.
-6. Type in your machine's IP address and the port of the local dev server (e.g. 10.0.1.1:8081).
-7. Go back to the **Developer menu** and select **Reload JS**.
-
-You can now enable Live reloading from the [Developer menu](debugging.md#accessing-the-in-app-developer-menu). Your app will reload whenever your JavaScript code has changed.
-
-## Building your app for production
-
-You have built a great app using React Native, and you are now itching to release it in the Play Store. The process is the same as any other native Android app, with some additional considerations to take into account. Follow the guide for [generating a signed APK](signed-apk-android.md) to learn more.
-
-
-
-
-[//]: # 'Windows, Android'
-
-### 1. Enable Debugging over USB
-
-Most Android devices can only install and run apps downloaded from Google Play, by default. You will need to enable USB Debugging on your device in order to install your app during development.
-
-To enable USB debugging on your device, you will first need to enable the "Developer options" menu by going to **Settings** → **About phone** → **Software information** and then tapping the `Build number` row at the bottom seven times. You can then go back to **Settings** → **Developer options** to enable "USB debugging".
-
-### 2. Plug in your device via USB
-
-Let's now set up an Android device to run our React Native projects. Go ahead and plug in your device via USB to your development machine.
-
-Now check that your device is properly connecting to ADB, the Android Debug Bridge, by running `adb devices`.
-
-```shell
-$ adb devices
-List of devices attached
-emulator-5554 offline # Google emulator
-14ed2fcc device # Physical device
-```
-
-Seeing `device` in the right column means the device is connected. You must have **only one device connected** at a time.
-
-### 3. Run your app
-
-Type the following in your command prompt to install and launch your app on the device:
-
-```shell
-$ npx react-native run-android
-```
-
-> If you get a "bridge configuration isn't available" error, see [Using adb reverse](running-on-device.md#method-1-using-adb-reverse-recommended).
-
-> Hint: You can also use the `React Native CLI` to generate and run a `Release` build (e.g. `npx react-native run-android --variant=release`).
-
-Connecting to the development server
-
-You can also iterate quickly on a device by connecting to the development server running on your development machine. There are several ways of accomplishing this, depending on whether you have access to a USB cable or a Wi-Fi network.
-
-### Method 1: Using adb reverse (recommended)
-
-You can use this method if your device is running Android 5.0 (Lollipop) or newer, it has USB debugging enabled, and it is connected via USB to your development machine.
-
-Run the following in a command prompt:
-
-```shell
-$ adb -s reverse tcp:8081 tcp:8081
-```
-
-To find the device name, run the following adb command:
-
-```shell
-$ adb devices
-```
-
-You can now enable Live reloading from the [Developer menu](debugging.md#accessing-the-in-app-developer-menu). Your app will reload whenever your JavaScript code has changed.
-
-### Method 2: Connect via Wi-Fi
-
-You can also connect to the development server over Wi-Fi. You'll first need to install the app on your device using a USB cable, but once that has been done you can debug wirelessly by following these instructions. You'll need your development machine's current IP address before proceeding.
-
-Open the command prompt and type `ipconfig` to find your machine's IP address ([more info](http://windows.microsoft.com/en-us/windows/using-command-line-tools-networking-information)).
-
-1. Make sure your laptop and your phone are on the **same** Wi-Fi network.
-2. Open your React Native app on your device.
-3. You'll see a [red screen with an error](debugging.md#in-app-errors-and-warnings). This is OK. The following steps will fix that.
-4. Open the in-app [Developer menu](debugging.md#accessing-the-in-app-developer-menu).
-5. Go to **Dev Settings** → **Debug server host & port for device**.
-6. Type in your machine's IP address and the port of the local dev server (e.g. 10.0.1.1:8081).
-7. Go back to the **Developer menu** and select **Reload JS**.
-
-You can now enable Live reloading from the [Developer menu](debugging.md#accessing-the-in-app-developer-menu). Your app will reload whenever your JavaScript code has changed.
-
-## Building your app for production
-
-You have built a great app using React Native, and you are now itching to release it in the Play Store. The process is the same as any other native Android app, with some additional considerations to take into account. Follow the guide for [generating a signed APK](signed-apk-android.md) to learn more.
-
-
-
-
-[//]: # 'Linux, Android'
-
-### 1. Enable Debugging over USB
-
-Most Android devices can only install and run apps downloaded from Google Play, by default. You will need to enable USB Debugging on your device in order to install your app during development.
-
-To enable USB debugging on your device, you will first need to enable the "Developer options" menu by going to **Settings** → **About phone** → **Software information** and then tapping the `Build number` row at the bottom seven times. You can then go back to **Settings** → **Developer options** to enable "USB debugging".
-
-### 2. Plug in your device via USB
-
-Let's now set up an Android device to run our React Native projects. Go ahead and plug in your device via USB to your development machine.
-
-Next, check the manufacturer code by using `lsusb` (on mac, you must first [install lsusb](https://github.com/jlhonora/lsusb)). `lsusb` should output something like this:
-
-```bash
-$ lsusb
-Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
-Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-Bus 001 Device 003: ID 22b8:2e76 Motorola PCS
-Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
-Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-```
-
-These lines represent the USB devices currently connected to your machine.
-
-You want the line that represents your phone. If you're in doubt, try unplugging your phone and running the command again:
-
-```bash
-$ lsusb
-Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
-Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
-Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-```
-
-You'll see that after removing the phone, the line which has the phone model ("Motorola PCS" in this case) disappeared from the list. This is the line that we care about.
-
-`Bus 001 Device 003: ID 22b8:2e76 Motorola PCS`
-
-From the above line, you want to grab the first four digits from the device ID:
-
-`22b8:2e76`
-
-In this case, it's `22b8`. That's the identifier for Motorola.
-
-You'll need to input this into your udev rules in order to get up and running:
-
-```shell
-echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666", GROUP="plugdev"' | sudo tee /etc/udev/rules.d/51-android-usb.rules
-```
-
-Make sure that you replace `22b8` with the identifier you get in the above command.
-
-Now check that your device is properly connecting to ADB, the Android Debug Bridge, by running `adb devices`.
-
-```shell
-$ adb devices
-List of devices attached
-emulator-5554 offline # Google emulator
-14ed2fcc device # Physical device
-```
-
-Seeing `device` in the right column means the device is connected. You must have **only one device connected** at a time.
-
-### 3. Run your app
-
-Type the following in your command prompt to install and launch your app on the device:
-
-```shell
-$ npx react-native run-android
-```
-
-> If you get a "bridge configuration isn't available" error, see [Using adb reverse](running-on-device.md#method-1-using-adb-reverse-recommended).
-
-> Hint: You can also use the `React Native CLI` to generate and run a `Release` build (e.g. `npx react-native run-android --variant=release`).
-
-Connecting to the development server
-
-You can also iterate quickly on a device by connecting to the development server running on your development machine. There are several ways of accomplishing this, depending on whether you have access to a USB cable or a Wi-Fi network.
-
-### Method 1: Using adb reverse (recommended)
-
-You can use this method if your device is running Android 5.0 (Lollipop) or newer, it has USB debugging enabled, and it is connected via USB to your development machine.
-
-Run the following in a command prompt:
-
-```shell
-$ adb -s reverse tcp:8081 tcp:8081
-```
-
-To find the device name, run the following adb command:
-
-```shell
-$ adb devices
-```
-
-You can now enable Live reloading from the [Developer menu](debugging.md#accessing-the-in-app-developer-menu). Your app will reload whenever your JavaScript code has changed.
-
-### Method 2: Connect via Wi-Fi
-
-You can also connect to the development server over Wi-Fi. You'll first need to install the app on your device using a USB cable, but once that has been done you can debug wirelessly by following these instructions. You'll need your development machine's current IP address before proceeding.
-
-Open a terminal and type `/sbin/ifconfig` to find your machine's IP address.
-
-1. Make sure your laptop and your phone are on the **same** Wi-Fi network.
-2. Open your React Native app on your device.
-3. You'll see a [red screen with an error](debugging.md#in-app-errors-and-warnings). This is OK. The following steps will fix that.
-4. Open the in-app [Developer menu](debugging.md#accessing-the-in-app-developer-menu).
-5. Go to **Dev Settings** → **Debug server host & port for device**.
-6. Type in your machine's IP address and the port of the local dev server (e.g. 10.0.1.1:8081).
-7. Go back to the **Developer menu** and select **Reload JS**.
-
-You can now enable Live reloading from the [Developer menu](debugging.md#accessing-the-in-app-developer-menu). Your app will reload whenever your JavaScript code has changed.
-
-## Building your app for production
-
-You have built a great app using React Native, and you are now itching to release it in the Play Store. The process is the same as any other native Android app, with some additional considerations to take into account. Follow the guide for [generating a signed APK](signed-apk-android.md) to learn more.
-
-
-
-
-
-
-
-## Running your app on iOS devices
-
-#### Development OS
-
-
-
-
-[//]: # 'macOS, iOS'
-
-### 1. Plug in your device via USB
-
-Connect your iOS device to your Mac using a USB to Lightning cable. Navigate to the `ios` folder in your project, then open the `.xcodeproj` file, or if you are using CocoaPods open `.xcworkspace`, within it using Xcode.
-
-If this is your first time running an app on your iOS device, you may need to register your device for development. Open the **Product** menu from Xcode's menubar, then go to **Destination**. Look for and select your device from the list. Xcode will then register your device for development.
-
-### 2. Configure code signing
-
-Register for an [Apple developer account](https://developer.apple.com/) if you don't have one yet.
-
-Select your project in the Xcode Project Navigator, then select your main target (it should share the same name as your project). Look for the "General" tab. Go to "Signing" and make sure your Apple developer account or team is selected under the Team dropdown. Do the same for the tests target (it ends with Tests, and is below your main target).
-
-**Repeat** this step for the **Tests** target in your project.
-
-
-
-### 3. Build and Run your app
-
-If everything is set up correctly, your device will be listed as the build target in the Xcode toolbar, and it will also appear in the Devices pane (`⇧⌘2`). You can now press the **Build and run** button (`⌘R`) or select **Run** from the **Product** menu. Your app will launch on your device shortly.
-
-
-
-> If you run into any issues, please take a look at Apple's [Launching Your App on a Device](https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/LaunchingYourApponDevices/LaunchingYourApponDevices.html#//apple_ref/doc/uid/TP40012582-CH27-SW4) docs.
-
-Connecting to the development server
-
-You can also iterate quickly on a device using the development server. You only have to be on the same Wi-Fi network as your computer. Shake your device to open the [Developer menu](debugging.md#accessing-the-in-app-developer-menu), then enable Live Reload. Your app will reload whenever your JavaScript code has changed.
-
-
-
-### Troubleshooting
-
-> If you have any issues, ensure that your Mac and device are on the same network and can reach each other. Many open wireless networks with captive portals are configured to prevent devices from reaching other devices on the network. You may use your device's Personal Hotspot feature in this case.
-
-When trying to connect to the development server you might get a [red screen with an error](debugging.md#in-app-errors-and-warnings) saying:
-
-> Connection to `http://localhost:8081/debugger-proxy?role=client` timed out. Are you running node proxy? If you are running on the device, check if you have the right IP address in `RCTWebSocketExecutor.m`.
-
-To solve this issue check the following points.
-
-#### 1. Wi-Fi network.
-
-Make sure your laptop and your phone are on the **same** Wi-Fi network.
-
-#### 2. IP address
-
-Make sure that the build script detected the IP address of your machine correctly (e.g. 10.0.1.123).
-
-
-
-Open the **Report navigator** tab, select the last **Build** and search for `xip.io`. The IP address which gets embedded in the app should match your machines IP address plus the domain `.xip.io` (e.g. 10.0.1.123.xip.io)
-
-#### 3. Network/router configuration
-
-React Native uses the wildcard DNS service **xip.io** to address your device, as Apple ATS prohibits URLs with IP addresses instead of domain names, and developers' networks are often not set up to resolve local hostnames. Some routers have security features to prevent DNS Servers from resolving to anything in the local IP range.
-
-Now check if you are able to resolve the xip.io address, by running `nslookup`.
-
-```bash
-$ nslookup 10.0.1.123.xip.io
-```
-
-If it doesn't resolve your local IP address either the **xip.io** service is down or more likely your router prevents it.
-
-To still use xip.io behind your router:
-
-- configure your phone to use Google DNS (8.8.8.8)
-- disable the appropriate security feature in your router
-
-## Building your app for production
-
-You have built a great app using React Native, and you are now itching to release it in the App Store. The process is the same as any other native iOS app, with some additional considerations to take into account. Follow the guide for [publishing to the Apple App Store](publishing-to-app-store.md) to learn more.
-
-
-
-
-[//]: # 'Windows, iOS'
-
-> A Mac is required in order to build your app for iOS devices. Alternatively, you can refer to our [environment setup guide](/docs/environment-setup) to learn how to build your app using Expo CLI, which will allow you to run your app using the Expo client app.
-
-
-
-
-[//]: # 'Linux, iOS'
-
-> A Mac is required in order to build your app for iOS devices. Alternatively, you can refer to our [environment setup guide](/docs/environment-setup) to learn how to build your app using Expo CLI, which will allow you to run your app using the Expo client app.
-
-
-
-
-
-
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 59df9668515..00000000000
--- a/website/versioned_docs/version-0.60/running-on-simulator-ios.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-id: running-on-simulator-ios
-title: Running On Simulator
----
-
-## 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, 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/safeareaview.md b/website/versioned_docs/version-0.60/safeareaview.md
deleted file mode 100644
index 727278dceb7..00000000000
--- a/website/versioned_docs/version-0.60/safeareaview.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-id: safeareaview
-title: SafeAreaView
----
-
-The purpose of `SafeAreaView` is to render content within the safe area boundaries of a device. It is currently only applicable to iOS devices with iOS version 11 or later.
-
-`SafeAreaView` renders nested content and automatically applies padding to reflect the portion of the view that is not covered by navigation bars, tab bars, toolbars, and other ancestor views. Moreover, and most importantly, Safe Area's paddings reflect the physical limitation of the screen, such as rounded corners or camera notches (i.e. the sensor housing area on iPhone X).
-
-### Usage Example
-
-To use, 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.
-
-```SnackPlayer name=SafeAreaView
-import React from 'react';
-import { StyleSheet, Text, SafeAreaView } from 'react-native';
-
-export default function App() {
- return (
-
- Page content
-
- );
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- },
-});
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `emulateUnlessSupported`
-
-| Type | Required | Default |
-| ---- | -------- | ------- |
-| bool | No | true |
diff --git a/website/versioned_docs/version-0.60/scrollview.md b/website/versioned_docs/version-0.60/scrollview.md
deleted file mode 100644
index 1db3e362251..00000000000
--- a/website/versioned_docs/version-0.60/scrollview.md
+++ /dev/null
@@ -1,717 +0,0 @@
----
-id: scrollview
-title: ScrollView
----
-
-Component that wraps platform ScrollView while providing integration with touch locking "responder" system.
-
-Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer `{flex: 1}` down the view stack can lead to errors here, which the element inspector makes quick to debug.
-
-Doesn't yet support other contained responders from blocking this scroll view from becoming the responder.
-
-`` vs [``](flatlist.md) - which one to use?
-
-`ScrollView` renders all its react child components at once, but this has a performance downside.
-
-Imagine you have a very long list of items you want to display, maybe several screens worth of content. Creating JS components and native views for everything all at once, much of which may not even be shown, will contribute to slow rendering and increased memory usage.
-
-This is where `FlatList` comes into play. `FlatList` renders items lazily, when they are about to appear, and removes items that scroll way off screen to save memory and processing time.
-
-`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 (
-
-
-
- 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.
-
-
-
- );
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- marginTop: Constants.statusBarHeight,
- },
- scrollView: {
- backgroundColor: 'pink',
- marginHorizontal: 20,
- },
- text: {
- fontSize: 42,
- },
-});
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `alwaysBounceHorizontal`
-
-When true, the scroll view bounces horizontally when it reaches the end even if the content is smaller than the scroll view itself. The default value is true when `horizontal={true}` and false otherwise.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `alwaysBounceVertical`
-
-When true, the scroll view bounces vertically when it reaches the end even if the content is smaller than the scroll view itself. The default value is false when `horizontal={true}` and true otherwise.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `automaticallyAdjustContentInsets`
-
-Controls whether iOS should automatically adjust the content inset for scroll views that are placed behind a navigation bar or tab bar/ toolbar. The default value is true.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `bounces`
-
-When true, the scroll view bounces when it reaches the end of the content if the content is larger then the scroll view along the axis of the scroll direction. When false, it disables all bouncing even if the `alwaysBounce*` props are true. The default value is true.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `bouncesZoom`
-
-When true, gestures can drive zoom past min/max and the zoom will animate to the min/max value at gesture end, otherwise the zoom will not exceed the limits.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `canCancelContentTouches`
-
-When false, once tracking starts, won't try to drag if the touch moves. The default value is true.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `centerContent`
-
-When true, the scroll view automatically centers the content when the content is smaller than the scroll view bounds; when the content is larger than the scroll view, this property has no effect. The default value is false.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `contentContainerStyle`
-
-These styles will be applied to the scroll view content container which wraps all of the child views. Example:
-
-```
-return (
-
-
-);
-...
-const styles = StyleSheet.create({
- contentContainer: {
- paddingVertical: 20
- }
-});
-```
-
-| Type | Required |
-| ------------------------------------ | -------- |
-| StyleSheetPropType(View Style props) | No |
-
----
-
-### `contentInset`
-
-The amount by which the scroll view content is inset from the edges of the scroll view. Defaults to `{top: 0, left: 0, bottom: 0, right: 0}`.
-
-| Type | Required | Platform |
-| ------------------------------------------------------------------ | -------- | -------- |
-| object: {top: number, left: number, bottom: number, right: number} | No | iOS |
-
----
-
-### `contentInsetAdjustmentBehavior`
-
-This property specifies how the safe area insets are used to modify the content area of the scroll view. The default value of this property is "never". Available on iOS 11 and later.
-
-| Type | Required | Platform |
-| ------------------------------------------------------ | -------- | -------- |
-| enum('automatic', 'scrollableAxes', 'never', 'always') | No | iOS |
-
----
-
-### `contentOffset`
-
-Used to manually set the starting scroll offset. The default value is `{x: 0, y: 0}`.
-
-| Type | Required | Platform |
-| ------------- | -------- | -------- |
-| PointPropType | No | iOS |
-
----
-
-### `decelerationRate`
-
-A floating-point number that determines how quickly the scroll view decelerates after the user lifts their finger. You may also use string shortcuts `"normal"` and `"fast"` which match the underlying iOS settings for `UIScrollViewDecelerationRateNormal` and `UIScrollViewDecelerationRateFast` respectively.
-
-- `'normal'` (the default), 0.998 on iOS, 0.985 on Android.
-- `'fast'`, 0.99 on iOS, 0.9 on Android.
-
-| Type | Required |
-| ------------------------------- | -------- |
-| enum('fast', 'normal'), ,number | No |
-
----
-
-### `directionalLockEnabled`
-
-When true, the ScrollView will try to lock to only vertical or horizontal scrolling while dragging. The default value is false.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `disableIntervalMomentum`
-
-When true, the scroll view stops on the next index (in relation to scroll position at release) regardless of how fast the gesture is. This can be used for horizontal pagination when the page is less than the width of the ScrollView. The default value is false.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `disableScrollViewPanResponder`
-
-When true, the default JS pan responder on the ScrollView is disabled, and full control over touches inside the ScrollView is left to its child components. This is particularly useful if `snapToInterval` is enabled, since it does not follow typical touch patterns. Do not use this on regular ScrollView use cases without `snapToInterval` as it may cause unexpected touches to occur while scrolling. The default value is false.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `endFillColor`
-
-Sometimes a scrollview takes up more space than its content fills. When this is the case, this prop will fill the rest of the scrollview with a color to avoid setting a background and creating unnecessary overdraw. This is an advanced optimization that is not needed in the general case.
-
-| Type | Required | Platform |
-| ------------------ | -------- | -------- |
-| [color](colors.md) | No | Android |
-
----
-
-### `horizontal`
-
-When true, the scroll view's children are arranged horizontally in a row instead of vertically in a column. The default value is false.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `indicatorStyle`
-
-The style of the scroll indicators.
-
-- `'default'` (the default), same as `black`.
-- `'black'`, scroll indicator is `black`. This style is good against a light background.
-- `'white'`, scroll indicator is `white`. This style is good against a dark background.
-
-| Type | Required | Platform |
-| --------------------------------- | -------- | -------- |
-| enum('default', 'black', 'white') | No | iOS |
-
----
-
-### `invertStickyHeaders`
-
-If sticky headers should stick at the bottom instead of the top of the ScrollView. This is usually used with inverted ScrollViews.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `keyboardDismissMode`
-
-Determines whether the keyboard gets dismissed in response to a drag.
-
-_Cross platform_
-
-- `'none'` (the default), drags do not dismiss the keyboard.
-- `'on-drag'`, the keyboard is dismissed when a drag begins.
-
-_iOS Only_
-
-- `'interactive'`, the keyboard is dismissed interactively with the drag and moves in synchrony with the touch; dragging upwards cancels the dismissal. On android this is not supported and it will have the same behavior as 'none'.
-
-| Type | Required |
-| -------------------------------------- | -------- |
-| enum('none', 'on-drag', 'interactive') | No |
-
----
-
-### `keyboardShouldPersistTaps`
-
-Determines when the keyboard should stay visible after a tap.
-
-- `'never'` (the default), tapping outside of the focused text input when the keyboard is up dismisses the keyboard. When this happens, children won't receive the tap.
-- `'always'`, the keyboard will not dismiss automatically, and the scroll view will not catch taps, but children of the scroll view can catch taps.
-- `'handled'`, the keyboard will not dismiss automatically when the tap was handled by children of the scroll view (or captured by an ancestor).
-- `false`, **_deprecated_**, use 'never' instead
-- `true`, **_deprecated_**, use 'always' instead
-
-| Type | Required |
-| ----------------------------------------------- | -------- |
-| enum('always', 'never', 'handled', false, true) | No |
-
----
-
-### `maintainVisibleContentPosition`
-
-When set, the scroll view will adjust the scroll position so that the first child that is currently visible and at or beyond `minIndexForVisible` will not change position. This is useful for lists that are loading content in both directions, e.g. a chat thread, where new messages coming in might otherwise cause the scroll position to jump. A value of 0 is common, but other values such as 1 can be used to skip loading spinners or other content that should not maintain position.
-
-The optional `autoscrollToTopThreshold` can be used to make the content automatically scroll to the top after making the adjustment if the user was within the threshold of the top before the adjustment was made. This is also useful for chat-like applications where you want to see new messages scroll into place, but not if the user has scrolled up a ways and it would be disruptive to scroll a bunch.
-
-Caveat 1: Reordering elements in the scrollview with this enabled will probably cause jumpiness and jank. It can be fixed, but there are currently no plans to do so. For now, don't re-order the content of any ScrollViews or Lists that use this feature.
-
-Caveat 2: This uses `contentOffset` and `frame.origin` in native code to compute visibility. Occlusion, transforms, and other complexity won't be taken into account as to whether content is "visible" or not.
-
-| Type | Required | Platform |
-| ------------------------------------------------------------------------ | -------- | -------- |
-| object: { minIndexForVisible: number, autoscrollToTopThreshold: number } | No | iOS |
-
----
-
-### `maximumZoomScale`
-
-The maximum allowed zoom scale. The default value is 1.0.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | iOS |
-
----
-
-### `minimumZoomScale`
-
-The minimum allowed zoom scale. The default value is 1.0.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | iOS |
-
----
-
-### `nestedScrollEnabled`
-
-Enables nested scrolling for Android API level 21+. Nested scrolling is supported by default on iOS.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
-### `onContentSizeChange`
-
-Called when scrollable content view of the ScrollView changes.
-
-Handler function is passed the content width and content height as parameters: `(contentWidth, contentHeight)`
-
-It's implemented using onLayout handler attached to the content container which this ScrollView renders.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onMomentumScrollBegin`
-
-Called when the momentum scroll starts (scroll which occurs as the ScrollView starts gliding).
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onMomentumScrollEnd`
-
-Called when the momentum scroll ends (scroll which occurs as the ScrollView glides to a stop).
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onScroll`
-
-Fires at most once per frame during scrolling. The frequency of the events can be controlled using the `scrollEventThrottle` prop. The event has the shape `{ nativeEvent: { contentInset: { bottom, left, right, top }, contentOffset: { x, y }, contentSize: { height, width }, layoutMeasurement: { height, width }, zoomScale } }`. All values are numbers.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onScrollBeginDrag`
-
-Called when the user begins to drag the scroll view.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onScrollEndDrag`
-
-Called when the user stops dragging the scroll view and it either stops or begins to glide.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onScrollToTop`
-
-Fires when the scroll view scrolls to top after the status bar has been tapped.
-
-| Type | Required | Platform |
-| -------- | -------- | -------- |
-| function | No | iOS |
-
----
-
-### `overScrollMode`
-
-Used to override default value of overScroll mode.
-
-Possible values:
-
-- `'auto'` - Default value, allow a user to over-scroll this view only if the content is large enough to meaningfully scroll.
-- `'always'` - Always allow a user to over-scroll this view.
-- `'never'` - Never allow a user to over-scroll this view.
-
-| Type | Required | Platform |
-| ------------------------------- | -------- | -------- |
-| enum('auto', 'always', 'never') | No | Android |
-
----
-
-### `pagingEnabled`
-
-When true, the scroll view stops on multiples of the scroll view's size when scrolling. This can be used for horizontal pagination. The default value is false.
-
-Note: Vertical pagination is not supported on Android.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `persistentScrollbar`
-
-Causes the scrollbars not to turn transparent when they are not in use. The default value is false.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `pinchGestureEnabled`
-
-When true, ScrollView allows use of pinch gestures to zoom in and out. The default value is true.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `refreshControl`
-
-A RefreshControl component, used to provide pull-to-refresh functionality for the ScrollView. Only works for vertical ScrollViews (`horizontal` prop must be `false`).
-
-See [RefreshControl](refreshcontrol.md).
-
-| Type | Required |
-| ------- | -------- |
-| element | No |
-
----
-
-### `removeClippedSubviews`
-
-Experimental: When true, offscreen child views (whose `overflow` value is `hidden`) are removed from their native backing superview when offscreen. This can improve scrolling performance on long lists. The default value is true.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `scrollEnabled`
-
-When false, the view cannot be scrolled via touch interaction. The default value is true.
-
-Note that the view can always be scrolled by calling `scrollTo`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `scrollEventThrottle`
-
-This controls how often the scroll event will be fired while scrolling (as a time interval in ms). A lower number yields better accuracy for code that is tracking the scroll position, but can lead to scroll performance problems due to the volume of information being send over the bridge. You will not notice a difference between values set between 1-16 as the JS run loop is synced to the screen refresh rate. If you do not need precise scroll position tracking, set this value higher to limit the information being sent across the bridge. The default value is zero, which results in the scroll event being sent only once each time the view is scrolled.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | iOS |
-
----
-
-### `scrollIndicatorInsets`
-
-The amount by which the scroll view indicators are inset from the edges of the scroll view. This should normally be set to the same value as the `contentInset`. Defaults to `{0, 0, 0, 0}`.
-
-| Type | Required | Platform |
-| ------------------------------------------------------------------ | -------- | -------- |
-| object: {top: number, left: number, bottom: number, right: number} | No | iOS |
-
----
-
-### `scrollPerfTag`
-
-Tag used to log scroll performance on this scroll view. Will force momentum events to be turned on (see sendMomentumEvents). This doesn't do anything out of the box and you need to implement a custom native FpsListener for it to be useful.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| string | No | Android |
-
----
-
-### `scrollToOverflowEnabled`
-
-When true, the scroll view can be programmatically scrolled beyond its content size. The default value is false.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `scrollsToTop`
-
-When true, the scroll view scrolls to top when the status bar is tapped. The default value is true.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `DEPRECATED_sendUpdatedChildFrames`
-
-When true, ScrollView will emit updateChildFrames data in scroll events, otherwise will not compute or emit child frame data. This only exists to support legacy issues, `onLayout` should be used instead to retrieve frame data. The default value is false.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `showsHorizontalScrollIndicator`
-
-When true, shows a horizontal scroll indicator. The default value is true.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `showsVerticalScrollIndicator`
-
-When true, shows a vertical scroll indicator. The default value is true.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `snapToAlignment`
-
-When `snapToInterval` is set, `snapToAlignment` will define the relationship of the snapping to the scroll view.
-
-- `'start'` (the default) will align the snap at the left (horizontal) or top (vertical).
-- `'center'` will align the snap in the center.
-- `'end'` will align the snap at the right (horizontal) or bottom (vertical).
-
-| Type | Required | Platform |
-| ------------------------------ | -------- | -------- |
-| enum('start', 'center', 'end') | No | iOS |
-
----
-
-### `snapToEnd`
-
-Use in conjunction with `snapToOffsets`. By default, the end of the list counts as a snap offset. Set `snapToEnd` to false to disable this behavior and allow the list to scroll freely between its end and the last `snapToOffsets` offset. The default value is true.
-
-| Type | Required |
-| ------- | -------- |
-| boolean | No |
-
----
-
-### `snapToInterval`
-
-When set, causes the scroll view to stop at multiples of the value of `snapToInterval`. This can be used for paginating through children that have lengths smaller than the scroll view. Typically used in combination with `snapToAlignment` and `decelerationRate="fast"`. Overrides less configurable `pagingEnabled` prop.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `snapToOffsets`
-
-When set, causes the scroll view to stop at the defined offsets. This can be used for paginating through variously sized children that have lengths smaller than the scroll view. Typically used in combination with `decelerationRate="fast"`. Overrides less configurable `pagingEnabled` and `snapToInterval` props.
-
-| Type | Required |
-| --------------- | -------- |
-| array of number | No |
-
----
-
-### `snapToStart`
-
-Use in conjunction with `snapToOffsets`. By default, the beginning of the list counts as a snap offset. Set `snapToStart` to false to disable this behavior and allow the list to scroll freely between its start and the first `snapToOffsets` offset. The default value is true.
-
-| Type | Required |
-| ------- | -------- |
-| boolean | No |
-
----
-
-### `stickyHeaderIndices`
-
-An array of child indices determining which children get docked to the top of the screen when scrolling. For example, passing `stickyHeaderIndices={[0]}` will cause the first child to be fixed to the top of the scroll view. This property is not supported in conjunction with `horizontal={true}`.
-
-| Type | Required |
-| --------------- | -------- |
-| array of number | No |
-
----
-
-### `zoomScale`
-
-The current scale of the scroll view content. The default value is 1.0.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | iOS |
-
-## Methods
-
-### `flashScrollIndicators()`
-
-```jsx
-flashScrollIndicators();
-```
-
-Displays the scroll indicators momentarily.
-
----
-
-### `scrollTo()`
-
-```jsx
-scrollTo(
- options?: {x?: number, y?: number, animated?: boolean} | number,
- deprecatedX?: number,
- deprecatedAnimated?: boolean,
-);
-```
-
-Scrolls to a given x, y offset, either immediately, with a smooth animation.
-
-Example:
-
-`scrollTo({x: 0, y: 0, animated: true})`
-
-Note: The weird function signature is due to the fact that, for historical reasons, the function also accepts separate arguments as an alternative to the options object. This is deprecated due to ambiguity (y before x), and SHOULD NOT BE USED.
-
----
-
-### `scrollToEnd()`
-
-```jsx
-scrollToEnd(([options]: {animated: boolean}));
-```
-
-If this is a vertical ScrollView scrolls to the bottom. If this is a horizontal ScrollView scrolls to the right.
-
-Use `scrollToEnd({animated: true})` for smooth animated scrolling, `scrollToEnd({animated: false})` for immediate scrolling. If no options are passed, `animated` defaults to true.
-
----
-
-### `scrollWithoutAnimationTo()`
-
-```jsx
-scrollWithoutAnimationTo(y, x);
-```
-
-Deprecated, use `scrollTo` instead.
diff --git a/website/versioned_docs/version-0.60/sectionlist.md b/website/versioned_docs/version-0.60/sectionlist.md
deleted file mode 100644
index 7bb353c0626..00000000000
--- a/website/versioned_docs/version-0.60/sectionlist.md
+++ /dev/null
@@ -1,455 +0,0 @@
----
-id: sectionlist
-title: SectionList
----
-
-A performant interface for rendering sectioned lists, supporting the most handy features:
-
-- Fully cross-platform.
-- Configurable viewability callbacks.
-- List header support.
-- List footer support.
-- Item separator support.
-- Section header support.
-- Section separator support.
-- Heterogeneous data and item rendering support.
-- Pull to Refresh.
-- Scroll loading.
-
-If you don't need section support and want a simpler interface, use [``](flatlist.md).
-
-### 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 (
-
- {title}
-
- );
-}
-
-export default function App() {
- return (
-
- item + index}
- renderItem={({ item }) => {title}
- )}
- />
-
- );
-}
-
-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.md), and thus inherits its props (as well as those of [``](scrollview.md) that aren't explicitly listed here, along with the following caveats:
-
-- Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.
-- This is a `PureComponent` which means that it will not re-render if `props` remain shallow-equal. Make sure that everything your `renderItem` function depends on is passed as a prop (e.g. `extraData`) that is not `===` after updates, otherwise your UI may not update on changes. This includes the `data` prop and parent component state.
-- In order to constrain memory and enable smooth scrolling, content is rendered asynchronously offscreen. This means it's possible to scroll faster than the fill rate and momentarily see blank content. This is a tradeoff that can be adjusted to suit the needs of each application, and we are working on improving it behind the scenes.
-- By default, the list looks for a `key` prop on each item and uses that for the React key. Alternatively, you can provide a custom `keyExtractor` prop.
-
-### Props
-
-- [`ScrollView` props...](scrollview.md#props)
-
-Required props:
-
-- [`renderItem`](sectionlist.md#renderitem)
-- [`sections`](sectionlist.md#sections)
-
-Optional props:
-
-- [`extraData`](sectionlist.md#extradata)
-- [`initialNumToRender`](sectionlist.md#initialnumtorender)
-- [`inverted`](sectionlist.md#inverted)
-- [`ItemSeparatorComponent`](sectionlist.md#itemseparatorcomponent)
-- [`keyExtractor`](sectionlist.md#keyextractor)
-- [`legacyImplementation`](sectionlist.md#legacyimplementation)
-- [`ListEmptyComponent`](sectionlist.md#listemptycomponent)
-- [`ListFooterComponent`](sectionlist.md#listfootercomponent)
-- [`ListHeaderComponent`](sectionlist.md#listheadercomponent)
-- [`onEndReached`](sectionlist.md#onendreached)
-- [`onEndReachedThreshold`](sectionlist.md#onendreachedthreshold)
-- [`onRefresh`](sectionlist.md#onrefresh)
-- [`onViewableItemsChanged`](sectionlist.md#onviewableitemschanged)
-- [`refreshing`](sectionlist.md#refreshing)
-- [`removeClippedSubviews`](sectionlist.md#removeclippedsubviews)
-- [`renderSectionFooter`](sectionlist.md#rendersectionfooter)
-- [`renderSectionHeader`](sectionlist.md#rendersectionheader)
-- [`SectionSeparatorComponent`](sectionlist.md#sectionseparatorcomponent)
-- [`stickySectionHeadersEnabled`](sectionlist.md#stickysectionheadersenabled)
-
-### Methods
-
-- [`flashScrollIndicators`](sectionlist.md#flashscrollindicators)
-- [`recordInteraction`](sectionlist.md#recordinteraction)
-- [`scrollToLocation`](sectionlist.md#scrolltolocation)
-
-### Type Definitions
-
-- [`Section`](sectionlist.md#section)
-
----
-
-# Reference
-
-## Props
-
-### `renderItem`
-
-Default renderer for every item in every section. Can be over-ridden on a per-section basis. Should return a React element.
-
-| Type | Required |
-| -------- | -------- |
-| function | Yes |
-
-The render function will be passed an object with the following keys:
-
-- 'item' (object) - the item object as specified in this section's `data` key
-- 'index' (number) - Item's index within the section.
-- 'section' (object) - The full section object as specified in `sections`.
-- 'separators' (object) - An object with the following keys:
- - 'highlight' (function) - `() => void`
- - 'unhighlight' (function) - `() => void`
- - 'updateProps' (function) - `(select, newProps) => void`
- - 'select' (enum) - possible values are 'leading', 'trailing'
- - 'newProps' (object)
-
----
-
-### `sections`
-
-The actual data to render, akin to the `data` prop in [`FlatList`](flatlist.md).
-
-| Type | Required |
-| ------------------------------------------- | -------- |
-| array of [Section](sectionlist.md#section)s | Yes |
-
----
-
-### `extraData`
-
-A marker property for telling the list to re-render (since it implements `PureComponent`). If any of your `renderItem`, Header, Footer, etc. functions depend on anything outside of the `data` prop, stick it here and treat it immutably.
-
-| Type | Required |
-| ---- | -------- |
-| any | No |
-
----
-
-### `initialNumToRender`
-
-How many items to render in the initial batch. This should be enough to fill the screen but not much more. Note these items will never be unmounted as part of the windowed rendering in order to improve perceived performance of scroll-to-top actions.
-
-| Type | Required |
-| ------ | -------- |
-| number | Yes |
-
----
-
-### `inverted`
-
-Reverses the direction of scroll. Uses scale transforms of -1.
-
-| Type | Required |
-| --------- | -------- |
-| [boolean] | No |
-
----
-
-### `ItemSeparatorComponent`
-
-Rendered in between each item, but not at the top or bottom. By default, `highlighted`, `section`, and `[leading/trailing][Item/Section]` props are provided. `renderItem` provides `separators.highlight`/`unhighlight` which will update the `highlighted` prop, but you can also add custom props with `separators.updateProps`.
-
-| Type | Required |
-| -------------------- | -------- |
-| [component, element] | No |
-
----
-
-### `keyExtractor`
-
-Used to extract a unique key for a given item at the specified index. Key is used for caching and as the React key to track item re-ordering. The default extractor checks `item.key`, then falls back to using the index, like React does. Note that this sets keys for each item, but each overall section still needs its own key.
-
-| Type | Required |
-| ------------------------------------- | -------- |
-| (item: Item, index: number) => string | Yes |
-
----
-
-### `legacyImplementation`
-
-The legacy implementation is no longer supported.
-
-| Type | Required |
-| --------- | -------- |
-| [boolean] | No |
-
----
-
-### `ListEmptyComponent`
-
-Rendered when the list is empty. Can be a React Component (e.g. `SomeComponent`), or a React element (e.g. `]` | No |
-
----
-
-### `renderSectionHeader`
-
-Rendered at the top of each section. These stick to the top of the `ScrollView` by default on iOS. See `stickySectionHeadersEnabled`.
-
-| Type | Required |
-| ------------------------------------------------------ | -------- |
-| `[(info: {section: SectionT}) => ?React.Element]` | No |
-
----
-
-### `SectionSeparatorComponent`
-
-Rendered at the top and bottom of each section (note this is different from `ItemSeparatorComponent` which is only rendered between items). These are intended to separate sections from the headers above and below and typically have the same highlight response as `ItemSeparatorComponent`. Also receives `highlighted`, `[leading/trailing][Item/Section]`, and any custom props from `separators.updateProps`.
-
-| Type | Required |
-| ------------------- | -------- |
-| `[ReactClass]` | No |
-
----
-
-### `stickySectionHeadersEnabled`
-
-Makes section headers stick to the top of the screen until the next one pushes it off. Only enabled by default on iOS because that is the platform standard there.
-
-| Type | Default |
-| ------- | ------------------------------------------------------------------------------------------------ |
-| boolean | `false` Android
iOS
|
-
-## Methods
-
-### `scrollToLocation()`
-
-```jsx
-scrollToLocation(params);
-```
-
-Scrolls to the item at the specified `sectionIndex` and `itemIndex` (within the section) positioned in the viewable area such that `viewPosition` 0 places it at the top (and may be covered by a sticky header), 1 at the bottom, and 0.5 centered in the middle.
-
-> Note: Cannot scroll to locations outside the render window without specifying the `getItemLayout` or `onScrollToIndexFailed` prop.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ----------- |
-| params | object | Yes | See below. |
-
-Valid `params` keys are:
-
-- 'animated' (boolean) - Whether the list should do an animation while scrolling. Defaults to `true`.
-- 'itemIndex' (number) - Index within section for the item to scroll to. Required.
-- 'sectionIndex' (number) - Index for section that contains the item to scroll to. Required.
-- 'viewOffset' (number) - A fixed number of pixels to offset the final target position, e.g. to compensate for sticky headers.
-- 'viewPosition' (number) - A value of `0` places the item specified by index at the top, `1` at the bottom, and `0.5` centered in the middle.
-
----
-
-### `recordInteraction()`
-
-```jsx
-recordInteraction();
-```
-
-Tells the list an interaction has occurred, which should trigger viewability calculations, e.g. if `waitForInteractions` is true and the user has not scrolled. This is typically called by taps on items or by navigation actions.
-
----
-
-### `flashScrollIndicators()`
-
-```jsx
-flashScrollIndicators();
-```
-
-Displays the scroll indicators momentarily.
-
-| Platfrom |
-| -------- |
-| iOS |
-
-## Type Definitions
-
-### Section
-
-An object that identifies the data to be rendered for a given section.
-
-| Type |
-| ---- |
-| any |
-
-**Properties:**
-
-| Name | Type | Description |
-| ------------------------ | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| data | array | The data for rendering items in this section. Array of objects, much like [`FlatList`'s data prop](flatlist.md#required-data). |
-| [key] | string | Optional key to keep track of section re-ordering. If you don't plan on re-ordering sections, the array index will be used by default. |
-| [renderItem] | function | Optionally define an arbitrary item renderer for this section, overriding the default [`renderItem`](sectionlist.md#renderitem) for the list. |
-| [ItemSeparatorComponent] | component, element | Optionally define an arbitrary item separator for this section, overriding the default [`ItemSeparatorComponent`](sectionlist.md#itemseparatorcomponent) for the list. |
-| [keyExtractor] | function | Optionally define an arbitrary key extractor for this section, overriding the default [`keyExtractor`](sectionlist.md#keyextractor). |
diff --git a/website/versioned_docs/version-0.60/segmentedcontrolios.md b/website/versioned_docs/version-0.60/segmentedcontrolios.md
deleted file mode 100644
index 63b240f22a0..00000000000
--- a/website/versioned_docs/version-0.60/segmentedcontrolios.md
+++ /dev/null
@@ -1,124 +0,0 @@
----
-id: segmentedcontrolios
-title: SegmentedControlIOS
----
-
-> **Deprecated.** Use [@react-native-community/segmented-control](https://github.com/react-native-segmented-control/segmented-control) instead.
-
-Uses `SegmentedControlIOS` to render a UISegmentedControl iOS.
-
-#### Programmatically changing selected index
-
-The selected index can be changed on the fly by assigning the selectedIndex prop to a state variable, then changing that variable. Note that the state variable would need to be updated as the user selects a value and changes the index, as shown in the example below.
-
-## Example
-
-```SnackPlayer name=SegmentedControlIOS%20Example&supportedPlatforms=ios
-import React, { useState } from "react";
-import { SegmentedControlIOS, StyleSheet, Text, View } from "react-native";
-
-export default App = () => {
- const [index, setIndex] = useState(0);
- return (
-
- {
- setIndex(event.nativeEvent.selectedSegmentIndex);
- }}
- />
-
- Selected index: {index}
-
-
- );
-};
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- padding: 24,
- justifyContent: "center"
- },
- text: {
- marginTop: 24
- }
-});
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `enabled`
-
-If false the user won't be able to interact with the control. Default value is true.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `momentary`
-
-If true, then selecting a segment won't persist visually. The `onValueChange` callback will still work as expected.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `onChange`
-
-Callback that is called when the user taps a segment; passes the event as an argument
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onValueChange`
-
-Callback that is called when the user taps a segment; passes the segment's value as an argument
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `selectedIndex`
-
-The index in `props.values` of the segment to be (pre)selected.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `tintColor`
-
-Accent color of the control.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `values`
-
-The labels for the control's segment buttons, in order.
-
-| Type | Required |
-| --------------- | -------- |
-| array of string | No |
diff --git a/website/versioned_docs/version-0.60/settings.md b/website/versioned_docs/version-0.60/settings.md
deleted file mode 100644
index 7f19edde71c..00000000000
--- a/website/versioned_docs/version-0.60/settings.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-id: settings
-title: Settings
----
-
-`Settings` serves as a wrapper for [`NSUserDefaults`](https://developer.apple.com/documentation/foundation/nsuserdefaults), a persistent key-value store available only on iOS.
-
----
-
-# Reference
-
-## Methods
-
-### `clearWatch()`
-
-```jsx
-static clearWatch(watchId)
-```
-
-`watchId` is the number returned by `watchKeys()` when the subscription was originally configured.
-
-### `get()`
-
-```jsx
-static get(key)
-```
-
-Get the current value for a key in `NSUserDefaults`.
-
----
-
-### `set()`
-
-```jsx
-static set(settings)
-```
-
-Set one or more values in `NSUserDefaults`.
-
----
-
-### `watchKeys()`
-
-```jsx
-static watchKeys(keys, callback)
-```
-
-Subscribe to be notified when the value for any of the keys specified by the `keys` array changes in `NSUserDefaults`. Returns a `watchId` number that may be used with `clearWatch()` to unsubscribe.
diff --git a/website/versioned_docs/version-0.60/shadow-props.md b/website/versioned_docs/version-0.60/shadow-props.md
deleted file mode 100644
index a51a19fe9f5..00000000000
--- a/website/versioned_docs/version-0.60/shadow-props.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-id: shadow-props
-title: Shadow Props
----
-
-# Reference
-
-## Props
-
-### `shadowColor`
-
-Sets the drop shadow color
-
-| Type | Required | Platform |
-| ------------------ | -------- | -------- |
-| [color](colors.md) | No | iOS |
-
----
-
-### `shadowOffset`
-
-Sets the drop shadow offset
-
-| Type | Required | Platform |
-| -------------------------------------- | -------- | -------- |
-| object: {width: number,height: number} | No | iOS |
-
----
-
-### `shadowOpacity`
-
-Sets the drop shadow opacity (multiplied by the color's alpha component)
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | iOS |
-
----
-
-### `shadowRadius`
-
-Sets the drop shadow blur radius
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | iOS |
diff --git a/website/versioned_docs/version-0.60/share.md b/website/versioned_docs/version-0.60/share.md
deleted file mode 100644
index 45e78c8d8bb..00000000000
--- a/website/versioned_docs/version-0.60/share.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-id: share
-title: Share
----
-
-# Reference
-
-## Methods
-
-### `share()`
-
-```jsx
-static share(content, options)
-```
-
-Open a dialog to share text content.
-
-In iOS, Returns a Promise which will be invoked an object containing `action`, `activityType`. If the user dismissed the dialog, the Promise will still be resolved with action being `Share.dismissedAction` and all the other keys being undefined. Note that some share options will not appear or work on the iOS simulator.
-
-In Android, Returns a Promise which always be resolved with action being `Share.sharedAction`.
-
-### Content
-
-- `message` - a message to share
-- `title` - title of the message
-
-#### iOS
-
-- `url` - an URL to share
-
-At least one of URL and message is required.
-
-### Options
-
-#### iOS
-
-- `subject` - a subject to share via email
-- `excludedActivityTypes`
-- `tintColor`
-
-#### Android
-
-- `dialogTitle`
-
----
-
-### `sharedAction()`
-
-```jsx
-static sharedAction()
-```
-
-The content was successfully shared.
-
----
-
-### `dismissedAction()`
-
-```jsx
-static dismissedAction()
-```
-
-_iOS Only_. The dialog has been dismissed.
-
-## Basic Example
-
-```jsx
-import React, {Component} from 'react';
-import {Share, Button} from 'react-native';
-
-class ShareExample extends Component {
- onShare = async () => {
- try {
- const result = await Share.share({
- message:
- 'React Native | A framework for building native apps using React',
- });
-
- if (result.action === Share.sharedAction) {
- if (result.activityType) {
- // shared with activity type of result.activityType
- } else {
- // shared
- }
- } else if (result.action === Share.dismissedAction) {
- // dismissed
- }
- } catch (error) {
- alert(error.message);
- }
- };
-
- render() {
- return {props.text} ;
-};
-
-const BlinkApp = () => {
- return (
-
-
- );
-};
-
-export default 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.
-
-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 the default text color. To customize the text color, you will have to [learn about Style](style.md).
diff --git a/website/versioned_docs/version-0.60/statusbar.md b/website/versioned_docs/version-0.60/statusbar.md
deleted file mode 100644
index 9f7d63f0045..00000000000
--- a/website/versioned_docs/version-0.60/statusbar.md
+++ /dev/null
@@ -1,270 +0,0 @@
----
-id: statusbar
-title: StatusBar
----
-
-Component to control the app status bar.
-
-### Usage with Navigator
-
-It is possible to have multiple `StatusBar` components mounted at the same time. The props will be merged in the order the `StatusBar` components were mounted.
-
-```jsx
-
-
-
-
-```
-
-### Imperative API
-
-For cases where using a component is not ideal, there is also an imperative API exposed as static functions on the component. It is however not recommended to use the static API and the component for the same prop because any value set by the static API will get overridden by the one set by the component in the next render.
-
----
-
-# Reference
-
-## Constants
-
-`currentHeight` (Android only) The height of the status bar.
-
-## Props
-
-### `animated`
-
-If the transition between status bar property changes should be animated. Supported for backgroundColor, barStyle and hidden.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `backgroundColor`
-
-The background color of the status bar.
-
-| Type | Required | Platform |
-| ------------------ | -------- | -------- |
-| [color](colors.md) | No | Android |
-
----
-
-### `barStyle`
-
-Sets the color of the status bar text.
-
-| Type | Required |
-| ------------------------------------------------ | -------- |
-| enum('default', 'light-content', 'dark-content') | No |
-
----
-
-### `hidden`
-
-If the status bar is hidden.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `networkActivityIndicatorVisible`
-
-If the network activity indicator should be visible.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `showHideTransition`
-
-The transition effect when showing and hiding the status bar using the `hidden` prop. Defaults to 'fade'.
-
-| Type | Required | Platform |
-| --------------------- | -------- | -------- |
-| enum('fade', 'slide') | No | iOS |
-
----
-
-### `translucent`
-
-If the status bar is translucent. When translucent is set to true, the app will draw under the status bar. This is useful when using a semi transparent status bar color.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
-## Methods
-
-### `popStackEntry()`
-
-```jsx
-static popStackEntry(entry: any)
-```
-
-Get and remove the last a StatusBar entry from the stack.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----- | ---- | -------- | ------------------------------------- |
-| entry | any | Yes | Entry returned from `pushStackEntry`. |
-
----
-
-### `pushStackEntry()`
-
-```jsx
-static pushStackEntry(props: any)
-```
-
-Push a StatusBar entry onto the stack. The return value should be passed to `popStackEntry` when complete.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----- | ---- | -------- | ---------------------------------------------------------------- |
-| props | any | Yes | Object containing the StatusBar props to use in the stack entry. |
-
----
-
-### `replaceStackEntry()`
-
-```jsx
-static replaceStackEntry(entry: any, props: any)
-```
-
-Replace an existing StatusBar stack entry with new props.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----- | ---- | -------- | ---------------------------------------------------------------------------- |
-| entry | any | Yes | Entry returned from `pushStackEntry` to replace. |
-| props | any | Yes | Object containing the StatusBar props to use in the replacement stack entry. |
-
----
-
-### `setBackgroundColor()`
-
-```jsx
-static setBackgroundColor(color: string, [animated]: boolean)
-```
-
-Set the background color for the status bar. Android-only
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ------- | -------- | ------------------------- |
-| color | string | Yes | Background color. |
-| animated | boolean | No | Animate the style change. |
-
----
-
-### `setBarStyle()`
-
-```jsx
-static setBarStyle(style: StatusBarStyle, [animated]: boolean)
-```
-
-Set the status bar style
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | --------------------------------------------- | -------- | ------------------------- |
-| style | [StatusBarStyle](statusbar.md#statusbarstyle) | Yes | Status bar style to set |
-| animated | boolean | No | Animate the style change. |
-
----
-
-### `setHidden()`
-
-```jsx
-static setHidden(hidden: boolean, [animation]: StatusBarAnimation)
-```
-
-Show or hide the status bar
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| --------- | ----------------------------------------------------- | -------- | ---------------------------------------------------------------- |
-| hidden | boolean | Yes | Hide the status bar. |
-| animation | [StatusBarAnimation](statusbar.md#statusbaranimation) | No | Optional animation when changing the status bar hidden property. |
-
----
-
-### `setNetworkActivityIndicatorVisible()`
-
-```jsx
-static setNetworkActivityIndicatorVisible(visible: boolean)
-```
-
-Control the visibility of the network activity indicator. iOS-only.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------- | ------- | -------- | ------------------- |
-| visible | boolean | Yes | Show the indicator. |
-
----
-
-### `setTranslucent()`
-
-```jsx
-static setTranslucent(translucent: boolean)
-```
-
-Control the translucency of the status bar. Android-only.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----------- | ------- | -------- | ------------------- |
-| translucent | boolean | Yes | Set as translucent. |
-
-## Type Definitions
-
-### StatusBarAnimation
-
-Status bar animation
-
-| Type |
-| ------ |
-| \$Enum |
-
-**Constants:**
-
-| Value | Description |
-| ----- | --------------- |
-| none | No animation |
-| fade | Fade animation |
-| slide | Slide animation |
-
----
-
-### StatusBarStyle
-
-Status bar style
-
-| Type |
-| ------ |
-| \$Enum |
-
-**Constants:**
-
-| Value | Description |
-| ------------- | -------------------------------------------------------------------- |
-| default | Default status bar style (dark for iOS, light for Android) |
-| light-content | Dark background, white texts and icons |
-| dark-content | Light background, dark texts and icons (requires API>=23 on Android) |
diff --git a/website/versioned_docs/version-0.60/statusbarios.md b/website/versioned_docs/version-0.60/statusbarios.md
deleted file mode 100644
index 8d74ee7d4d3..00000000000
--- a/website/versioned_docs/version-0.60/statusbarios.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-id: statusbarios
-title: StatusBarIOS
----
-
-> Use `StatusBar` for mutating the status bar.
-
----
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 a41e8216f86..00000000000
--- a/website/versioned_docs/version-0.60/style.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-id: style
-title: Style
----
-
-With React Native, you 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 (
-
- just red
- just bigBlue
- bigBlue, then red
- red, then bigBlue
-
- );
- }
-}
-```
-
-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 expert is to [learn how to control component size](height-and-width.md).
diff --git a/website/versioned_docs/version-0.60/stylesheet.md b/website/versioned_docs/version-0.60/stylesheet.md
deleted file mode 100644
index b2cbcb630a6..00000000000
--- a/website/versioned_docs/version-0.60/stylesheet.md
+++ /dev/null
@@ -1,185 +0,0 @@
----
-id: stylesheet
-title: StyleSheet
----
-
-A StyleSheet is an abstraction similar to CSS StyleSheets
-
-Create a new StyleSheet:
-
-```jsx
-const styles = StyleSheet.create({
- container: {
- borderRadius: 4,
- borderWidth: 0.5,
- borderColor: '#d6d7da',
- },
- title: {
- fontSize: 19,
- fontWeight: 'bold',
- },
- activeTitle: {
- color: 'red',
- },
-});
-```
-
-Use a StyleSheet:
-
-```jsx
-
-
-```
-
-Code quality:
-
-- By moving styles away from the render function, you're making the code easier to understand.
-- Naming the styles is a good way to add meaning to the low level components in the render function.
-
----
-
-# Reference
-
-## Methods
-
-### `setStyleAttributePreprocessor()`
-
-```jsx
-static setStyleAttributePreprocessor(property, process)
-```
-
-WARNING: EXPERIMENTAL. Breaking changes will probably happen a lot and will not be reliably announced. The whole thing might be deleted, who knows? Use at your own risk.
-
-Sets a function to use to pre-process a style property value. This is used internally to process color and transform values. You should not use this unless you really know what you are doing and have exhausted other options.
-
----
-
-### `create()`
-
-```jsx
-static create(obj)
-```
-
-Creates a StyleSheet style reference from the given object.
-
----
-
-### `flatten`
-
-```jsx
-static flatten(style)
-```
-
-Flattens an array of style objects, into one aggregated style object. Alternatively, this method can be used to lookup IDs, returned by `StyleSheet.register`.
-
-> _NOTE_: Exercise caution as abusing this can tax you in terms of optimizations. IDs enable optimizations through the bridge and memory in general. Refering to style objects directly will deprive you of these optimizations.
-
-Example:
-
-```jsx
-var styles = StyleSheet.create({
- listItem: {
- flex: 1,
- fontSize: 16,
- color: 'white',
- },
- selectedListItem: {
- color: 'green',
- },
-});
-
-StyleSheet.flatten([styles.listItem, styles.selectedListItem]);
-// returns { flex: 1, fontSize: 16, color: 'green' }
-```
-
-Alternative use:
-
-```jsx
-var styles = StyleSheet.create({
- listItem: {
- flex: 1,
- fontSize: 16,
- color: 'white',
- },
- selectedListItem: {
- color: 'green',
- },
-});
-
-StyleSheet.flatten(styles.listItem);
-// returns { flex: 1, fontSize: 16, color: 'white' }
-// Simply styles.listItem would return its ID (number)
-```
-
-This method internally uses `StyleSheetRegistry.getStyleByID(style)` to resolve style objects represented by IDs. Thus, an array of style objects (instances of `StyleSheet.create()`), are individually resolved to, their respective objects, merged as one and then returned. This also explains the alternative use.
-
----
-
-### `compose`
-
-Combines two styles such that `style2` will override any styles in `style1`. If either style is falsy, the other one is returned without allocating an array, saving allocations and maintaining reference equality for PureComponent checks.
-
-```jsx
-static compose(style1, style2)
-```
-
-## Properties
-
-### `hairlineWidth`
-
-This is defined as the width of a thin line on the platform. It can be used as the thickness of a border or division between two elements. Example:
-
-```jsx
-var styles = StyleSheet.create({
- separator: {
- borderBottomColor: '#bbb',
- borderBottomWidth: StyleSheet.hairlineWidth,
- },
-});
-```
-
-This constant will always be a round number of pixels (so a line defined by it can look crisp) and will try to match the standard width of a thin line on the underlying platform. However, you should not rely on it being a constant size, because on different platforms and screen densities its value may be calculated differently.
-
-A line with hairline width may not be visible if your simulator is downscaled.
-
----
-
-### `absoluteFill`
-
-A very common pattern is to create overlays with position absolute and zero positioning (`position: 'absolute', left: 0, right: 0, top: 0, bottom: 0`), so `absoluteFill` can be used for convenience and to reduce duplication of these repeated styles. If you want, absoluteFill can be used to create a customized entry in a StyleSheet, e.g.:
-
-```jsx
-const styles = StyleSheet.create({
- wrapper: {
- ...StyleSheet.absoluteFill,
- },
-});
-```
-
----
-
-### `absoluteFillObject`
-
-Sometimes you may want `absoluteFill` but with a couple tweaks - `absoluteFillObject` can be used to create a customized entry in a `StyleSheet`, e.g.:
-
-```jsx
-const styles = StyleSheet.create({
- wrapper: {
- ...StyleSheet.absoluteFillObject,
- top: 10,
- backgroundColor: 'transparent',
- },
-});
-```
-
----
-
-### `absoluteFill` vs. `absoluteFillObject`
-
-Currently, there is no difference between using `absoluteFill` vs. `absoluteFillObject` as you can see in the [source code](https://github.com/facebook/react-native/blob/0.60-stable/Libraries/StyleSheet/StyleSheet.js#L255)
diff --git a/website/versioned_docs/version-0.60/switch.md b/website/versioned_docs/version-0.60/switch.md
deleted file mode 100644
index c260569d678..00000000000
--- a/website/versioned_docs/version-0.60/switch.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-id: switch
-title: Switch
----
-
-Renders a boolean input.
-
-This is a controlled component that requires an `onValueChange` callback that updates the `value` prop in order for the component to reflect user actions. If the `value` prop is not updated, the component will continue to render the supplied `value` prop instead of the expected result of any user actions.
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `disabled`
-
-If true the user won't be able to toggle the switch. Default value is false.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `ios_backgroundColor`
-
-On iOS, custom color for the background. This background color can be seen either when the switch value is false or when the switch is disabled (and the switch is translucent).
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `onChange`
-
-Invoked when the user tries to change the value of the switch. Receives the change event as an argument. If you want to only receive the new value, use `onValueChange` instead.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onValueChange`
-
-Invoked when the user tries to change the value of the switch. Receives the new value as an argument. If you want to instead receive an event, use `onChange`.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `thumbColor`
-
-Color of the foreground switch grip. If this is set on iOS, the switch grip will lose its drop shadow.
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `trackColor`
-
-Custom colors for the switch track.
-
-_iOS_: When the switch value is false, the track shrinks into the border. If you want to change the color of the background exposed by the shrunken track, use [`ios_backgroundColor`](switch.md#ios_backgroundColor).
-
-| Type | Required |
-| ------------------------------------------------------------- | -------- |
-| object: {false: [color](colors.md), true: [color](colors.md)} | No |
-
----
-
-### `value`
-
-The value of the switch. If true the switch will be turned on. Default value is false.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
diff --git a/website/versioned_docs/version-0.60/symbolication.md b/website/versioned_docs/version-0.60/symbolication.md
deleted file mode 100644
index 642e412ce1f..00000000000
--- a/website/versioned_docs/version-0.60/symbolication.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-id: symbolication
-title: Symbolicating a stack trace
----
-
-If a React Native app throws an unhandled exception in a release build, the output may be obfuscated and hard to read:
-
-```shell
-07-15 10:58:25.820 18979 18998 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
-07-15 10:58:25.820 18979 18998 E AndroidRuntime: Process: com.awesomeproject, PID: 18979 07-15 10:58:25.820 18979 18998 E AndroidRuntime: com.facebook.react.common.JavascriptException: Failed, js engine: hermes, stack:
-07-15 10:58:25.820 18979 18998 E AndroidRuntime: p@1:132161
-07-15 10:58:25.820 18979 18998 E AndroidRuntime: p@1:132084
-07-15 10:58:25.820 18979 18998 E AndroidRuntime: f@1:131854
-07-15 10:58:25.820 18979 18998 E AndroidRuntime: anonymous@1:131119
-```
-
-The sections like `p@1:132161` are minified function names and bytecode offsets. To debug the problem, you would instead want to translate it into file, line and function name: `AwesomeProject/App.js:54:initializeMap`. This is known as **symbolication.** You can symbolicate minified function names and bytecode like the above by passing `metro-symbolicate` a generated source map and the stack trace.
-
-> The `metro-symbolicate` package is installed by default in the React Native template project from [setting up your development environment](/docs/environment-setup).
-
-From a file containing the stacktrace:
-
-```shell
-npx metro-symbolicate android/app/build/generated/sourcemaps/react/release/index.android.bundle.map < stacktrace.txt
-```
-
-From `adb logcat`directly:
-
-```shell
-adb logcat -d | npx metro-symbolicate android/app/build/generated/sourcemaps/react/release/index.android.bundle.map
-```
-
-This will turn each minified function name and offset like `p@1:132161` into the actual file- and function name `AwesomeProject/App.js:54:initializeMap`.
-
-## Notes on Sourcemaps
-
-- Multiple source maps may be generated by the build process. Make sure to used the one in the location shown in the examples.
-- Make sure that the source map you use corresponds to the exact commit of the crashing app. Small changes in source code can cause large differences in offsets.
-- If `metro-symbolicate` exits immediately with success, make sure the input comes from a pipe or redirection and not from a terminal.
diff --git a/website/versioned_docs/version-0.60/systrace.md b/website/versioned_docs/version-0.60/systrace.md
deleted file mode 100644
index 9c79d595715..00000000000
--- a/website/versioned_docs/version-0.60/systrace.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-id: systrace
-title: Systrace
----
-
-# Reference
-
-## Methods
-
-### `installReactHook()`
-
-```jsx
-static installReactHook(useFiber)
-```
-
----
-
-### `setEnabled()`
-
-```jsx
-static setEnabled(enabled)
-```
-
----
-
-### `isEnabled()`
-
-```jsx
-static isEnabled()
-```
-
----
-
-### `beginEvent()`
-
-```jsx
-static beginEvent(profileName?, args?)
-```
-
-beginEvent/endEvent for starting and then ending a profile within the same call stack frame.
-
----
-
-### `endEvent()`
-
-```jsx
-static endEvent()
-```
-
----
-
-### `beginAsyncEvent()`
-
-```jsx
-static beginAsyncEvent(profileName?)
-```
-
-beginAsyncEvent/endAsyncEvent for starting and then ending a profile where the end can either occur on another thread or out of the current stack frame, eg await the returned cookie variable should be used as input into the endAsyncEvent call to end the profile.
-
----
-
-### `endAsyncEvent()`
-
-```jsx
-static endAsyncEvent(profileName?, cookie?)
-```
-
----
-
-### `counterEvent()`
-
-```jsx
-static counterEvent(profileName?, value?)
-```
-
-Register the value to the profileName on the systrace timeline.
diff --git a/website/versioned_docs/version-0.60/tabbarios-item.md b/website/versioned_docs/version-0.60/tabbarios-item.md
deleted file mode 100644
index 3fb6b777023..00000000000
--- a/website/versioned_docs/version-0.60/tabbarios-item.md
+++ /dev/null
@@ -1,134 +0,0 @@
----
-id: tabbarios-item
-title: TabBarIOS.Item
----
-
-### Props
-
-- [View props...](view.md#props)
-
-* [`selected`](tabbarios-item.md#selected)
-* [`badge`](tabbarios-item.md#badge)
-* [`icon`](tabbarios-item.md#icon)
-* [`onPress`](tabbarios-item.md#onpress)
-* [`renderAsOriginal`](tabbarios-item.md#renderasoriginal)
-* [`badgeColor`](tabbarios-item.md#badgecolor)
-* [`selectedIcon`](tabbarios-item.md#selectedicon)
-* [`style`](tabbarios-item.md#style)
-* [`systemIcon`](tabbarios-item.md#systemicon)
-* [`title`](tabbarios-item.md#title)
-* [`isTVSelectable`](tabbarios-item.md#istvselectable)
-
----
-
-# Reference
-
-## Props
-
-### `selected`
-
-It specifies whether the children are visible or not. If you see a blank content, you probably forgot to add a selected one.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `badge`
-
-Little red bubble that sits at the top right of the icon.
-
-| Type | Required |
-| --------------- | -------- |
-| string, ,number | No |
-
----
-
-### `icon`
-
-A custom icon for the tab. It is ignored when a system icon is defined.
-
-| Type | Required |
-| ---------------------- | -------- |
-| Image.propTypes.source | No |
-
----
-
-### `onPress`
-
-Callback when this tab is being selected, you should change the state of your component to set selected={true}.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `renderAsOriginal`
-
-If set to true it renders the image as original, it defaults to being displayed as a template
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `badgeColor`
-
-Background color for the badge. Available since iOS 10.
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `selectedIcon`
-
-A custom icon when the tab is selected. It is ignored when a system icon is defined. If left empty, the icon will be tinted in blue.
-
-| Type | Required |
-| ---------------------- | -------- |
-| Image.propTypes.source | No |
-
----
-
-### `style`
-
-React style object.
-
-| Type | Required |
-| ---------- | -------- |
-| View.style | No |
-
----
-
-### `systemIcon`
-
-Items comes with a few predefined system icons. Note that if you are using them, the title and selectedIcon will be overridden with the system ones.
-
-| Type | Required |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- |
-| enum('bookmarks', 'contacts', 'downloads', 'favorites', 'featured', 'history', 'more', 'most-recent', 'most-viewed', 'recents', 'search', 'top-rated') | No |
-
----
-
-### `title`
-
-Text that appears under the icon. It is ignored when a system icon is defined.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `isTVSelectable`
-
-(Apple TV only)\* When set to true, this view will be focusable and navigable using the Apple TV remote.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
diff --git a/website/versioned_docs/version-0.60/tabbarios.md b/website/versioned_docs/version-0.60/tabbarios.md
deleted file mode 100644
index 46b593e2178..00000000000
--- a/website/versioned_docs/version-0.60/tabbarios.md
+++ /dev/null
@@ -1,103 +0,0 @@
----
-id: tabbarios
-title: TabBarIOS
----
-
-### Props
-
-- [View props...](view.md#props)
-
-* [`barStyle`](tabbarios.md#barstyle)
-* [`barTintColor`](tabbarios.md#bartintcolor)
-* [`itemPositioning`](tabbarios.md#itempositioning)
-* [`style`](tabbarios.md#style)
-* [`tintColor`](tabbarios.md#tintcolor)
-* [`translucent`](tabbarios.md#translucent)
-* [`unselectedItemTintColor`](tabbarios.md#unselecteditemtintcolor)
-* [`unselectedTintColor`](tabbarios.md#unselectedtintcolor)
-
----
-
-# Reference
-
-## Props
-
-### `barStyle`
-
-The style of the tab bar. Supported values are 'default', 'black'. Use 'black' instead of setting `barTintColor` to `black`. This produces a tab bar with the native iOS style with higher translucency.
-
-| Type | Required |
-| ------------------------ | -------- |
-| enum('default', 'black') | No |
-
----
-
-### `barTintColor`
-
-Background color of the tab bar
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `itemPositioning`
-
-Specifies tab bar item positioning. Available values are:
-
-- fill - distributes items across the entire width of the tab bar
-- center - centers item in the available tab bar space
-- auto (default) - distributes items dynamically according to the user interface idiom. In a horizontally compact environment (e.g. iPhone 5) this value defaults to `fill`, in a horizontally regular one (e.g. iPad) it defaults to center.
-
-| Type | Required |
-| ------------------------------ | -------- |
-| enum('fill', 'center', 'auto') | No |
-
----
-
-### `style`
-
-| Type | Required |
-| ---------- | -------- |
-| View.style | No |
-
----
-
-### `tintColor`
-
-Color of the currently selected tab icon
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `translucent`
-
-A Boolean value that indicates whether the tab bar is translucent
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `unselectedItemTintColor`
-
-Color of unselected tab icons. Available since iOS 10.
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `unselectedTintColor`
-
-Color of text on unselected tabs
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
diff --git a/website/versioned_docs/version-0.60/testing-overview.md b/website/versioned_docs/version-0.60/testing-overview.md
deleted file mode 100644
index 9bb25763527..00000000000
--- a/website/versioned_docs/version-0.60/testing-overview.md
+++ /dev/null
@@ -1,272 +0,0 @@
----
-id: testing-overview
-title: Testing
-author: Vojtech Novak
-authorURL: 'https://twitter.com/vonovak'
-description: This guide introduces React Native developers to the key concepts behind testing, how to write good tests, and what kinds of tests you can incorporate into your workflow.
----
-
-As your codebase expands, small errors and edge cases you don’t expect can cascade into larger failures. Bugs lead to bad user experience and ultimately, business losses. One way to prevent fragile programming is to test your code before releasing it into the wild.
-
-In this guide, we will cover different, automated ways to ensure your app works as expected, ranging from static analysis to end-to-end tests.
-
-QA , freeing up valuable time.
-
-## Static Analysis
-
-The first step to improve your code quality is to start using static analysis tools. Static analysis checks your code for errors as you write it, but without running any of that code.
-
-- **Linters** analyze code to catch common errors such as unused code and to help avoid pitfalls, to flag style guide no-nos like using tabs instead of spaces (or vice versa, depending on your configuration).
-- **Type checking** ensures that the construct you’re passing to a function matches what the function was designed to accept, preventing passing a string to a counting function that expects a number, for instance.
-
-React Native comes with two such tools configured out of the box: [ESLint](https://eslint.org/) for linting and [Flow](https://flow.org/en/docs/) for type checking. You can also use [TypeScript](typescript), which is a typed language that compiles to plain JavaScript.
-
-## Writing Testable Code
-
-To start with tests, you first need to write code that is testable. Consider an aircraft manufacturing process - before any model first takes off to show that all of its complex systems work well together, individual parts are tested to guarantee they are safe and function correctly. For example, wings are tested by bending them under extreme load; engine parts are tested for their durability; the windshield is tested against simulated bird impact.
-
-Software is similar. Instead of writing your entire program in one huge file with many lines of code, you write your code in multiple small modules that you can test more thoroughly than if you tested the assembled whole. In this way, writing testable code is intertwined with writing clean, modular code.
-
-To make your app more testable, start by separating the view part of your app—your React components—from your business logic and app state (regardless of whether you use Redux, MobX or other solutions). This way, you can keep your business logic testing—which shouldn’t rely on your React components—independent of the components themselves, whose job is primarily rendering your app’s UI!
-
-Theoretically, you could go so far as to move all logic and data fetching out of your components. This way your components would be solely dedicated to rendering. Your state would be entirely independent of your components. Your app’s logic would work without any React components at all!
-
-> We encourage you to further explore the topic of testable code in other learning resources.
-
-## Writing Tests
-
-After writing testable code, it’s time to write some actual tests! The default template of React Native ships with [Jest](https://jestjs.io) testing framework. It includes a preset that's tailored to this environment so you can get productive without tweaking the configuration and mocks straight away—[more on mocks](#mocking) shortly. You can use Jest to write all types of tests featured in this guide.
-
-> If you do test-driven development, you actually write tests first! That way, testability of your code is given.
-
-### Structuring Tests
-
-Your tests should be short and ideally test only one thing. Let's start with an example unit test written with Jest:
-
-```js
-it('given a date in the past, colorForDueDate() returns red', () => {
- expect(colorForDueDate('2000-10-20')).toBe('red');
-});
-```
-
-The test is described by the string passed to the [`it`](https://jestjs.io/docs/en/api#testname-fn-timeout) function. Take good care writing the description so that it’s clear what is being tested. Do your best to cover the following:
-
-1. **Given** - some precondition
-2. **When** - some action executed by the function that you’re testing
-3. **Then** - the expected outcome
-
-This is also known as AAA (Arrange, Act, Assert).
-
-Jest offers [`describe`](https://jestjs.io/docs/en/api#describename-fn) function to help structure your tests. Use `describe` to group together all tests that belong to one functionality. Describes can be nested, if you need that. Other functions you'll commonly use are [`beforeEach`](https://jestjs.io/docs/en/api#beforeeachfn-timeout) or [`beforeAll`](https://jestjs.io/docs/en/api#beforeallfn-timeout) that you can use for setting up the objects you're testing. Read more in the [Jest api reference](https://jestjs.io/docs/en/api).
-
-If your test has many steps or many expectations, you probably want to split it into multiple smaller ones. Also, ensure that your tests are completely independent of one another. Each test in your suite must be executable on its own without first running some other test. Conversely, if you run all your tests together, the first test must not influence the output of the second one.
-
-Lastly, as developers we like when our code works great and doesn't crash. With tests, this is often the opposite. Think of a failed test as of a _good thing!_ When a test fails, it often means something is not right. This gives you an opportunity to fix the problem before it impacts the users.
-
-## Unit tests
-
-Unit tests cover the smallest parts of code, like individual functions or classes.
-
-When the object being tested has any dependencies, you’ll often need to mock them out, as described in the next paragraph.
-
-The great thing about unit tests is that they are quick to write and run. Therefore, as you work, you get fast feedback about whether your tests are passing. Jest even has an option to continuously run tests that are related to code you’re editing: [Watch mode](https://jestjs.io/docs/en/cli#watch).
-
-I/O
-
- setGroceryItem(text)}
- />
- {item}
- ))}
-
- );
-}
-```
-
-When testing user interactions, test the component from the user perspective—what's on the page? What changes when interacted with?
-
-As a rule of thumb, prefer using things users can see or hear:
-
-- make assertions using rendered text or [accessibility helpers](https://reactnative.dev/docs/accessibility#accessibility-properties)
-
-Conversely, you should avoid:
-
-- making assertions on component props or state
-- testID queries
-
-Avoid testing implementation details like props or state—while such tests work, they are not oriented toward how users will interact with the component and tend to break by refactoring (for example when you'd like to rename some things or rewrite class component using hooks).
-
-> React class components are especially prone to testing their implementation details such as internal state, props or event handlers. To avoid testing implementation details, prefer using function components with Hooks, which make relying on component internals _harder_.
-
-Component testing libraries such as [React Native Testing Library](https://callstack.github.io/react-native-testing-library/) facilitate writing user-centric tests by careful choice of provided APIs. The following example uses `fireEvent` methods `changeText` and `press` that simulate a user interacting with the component and a query function `getAllByText` that finds matching `Text` nodes in the rendered output.
-
-```jsx
-test('given empty GroceryShoppingList, user can add an item to it', () => {
- const {getByPlaceholder, getByText, getAllByText} = render(
-
- Welcome to React Native!
-
-```
-
-With snapshot testing, you typically first implement your component and then run the snapshot test. The snapshot test then creates a snapshot and saves it to a file in your repo as a reference snapshot. **The file is then committed and checked during code review**. Any future changes to the component render output will change its snapshot, which will cause the test to fail. You then need to update the stored reference snapshot for the test to pass. That change again needs to be committed and reviewed.
-
-Snapshots have several weak points:
-
-- For you as a developer or reviewer, it can be hard to tell whether a change in snapshot is intended or whether it's evidence of a bug. Especially large snapshots can quickly become hard to understand and their added value becomes low.
-- When snapshot is created, at that point it is considered to be correct-even in the case when the rendered output is actually wrong.
-- When a snapshot fails, it's tempting to update it using the `--updateSnapshot` jest option without taking proper care to investigate whether the change is expected. Certain developer discipline is thus needed.
-
-Snapshots themselves do not ensure that your component render logic is correct, they are merely good at guarding against unexpected changes and for checking that the components in the React tree under test receive the expected props (styles and etc.).
-
-We recommend that you only use small snapshots (see [`no-large-snapshots` rule](https://github.com/jest-community/eslint-plugin-jest/blob/master/docs/rules/no-large-snapshots.md)). If you want to test a _change_ between two React component states, use [`snapshot-diff`](https://github.com/jest-community/snapshot-diff). When in doubt, prefer explicit expectations as described in the previous paragraph.
-
-
-
- {this.state.titleText}{'\n'}{'\n'}
-
-
- {this.state.bodyText}
-
-
- );
- }
-}
-
-const styles = StyleSheet.create({
- baseText: {
- fontFamily: 'Cochin',
- marginVertical: 20,
- },
- titleText: {
- fontSize: 20,
- fontWeight: 'bold',
- },
-});
-```
-
-## Nested text
-
-Both Android and iOS allow you to display formatted text by annotating ranges of a string with specific formatting like bold or colored text (`NSAttributedString` on iOS, `SpannableString` on Android). In practice, this is very tedious. For React Native, we decided to use web paradigm for this where you can nest text to achieve the same effect.
-
-```SnackPlayer name=Nested
-import React, { Component } from 'react';
-import { Text } from 'react-native';
-
-export default class BoldAndBeautiful extends Component {
- render() {
- return (
-
- I am bold
-
- and red
-
-
- );
- }
-}
-```
-
-Behind the scenes, React Native converts this to a flat `NSAttributedString` or `SpannableString` that contains the following information:
-
-```jsx
-"I am bold and red"
-0-9: bold
-9-17: bold, red
-```
-
-## Containers
-
-The `` element is unique relative to layout: everything inside is no longer using the flexbox layout but using text layout. This means that elements inside of a `` are no longer rectangles, but wrap when they see the end of the line.
-
-```jsx
-
- First part and
- second part
-
-// Text container: the text will be inline if the space allowed it
-// |First part and second part|
-
-// otherwise, the text will flow as if it was one
-// |First part |
-// |and second |
-// |part |
-
-
- First part and
- second part
-
-// View container: each text is its own block
-// |First part and|
-// |second part |
-
-// otherwise, the text will flow in its own block
-// |First part |
-// |and |
-// |second part|
-```
-
-## Limited Style Inheritance
-
-On the web, the usual way to set a font family and size for the entire document is to take advantage of inherited CSS properties like so:
-
-```css
-html {
- font-family: 'lucida grande', tahoma, verdana, arial, sans-serif;
- font-size: 11px;
- color: #141823;
-}
-```
-
-All elements in the document will inherit this font unless they or one of their parents specifies a new rule.
-
-In React Native, we are more strict about it: **you must wrap all the text nodes inside of a `` component**. You cannot have a text node directly under a ``.
-
-```jsx
-// BAD: will raise exception, can't have a text node as child of a
-
- Some text
-
-
-// GOOD
-
-
- Some text
-
-
-```
-
-You also lose the ability to set up a default font for an entire subtree. Meanwhile, `fontFamily` only accepts a single font name, which is different from `font-family` in CSS. The recommended way to use consistent fonts and sizes across your application is to create a component `MyAppText` that includes them and use this component across your app. You can also use this component to make more specific components like `MyAppHeaderText` for other kinds of text.
-
-```jsx
-
-
- Text styled with the default font for the entire application
-
- Text styled as a header
-
-```
-
-Assuming that `MyAppText` is a component that only renders out its children into a `Text` component with styling, then `MyAppHeaderText` can be defined as follows:
-
-```jsx
-class MyAppHeaderText extends Component {
- render() {
- return (
-
- {this.props.children}
-
- );
- }
-}
-```
-
-Composing `MyAppText` in this way ensures that we get the styles from a top-level component, but leaves us the ability to add / override them in specific use cases.
-
-React Native still has the concept of style inheritance, but limited to text subtrees. In this case, the second part will be both bold and red.
-
-```jsx
-
- I am bold
- and red
-
-```
-
-We believe that this more constrained way to style text will yield better apps:
-
-- (Developer) React components are designed with strong isolation in mind: You should be able to drop a component anywhere in your application, trusting that as long as the props are the same, it will look and behave the same way. Text properties that could inherit from outside of the props would break this isolation.
-
-- (Implementor) The implementation of React Native is also simplified. We do not need to have a `fontFamily` field on every single element, and we do not need to potentially traverse the tree up to the root every time we display a text node. The style inheritance is only encoded inside of the native Text component and doesn't leak to other components or the system itself.
-
----
-
-# Reference
-
-## Props
-
-### `accessible`
-
-When `true`, indicates that the view is an accessibility element. By default, all the touchable elements are accessible.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `accessibilityLabel`
-
-Overrides the text that's read by the screen reader when the user interacts with the element. By default, the label is constructed by traversing all the children and accumulating all the `Text` nodes separated by space.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `accessibilityHint`
-
-An accessibility hint helps users understand what will happen when they perform an action on the accessibility element when that result is not clear from the accessibility label.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `accessibilityRole`
-
-`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).
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `accessibilityState`
-
-Describes the current state of a component to the user of an assistive technology.
-
-See the [Accessibility guide](accessibility.md#accessibilitystate-ios-android) for more information.
-
-| Type | Required |
-| ---------------------------------------------------------------------------------------------- | -------- |
-| object: {disabled: bool, selected: bool, checked: bool or 'mixed', busy: bool, expanded: bool} | No |
-
----
-
-### `adjustsFontSizeToFit`
-
-Specifies whether fonts should be scaled down automatically to fit given style constraints.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `allowFontScaling`
-
-Specifies whether fonts should scale to respect Text Size accessibility settings. The default is `true`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `dataDetectorType`
-
-Determines the types of data converted to clickable URLs in the text element. By default no data types are detected.
-
-You can provide only one type.
-
-Possible values for `dataDetectorType` are:
-
-- `'phoneNumber'`
-- `'link'`
-- `'email'`
-- `'none'`
-- `'all'`
-
-| Type | Required | Platform |
-| --------------------------------------------------- | -------- | -------- |
-| enum('phoneNumber', 'link', 'email', 'none', 'all') | No | Android |
-
----
-
-### `disabled`
-
-Specifies the disabled state of the text view for testing purposes
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `ellipsizeMode`
-
-When `numberOfLines` is set, this prop defines how text will be truncated. `numberOfLines` must be set in conjunction with this prop.
-
-This can be one of the following values:
-
-- `head` - The line is displayed so that the end fits in the container and the missing text at the beginning of the line is indicated by an ellipsis glyph. e.g., "...wxyz"
-- `middle` - The line is displayed so that the beginning and end fit in the container and the missing text in the middle is indicated by an ellipsis glyph. "ab...yz"
-- `tail` - The line is displayed so that the beginning fits in the container and the missing text at the end of the line is indicated by an ellipsis glyph. e.g., "abcd..."
-- `clip` - Lines are not drawn past the edge of the text container.
-
-The default is `tail`.
-
-| Type | Required |
-| -------------------------------------- | -------- |
-| enum('head', 'middle', 'tail', 'clip') | No |
-
----
-
-### `maxFontSizeMultiplier`
-
-Specifies largest possible scale a font can reach when `allowFontScaling` is enabled. Possible values:
-
-- `null/undefined` (default): inherit from the parent node or the global default (0)
-- `0`: no max, ignore parent/global default
-- `>= 1`: sets the `maxFontSizeMultiplier` of this node to this value
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `minimumFontScale`
-
-Specifies smallest possible scale a font can reach when adjustsFontSizeToFit is enabled. (values 0.01-1.0).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | iOS |
-
----
-
-### `nativeID`
-
-Used to locate this view from native code.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `numberOfLines`
-
-Used to truncate the text with an ellipsis after computing the text layout, including line wrapping, such that the total number of lines does not exceed this number.
-
-This prop is commonly used with `ellipsizeMode`.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `onLayout`
-
-Invoked on mount and layout changes with
-
-`{nativeEvent: {layout: {x, y, width, height}}}`
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onLongPress`
-
-This function is called on long press.
-
-e.g., `onLongPress={this.increaseSize}>`
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onMoveShouldSetResponder`
-
-Does this view want to "claim" touch responsiveness? This is called for every touch move on the `View` when it is not the responder.
-
-`View.props.onMoveShouldSetResponder: (event) => [true | false]`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onPress`
-
-This function is called on press.
-
-e.g., `onPress={() => console.log('1st')}`
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onResponderGrant`
-
-The View is now responding for touch events. This is the time to highlight and show the user what is happening.
-
-`View.props.onResponderGrant: (event) => {}`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onResponderMove`
-
-The user is moving their finger.
-
-`View.props.onResponderMove: (event) => {}`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onResponderRelease`
-
-Fired at the end of the touch.
-
-`View.props.onResponderRelease: (event) => {}`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onResponderTerminate`
-
-The responder has been taken from the `View`. Might be taken by other views after a call to `onResponderTerminationRequest`, or might be taken by the OS without asking (e.g., happens with control center/ notification center on iOS)
-
-`View.props.onResponderTerminate: (event) => {}`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onResponderTerminationRequest`
-
-Some other `View` wants to become responder and is asking this `View` to release its responder. Returning `true` allows its release.
-
-`View.props.onResponderTerminationRequest: (event) => {}`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onStartShouldSetResponderCapture`
-
-If a parent `View` wants to prevent a child `View` from becoming responder on a touch start, it should have this handler which returns `true`.
-
-`View.props.onStartShouldSetResponderCapture: (event) => [true | false]`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onTextLayout`
-
-TODO.
-
-### `pressRetentionOffset`
-
-When the scroll view is disabled, this defines how far your touch may move off of the button, before deactivating the button. Once deactivated, try moving it back and you'll see that the button is once again reactivated! Move it back and forth several times while the scroll view is disabled. Ensure you pass in a constant to reduce memory allocations.
-
-| Type | Required |
-| ------------------------------------------------------------------ | -------- |
-| object: {top: number, left: number, bottom: number, right: number} | No |
-
----
-
-### `selectable`
-
-Lets the user select text, to use the native copy and paste functionality.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `selectionColor`
-
-The highlight color of the text.
-
-| Type | Required | Platform |
-| ------------------ | -------- | -------- |
-| [color](colors.md) | No | Android |
-
----
-
-### `style`
-
-| Type | Required |
-| -------------------------------------------------------------------------------- | -------- |
-| [Text Style Props](text-style-props.md), [View Style Props](view-style-props.md) | No |
-
----
-
-### `suppressHighlighting`
-
-When `true`, no visual change is made when text is pressed down. By default, a gray oval highlights the text on press down.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `testID`
-
-Used to locate this view in end-to-end tests.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `textBreakStrategy`
-
-Set text break strategy on Android API Level 23+, possible values are `simple`, `highQuality`, `balanced` The default value is `highQuality`.
-
-| Type | Required | Platform |
-| ----------------------------------------- | -------- | -------- |
-| enum('simple', 'highQuality', 'balanced') | No | Android |
-
-# Known issues
-
-- [react-native#22811](https://github.com/facebook/react-native/issues/22811): Nested Text elements do not support `numberOfLines` attribute
diff --git a/website/versioned_docs/version-0.60/textinput.md b/website/versioned_docs/version-0.60/textinput.md
deleted file mode 100644
index 12e72706564..00000000000
--- a/website/versioned_docs/version-0.60/textinput.md
+++ /dev/null
@@ -1,803 +0,0 @@
----
-id: textinput
-title: TextInput
----
-
-A foundational component for inputting text into the app via a keyboard. Props provide configurability for several features, such as auto-correction, auto-capitalization, placeholder text, and different keyboard types, such as a numeric keypad.
-
-The most basic use case is to plop down a `TextInput` and subscribe to the `onChangeText` events to read the user input. There are also other events, such as `onSubmitEditing` and `onFocus` that can be subscribed to. A minimal example:
-
-```SnackPlayer name=TextInput
-import React, { Component } from 'react';
-import { TextInput } from 'react-native';
-
-export default function UselessTextInput() {
- const [value, onChangeText] = React.useState('Useless Placeholder');
-
- return (
- onChangeText(text)}
- value={value}
- />
- );
-}
-```
-
-Two methods exposed via the native element are .focus() and .blur() that will focus or blur the TextInput programmatically.
-
-Note that some props are only available with `multiline={true/false}`. Additionally, border styles that apply to only one side of the element (e.g., `borderBottomColor`, `borderLeftWidth`, etc.) will not be applied if `multiline=false`. To achieve the same effect, you can wrap your `TextInput` in a `View`:
-
-```SnackPlayer name=TextInput
-import React, { Component } from 'react';
-import { View, TextInput } from 'react-native';
-
-function UselessTextInput(props) {
- return (
-
- onChangeText(text)}
- value={value}
- />
-
- );
-}
-```
-
-`TextInput` has by default a border at the bottom of its view. This border has its padding set by the background image provided by the system, and it cannot be changed. Solutions to avoid this is to either not set height explicitly, case in which the system will take care of displaying the border in the correct position, or to not display the border by setting `underlineColorAndroid` to transparent.
-
-Note that on Android performing text selection in input can change app's activity `windowSoftInputMode` param to `adjustResize`. This may cause issues with components that have position: 'absolute' while keyboard is active. To avoid this behavior either specify `windowSoftInputMode` in AndroidManifest.xml ( https://developer.android.com/guide/topics/manifest/activity-element.html ) or control this param programmatically with native code.
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `allowFontScaling`
-
-Specifies whether fonts should scale to respect Text Size accessibility settings. The default is `true`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `autoCapitalize`
-
-Can tell `TextInput` to automatically capitalize certain characters. This property is not supported by some keyboard types such as `name-phone-pad`.
-
-- `characters`: all characters.
-- `words`: first letter of each word.
-- `sentences`: first letter of each sentence (_default_).
-- `none`: don't auto capitalize anything.
-
-| Type | Required |
-| ------------------------------------------------ | -------- |
-| enum('none', 'sentences', 'words', 'characters') | No |
-
----
-
-### `autoCompleteType`
-
-Specifies autocomplete hints for the system, so it can provide autofill. On Android, the system will always attempt to offer autofill by using heuristics to identify the type of content. To disable autocomplete, set `autoCompleteType` to `off`.
-
-Possible values for `autoCompleteType` are:
-
-- `off`
-- `username`
-- `password`
-- `email`
-- `name`
-- `tel`
-- `street-address`
-- `postal-code`
-- `cc-number`
-- `cc-csc`
-- `cc-exp`
-- `cc-exp-month`
-- `cc-exp-year`
-
-| Type | Required | Platform |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | -------- |
-| enum('off', 'username', 'password', 'email', 'name', 'tel', 'street-address', 'postal-code', 'cc-number', 'cc-csc', 'cc-exp', 'cc-exp-month', 'cc-exp-year') | No | Android |
-
----
-
-### `autoCorrect`
-
-If `false`, disables auto-correct. The default value is `true`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `autoFocus`
-
-If `true`, focuses the input on `componentDidMount`. The default value is `false`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `blurOnSubmit`
-
-If `true`, the text field will blur when submitted. The default value is true for single-line fields and false for multiline fields. Note that for multiline fields, setting `blurOnSubmit` to `true` means that pressing return will blur the field and trigger the `onSubmitEditing` event instead of inserting a newline into the field.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `caretHidden`
-
-If `true`, caret is hidden. The default value is `false`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `clearButtonMode`
-
-When the clear button should appear on the right side of the text view. This property is supported only for single-line TextInput component. The default value is `never`.
-
-| Type | Required | Platform |
-| ---------------------------------------------------------- | -------- | -------- |
-| enum('never', 'while-editing', 'unless-editing', 'always') | No | iOS |
-
----
-
-### `clearTextOnFocus`
-
-If `true`, clears the text field automatically when editing begins.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `contextMenuHidden`
-
-If `true`, context menu is hidden. The default value is `false`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `dataDetectorTypes`
-
-Determines the types of data converted to clickable URLs in the text input. Only valid if `multiline={true}` and `editable={false}`. By default no data types are detected.
-
-You can provide one type or an array of many types.
-
-Possible values for `dataDetectorTypes` are:
-
-- `'phoneNumber'`
-- `'link'`
-- `'address'`
-- `'calendarEvent'`
-- `'none'`
-- `'all'`
-
-| Type | Required | Platform |
-| -------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- |
-| enum('phoneNumber', 'link', 'address', 'calendarEvent', 'none', 'all'), ,array of enum('phoneNumber', 'link', 'address', 'calendarEvent', 'none', 'all') | No | iOS |
-
----
-
-### `defaultValue`
-
-Provides an initial value that will change when the user starts typing. Useful for use-cases where you do not want to deal with listening to events and updating the value prop to keep the controlled state in sync.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `disableFullscreenUI`
-
-When `false`, if there is a small amount of space available around a text input (e.g. landscape orientation on a phone), the OS may choose to have the user edit the text inside of a full screen text input mode. When `true`, this feature is disabled and users will always edit the text directly inside of the text input. Defaults to `false`.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `editable`
-
-If `false`, text is not editable. The default value is `true`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `enablesReturnKeyAutomatically`
-
-If `true`, the keyboard disables the return key when there is no text and automatically enables it when there is text. The default value is `false`.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `importantForAutofill`
-
-Say the system whether the individual fields in your app should be included in a view structure for autofill purposes on Android API Level 26+, possible values are `auto`, `no`, `noExcludeDescendants`, `yes`, `yesExcludeDescendants`. The default value is `auto`.
-
-- `auto`: Let the Android System use its heuristics to determine if the view is important for autofill.
-- `no`: This view isn't important for autofill.
-- `noExcludeDescendants`: This view and its children aren't important for autofill.
-- `yes`: This view is important for autofill.
-- `yesExcludeDescendants`: This view is important for autofill, but its children aren't important for autofill.
-
-| Type | Required | Platform |
-| -------------------------------------------------------------------------- | -------- | -------- |
-| enum('auto', 'no', 'noExcludeDescendants', 'yes', 'yesExcludeDescendants') | No | Android |
-
----
-
-### `inlineImageLeft`
-
-If defined, the provided image resource will be rendered on the left. The image resource must be inside `/android/app/src/main/res/drawable` and referenced like
-
-```
-
-
- );
- }
-}
-```
-
----
-
-# Reference
-
-## Methods
-
-### `show()`
-
-```jsx
-static show(message, duration)
-```
-
----
-
-### `showWithGravity()`
-
-```jsx
-static showWithGravity(message, duration, gravity)
-```
-
----
-
-### `showWithGravityAndOffset()`
-
-```jsx
-static showWithGravityAndOffset(message, duration, gravity, xOffset, yOffset)
-```
-
-## Properties
-
-### `SHORT`
-
-Indicates the duration on the screen.
-
-```jsx
-ToastAndroid.SHORT;
-```
-
----
-
-### `LONG`
-
-Indicates the duration on the screen.
-
-```jsx
-ToastAndroid.LONG;
-```
-
----
-
-### `TOP`
-
-Indicates the position on the screen.
-
-```jsx
-ToastAndroid.TOP;
-```
-
----
-
-### `BOTTOM`
-
-Indicates the position on the screen.
-
-```jsx
-ToastAndroid.BOTTOM;
-```
-
----
-
-### `CENTER`
-
-Indicates the position on the screen.
-
-```jsx
-ToastAndroid.CENTER;
-```
diff --git a/website/versioned_docs/version-0.60/toolbarandroid.md b/website/versioned_docs/version-0.60/toolbarandroid.md
deleted file mode 100644
index ba559eb578b..00000000000
--- a/website/versioned_docs/version-0.60/toolbarandroid.md
+++ /dev/null
@@ -1,194 +0,0 @@
----
-id: toolbarandroid
-title: ToolbarAndroid
----
-
-> **NOTE**: Toolbar Android has been deprecated and removed from the package since React Native v0.61.0. Use [@react-native-community/toolbar-android](https://github.com/react-native-community/toolbar-android) instead.
-
-React component that wraps the Android-only [`Toolbar` widget][0]. A Toolbar can display a logo, navigation icon (e.g. hamburger menu), a title & subtitle and a list of actions. The title and subtitle are expanded so the logo and navigation icons are displayed on the left, title and subtitle in the middle and the actions on the right.
-
-If the toolbar has an only child, it will be displayed between the title and actions.
-
-Although the Toolbar supports remote images for the logo, navigation and action icons, this should only be used in DEV mode where `require('./some_icon.png')` translates into a bundler URL. In release mode you should always use a drawable resource for these icons. Using `require('./some_icon.png')` will do this automatically for you, so as long as you don't explicitly use e.g. `{uri: 'http://...'}`, you will be good.
-
-Example:
-
-```jsx
-render: function() {
- return (
-
-
- );
-},
-```
-
-### Example
-
-```SnackPlayer name=TouchableHighlight
-import React, { Component } from 'react'
-import {
- StyleSheet,
- TouchableHighlight,
- Text,
- View,
-} from 'react-native'
-
-export default class App extends Component {
- constructor(props) {
- super(props)
- this.state = { count: 0 }
- }
-
- onPress = () => {
- this.setState({
- count: this.state.count+1
- })
- }
-
- render() {
- return (
-
-
- Touch Here
-
-
-
- { this.state.count !== 0 ? this.state.count: null}
-
-
-
- )
- }
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- justifyContent: 'center',
- paddingHorizontal: 10
- },
- button: {
- alignItems: 'center',
- backgroundColor: '#DDDDDD',
- padding: 10
- },
- countContainer: {
- alignItems: 'center',
- padding: 10
- },
- countText: {
- color: '#FF00FF'
- }
-})
-```
-
-### Props
-
-- [TouchableWithoutFeedback props...](touchablewithoutfeedback.md#props)
-
-* [`activeOpacity`](touchablehighlight.md#activeopacity)
-* [`onHideUnderlay`](touchablehighlight.md#onhideunderlay)
-* [`onShowUnderlay`](touchablehighlight.md#onshowunderlay)
-* [`style`](touchablehighlight.md#style)
-* [`underlayColor`](touchablehighlight.md#underlaycolor)
-* [`hasTVPreferredFocus`](touchablehighlight.md#hastvpreferredfocus)
-* [`tvParallaxProperties`](touchablehighlight.md#tvparallaxproperties)
-* [`nextFocusDown`](touchablehighlight.md#nextFocusDown)
-* [`nextFocusForward`](touchablehighlight.md#nextFocusForward)
-* [`nextFocusLeft`](touchablehighlight.md#nextFocusLeft)
-* [`nextFocusRight`](touchablehighlight.md#nextFocusRight)
-* [`nextFocusUp`](touchablehighlight.md#nextFocusUp)
-* [`testOnly_pressed`](touchablehighlight.md#testOnly_pressed)
-
----
-
-# Reference
-
-## Props
-
-Inherits [TouchableWithoutFeedback Props](touchablewithoutfeedback.md#props).
-
-### `activeOpacity`
-
-Determines what the opacity of the wrapped view should be when touch is active. The value should be between 0 and 1. Defaults to 0.85. Requires `underlayColor` to be set.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `onHideUnderlay`
-
-Called immediately after the underlay is hidden.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onShowUnderlay`
-
-Called immediately after the underlay is shown.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `style`
-
-| Type | Required |
-| ---------- | -------- |
-| View.style | No |
-
----
-
-### `underlayColor`
-
-The color of the underlay that will show through when the touch is active.
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `hasTVPreferredFocus`
-
-_(Apple TV only)_ TV preferred focus (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `tvParallaxProperties`
-
-_(Apple TV only)_ Object with properties to control Apple TV parallax effects.
-
-enabled: If true, parallax effects are enabled. Defaults to true. shiftDistanceX: Defaults to 2.0. shiftDistanceY: Defaults to 2.0. tiltAngle: Defaults to 0.05. magnification: Defaults to 1.0. pressMagnification: Defaults to 1.0. pressDuration: Defaults to 0.3. pressDelay: Defaults to 0.0.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| object | No | iOS |
-
----
-
-### `nextFocusDown`
-
-TV next focus down (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusForward`
-
-TV next focus forward (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusLeft`
-
-TV next focus left (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusRight`
-
-TV next focus right (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusUp`
-
-TV next focus up (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `testOnly_pressed`
-
-Handy for snapshot tests.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
diff --git a/website/versioned_docs/version-0.60/touchablenativefeedback.md b/website/versioned_docs/version-0.60/touchablenativefeedback.md
deleted file mode 100644
index 719ccf852f2..00000000000
--- a/website/versioned_docs/version-0.60/touchablenativefeedback.md
+++ /dev/null
@@ -1,159 +0,0 @@
----
-id: touchablenativefeedback
-title: TouchableNativeFeedback
----
-
-A wrapper for making views respond properly to touches (Android only). On Android this component uses native state drawable to display touch feedback.
-
-At the moment it only supports having a single View instance as a child node, as it's implemented by replacing that View with another instance of RCTView node with some additional properties set.
-
-Background drawable of native feedback touchable can be customized with `background` property.
-
-Example:
-
-```jsx
-renderButton: function() {
- return (
-
-
- Button
-
-
- );
-},
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [TouchableWithoutFeedback Props](touchablewithoutfeedback.md#props).
-
-### `background`
-
-Determines the type of background drawable that's going to be used to display feedback. It takes an object with `type` property and extra data depending on the `type`. It's recommended to use one of the static methods to generate that dictionary.
-
-| Type | Required |
-| ------------------ | -------- |
-| backgroundPropType | No |
-
----
-
-### `useForeground`
-
-Set to true to add the ripple effect to the foreground of the view, instead of the background. This is useful if one of your child views has a background of its own, or you're e.g. displaying images, and you don't want the ripple to be covered by them.
-
-Check TouchableNativeFeedback.canUseNativeForeground() first, as this is only available on Android 6.0 and above. If you try to use this on older versions you will get a warning and fallback to background.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `hasTVPreferredFocus`
-
-TV preferred focus (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusDown`
-
-TV next focus down (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusForward`
-
-TV next focus forward (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusLeft`
-
-TV next focus left (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusRight`
-
-TV next focus right (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusUp`
-
-TV next focus up (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
-## Methods
-
-### `SelectableBackground()`
-
-```jsx
-static SelectableBackground()
-```
-
-Creates an object that represents android theme's default background for selectable elements (?android:attr/selectableItemBackground).
-
----
-
-### `SelectableBackgroundBorderless()`
-
-```jsx
-static SelectableBackgroundBorderless()
-```
-
-Creates an object that represent android theme's default background for borderless selectable elements (?android:attr/selectableItemBackgroundBorderless). Available on android API level 21+.
-
----
-
-### `Ripple()`
-
-```jsx
-static Ripple(color: string, borderless: boolean)
-```
-
-Creates an object that represents ripple drawable with specified color (as a string). If property `borderless` evaluates to true the ripple will render outside of the view bounds (see native actionbar buttons as an example of that behavior). This background type is available on Android API level 21+.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ---------- | ------- | -------- | ------------------------------------------- |
-| color | string | Yes | The ripple color |
-| borderless | boolean | Yes | If the ripple can render outside its bounds |
-
----
-
-### `canUseNativeForeground()`
-
-```jsx
-static canUseNativeForeground()
-```
diff --git a/website/versioned_docs/version-0.60/touchableopacity.md b/website/versioned_docs/version-0.60/touchableopacity.md
deleted file mode 100644
index 725a6e1f8ab..00000000000
--- a/website/versioned_docs/version-0.60/touchableopacity.md
+++ /dev/null
@@ -1,192 +0,0 @@
----
-id: touchableopacity
-title: TouchableOpacity
----
-
-A wrapper for making views respond properly to touches. On press down, the opacity of the wrapped view is decreased, dimming it.
-
-Opacity is controlled by wrapping the children in an Animated.View, which is added to the view hierarchy. Be aware that this can affect layout.
-
-Example:
-
-```jsx
-renderButton: function() {
- return (
-
-
- );
-},
-```
-
-### Example
-
-```SnackPlayer name=TouchableOpacity
-import React, { Component } from 'react'
-import {
- StyleSheet,
- TouchableOpacity,
- Text,
- View,
-} from 'react-native'
-
-export default class App extends Component {
- constructor(props) {
- super(props)
- this.state = { count: 0 }
- }
-
- onPress = () => {
- this.setState({
- count: this.state.count+1
- })
- }
-
- render() {
- return (
-
-
- Touch Here
-
-
-
- { this.state.count !== 0 ? this.state.count: null}
-
-
-
- )
- }
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- justifyContent: 'center',
- paddingHorizontal: 10
- },
- button: {
- alignItems: 'center',
- backgroundColor: '#DDDDDD',
- padding: 10
- },
- countContainer: {
- alignItems: 'center',
- padding: 10
- },
- countText: {
- color: '#FF00FF'
- }
-})
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [TouchableWithoutFeedback Props](touchablewithoutfeedback.md#props).
-
-### `style`
-
-| Type | Required |
-| ---------- | -------- |
-| View.style | No |
-
----
-
-### `activeOpacity`
-
-Determines what the opacity of the wrapped view should be when touch is active. Defaults to 0.2.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `tvParallaxProperties`
-
-_(Apple TV only)_ Object with properties to control Apple TV parallax effects.
-
-enabled: If true, parallax effects are enabled. Defaults to true. shiftDistanceX: Defaults to 2.0. shiftDistanceY: Defaults to 2.0. tiltAngle: Defaults to 0.05. magnification: Defaults to 1.0. pressMagnification: Defaults to 1.0. pressDuration: Defaults to 0.3. pressDelay: Defaults to 0.0.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| object | No | iOS |
-
----
-
-### `hasTVPreferredFocus`
-
-_(Apple TV only)_ TV preferred focus (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `nextFocusDown`
-
-TV next focus down (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusForward`
-
-TV next focus forward (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusLeft`
-
-TV next focus left (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusRight`
-
-TV next focus right (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `nextFocusUp`
-
-TV next focus up (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
-## Methods
-
-### `setOpacityTo()`
-
-```jsx
-setOpacityTo((value: number), (duration: number));
-```
-
-Animate the touchable to a new opacity.
diff --git a/website/versioned_docs/version-0.60/touchablewithoutfeedback.md b/website/versioned_docs/version-0.60/touchablewithoutfeedback.md
deleted file mode 100644
index 914f8291d1b..00000000000
--- a/website/versioned_docs/version-0.60/touchablewithoutfeedback.md
+++ /dev/null
@@ -1,308 +0,0 @@
----
-id: touchablewithoutfeedback
-title: TouchableWithoutFeedback
----
-
-Do not use unless you have a very good reason. All elements that respond to press should have a visual feedback when touched.
-
-`TouchableWithoutFeedback` supports only one child. If you wish to have several child components, wrap them in a View. Importantly, `TouchableWithoutFeedback` works by cloning its child and applying responder props to it. It is therefore required that any intermediary components pass through those props to the underlying React Native component.
-
-### Usage Example
-
-```jsx
-function MyComponent(props) {
- return (
-
- My Component
-
- );
-}
-
- alert('Pressed!')}>
- ;
-```
-
----
-
-# Reference
-
-## Props
-
-### `accessibilityIgnoresInvertColors`
-
-| Type | Required |
-| ------- | -------- |
-| Boolean | No |
-
----
-
-### `accessible`
-
-When `true`, indicates that the view is an accessibility element. By default, all the touchable elements are accessible.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `accessibilityLabel`
-
-Overrides the text that's read by the screen reader when the user interacts with the element. By default, the label is constructed by traversing all the children and accumulating all the `Text` nodes separated by space.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `accessibilityHint`
-
-An accessibility hint helps users understand what will happen when they perform an action on the accessibility element when that result is not clear from the accessibility label.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `accessibilityRole`
-
-`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).
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `accessibilityState`
-
-Describes the current state of a component to the user of an assistive technology.
-
-See the [Accessibility guide](accessibility.md#accessibilitystate-ios-android) for more information.
-
-| Type | Required |
-| ---------------------------------------------------------------------------------------------- | -------- |
-| object: {disabled: bool, selected: bool, checked: bool or 'mixed', busy: bool, expanded: bool} | No |
-
----
-
-### `accessibilityActions`
-
-Accessibility actions allow an assistive technology to programmatically invoke the actions of a component. The `accessibilityActions` property should contain a list of action objects. Each action object should contain the field name and label.
-
-See the [Accessibility guide](accessibility.md#accessibility-actions) for more information.
-
-| Type | Required |
-| ----- | -------- |
-| array | No |
-
----
-
-### `onAccessibilityAction`
-
-Invoked when the user performs the accessibility actions. The only argument to this function is an event containing the name of the action to perform.
-
-See the [Accessibility guide](accessibility.md#accessibility-actions) for more information.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `delayLongPress`
-
-Delay in ms, from onPressIn, before onLongPress is called.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `delayPressIn`
-
-Delay in ms, from the start of the touch, before onPressIn is called.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `delayPressOut`
-
-Delay in ms, from the release of the touch, before onPressOut is called.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `disabled`
-
-If true, disable all interactions for this component.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `hitSlop`
-
-This defines how far your touch can start away from the button. This is added to `pressRetentionOffset` when moving off of the button. ** NOTE ** The touch area never extends past the parent view bounds and the Z-index of sibling views always takes precedence if a touch hits two overlapping views.
-
-| Type | Required |
-| ------------------------------------------------------------------ | -------- |
-| object: {top: number, left: number, bottom: number, right: number} | No |
-
-### `onBlur`
-
-Invoked when the item loses focus.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onFocus`
-
-Invoked when the item receives focus.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onLayout`
-
-Invoked on mount and layout changes with
-
-`{nativeEvent: {layout: {x, y, width, height}}}`
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onLongPress`
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onPress`
-
-Called when the touch is released, but not if cancelled (e.g. by a scroll that steals the responder lock).
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onPressIn`
-
-Called as soon as the touchable element is pressed and invoked even before onPress. This can be useful when making network requests.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onPressOut`
-
-Called as soon as the touch is released even before onPress.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `pressRetentionOffset`
-
-When the scroll view is disabled, this defines how far your touch may move off of the button, before deactivating the button. Once deactivated, try moving it back and you'll see that the button is once again reactivated! Move it back and forth several times while the scroll view is disabled. Ensure you pass in a constant to reduce memory allocations.
-
-| Type | Required |
-| ------------------------------------------------------------------ | -------- |
-| object: {top: number, left: number, bottom: number, right: number} | No |
-
----
-
-### `nativeID`
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `testID`
-
-Used to locate this view in end-to-end tests.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `touchSoundDisabled`
-
-If true, doesn't play a system sound on touch.
-
-| Type | Required | Platform |
-| ------- | -------- | -------- |
-| Boolean | No | Android |
-
----
-
-## Type Definitions
-
-### Event
-
-| Type |
-| ------ |
-| Object |
diff --git a/website/versioned_docs/version-0.60/transforms.md b/website/versioned_docs/version-0.60/transforms.md
deleted file mode 100644
index a88a4504db1..00000000000
--- a/website/versioned_docs/version-0.60/transforms.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-id: transforms
-title: Transforms
----
-
-# Reference
-
-## Props
-
-### `decomposedMatrix`
-
-> **Deprecated.** Use the [`transform`](transforms.md#transform) prop instead.
-
-| Type | Required |
-| ------------------------ | -------- |
-| DecomposedMatrixPropType | No |
-
----
-
-### `rotation`
-
-| Type | Required |
-| ---------------------------------------------------------------------------- | -------- |
-| deprecatedPropType(ReactPropTypes.number, 'Use the transform prop instead.') | No |
-
----
-
-### `scaleX`
-
-| Type | Required |
-| ---------------------------------------------------------------------------- | -------- |
-| deprecatedPropType(ReactPropTypes.number, 'Use the transform prop instead.') | No |
-
----
-
-### `scaleY`
-
-| Type | Required |
-| ---------------------------------------------------------------------------- | -------- |
-| deprecatedPropType(ReactPropTypes.number, 'Use the transform prop instead.') | No |
-
----
-
-### `transform`
-
-`transform` accepts an array of transformation objects. Each object specifies the property that will be transformed as the key, and the value to use in the transformation. Objects should not be combined. Use a single key/value pair per object.
-
-The rotate transformations require a string so that the transform may be expressed in degrees (deg) or radians (rad). For example:
-
-`transform([{ rotateX: '45deg' }, { rotateZ: '0.785398rad' }])`
-
-The skew transformations require a string so that the transform may be expressed in degrees (deg). For example:
-
-`transform([{ skewX: '45deg' }])`
-
-| Type | Required |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
-| array of object: {perspective: number}, ,object: {rotate: string}, ,object: {rotateX: string}, ,object: {rotateY: string}, ,object: {rotateZ: string}, ,object: {scale: number}, ,object: {scaleX: number}, ,object: {scaleY: number}, ,object: {translateX: number}, ,object: {translateY: number}, ,object: {skewX: string}, ,object: {skewY: string} | No |
-
----
-
-### `transformMatrix`
-
-> **Deprecated.** Use the [`transform`](transforms.md#transform) prop instead.
-
-| Type | Required |
-| ----------------------- | -------- |
-| TransformMatrixPropType | No |
-
----
-
-### `translateX`
-
-| Type | Required |
-| ---------------------------------------------------------------------------- | -------- |
-| deprecatedPropType(ReactPropTypes.number, 'Use the transform prop instead.') | No |
-
----
-
-### `translateY`
-
-| Type | Required |
-| ---------------------------------------------------------------------------- | -------- |
-| deprecatedPropType(ReactPropTypes.number, 'Use the transform prop instead.') | No |
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 1a3fed91335..00000000000
--- a/website/versioned_docs/version-0.60/troubleshooting.md
+++ /dev/null
@@ -1,112 +0,0 @@
----
-id: troubleshooting
-title: 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 [Metro bundler][metro] runs on port 8081. If another process is already using that port, you can either terminate that process, or change the port that the bundler 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
-```
-
-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 bundler 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 `
- Hello, world!
-
- );
- }
-}
-```
-
-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 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 `Hello world! ` or `
`, you use React components. In this case, `` is a [Core Component](intro-react-native-components) that displays some text and `View` is like the `` or `
`.
-
-## 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 basic - 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/typescript.md b/website/versioned_docs/version-0.60/typescript.md
deleted file mode 100644
index 3606ed54915..00000000000
--- a/website/versioned_docs/version-0.60/typescript.md
+++ /dev/null
@@ -1,229 +0,0 @@
----
-id: typescript
-title: Using TypeScript with React Native
----
-
-[TypeScript][ts] is a language which extends JavaScript by adding type definitions, much like [Flow][flow]. While React Native is built in Flow, it supports both TypeScript _and_ Flow by default.
-
-## Getting Started with TypeScript
-
-If you're starting a new project, there are a few different ways to get started. You can use the [TypeScript template][ts-template]:
-
-```shell
-# Template version is specifically for React Native 0.60
-npx react-native init MyTSProject --template react-native-template-typescript@6.2.0
-```
-
-You can use [Expo][expo] which has two TypeScript templates:
-
-```shell
-npm install -g expo-cli
-expo init MyTSProject
-```
-
-Or you could use [Ignite][ignite], which also has a TypeScript template:
-
-```shell
-npm install -g ignite-cli
-ignite new MyTSProject
-```
-
-## Adding TypeScript to an Existing Project
-
-1. Add TypeScript and the types for React Native and Jest to your project.
-
-```shell
-yarn add --dev typescript @types/jest @types/react @types/react-native @types/react-test-renderer
-# or for npm
-npm install --save-dev typescript @types/jest @types/react @types/react-native @types/react-test-renderer
-```
-
-2. Add a TypeScript config file. Create a `tsconfig.json` in the root of your project:
-
-```json
-{
- "compilerOptions": {
- "allowJs": true,
- "allowSyntheticDefaultImports": true,
- "esModuleInterop": true,
- "isolatedModules": true,
- "jsx": "react",
- "lib": ["es6"],
- "moduleResolution": "node",
- "noEmit": true,
- "strict": true,
- "target": "esnext"
- },
- "exclude": [
- "node_modules",
- "babel.config.js",
- "metro.config.js",
- "jest.config.js"
- ]
-}
-```
-
-3. Create a `jest.config.js` file to configure Jest to use TypeScript
-
-```js
-module.exports = {
- preset: 'react-native',
- moduleFileExtensions: [
- 'ts',
- 'tsx',
- 'js',
- 'jsx',
- 'json',
- 'node',
- ],
-};
-```
-
-4. Rename a JavaScript file to be `*.tsx`
-
-5. Run `yarn tsc` to type-check your new TypeScript files.
-
-## How TypeScript and React Native works
-
-Out of the box, transforming your files to JavaScript works via the same [Babel infrastructure][babel] as a non-TypeScript React Native project. We recommend that you use the TypeScript compiler only for type checking. If you have existing TypeScript code being ported to React Native, there are [one or two caveats][babel-7-caveats] to using Babel instead of TypeScript.
-
-## What does React Native + TypeScript look like
-
-You can provide an interface for a React Component's [Props]](props) and [State]](state) via `React.Component` which will provide type-checking and editor auto-completing when working with that component in JSX.
-
-```tsx
-// components/Hello.tsx
-import React from 'react';
-import {Button, StyleSheet, Text, View} from 'react-native';
-
-export interface Props {
- name: string;
- enthusiasmLevel?: number;
-}
-
-const Hello: React.FC = (props) => {
- const [enthusiasmLevel, setEnthusiasmLevel] = React.useState(props.enthusiasmLevel);
-
- const onIncrement = () => setEnthusiasmLevel((enthusiasmLevel || 0) + 1);
- const onDecrement = () => setEnthusiasmLevel((enthusiasmLevel || 0) - 1);
-
- const getExclamationMarks = (numChars: number) => Array(numChars + 1).join('!');
- return (
-
-
- Hello{' '}
- {props.name + getExclamationMarks(enthusiasmLevel || 0)}
-
-
-
-
-
-
-
-
-
-
- );
- }
-}
-
-// styles
-const styles = StyleSheet.create({
- root: {
- alignItems: 'center',
- alignSelf: 'center',
- },
- buttons: {
- flexDirection: 'row',
- minHeight: 70,
- alignItems: 'stretch',
- alignSelf: 'center',
- borderWidth: 5,
- },
- button: {
- flex: 1,
- paddingVertical: 0,
- },
- greeting: {
- color: '#999',
- fontWeight: 'bold',
- },
-});
-```
-
-You can explore the syntax more in the [TypeScript playground][tsplay].
-
-## Where to Find Useful Advice
-
-- [TypeScript Handbook][ts-handbook]
-- [React's documentation on TypeScript][react-ts]
-- [React + TypeScript Cheatsheets][cheats] has a good overview on how to use React with TypeScript
-
-## Using Custom Path Aliases with TypeScript
-
-To use custom path aliases with TypeScript, you need to set the path aliases to work from both Babel and TypeScript. Here's how:
-
-1. Edit your `tsconfig.json` to have your [custom path mappings][path-map]. Set anything in the root of `src` to be available with no preceding path reference, and allow any test file to be accessed by using `test/File.tsx`:
-
-```diff
- "target": "esnext",
-+ "baseUrl": ".",
-+ "paths": {
-+ "*": ["src/*"],
-+ "tests": ["tests/*"]
-+ },
- }
-```
-
-2. Configure the Babel side done by adding a new dependency, [`babel-plugin-module-resolver`][bpmr]:
-
-```shell
-yarn add --dev babel-plugin-module-resolver
-# or
-npm install --save-dev babel-plugin-module-resolver
-```
-
-3. Finally, configure your `babel.config.js` (note that the syntax for your `babel.config.js` is different from your `tsconfig.json`):
-
-```diff
-{
- plugins: [
-+ [
-+ 'module-resolver',
-+ {
-+ root: ['./src'],
-+ extensions: ['.ios.js', '.android.js', '.js', '.ts', '.tsx', '.json'],
-+ alias: {
-+ "test/*": ["./test/"],
-+ }
-+ }
-+ ]
- ]
-}
-```
-
-[react-ts]: https://reactjs.org/docs/static-type-checking.html#typescript
-[ts]: https://www.typescriptlang.org/
-[flow]: https://flow.org
-[ts-template]: https://github.com/react-native-community/react-native-template-typescript
-[babel]: /docs/javascript-environment#javascript-syntax-transformers
-[babel-7-caveats]: https://babeljs.io/docs/en/next/babel-plugin-transform-typescript
-[cheats]: https://github.com/typescript-cheatsheets/react-typescript-cheatsheet#reacttypescript-cheatsheets
-[ts-handbook]: http://www.typescriptlang.org/docs/home.html
-[path-map]: https://www.typescriptlang.org/docs/handbook/module-resolution.html#path-mapping
-[bpmr]: https://github.com/tleunen/babel-plugin-module-resolver
-[expo]: https://expo.io
-[ignite]: https://infinite.red/ignite
-[tsplay]: https://www.typescriptlang.org/play/?strictNullChecks=false&esModuleInterop=true&jsx=3#code/JYWwDg9gTgLgBAJQKYEMDG8BmUIjgcilQ3wG4BYAKFEljgG8AhAVxhggDsAaOAZRgCeAGyS8AFkiQweAFSQAPaXABqwJAHcAvnGy4CRdDAC0HFDGAA3JGSpUFteMA4wkUTOiRwACjjABnBio4YLhTECQALjg-GCgnAHMKShC4JGcxZj9gFD8QABkkKyEAfiiOZhAAI1ckzVtKNE4YuAAJJCEhCCjkQwA6ADEAYQAeHwh-AD44AF44AAowXz8AShmp+iCQxo5mgG00mAysnPzC9p4-KQBRdMzs3IKigF0ZxGIYXszRGDMkBaXegcjvdTkVlklNsFts1OABJDhoIjhZyvOaraZTS4wG6HO4nR7tOZzIF4h5nIRwAA+lLgAAZVgBqOAARnBkLg0PgnAAIkhEUhkfBZmi1tFrrdjmSikSSZLQe0qTT6XAjCy2ZR2Zy4PFrvI0EIUCAzMBOABZFBQADWAWF5RAgzEFr8ZQq1Sg6KmAEEoFAUAI5naHU64EzWb0AFYQJxzfAAQnw6pSRBgzCgHHm7JSw1UGmighE03oMWESD8vRwEBgmgmmZCwzkijzJcLxZEZfiRCkCWrtZSwTaHQg9HwBDqyT7E-oi3GZbCniZOuxeoNRvMZot1uJEpBBIp1LpyzHE+CwwA9A2YDWNeOJ9m1OomwWi-nS71Kqx2Dsezfjyecw-WyQFsXzLd82E4b9fyzFhwI4XsoPMGACwAIiMZD4N-TgfFLPxCx5PkkQOI8oIndA0Bw4BKmAIRgEEPIUGqIRpmQgATAiBQOdCfxIqEIE6KBmKIFiuJ4uBTyvUSz3-K8MLrf9HyA58S1Aj8IIknjhhgz9ZInRCUIZETRJCLCiD8XD6DhBFCOcYijLgMiKKomi6IY9pmKcflBUMuzGn45jKiEZgkG8qDxJ0uApPvdTb1PaT4MijRorgRMQjHMcqFPU8FL8KgtUAm0+BfcRJA+flfjmDYfwrGAokq38UBo+IOFhFwQGdAhyOcVx8C4eCGuAJreHaTAonwTqXCgHr2U0XqfzAz92rqidMBEeRuWAIgMBNDhRpwdQpu4kIQCcNoBrEGq4AAdlpWb6sa5rWva-AYmTNAxAOu6Bo4IahBGjqDm627j0qaA2KgAB1YAWMOKIAFYgeCGb2XmzhavglaFCiZkEb7MAUBYliEmUVxzDQBqohu6acY7EqEjRw7eP40aAGIAE52Y+49ME4GBwaQM6LvwEGhBYznEdmzRwSAA
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 adcba556758..00000000000
--- a/website/versioned_docs/version-0.60/upgrading.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-id: upgrading
-title: Upgrading to new React Native versions
----
-
-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 straightforward 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:
-
-```shell
-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:
-
-```shell
-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`:
-
-```shell
-# {{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 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:
-
-```shell
-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 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:
-
-```shell
-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/usewindowdimensions.md b/website/versioned_docs/version-0.60/usewindowdimensions.md
deleted file mode 100644
index 1b3768df476..00000000000
--- a/website/versioned_docs/version-0.60/usewindowdimensions.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-id: usewindowdimensions
-title: useWindowDimensions
----
-
-```jsx
-import {useWindowDimensions} from 'react-native';
-```
-
-`useWindowDimensions` automatically updates `width` and `height` values when screen size changes. You can get your application window's width and height like so:
-
-```jsx
-const windowWidth = useWindowDimensions().width;
-const windowHeight = useWindowDimensions().height;
-```
-
-## Example
-
-```SnackPlayer name=useWindowDimensions&supportedPlatforms=ios,android
-import React from "react";
-import { View, StyleSheet, Text, useWindowDimensions } from "react-native";
-
-const App = () => {
- const window = useWindowDimensions();
- return (
-
- {`Window Dimensions: height - ${window.height}, width - ${window.width}`}
-
- );
-}
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- justifyContent: "center",
- alignItems: "center"
- }
-});
-
-export default App;
-```
-
-- The [useDimensions](https://github.com/react-native-community/react-native-hooks#usedimensions) hook from the community [React Native hooks](https://github.com/react-native-community/react-native-hooks) library aims to make handling screen/window size changes easier to work with.
-- [React Native Responsive Dimensions](https://github.com/DaniAkash/react-native-responsive-dimensions) also comes with responsive hooks.
-
-## Properties
-
-### `fontScale`
-
-The scale of the font currently used. Some operating systems allow users to scale their font sizes larger or smaller for reading comfort. This property will let you know what is in effect.
-
-```jsx
-useWindowDimensions().fontScale;
-```
-
-### `height`
-
-The height in pixels of the window or screen your app occupies.
-
-```jsx
-useWindowDimensions().height;
-```
-
-### `scale`
-
-The pixel ratio of the device your app is running on.
-
-```jsx
-useWindowDimensions().scale;
-```
-
-> A value of `1` indicates PPI/DPI of 96 (76 on some platforms). `2` indicates a Retina or high DPI display.
-
-### `width`
-
-The width in pixels of the window or screen your app occupies.
-
-```jsx
-useWindowDimensions().width;
-```
diff --git a/website/versioned_docs/version-0.60/using-a-listview.md b/website/versioned_docs/version-0.60/using-a-listview.md
deleted file mode 100644
index bc45a643189..00000000000
--- a/website/versioned_docs/version-0.60/using-a-listview.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-id: using-a-listview
-title: Using List Views
----
-
-React Native provides a suite of components for presenting lists of data. Generally, you'll want to use either [FlatList](flatlist.md) or [SectionList](sectionlist.md).
-
-The `FlatList` component displays a scrolling list of changing, but similarly structured, data. `FlatList` works well for long lists of data, where the number of items might change over time. Unlike the more generic [`ScrollView`](using-a-scrollview.md), the `FlatList` only renders elements that are currently showing on the screen, not all the elements at once.
-
-The `FlatList` component requires two props: `data` and `renderItem`. `data` is the source of information for the list. `renderItem` takes one item from the source and returns a formatted component to render.
-
-This example creates a basic `FlatList` of hardcoded data. Each item in the `data` props is rendered as a `Text` component. The `FlatListBasics` component then renders the `FlatList` and all `Text` components.
-
-```SnackPlayer name=FlatList%20Basics
-import React, { Component } from 'react';
-import { FlatList, StyleSheet, Text, View } from 'react-native';
-
-export default class FlatListBasics extends Component {
- render() {
- return (
-
- {item.key} }
- />
-
- );
- }
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- paddingTop: 22
- },
- item: {
- padding: 10,
- fontSize: 18,
- height: 44,
- },
-})
-```
-
-If you want to render a set of data broken into logical sections, maybe with section headers, similar to `UITableView`s on iOS, then a [SectionList](sectionlist.md) is the way to go.
-
-```SnackPlayer name=SectionList%20Basics
-import React, { Component } from 'react';
-import { SectionList, StyleSheet, Text, View } from 'react-native';
-
-export default class SectionListBasics extends Component {
- render() {
- return (
-
- {item} }
- renderSectionHeader={({section}) => {section.title} }
- keyExtractor={(item, index) => index}
- />
-
- );
- }
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- paddingTop: 22
- },
- sectionHeader: {
- paddingTop: 2,
- paddingLeft: 10,
- paddingRight: 10,
- paddingBottom: 2,
- fontSize: 14,
- fontWeight: 'bold',
- backgroundColor: 'rgba(247,247,247,1.0)',
- },
- item: {
- padding: 10,
- fontSize: 18,
- height: 44,
- },
-})
-```
-
-One of the most common uses for a list view is displaying data that you fetch from a server. To do that, you will need to [learn about networking in React Native](network.md).
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 ebaffa6f9e9..00000000000
--- a/website/versioned_docs/version-0.60/using-a-scrollview.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-id: using-a-scrollview
-title: Using a ScrollView
----
-
-The [ScrollView](scrollview.md) is a generic scrolling container that can contain 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 (
-
- Scroll me plz
- If you like
- Scrolling down
- What's the best
- Framework around?
- React Native
-
- );
- }
-}
-```
-
-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.
diff --git a/website/versioned_docs/version-0.60/vibration.md b/website/versioned_docs/version-0.60/vibration.md
deleted file mode 100644
index 6f351801a40..00000000000
--- a/website/versioned_docs/version-0.60/vibration.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: vibration
-title: Vibration
----
-
-The Vibration API is exposed at `Vibration.vibrate()`. The vibration is synchronous so this method will return immediately.
-
-There will be no effect on devices that do not support Vibration, eg. the simulator.
-
-**Note for Android:** add `, repeat: boolean)
-```
-
-Trigger a vibration with specified `pattern`.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------- | ------------------------- | -------- | ---------------------------------------------------------------------------- |
-| pattern | `number or Array` | Yes | Vibration pattern, accept a number or an array of numbers. Default to 400ms. |
-| repeat | boolean | No | Repeat vibration pattern until cancel(), default to false. |
-
----
-
-### `cancel()`
-
-```jsx
-Vibration.cancel();
-```
-
-Stop vibration.
-
-```
-Vibration.cancel()
-```
diff --git a/website/versioned_docs/version-0.60/vibrationios.md b/website/versioned_docs/version-0.60/vibrationios.md
deleted file mode 100644
index 7a954246c05..00000000000
--- a/website/versioned_docs/version-0.60/vibrationios.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-id: vibrationios
-title: VibrationIOS
----
-
-NOTE: `VibrationIOS` is being deprecated. Use `Vibration` instead.
-
-The Vibration API is exposed at `VibrationIOS.vibrate()`. On iOS, calling this function will trigger a one second vibration. The vibration is synchronous so this method will return immediately.
-
-There will be no effect on devices that do not support Vibration, eg. the iOS simulator.
-
-Vibration patterns are currently unsupported.
-
-### Methods
-
-- [`vibrate`](vibrationios.md#vibrate)
-
----
-
-# Reference
-
-## Methods
-
-### `vibrate()`
-
-```jsx
-static vibrate()
-```
-
-@deprecated
diff --git a/website/versioned_docs/version-0.60/view-style-props.md b/website/versioned_docs/version-0.60/view-style-props.md
deleted file mode 100644
index abf36d91331..00000000000
--- a/website/versioned_docs/version-0.60/view-style-props.md
+++ /dev/null
@@ -1,218 +0,0 @@
----
-id: view-style-props
-title: View Style Props
----
-
-# Reference
-
-## Props
-
-### `borderRightColor`
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `backfaceVisibility`
-
-| Type | Required |
-| ------------------------- | -------- |
-| enum('visible', 'hidden') | No |
-
----
-
-### `borderBottomColor`
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `borderBottomEndRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderBottomLeftRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderBottomRightRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderBottomStartRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderBottomWidth`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderColor`
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `borderEndColor`
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `borderLeftColor`
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `borderLeftWidth`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderRadius`
-
-If the rounded border is not visible, try applying `overflow: 'hidden'` as well.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `backgroundColor`
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `borderRightWidth`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderStartColor`
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `borderStyle`
-
-| Type | Required |
-| --------------------------------- | -------- |
-| enum('solid', 'dotted', 'dashed') | No |
-
----
-
-### `borderTopColor`
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `borderTopEndRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderTopLeftRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderTopRightRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderTopStartRadius`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderTopWidth`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `borderWidth`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `opacity`
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `elevation`
-
-(Android-only) Sets the elevation of a view, using Android's underlying [elevation API](https://developer.android.com/training/material/shadows-clipping.html#Elevation). This adds a drop shadow to the item and affects z-order for overlapping views. Only supported on Android 5.0+, has no effect on earlier versions.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
diff --git a/website/versioned_docs/version-0.60/view.md b/website/versioned_docs/version-0.60/view.md
deleted file mode 100644
index c9bcd7684c0..00000000000
--- a/website/versioned_docs/version-0.60/view.md
+++ /dev/null
@@ -1,603 +0,0 @@
----
-id: view
-title: View
----
-
-The most fundamental component for building a UI, `View` is a container that supports layout with [flexbox](flexbox.md), [style](style.md), [some touch handling](handling-touches.md), and [accessibility](accessibility.md) controls. `View` maps directly to the native view equivalent on whatever platform React Native is running on, whether that is a `UIView`, ``, `android.view`, etc.
-
-`View` is designed to be nested inside other views and can have 0 to many children of any type.
-
-This example creates a `View` that wraps two colored boxes and a text component in a row with padding.
-
-```jsx
-class ViewColoredBoxesWithText extends Component {
- render() {
- return (
-
- Hello World!
-
- );
- }
-}
-```
-
-> `View`s are designed to be used with [`StyleSheet`](style.md) for clarity and performance, although inline styles are also supported.
-
-### Synthetic Touch Events
-
-For `View` responder props (e.g., `onResponderMove`), the synthetic touch event passed to them are of the following form:
-
-- `nativeEvent`
- - `changedTouches` - Array of all touch events that have changed since the last event.
- - `identifier` - The ID of the touch.
- - `locationX` - The X position of the touch, relative to the element.
- - `locationY` - The Y position of the touch, relative to the element.
- - `pageX` - The X position of the touch, relative to the root element.
- - `pageY` - The Y position of the touch, relative to the root element.
- - `target` - The node id of the element receiving the touch event.
- - `timestamp` - A time identifier for the touch, useful for velocity calculation.
- - `touches` - Array of all current touches on the screen.
-
----
-
-# Reference
-
-## Props
-
-### `onStartShouldSetResponder`
-
-Does this view want to become responder on the start of a touch?
-
-`View.props.onStartShouldSetResponder: (event) => [true | false]`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `accessible`
-
-When `true`, indicates that the view is an accessibility element. By default, all the touchable elements are accessible.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `accessibilityLabel`
-
-Overrides the text that's read by the screen reader when the user interacts with the element. By default, the label is constructed by traversing all the children and accumulating all the `Text` nodes separated by space.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `accessibilityHint`
-
-An accessibility hint helps users understand what will happen when they perform an action on the accessibility element when that result is not clear from the accessibility label.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `accessibilityRole`
-
-`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).
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `accessibilityState`
-
-Describes the current state of a component to the user of an assistive technology.
-
-See the [Accessibility guide](accessibility.md#accessibilitystate-ios-android) for more information.
-
-| Type | Required |
-| ---------------------------------------------------------------------------------------------- | -------- |
-| object: {disabled: bool, selected: bool, checked: bool or 'mixed', busy: bool, expanded: bool} | No |
-
----
-
-### `accessibilityValue`
-
-Represents the current value of a component. It can be a textual description of a component's value, or for range-based components, such as sliders and progress bars, it contains range information (minimum, current, and maximum).
-
-See the [Accessibility guide](accessibility.md#accessibilityvalue-ios-android) for more information.
-
-| Type | Required |
-| ------------------------------------------------------------- | -------- |
-| object: {min: number, max: number, now: number, text: string} | No |
-
----
-
-### `accessibilityActions`
-
-Accessibility actions allow an assistive technology to programmatically invoke the actions of a component. The `accessibilityActions` property should contain a list of action objects. Each action object should contain the field name and label.
-
-See the [Accessibility guide](accessibility.md#accessibility-actions) for more information.
-
-| Type | Required |
-| ----- | -------- |
-| array | No |
-
----
-
-### `onAccessibilityAction`
-
-Invoked when the user performs the accessibility actions. The only argument to this function is an event containing the name of the action to perform.
-
-See the [Accessibility guide](accessibility.md#accessibility-actions) for more information.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onAccessibilityTap`
-
-When `accessible` is true, the system will try to invoke this function when the user performs accessibility tap gesture.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onMagicTap`
-
-When `accessible` is `true`, the system will invoke this function when the user performs the magic tap gesture.
-
-| Type | Required | Platform |
-| -------- | -------- | -------- |
-| function | No | iOS |
-
----
-
-### `onAccessibilityEscape`
-
-When `accessible` is `true`, the system will invoke this function when the user performs the escape gesture.
-
-| Type | Required | Platform |
-| -------- | -------- | -------- |
-| function | No | iOS |
-
----
-
-### `accessibilityViewIsModal`
-
-A value indicating whether VoiceOver should ignore the elements within views that are siblings of the receiver. Default is `false`.
-
-See the [Accessibility guide](accessibility.md#accessibilityviewismodal-ios) for more information.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `accessibilityElementsHidden`
-
-A value indicating whether the accessibility elements contained within this accessibility element are hidden. Default is `false`.
-
-See the [Accessibility guide](accessibility.md#accessibilityelementshidden-ios) for more information.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `accessibilityIgnoresInvertColors`
-
-A value indicating this view should or should not be inverted when color inversion is turned on. A value of `true` will tell the view to not be inverted even if color inversion is turned on.
-
-See the [Accessibility guide](accessibility.md#accessibilityignoresinvertcolors) for more information.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `accessibilityLiveRegion`
-
-Indicates to accessibility services whether the user should be notified when this view changes. Works for Android API >= 19 only. Possible values:
-
-- `'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.
-
-See the [Android `View` docs](http://developer.android.com/reference/android/view/View.html#attr_android:accessibilityLiveRegion) for reference.
-
-| Type | Required | Platform |
-| ----------------------------------- | -------- | -------- |
-| enum('none', 'polite', 'assertive') | No | Android |
-
----
-
-### `importantForAccessibility`
-
-Controls how view is important for accessibility which is if it fires accessibility events and if it is reported to accessibility services that query the screen. Works for Android only.
-
-Possible values:
-
-- `'auto'` - The system determines whether the view is important for accessibility - default (recommended).
-- `'yes'` - The view is important for accessibility.
-- `'no'` - The view is not important for accessibility.
-- `'no-hide-descendants'` - The view is not important for accessibility, nor are any of its descendant views.
-
-See the [Android `importantForAccessibility` docs](http://developer.android.com/reference/android/R.attr.html#importantForAccessibility) for reference.
-
-| Type | Required | Platform |
-| ------------------------------------------------ | -------- | -------- |
-| enum('auto', 'yes', 'no', 'no-hide-descendants') | No | Android |
-
----
-
-### `hitSlop`
-
-This defines how far a touch event can start away from the view. Typical interface guidelines recommend touch targets that are at least 30 - 40 points/density-independent pixels.
-
-For example, if a touchable view has a height of 20 the touchable height can be extended to 40 with `hitSlop={{top: 10, bottom: 10, left: 0, right: 0}}`
-
-> The touch area never extends past the parent view bounds and the Z-index of sibling views always takes precedence if a touch hits two overlapping views.
-
-| Type | Required |
-| ------------------------------------------------------------------ | -------- |
-| object: {top: number, left: number, bottom: number, right: number} | No |
-
----
-
-### `nativeID`
-
-Used to locate this view from native classes.
-
-> This disables the 'layout-only view removal' optimization for this view!
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `onLayout`
-
-Invoked on mount and layout changes with:
-
-`{nativeEvent: { layout: {x, y, width, height}}}`
-
-This event is fired immediately once the layout has been calculated, but the new layout may not yet be reflected on the screen at the time the event is received, especially if a layout animation is in progress.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onMoveShouldSetResponder`
-
-Does this view want to "claim" touch responsiveness? This is called for every touch move on the `View` when it is not the responder.
-
-`View.props.onMoveShouldSetResponder: (event) => [true | false]`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onMoveShouldSetResponderCapture`
-
-If a parent `View` wants to prevent a child `View` from becoming responder on a move, it should have this handler which returns `true`.
-
-`View.props.onMoveShouldSetResponderCapture: (event) => [true | false]`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onResponderGrant`
-
-The View is now responding for touch events. This is the time to highlight and show the user what is happening.
-
-`View.props.onResponderGrant: (event) => {}`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onResponderMove`
-
-The user is moving their finger.
-
-`View.props.onResponderMove: (event) => {}`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onResponderReject`
-
-Another responder is already active and will not release it to that `View` asking to be the responder.
-
-`View.props.onResponderReject: (event) => {}`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onResponderRelease`
-
-Fired at the end of the touch.
-
-`View.props.onResponderRelease: (event) => {}`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onResponderTerminate`
-
-The responder has been taken from the `View`. Might be taken by other views after a call to `onResponderTerminationRequest`, or might be taken by the OS without asking (e.g., happens with control center/ notification center on iOS)
-
-`View.props.onResponderTerminate: (event) => {}`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onResponderTerminationRequest`
-
-Some other `View` wants to become responder and is asking this `View` to release its responder. Returning `true` allows its release.
-
-`View.props.onResponderTerminationRequest: (event) => {}`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onStartShouldSetResponderCapture`
-
-If a parent `View` wants to prevent a child `View` from becoming responder on a touch start, it should have this handler which returns `true`.
-
-`View.props.onStartShouldSetResponderCapture: (event) => [true | false]`, where `event` is a synthetic touch event as described above.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `pointerEvents`
-
-Controls whether the `View` can be the target of touch events.
-
-- `'auto'`: The View can be the target of touch events.
-- `'none'`: The View is never the target of touch events.
-- `'box-none'`: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
-
-```
-.box-none {
- pointer-events: none;
-}
-.box-none * {
- pointer-events: auto;
-}
-```
-
-- `'box-only'`: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
-
-```
-.box-only {
- pointer-events: auto;
-}
-.box-only * {
- pointer-events: none;
-}
-```
-
-> Since `pointerEvents` does not affect layout/appearance, and we are already deviating from the spec by adding additional modes, we opt to not include `pointerEvents` on `style`. On some platforms, we would need to implement it as a `className` anyways. Using `style` or not is an implementation detail of the platform.
-
-| Type | Required |
-| -------------------------------------------- | -------- |
-| enum('box-none', 'none', 'box-only', 'auto') | No |
-
----
-
-### `removeClippedSubviews`
-
-This is a reserved performance property exposed by `RCTView` and is useful for scrolling content when there are many subviews, most of which are offscreen. For this property to be effective, it must be applied to a view that contains many subviews that extend outside its bound. The subviews must also have `overflow: hidden`, as should the containing view (or one of its superviews).
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `style`
-
-| Type | Required |
-| ---------------------------------- | -------- |
-| [view styles](view-style-props.md) | No |
-
----
-
-### `testID`
-
-Used to locate this view in end-to-end tests.
-
-> This disables the 'layout-only view removal' optimization for this view!
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `collapsable`
-
-Views that are only used to layout their children or otherwise don't draw anything may be automatically removed from the native hierarchy as an optimization. Set this property to `false` to disable this optimization and ensure that this `View` exists in the native view hierarchy.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `needsOffscreenAlphaCompositing`
-
-Whether this `View` needs to rendered offscreen and composited with an alpha in order to preserve 100% correct colors and blending behavior. The default (`false`) falls back to drawing the component and its children with an alpha applied to the paint used to draw each element instead of rendering the full component offscreen and compositing it back with an alpha value. This default may be noticeable and undesired in the case where the `View` you are setting an opacity on has multiple overlapping elements (e.g. multiple overlapping `View`s, or text and a background).
-
-Rendering offscreen to preserve correct alpha behavior is extremely expensive and hard to debug for non-native developers, which is why it is not turned on by default. If you do need to enable this property for an animation, consider combining it with renderToHardwareTextureAndroid if the view **contents** are static (i.e. it doesn't need to be redrawn each frame). If that property is enabled, this View will be rendered off-screen once, saved in a hardware texture, and then composited onto the screen with an alpha each frame without having to switch rendering targets on the GPU.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `renderToHardwareTextureAndroid`
-
-Whether this `View` should render itself (and all of its children) into a single hardware texture on the GPU.
-
-On Android, this is useful for animations and interactions that only modify opacity, rotation, translation, and/or scale: in those cases, the view doesn't have to be redrawn and display lists don't need to be re-executed. The texture can be re-used and re-composited with different parameters. The downside is that this can use up limited video memory, so this prop should be set back to false at the end of the interaction/animation.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `shouldRasterizeIOS`
-
-Whether this `View` should be rendered as a bitmap before compositing.
-
-On iOS, this is useful for animations and interactions that do not modify this component's dimensions nor its children; for example, when translating the position of a static view, rasterization allows the renderer to reuse a cached bitmap of a static view and quickly composite it during each frame.
-
-Rasterization incurs an off-screen drawing pass and the bitmap consumes memory. Test and measure when using this property.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `nextFocusDown`
-
-Designates the next view to receive focus when the user navigates down. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusDown).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusForward`
-
-Designates the next view to receive focus when the user navigates forward. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusForward).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusLeft`
-
-Designates the next view to receive focus when the user navigates left. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusLeft).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusRight`
-
-Designates the next view to receive focus when the user navigates right. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusRight).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusUp`
-
-Designates the next view to receive focus when the user navigates up. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusUp).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `clickable`
-
-Determines whether this `View` is clickable or tappable for accessibility hints.
-
-| Type | Required | Platform |
-| ------- | -------- | -------- |
-| boolean | No | Android |
diff --git a/website/versioned_docs/version-0.60/viewpagerandroid.md b/website/versioned_docs/version-0.60/viewpagerandroid.md
deleted file mode 100644
index 0bd803b9d68..00000000000
--- a/website/versioned_docs/version-0.60/viewpagerandroid.md
+++ /dev/null
@@ -1,180 +0,0 @@
----
-id: viewpagerandroid
-title: '🚧 ViewPagerAndroid'
----
-
-> **Deprecated.** Use [react-native-community/react-native-viewpager](https://github.com/react-native-community/react-native-viewpager) instead.
-
-Container that allows to flip left and right between child views. Each child view of the `ViewPagerAndroid` will be treated as a separate page and will be stretched to fill the `ViewPagerAndroid`.
-
-It is important all children are `
`s and not composite components. You can set style properties like `padding` or `backgroundColor` for each child. It is also important that each child have a `key` prop.
-
-Example:
-
-```jsx
-render() {
- return (
-
-
- First page
-
-
- Second page
-
-
- );
-}
-
-...
-
-const styles = {
- ...
- viewPager: {
- flex: 1
- },
- pageStyle: {
- alignItems: 'center',
- padding: 20,
- }
-}
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `initialPage`
-
-Index of initial page that should be selected. Use `setPage` method to update the page, and `onPageSelected` to monitor page changes
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `keyboardDismissMode`
-
-Determines whether the keyboard gets dismissed in response to a drag.
-
-- 'none' (the default), drags do not dismiss the keyboard.
-- 'on-drag', the keyboard is dismissed when a drag begins.
-
-| Type | Required |
-| ----------------------- | -------- |
-| enum('none', 'on-drag') | No |
-
----
-
-### `onPageScroll`
-
-Executed when transitioning between pages (either because of animation for the requested page change or when user is swiping/dragging between pages) The `event.nativeEvent` object for this callback will carry following data:
-
-- position - index of first page from the left that is currently visible
-- offset - value from range [0, 1] describing stage between page transitions. Value x means that (1 - x) fraction of the page at "position" index is visible, and x fraction of the next page is visible.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onPageScrollStateChanged`
-
-Function called when the page scrolling state has changed. The page scrolling state can be in 3 states:
-
-- idle, meaning there is no interaction with the page scroller happening at the time
-- dragging, meaning there is currently an interaction with the page scroller
-- settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onPageSelected`
-
-This callback will be called once ViewPager finish navigating to selected page (when user swipes between pages). The `event.nativeEvent` object passed to this callback will have following fields:
-
-- position - index of page that has been selected
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `pageMargin`
-
-Blank space to show between pages. This is only visible while scrolling, pages are still edge-to-edge.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `peekEnabled`
-
-Whether enable showing peekFraction or not. If this is true, the preview of last and next page will show in current screen. Defaults to false.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `scrollEnabled`
-
-When false, the content does not scroll. The default value is true.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `setPage`
-
-A helper function to scroll to a specific page in the ViewPager. The transition between pages will be animated.
-
-- position - index of page that will be selected
-
-| Type | Required |
-| ------ | -------- |
-| Number | Yes |
-
----
-
-### `setPageWithoutAnimation`
-
-A helper function to scroll to a specific page in the ViewPager. The transition between pages will _not_ be animated.
-
-- position - index of page that will be selected
-
-| Type | Required |
-| ------ | -------- |
-| Number | Yes |
-
-## Type Definitions
-
-### ViewPagerScrollState
-
-| Type |
-| ------ |
-| \$Enum |
-
-**Constants:**
-
-| Value | Description |
-| -------- | ----------- |
-| idle | |
-| dragging | |
-| settling | |
diff --git a/website/versioned_docs/version-0.60/virtualizedlist.md b/website/versioned_docs/version-0.60/virtualizedlist.md
deleted file mode 100644
index df8ded9e5ce..00000000000
--- a/website/versioned_docs/version-0.60/virtualizedlist.md
+++ /dev/null
@@ -1,511 +0,0 @@
----
-id: virtualizedlist
-title: VirtualizedList
----
-
-Base implementation for the more convenient [``](flatlist.md) and [``](sectionlist.md) components, which are also better documented. In general, this should only really be used if you need more flexibility than [`FlatList`](flatlist.md) provides, e.g. for use with immutable data instead of plain arrays.
-
-Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
-
-Some caveats:
-
-- Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.
-- This is a `PureComponent` which means that it will not re-render if `props` remain shallow-equal. Make sure that everything your `renderItem` function depends on is passed as a prop (e.g. `extraData`) that is not `===` after updates, otherwise your UI may not update on changes. This includes the `data` prop and parent component state.
-- In order to constrain memory and enable smooth scrolling, content is rendered asynchronously offscreen. This means it's possible to scroll faster than the fill rate and momentarily see blank content. This is a tradeoff that can be adjusted to suit the needs of each application, and we are working on improving it behind the scenes.
-- By default, the list looks for a `key` prop on each item and uses that for the React key. Alternatively, you can provide a custom `keyExtractor` prop.
-
----
-
-# Reference
-
-## Props
-
-Inherits [ScrollView Props](scrollview.md#props).
-
-### `renderItem`
-
-```jsx
-(info: any) => ?React.Element
-```
-
-Takes an item from `data` and renders it into the list
-
-| Type | Required |
-| -------- | -------- |
-| function | Yes |
-
----
-
-### `data`
-
-The default accessor functions assume this is an array of objects with shape `{key: string}` but you can override `getItem`, `getItemCount`, and `keyExtractor` to handle any type of index-based data.
-
-| Type | Required |
-| ---- | -------- |
-| any | Yes |
-
----
-
-### `getItem`
-
-```jsx
-(data: any, index: number) => object;
-```
-
-A generic accessor for extracting an item from any sort of data blob.
-
-| Type | Required |
-| -------- | -------- |
-| function | Yes |
-
----
-
-### `getItemCount`
-
-```jsx
-(data: any) => number;
-```
-
-Determines how many items are in the data blob.
-
-| Type | Required |
-| -------- | -------- |
-| function | Yes |
-
----
-
-### `debug`
-
-`debug` will turn on extra logging and visual overlays to aid with debugging both usage and implementation, but with a significant perf hit.
-
-| Type | Required |
-| ------- | -------- |
-| boolean | No |
-
----
-
-### `extraData`
-
-A marker property for telling the list to re-render (since it implements `PureComponent`). If any of your `renderItem`, Header, Footer, etc. functions depend on anything outside of the `data` prop, stick it here and treat it immutably.
-
-| Type | Required |
-| ---- | -------- |
-| any | No |
-
----
-
-### `getItemLayout`
-
-```jsx
-(
- data: any,
- index: number,
- ) => {length: number, offset: number, index: number}
-```
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `initialScrollIndex`
-
-Instead of starting at the top with the first item, start at `initialScrollIndex`. This disables the "scroll to top" optimization that keeps the first `initialNumToRender` items always rendered and immediately renders the items starting at this initial index. Requires `getItemLayout` to be implemented.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `inverted`
-
-Reverses the direction of scroll. Uses scale transforms of -1.
-
-| Type | Required |
-| ------- | -------- |
-| boolean | No |
-
----
-
-### `CellRendererComponent`
-
-Each cell is rendered using this element. Can be a React Component Class,or a render function. Defaults to using [`View`](view.md).
-
-| Type | Required |
-| ------------------- | -------- |
-| component, function | No |
-
----
-
-### `listKey`
-
-A unique identifier for this list. If there are multiple VirtualizedLists at the same level of nesting within another VirtualizedList, this key is necessary for virtualization to work properly.
-
-| Type | Required |
-| ------ | -------- |
-| string | True |
-
----
-
-### `ListEmptyComponent`
-
-Rendered when the list is empty. Can be a React Component (e.g. `SomeComponent`), or a React element (e.g. `` component built internally. The onRefresh and refreshing props are also ignored. Only works for vertical VirtualizedList.
-
-| Type | Required |
-| ------- | -------- |
-| element | No |
-
----
-
-### `removeClippedSubviews`
-
-This may improve scroll performance for large lists.
-
-> Note: May have bugs (missing content) in some circumstances - use at your own risk.
-
-| Type | Required |
-| ------- | -------- |
-| boolean | No |
-
----
-
-### `renderScrollComponent`
-
-```jsx
-(props: object) => element;
-```
-
-Render a custom scroll component, e.g. with a differently styled `RefreshControl`.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `viewabilityConfig`
-
-See `ViewabilityHelper.js` for flow type and further documentation.
-
-| Type | Required |
-| ----------------- | -------- |
-| ViewabilityConfig | No |
-
----
-
-### `viewabilityConfigCallbackPairs`
-
-List of `ViewabilityConfig`/`onViewableItemsChanged` pairs. A specific `onViewableItemsChanged` will be called when its corresponding `ViewabilityConfig`'s conditions are met. See `ViewabilityHelper.js` for flow type and further documentation.
-
-| Type | Required |
-| -------------------------------------- | -------- |
-| array of ViewabilityConfigCallbackPair | No |
-
----
-
-### `horizontal`
-
-| Type | Required |
-| ------- | -------- |
-| boolean | No |
-
----
-
-### `initialNumToRender`
-
-How many items to render in the initial batch. This should be enough to fill the screen but not much more. Note these items will never be unmounted as part of the windowed rendering in order to improve perceived performance of scroll-to-top actions.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `keyExtractor`
-
-```jsx
-(item: object, index: number) => string;
-```
-
-Used to extract a unique key for a given item at the specified index. Key is used for caching and as the react key to track item re-ordering. The default extractor checks `item.key`, then `item.id`, and then falls back to using the index, like React does.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `maxToRenderPerBatch`
-
-The maximum number of items to render in each incremental render batch. The more rendered at once, the better the fill rate, but responsiveness may suffer because rendering content may interfere with responding to button taps or other interactions.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `onEndReached`
-
-```jsx
-(info: {distanceFromEnd: number}) => void
-```
-
-Called once when the scroll position gets within `onEndReachedThreshold` of the rendered content.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onEndReachedThreshold`
-
-How far from the end (in units of visible length of the list) the bottom edge of the list must be from the end of the content to trigger the `onEndReached` callback. Thus a value of 0.5 will trigger `onEndReached` when the end of the content is within half the visible length of the list.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `updateCellsBatchingPeriod`
-
-Amount of time between low-pri item render batches, e.g. for rendering items quite a ways off screen. Similar fill rate/responsiveness tradeoff as `maxToRenderPerBatch`.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `windowSize`
-
-Determines the maximum number of items rendered outside of the visible area, in units of visible lengths. So if your list fills the screen, then `windowSize={21}` (the default) will render the visible screen area plus up to 10 screens above and 10 below the viewport. Reducing this number will reduce memory consumption and may improve performance, but will increase the chance that fast scrolling may reveal momentary blank areas of unrendered content.
-
-| Type | Required |
-| ------ | -------- |
-| number | No |
-
----
-
-### `disableVirtualization`
-
-> **Deprecated.** Virtualization provides significant performance and memory optimizations, but fully unmounts react instances that are outside of the render window. You should only need to disable this for debugging purposes.
-
-| Type | Required |
-| ---- | -------- |
-| | No |
-
----
-
-### `persistentScrollbar`
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `progressViewOffset`
-
-Set this when offset is needed for the loading indicator to show correctly.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
-## Methods
-
-### `scrollToEnd()`
-
-```jsx
-scrollToEnd(([options]: {animated: boolean}));
-```
-
-Scrolls to the end of the content. May be janky without `getItemLayout` prop.
-
-**Parameters:**
-
-| Name | Type |
-| ------ | ------ |
-| params | object |
-
-Valid `params` keys are:
-
-- 'animated' (boolean) - Whether the list should do an animation while scrolling. Defaults to `true`.
-
----
-
-### `scrollToIndex()`
-
-```jsx
-scrollToIndex((params: object));
-```
-
----
-
-### `scrollToItem()`
-
-```jsx
-scrollToItem((params: object));
-```
-
----
-
-### `scrollToOffset()`
-
-```jsx
-scrollToOffset((params: object));
-```
-
-Scroll to a specific content pixel offset in the list.
-
-Param `offset` expects the offset to scroll to. In case of `horizontal` is true, the offset is the x-value, in any other case the offset is the y-value.
-
-Param `animated` (`true` by default) defines whether the list should do an animation while scrolling.
-
----
-
-### `recordInteraction()`
-
-```jsx
-recordInteraction();
-```
-
----
-
-### `flashScrollIndicators()`
-
-```jsx
-flashScrollIndicators();
-```
diff --git a/website/versioned_docs/version-0.60/webview.md b/website/versioned_docs/version-0.60/webview.md
deleted file mode 100644
index f0886d6e45f..00000000000
--- a/website/versioned_docs/version-0.60/webview.md
+++ /dev/null
@@ -1,502 +0,0 @@
----
-id: webview
-title: '🚧 WebView'
----
-
-> **Deprecated.** Use [react-native-community/react-native-webview](https://github.com/react-native-community/react-native-webview) instead.
-
-`WebView` renders web content in a native view.
-
-```jsx
-import React, {Component} from 'react';
-import {WebView} from 'react-native';
-
-class MyWeb extends Component {
- render() {
- return (
- Hello world'}}
- />
- );
- }
-}
-```
-
-You can use this component to navigate back and forth in the web view's history and configure various properties for the web content.
-
-On iOS, the `useWebKit` prop can be used to opt into a WKWebView-backed implementation.
-
-> **Security Warning:** Currently, `onMessage` and `postMessage` do not allow specifying an origin. This can lead to cross-site scripting attacks if an unexpected document is loaded within a `WebView` instance. Please refer to the MDN documentation for [`Window.postMessage()`](https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage) for more details on the security implications of this.
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
----
-
-### `source`
-
-Loads static HTML or a URI (with optional headers) in the WebView. Note that static HTML will require setting [`originWhitelist`](webview#originwhitelist) to `["*"]`.
-
-The object passed to `source` can have either of the following shapes:
-
-**Load uri**
-
-- `uri` (string) - The URI to load in the `WebView`. Can be a local or remote file.
-- `method` (string) - The HTTP Method to use. Defaults to GET if not specified. On Android, the only supported methods are GET and POST.
-- `headers` (object) - Additional HTTP headers to send with the request. On Android, this can only be used with GET requests.
-- `body` (string) - The HTTP body to send with the request. This must be a valid UTF-8 string, and will be sent exactly as specified, with no additional encoding (e.g. URL-escaping or base64) applied. On Android, this can only be used with POST requests.
-
-**Static HTML**
-
-- `html` (string) - A static HTML page to display in the WebView.
-- `baseUrl` (string) - The base URL to be used for any relative links in the HTML.
-
-| Type | Required |
-| ------ | -------- |
-| object | No |
-
----
-
-### `automaticallyAdjustContentInsets`
-
-Controls whether to adjust the content inset for web views that are placed behind a navigation bar, tab bar, or toolbar. The default value is `true`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `injectJavaScript`
-
-Function that accepts a string that will be passed to the WebView and executed immediately as JavaScript.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `injectedJavaScript`
-
-Set this to provide JavaScript that will be injected into the web page when the view loads.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `mediaPlaybackRequiresUserAction`
-
-Boolean that determines whether HTML5 audio and video requires the user to tap them before they start playing. The default value is `true`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `nativeConfig`
-
-Override the native component used to render the WebView. Enables a custom native WebView which uses the same JavaScript as the original WebView.
-
-The `nativeConfig` prop expects an object with the following keys:
-
-- `component` (any)
-- `props` (object)
-- `viewManager` (object)
-
-| Type | Required |
-| ------ | -------- |
-| object | No |
-
----
-
-### `onError`
-
-Function that is invoked when the `WebView` load fails.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onLoad`
-
-Function that is invoked when the `WebView` has finished loading.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onLoadEnd`
-
-Function that is invoked when the `WebView` load succeeds or fails.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onLoadStart`
-
-Function that is invoked when the `WebView` starts loading.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onMessage`
-
-A function that is invoked when the webview calls `window.postMessage`. Setting this property will inject a `postMessage` global into your webview, but will still call pre-existing values of `postMessage`.
-
-`window.postMessage` accepts one argument, `data`, which will be available on the event object, `event.nativeEvent.data`. `data` must be a string.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onNavigationStateChange`
-
-Function that is invoked when the `WebView` loading starts or ends.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `originWhitelist`
-
-List of origin strings to allow being navigated to. The strings allow wildcards and get matched against _only_ the origin (not the full URL). If the user taps to navigate to a new page but the new page is not in this safelist, the URL will be handled by the OS. The default safelistlisted origins are `"http://*"` and `"https://*"`.
-
-| Type | Required |
-| ---------------- | -------- |
-| array of strings | No |
-
----
-
-### `renderError`
-
-Function that returns a view to show if there's an error.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `renderLoading`
-
-Function that returns a loading indicator. The startInLoadingState prop must be set to true in order to use this prop.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `scalesPageToFit`
-
-Boolean that controls whether the web content is scaled to fit the view and enables the user to change the scale. The default value is `true`.
-
-On iOS, when [`useWebKit=true`](webview#usewebkit), this prop will not work.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `onShouldStartLoadWithRequest`
-
-Function that allows custom handling of any web view requests. Return `true` from the function to continue loading the request and `false` to stop loading.
-
-| Type | Required | Platform |
-| -------- | -------- | -------- |
-| function | No | iOS |
-
----
-
-### `startInLoadingState`
-
-Boolean value that forces the `WebView` to show the loading view on the first load. This prop must be set to `true` in order for the `renderLoading` prop to work.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `decelerationRate`
-
-A floating-point number that determines how quickly the scroll view decelerates after the user lifts their finger. You may also use the string shortcuts `"normal"` and `"fast"` which match the underlying iOS settings for `UIScrollViewDecelerationRateNormal` and `UIScrollViewDecelerationRateFast` respectively:
-
-- normal: 0.998
-- fast: 0.99 (the default for iOS web view)
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | iOS |
-
----
-
-### `domStorageEnabled`
-
-Boolean value to control whether DOM Storage is enabled. Used only in Android.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `javaScriptEnabled`
-
-Boolean value to enable JavaScript in the `WebView`. Used on Android only as JavaScript is enabled by default on iOS. The default value is `true`.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `mixedContentMode`
-
-Specifies the mixed content mode. i.e WebView will allow a secure origin to load content from any other origin.
-
-Possible values for `mixedContentMode` are:
-
-- `never` (default) - WebView will not allow a secure origin to load content from an insecure origin.
-- `always` - WebView will allow a secure origin to load content from any other origin, even if that origin is insecure.
-- `compatibility` - WebView will attempt to be compatible with the approach of a modern web browser with regard to mixed content.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| string | No | Android |
-
----
-
-### `thirdPartyCookiesEnabled`
-
-Boolean value to enable third party cookies in the `WebView`. Used on Android Lollipop and above only as third party cookies are enabled by default on Android Kitkat and below and on iOS. The default value is `true`.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `userAgent`
-
-Sets the user-agent for the `WebView`.
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| string | No | Android |
-
----
-
-### `allowsInlineMediaPlayback`
-
-Boolean that determines whether HTML5 videos play inline or use the native full-screen controller. The default value is `false`.
-
-> **NOTE**
->
-> In order for video to play inline, not only does this property need to be set to `true`, but the video element in the HTML document must also include the `webkit-playsinline` attribute.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `bounces`
-
-Boolean value that determines whether the web view bounces when it reaches the edge of the content. The default value is `true`.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `contentInset`
-
-The amount by which the web view content is inset from the edges of the scroll view. Defaults to {top: 0, left: 0, bottom: 0, right: 0}.
-
-| Type | Required | Platform |
-| ------------------------------------------------------------------ | -------- | -------- |
-| object: {top: number, left: number, bottom: number, right: number} | No | iOS |
-
----
-
-### `dataDetectorTypes`
-
-Determines the types of data converted to clickable URLs in the web view's content. By default only phone numbers are detected.
-
-You can provide one type or an array of many types.
-
-Possible values for `dataDetectorTypes` are:
-
-- `phoneNumber`
-- `link`
-- `address`
-- `calendarEvent`
-- `none`
-- `all`
-
-With the [new WebKit](webview#usewebkit) implementation, we have three new values:
-
-- `trackingNumber`
-- `flightNumber`
-- `lookupSuggestion`
-
-| Type | Required | Platform |
-| ---------------- | -------- | -------- |
-| string, or array | No | iOS |
-
----
-
-### `scrollEnabled`
-
-Boolean value that determines whether scrolling is enabled in the `WebView`. The default value is `true`.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `geolocationEnabled`
-
-Set whether Geolocation is enabled in the `WebView`. The default value is `false`. Used only in Android.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `allowUniversalAccessFromFileURLs`
-
-Boolean that sets whether JavaScript running in the context of a file scheme URL should be allowed to access content from any origin. Including accessing content from other file scheme URLs. The default value is `false`.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `allowFileAccess`
-
-Boolean that sets whether the `WebView` has access to the file system. The default value is `false`.
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | Android |
-
----
-
-### `useWebKit`
-
-If true, use WKWebView instead of UIWebView.
-
-| Type | Required | Platform |
-| ------- | -------- | -------- |
-| boolean | No | iOS |
-
----
-
-### `url`
-
-**Deprecated.** Use the `source` prop instead.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `html`
-
-**Deprecated.** Use the `source` prop instead.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
-## Methods
-
-### `extraNativeComponentConfig()`
-
-```jsx
-static extraNativeComponentConfig()
-```
-
-### `goForward()`
-
-```jsx
-goForward();
-```
-
-Go forward one page in the web view's history.
-
-### `goBack()`
-
-```jsx
-goBack();
-```
-
-Go back one page in the web view's history.
-
-### `reload()`
-
-```jsx
-reload();
-```
-
-Reloads the current page.
-
-### `stopLoading()`
-
-```jsx
-stopLoading();
-```
-
-Stop loading the current page.
diff --git a/website/versioned_docs/version-0.61/_getting-started-linux-android.md b/website/versioned_docs/version-0.61/_getting-started-linux-android.md
deleted file mode 100644
index 4fe0a84daf4..00000000000
--- a/website/versioned_docs/version-0.61/_getting-started-linux-android.md
+++ /dev/null
@@ -1,177 +0,0 @@
-## Installing dependencies
-
-You will need Node, the React Native command line interface, a JDK, and Android Studio.
-
-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.
-
-Node
-
-Follow the [installation instructions for your Linux distribution](https://nodejs.org/en/download/package-manager/) to install Node 10 or newer.
-
-Java Development Kit
-
-React Native requires at least the 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 14](https://www.oracle.com/java/technologies/javase-jdk14-downloads.html) if desired.
-
-Android development environment
-
-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.
-
-1. Install Android Studio
-
-[Download and install Android Studio](https://developer.android.com/studio/index.html). While on Android Studio installation wizard, make sure the boxes next to all of the following items are checked:
-
-- `Android SDK`
-- `Android SDK Platform`
-- `Android Virtual Device`
-
-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.
-
-2. Install the Android SDK
-
-Android Studio installs the latest Android SDK by default. Building a React Native app with native code, however, requires the `Android 10 (Q)` SDK in particular. Additional Android SDKs can be installed through the SDK Manager in Android Studio.
-
-To do that, open Android Studio, click on "Configure" button and select "SDK Manager".
-
-> 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 10 (Q)` entry, then make sure the following items are checked:
-
-- `Android SDK Platform 29`
-- `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 `29.0.2` is selected.
-
-Finally, click "Apply" to download and install the Android SDK and related build tools.
-
-3. Configure the ANDROID_HOME environment variable
-
-The React Native tools require some environment variables to be set up in order to build apps with native code.
-
-Add the following lines to your `$HOME/.bash_profile` or `$HOME/.bashrc` (if you are using `zsh` then `~/.zprofile` or `~/.zshrc`) config file:
-
-```shell
-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
-```
-
-> `.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` for `bash` or `source $HOME/.zprofile` to load the config into your current shell. Verify that ANDROID_HOME has been set by running `echo $ANDROID_HOME` and the appropriate directories have 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**.
-
-Watchman
-
-Follow the [Watchman installation guide](https://facebook.github.io/watchman/docs/install/#buildinstall) to compile and install Watchman from source.
-
-> [Watchman](https://facebook.github.io/watchman/docs/install/) 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).
-
-React Native Command Line Interface
-
-React Native has a built-in command line interface. Rather than install and manage a specific version of the CLI globally, we recommend you access the current version at runtime using `npx`, which ships with Node.js. With `npx react-native `, the current stable version of the CLI will be downloaded and executed at the time the command is run.
-
-Creating a new application
-
-> If you previously installed a global `react-native-cli` package, please remove it as it may cause unexpected issues.
-
-React Native has a built-in command line interface, which you can use to generate a new project. You can access it without installing anything globally using `npx`, which ships with Node.js. Let's create a new React Native project called "AwesomeProject":
-
-```shell
-npx react-native init AwesomeProject
-```
-
-This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Expo, 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 or template
-
-If you want to start a new project with a specific React Native version, you can use the `--version` argument:
-
-```shell
-npx react-native init AwesomeProject --version X.XX.X
-```
-
-You can also start a project with a custom React Native template, like TypeScript, with `--template` argument:
-
-```shell
-npx react-native init AwesomeTSProject --template react-native-template-typescript
-```
-
-Preparing the Android device
-
-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
-
-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
-
-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:
-
-
-
-If you have recently 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 **Q** API Level 29 image.
-
-> 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.
-
-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.
-
-Running your React Native application
-
-Step 1: Start Metro
-
-First, you will need to start Metro, the JavaScript bundler that ships with React Native. Metro "takes in an entry file and various options, and returns a single JavaScript file that includes all your code and its dependencies."—[Metro Docs](https://facebook.github.io/metro/docs/concepts)
-
-To start Metro, run `npx react-native start` inside your React Native project folder:
-
-```shell
-npx react-native start
-```
-
-`react-native start` starts Metro Bundler.
-
-> If you use the Yarn package manager, you can use `yarn` instead of `npx` when running React Native commands inside an existing project.
-
-> If you're familiar with web development, Metro is a lot like webpack—for React Native apps. Unlike Kotlin or Java, JavaScript isn't compiled—and neither is React Native. Bundling isn't the same as compiling, but it can help improve startup performance and translate some platform-specific JavaScript into more JavaScript.
-
-Step 2: Start your application
-
-Let Metro Bundler run in its own terminal. Open a new terminal inside your React Native project folder. Run the following:
-
-```shell
-npx react-native run-android
-```
-
-If everything is set up correctly, you should see your new app running in your Android emulator shortly.
-
-`npx react-native run-android` is 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.
-
-Modifying your app
-
-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!
-
-That's it!
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-Now what?
-
-- 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, check out the [Introduction to React Native](getting-started).
diff --git a/website/versioned_docs/version-0.61/_getting-started-macos-android.md b/website/versioned_docs/version-0.61/_getting-started-macos-android.md
deleted file mode 100644
index a435135dd14..00000000000
--- a/website/versioned_docs/version-0.61/_getting-started-macos-android.md
+++ /dev/null
@@ -1,191 +0,0 @@
-## Installing dependencies
-
-You will need Node, Watchman, the React Native command line interface, a JDK, and Android Studio.
-
-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.
-
-Node & Watchman
-
-We recommend installing Node and Watchman using [Homebrew](http://brew.sh/). Run the following commands in a Terminal after installing Homebrew:
-
-```shell
-brew install node
-brew install watchman
-```
-
-If you have already installed Node on your system, make sure it is Node 10 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.
-
-Java Development Kit
-
-We recommend installing JDK using [Homebrew](http://brew.sh/). Run the following commands in a Terminal after installing Homebrew:
-
-```shell
-brew install --cask adoptopenjdk/openjdk/adoptopenjdk8
-```
-
-If you have already installed JDK on your system, make sure it is JDK 8 or newer.
-
-Android development environment
-
-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.
-
-1. Install Android Studio
-
-[Download and install Android Studio](https://developer.android.com/studio/index.html). While on Android Studio installation wizard, make sure the boxes next to all of the following items are checked:
-
-- `Android SDK`
-- `Android SDK Platform`
-- `Android Virtual Device`
-- If you are not already using Hyper-V: `Performance (Intel ® HAXM)` ([See here for AMD or Hyper-V](https://android-developers.googleblog.com/2018/07/android-emulator-amd-processor-hyper-v.html))
-
-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.
-
-2. Install the Android SDK
-
-Android Studio installs the latest Android SDK by default. Building a React Native app with native code, however, requires the `Android 10 (Q)` SDK in particular. Additional Android SDKs can be installed through the SDK Manager in Android Studio.
-
-To do that, open Android Studio, click on "More Actions" button and select "SDK Manager".
-
-
-
-> 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 10 (Q)` entry, then make sure the following items are checked:
-
-- `Android SDK Platform 29`
-- `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 `29.0.2` is selected.
-
-Finally, click "Apply" to download and install the Android SDK and related build tools.
-
-3. Configure the ANDROID_HOME environment variable
-
-The React Native tools require some environment variables to be set up in order to build apps with native code.
-
-Add the following lines to your `$HOME/.bash_profile` or `$HOME/.bashrc` (if you are using `zsh` then `~/.zprofile` or `~/.zshrc`) config file:
-
-```shell
-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
-```
-
-> `.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` for `bash` or `source $HOME/.zprofile` to load the config into your current shell. Verify that ANDROID_HOME has been set by running `echo $ANDROID_HOME` and the appropriate directories have 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**.
-
-React Native Command Line Interface
-
-React Native has a built-in command line interface. Rather than install and manage a specific version of the CLI globally, we recommend you access the current version at runtime using `npx`, which ships with Node.js. With `npx react-native `, the current stable version of the CLI will be downloaded and executed at the time the command is run.
-
-Creating a new application
-
-> If you previously installed a global `react-native-cli` package, please remove it as it may cause unexpected issues.
-
-React Native has a built-in command line interface, which you can use to generate a new project. You can access it without installing anything globally using `npx`, which ships with Node.js. Let's create a new React Native project called "AwesomeProject":
-
-```shell
-npx react-native init AwesomeProject
-```
-
-This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Expo, 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 or template
-
-If you want to start a new project with a specific React Native version, you can use the `--version` argument:
-
-```shell
-npx react-native init AwesomeProject --version X.XX.X
-```
-
-You can also start a project with a custom React Native template, like TypeScript, with `--template` argument:
-
-```shell
-npx react-native init AwesomeTSProject --template react-native-template-typescript
-```
-
-Preparing the Android device
-
-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
-
-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
-
-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:
-
-
-
-If you have recently 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 **Q** API Level 29 image.
-
-> 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.
-
-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.
-
-Running your React Native application
-
-Step 1: Start Metro
-
-First, you will need to start Metro, the JavaScript bundler that ships with React Native. Metro "takes in an entry file and various options, and returns a single JavaScript file that includes all your code and its dependencies."—[Metro Docs](https://facebook.github.io/metro/docs/concepts)
-
-To start Metro, run `npx react-native start` inside your React Native project folder:
-
-```shell
-npx react-native start
-```
-
-`react-native start` starts Metro Bundler.
-
-> If you use the Yarn package manager, you can use `yarn` instead of `npx` when running React Native commands inside an existing project.
-
-> If you're familiar with web development, Metro is a lot like webpack—for React Native apps. Unlike Kotlin or Java, JavaScript isn't compiled—and neither is React Native. Bundling isn't the same as compiling, but it can help improve startup performance and translate some platform-specific JavaScript into more JavaScript.
-
-Step 2: Start your application
-
-Let Metro Bundler run in its own terminal. Open a new terminal inside your React Native project folder. Run the following:
-
-```shell
-npx react-native run-android
-```
-
-If everything is set up correctly, you should see your new app running in your Android emulator shortly.
-
-
-
-`npx react-native run-android` is 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.
-
-Modifying your app
-
-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 (`⌘M`) to see your changes!
-
-That's it!
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-Now what?
-
-- 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, check out the [Introduction to React Native](getting-started).
diff --git a/website/versioned_docs/version-0.61/_getting-started-macos-ios.md b/website/versioned_docs/version-0.61/_getting-started-macos-ios.md
deleted file mode 100644
index eba4bed9c53..00000000000
--- a/website/versioned_docs/version-0.61/_getting-started-macos-ios.md
+++ /dev/null
@@ -1,135 +0,0 @@
-## Installing dependencies
-
-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.
-
-### Node & Watchman
-
-We recommend installing Node and Watchman using [Homebrew](http://brew.sh/). Run the following commands in a Terminal after installing Homebrew:
-
-```shell
-brew install node
-brew install watchman
-```
-
-If you have already installed Node on your system, make sure it is Node 10 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.
-
-### Xcode & CocoaPods
-
-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
-
-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.
-
-
-
-#### Installing an iOS Simulator in Xcode
-
-To install a simulator, open Xcode > Preferences... and select the Components tab. Select a simulator with the corresponding version of iOS you wish to use.
-
-#### CocoaPods
-
-[CocoaPods](https://cocoapods.org/) is built with Ruby and it will be installable with the default Ruby available on macOS. You can use a Ruby Version manager, however we recommend that you use the standard Ruby available on macOS unless you know what you're doing.
-
-Using the default Ruby install will require you to use `sudo` when installing gems. (This is only an issue for the duration of the gem installation, though.)
-
-```shell
-sudo gem install cocoapods
-```
-
-For more information, please visit [CocoaPods Getting Started guide](https://guides.cocoapods.org/using/getting-started.html).
-
-### React Native Command Line Interface
-
-React Native has a built-in command line interface. Rather than install and manage a specific version of the CLI globally, we recommend you access the current version at runtime using `npx`, which ships with Node.js. With `npx react-native `, the current stable version of the CLI will be downloaded and executed at the time the command is run.
-
-## Creating a new application
-
-> If you previously installed a global `react-native-cli` package, please remove it as it may cause unexpected issues.
-
-You can use React Native's built-in command line interface to generate a new project. Let's create a new React Native project called "AwesomeProject":
-
-```shell
-npx react-native init AwesomeProject
-```
-
-This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Expo, 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 or template
-
-If you want to start a new project with a specific React Native version, you can use the `--version` argument:
-
-```shell
-npx react-native init AwesomeProject --version X.XX.X
-```
-
-You can also start a project with a custom React Native template, like TypeScript, with `--template` argument:
-
-```shell
-npx react-native init AwesomeTSProject --template react-native-template-typescript
-```
-
-> **Note** If the above command is failing, you may have old version of `react-native` or `react-native-cli` installed globally on your pc. Try uninstalling the cli and run the cli using `npx`.
-
-## Running your React Native application
-
-### Step 1: Start Metro
-
-First, you will need to start Metro, the JavaScript bundler that ships with React Native. Metro "takes in an entry file and various options, and returns a single JavaScript file that includes all your code and its dependencies."—[Metro Docs](https://facebook.github.io/metro/docs/concepts)
-
-To start Metro, run `npx react-native start` inside your React Native project folder:
-
-```shell
-npx react-native start
-```
-
-`react-native start` starts Metro Bundler.
-
-> If you use the Yarn package manager, you can use `yarn` instead of `npx` when running React Native commands inside an existing project.
-
-> If you're familiar with web development, Metro is a lot like webpack—for React Native apps. Unlike Kotlin or Java, JavaScript isn't compiled—and neither is React Native. Bundling isn't the same as compiling, but it can help improve startup performance and translate some platform-specific JavaScript into more JavaScript.
-
-### Step 2: Start your application
-
-Let Metro Bundler run in its own terminal. Open a new terminal inside your React Native project folder. Run the following:
-
-```shell
-npx react-native run-ios
-```
-
-You should see your new app running in the iOS Simulator shortly.
-
-
-
-`npx react-native run-ios` is 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
-
-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).
-
-### Modifying your app
-
-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.
-- Hit `⌘R` in your iOS Simulator to reload the app and see your changes!
-
-### That's it!
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-Installing dependencies
-
-You will need Node, the React Native command line interface, Python2, a JDK, and Android Studio.
-
-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.
-
-Node, Python2, JDK
-
-We recommend installing Node and Python2 via [Chocolatey](https://chocolatey.org), a popular package manager for Windows.
-
-React Native also requires [Java SE Development Kit (JDK)](https://openjdk.java.net/projects/jdk8/), as well as Python2. 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 openjdk8
-```
-
-If you have already installed Node on your system, make sure it is Node 10 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/).
-
-> If you're using the latest version of Java Development Kit, you'll need to change the Gradle version of your project so it can recognize the JDK. You can do that by going to `{project root folder}\android\gradle\wrapper\gradle-wrapper.properties` and changing the `distributionUrl` value to upgrade the Gradle version. You can check out [here the latest releases of Gradle](https://gradle.org/releases/).
-
-Android development environment
-
-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.
-
-1. Install Android Studio
-
-[Download and install Android Studio](https://developer.android.com/studio/index.html). While on Android Studio installation wizard, make sure the boxes next to all of the following items are checked:
-
-- `Android SDK`
-- `Android SDK Platform`
-- `Android Virtual Device`
-- If you are not already using Hyper-V: `Performance (Intel ® HAXM)` ([See here for AMD or Hyper-V](https://android-developers.googleblog.com/2018/07/android-emulator-amd-processor-hyper-v.html))
-
-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.
-
-2. Install the Android SDK
-
-Android Studio installs the latest Android SDK by default. Building a React Native app with native code, however, requires the `Android 10 (Q)` SDK in particular. Additional Android SDKs can be installed through the SDK Manager in Android Studio.
-
-To do that, open Android Studio, click on "More Actions" button and select "SDK Manager".
-
-
-
-> 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 10 (Q)` entry, then make sure the following items are checked:
-
-- `Android SDK Platform 29`
-- `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 `29.0.2` is selected.
-
-Finally, click "Apply" to download and install the Android SDK and related build tools.
-
-3. Configure the ANDROID_HOME environment variable
-
-The React Native tools require some environment variables to be set up in order to build apps with native code.
-
-1. Open the **Windows Control Panel.**
-2. Click on **User Accounts,** then click **User Accounts** again
-3. Click on **Change my environment variables**
-4. Click on **New...** to create a new `ANDROID_HOME` user variable that points to the path to your Android SDK:
-
-
-
-The SDK is installed, by default, at the following location:
-
-```powershell
-%LOCALAPPDATA%\Android\Sdk
-```
-
-You can find the actual location of the SDK in the Android Studio "Settings" 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.
-
-1. Open powershell
-2. Copy and paste **Get-ChildItem -Path Env:\\** into powershell
-3. Verify `ANDROID_HOME` has been added
-
-4. Add platform-tools to Path
-
-1. Open the **Windows Control Panel.**
-2. Click on **User Accounts,** then click **User Accounts** again
-3. Click on **Change my environment variables**
-4. Select the **Path** variable.
-5. Click **Edit.**
-6. Click **New** and add the path to platform-tools to the list.
-
-The default location for this folder is:
-
-```powershell
-%LOCALAPPDATA%\Android\Sdk\platform-tools
-```
-
-React Native Command Line Interface
-
-React Native has a built-in command line interface. Rather than install and manage a specific version of the CLI globally, we recommend you access the current version at runtime using `npx`, which ships with Node.js. With `npx react-native `, the current stable version of the CLI will be downloaded and executed at the time the command is run.
-
-Creating a new application
-
-> If you previously installed a global `react-native-cli` package, please remove it as it may cause unexpected issues.
-
-React Native has a built-in command line interface, which you can use to generate a new project. You can access it without installing anything globally using `npx`, which ships with Node.js. Let's create a new React Native project called "AwesomeProject":
-
-```shell
-npx react-native init AwesomeProject
-```
-
-This is not necessary if you are integrating React Native into an existing application, if you "ejected" from Expo, 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 or template
-
-If you want to start a new project with a specific React Native version, you can use the `--version` argument:
-
-```shell
-npx react-native init AwesomeProject --version X.XX.X
-```
-
-You can also start a project with a custom React Native template, like TypeScript, with `--template` argument:
-
-```shell
-npx react-native init AwesomeTSProject --template react-native-template-typescript
-```
-
-Preparing the Android device
-
-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
-
-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
-
-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:
-
-
-
-If you have recently 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 **Q** API Level 29 image.
-
-> 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.
-
-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.
-
-Running your React Native application
-
-Step 1: Start Metro
-
-First, you will need to start Metro, the JavaScript bundler that ships with React Native. Metro "takes in an entry file and various options, and returns a single JavaScript file that includes all your code and its dependencies."—[Metro Docs](https://facebook.github.io/metro/docs/concepts)
-
-To start Metro, run `npx react-native start` inside your React Native project folder:
-
-```shell
-npx react-native start
-```
-
-`react-native start` starts Metro Bundler.
-
-> If you use the Yarn package manager, you can use `yarn` instead of `npx` when running React Native commands inside an existing project.
-
-> If you're familiar with web development, Metro is a lot like webpack—for React Native apps. Unlike Kotlin or Java, JavaScript isn't compiled—and neither is React Native. Bundling isn't the same as compiling, but it can help improve startup performance and translate some platform-specific JavaScript into more JavaScript.
-
-Step 2: Start your application
-
-Let Metro Bundler run in its own terminal. Open a new terminal inside your React Native project folder. Run the following:
-
-```shell
-npx react-native run-android
-```
-
-If everything is set up correctly, you should see your new app running in your Android emulator shortly.
-
-
-
-`npx react-native run-android` is 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.
-
-Modifying your app
-
-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!
-
-That's it!
-
-Congratulations! You've successfully run and modified your first React Native app.
-
-Now what?
-
-- 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, check out the [Introduction to React Native](getting-started).
diff --git a/website/versioned_docs/version-0.61/_integration-with-existing-apps-java.md b/website/versioned_docs/version-0.61/_integration-with-existing-apps-java.md
deleted file mode 100644
index c84c29d9d13..00000000000
--- a/website/versioned_docs/version-0.61/_integration-with-existing-apps-java.md
+++ /dev/null
@@ -1,385 +0,0 @@
-## Key Concepts
-
-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.
-
-## Prerequisites
-
-Follow the React Native CLI Quickstart in the [environment setup guide](/docs/environment-setup) 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.
-
-### 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:
-
-```shell
-$ 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:
-
-```shell
-$ 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.
-
-## Adding React Native to your app
-
-### Configuring maven
-
-Add the React Native and JSC 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
- implementation "org.webkit:android-jsc:+"
-}
-```
-
-> 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 and JSC maven directories to the top-level `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"
- }
- maven {
- // Android JSC is installed from npm
- url("$rootDir/../node_modules/jsc-android/dist")
- }
- ...
- }
- ...
-}
-```
-
-> 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.
-
-### Enable native modules autolinking
-
-To use the power of [autolinking](https://github.com/react-native-community/cli/blob/master/docs/autolinking.md), we have to apply it a few places. First add the following entry to `settings.gradle`:
-
-```gradle
-apply from: file("../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesSettingsGradle(settings)
-```
-
-Next add the following entry at the very bottom of the `app/build.gradle`:
-
-```gradle
-apply from: file("../../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesAppBuildGradle(project)
-```
-
-### Configuring permissions
-
-Next, make sure you have the Internet permission in your `AndroidManifest.xml`:
-
-
-
-
-
-```
-
-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 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 a `` component within a styled ``:
-
-```jsx
-import React from 'react';
-import {AppRegistry, StyleSheet, Text, View} from 'react-native';
-
-class HelloWorld extends React.Component {
- render() {
- return (
-
- Hello, World
-
- );
- }
-}
-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 targeting 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);
- SoLoader.init(this, false);
-
- mReactRootView = new ReactRootView(this);
- List packages = new PackageList(getApplication()).getPackages();
- // Packages that cannot be autolinked yet can be added manually here, for example:
- // packages.add(new MyReactNativePackage());
- // Remember to include them in `settings.gradle` and `app/build.gradle` too.
-
- mReactInstanceManager = ReactInstanceManager.builder()
- .setApplication(getApplication())
- .setCurrentActivity(this)
- .setBundleAssetName("index.android.bundle")
- .setJSMainModulePath("index")
- .addPackages(packages)
- .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).
-
-Perform a “Sync Project files with Gradle” operation.
-
-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
-
-
-```
-
-> 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 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 [Metro bundler][metro] 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, run the following command in the root directory of your React Native project:
-
-```shell
-$ 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:
-
-
-
-### Creating a release build in Android Studio
-
-You can use Android Studio to create your release builds too! It’s as quick as creating release builds of your previously-existing native Android app. There’s 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:
-
-```shell
-$ npx 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, create a release build of your native app from within Android Studio as usual and you should be good to go!
-
-### Now what?
-
-At this point you can continue developing your app as usual. Refer to our [debugging](debugging) and [deployment](running-on-device) docs to learn more about working with React Native.
-
-[metro]: https://facebook.github.io/metro/
diff --git a/website/versioned_docs/version-0.61/_integration-with-existing-apps-objc.md b/website/versioned_docs/version-0.61/_integration-with-existing-apps-objc.md
deleted file mode 100644
index 19103da59e8..00000000000
--- a/website/versioned_docs/version-0.61/_integration-with-existing-apps-objc.md
+++ /dev/null
@@ -1,356 +0,0 @@
-## Key Concepts
-
-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.
-
-## Prerequisites
-
-Follow the React Native CLI Quickstart in the [environment setup guide](/docs/environment-setup) 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.
-
-### 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:
-
-```shell
-$ 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:
-
-```shell
-$ 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.
-
-### 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/).
-
-```shell
-$ 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.
-
-## Adding React Native to your app
-
-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.
-
-
-
-### 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.
-
-
-
-### 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/0.61-stable/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 `` elements), then you will need the `RCTText` `subspec`. If you want the `Image` library (e.g., for `` 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:
-
-```shell
-$ pod init
-```
-
-The `Podfile` will contain a boilerplate setup that you will tweak for your integration purposes.
-
-> The `Podfile` version changes depending on your version of `react-native`. Refer to https://react-native-community.github.io/upgrade-helper/ for the specific version of `Podfile` you should be using.
-
-Ultimately, your `Podfile` should look something similar to this:
-
-```
-# 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 'FBLazyVector', :path => "../node_modules/react-native/Libraries/FBLazyVector"
- pod 'FBReactNativeSpec', :path => "../node_modules/react-native/Libraries/FBReactNativeSpec"
- pod 'RCTRequired', :path => "../node_modules/react-native/Libraries/RCTRequired"
- pod 'RCTTypeSafety', :path => "../node_modules/react-native/Libraries/TypeSafety"
- pod 'React', :path => '../node_modules/react-native/'
- pod 'React-Core', :path => '../node_modules/react-native/'
- pod 'React-CoreModules', :path => '../node_modules/react-native/React/CoreModules'
- pod 'React-Core/DevSupport', :path => '../node_modules/react-native/'
- 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-Core/RCTWebSocket', :path => '../node_modules/react-native/'
-
- 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 'ReactCommon/callinvoker', :path => "../node_modules/react-native/ReactCommon"
- pod 'ReactCommon/turbomodule/core', :path => "../node_modules/react-native/ReactCommon"
- 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
-```
-
-After you have created your `Podfile`, you are ready to install the React Native pod.
-
-```shell
-$ pod install
-```
-
-You should see output such as:
-
-```
-Analyzing dependencies
-Fetching podspec for `React` from `../node_modules/react-native`
-Downloading dependencies
-Installing React (0.62.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.
-
-### 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 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 a `` component within a styled ``
-
-```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 => (
-
- {score.name}:{score.value}
- {'\n'}
-
- ));
- return (
-
-
- 2048 High Scores!
-
- {contents}
-
- );
- }
-}
-
-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 contain 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.
-
-
-
-##### 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 [Metro bundler][metro] 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.
-
-First `import` the `RCTRootView` header.
-
-```objectivec
-#import
-```
-
-> 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/0.61-stable/React/Base/RCTBridge.h#L93) to create a bridge and then use `RCTRootView initWithBridge`.
-
-> 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.
-
-##### 3. Wire Up
-
-Wire up the new link in the main menu to the newly added event handler method.
-
-
-
-> 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 [Metro bundler][metro] 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
-NSAppTransportSecurity
-
- NSExceptionDomains
-
- localhost
-
- NSTemporaryExceptionAllowsInsecureHTTPLoads
-
-
-
-```
-
-> 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, run the following command in the root directory of your React Native project:
-
-```shell
-$ 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
-$ npx 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:
-
-
-
-Here is the _React Native_ high score screen:
-
-
-
-> 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
-
-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).
-
-### Now what?
-
-At this point you can continue developing your app as usual. Refer to our [debugging](debugging) and [deployment](running-on-device) docs to learn more about working with React Native.
-
-[metro]: https://facebook.github.io/metro/
diff --git a/website/versioned_docs/version-0.61/_integration-with-existing-apps-swift.md b/website/versioned_docs/version-0.61/_integration-with-existing-apps-swift.md
deleted file mode 100644
index cf585798659..00000000000
--- a/website/versioned_docs/version-0.61/_integration-with-existing-apps-swift.md
+++ /dev/null
@@ -1,345 +0,0 @@
-## Key Concepts
-
-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.
-
-## Prerequisites
-
-Follow the React Native CLI Quickstart in the [environment setup guide](/docs/environment-setup) 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.
-
-### 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:
-
-```shell
-$ 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:
-
-```shell
-$ 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.
-
-### 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/).
-
-```shell
-$ 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.
-
-## Adding React Native to your app
-
-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.
-
-
-
-### 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.
-
-
-
-### 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/0.61-stable/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 `` elements), then you will need the `RCTText` `subspec`. If you want the `Image` library (e.g., for `` 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:
-
-```shell
-$ pod init
-```
-
-The `Podfile` will contain a boilerplate setup that you will tweak for your integration purposes.
-
-> The `Podfile` version changes depending on your version of `react-native`. Refer to https://react-native-community.github.io/upgrade-helper/ for the specific version of `Podfile` you should be using.
-
-Ultimately, your `Podfile` should look something similar to this:
-
-```
-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
-```
-
-After you have created your `Podfile`, you are ready to install the React Native pod.
-
-```shell
-$ pod install
-```
-
-You should see output such as:
-
-```
-Analyzing dependencies
-Fetching podspec for `React` from `../node_modules/react-native`
-Downloading dependencies
-Installing React (0.62.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.
-
-> 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)`.
-
-### 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 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 a `` component within a styled ``
-
-```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 => (
-
- {score.name}:{score.value}
- {'\n'}
-
- ));
- return (
-
-
- 2048 High Scores!
-
- {contents}
-
- );
- }
-}
-
-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 contain 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.
-
-
-
-##### 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 [Metro bundler][metro] 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.
-
-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/0.61-stable/React/Base/RCTBridge.h#L89) to create a bridge and then use `RCTRootView initWithBridge`.
-
-> 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.
-
-##### 3. Wire Up
-
-Wire up the new link in the main menu to the newly added event handler method.
-
-
-
-> 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 [Metro bundler][metro] 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
-NSAppTransportSecurity
-
- NSExceptionDomains
-
- localhost
-
- NSTemporaryExceptionAllowsInsecureHTTPLoads
-
-
-
-```
-
-> 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, run the following command in the root directory of your React Native project:
-
-```shell
-$ 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
-$ npx 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:
-
-
-
-Here is the _React Native_ high score screen:
-
-
-
-> 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
-
-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).
-
-### Now what?
-
-At this point you can continue developing your app as usual. Refer to our [debugging](debugging) and [deployment](running-on-device) docs to learn more about working with React Native.
-
-[metro]: https://facebook.github.io/metro/
diff --git a/website/versioned_docs/version-0.61/accessibility.md b/website/versioned_docs/version-0.61/accessibility.md
deleted file mode 100644
index 66de1067452..00000000000
--- a/website/versioned_docs/version-0.61/accessibility.md
+++ /dev/null
@@ -1,293 +0,0 @@
----
-id: accessibility
-title: Accessibility
----
-
-Both Android and iOS provide APIs for integrating apps with assistive technologies like the bundled screen readers VoiceOver (iOS) and TalkBack (Android). React Native has complimentary APIs that let your app accommodate all users.
-
-> Android and iOS differ slightly in their approaches, and thus the React Native implementations may vary by platform.
-
-## Accessibility properties
-
-### `accessible` (Android, iOS)
-
-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
-
- text one
- text two
-
-```
-
-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` (Android, iOS)
-
-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
-
-
- Press me!
-
-
-```
-
-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` (Android, iOS)
-
-An accessibility hint helps users understand what will happen when they perform an action on the accessibility element when that result is not clear from the accessibility label.
-
-To use, set the `accessibilityHint` property to a custom string on your View, Text or Touchable:
-
-```jsx
-
-
- Back
-
-
-```
-
-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` (Android, iOS)
-
-`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).
-
-### `accessibilityState` (Android, iOS)
-
-Describes the current state of a component to the user of an assistive technology.
-
-`accessibilityState` is an object. It contains the following fields:
-
-| Name | Description | Type | Required |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | -------- |
-| disabled | Indicates whether the element is disabled or not. | boolean | No |
-| selected | Indicates whether a selectable element is currently selected or not. | boolean | No |
-| checked | Indicates the state of a checkable element. This field can either take a boolean or the "mixed" string to represent mixed checkboxes. | boolean or 'mixed' | No |
-| busy | Indicates whether an element is currently busy or not. | boolean | No |
-| expanded | Indicates whether an expandable element is currently expanded or collapsed. | boolean | No |
-
-To use, set the `accessibilityState` to an object with a specific definition.
-
-### `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` (Android, 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
-
-
- Click me
-
-
-
- Clicked {count} times
-
-```
-
-In the above example method `addOne` changes the state variable `count`. 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
-
-
- First layout
-
-
- Second layout
-
-
-```
-
-In the above example, the `yellow` layout and its descendants are completely invisible to TalkBack and all other accessibility services. So we can 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
- {
- 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) 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 set accessibility focus to a view). Native UIManager module exposes a method ‘sendAccessibilityEvent’ for this purpose. It takes two arguments: view tag and a type of an event. The supported event types are `typeWindowStateChanged`, `typeViewFocused` and `typeViewClicked`.
-
-```jsx
-import {Platform, UIManager, findNodeHandle} from 'react-native';
-
-if (Platform.OS === 'android') {
- UIManager.sendAccessibilityEvent(
- findNodeHandle(this),
- UIManager.AccessibilityEventTypes.typeViewFocused,
- );
-}
-```
-
-## 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:
-
-```shell
-# 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
-```
-
-## Additional Resources
-
-- [Making React Native Apps Accessible](https://engineering.fb.com/ios/making-react-native-apps-accessible/)
diff --git a/website/versioned_docs/version-0.61/accessibilityinfo.md b/website/versioned_docs/version-0.61/accessibilityinfo.md
deleted file mode 100644
index 8b4fd5c8853..00000000000
--- a/website/versioned_docs/version-0.61/accessibilityinfo.md
+++ /dev/null
@@ -1,184 +0,0 @@
----
-id: accessibilityinfo
-title: AccessibilityInfo
----
-
-Sometimes it's useful to know whether or not the device has a screen reader that is currently active. The `AccessibilityInfo` API is designed for this purpose. You can use it to query the current state of the screen reader as well as to register to be notified when the state of the screen reader changes.
-
-Here's a small example illustrating how to use `AccessibilityInfo`:
-
-```jsx
-class AccessibilityStatusExample extends React.Component {
- state = {
- reduceMotionEnabled: false,
- screenReaderEnabled: false,
- };
-
- componentDidMount() {
- AccessibilityInfo.addEventListener(
- 'reduceMotionChanged',
- this._handleReduceMotionToggled,
- );
- AccessibilityInfo.addEventListener(
- 'screenReaderChanged',
- this._handleScreenReaderToggled,
- );
-
- AccessibilityInfo.isReduceMotionEnabled().then(
- reduceMotionEnabled => {
- this.setState({reduceMotionEnabled});
- },
- );
- AccessibilityInfo.isScreenReaderEnabled().then(
- screenReaderEnabled => {
- this.setState({screenReaderEnabled});
- },
- );
- }
-
- componentWillUnmount() {
- AccessibilityInfo.removeEventListener(
- 'reduceMotionChanged',
- this._handleReduceMotionToggled,
- );
-
- AccessibilityInfo.removeEventListener(
- 'screenReaderChanged',
- this._handleScreenReaderToggled,
- );
- }
-
- _handleReduceMotionToggled = reduceMotionEnabled => {
- this.setState({reduceMotionEnabled});
- };
-
- _handleScreenReaderToggled = screenReaderEnabled => {
- this.setState({screenReaderEnabled});
- };
-
- render() {
- return (
-
-
- The reduce motion is{' '}
- {this.state.reduceMotionEnabled
- ? 'enabled'
- : 'disabled'}
- .
-
-
- The screen reader is{' '}
- {this.state.screenReaderEnabled
- ? 'enabled'
- : 'disabled'}
- .
-
-
- );
- }
-}
-```
-
----
-
-# Reference
-
-## Methods
-
-### `isBoldTextEnabled()`
-
-```jsx
-static isBoldTextEnabled()
-```
-
-**iOS-Only.** Query whether a bold text is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when bold text is enabled and `false` otherwise.
-
-### `isGrayscaleEnabled()`
-
-```jsx
-static isGrayscaleEnabled()
-```
-
-**iOS-Only.** Query whether grayscale is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when grayscale is enabled and `false` otherwise.
-
-### `isInvertColorsEnabled()`
-
-```jsx
-static isInvertColorsEnabled()
-```
-
-**iOS-Only.** Query whether invert colors is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when invert colors is enabled and `false` otherwise.
-
-### `isReduceMotionEnabled()`
-
-```jsx
-static isReduceMotionEnabled()
-```
-
-Query whether reduce motion is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when reduce motion is enabled and `false` otherwise.
-
-### `isReduceTransparencyEnabled()`
-
-```jsx
-static isReduceTransparencyEnabled()
-```
-
-**iOS-Only.** Query whether reduce transparency is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when a reduce transparency is enabled and `false` otherwise.
-
-### `isScreenReaderEnabled()`
-
-```jsx
-static isScreenReaderEnabled()
-```
-
-Query whether a screen reader is currently enabled. Returns a promise which resolves to a boolean. The result is `true` when a screen reader is enabled and `false` otherwise.
-
----
-
-### `addEventListener()`
-
-```jsx
-static addEventListener(eventName, handler)
-```
-
-Add an event handler. Supported events:
-
-- `boldTextChanged`: iOS-only event. Fires when the state of the bold text toggle changes. The argument to the event handler is a boolean. The boolean is `true` when bold text is enabled and `false` otherwise.
-- `grayscaleChanged`: iOS-only event. Fires when the state of the gray scale toggle changes. The argument to the event handler is a boolean. The boolean is `true` when a gray scale is enabled and `false` otherwise.
-- `invertColorsChanged`: iOS-only event. Fires when the state of the invert colors toggle changes. The argument to the event handler is a boolean. The boolean is `true` when invert colors is enabled and `false` otherwise.
-- `reduceMotionChanged`: Fires when the state of the reduce motion toggle changes. The argument to the event handler is a boolean. The boolean is `true` when a reduce motion is enabled (or when "Transition Animation Scale" in "Developer options" is "Animation off") and `false` otherwise.
-- `screenReaderChanged`: Fires when the state of the screen reader changes. The argument to the event handler is a boolean. The boolean is `true` when a screen reader is enabled and `false` otherwise.
-- `reduceTransparencyChanged`: iOS-only event. Fires when the state of the reduce transparency toggle changes. The argument to the event handler is a boolean. The boolean is `true` when reduce transparency is enabled and `false` otherwise.
-- `announcementFinished`: iOS-only event. Fires when the screen reader has finished making an announcement. The argument to the event handler is a dictionary with these keys:
- - `announcement`: The string announced by the screen reader.
- - `success`: A boolean indicating whether the announcement was successfully made.
-
----
-
-### `setAccessibilityFocus()`
-
-```jsx
-static setAccessibilityFocus(reactTag)
-```
-
-Set accessibility focus to a React component. On Android, this is equivalent to `UIManager.sendAccessibilityEvent(reactTag, UIManager.AccessibilityEventTypes.typeViewFocused);`.
-
----
-
-### `announceForAccessibility()`
-
-```jsx
-static announceForAccessibility(announcement)
-```
-
-Post a string to be announced by the screen reader.
-
----
-
-### `removeEventListener()`
-
-```jsx
-static removeEventListener(eventName, handler)
-```
-
-Remove an event handler.
diff --git a/website/versioned_docs/version-0.61/actionsheetios.md b/website/versioned_docs/version-0.61/actionsheetios.md
deleted file mode 100644
index 9d55bd16baa..00000000000
--- a/website/versioned_docs/version-0.61/actionsheetios.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-id: actionsheetios
-title: ActionSheetIOS
----
-
-# Reference
-
-## Methods
-
-### `showActionSheetWithOptions()`
-
-```jsx
-static showActionSheetWithOptions(options, callback)
-```
-
-Display an iOS action sheet. The `options` object must contain one or more of:
-
-- `options` (array of strings) - a list of button titles (required)
-- `cancelButtonIndex` (int) - index of cancel button in `options`
-- `destructiveButtonIndex` (int) - index of destructive button in `options`
-- `title` (string) - a title to show above the action sheet
-- `message` (string) - a message to show below the title
-- `anchor` (number) - the node to which the action sheet should be anchored (used for iPad)
-- `tintColor` (string) - the [color](colors.md) used for non-destructive button titles
-
-The 'callback' function takes one parameter, the zero-based index of the selected item.
-
-Minimal example:
-
-```jsx
-ActionSheetIOS.showActionSheetWithOptions(
- {
- options: ['Cancel', 'Remove'],
- destructiveButtonIndex: 1,
- cancelButtonIndex: 0,
- },
- buttonIndex => {
- if (buttonIndex === 1) {
- /* destructive action */
- }
- },
-);
-```
-
----
-
-### `showShareActionSheetWithOptions()`
-
-```jsx
-static showShareActionSheetWithOptions(options, failureCallback, successCallback)
-```
-
-Display the iOS share sheet. The `options` object should contain one or both of `message` and `url` and can additionally have a `subject` or `excludedActivityTypes`:
-
-- `url` (string) - a URL to share
-- `message` (string) - a message to share
-- `subject` (string) - a subject for the message
-- `excludedActivityTypes` (array) - the activities to exclude from the ActionSheet
-
-NOTE: if `url` points to a local file, or is a base64-encoded uri, the file it points to will be loaded and shared directly. In this way, you can share images, videos, PDF files, etc.
-
-The 'failureCallback' function takes one parameter, an error object. The only property defined on this object is an optional `stack` property of type `string`.
-
-The 'successCallback' function takes two parameters:
-
-- a boolean value signifying success or failure
-- a string that, in the case of success, indicates the method of sharing
diff --git a/website/versioned_docs/version-0.61/activityindicator.md b/website/versioned_docs/version-0.61/activityindicator.md
deleted file mode 100644
index ca2fe6bdb81..00000000000
--- a/website/versioned_docs/version-0.61/activityindicator.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-id: activityindicator
-title: ActivityIndicator
----
-
-Displays a circular loading indicator.
-
-### Example
-
-```SnackPlayer name=activityindicator
-import React, { Component } from 'react'
-import {
- ActivityIndicator,
- StyleSheet,
- Text,
- View,
-} from 'react-native'
-
-export default class App extends Component {
- render() {
- return (
-
-
- )
- }
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- justifyContent: 'center'
- },
- horizontal: {
- flexDirection: 'row',
- justifyContent: 'space-around',
- padding: 10
- }
-})
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view.md#props).
-
-### `animating`
-
-Whether to show the indicator (true, the default) or hide it (false).
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `color`
-
-The foreground color of the spinner (default is gray on iOS and dark cyan on Android).
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `hidesWhenStopped`
-
-Whether the indicator should hide when not animating (true by default).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
----
-
-### `size`
-
-Size of the indicator (default is 'small'). Passing a number to the size prop is only supported on Android.
-
-| Type | Required |
-| ------------------------------ | -------- |
-| enum('small', 'large'), number | No |
diff --git a/website/versioned_docs/version-0.61/alert.md b/website/versioned_docs/version-0.61/alert.md
deleted file mode 100644
index f731ece5a71..00000000000
--- a/website/versioned_docs/version-0.61/alert.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-id: alert
-title: Alert
----
-
-Launches an alert dialog with the specified title and message.
-
-Optionally provide a list of buttons. Tapping any button will fire the respective onPress callback and dismiss the alert. By default, the only button will be an 'OK' button.
-
-This is an API that works both on Android and iOS and can show static alerts. To show an alert that prompts the user to enter some information, see `AlertIOS`; entering text in an alert is common on iOS only.
-
-## Example
-
-
-
- iOS
- Android
-
-
-
-
-
-
-
-
-
-## iOS
-
-On iOS you can specify any number of buttons. Each button can optionally specify a style, which is one of 'default', 'cancel' or 'destructive'.
-
-## Android
-
-On Android at most three buttons can be specified. Android has a concept of a neutral, negative and a positive button:
-
-- If you specify one button, it will be the 'positive' one (such as 'OK')
-- Two buttons mean 'negative', 'positive' (such as 'Cancel', 'OK')
-- Three buttons mean 'neutral', 'negative', 'positive' (such as 'Later', 'Cancel', 'OK')
-
-By default alerts on Android can be dismissed by tapping outside of the alert box. This event can be handled by providing an optional options parameter, with an onDismiss callback property { onDismiss: () => {} }.
-
-Alternatively, the dismissing behavior can be disabled altogether by providing an optional options parameter with the cancelable property set to false i.e. { cancelable: false }
-
-Example usage:
-
-```jsx
-// Works on both Android and iOS
-Alert.alert(
- 'Alert Title',
- 'My Alert Msg',
- [
- {
- text: 'Ask me later',
- onPress: () => console.log('Ask me later pressed'),
- },
- {
- text: 'Cancel',
- onPress: () => console.log('Cancel Pressed'),
- style: 'cancel',
- },
- {text: 'OK', onPress: () => console.log('OK Pressed')},
- ],
- {cancelable: false},
-);
-```
-
----
-
-# Reference
-
-## Methods
-
-### `alert()`
-
-```jsx
-static alert(title, message?, buttons?, options? type?)
-```
diff --git a/website/versioned_docs/version-0.61/alertios.md b/website/versioned_docs/version-0.61/alertios.md
deleted file mode 100644
index 633925b0293..00000000000
--- a/website/versioned_docs/version-0.61/alertios.md
+++ /dev/null
@@ -1,190 +0,0 @@
----
-id: alertios
-title: '🚧 AlertIOS'
----
-
-> **Deprecated.** Use [`Alert`](alert) instead.
-
-`AlertIOS` provides functionality to create an iOS alert dialog with a message or create a prompt for user input.
-
-Creating an iOS alert:
-
-```jsx
-AlertIOS.alert(
- 'Sync Complete',
- 'All your data are belong to us.',
-);
-```
-
-Creating an iOS prompt:
-
-```jsx
-AlertIOS.prompt('Enter a value', null, text =>
- console.log('You entered ' + text),
-);
-```
-
-We recommend using the [`Alert.alert`](alert.md) method for cross-platform support if you don't need to create iOS-only prompts.
-
----
-
-# Reference
-
-## Methods
-
-### `alert()`
-
-```jsx
-static alert(title: string, [message]: string, [callbackOrButtons]: ?(() => void), ButtonsArray, [type]: AlertType): [object Object]
-```
-
-Create and display a popup alert.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----------------- | ------------------------------------------------------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| title | string | Yes | The dialog's title. Passing null or '' will hide the title. |
-| message | string | No | An optional message that appears below the dialog's title. |
-| callbackOrButtons | ?(() => void),[ButtonsArray](alertios.md#buttonsarray) | No | This optional argument should be either a single-argument function or an array of buttons. If passed a function, it will be called when the user taps 'OK'. If passed an array of button configurations, each button should include a `text` key, as well as optional `onPress` and `style` keys. `style` should be one of 'default', 'cancel' or 'destructive'. |
-| type | [AlertType](alertios.md#alerttype) | No | Deprecated, do not use. |
-
-Example with custom buttons:
-
-```jsx
-AlertIOS.alert(
- 'Update available',
- 'Keep your app up to date to enjoy the latest features',
- [
- {
- text: 'Cancel',
- onPress: () => console.log('Cancel Pressed'),
- style: 'cancel',
- },
- {
- text: 'Install',
- onPress: () => console.log('Install Pressed'),
- },
- ],
-);
-```
-
----
-
-### `prompt()`
-
-```jsx
-static prompt(title: string, [message]: string, [callbackOrButtons]: ?((text: string) => void), ButtonsArray, [type]: AlertType, [defaultValue]: string, [keyboardType]: string): [object Object]
-```
-
-Create and display a prompt to enter some text.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----------------- | ------------------------------------------------------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| title | string | Yes | The dialog's title. |
-| message | string | No | An optional message that appears above the text input. |
-| callbackOrButtons | ?((text: string) => void),[ButtonsArray](alertios.md#buttonsarray) | No | This optional argument should be either a single-argument function or an array of buttons. If passed a function, it will be called with the prompt's value when the user taps 'OK'. If passed an array of button configurations, each button should include a `text` key, as well as optional `onPress` and `style` keys (see example). `style` should be one of 'default', 'cancel' or 'destructive'. |
-| type | [AlertType](alertios.md#alerttype) | No | This configures the text input. One of 'plain-text', 'secure-text' or 'login-password'. |
-| defaultValue | string | No | The default text in text input. |
-| keyboardType | string | No | The keyboard type of first text field(if exists). One of 'default', 'email-address', 'numeric', 'phone-pad', 'ascii-capable', 'numbers-and-punctuation', 'url', 'number-pad', 'name-phone-pad', 'decimal-pad', 'twitter' or 'web-search'. |
-
-Example with custom buttons:
-
-```jsx
-AlertIOS.prompt(
- 'Enter password',
- 'Enter your password to claim your $1.5B in lottery winnings',
- [
- {
- text: 'Cancel',
- onPress: () => console.log('Cancel Pressed'),
- style: 'cancel',
- },
- {
- text: 'OK',
- onPress: password =>
- console.log('OK Pressed, password: ' + password),
- },
- ],
- 'secure-text',
-);
-```
-
-,
-
-Example with the default button and a custom callback:
-
-```jsx
-AlertIOS.prompt(
- 'Update username',
- null,
- text => console.log('Your username is ' + text),
- null,
- 'default',
-);
-```
-
-## Type Definitions
-
-### AlertType
-
-An Alert button type
-
-| Type |
-| ------ |
-| \$Enum |
-
-**Constants:**
-
-| Value | Description |
-| -------------- | ---------------------------- |
-| default | Default alert with no inputs |
-| plain-text | Plain text input alert |
-| secure-text | Secure text input alert |
-| login-password | Login and password alert |
-
----
-
-### AlertButtonStyle
-
-An Alert button style
-
-| Type |
-| ------ |
-| \$Enum |
-
-**Constants:**
-
-| Value | Description |
-| ----------- | ------------------------ |
-| default | Default button style |
-| cancel | Cancel button style |
-| destructive | Destructive button style |
-
----
-
-### ButtonsArray
-
-Array or buttons
-
-| Type |
-| ----- |
-| Array |
-
-**Properties:**
-
-| Name | Type | Description |
-| --------- | ------------------------------------------------ | ------------------------------------- |
-| [text] | string | Button label |
-| [onPress] | function | Callback function when button pressed |
-| [style] | [AlertButtonStyle](alertios.md#alertbuttonstyle) | Button style |
-
-**Constants:**
-
-| Value | Description |
-| ------- | ------------------------------------- |
-| text | Button label |
-| onPress | Callback function when button pressed |
-| style | Button style |
diff --git a/website/versioned_docs/version-0.61/animated.md b/website/versioned_docs/version-0.61/animated.md
deleted file mode 100644
index 12a1ba07180..00000000000
--- a/website/versioned_docs/version-0.61/animated.md
+++ /dev/null
@@ -1,391 +0,0 @@
----
-id: animated
-title: Animated
----
-
-The `Animated` library is designed to make animations fluid, powerful, and painless to build and maintain. `Animated` focuses on declarative relationships between inputs and outputs, with configurable transforms in between, and `start`/`stop` methods to control time-based animation execution.
-
-The most basic workflow for creating an animation is to create an `Animated.Value`, hook it up to one or more style attributes of an animated component, and then drive updates via animations using `Animated.timing()`:
-
-```jsx
-Animated.timing(
- // Animate value over time
- this.state.fadeAnim, // The value to drive
- {
- toValue: 1, // Animate to final value of 1
- },
-).start(); // Start the animation
-```
-
-Refer to the [Animations](animations.md#animated-api) guide to see additional examples of `Animated` in action.
-
-## Overview
-
-There are two value types you can use with `Animated`:
-
-- [`Animated.Value()`](animated.md#value) for single values
-- [`Animated.ValueXY()`](animated.md#valuexy) for vectors
-
-`Animated.Value` can bind to style properties or other props, and can be interpolated as well. A single `Animated.Value` can drive any number of properties.
-
-### Configuring animations
-
-`Animated` provides three types of animation types. Each animation type provides a particular animation curve that controls how your values animate from their initial value to the final value:
-
-- [`Animated.decay()`](animated.md#decay) starts with an initial velocity and gradually slows to a stop.
-- [`Animated.spring()`](animated.md#spring) provides a basic spring physics model.
-- [`Animated.timing()`](animated.md#timing) animates a value over time using [easing functions](easing.md).
-
-In most cases, you will be using `timing()`. By default, it uses a symmetric easeInOut curve that conveys the gradual acceleration of an object to full speed and concludes by gradually decelerating to a stop.
-
-### Working with animations
-
-Animations are started by calling `start()` on your animation. `start()` takes a completion callback that will be called when the animation is done. If the animation finished running normally, the completion callback will be invoked with `{finished: true}`. If the animation is done because `stop()` was called on it before it could finish (e.g. because it was interrupted by a gesture or another animation), then it will receive `{finished: false}`.
-
-### Using the native driver
-
-By using the native driver, 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.
-
-You can use the native driver by specifying `useNativeDriver: true` in your animation configuration. See the [Animations](animations.md#using-the-native-driver) guide to learn more.
-
-### Animatable components
-
-Only animatable components can be animated. These unique components do the magic of binding the animated values to the properties, and do targeted native updates to avoid the cost of the react render and reconciliation process on every frame. They also handle cleanup on unmount so they are safe by default.
-
-- [`createAnimatedComponent()`](animated.md#createanimatedcomponent) can be used to make a component animatable.
-
-`Animated` exports the following animatable components using the above wrapper:
-
-- `Animated.Image`
-- `Animated.ScrollView`
-- `Animated.Text`
-- `Animated.View`
-- `Animated.FlatList`
-- `Animated.SectionList`
-
-### Composing animations
-
-Animations can also be combined in complex ways using composition functions:
-
-- [`Animated.delay()`](animated.md#delay) starts an animation after a given delay.
-- [`Animated.parallel()`](animated.md#parallel) starts a number of animations at the same time.
-- [`Animated.sequence()`](animated.md#sequence) starts the animations in order, waiting for each to complete before starting the next.
-- [`Animated.stagger()`](animated.md#stagger) starts animations in order and in parallel, but with successive delays.
-
-Animations can also be chained together by setting the `toValue` of one animation to be another `Animated.Value`. See [Tracking dynamic values](animations.md#tracking-dynamic-values) in the Animations guide.
-
-By default, if one animation is stopped or interrupted, then all other animations in the group are also stopped.
-
-### Combining animated values
-
-You can combine two animated values via addition, subtraction, multiplication, division, or modulo to make a new animated value:
-
-- [`Animated.add()`](animated.md#add)
-- [`Animated.subtract()`](animated.md#subtract)
-- [`Animated.divide()`](animated.md#divide)
-- [`Animated.modulo()`](animated.md#modulo)
-- [`Animated.multiply()`](animated.md#multiply)
-
-### Interpolation
-
-The `interpolate()` function allows input ranges to map to different output ranges. By default, it will extrapolate the curve beyond the ranges given, but you can also have it clamp the output value. It uses linear interpolation by default but also supports easing functions.
-
-- [`interpolate()`](animated.md#interpolate)
-
-Read more about interpolation in the [Animation](animations.md#interpolation) guide.
-
-### Handling gestures and other events
-
-Gestures, like panning or scrolling, and other events can map directly to animated values using `Animated.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.
-
-- [`Animated.event()`](animated.md#event)
-
-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
- }
- }
- }]
- )}
-```
-
----
-
-# Reference
-
-## Methods
-
-When the given value is a ValueXY instead of a Value, each config option may be a vector of the form `{x: ..., y: ...}` instead of a scalar.
-
-### `decay()`
-
-```jsx
-static decay(value, config)
-```
-
-Animates a value from an initial velocity to zero based on a decay coefficient.
-
-Config is an object that may have the following options:
-
-- `velocity`: Initial velocity. Required.
-- `deceleration`: Rate of decay. Default 0.997.
-- `isInteraction`: Whether or not this animation creates an "interaction handle" on the `InteractionManager`. Default true.
-- `useNativeDriver`: Uses the native driver when true. Default false.
-
----
-
-### `timing()`
-
-```jsx
-static timing(value, config)
-```
-
-Animates a value along a timed easing curve. The [`Easing`](easing.md) module has tons of predefined curves, or you can use your own function.
-
-Config is an object that may have the following options:
-
-- `duration`: Length of animation (milliseconds). Default 500.
-- `easing`: Easing function to define curve. Default is `Easing.inOut(Easing.ease)`.
-- `delay`: Start the animation after delay (milliseconds). Default 0.
-- `isInteraction`: Whether or not this animation creates an "interaction handle" on the `InteractionManager`. Default true.
-- `useNativeDriver`: Uses the native driver when true. Default false.
-
----
-
-### `spring()`
-
-```jsx
-static spring(value, config)
-```
-
-Animates a value according to an analytical spring model based on [damped harmonic oscillation](https://en.wikipedia.org/wiki/Harmonic_oscillator#Damped_harmonic_oscillator). Tracks velocity state to create fluid motions as the `toValue` updates, and can be chained together.
-
-Config is an object that may have the following options.
-
-Note that you can only define one of bounciness/speed, tension/friction, or stiffness/damping/mass, but not more than one:
-
-The friction/tension or bounciness/speed options match the spring model in [`Facebook Pop`](https://github.com/facebook/pop), [Rebound](https://github.com/facebookarchive/rebound), and [Origami](http://origami.design/).
-
-- `friction`: Controls "bounciness"/overshoot. Default 7.
-- `tension`: Controls speed. Default 40.
-- `speed`: Controls speed of the animation. Default 12.
-- `bounciness`: Controls bounciness. Default 8.
-
-Specifying stiffness/damping/mass as parameters makes `Animated.spring` use an analytical spring model based on the motion equations of a [damped harmonic oscillator](https://en.wikipedia.org/wiki/Harmonic_oscillator#Damped_harmonic_oscillator). This behavior is slightly more precise and faithful to the physics behind spring dynamics, and closely mimics the implementation in iOS's CASpringAnimation.
-
-- `stiffness`: The spring stiffness coefficient. Default 100.
-- `damping`: Defines how the spring’s motion should be damped due to the forces of friction. Default 10.
-- `mass`: The mass of the object attached to the end of the spring. Default 1.
-
-Other configuration options are as follows:
-
-- `velocity`: The initial velocity of the object attached to the spring. Default 0 (object is at rest).
-- `overshootClamping`: Boolean indicating whether the spring should be clamped and not bounce. Default false.
-- `restDisplacementThreshold`: The threshold of displacement from rest below which the spring should be considered at rest. Default 0.001.
-- `restSpeedThreshold`: The speed at which the spring should be considered at rest in pixels per second. Default 0.001.
-- `delay`: Start the animation after delay (milliseconds). Default 0.
-- `isInteraction`: Whether or not this animation creates an "interaction handle" on the `InteractionManager`. Default true.
-- `useNativeDriver`: Uses the native driver when true. Default false.
-
----
-
-### `add()`
-
-```jsx
-static add(a, b)
-```
-
-Creates a new Animated value composed from two Animated values added together.
-
----
-
-### `subtract()`
-
-```jsx
-static subtract(a, b)
-```
-
-Creates a new Animated value composed by subtracting the second Animated value from the first Animated value.
-
----
-
-### `divide()`
-
-```jsx
-static divide(a, b)
-```
-
-Creates a new Animated value composed by dividing the first Animated value by the second Animated value.
-
----
-
-### `multiply()`
-
-```jsx
-static multiply(a, b)
-```
-
-Creates a new Animated value composed from two Animated values multiplied together.
-
----
-
-### `modulo()`
-
-```jsx
-static modulo(a, modulus)
-```
-
-Creates a new Animated value that is the (non-negative) modulo of the provided Animated value
-
----
-
-### `diffClamp()`
-
-```jsx
-static diffClamp(a, min, max)
-```
-
-Create a new Animated value that is limited between 2 values. It uses the difference between the last value so even if the value is far from the bounds it will start changing when the value starts getting closer again. (`value = clamp(value + diff, min, max)`).
-
-This is useful with scroll events, for example, to show the navbar when scrolling up and to hide it when scrolling down.
-
----
-
-### `delay()`
-
-```jsx
-static delay(time)
-```
-
-Starts an animation after the given delay.
-
----
-
-### `sequence()`
-
-```jsx
-static sequence(animations)
-```
-
-Starts an array of animations in order, waiting for each to complete before starting the next. If the current running animation is stopped, no following animations will be started.
-
----
-
-### `parallel()`
-
-```jsx
-static parallel(animations, config?)
-```
-
-Starts an array of animations all at the same time. By default, if one of the animations is stopped, they will all be stopped. You can override this with the `stopTogether` flag.
-
----
-
-### `stagger()`
-
-```jsx
-static stagger(time, animations)
-```
-
-Array of animations may run in parallel (overlap), but are started in sequence with successive delays. Nice for doing trailing effects.
-
----
-
-### `loop()`
-
-```jsx
-static loop(animation, config?)
-```
-
-Loops a given animation continuously, so that each time it reaches the end, it resets and begins again from the start. Will loop without blocking the UI thread if the child animation is set to `useNativeDriver: true`. In addition, loops can prevent `VirtualizedList`-based components from rendering more rows while the animation is running. You can pass `isInteraction: false` in the child animation config to fix this.
-
-Config is an object that may have the following options:
-
-- `iterations`: Number of times the animation should loop. Default `-1` (infinite).
-
----
-
-### `event()`
-
-```jsx
-static event(argMapping, config?)
-```
-
-Takes an array of mappings and extracts values from each arg accordingly, then calls `setValue` on the mapped outputs. e.g.
-
-```jsx
- onScroll={Animated.event(
- [{nativeEvent: {contentOffset: {x: this._scrollX}}}],
- {listener: (event) => console.log(event)}, // Optional async listener
- )}
- ...
- onPanResponderMove: Animated.event([
- null, // raw event arg ignored
- {dx: this._panX}], // gestureState arg
-{listener: (event, gestureState) => console.log(event, gestureState)}, // Optional async listener
- ),
-```
-
-Config is an object that may have the following options:
-
-- `listener`: Optional async listener.
-- `useNativeDriver`: Uses the native driver when true. Default false.
-
----
-
-### `forkEvent()`
-
-```jsx
-static forkEvent(event, listener)
-```
-
-Advanced imperative API for snooping on animated events that are passed in through props. It permits to add a new javascript listener to an existing `AnimatedEvent`. If `animatedEvent` is a javascript listener, it will merge the 2 listeners into a single one, and if `animatedEvent` is null/undefined, it will assign the javascript listener directly. Use values directly where possible.
-
----
-
-### `unforkEvent()`
-
-```jsx
-static unforkEvent(event, listener)
-```
-
-## Properties
-
-### `Value`
-
-Standard value class for driving animations. Typically initialized with `new Animated.Value(0);`
-
----
-
-### `ValueXY`
-
-2D value class for driving 2D animations, such as pan gestures.
-
----
-
-### `Interpolation`
-
-Exported to use the Interpolation type in flow.
-
----
-
-### `Node`
-
-Exported for ease of type checking. All animated values derive from this class.
-
----
-
-### `createAnimatedComponent`
-
-Make any React component Animatable. Used to create `Animated.View`, etc.
-
----
-
-### `attachNativeEvent`
-
-Imperative API to attach an animated value to an event on a view. Prefer using `Animated.event` with `useNativeDrive: true` if possible.
diff --git a/website/versioned_docs/version-0.61/animatedvalue.md b/website/versioned_docs/version-0.61/animatedvalue.md
deleted file mode 100644
index 6cbc745484c..00000000000
--- a/website/versioned_docs/version-0.61/animatedvalue.md
+++ /dev/null
@@ -1,228 +0,0 @@
----
-id: animatedvalue
-title: AnimatedValue
----
-
-Standard value for driving animations. One `Animated.Value` can drive multiple properties in a synchronized fashion, but can only be driven by one mechanism at a time. Using a new mechanism (e.g. starting a new animation, or calling `setValue`) will stop any previous ones.
-
-Typically initialized with `new Animated.Value(0);`
-
-See also [`Animated`](animated.md).
-
-### Methods
-
-- [`setValue`](animatedvalue.md#setvalue)
-- [`setOffset`](animatedvalue.md#setoffset)
-- [`flattenOffset`](animatedvalue.md#flattenoffset)
-- [`extractOffset`](animatedvalue.md#extractoffset)
-- [`addListener`](animatedvalue.md#addlistener)
-- [`removeListener`](animatedvalue.md#removelistener)
-- [`removeAllListeners`](animatedvalue.md#removealllisteners)
-- [`stopAnimation`](animatedvalue.md#stopanimation)
-- [`resetAnimation`](animatedvalue.md#resetanimation)
-- [`interpolate`](animatedvalue.md#interpolate)
-- [`animate`](animatedvalue.md#animate)
-- [`stopTracking`](animatedvalue.md#stoptracking)
-- [`track`](animatedvalue.md#track)
-
----
-
-# Reference
-
-## Methods
-
-### `setValue()`
-
-```jsx
-setValue(value);
-```
-
-Directly set the value. This will stop any animations running on the value and update all the bound properties.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----- | ------ | -------- | ----------- |
-| value | number | Yes | Value |
-
----
-
-### `setOffset()`
-
-```jsx
-setOffset(offset);
-```
-
-Sets an offset that is applied on top of whatever value is set, whether via `setValue`, an animation, or `Animated.event`. Useful for compensating things like the start of a pan gesture.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ------------ |
-| offset | number | Yes | Offset value |
-
----
-
-### `flattenOffset()`
-
-```jsx
-flattenOffset();
-```
-
-Merges the offset value into the base value and resets the offset to zero. The final output of the value is unchanged.
-
----
-
-### `extractOffset()`
-
-```jsx
-extractOffset();
-```
-
-Sets the offset value to the base value, and resets the base value to zero. The final output of the value is unchanged.
-
----
-
-### `addListener()`
-
-```jsx
-addListener(callback);
-```
-
-Adds an asynchronous listener to the value so you can observe updates from animations. This is useful because there is no way to synchronously read the value because it might be driven natively.
-
-Returns a string that serves as an identifier for the listener.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | ------------------------------------------------------------------------------------------- |
-| callback | function | Yes | The callback function which will receive an object with a `value` key set to the new value. |
-
----
-
-### `removeListener()`
-
-```jsx
-removeListener(id);
-```
-
-Unregister a listener. The `id` param shall match the identifier previously returned by `addListener()`.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ---- | ------ | -------- | ---------------------------------- |
-| id | string | Yes | Id for the listener being removed. |
-
----
-
-### `removeAllListeners()`
-
-```jsx
-removeAllListeners();
-```
-
-Remove all registered listeners.
-
----
-
-### `stopAnimation()`
-
-```jsx
-stopAnimation([callback]);
-```
-
-Stops any running animation or tracking. `callback` is invoked with the final value after stopping the animation, which is useful for updating state to match the animation position with layout.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | --------------------------------------------- |
-| callback | function | No | A function that will receive the final value. |
-
----
-
-### `resetAnimation()`
-
-```jsx
-resetAnimation([callback]);
-```
-
-Stops any animation and resets the value to its original.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | ------------------------------------------------ |
-| callback | function | No | A function that will receive the original value. |
-
----
-
-### `interpolate()`
-
-```jsx
-interpolate(config);
-```
-
-Interpolates the value before updating the property, e.g. mapping 0-1 to 0-10.
-
-See `AnimatedInterpolation.js`
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ----------- |
-| config | object | Yes | See below. |
-
-The `config` object is composed of the following keys:
-
-- `inputRange`: an array of numbers
-- `outputRange`: an array of numbers or strings
-- `easing` (optional): a function that returns a number, given an input number
-- `extrapolate` (optional): a string such as 'extend', 'identity', or 'clamp'
-- `extrapolateLeft` (optional): a string such as 'extend', 'identity', or 'clamp'
-- `extrapolateRight` (optional): a string such as 'extend', 'identity', or 'clamp'
-
----
-
-### `animate()`
-
-```jsx
-animate(animation, callback);
-```
-
-Typically only used internally, but could be used by a custom Animation class.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| --------- | --------- | -------- | ------------------- |
-| animation | Animation | Yes | See `Animation.js`. |
-| callback | function | Yes | Callback function. |
-
----
-
-### `stopTracking()`
-
-```jsx
-stopTracking();
-```
-
-Typically only used internally.
-
----
-
-### `track()`
-
-```jsx
-track(tracking);
-```
-
-Typically only used internally.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ------------ | -------- | --------------------- |
-| tracking | AnimatedNode | Yes | See `AnimatedNode.js` |
diff --git a/website/versioned_docs/version-0.61/animatedvaluexy.md b/website/versioned_docs/version-0.61/animatedvaluexy.md
deleted file mode 100644
index f89a4403120..00000000000
--- a/website/versioned_docs/version-0.61/animatedvaluexy.md
+++ /dev/null
@@ -1,222 +0,0 @@
----
-id: animatedvaluexy
-title: AnimatedValueXY
----
-
-2D Value for driving 2D animations, such as pan gestures. Almost identical API to normal [`Animated.Value`](animatedvalue.md), but multiplexed. Contains two regular `Animated.Value`s under the hood.
-
-See also [`Animated`](animated.md).
-
-## Example
-
-```jsx
-class DraggableView extends React.Component {
- constructor(props) {
- super(props);
- this.state = {
- pan: new Animated.ValueXY(), // inits to zero
- };
- this.state.panResponder = PanResponder.create({
- onStartShouldSetPanResponder: () => true,
- onPanResponderMove: Animated.event([
- null,
- {
- dx: this.state.pan.x, // x,y are Animated.Value
- dy: this.state.pan.y,
- },
- ]),
- onPanResponderRelease: () => {
- Animated.spring(
- this.state.pan, // Auto-multiplexed
- {toValue: {x: 0, y: 0}}, // Back to zero
- ).start();
- },
- });
- }
- render() {
- return (
-
- {this.props.children}
-
- );
- }
-}
-```
-
-### Methods
-
-- [`setValue`](animatedvaluexy.md#setvalue)
-- [`setOffset`](animatedvaluexy.md#setoffset)
-- [`flattenOffset`](animatedvaluexy.md#flattenoffset)
-- [`extractOffset`](animatedvaluexy.md#extractoffset)
-- [`addListener`](animatedvaluexy.md#addlistener)
-- [`removeListener`](animatedvaluexy.md#removelistener)
-- [`removeAllListeners`](animatedvaluexy.md#removealllisteners)
-- [`stopAnimation`](animatedvaluexy.md#stopanimation)
-- [`resetAnimation`](animatedvaluexy.md#resetanimation)
-- [`getLayout`](animatedvaluexy.md#getlayout)
-- [`getTranslateTransform`](animatedvaluexy.md#gettranslatetransform)
-
----
-
-# Reference
-
-## Methods
-
-### `setValue()`
-
-```jsx
-setValue(value);
-```
-
-Directly set the value. This will stop any animations running on the value and update all the bound properties.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ----- | ------ | -------- | ----------- |
-| value | number | Yes | |
-
----
-
-### `setOffset()`
-
-```jsx
-setOffset(offset);
-```
-
-Sets an offset that is applied on top of whatever value is set, whether via `setValue`, an animation, or `Animated.event`. Useful for compensating things like the start of a pan gesture.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ----------- |
-| offset | number | Yes | |
-
----
-
-### `flattenOffset()`
-
-```jsx
-flattenOffset();
-```
-
-Merges the offset value into the base value and resets the offset to zero. The final output of the value is unchanged.
-
----
-
-### `extractOffset()`
-
-```jsx
-extractOffset();
-```
-
-Sets the offset value to the base value, and resets the base value to zero. The final output of the value is unchanged.
-
----
-
-### `addListener()`
-
-```jsx
-addListener(callback);
-```
-
-Adds an asynchronous listener to the value so you can observe updates from animations. This is useful because there is no way to synchronously read the value because it might be driven natively.
-
-Returns a string that serves as an identifier for the listener.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | ------------------------------------------------------------------------------------------- |
-| callback | function | Yes | The callback function which will receive an object with a `value` key set to the new value. |
-
----
-
-### `removeListener()`
-
-```jsx
-removeListener(id);
-```
-
-Unregister a listener. The `id` param shall match the identifier previously returned by `addListener()`.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ---- | ------ | -------- | ---------------------------------- |
-| id | string | Yes | Id for the listener being removed. |
-
----
-
-### `removeAllListeners()`
-
-```jsx
-removeAllListeners();
-```
-
-Remove all registered listeners.
-
----
-
-### `stopAnimation()`
-
-```jsx
-stopAnimation([callback]);
-```
-
-Stops any running animation or tracking. `callback` is invoked with the final value after stopping the animation, which is useful for updating state to match the animation position with layout.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | --------------------------------------------- |
-| callback | function | No | A function that will receive the final value. |
-
----
-
-### `resetAnimation()`
-
-```jsx
-resetAnimation([callback]);
-```
-
-Stops any animation and resets the value to its original.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------- | -------- | ------------------------------------------------ |
-| callback | function | No | A function that will receive the original value. |
-
----
-
-### `getLayout()`
-
-```jsx
-getLayout();
-```
-
-Converts `{x, y}` into `{left, top}` for use in style, e.g.
-
-```jsx
-style={this.state.anim.getLayout()}
-```
-
----
-
-### `getTranslateTransform()`
-
-```jsx
-getTranslateTransform();
-```
-
-Converts `{x, y}` into a useable translation transform, e.g.
-
-```jsx
-style={{
- transform: this.state.anim.getTranslateTransform()
-}}
-```
diff --git a/website/versioned_docs/version-0.61/animations.md b/website/versioned_docs/version-0.61/animations.md
deleted file mode 100644
index 3ed2555949e..00000000000
--- a/website/versioned_docs/version-0.61/animations.md
+++ /dev/null
@@ -1,408 +0,0 @@
----
-id: animations
-title: 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 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 `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 [fadeAnim] = useState(new Animated.Value(0)) // Initial value for opacity: 0
-
- React.useEffect(() => {
- Animated.timing(
- fadeAnim,
- {
- toValue: 1,
- duration: 10000,
- }
- ).start();
- }, [])
-
- return (
-
- {props.children}
-
- );
-}
-
-// You can then use your `FadeInView` in place of a `View` in your components:
-export default () => {
- return (
-
-
- Fading in
-
-
- )
-}
-```
-
-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, only 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 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 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 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. 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 wrapper that 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 clear 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](/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.
-
-To use the native driver for normal animations 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
-
- {content}
-
-```
-
-You can see the native driver in action by running the [RNTester app](https://github.com/facebook/react-native/tree/0.61-stable/packages/rn-tester/), then loading the Native Animated Example. You can also take a look at the [source code](https://github.com/facebook/react-native/blob/0.61-stable/packages/rn-tester/js/examples/NativeAnimation/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
-
-
-
- Press me!
-
-
-
- );
- }
-}
-
-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/0.61-stable/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](/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.61/app-extensions.md b/website/versioned_docs/version-0.61/app-extensions.md
deleted file mode 100644
index 809cacfe1dd..00000000000
--- a/website/versioned_docs/version-0.61/app-extensions.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-id: app-extensions
-title: 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 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':
-
-
-
-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, you can quickly 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.61/appregistry.md b/website/versioned_docs/version-0.61/appregistry.md
deleted file mode 100644
index 0a1474b6b57..00000000000
--- a/website/versioned_docs/version-0.61/appregistry.md
+++ /dev/null
@@ -1,173 +0,0 @@
----
-id: appregistry
-title: AppRegistry
----
-
-
-
Project with Native Code Required
-
- This API only works in projects made with react-native init
- or in those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Expo documentation..
-
-
Current state is: {this.state.appState} ;
- }
-}
-```
-
-This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state, and the null state will happen only momentarily.
-
----
-
-# Reference
-
-## Events
-
-### `change`
-
-This even is received when the app state has changed. The listener is called with one of [the current app state values](appstate.md#app-states).
-
-### `focus`
-
-[Android only] Received when the app gains focus (the user is interacting with the app).
-
-### `blur`
-
-[Android only] Received when the user is not actively interacting with the app. Useful in situations when the user pulls down the [notification drawer](https://developer.android.com/guide/topics/ui/notifiers/notifications#bar-and-drawer). `AppState` won't change but the `blur` event will get fired.
-
-## Methods
-
-### `addEventListener()`
-
-```jsx
-addEventListener(type, handler);
-```
-
-Add a handler to AppState changes by listening to the `change` event type and providing the handler
-
-
-
----
-
-### `removeEventListener()`
-
-```jsx
-removeEventListener(type, handler);
-```
-
-Remove a handler by passing the `change` event type and the handler
-
-## Properties
-
-### `currentState`
-
-```jsx
-AppState.currentState;
-```
diff --git a/website/versioned_docs/version-0.61/asyncstorage.md b/website/versioned_docs/version-0.61/asyncstorage.md
deleted file mode 100644
index adb0b37f759..00000000000
--- a/website/versioned_docs/version-0.61/asyncstorage.md
+++ /dev/null
@@ -1,365 +0,0 @@
----
-id: asyncstorage
-title: '🚧 AsyncStorage'
----
-
-> **Deprecated.** Use [@react-native-community/async-storage](https://github.com/react-native-community/react-native-async-storage) instead.
-
-`AsyncStorage` is an unencrypted, asynchronous, persistent, key-value storage system that is global to the app. It should be used instead of LocalStorage.
-
-It is recommended that you use an abstraction on top of `AsyncStorage` instead of `AsyncStorage` directly for anything more than light usage since it operates globally.
-
-On iOS, `AsyncStorage` is backed by native code that stores small values in a serialized dictionary and larger values in separate files. On Android, `AsyncStorage` will use either [RocksDB](http://rocksdb.org/) or SQLite based on what is available.
-
-The `AsyncStorage` JavaScript code is a facade that provides a clear JavaScript API, real `Error` objects, and non-multi functions. Each method in the API returns a `Promise` object.
-
-Importing the `AsyncStorage` library:
-
-```jsx
-import {AsyncStorage} from 'react-native';
-```
-
-Persisting data:
-
-```jsx
-_storeData = async () => {
- try {
- await AsyncStorage.setItem(
- '@MySuperStore:key',
- 'I like to save it.',
- );
- } catch (error) {
- // Error saving data
- }
-};
-```
-
-Fetching data:
-
-```jsx
-_retrieveData = async () => {
- try {
- const value = await AsyncStorage.getItem('TASKS');
- if (value !== null) {
- // We have data!!
- console.log(value);
- }
- } catch (error) {
- // Error retrieving data
- }
-};
-```
-
----
-
-# Reference
-
-## Methods
-
-### `getItem()`
-
-```jsx
-static getItem(key: string, [callback]: ?(error: ?Error, result: ?string) => void)
-```
-
-Fetches an item for a `key` and invokes a callback upon completion. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ------------------------------------------- | -------- | ----------------------------------------------------------------- |
-| key | string | Yes | Key of the item to fetch. |
-| callback | `?(error: ?Error, result: ?string) => void` | No | Function that will be called with a result if found or any error. |
-
----
-
-### `setItem()`
-
-```jsx
-static setItem(key: string, value: string, [callback]: ?(error: ?Error) => void)
-```
-
-Sets the value for a `key` and invokes a callback upon completion. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------------------------- | -------- | -------------------------------------------- |
-| key | string | Yes | Key of the item to set. |
-| value | string | Yes | Value to set for the `key`. |
-| callback | `?(error: ?Error) => void` | No | Function that will be called with any error. |
-
----
-
-### `removeItem()`
-
-```jsx
-static removeItem(key: string, [callback]: ?(error: ?Error) => void)
-```
-
-Removes an item for a `key` and invokes a callback upon completion. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------------------------- | -------- | -------------------------------------------- |
-| key | string | Yes | Key of the item to remove. |
-| callback | `?(error: ?Error) => void` | No | Function that will be called with any error. |
-
----
-
-### `mergeItem()`
-
-```jsx
-static mergeItem(key: string, value: string, [callback]: ?(error: ?Error) => void)
-```
-
-Merges an existing `key` value with an input value, assuming both values are stringified JSON. Returns a `Promise` object.
-
-**NOTE:** This is not supported by all native implementations.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------------------------- | -------- | -------------------------------------------- |
-| key | string | Yes | Key of the item to modify. |
-| value | string | Yes | New value to merge for the `key`. |
-| callback | `?(error: ?Error) => void` | No | Function that will be called with any error. |
-
-Example:
-
-```jsx
-let UID123_object = {
- name: 'Chris',
- age: 30,
- traits: {hair: 'brown', eyes: 'brown'},
-};
-// You only need to define what will be added or updated
-let UID123_delta = {
- age: 31,
- traits: {eyes: 'blue', shoe_size: 10},
-};
-
-AsyncStorage.setItem(
- 'UID123',
- JSON.stringify(UID123_object),
- () => {
- AsyncStorage.mergeItem(
- 'UID123',
- JSON.stringify(UID123_delta),
- () => {
- AsyncStorage.getItem('UID123', (err, result) => {
- console.log(result);
- });
- },
- );
- },
-);
-
-// Console log result:
-// => {'name':'Chris','age':31,'traits':
-// {'shoe_size':10,'hair':'brown','eyes':'blue'}}
-```
-
----
-
-### `clear()`
-
-```jsx
-static clear([callback]: ?(error: ?Error) => void)
-```
-
-Erases _all_ `AsyncStorage` for all clients, libraries, etc. You probably don't want to call this; use `removeItem` or `multiRemove` to clear only your app's keys. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | -------------------------- | -------- | -------------------------------------------- |
-| callback | `?(error: ?Error) => void` | No | Function that will be called with any error. |
-
----
-
-### `getAllKeys()`
-
-```jsx
-static getAllKeys([callback]: ?(error: ?Error, keys: ?Array) => void)
-```
-
-Gets _all_ keys known to your app; for all callers, libraries, etc. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ------------------------------------------------ | -------- | --------------------------------------------------------------- |
-| callback | `?(error: ?Error, keys: ?Array) => void` | No | Function that will be called with all keys found and any error. |
-
----
-
-### `flushGetRequests()`
-
-```jsx
-static flushGetRequests(): [object Object]
-```
-
-Flushes any pending requests using a single batch call to get the data.
-
----
-
-### `multiGet()`
-
-```jsx
-static multiGet(keys: Array, [callback]: ?(errors: ?Array, result: ?Array>) => void)
-```
-
-This allows you to batch the fetching of items given an array of `key` inputs. Your callback will be invoked with an array of corresponding key-value pairs found:
-
-```
-multiGet(['k1', 'k2'], cb) -> cb([['k1', 'val1'], ['k2', 'val2']])
-```
-
-The method returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ----------------------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------- |
-| keys | `Array` | Yes | Array of key for the items to get. |
-| callback | `?(errors: ?Array, result: ?Array>) => void` | No | Function that will be called with a key-value array of the results, plus an array of any key-specific errors found. |
-
-Example:
-
-```jsx
-AsyncStorage.getAllKeys((err, keys) => {
- AsyncStorage.multiGet(keys, (err, stores) => {
- stores.map((result, i, store) => {
- // get at each store's key/value so you can work with it
- let key = store[i][0];
- let value = store[i][1];
- });
- });
-});
-```
-
----
-
-### `multiSet()`
-
-```jsx
-static multiSet(keyValuePairs: Array>, [callback]: ?(errors: ?Array) => void)
-```
-
-Use this as a batch operation for storing multiple key-value pairs. When the operation completes you'll get a single callback with any errors:
-
-```
-multiSet([['k1', 'val1'], ['k2', 'val2']], cb);
-```
-
-The method returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------------- | ---------------------------------- | -------- | ---------------------------------------------------------------------------- |
-| keyValuePairs | `Array>` | Yes | Array of key-value array for the items to set. |
-| callback | `?(errors: ?Array) => void` | No | Function that will be called with an array of any key-specific errors found. |
-
----
-
-### `multiRemove()`
-
-```jsx
-static multiRemove(keys: Array, [callback]: ?(errors: ?Array) => void)
-```
-
-Call this to batch the deletion of all keys in the `keys` array. Returns a `Promise` object.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| -------- | ---------------------------------- | -------- | ----------------------------------------------------------------------- |
-| keys | `Array` | Yes | Array of key for the items to delete. |
-| callback | `?(errors: ?Array) => void` | No | Function that will be called an array of any key-specific errors found. |
-
-Example:
-
-```jsx
-let keys = ['k1', 'k2'];
-AsyncStorage.multiRemove(keys, err => {
- // keys k1 & k2 removed, if they existed
- // do most stuff after removal (if you want)
-});
-```
-
----
-
-### `multiMerge()`
-
-```jsx
-static multiMerge(keyValuePairs: Array>, [callback]: ?(errors: ?Array) => void)
-```
-
-Batch operation to merge in existing and new values for a given set of keys. This assumes that the values are stringified JSON. Returns a `Promise` object.
-
-**NOTE**: This is not supported by all native implementations.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------------- | ---------------------------------- | -------- | ---------------------------------------------------------------------------- |
-| keyValuePairs | `Array>` | Yes | Array of key-value array for the items to merge. |
-| callback | `?(errors: ?Array) => void` | No | Function that will be called with an array of any key-specific errors found. |
-
-Example:
-
-```jsx
-// first user, initial values
-let UID234_object = {
- name: 'Chris',
- age: 30,
- traits: {hair: 'brown', eyes: 'brown'},
-};
-
-// first user, delta values
-let UID234_delta = {
- age: 31,
- traits: {eyes: 'blue', shoe_size: 10},
-};
-
-// second user, initial values
-let UID345_object = {
- name: 'Marge',
- age: 25,
- traits: {hair: 'blonde', eyes: 'blue'},
-};
-
-// second user, delta values
-let UID345_delta = {
- age: 26,
- traits: {eyes: 'green', shoe_size: 6},
-};
-
-let multi_set_pairs = [
- ['UID234', JSON.stringify(UID234_object)],
- ['UID345', JSON.stringify(UID345_object)],
-];
-let multi_merge_pairs = [
- ['UID234', JSON.stringify(UID234_delta)],
- ['UID345', JSON.stringify(UID345_delta)],
-];
-
-AsyncStorage.multiSet(multi_set_pairs, err => {
- AsyncStorage.multiMerge(multi_merge_pairs, err => {
- AsyncStorage.multiGet(['UID234', 'UID345'], (err, stores) => {
- stores.map((result, i, store) => {
- let key = store[i][0];
- let val = store[i][1];
- console.log(key, val);
- });
- });
- });
-});
-
-// Console log results:
-// => UID234 {"name":"Chris","age":31,"traits":{"shoe_size":10,"hair":"brown","eyes":"blue"}}
-// => UID345 {"name":"Marge","age":26,"traits":{"shoe_size":6,"hair":"blonde","eyes":"green"}}
-```
diff --git a/website/versioned_docs/version-0.61/backandroid.md b/website/versioned_docs/version-0.61/backandroid.md
deleted file mode 100644
index f8b7a3f6832..00000000000
--- a/website/versioned_docs/version-0.61/backandroid.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-id: backandroid
-title: BackAndroid
----
-
-Deprecated. Use BackHandler instead.
-
-### Methods
-
-- [`exitApp`](backandroid.md#exitapp)
-- [`addEventListener`](backandroid.md#addeventlistener)
-- [`removeEventListener`](backandroid.md#removeeventlistener)
-
----
-
-# Reference
-
-## Methods
-
-### `exitApp()`
-
-```jsx
-static exitApp()
-```
-
----
-
-### `addEventListener()`
-
-```jsx
-static addEventListener(eventName, handler)
-```
-
----
-
-### `removeEventListener()`
-
-```jsx
-static removeEventListener(eventName, handler)
-```
diff --git a/website/versioned_docs/version-0.61/backhandler.md b/website/versioned_docs/version-0.61/backhandler.md
deleted file mode 100644
index 2c9fc9db060..00000000000
--- a/website/versioned_docs/version-0.61/backhandler.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-id: backhandler
-title: BackHandler
----
-
-Detect hardware button presses for back navigation.
-
-Android: Detect hardware back button presses, and programmatically invoke the default back button functionality to exit the app if there are no listeners or if none of the listeners return true.
-
-tvOS: Detect presses of the menu button on the TV remote. (Still to be implemented: programmatically disable menu button handling functionality to exit the app if there are no listeners or if none of the listeners return true.)
-
-iOS: Not applicable.
-
-The event subscriptions are called in reverse order (i.e. last registered subscription first), and if one subscription returns true then subscriptions registered earlier will not be called. Beware: If your app shows an opened `Modal`, BackHandler will not publish any events ([see `Modal` docs](/docs/modal#onrequestclose)).
-
-Example:
-
-```jsx
-BackHandler.addEventListener('hardwareBackPress', function () {
- // this.onMainScreen and this.goBack are just examples, you need to use your own implementation here
- // Typically you would use the navigator here to go to the last state.
-
- if (!this.onMainScreen()) {
- this.goBack();
- return true;
- }
- return false;
-});
-```
-
-Lifecycle example:
-
-```jsx
- componentDidMount() {
- this.backHandler = BackHandler.addEventListener('hardwareBackPress', this.handleBackPress);
- }
-
- componentWillUnmount() {
- this.backHandler.remove()
- }
-
- handleBackPress = () => {
- this.goBack(); // works best when the goBack is async
- return true;
- }
-```
-
-Lifecycle alternative:
-
-```jsx
- componentDidMount() {
- this.backHandler = BackHandler.addEventListener('hardwareBackPress', () => {
- this.goBack(); // works best when the goBack is async
- return true;
- });
- }
-
- componentWillUnmount() {
- this.backHandler.remove();
- }
-```
-
----
-
-# Reference
-
-## Methods
-
-### `addEventListener()`
-
-```jsx
-static addEventListener(eventName, handler)
-```
-
----
-
-### `exitApp()`
-
-```jsx
-static exitApp()
-```
-
----
-
-### `removeEventListener()`
-
-```jsx
-static removeEventListener(eventName, handler)
-```
diff --git a/website/versioned_docs/version-0.61/building-for-tv.md b/website/versioned_docs/version-0.61/building-for-tv.md
deleted file mode 100644
index bc50241af3b..00000000000
--- a/website/versioned_docs/version-0.61/building-for-tv.md
+++ /dev/null
@@ -1,187 +0,0 @@
----
-id: building-for-tv
-title: Building For TV Devices
-hide_table_of_contents: true
----
-
-import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
-
-TV devices support has been implemented with the intention of making existing React Native applications work on Apple TV and Android TV, with few or no changes needed in the JavaScript code for the applications.
-
-
-
-
-
-## Build changes
-
-- _Native layer_: To run React Native project on Android TV make sure to make the following changes to `AndroidManifest.xml`
-
-```xml
-
-
- ...
-
- ...
-
-
- ...
-
-```
-
-- _JavaScript layer_: Support for Android TV has been added to `Platform.android.js`. You can check whether code is running on Android TV by doing
-
-```js
-var Platform = require('Platform');
-var running_on_android_tv = Platform.isTV;
-```
-
-## Code changes
-
-- _Access to touchable controls_: When running on Android TV the Android framework will automatically apply a directional navigation scheme based on relative position of focusable elements in your views. The `Touchable` mixin has code added to detect focus changes and use existing methods to style the components properly and initiate the proper actions when the view is selected using the TV remote, so `TouchableWithoutFeedback`, `TouchableHighlight`, `TouchableOpacity` and `TouchableNativeFeedback` will work as expected. In particular:
-
- - `onFocus` will be executed when the touchable view goes into focus
- - `onBlur` will be executed when the touchable view goes out of focus
- - `onPress` will be executed when the touchable view is actually selected by pressing the "select" button on the TV remote.
-
-- _TV remote/keyboard input_: A new native class, `ReactAndroidTVRootViewHelper`, sets up key events handlers for TV remote events. When TV remote events occur, this class fires a JS event. This event will be picked up by instances of the `TVEventHandler` JavaScript object. Application code that needs to implement custom handling of TV remote events can create an instance of `TVEventHandler` and listen for these events, as in the following code:
-
-```jsx
-var TVEventHandler = require('TVEventHandler');
-
-class Game2048 extends React.Component {
- _tvEventHandler: any;
-
- _enableTVEventHandler() {
- this._tvEventHandler = new TVEventHandler();
- this._tvEventHandler.enable(this, function (cmp, evt) {
- if (evt && evt.eventType === 'right') {
- cmp.setState({board: cmp.state.board.move(2)});
- } else if (evt && evt.eventType === 'up') {
- cmp.setState({board: cmp.state.board.move(1)});
- } else if (evt && evt.eventType === 'left') {
- cmp.setState({board: cmp.state.board.move(0)});
- } else if (evt && evt.eventType === 'down') {
- cmp.setState({board: cmp.state.board.move(3)});
- } else if (evt && evt.eventType === 'playPause') {
- cmp.restartGame();
- }
- });
- }
-
- _disableTVEventHandler() {
- if (this._tvEventHandler) {
- this._tvEventHandler.disable();
- delete this._tvEventHandler;
- }
- }
-
- componentDidMount() {
- this._enableTVEventHandler();
- }
-
- componentWillUnmount() {
- this._disableTVEventHandler();
- }
-}
-```
-
-- _Dev Menu support_: On the simulator, cmd-M will bring up the developer menu, similar to Android. To bring it up on a real Android TV device, press the menu button or long press the fast-forward button on the remote. (Please do not shake the Android TV device, that will not work :) )
-
-- _Known issues_:
-
- - `InputText` components do not work for now (i.e. they cannot receive focus).
-
-
-
-
-> **Deprecated.** Use [react-native-tvos](https://github.com/react-native-community/react-native-tvos) instead. For the details please check the [0.62 release blog post](https://reactnative.dev/blog/#moving-apple-tv-to-react-native-tvos).
-
-## Build changes
-
-- _Native layer_: React Native Xcode projects all now have Apple TV build targets, with names ending in the string '-tvOS'.
-
-- _react-native init_: New React Native projects created with `react-native init` will have Apple TV target automatically created in their XCode projects.
-
-- _JavaScript layer_: Support for Apple TV has been added to `Platform.ios.js`. You can check whether code is running on AppleTV by doing
-
-```jsx
-var Platform = require('Platform');
-var running_on_tv = Platform.isTV;
-
-// If you want to be more specific and only detect devices running tvOS
-// (but no Android TV devices) you can use:
-var running_on_apple_tv = Platform.isTVOS;
-```
-
-## Code changes
-
-- _General support for tvOS_: Apple TV specific changes in native code are all wrapped by the TARGET_OS_TV define. These include changes to suppress APIs that are not supported on tvOS (e.g. web views, sliders, switches, status bar, etc.), and changes to support user input from the TV remote or keyboard.
-
-- _Common codebase_: Since tvOS and iOS share most Objective-C and JavaScript code in common, most documentation for iOS applies equally to tvOS.
-
-- _Access to touchable controls_: When running on Apple TV, the native view class is `RCTTVView`, which has additional methods to make use of the tvOS focus engine. The `Touchable` mixin has code added to detect focus changes and use existing methods to style the components properly and initiate the proper actions when the view is selected using the TV remote, so `TouchableWithoutFeedback`, `TouchableHighlight` and `TouchableOpacity` will work as expected. In particular:
-
- - `onFocus` will be executed when the touchable view goes into focus
- - `onBlur` will be executed when the touchable view goes out of focus
- - `onPress` will be executed when the touchable view is actually selected by pressing the "select" button on the TV remote.
-
-- _TV remote/keyboard input_: A new native class, `RCTTVRemoteHandler`, sets up gesture recognizers for TV remote events. When TV remote events occur, this class fires notifications that are picked up by `RCTTVNavigationEventEmitter` (a subclass of `RCTEventEmitter`), that fires a JS event. This event will be picked up by instances of the `TVEventHandler` JavaScript object. Application code that needs to implement custom handling of TV remote events can create an instance of `TVEventHandler` and listen for these events, as in the following code:
-
-```jsx
-var TVEventHandler = require('TVEventHandler');
-
-class Game2048 extends React.Component {
- _tvEventHandler: any;
-
- _enableTVEventHandler() {
- this._tvEventHandler = new TVEventHandler();
- this._tvEventHandler.enable(this, function (cmp, evt) {
- if (evt && evt.eventType === 'right') {
- cmp.setState({board: cmp.state.board.move(2)});
- } else if (evt && evt.eventType === 'up') {
- cmp.setState({board: cmp.state.board.move(1)});
- } else if (evt && evt.eventType === 'left') {
- cmp.setState({board: cmp.state.board.move(0)});
- } else if (evt && evt.eventType === 'down') {
- cmp.setState({board: cmp.state.board.move(3)});
- } else if (evt && evt.eventType === 'playPause') {
- cmp.restartGame();
- }
- });
- }
-
- _disableTVEventHandler() {
- if (this._tvEventHandler) {
- this._tvEventHandler.disable();
- delete this._tvEventHandler;
- }
- }
-
- componentDidMount() {
- this._enableTVEventHandler();
- }
-
- componentWillUnmount() {
- this._disableTVEventHandler();
- }
-}
-```
-
-- _Dev Menu support_: On the simulator, cmd-D will bring up the developer menu, similar to iOS. To bring it up on a real Apple TV device, make a long press on the play/pause button on the remote. (Please do not shake the Apple TV device, that will not work :) )
-
-- _TV remote animations_: `RCTTVView` native code implements Apple-recommended parallax animations to help guide the eye as the user navigates through views. The animations can be disabled or adjusted with new optional view properties.
-
-- _Back navigation with the TV remote menu button_: The `BackHandler` component, originally written to support the Android back button, now also supports back navigation on the Apple TV using the menu button on the TV remote.
-
-- _TabBarIOS behavior_: The `TabBarIOS` component wraps the native `UITabBar` API, which works differently on Apple TV. To avoid jittery re-rendering of the tab bar in tvOS (see [this issue](https://github.com/facebook/react-native/issues/15081)), the selected tab bar item can only be set from JavaScript on initial render, and is controlled after that by the user through native code.
-
-- _Known issues_:
-
- - [ListView scrolling](https://github.com/facebook/react-native/issues/12793). The issue can be worked around by setting `removeClippedSubviews` to false in ListView and similar components. For more discussion of this issue, see [this PR](https://github.com/facebook/react-native/pull/12944).
-
-
-
diff --git a/website/versioned_docs/version-0.61/button.md b/website/versioned_docs/version-0.61/button.md
deleted file mode 100644
index 465cdaaa441..00000000000
--- a/website/versioned_docs/version-0.61/button.md
+++ /dev/null
@@ -1,237 +0,0 @@
----
-id: button
-title: Button
----
-
-A basic button component that should render nicely on any platform. Supports a minimal level of customization.
-
-If this button doesn't look right for your app, you can build your own button using [TouchableOpacity](touchableopacity.md) or [TouchableNativeFeedback](touchablenativefeedback.md). For inspiration, look at the [source code for this button component](https://github.com/facebook/react-native/blob/0.61-stable/Libraries/Components/Button.js). Or, take a look at the [wide variety of button components built by the community](https://js.coach/?menu%5Bcollections%5D=React%20Native&page=1&query=button).
-
-### Example
-
-```SnackPlayer name=rn-buttons
-import React from 'react';
-import {
- StyleSheet,
- Button,
- View,
- SafeAreaView,
- Text,
- Alert,
-} from 'react-native';
-import Constants from 'expo-constants';
-
-function Separator() {
- return
-
-
- The title and onPress handler are required. It is recommended to set
- accessibilityLabel to help make your app usable by everyone.
-
- Alert.alert('Simple Button pressed')}
- />
-
-
-
- Adjust the color in a way that looks standard on each platform. On
- iOS, the color prop controls the color of the text. On Android, the
- color adjusts the backgroud color of the button.
-
- Alert.alert('Button with adjusted color pressed')}
- />
-
-
-
- All interaction for the component are disabled.
-
- Alert.alert('Cannot press this one')}
- />
-
-
-
- This layout strategy lets the title define the width of the button.
-
-
- Alert.alert('Left button pressed')}
- />
- Alert.alert('Right button pressed')}
- />
-
-
-
- );
-}
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- marginTop: Constants.statusBarHeight,
- marginHorizontal: 16,
- },
- title: {
- textAlign: 'center',
- marginVertical: 8,
- },
- fixToText: {
- flexDirection: 'row',
- justifyContent: 'space-between',
- },
- separator: {
- marginVertical: 8,
- borderBottomColor: '#737373',
- borderBottomWidth: StyleSheet.hairlineWidth,
- },
-});
-```
-
----
-
-# Reference
-
-## Props
-
-### `onPress`
-
-Handler to be called when the user taps the button
-
-| Type | Required |
-| -------- | -------- |
-| function | Yes |
-
----
-
-### `title`
-
-Text to display inside the button
-
-| Type | Required |
-| ------ | -------- |
-| string | Yes |
-
----
-
-### `accessibilityLabel`
-
-Text to display for blindness accessibility features
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `color`
-
-Color of the text (iOS), or background color of the button (Android)
-
-| Type | Required |
-| ------------------ | -------- |
-| [color](colors.md) | No |
-
----
-
-### `disabled`
-
-If true, disable all interactions for this component.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `testID`
-
-Used to locate this view in end-to-end tests.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `hasTVPreferredFocus`
-
-_(Apple TV only)_ TV preferred focus (see documentation for the View component).
-
-| Type | Required | Platform |
-| ---- | -------- | -------- |
-| bool | No | iOS |
-
-### `nextFocusDown`
-
-Designates the next view to receive focus when the user navigates down. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusDown).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusForward`
-
-Designates the next view to receive focus when the user navigates forward. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusForward).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusLeft`
-
-Designates the next view to receive focus when the user navigates left. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusLeft).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusRight`
-
-Designates the next view to receive focus when the user navigates right. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusRight).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `nextFocusUp`
-
-Designates the next view to receive focus when the user navigates up. See the [Android documentation](https://developer.android.com/reference/android/view/View.html#attr_android:nextFocusUp).
-
-| Type | Required | Platform |
-| ------ | -------- | -------- |
-| number | No | Android |
-
----
-
-### `touchSoundDisabled`
-
-If true, doesn't play system sound on touch.
-
-| Type | Required | Platform |
-| ------- | -------- | -------- |
-| boolean | No | Android |
diff --git a/website/versioned_docs/version-0.61/cameraroll.md b/website/versioned_docs/version-0.61/cameraroll.md
deleted file mode 100644
index 9cea77e8e17..00000000000
--- a/website/versioned_docs/version-0.61/cameraroll.md
+++ /dev/null
@@ -1,144 +0,0 @@
----
-id: cameraroll
-title: '🚧 CameraRoll'
-
-custom_edit_url: 'https://github.com/facebook/react-native-website/edit/master/website/versioned_docs/version-0.58/cameraroll.md'
----
-
-> **Deprecated.** Use [@react-native-community/cameraroll](https://github.com/react-native-community/react-native-cameraroll) instead.
-
-`CameraRoll` provides access to the local camera roll or photo library.
-
-On iOS, the `CameraRoll` API requires the `RCTCameraRoll` library to be linked. You can refer to [Linking Libraries (iOS)](linking-libraries-ios.md) to learn more.
-
-### Permissions
-
-The user's permission is required in order to access the Camera Roll on devices running iOS 10 or later. Add the `NSPhotoLibraryUsageDescription` key in your `Info.plist` with a string that describes how your app will use this data. This key will appear as `Privacy - Photo Library Usage Description` in Xcode.
-
-If you are targeting devices running iOS 11 or later, you will also need to add the `NSPhotoLibraryAddUsageDescription` key in your `Info.plist`. Use this key to define a string that describes how your app will use this data. By adding this key to your `Info.plist`, you will be able to request write-only access permission from the user. If you try to save to the camera roll without this permission, your app will exit.
-
----
-
-# Reference
-
-## Methods
-
-### `saveToCameraRoll()`
-
-```jsx
-CameraRoll.saveToCameraRoll(tag, [type]);
-```
-
-Saves the photo or video to the camera roll or photo library.
-
-On Android, the tag must be a local image or video URI, such as `"file:///sdcard/img.png"`.
-
-On iOS, the tag can be any image URI (including local, remote asset-library and base64 data URIs) or a local video file URI (remote or data URIs are not supported for saving video at this time).
-
-If the tag has a file extension of .mov or .mp4, it will be inferred as a video. Otherwise it will be treated as a photo. To override the automatic choice, you can pass an optional `type` parameter that must be one of 'photo' or 'video'.
-
-Returns a Promise which will resolve with the new URI.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ---- | ---------------------- | -------- | ---------------------------------------------------------- |
-| tag | string | Yes | See above. |
-| type | enum('photo', 'video') | No | Overrides automatic detection based on the file extension. |
-
----
-
-### `getPhotos()`
-
-```jsx
-CameraRoll.getPhotos(params);
-```
-
-Returns a Promise with photo identifier objects from the local camera roll of the device matching shape defined by `getPhotosReturnChecker`.
-
-**Parameters:**
-
-| Name | Type | Required | Description |
-| ------ | ------ | -------- | ------------------------------------------------ |
-| params | object | Yes | Expects a params with the shape described below. |
-
-- `first` : {number} : The number of photos wanted in reverse order of the photo application (i.e. most recent first for SavedPhotos).
-- `after` : {string} : A cursor that matches `page_info { end_cursor }` returned from a previous call to `getPhotos`.
-- `groupTypes` : {string} : Specifies which group types to filter the results to. Valid values are:
- - `Album`
- - `All`
- - `Event`
- - `Faces`
- - `Library`
- - `PhotoStream`
- - `SavedPhotos` // default
-- `groupName` : {string} : Specifies filter on group names, like 'Recent Photos' or custom album titles.
-- `assetType` : {string} : Specifies filter on asset type. Valid values are:
- - `All`
- - `Videos`
- - `Photos` // default
-- `mimeTypes` : {Array} : Filter by mimetype (e.g. image/jpeg).
-
-Returns a Promise which when resolved will be of the following shape:
-
-- `edges` : {`Array`} An array of node objects
- - `node`: {object} An object with the following shape:
- - `type`: {string}
- - `group_name`: {string}
- - `image`: {object} : An object with the following shape:
- - `uri`: {string}
- - `height`: {number}
- - `width`: {number}
- - `isStored`: {boolean}
- - `playableDuration`: {number}
- - `timestamp`: {number}
- - `location`: {object} : An object with the following shape:
- - `latitude`: {number}
- - `longitude`: {number}
- - `altitude`: {number}
- - `heading`: {number}
- - `speed`: {number}
-- `page_info` : {object} : An object with the following shape:
- - `has_next_page`: {boolean}
- - `start_cursor`: {string}
- - `end_cursor`: {string}
-
-#### Example
-
-Loading images:
-
-```jsx
-_handleButtonPress = () => {
- CameraRoll.getPhotos({
- first: 20,
- assetType: 'Photos',
- })
- .then(r => {
- this.setState({ photos: r.edges });
- })
- .catch((err) => {
- //Error Loading Images
- });
- };
-render() {
- return (
-
-
- {this.state.photos.map((p, i) => {
- return (
-
-
- );
-}
-```
diff --git a/website/versioned_docs/version-0.61/checkbox.md b/website/versioned_docs/version-0.61/checkbox.md
deleted file mode 100644
index b4517a91ba7..00000000000
--- a/website/versioned_docs/version-0.61/checkbox.md
+++ /dev/null
@@ -1,111 +0,0 @@
----
-id: checkbox
-title: '🚧 CheckBox'
----
-
-> **Deprecated.** Use [@react-native-community/checkbox](https://github.com/react-native-community/react-native-checkbox) instead.
-
-Renders a boolean input (Android only).
-
-This is a controlled component that requires an `onValueChange` callback that updates the `value` prop in order for the component to reflect user actions. If the `value` prop is not updated, the component will continue to render the supplied `value` prop instead of the expected result of any user actions.
-
-## Example
-
-```SnackPlayer name=CheckBox%20Component%20Example&supportedPlatforms=android,web
-import React, { useState } from "react";
-import { CheckBox, Text, StyleSheet, View } from "react-native";
-
-export default App = () => {
- const [isSelected, setSelection] = useState(false);
-
- return (
-
-
- Do you like React Native?
-
- Is CheckBox selected: {isSelected ? "👍" : "👎"}
-
- );
-};
-
-const styles = StyleSheet.create({
- container: {
- flex: 1,
- alignItems: "center",
- justifyContent: "center",
- },
- checkboxContainer: {
- flexDirection: "row",
- marginBottom: 20,
- },
- checkbox: {
- alignSelf: "center",
- },
- label: {
- margin: 8,
- },
-});
-```
-
----
-
-# Reference
-
-## Props
-
-Inherits [View Props](view#props).
-
----
-
-### `disabled`
-
-If true the user won't be able to toggle the checkbox. Default value is `false`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
-
----
-
-### `onChange`
-
-Used in case the props change removes the component.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `onValueChange`
-
-Invoked with the new value when the value changes.
-
-| Type | Required |
-| -------- | -------- |
-| function | No |
-
----
-
-### `testID`
-
-Used to locate this view in end-to-end tests.
-
-| Type | Required |
-| ------ | -------- |
-| string | No |
-
----
-
-### `value`
-
-The value of the checkbox. If true the checkbox will be turned on. Default value is `false`.
-
-| Type | Required |
-| ---- | -------- |
-| bool | No |
diff --git a/website/versioned_docs/version-0.61/clipboard.md b/website/versioned_docs/version-0.61/clipboard.md
deleted file mode 100644
index f973d18f189..00000000000
--- a/website/versioned_docs/version-0.61/clipboard.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-id: clipboard
-title: '🚧 Clipboard'
----
-
-> **Deprecated.** Use [@react-native-community/clipboard](https://github.com/react-native-clipboard/clipboard) instead.
-
-`Clipboard` gives you an interface for setting and getting content from Clipboard on both Android and iOS
-
----
-
-# Reference
-
-## Methods
-
-### `getString()`
-
-```jsx
-static getString()
-```
-
-Get content of string type, this method returns a `Promise`, so you can use following code to get clipboard content
-
-```jsx
-async _getContent() {
- var content = await Clipboard.getString();
-}
-```
-
----
-
-### `setString()`
-
-```jsx
-static setString(content)
-```
-
-Set content of string type. You can use following code to set clipboard content
-
-```jsx
-_setContent() {
- Clipboard.setString('hello world');
-}
-```
-
-@param the content to be stored in the clipboard.
diff --git a/website/versioned_docs/version-0.61/colors.md b/website/versioned_docs/version-0.61/colors.md
deleted file mode 100644
index e02172d982f..00000000000
--- a/website/versioned_docs/version-0.61/colors.md
+++ /dev/null
@@ -1,184 +0,0 @@
----
-id: colors
-title: Color Reference
----
-
-Components in React Native are [styled using JavaScript](style.md). Color properties usually match how [CSS works on the web](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value).
-
-### Red-green-blue
-
-React Native supports `rgb()` and `rgba()` in both hexadecimal and functional notation:
-
-- `'#f0f'` (#rgb)
-- `'#ff00ff'` (#rrggbb)
-
-- `'rgb(255, 0, 255)'`
-- `'rgba(255, 255, 255, 1.0)'`
-
-- `'#f0ff'` (#rgba)
-- `'#ff00ff00'` (#rrggbbaa)
-
-### Hue-saturation-lightness
-
-`hsl()` and `hsla()` is supported in functional notation:
-
-- `'hsl(360, 100%, 100%)'`
-- `'hsla(360, 100%, 100%, 1.0)'`
-
-### `transparent`
-
-This is a shortcut for `rgba(0,0,0,0)`:
-
-- `'transparent'`
-
-### Named colors
-
-You can also use color names as values. React Native follows the [CSS3 specification](http://www.w3.org/TR/css3-color/#svg-color):
-
-
-
--  imageList = new ArrayList(Arrays.asList(
- "http://foo.com/bar1.png",
- "http://foo.com/bar2.png"
- ));
- initialProperties.putStringArrayList("images", imageList);
- return initialProperties;
- }
- };
- }
-}
-```
-
-```jsx
-import React from 'react';
-import {View, Image} from 'react-native';
-
-export default class ImageBrowserApp extends React.Component {
- renderImage(imgURI) {
- return {this.props.images.map(this.renderImage)} ;
- }
-}
-```
-
-`ReactRootView` 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.
-
-```java
-Bundle updatedProps = mReactRootView.getAppProperties();
-ArrayList imageList = new ArrayList(Arrays.asList(
- "http://foo.com/bar3.png",
- "http://foo.com/bar4.png"
-));
-updatedProps.putStringArrayList("images", imageList);
-
-mReactRootView.setAppProperties(updatedProps);
-```
-
-It is fine to update properties anytime. However, updates have to be performed on the main thread. You use the getter on any thread.
-
-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-android.md#3-expose-view-property-setters-using-reactprop-or-reactpropgroup-annotation). In short, properties that are to be reflected in JavaScript needs to be exposed as setter method annotated with `@ReactProp`, then 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-android.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-android.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).
-
-### Calling native functions from React Native (native modules)
-
-Native modules are Java 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-android.md).
-
-> **_Warning_**: All native modules share the same namespace. Watch out for name collisions when creating new ones.
diff --git a/website/versioned_docs/version-0.61/communication-ios.md b/website/versioned_docs/version-0.61/communication-ios.md
deleted file mode 100644
index 6bc71eea4fa..00000000000
--- a/website/versioned_docs/version-0.61/communication-ios.md
+++ /dev/null
@@ -1,200 +0,0 @@
----
-id: communication-ios
-title: Communication between native and React Native
----
-
-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 specific, 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 {this.props.images.map(this.renderImage)} ;
- }
-}
-```
-
-`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 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/0.61-stable/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). To summarize, 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/0.61-stable/packages/rn-tester/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 separate 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.61/components-and-apis.md b/website/versioned_docs/version-0.61/components-and-apis.md
deleted file mode 100644
index 3b934df9aba..00000000000
--- a/website/versioned_docs/version-0.61/components-and-apis.md
+++ /dev/null
@@ -1,291 +0,0 @@
----
-id: components-and-apis
-title: Components and APIs
----
-
-React Native provides a number of [Core Components](intro-react-native-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.
-
-
-
-## User Interface
-
-Render common user interface controls on any platform using the following components. For platform specific components, keep reading.
-
-
-
-## List Views
-
-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.
-
-
-
-## iOS Components and APIs
-
-Many of the following components provide wrappers for commonly used UIKit classes.
-
-
-
-## Android Components and APIs
-
-Many of the following components provide wrappers for commonly used Android classes.
-
-
-
-## 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.
-
-
diff --git a/website/versioned_docs/version-0.61/custom-webview-android.md b/website/versioned_docs/version-0.61/custom-webview-android.md
deleted file mode 100644
index 492391662da..00000000000
--- a/website/versioned_docs/version-0.61/custom-webview-android.md
+++ /dev/null
@@ -1,261 +0,0 @@
----
-id: custom-webview-android
-title: Custom WebView
----
-
-While the built-in web view has a lot of features, it is not possible to handle every use-case in React Native. You can, however, extend the web view with native code without forking React Native or duplicating all the existing web view code.
-
-Before you do this, you should be familiar with the concepts in [native UI components](native-components-android). You should also familiarise yourself with the [native code for web views](https://github.com/facebook/react-native/blob/0.61-stable/ReactAndroid/src/main/java/com/facebook/react/views/webview/ReactWebViewManager.java), as you will have to use this as a reference when implementing new features—although a deep understanding is not required.
-
-## Native Code
-
-To get started, you'll need to create a subclass of `ReactWebViewManager`, `ReactWebView`, and `ReactWebViewClient`. In your view manager, you'll then need to override:
-
-- `createReactWebViewInstance`
-- `getName`
-- `addEventEmitters`
-
-```java
-@ReactModule(name = CustomWebViewManager.REACT_CLASS)
-public class CustomWebViewManager extends ReactWebViewManager {
- /* This name must match what we're referring to in JS */
- protected static final String REACT_CLASS = "RCTCustomWebView";
-
- protected static class CustomWebViewClient extends ReactWebViewClient { }
-
- protected static class CustomWebView extends ReactWebView {
- public CustomWebView(ThemedReactContext reactContext) {
- super(reactContext);
- }
- }
-
- @Override
- protected ReactWebView createReactWebViewInstance(ThemedReactContext reactContext) {
- return new CustomWebView(reactContext);
- }
-
- @Override
- public String getName() {
- return REACT_CLASS;
- }
-
- @Override
- protected void addEventEmitters(ThemedReactContext reactContext, WebView view) {
- view.setWebViewClient(new CustomWebViewClient());
- }
-}
-```
-
-You'll need to follow the usual steps to [register the module](native-modules-android.md#register-the-module).
-
-### Adding New Properties
-
-To add a new property, you'll need to add it to `CustomWebView`, and then expose it in `CustomWebViewManager`.
-
-```java
-public class CustomWebViewManager extends ReactWebViewManager {
- ...
-
- protected static class CustomWebView extends ReactWebView {
- public CustomWebView(ThemedReactContext reactContext) {
- super(reactContext);
- }
-
- protected @Nullable String mFinalUrl;
-
- public void setFinalUrl(String url) {
- mFinalUrl = url;
- }
-
- public String getFinalUrl() {
- return mFinalUrl;
- }
- }
-
- ...
-
- @ReactProp(name = "finalUrl")
- public void setFinalUrl(WebView view, String url) {
- ((CustomWebView) view).setFinalUrl(url);
- }
-}
-```
-
-### Adding New Events
-
-For events, you'll first need to make create event subclass.
-
-```java
-// NavigationCompletedEvent.java
-public class NavigationCompletedEvent extends Event {
- private WritableMap mParams;
-
- public NavigationCompletedEvent(int viewTag, WritableMap params) {
- super(viewTag);
- this.mParams = params;
- }
-
- @Override
- public String getEventName() {
- return "navigationCompleted";
- }
-
- @Override
- public void dispatch(RCTEventEmitter rctEventEmitter) {
- init(getViewTag());
- rctEventEmitter.receiveEvent(getViewTag(), getEventName(), mParams);
- }
-}
-```
-
-You can trigger the event in your web view client. You can hook existing handlers if your events are based on them.
-
-You should refer to [ReactWebViewManager.java](https://github.com/facebook/react-native/blob/0.61-stable/ReactAndroid/src/main/java/com/facebook/react/views/webview/ReactWebViewManager.java) in the React Native codebase to see what handlers are available and how they are implemented. You can extend any methods here to provide extra functionality.
-
-```java
-public class NavigationCompletedEvent extends Event {
- private WritableMap mParams;
-
- public NavigationCompletedEvent(int viewTag, WritableMap params) {
- super(viewTag);
- this.mParams = params;
- }
-
- @Override
- public String getEventName() {
- return "navigationCompleted";
- }
-
- @Override
- public void dispatch(RCTEventEmitter rctEventEmitter) {
- init(getViewTag());
- rctEventEmitter.receiveEvent(getViewTag(), getEventName(), mParams);
- }
-}
-
-// CustomWebViewManager.java
-protected static class CustomWebViewClient extends ReactWebViewClient {
- @Override
- public boolean shouldOverrideUrlLoading(WebView view, String url) {
- boolean shouldOverride = super.shouldOverrideUrlLoading(view, url);
- String finalUrl = ((CustomWebView) view).getFinalUrl();
-
- if (!shouldOverride && url != null && finalUrl != null && new String(url).equals(finalUrl)) {
- final WritableMap params = Arguments.createMap();
- dispatchEvent(view, new NavigationCompletedEvent(view.getId(), params));
- }
-
- return shouldOverride;
- }
-}
-```
-
-Finally, you'll need to expose the events in `CustomWebViewManager` through `getExportedCustomDirectEventTypeConstants`. Note that currently, the default implementation returns `null`, but this may change in the future.
-
-```java
-public class CustomWebViewManager extends ReactWebViewManager {
- ...
-
- @Override
- public @Nullable
- Map getExportedCustomDirectEventTypeConstants() {
- Map export = super.getExportedCustomDirectEventTypeConstants();
- if (export == null) {
- export = MapBuilder.newHashMap();
- }
- export.put("navigationCompleted", MapBuilder.of("registrationName", "onNavigationCompleted"));
- return export;
- }
-}
-```
-
-## JavaScript Interface
-
-To use your custom web view, you'll need to create a class for it. Your class must:
-
-- Export all the prop types from `WebView.propTypes`
-- Return a `WebView` component with the prop `nativeConfig.component` set to your native component (see below)
-
-To get your native component, you must use `requireNativeComponent`: the same as for regular custom components. However, you must pass in an extra third argument, `WebView.extraNativeComponentConfig`. This third argument contains prop types that are only required for native code.
-
-```jsx
-import React, {Component, PropTypes} from 'react';
-import {WebView, requireNativeComponent} from 'react-native';
-
-export default class CustomWebView extends Component {
- static propTypes = WebView.propTypes;
-
- render() {
- return (
-
-
-@interface RCTCustomWebView : RCTWebView
-
-@end
-
-// RCTCustomWebView.m
-#import "RCTCustomWebView.h"
-
-@interface RCTCustomWebView ()
-
-@end
-
-@implementation RCTCustomWebView { }
-
-@end
-```
-
-For the view manager, you need to make a subclass `RCTWebViewManager`. You must still include:
-
-- `(UIView *)view` that returns your custom view
-- The `RCT_EXPORT_MODULE()` tag
-
-```objc
-// RCTCustomWebViewManager.h
-#import
-
-@interface RCTCustomWebViewManager : RCTWebViewManager
-
-@end
-
-// RCTCustomWebViewManager.m
-#import "RCTCustomWebViewManager.h"
-#import "RCTCustomWebView.h"
-
-@interface RCTCustomWebViewManager ()
-
-@end
-
-@implementation RCTCustomWebViewManager { }
-
-RCT_EXPORT_MODULE()
-
-- (UIView *)view
-{
- RCTCustomWebView *webView = [RCTCustomWebView new];
- webView.delegate = self;
- return webView;
-}
-
-@end
-```
-
-### Adding New Events and Properties
-
-Adding new properties and events is the same as regular UI components. For properties, you define an `@property` in the header. For events, you define a `RCTDirectEventBlock` in the view's `@interface`.
-
-```objc
-// RCTCustomWebView.h
-@property (nonatomic, copy) NSString *finalUrl;
-
-// RCTCustomWebView.m
-@interface RCTCustomWebView ()
-
-@property (nonatomic, copy) RCTDirectEventBlock onNavigationCompleted;
-
-@end
-```
-
-Then expose it in the view manager's `@implementation`.
-
-```objc
-// RCTCustomWebViewManager.m
-RCT_EXPORT_VIEW_PROPERTY(onNavigationCompleted, RCTDirectEventBlock)
-RCT_EXPORT_VIEW_PROPERTY(finalUrl, NSString)
-```
-
-### Extending Existing Events
-
-You should refer to [RCTWebView.m](https://github.com/facebook/react-native/blob/0.61-stable/React/Views/RCTWebView.m) in the React Native codebase to see what handlers are available and how they are implemented. You can extend any methods here to provide extra functionality.
-
-By default, most methods aren't exposed from RCTWebView. If you need to expose them, you need to create an [Objective C category](https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/CustomizingExistingClasses/CustomizingExistingClasses.html), and then expose all the methods you need to use.
-
-```objc
-// RCTWebView+Custom.h
-#import
-
-@interface RCTWebView (Custom)
-- (BOOL)webView:(__unused UIWebView *)webView shouldStartLoadWithRequest:(NSURLRequest *)request navigationType:(UIWebViewNavigationType)navigationType;
-- (NSMutableDictionary *)baseEvent;
-@end
-```
-
-Once these are exposed, you can reference them in your custom web view class.
-
-```objc
-// RCTCustomWebView.m
-
-// Remember to import the category file.
-#import "RCTWebView+Custom.h"
-
-- (BOOL)webView:(__unused UIWebView *)webView shouldStartLoadWithRequest:(NSURLRequest *)request
- navigationType:(UIWebViewNavigationType)navigationType
-{
- BOOL allowed = [super webView:webView shouldStartLoadWithRequest:request navigationType:navigationType];
-
- if (allowed) {
- NSString* url = request.URL.absoluteString;
- if (url && [url isEqualToString:_finalUrl]) {
- if (_onNavigationCompleted) {
- NSMutableDictionary *event = [self baseEvent];
- _onNavigationCompleted(event);
- }
- }
- }
-
- return allowed;
-}
-```
-
-## JavaScript Interface
-
-To use your custom web view, you'll need to create a class for it. Your class must:
-
-- Export all the prop types from `WebView.propTypes`
-- Return a `WebView` component with the prop `nativeConfig.component` set to your native component (see below)
-
-To get your native component, you must use `requireNativeComponent`: the same as for regular custom components. However, you must pass in an extra third argument, `WebView.extraNativeComponentConfig`. This third argument contains prop types that are only required for native code.
-
-```jsx
-import React, {Component, PropTypes} from 'react';
-import {
- WebView,
- requireNativeComponent,
- NativeModules,
-} from 'react-native';
-const {CustomWebViewManager} = NativeModules;
-
-export default class CustomWebView extends Component {
- static propTypes = WebView.propTypes;
-
- render() {
- return (
-
