♻️ (naming) replace gondola with nonav

Author: tpucci

README.md

@@ -1,4 +1,4 @@
-<h1 align="center">React Gondola</h1>
+<h1 align="center">React Nonav</h1>
 
 <p align="center">React Native declarative and reactive navigation.</p>
 
@@ -16,7 +16,7 @@
 
 This repo focuses on grouping screens by business conversion tunnels called **canals**. Why did I call it `react-nonav`? Just because I though of this package when I was visiting Venice... and I kind of hope that using this package will feel like navigating in Venice 📸
 
-**When you use React Gondola**, you define several screens and you have the possibility to control their visibility with YOUR state machine. You define the rules of WHEN some screens should appear; `react-nonav` takes care of the rest.
+**When you use React Nonav**, you define several screens and you have the possibility to control their visibility with YOUR state machine. You define the rules of WHEN some screens should appear; `react-nonav` takes care of the rest.
 
 ## 👍 TLDR; Use this package if:
 
@@ -29,7 +29,7 @@ This repo focuses on grouping screens by business conversion tunnels called **ca
 - you want to navigate imperatively.
 - you need to use Native navigation (react-nonav's navigation is powered by JS code only).
 
-## Docs
+## Docs [![Netlify Status](https://api.netlify.com/api/v1/badges/a0a567d1-8c40-4c59-831c-0b137a3b176c/deploy-status)](https://app.netlify.com/sites/react-nonav/deploys)
 
 The docs are here: https://react-nonav.netlify.com/
 Powered by the incredible [docz](https://www.docz.site/).

docs/Welcome.mdx

@@ -3,15 +3,15 @@ name: Welcome
 route: /
 ---
 
-# React Gondola
+# React Nonav
 
 React Native declarative and reactive navigation.
 
 ## Philosophy
 
 This repo focuses on grouping screens by business conversion tunnels called **canals**. Why did I call it `react-nonav`? Just because I though of this package when I was visiting Venice... and I kind of hope that using this package will feel like navigating in Venice 📸
 
-**When you use React Gondola**, you define several screens and you have the possibility to control their visibility with YOUR state machine. You define the rules of WHEN some screens should appear; `react-nonav` takes care of the rest.
+**When you use React Nonav**, you define several screens and you have the possibility to control their visibility with YOUR state machine. You define the rules of WHEN some screens should appear; `react-nonav` takes care of the rest.
 
 ## When to use this package
 

docs/guides/ReactNavigationInteroperability.mdx

@@ -4,7 +4,7 @@ menu: Guides
 route: /guides/react-navigation
 ---
 
-# Can React Gondola work with React Navigation ❤️ ?
+# Can React Nonav work with React Navigation ❤️ ?
 
 Yes it can.
 

example/src/Welcome.tsx

@@ -6,7 +6,7 @@ export class Welcome extends Component {
     return (
       <View style={{ flex: 1, justifyContent: 'center', padding: 16 }}>
         <Text style={{ fontSize: 32, fontWeight: '500', textAlign: 'center', marginBottom: 16 }}>
-          Welcome in React Gondola !
+          Welcome in React Nonav !
         </Text>
         <Text style={{ marginTop: 16 }}>
           Choose an example in the tab bar to explore this example app.

src/FullScreenPortal.mdx

@@ -18,7 +18,7 @@ route: /api/full-screen-portal
 
 ### `fullScreenStack: IStreamListener<StopInterface[]>`
 
-MobX Strem Listener of list of React Gondola full screen Stops. This stream is observed by MobX and fires the rendering of the full screen stack in the `FullScreenPortal.render` method.
+MobX Strem Listener of list of React Nonav full screen Stops. This stream is observed by MobX and fires the rendering of the full screen stack in the `FullScreenPortal.render` method.
 
 ## Basic usage