Merge branch 'main' into feature/update-adding-design-system

Author: PoojaB26

docs/ff-concepts/adding-customization/vscode-extension.md

@@ -231,6 +231,72 @@ To delete a Custom Action or Widget, delete the associated file.
 ### Adding New Dependencies
 You can add custom [pub.dev](https://pub.dev/) package dependencies with the `Dart: Add Dependency` command from the Visual Studio Code command palette. This will update the `pubspec.yaml` file.
 
+## Using Flutter Version Management (FVM)
+If you want to manage Flutter versions with [**Flutter Version Management (FVM)**](https://fvm.app/), you need to install it and add it to your system’s PATH. Follow these steps to get started:
+
+### Install FVM
+
+To install **FVM**, run the following command in your terminal. This installs FVM globally using Dart’s package manager.
+
+```
+dart pub global activate fvm
+```
+
+### Add FVM to Your System’s PATH
+
+After installation, you need to add the directory containing FVM’s executables to your **PATH variable** so that it can be accessed globally.
+
+#### For macOS & Linux
+
+1. Open the Terminal and run the following command. It adds the `~/.pub-cache/bin` directory to your system's `PATH` permanently by updating your `~/.zshrc` file. This ensures that the FVM installed in `~/.pub-cache/bin` is accessible from anywhere in the terminal.
+    
+    ```bash
+    echo 'export PATH="$PATH":"$HOME/.pub-cache/bin"' >> ~/.zshrc  # For Zsh
+    echo 'export PATH="$PATH":"$HOME/.pub-cache/bin"' >> ~/.bashrc # For Bash
+    ```
+    
+2. Restart your terminal or run `source ~/.zshrc` (or `source ~/.bashrc`) to apply the changes.
+
+#### For Windows
+
+1. Locate the **FVM executable path**, typically:
+    
+    ```
+    C:\Users\YourUsername\AppData\Local\Pub\Cache\bin
+    ```
+    
+2. Add this path to your **System’s PATH variable**:
+    1. Open **System Properties** → **Advanced system settings**.
+    2. Click **Environment Variables**.
+    3. Under **System variables**, select **Path** → **Edit**.
+    4. Click **New** and add the above path.
+    5. Click **OK** and restart your terminal.
+
+
+### Verify the Installation
+
+To check if FVM is correctly installed and accessible, run:
+
+```bash
+fvm --version
+```
+
+If this command prints the installed version of FVM, it means FVM is successfully installed and added to PATH.
+
+
+### Configure FVM in Your Flutter Project
+
+Once FVM is installed, navigate to your Flutter project folder and set up FVM:
+
+```bash
+cd your-flutterflow-project
+fvm init
+fvm install <flutter_version>
+fvm use <flutter_version>
+```
+
+*(Replace `<flutter_version>` with the required Flutter version.)*
+
 
 ## FAQs
 <details>

docs/ff-integrations/firebase/connect-to-firebase-setup.md

@@ -168,9 +168,9 @@ com/embed/1abddd1120db477da2c085dbc6b7a742?sid=5b161c8b-3957-4ac9-b27f-dc5ebc03f
 
 
 
-## Enable Billing for Cloud Functions Access
+## Enable Billing
 
-If you want to deploy functions (e.g., Braintree payments, Push Notifications), you will need to enable billing for your Firebase project. Please follow these steps to enable billing:
+If you want to deploy [Cloud Functions](https://firebase.google.com/products/functions) (e.g., Braintree payments, Push Notifications) or use [Firebase Cloud Storage](https://firebase.google.com/products/storage), you will need to enable billing for your Firebase project. Please follow these steps to enable billing:
 
 1. From the Firebase dashboard of your project, navigate to the far left menu. Under Build, select **Functions** and then select **Upgrade project**.
 

docs/resources/data-representation/global-properties.md

@@ -33,7 +33,7 @@ A list of all the available global properties is as follows:
 
 - **Current Device Location:** Obtains he user's current location, ideal for updating their position on Google Maps or storing it in a backend database. [Check out examples](#current-device-location) on how to retrieve and save the current device location.
 
-- **Link To Current Page:** Provides the deep link of the current page. Learn more about [adding deep links here](../../ff-concepts/navigation-routing/deep-dynamic-linking.md#adding-deep-link).
+- **Current Route Path**: Provides the route name of the currently active or visible page in your app. This property is especially helpful in scenarios where you want to adjust or block specific actions if the active page isn't the one you expect. For example, if you launch the app through a push notification, the home page might still run in the background, even if the notification directs you to a different page. Using this property, you can prevent unnecessary action triggers, such as On Page Load from the home page. See details on avoiding [this issue](https://github.com/FlutterFlow/flutterflow-issues/issues/2765#issuecomment-2598915946).
 - **Fraction of Screen Width:** Determines the proportional width of the device's screen.
 - **Fraction of Screen Height:** Determines the proportional height of the device's screen.
 - **Screen Width:** Provides the total width of the current device's screen in pixels.
@@ -45,7 +45,7 @@ A list of all the available global properties is as follows:
 - **Is Dark Mode:** Checks if the app's current theme mode is set to dark.
 - **Is Light Mode:** Checks if the app's current theme mode is set to light.
 - **Is On-Screen Keyboard Visible:** Checks if the on-screen or soft keyboard is visible. This is helpful in making UI adjustments if keyboard is visible on screen. See a [quick example](#is-on-screen-keyboard-visible). 
-
+- **Current Environment**: Gives you the current [development environment](../../testing-deployment-publishing/development-environments/development-environments.md) value.
 
 :::tip[Generated Code]
 Learn more about the [**Generated Code**](../../ff-concepts/state-management/generated-code.md#global-state) behind Global Properties.

docs/resources/projects/libraries.md

@@ -80,6 +80,17 @@ To publish a FlutterFlow project as a library, start by creating a FlutterFlow p
 - It's recommended to include a message that tells users what has changed in the version your are publishing.
 :::
 
+:::warning
+To publish a project as a library, it must meet the following requirements:
+
+- **No Prior Store Deployment**: The project must not have been deployed to the Google Play Store or Apple App Store.
+- **No Failed Deployments**: The Publish button remains disabled if a deployment process was started and failed.
+- **No Errors or Warnings**: All project errors or warnings must be addressed beforehand.
+- **Main Branch Only**: You can only publish from the main branch.
+- **Pro Plan Subscription**: A Pro Plan is required to publish a project as a Library.
+- **Not Cloned from Marketplace**: The project cannot be a clone of a Marketplace item.
+:::
+
 ### Disabled Features in a Library
 
 When a project is converted into a library, the following features are disabled to ensure compatibility and functionality limitations:

docs/testing-deployment-publishing/branching-collaboration/branching.md

@@ -384,6 +384,34 @@ You can modify files or edit the project directly from the lower panel at any ti
 
 After editing, click **Save Changes** to confirm your changes. A red reset button appears if you want to undo your changes and restore the file to its initial state before you began editing.
 
+For more information, check out the video below.
+
+<div style={{
+    position: 'relative',
+    paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
+    height: 0,
+    width: '100%'}}>
+    <iframe 
+        src="https://www.youtube.com/embed/r8BR248HR0U"
+        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>
+
 ### Resolve Merge Conflicts
 A merge conflict occurs when multiple team members make changes to the same part of the project.
 
@@ -526,15 +554,9 @@ To configure these permissions, navigate to **Settings & Integrations > Project
 
 Closing a branch is a common practice after the branch has served its purpose, typically once its changes have been merged into another branch (like the `main` or `development` branch). By regularly closing inactive or merged branches, you help maintain a clean, efficient, and well-organized project.
 
-### When to Close a Branch
-
+:::info[When to Close a Branch]
 - **After a Merge:** Once the branch’s changes have been merged into the `main` branch (or another target branch), it’s safe to close the branch. This often happens after a feature is complete or a bug is fixed.
 - **Unused Branch:** If a branch is no longer needed (e.g., a feature was abandoned or changes were made in another branch), it’s a good idea to close it.
-
-:::warning
-
-Once a branch is closed, it will no longer appear in the list of active **Branches**, meaning no further changes can be made. **This action is permanent and cannot be undone**, so ensure that all necessary work is completed or merged before closing the branch.
-
 :::
 
 Here’s how you can close a branch:
@@ -571,6 +593,40 @@ Here’s how you can close a branch:
 - **Coordinate with your team:** If you’re working in a team, ensure that no one is actively using the branch before you close it, to avoid disrupting ongoing work.
 :::
 
+Once a branch is closed, it will no longer appear in the list of active branches. However, you can restore a closed branch within **30 days** of its closure.
+
+### Restore Branch
+To restore a branch, open the **Branch Filter** menu and enable **Show Closed Branches**. Search for or select the branch you want to restore, and it will open in a new browser tab. Then, within the closed branch, open the **Branching Options** menu and select **Restore Branch** to reactivate it.
+
+
+<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/RQ8lrFH85EZr71sQ7VKN?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>
+
+
+
 ## FAQs
 <details>
 <summary>

firebase.json

@@ -2317,6 +2317,11 @@
         "source": "/misc/flutterflow-experts",
         "destination": "/misc/hire-flutterflow-developer",
         "type": 301
+      },
+      {
+        "source": "/firebase-content-manager",
+        "destination": "/integrations/database/cloud-firestore/firestore-content-manager/",
+        "type": 301
       }
     ]
   }