* Completely rewritten the docs from scratch
* More coherent separation between guides and API documentation
* Switched to Docusaurus 2 since Docsify is deprecated
* More code samples
* Images and animated gifs were added where appropriate improve clarity (more will be added in the future)

When mergeOptions is called before a view is created or after it's destroyed, don't attempt to create the view.

Fixes #6097

Add snapshot tests

Prevously: Adding a sideMenu with no width resulted in the side content having 100% width (partially drawn behind center view). Adding a sidemenu with a width option resulted in SafeAreaView inside the side content not working (content obstructed by iPhone notch).

Undoing the fix in commit 37f5697 fixes the first problem.
Calling setNeedsLayout on the sideMenu also fixes the original problem of SafeAreaView not working correctly. Although I am not sure why this is needed. There may a better solution.

Co-authored-by: Yogev Ben David <yogev132@gmail.com>

* Use viewController hidesBottomBarWhenPushed method for bottomTabs visibility

Refactor right buttons

This pr started with an attempt to eliminate button flickering entirely when updating buttons which contain react components via mergeOptions. While the attempt wasn't 100% successful, I dit get some insights in the process.

* It's not possible to add buttons at specific indices. Buttons contain an order property which determines the order of the button in the TopBar. To somewhat overcome this limitation, we can let users control button order via options.

* When a right most component button is replaced with another component button, the rest of the buttons shift to the right since the newly added component isn't measured when it's added to the menu and its width is zero. 
We usually handle this situation with the `waitForRender` option but since buttons are measured with `MeasureSpec.UNSPECIFIED`, their dimensions are zero. Because of this, I've added options to set button dimensions.

* When updating buttons via mergeOptions, if a component button is already added to the menu with the same order we will not remove and added it again. This mitigates flickering in some situations.

* Textual button style properties were applied by traversing the view hierarchy and searching for the TextView corresponding to the button and updating its styles directly.
There was an inherent bug in this logic where if two buttons contained the same text, styles could have been applied to the wrong TextView. We now apply styles directly on the button using spans.

* Fix invalid popover enum value for modal presentation style

The correct enum value as defined in lib/ios/RNNConvert.m is "popover" not "popOver", in line with UIModalPresentationPopover.

* Add to documentation on modal presentation styles

Add popover value and link to iOS documentation.

Co-authored-by: Yogev Ben David <yogev132@gmail.com>

iOS 13.4 doesn't allow overriding UIViewController's methods in categories (and it's also discouraged by apple) which causes styles to break.

Move UIViewController override methods from category to controllers.
Fixes BottomTab style visibility
Fixes statusBar.style
Closes #6075

This commit fixes statusBar.visible option which stopped working on iOS 13.

Show transparent overlay option in docs

This commit fix topBar background wrong color when swiping pop gesture on iOS 13 and above.

Addresses #6055

This commit fixes a bug related to setting a new react component as title via mergeOptions. When a title component was set, and the user tried to replace the existing title with a new title via mergeOptions, the new title was not created and instead the current title was reapplied.
Fixes #5377

This is probably leftover from the previous Shared Element implementation which was refactored in v5

* Configure scrollEdgeAppearance with opaque background

I noticed there is now an animation that occurs when pushing the first
view on a stack. This will happen with both:

`largeTitle: { visible: true }`
and
`largeTitle: { visible: false }`

It seems caused by the setting of the `scrollEdgeAppearance` background
without first configuring it using `configureWithOpaqueBackground`.

I also added checks for iOS 13 since these APIs require iOS 13.

* Update lib/ios/TopBarAppearancePresenter.m

Co-Authored-By: Yogev Ben David <yogevbd@wix.com>

* Update lib/ios/TopBarAppearancePresenter.m

Co-authored-by: Yogev Ben David <yogev132@gmail.com>
Co-authored-by: Yogev Ben David <yogevbd@wix.com>

When no modals are displayed and dismissAllModals is called, resolve the promise successfully. This regression was introduced in #5991

Add id property to Button component interface

Split animation config in playground to custom animations and slow animations

Solves an issue where setting bottomTabs.badge with mergeOptions resets the bottomTab icon and title.

* Fix possible retain cycles in commands handler
* Fix compiler build warnings

Until now the promise was rejected only on Android.

Co-authored-by: Guy Carmeli <guyca@users.noreply.github.com>

Removed stale code from ModalScreen as well.

While it's not used at the moment, we can use it at some point in Overlay e2e or for debugging purposes.

Added pop animation and tweaked values a bit.

Check if prefersLargeTitles is supported to avoid a crash on iOS < 11.0

Added windows compatibility to build scripts. To run the packager on windows, use: `npm run start-windows`

Co-authored-by: Guy Carmeli <guyca@users.noreply.github.com>

Co-authored-by: Guy Carmeli <guyca@users.noreply.github.com>

Resolves largeTitle background color from topBar.title.background.color

Co-authored-by: Guy Carmeli <guyca@users.noreply.github.com>

* Fix translucent bottomTabs

* Remove unnecessary safeAreaView from Root component

* Add bottomTabsPresenter base class

* Revert Root.js

* DrawBehind when largeTitle is visible

Co-authored-by: Guy Carmeli <guyca@users.noreply.github.com>

Fix an issue where bottomTab.testID doesn't get updated on mergeOptions unless a new UITabBarItem is created. Look like an issue in iOS where tabBarItem.accessibilityIdentifier doesn't get updated unless a new tabBarItem is created.