Document functional components + hooks

playground/src/screens/SideMenuLeftScreen.js

@@ -12,15 +12,16 @@ const {
 
 function SideMenuLeftScreen(props) {
   useEffect(() => {
-    const componentDisappearListener = Navigation.events().registerComponentDidDisappearListener(
-      ({ componentId }) => {
-        if (componentId === props.componentId) {
-          console.log('RNN', `componentDisappearListener ${componentId}/${JSON.stringify(props)}`);
-        }
+    const unsubscribe = Navigation.events().bindComponent({
+      componentDidAppear: () => {
+        console.log('RNN', `componentDidAppear`);
       },
-    );
+      componentDidDisappear: () => {
+        console.log('RNN', `componentDidDisappear`);
+      }
+    }, props.componentId);
     return () => {
-      componentDisappearListener.remove();
+      unsubscribe.remove();
     };
   }, []);
 

website/docs/docs-functional-components.mdx

@@ -0,0 +1,88 @@
+---
+id: functionalComponents
+title: Using functional components as screens
+sidebar_label: Using functional components
+---
+
+Both class components and functional components can be used as screens. There is no performance difference between the two. Deciding which type component to use boils down to user preference.
+
+## Declaring static options
+Static options are a great way to declare options close to where they are used. Declaring static options is done by first declaring the functional component, and then declaring the options on the function class.
+```jsx
+const MyScreen = (props) => {
+  return (
+      <View>
+        <Text>Screen Component</Text>
+      </View>
+    );
+};
+
+MyScreen.options = {
+  topBar: {
+    background: {
+      color: 'red'
+    }
+  }
+}
+```
+
+## Listening to navigation events
+Navigation events let you react to various events related to a specific component or the app its self. Read more about them [here](api-events.mdx)
+
+```jsx
+import { useEffect } from 'react';
+import Navigation from 'react-native-navigation';
+
+function MyScreen(props) {
+  useEffect(() => {
+    const listener = {
+      componentDidAppear: () => {
+        console.log('RNN', `componentDidAppear`);
+      },
+      componentDidDisappear: () => {
+        console.log('RNN', `componentDidDisappear`);
+      }
+    };
+    // Register the listener to all events related to our component
+    const unsubscribe = Navigation.events().bindComponent(listener, props.componentId);
+    return () => {
+      // Make sure to unregister the listener during cleanup
+      unsubscribe.remove();
+    };
+  }, []);
+
+  return (
+      <View>
+        <Text>Screen Component</Text>
+      </View>
+    );
+}
+```
+
+Notice that in the example above, we call `Navigation.events().bindComponent()` to register our listener even though we're not binding any component. That's because our listener is registered with the `componentId` passed in the second argument.
+
+:::tip
+[underscopeio/react-native-navigation-hooks](https://github.com/underscopeio/react-native-navigation-hooks) is a wonderful library which greatly simplifies usage with hooks by introducing dedicated hooks for each event. The following example, which is taken from their docs, shows how to listen to all appear events and a particular screen's appear events:
+
+```jsx
+import { useNavigationComponentDidAppear } from 'react-native-navigation-hooks'
+
+const ScreenComponent = ({ componentId }) => {
+  // Global listener
+  useNavigationComponentDidAppear(e => {
+    console.log(`${e.componentName} (${e.componentId}) appeared`)
+  })
+
+  // Listen events only for this screen (componentId)
+  useNavigationComponentDidAppear(e => {
+    console.log(`${e.componentName} appeared`)
+  }, componentId)
+
+  return (
+    <View>
+      <Text>Screen Component</Text>
+    </View>
+  )
+}
+```
+:::

website/sidebars.js

@@ -12,6 +12,7 @@ module.exports = {
        'advanced-navigation',
        'screen-lifecycle',
        'passing-data-to-components',
+       'functionalComponents'
     ],
     Layouts: [
        'stack',