Merge branch 'main' into feature/semantic-focus-config

Author: pinkeshmars

docs/ff-integrations/authentication/firebase-auth/google-login.md

@@ -126,7 +126,7 @@ To let users log out of your app, you can use the [**Logout**](auth-actions.md#l
       your [Project Credentials](https://console.cloud.google.com/apis/credentials?project=_) page.
 
     2. Ensure you are on the correct project. In our case, we are using the
-      [EcommerceFlow demo project](https://bit.ly/ff-docs-demo-v1), it will be different for you.
+      [EcommerceFlow demo project](https://bit.ly/ff-docs-demo-v2), it will be different for you.
 
     ![credential-page.png](../imgs/credential-page.png)
 

docs/ff-integrations/maps/google-maps/generate-maps-keys.md

@@ -69,10 +69,7 @@ com/embed/2c644aa950c44f76b19c6787784cf3b5?sid=3e22206e-4b4b-4734-b842-0c644d32f
 
 ## Add Places APIs
 
-To enable **Places API** in your project, please follow the steps under 
-["Add Maps API" section](#add-maps-apis) and additionally also enable Places API from the API 
-library if not 
-already enabled. 
+You can [enable the **Places API**](https://console.cloud.google.com/apis/library/places-backend.googleapis.com) from your Google Cloud Console — make sure you are in the correct Google Cloud project. **Please note** that the current [PlacePicker widget](../../maps/google-maps/place-picker-widget.md) uses the legacy Places API. We plan to update the PlacePicker widget soon to support the new API. In the meantime, ensure that the legacy Places API is enabled for full functionality.
 
 ![places-api.png](imgs/places-api.png)
 

docs/ff-integrations/maps/google-maps/place-picker-widget.md

@@ -47,7 +47,7 @@ Here's an example from the Demo app:
 
 :::info[Prerequisites]
 - The Place Picker **requires a Google Maps API key**. See how to [**create and add API keys**](generate-maps-keys.md#add-maps-apis) to FlutterFlow.
-- Ensure you have enabled **Places API** from Cloud console. [**Check out the Setup docs.**](generate-maps-keys.md#add-places-apis)
+- Ensure you have enabled the [**Places API**](generate-maps-keys.md#add-places-apis) from Cloud console.
 - Enable **Google Maps Platform Billing** via your Cloud console. Please note: Failing to enable the Google Maps Platform Billing will not show any place in an autocomplete list.
 :::
 <figure>
@@ -98,9 +98,9 @@ If you retain the Text widget, the text will update to the name of the selected
   <figcaption class="centered-caption">The widget properties of Place Picker widget</figcaption>
 </figure>
 
-## Use PlacePicker widget state values
+## Use PlacePicker Values
 
-The values associated with the selected place are stored in a `GooglePlace` custom data type exposed by FlutterFlow. It holds fields such as the selected place's Name, Address, LatLng, City, State, Country, and Zipcode. Users can use these values in any widget, either to directly set them in a Text widget or for further conditional calculations.
+The selected place’s details are stored in a `GooglePlace` custom data type provided by FlutterFlow. You can access this via **Widget State > placePickerValue**, which includes fields like name, address, latitude/longitude (LatLng), city, state, country, and ZIP code. These values can be used to display content in Text widgets or perform conditional logic based on the selected location.
 
 <div style={{
     position: 'relative',
@@ -109,7 +109,7 @@ The values associated with the selected place are stored in a `GooglePlace` cust
     width: '100%'
 }}>
     <iframe 
-        src="https://demo.arcade.software/uWaLSOHPZctjnGik03Pu?embed&show_copy_link=true"
+        src="https://demo.arcade.software/oje0Gsbf9IJh7M0pb6Tv?embed&show_copy_link=true"
         title="Use PlacePicker widget state"
         style={{
             position: 'absolute',
@@ -128,32 +128,4 @@ The values associated with the selected place are stored in a `GooglePlace` cust
     </iframe>
 </div>
 
-<p></p>
-Let's test this change in Test Mode:
-
-<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/2ncapOklwNGM3ETCntdl?embed&show_copy_link=true"
-        title="Place Picker Test"
-        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>

docs/generated-code/component-gen-code.md

@@ -9,7 +9,7 @@ sidebar_position: 5
 Similar to a [**Page**](pages-generated-code.md), when creating a **[component](../resources/ui/components/intro-components.md)** in FlutterFlow, it automatically generates two files: a `Widget` class and a `Model` class. 
 
 :::info[Prerequisites]
-This guide uses examples from the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
+This guide uses examples from the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v2)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
 :::
 
 ## ComponentModel class

docs/generated-code/custom-data-type-gen.md

@@ -7,7 +7,7 @@ sidebar_position: 2
 # DataTypeStruct class
 
 :::info[Prerequisites]
-This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
+This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v2)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
 :::
 
 

docs/generated-code/directory-structure.md

@@ -7,7 +7,7 @@ sidebar_position: 1
 # Directory Structure
 
 :::info[Prerequisites]
-This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
+This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v2)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
 :::
 
 When you download the code generated by FlutterFlow, you'll notice many additional files and folders beyond what you see in FlutterFlow's Code Viewer. These files make up the complete project structure, organized according to a specific architecture. Understanding this structure is like having a detailed map, guiding you through the code and making it easier to navigate and customize your FlutterFlow project later. So, let's dive in and explore this directory structure.

docs/generated-code/ff-app-state.md

@@ -6,14 +6,14 @@ sidebar_position: 4
 # FFAppState
 
 :::info[Prerequisites]
-This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
+This guide uses example of the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v2)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
 :::
 
 The `FFAppState` class in FlutterFlow acts as a central hub for managing the application's global state. It's designed as a singleton, meaning there's only one instance of this class throughout the app's lifecycle. This class extends [**ChangeNotifier**](https://api.flutter.dev/flutter/foundation/ChangeNotifier-class.html), allowing widgets to listen and react to state changes.
 
 It includes methods for initializing and updating the app's persisted state and also defines various state variables with corresponding **getters and setters** for manipulating these values.
 
-Here is a basic template of the class, taken from the [**eCommerceFlow demo app**](https://bit.ly/ff-docs-demo-v1)'s generated code:
+Here is a basic template of the class, taken from the [**eCommerceFlow demo app**](https://bit.ly/ff-docs-demo-v2)'s generated code:
 
 ```js
 class FFAppState extends ChangeNotifier {

docs/generated-code/pages-generated-code.md

@@ -9,7 +9,7 @@ sidebar_position: 5
 When you create a new Page in FlutterFlow, it automatically generates two files: a `Widget` class and a `Model` class. So if the name of the page you created is called **ProductListPage**, FlutterFlow generation backend will automatically create **ProductListPageWidget** class and **ProductListPageModel** class. 
 
 :::info[Prerequisites]
-This guide uses examples from the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v1)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
+This guide uses examples from the generated code of the **[EcommerceFlow demo app](https://bit.ly/ff-docs-demo-v2)**. To view the generated code directly, check out the **[Github repository](https://github.com/FlutterFlow/sample-apps/tree/main/ecommerce_flow)**.
 :::
 
 ## PageModel class

docs/resources/control-flow/functions/utility-functions.md

@@ -30,7 +30,7 @@ FlutterFlow has the following built-in functions:
 ## Combine Text
 
 Oftentimes, you will encounter scenarios where you need to show two variables in a single String or
-Text widget. For example, in our [Ecommerce Demo](https://bit.ly/ff-docs-demo-v1) app, we have a price object in the following
+Text widget. For example, in our [Ecommerce Demo](https://bit.ly/ff-docs-demo-v2) app, we have a price object in the following
 format:
 
 ```json

docs/resources/ui/components/intro-components.md

@@ -67,7 +67,7 @@ some common use-cases.
 - Design sections of a screen that are frequently repeated, such as testimonials, image galleries,
    or feature highlights, and reuse them to maintain a cohesive layout.
 
-Here's an example of all the widely used components used in the [EcommerceFlow demo](https://bit.ly/ff-docs-demo-v1) app.
+Here's an example of all the widely used components used in the [EcommerceFlow demo](https://bit.ly/ff-docs-demo-v2) app.
 
 
 <figure>