Merge branch 'main' into david/troubleshootingtopics

Author: PoojaB26

docs/ff-concepts/design-system/design-system.md

@@ -256,7 +256,7 @@ Here are all the properties you can customize:
 
     ![main-axis-margin](../imgs/main-axis-margin.avif)
 
-6. **Cross Axis Maring:** This refers to the space or gap along the cross direction of the scrollbar. For instance, in a vertically scrolling list, it refers to the left and right spacing, and in a horizontally scrolling list, it refers to the top and bottom spacing.
+6. **Cross Axis Margin:** This refers to the space or gap along the cross direction of the scrollbar. For instance, in a vertically scrolling list, it refers to the left and right spacing, and in a horizontally scrolling list, it refers to the top and bottom spacing.
 
     ![cross-axis-margin](../imgs/cross-axis-margin.avif)
 

docs/ff-concepts/state-management/imgs/rebuild.avif

@@ -49,5 +49,14 @@ You can learn more about state management from this video:
 :::
 
 
+## Rebuild [Action]
 
+The **Rebuild** action allows you to refresh a page or a component’s UI. This is especially useful when data changes dynamically; for example, after an API call, a database update, a custom action, or a class method modifies the internal state, and you want the latest data or UI state to be reflected instantly.
 
+The Rebuild action provides different update types depending on where it is used:
+
+- **Rebuild Page:** When on a page, you will see the **Rebuild Current Page** option, which refreshes the entire page’s UI.
+- **Rebuild Component:** When on a component, you will see the **Rebuild Current Component** option, which refreshes only that specific component.
+    - **Rebuild Containing Page:** When on a component, you will see this option as well, which refreshes the entire page that contains the component. For example, if you have a **"Confirm"** button inside a dialog component that updates an order’s status, selecting this action will refresh the parent page to instantly show the updated order list.
+
+![rebuild](imgs/rebuild.avif)

docs/ff-concepts/state-management/state-variables.md

@@ -410,6 +410,15 @@ To autofocus a TextField, select the TextField widget, move to the **Properties
 </div>
 <p></p>
 
+### Enable Interactive Selection
+
+The **Enable Interactive Selection** toggle controls whether users can interact with the text selection features, such as long-press selection, copy/paste menus, and selection handles.
+
+By default, this property is set to **True**, allowing users to select, copy, and paste text using the platform's built-in text selection controls. Disabling this can help prevent unintended text copying or editing, especially in sensitive fields.
+
+
+![interactive-selection](../imgs/interactive-selection.avif)
+
 ### Autocomplete a TextField
 
 You might want to allow users to enter the text by suggesting them a list of items. The suggested items are shown if it contains the currently entered text from TextField. For example, using autocomplete to get the *Country* *name*, *Fruit* *name*, etc.

docs/resources/control-flow/user-interactivity/forms/form-widgets/text-field.md

@@ -114,6 +114,10 @@ Here's a quick guide to updating the app state variable. We need to add an actio
     </iframe>
 </div>
 
+:::tip
+If you want to rebuild a page or component without updating any state variables, use the [**Rebuild**](../../ff-concepts/state-management/state-variables.md#rebuild-action) state action.
+:::
+
 ## FAQs
 
 <details>

docs/resources/control-flow/user-interactivity/forms/imgs/interactive-selection.avif

@@ -253,17 +253,17 @@ You can easily upgrade to newer versions of the libraries as they become availab
 
 ## Library Pages
 
-You can also add and manage pages within a library, making it easy to reuse those pages across multiple projects. These pages function like any regular project page in your app; they support navigation, parameters, state management, and transitions. 
+When you publish a library, all the pages included in the library become available for use in the consumer project. These pages function like any regular project page in your app; they support navigation, parameters, state management, and transitions. 
 
-Including pages with libraries offers a modular approach to development, making it ideal for large teams and complex, multi-feature apps. For example, instead of recreating common flows like onboarding and payment flows, you can build them in a library once and use them wherever needed.
+Library Pages offers a modular approach to development, making it ideal for large teams and complex, multi-feature apps. For example, instead of recreating common flows like onboarding and payment flows, you can build them in a library once and use them wherever needed.
 
 :::tip[Possible Use Cases]
 - **Super Apps** like Gojek and Uber with distinct modules such as ride booking, shopping, and payments. Each module can be developed as a separate library and imported into a single main project.
 - **Enterprise Apps** with isolated user journeys for different roles, such as admin and customer. Each role-based flow can be built as its own library and integrated into the core app as needed.
 - **White-labeled Apps** that share common onboarding flows can benefit from libraries. The onboarding process can be built once as a library and reused across all branded versions of the app.
 :::
 
-The library author selects which pages to include and publishes the library. When users import or update the library, they can override the default route names to prevent conflicts between the library and their project. Library pages then appear in navigation actions just like any regular page.
+When users import or update the library, they can override the default route names to prevent conflicts between the library and their project. Library pages then appear in navigation actions just like any regular page.
 
 <div style={{
     position: 'relative',
@@ -291,7 +291,50 @@ The library author selects which pages to include and publishes the library. Whe
 </div>
 <p></p>
 
+### Library Pages in NavBar
 
+Library pages can also be used in the NavBar, allowing users to add reusable flows into the app’s primary navigation structure. For example, in a Super App, you can import ride booking, food delivery, or payment pages from separate libraries and add them directly to the bottom navigation, giving users quick access to each module.
+
+:::tip
+Want to learn more about building modular Super Apps using libraries? Check out our [**blog post**](https://blog.flutterflow.io/scaling-super-apps-modular-architecture-with-flutterflow-libraries/).
+:::
+
+To display a library page on the NavBar, navigate to **Project Dependencies > FlutterFlow Libraries**, then click on **Pages** for the relevant library to open its details. In the list of pages, locate the desired page and click **Nav Bar Settings**, then enable **Show on NavBar**. You can also customize additional settings, such as label and icon, as needed.
+
+To confirm, go to the **Nav Bar & App Bar** section, where you’ll see the library page listed as part of the NavBar items.
+
+:::info
+NavBar settings for regular pages are available directly within the Page Settings panel in the builder. However, for Library pages, these settings are managed through the Library Details dialog.
+
+![NavBar-settings-for-regular-and-library-page](imgs/NavBar-settings-for-regular-and-library-page.avif)
+:::
+
+
+<div style={{
+    position: 'relative',
+    paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
+    height: 0,
+    width: '100%'}}>
+    <iframe 
+        src="https://demo.arcade.software/BDac382RQTHTKFhtZcsc?embed&show_copy_link=true"
+        title=""
+        style={{
+            position: 'absolute',
+            top: 0,
+            left: 0,
+            width: '100%',
+            height: '100%',
+            colorScheme: 'light'
+        }}
+        frameborder="0"
+        loading="lazy"
+        webkitAllowFullScreen
+        mozAllowFullScreen
+        allowFullScreen
+        allow="clipboard-write">
+    </iframe>
+</div>
+<p></p>
 
 ## Library Values
 

docs/resources/data-representation/app-state.md

@@ -249,6 +249,10 @@ Type** property in your Action properties. Here's what it means:
 - **No Rebuild:** Choose this option when you need to update the state value without
   immediately reflecting the changes in the UI.
 
+:::tip
+If you want to rebuild a component without updating any state variables, use the [**Rebuild**](../../../ff-concepts/state-management/state-variables.md#rebuild-action) state action.
+:::
+
 :::warning[Expensive Rebuilds]
 Too many rebuilds can impact performance because rebuilding the widget tree
 frequently consumes resources and may lead to decreased responsiveness and

docs/resources/projects/imgs/NavBar-settings-for-regular-and-library-page.avif

@@ -327,13 +327,17 @@ update, create a new Action called **Update Page State**.
 When updating your page state in Flutter, you'll often come across the **Update
 Type** property in your Action properties. Here's what it means:
 
-**Rebuild Current Type:** This option triggers a re-rendering of the page,
+**Rebuild Current Page:** This option triggers a re-rendering of the page,
 ensuring
 that any changes to the state are reflected in the user interface (UI).
 
 **No Rebuild:** Choose this option when you need to update the state without
 immediately reflecting the changes in the UI.
 
+:::tip
+If you want to rebuild a page without updating any state variables, use the [**Rebuild**](../../../ff-concepts/state-management/state-variables.md#rebuild-action) state action.
+:::
+
 :::warning[Expensive Rebuilds]
 Too many rebuilds can impact performance because rebuilding the widget tree
 frequently consumes resources and may lead to decreased responsiveness and