From aba573740bc1fdc2160eee74d1b5a53e9934d51a Mon Sep 17 00:00:00 2001 From: Brent Vatne Date: Wed, 17 Aug 2022 12:56:20 -0700 Subject: [PATCH 1/3] Use anchor directly instead of markdown, which is apparently not supported in this context --- docs/appregistry.md | 2 +- website/versioned_docs/version-0.69/appregistry.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/appregistry.md b/docs/appregistry.md index 1a2f3aaa3c1..0adf5b64772 100644 --- a/docs/appregistry.md +++ b/docs/appregistry.md @@ -6,7 +6,7 @@ title: AppRegistry

Project with Native Code Required

- If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through [registerRootComponent](https://docs.expo.dev/versions/latest/sdk/register-root-component/)). You do not need to use this API. + If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.

diff --git a/website/versioned_docs/version-0.69/appregistry.md b/website/versioned_docs/version-0.69/appregistry.md index 1a2f3aaa3c1..0adf5b64772 100644 --- a/website/versioned_docs/version-0.69/appregistry.md +++ b/website/versioned_docs/version-0.69/appregistry.md @@ -6,7 +6,7 @@ title: AppRegistry

Project with Native Code Required

- If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through [registerRootComponent](https://docs.expo.dev/versions/latest/sdk/register-root-component/)). You do not need to use this API. + If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.

From d945893bacf4fcdb3cd4303c5d272331499c7265 Mon Sep 17 00:00:00 2001 From: Brent Vatne Date: Wed, 17 Aug 2022 12:57:02 -0700 Subject: [PATCH 2/3] Copy over to changes to the Expo section of more-resources from the versioned doc --- docs/more-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/more-resources.md b/docs/more-resources.md index 7e061a9ccb4..2f775cee371 100644 --- a/docs/more-resources.md +++ b/docs/more-resources.md @@ -26,7 +26,7 @@ We recommend using the [VS Code](https://code.visualstudio.com/) code editor and ## Platforms to try -[Expo](https://docs.expo.dev/) is a framework of tools and services for React Native that focuses on letting you build React Native apps without ever touching Xcode or Android Studio. If you have a web development background, this might appeal to you. +[Expo](https://docs.expo.dev/) is a framework of tools and services for React Native that focuses on helping you build, ship, and iterate on your app, to use preview deployment workflows that are popular with web development, and to automate your development workflows. Expo also makes it possible to build React Native apps without ever touching Xcode or Android Studio, and it doesn't get in the way if you want to use those tools. [Ignite](https://github.com/infinitered/ignite) is a starter kit CLI with several React Native boilerplates. The latest, [Ignite Bowser](https://github.com/infinitered/ignite-bowser), uses MobX-State-Tree for state management, React Navigation, and other common libraries. It has generators for components, models, and more, and supports Expo out of the box. If you are looking for a preconfigured tech stack, Ignite could be perfect for you. From 00d3190a847f1810d30c045e7a5791190d106767 Mon Sep 17 00:00:00 2001 From: Brent Vatne Date: Wed, 17 Aug 2022 13:02:27 -0700 Subject: [PATCH 3/3] Fix grammar --- docs/getting-started.md | 2 +- website/versioned_docs/version-0.69/getting-started.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/getting-started.md b/docs/getting-started.md index c7401c24a13..7146a639dd2 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -78,7 +78,7 @@ The Expo Go app is a great tool to get started — it exists to help developers The tradeoff is that the Expo Go app does not allow you to add custom native code — you can only use native modules built into the Expo SDK. There are many great libraries available outside of the Expo SDK, and you may even want to build your own native library. You can leverage these libraries with [development builds](https://docs.expo.dev/development/introduction/), or by using ["prebuild"](https://docs.expo.dev/workflow/prebuild/) to generate the native projects, or both. [Learn more about adding native code to projects created with `create-expo-app`](https://docs.expo.dev/workflow/customizing/). -`create-expo-app` configures your project to use the most recent React Native version that is supported by the Expo SDK. The Expo Go app usually gains support for a given React Native version with new SDK (released quarterly). You can check [this document](https://docs.expo.dev/versions/latest/#each-expo-sdk-version-depends-on-a) to find out what versions are supported. +`create-expo-app` configures your project to use the most recent React Native version that is supported by the Expo SDK. The Expo Go app usually gains support for a given React Native version with new SDK versions (released quarterly). You can check [this document](https://docs.expo.dev/versions/latest/#each-expo-sdk-version-depends-on-a) to find out what versions are supported. If you're integrating React Native into an existing project, [you can use the Expo SDK](https://docs.expo.dev/bare/installing-expo-modules/) and [development builds](https://docs.expo.dev/development/introduction/), but you will need to set up a native development environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native. diff --git a/website/versioned_docs/version-0.69/getting-started.md b/website/versioned_docs/version-0.69/getting-started.md index c7401c24a13..7146a639dd2 100644 --- a/website/versioned_docs/version-0.69/getting-started.md +++ b/website/versioned_docs/version-0.69/getting-started.md @@ -78,7 +78,7 @@ The Expo Go app is a great tool to get started — it exists to help developers The tradeoff is that the Expo Go app does not allow you to add custom native code — you can only use native modules built into the Expo SDK. There are many great libraries available outside of the Expo SDK, and you may even want to build your own native library. You can leverage these libraries with [development builds](https://docs.expo.dev/development/introduction/), or by using ["prebuild"](https://docs.expo.dev/workflow/prebuild/) to generate the native projects, or both. [Learn more about adding native code to projects created with `create-expo-app`](https://docs.expo.dev/workflow/customizing/). -`create-expo-app` configures your project to use the most recent React Native version that is supported by the Expo SDK. The Expo Go app usually gains support for a given React Native version with new SDK (released quarterly). You can check [this document](https://docs.expo.dev/versions/latest/#each-expo-sdk-version-depends-on-a) to find out what versions are supported. +`create-expo-app` configures your project to use the most recent React Native version that is supported by the Expo SDK. The Expo Go app usually gains support for a given React Native version with new SDK versions (released quarterly). You can check [this document](https://docs.expo.dev/versions/latest/#each-expo-sdk-version-depends-on-a) to find out what versions are supported. If you're integrating React Native into an existing project, [you can use the Expo SDK](https://docs.expo.dev/bare/installing-expo-modules/) and [development builds](https://docs.expo.dev/development/introduction/), but you will need to set up a native development environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.