docs: rewrite Community libraries and remove Alternatives (react-navigation#1219)

kacperkapusciak · web-flow · commit dcff6226a032 · 2023-03-06T11:39:32.000+01:00
* Update anti-pitch to recommend RNN

* Remove alternatives

* docs: rewrite community libraries section

* Describe file-based routing
diff --git a/versioned_docs/version-6.x/alternatives.md b/versioned_docs/version-6.x/alternatives.md
diff --git a/versioned_docs/version-6.x/navigation-solutions-and-community-libraries.md b/versioned_docs/version-6.x/navigation-solutions-and-community-libraries.md
@@ -1,38 +1,44 @@
 ---
-id: community-libraries-and-navigators
-title: Community-developed Navigators and Libraries
-sidebar_label: Community Navigators and Libraries
+id: navigation-solutions-and-community-libraries
+title: Navigation Solutions and Community Libraries
+sidebar_label: Navigation Solutions and Community Libraries
 ---
 
 > Libraries listed in this guide may not have been updated to work with the latest version of React Navigation. Please refer to the library's documentation to see which version of React Navigation it supports.
 
-# Navigators
+# Solutions built on top of React Navigation
 
-## Fluid Transitions
+## Solito
 
-Fluid Transitions is a library that provides Shared Element Transitions during navigation between screens using react-navigation.
+A tiny wrapper around React Navigation and Next.js that lets you share navigation code across platforms. Also, it provides a set of patterns and examples for building cross-platform apps with React Native + Next.js.
 
-A Shared Element Transition is the visualization of an element in one screen being transformed into a corresponding element in another screen during the navigation transition.
+#### Links
 
-The library implements a custom navigator called `FluidNavigator` that makes all this and more possible.
+[Documentation](https://solito.dev/)
 
-#### Links
+[github.com/nandorojo/solito](https://github.com/nandorojo/solito)
+
+## Expo Router
 
-[github.com/fram-x/FluidTransitions](https://github.com/fram-x/FluidTransitions)
+File-based router for React Native apps. With Expo Router pages are automatically generated by simply creating files in a project.
 
-# Libraries
+#### Links
+
+[Documentation](https://expo.github.io/router/docs)
 
-## react-navigation-collapsible
+[github.com/expo/router](https://github.com/expo/router)
 
-react-navigation-collapsible is a library and a `Higher Order Component` that adjusts your screen options and makes your screen header collapsible.
+## Navio
 
-Since react-navigation's header is designed as `Animated` component, you can animate the header by passing `Animated.Value` from your `ScrollView` or `FlatList` to the header.
+A navigation library built on top of React Navigation. It's main goal is to improve DX by building the app layout in one place and using the power of TypeScript to provide route names autocompletion.
 
 #### Links
 
-[github.com/benevbright/react-navigation-collapsible](https://github.com/benevbright/react-navigation-collapsible)
+[github.com/kanzitelli/rn-navio](https://github.com/kanzitelli/rn-navio)
+
+[Demo on Snack](https://snack.expo.dev/@kanzitelli/rn-navio-snack)
 
-[Demo on Snack](https://snack.expo.io/@benevbright/react-navigation-collapsible)
+# Community libraries
 
 ## react-native-screens
 
@@ -59,12 +65,3 @@ Provides simple HOCs that map react-navigation props to your screen components d
 #### Links
 
 [github.com/vonovak/react-navigation-props-mapper](https://github.com/vonovak/react-navigation-props-mapper)
-
-## react-navigation-backhandler
-
-Easily handle Android back button behavior with React-Navigation with a component based API.
-
-#### Links
-
-[github.com/vonovak/react-navigation-backhandler](https://github.com/vonovak/react-navigation-backhandler)
-
diff --git a/versioned_docs/version-6.x/pitch.md b/versioned_docs/version-6.x/pitch.md
@@ -19,5 +19,5 @@ It's useful when considering whether or not to use a project to understand the t
 
 - Improvements may require breaking changes. We are working to make ["easy things easy and hard things possible"](https://www.quora.com/What-is-the-origin-of-the-phrase-make-the-easy-things-easy-and-the-hard-things-possible) and this may require us to change the API at times.
 - Some navigators don't directly use the native navigation APIs on iOS and Android; rather, they use the lowest level pieces and then re-creates some subset of the APIs on top. This is a conscious choice in order to make it possible for users to customize any part of the navigation experience (because it's implemented in JavaScript) and to be able to debug issues that they encounter without needing to learn Objective C / Swift / Java / Kotlin.
-  - If you need the exact platform behavior, you can choose to use the navigators that use native platform primitives (e.g. [Native Stack Navigator](native-stack-navigator.md)), or use another library that wraps the platform APIs. Read more about these in [Alternatives](alternatives.md) and be sure to understand the tradeoffs that they make before digging in!
+  - If you need the exact platform behavior, you can choose to use the navigators that use native platform primitives (e.g. [Native Stack Navigator](native-stack-navigator.md)), or use a different navigation library which provides fully native navigation APIs (e.g. [React Native Navigation](https://github.com/wix/react-native-navigation)).
 - There are other limitations which you may want to consider, see [Limitations](limitations.md) for more details.
diff --git a/versioned_docs/version-7.x/alternatives.md b/versioned_docs/version-7.x/alternatives.md
diff --git a/versioned_docs/version-7.x/navigation-solutions-and-community-libraries.md b/versioned_docs/version-7.x/navigation-solutions-and-community-libraries.md
@@ -1,38 +1,44 @@
 ---
-id: community-libraries-and-navigators
-title: Community-developed Navigators and Libraries
-sidebar_label: Community Navigators and Libraries
+id: navigation-solutions-and-community-libraries
+title: Navigation Solutions and Community Libraries
+sidebar_label: Navigation Solutions and Community Libraries
 ---
 
 > Libraries listed in this guide may not have been updated to work with the latest version of React Navigation. Please refer to the library's documentation to see which version of React Navigation it supports.
 
-# Navigators
+# Solutions built on top of React Navigation
 
-## Fluid Transitions
+## Solito
 
-Fluid Transitions is a library that provides Shared Element Transitions during navigation between screens using react-navigation.
+A tiny wrapper around React Navigation and Next.js that lets you share navigation code across platforms. Also, it provides a set of patterns and examples for building cross-platform apps with React Native + Next.js.
 
-A Shared Element Transition is the visualization of an element in one screen being transformed into a corresponding element in another screen during the navigation transition.
+#### Links
 
-The library implements a custom navigator called `FluidNavigator` that makes all this and more possible.
+[Documentation](https://solito.dev/)
 
-#### Links
+[github.com/nandorojo/solito](https://github.com/nandorojo/solito)
+
+## Expo Router
 
-[github.com/fram-x/FluidTransitions](https://github.com/fram-x/FluidTransitions)
+File-based router for React Native apps. With Expo Router pages are automatically generated by simply creating files in a project.
 
-# Libraries
+#### Links
+
+[Documentation](https://expo.github.io/router/docs)
 
-## react-navigation-collapsible
+[github.com/expo/router](https://github.com/expo/router)
 
-react-navigation-collapsible is a library and a `Higher Order Component` that adjusts your screen options and makes your screen header collapsible.
+## Navio
 
-Since react-navigation's header is designed as `Animated` component, you can animate the header by passing `Animated.Value` from your `ScrollView` or `FlatList` to the header.
+A navigation library built on top of React Navigation. It's main goal is to improve DX by building the app layout in one place and using the power of TypeScript to provide route names autocompletion.
 
 #### Links
 
-[github.com/benevbright/react-navigation-collapsible](https://github.com/benevbright/react-navigation-collapsible)
+[github.com/kanzitelli/rn-navio](https://github.com/kanzitelli/rn-navio)
+
+[Demo on Snack](https://snack.expo.dev/@kanzitelli/rn-navio-snack)
 
-[Demo on Snack](https://snack.expo.io/@benevbright/react-navigation-collapsible)
+# Community libraries
 
 ## react-native-screens
 
@@ -59,12 +65,3 @@ Provides simple HOCs that map react-navigation props to your screen components d
 #### Links
 
 [github.com/vonovak/react-navigation-props-mapper](https://github.com/vonovak/react-navigation-props-mapper)
-
-## react-navigation-backhandler
-
-Easily handle Android back button behavior with React-Navigation with a component based API.
-
-#### Links
-
-[github.com/vonovak/react-navigation-backhandler](https://github.com/vonovak/react-navigation-backhandler)
-
diff --git a/versioned_docs/version-7.x/pitch.md b/versioned_docs/version-7.x/pitch.md
@@ -19,5 +19,5 @@ It's useful when considering whether or not to use a project to understand the t
 
 - Improvements may require breaking changes. We are working to make ["easy things easy and hard things possible"](https://www.quora.com/What-is-the-origin-of-the-phrase-make-the-easy-things-easy-and-the-hard-things-possible) and this may require us to change the API at times.
 - Some navigators don't directly use the native navigation APIs on iOS and Android; rather, they use the lowest level pieces and then re-creates some subset of the APIs on top. This is a conscious choice in order to make it possible for users to customize any part of the navigation experience (because it's implemented in JavaScript) and to be able to debug issues that they encounter without needing to learn Objective C / Swift / Java / Kotlin.
-  - If you need the exact platform behavior, you can choose to use the navigators that use native platform primitives (e.g. [Native Stack Navigator](native-stack-navigator.md)), or use another library that wraps the platform APIs. Read more about these in [Alternatives](alternatives.md) and be sure to understand the tradeoffs that they make before digging in!
+  - If you need the exact platform behavior, you can choose to use the navigators that use native platform primitives (e.g. [Native Stack Navigator](native-stack-navigator.md)), or use a different navigation library which provides fully native navigation APIs (e.g. [React Native Navigation](https://github.com/wix/react-native-navigation)).
 - There are other limitations which you may want to consider, see [Limitations](limitations.md) for more details.
diff --git a/versioned_sidebars/version-6.x-sidebars.json b/versioned_sidebars/version-6.x-sidebars.json
@@ -101,14 +101,13 @@
     ],
     "Additional Resources": [
       "version-6.x/migration-guides",
-      "version-6.x/community-libraries-and-navigators",
+      "version-6.x/navigation-solutions-and-community-libraries",
       "version-6.x/more-resources"
     ],
     "Meta": [
       "version-6.x/pitch",
-      "version-6.x/alternatives",
       "version-6.x/used-by",
       "version-6.x/contributing"
     ]
   }
-}
+}
diff --git a/versioned_sidebars/version-7.x-sidebars.json b/versioned_sidebars/version-7.x-sidebars.json
@@ -108,14 +108,13 @@
     ],
     "Additional Resources": [
       "version-7.x/migration-guides",
-      "version-7.x/community-libraries-and-navigators",
+      "version-7.x/navigation-solutions-and-community-libraries",
       "version-7.x/more-resources"
     ],
     "Meta": [
       "version-7.x/pitch",
-      "version-7.x/alternatives",
       "version-7.x/used-by",
       "version-7.x/contributing"
     ]
   }
-}
+}
