Merge branch '@ksienkiewicz/docs-core-functionalities' into @ksienkiewicz/docs-guides

Author: hejsztynx

docs/docs/core-functionalities/rendering-rich-text.mdx

@@ -59,6 +59,7 @@ the only shape difference from the input's `htmlStyle`. See the
 - **`useHtmlNormalizer`** - normalize external or messy HTML into the library's canonical
   tag subset before rendering. Defaults to `true`. See
   [Normalization](/fundamentals/core-concepts#normalization).
+- **`allowFontScaling`** - whether to respect the system's accessibility font scaling settings.
 
 :::note
 

docs/docs/core-functionalities/styling-the-input.md

@@ -12,6 +12,9 @@ everything from the container's dimensions down to the color of a bullet point.
 - **`htmlStyle`** - the appearance of individual rich text elements: heading
   sizes, blockquote borders, code colors, list markers, mention colors, and so
   on.
+- **`placeholderTextColor`** - the color of the placeholder text.
+- **`selectionColor`** - the color of the text selection highlight.
+- **`cursorColor`** - the color of the text cursor.
 
 ```tsx
 <EnrichedTextInput

docs/docs/core-functionalities/web-support.md

@@ -11,7 +11,8 @@ detail stays behind the same public API.
 
 ## One API across platforms
 
-The web build exposes the **same props, ref methods, and events** as native.
+The web build exposes the same core API as native - **props, ref methods, and events** -
+with one web-only addition - `sanitizationConfig` prop.
 Events keep their native shape too - they arrive as
 `NativeSyntheticEvent`, read off `e.nativeEvent`, so
 [event-handling](/core-functionalities/handling-events) code is portable as-is:

docs/docs/fundamentals/core-concepts.md

@@ -16,8 +16,8 @@ and you talk to it through a `ref`.
 
 This is deliberate. Rich text changes constantly - every character, selection
 move and style toggle - and round-tripping all of that through JavaScript state
-would be extremely slow and open to a possible de-synchronization of those states.
-Keeping it native makes the editor fast and stable.
+would be extremely slow and open to a possible de-synchronization of those states
+between the JS and native side. Keeping it in the native makes the editor fast and stable.
 
 In practice this means:
 
@@ -26,6 +26,13 @@ In practice this means:
 
 You never set a `value` prop and re-render to make an edit happen.
 
+:::note
+
+We have one value-setting prop - `defaultValue`. This provides the editor's initial value upon creation,
+so we don't violate the _uncontrolled_ nature of the component here.
+
+:::
+
 ## HTML is the source of truth
 
 The editor's content is HTML. `setValue` and `defaultValue` seeds it with an HTML string,

docs/docs/fundamentals/getting-started.md

@@ -23,7 +23,7 @@ renders the input's output. Both speak HTML - the input
 produces it, the display consumes it.
 
 Not only does this library allow you to apply basic rich text styles you know well,
-like *bold* or _italic_, but also provides more powerful tools like `mentions`, something
+like _bold_ or _italic_, but also provides more powerful tools like _mentions_, something
 you will learn more about in the next chapters.
 
 ## Prerequisites
@@ -60,7 +60,7 @@ The library contains native code, so rebuild your app after installing. On iOS,
 install the pods first:
 
 ```sh
-cd ios && bundler install && bundler exec pod install
+cd ios && pod install
 ```
 
 ### Expo
@@ -103,8 +103,7 @@ Install the package:
   </TabItem>
 </Tabs>
 
-The shipped components share the React Native's API, minus the functionalities a
-browser can't provide. See the _Web support_ guide for what's covered.
+The web version should work right out of the box. Check the details in the Web Support section. 
 
 ## Nightly builds
 

docs/docs/fundamentals/your-first-editor.mdx

@@ -8,7 +8,7 @@ import FirstEditorSrc from '!!raw-loader!@site/src/examples/FirstEditor';
 
 # Your first editor
 
-Let's build a small editor with a button that toggles bold and lights up when
+Let's build a small editor with a button that toggles bold and highlights when
 the current selection is bold. It's just enough to see the two moving parts of
 the library: **calling methods on the input** and **reading its state back**.
 
@@ -34,7 +34,9 @@ export default function App() {
 }
 
 const styles = StyleSheet.create({
-  container: { gap: 12 },
+  container: {
+    gap: 12
+  },
   input: {
     fontSize: 18,
     color: '#232736',
@@ -48,9 +50,6 @@ const styles = StyleSheet.create({
 
 ## Toggling a style
 
-The input is uncontrolled - you don't change its content through props. Instead
-you call methods on it through a `ref` of type `EnrichedTextInputInstance`.
-
 Add a ref and a button that calls `toggleBold`. Each call flips bold on the
 current selection, or arms it for the next characters you type if nothing is
 selected.
@@ -79,7 +78,9 @@ export default function App() {
 }
 
 const styles = StyleSheet.create({
-  container: { gap: 12 },
+  container: {
+    gap: 12
+  },
   input: {
     fontSize: 18,
     color: '#232736',
@@ -103,8 +104,11 @@ const styles = StyleSheet.create({
 });
 ```
 
-Every other style is toggled similarly via `ref` - there's a `toggleItalic`,
-`toggleUnderline`, `toggleH1`, `toggleOrderedList`, and so on.
+:::note
+
+To learn how you can toggle each of the available styles, visit [Basic styles](/rich-text-formatting/basic-styles).
+
+:::
 
 ## Reading the state back
 
@@ -147,7 +151,9 @@ export default function App() {
 }
 
 const styles = StyleSheet.create({
-  container: { gap: 12 },
+  container: {
+    gap: 12
+  },
   input: {
     fontSize: 18,
     color: '#232736',