Coming from JS, this can be disturbing. You could think it's unused, since _ are often unused to avoid non usage warning.

We could also try to remove them & use lowercase.

Thoughts @cknitt @sgny ?

The problem

Clicking the button «Get started» on the landing pge does nothing. Tested on latest iOS Safari.

How to reproduce

1. Go to landing page.
2. Try to click the «Get started» button.

Expected behavior

Clicking the button should take me to the get started page.

Actual behavior

Nothing happens. Button does not respond.

Environment

Latest iOS Safari at the time of writing.
Ask if more info is needed.

For convenience so we can easily get internal links.

Is possible based in documentation of react-native create one documentation of component like:

• Text - #21
• Button - #22
• ActivityIndicator
• Fllatlist
• Image
• ImageBackground
• KeyboardAvoidingView
• Modal
• Press
• RefreshControl
• ScrollView
• SectionList
• StatusBar
• Switch
• TextInput
• TouchableHighlight
• TouchableOpacity
• TouchableWithoutFeedback
• View
• VirtualizedList

People are going to look for it.

The problem

The Edit Link at each page leads to the old github repo.

How to reproduce

Visit any of the pages (for example, getting-started), and click the Edit button.

The problem

Almost all of the of the React Native component documentation is not available on the website.

How to reproduce

Navigate to: https://rescript-react-native.github.io/docs/keyboardavoidingview, or most other components, and see that there is no documentation. The only one with documentation I've come across is: https://rescript-react-native.github.io/docs/pressable.

Expected behavior

I'd expect at the very least the component definition so I can see the prop names for the bindings, or more ideally the props + an example usage + link to official RN documentation.

Actual behavior

No documentation at all.

I often have to open the source code to figure out how to use a component. It seems pretty unideal

Environment

Firefox: 91.0

or

Chrome: 92.0.4515.131

The problem

This site is very good, but no has documentation on how to run this site.

Considered solution

build documentation on how to run this site locally.