Fix Navigation Menu links

Author: PoojaB26

docs/ff-concepts/adding-customization/cloud-functions.md

@@ -2,14 +2,14 @@
 slug: /concepts/custom-code/cloud-functions
 title: Cloud Functions
 description: Learn how to use Cloud Functions in your FlutterFlow app for serverless backend functionality.
-tags: [FlutterFlow, Cloud Functions, Serverless, Integration]
+tags: [Cloud Functions, Serverless, Integration]
 sidebar_position: 6
 keywords: [FlutterFlow, Cloud Functions, Serverless, Integration]
 ---
 
 # Cloud Functions
 
-[Cloud Functions](https://firebase.google.com/docs/functions) allows you to run backend code in response to events triggered by Firebase features and HTTPS requests. For example, you want to automatically send a welcome email to users when they sign up for your app. You can do this using a Cloud Function that triggers on Firebase Authentication's user creation event.
+[**Cloud Functions**](https://firebase.google.com/docs/functions) allows you to run backend code in response to events triggered by Firebase features and HTTPS requests. For example, you want to automatically send a welcome email to users when they sign up for your app. You can do this using a Cloud Function that triggers on Firebase Authentication's user creation event.
 
 We allow you to write and deploy Firebase Cloud Functions directly within the platform. With an integrated code editor, writing JavaScript cloud functions is quick and user-friendly. Each function has customizable boilerplate settings, including pre-configured essentials like memory, region, and timeout.
 
@@ -73,16 +73,18 @@ Few things to note here:
 
 To create and deploy a *Cloud Function* :
 
-1. Click on the **Cloud Functions** from the [*Navigation Menu*]
-(/getting-started/ui-builder/navigation-menu) (left side of your screen).
-5. Click **+ Add**. This will add the default newCloudFunction*.*
+1. Click on the **Cloud Functions** from the 
+[**Navigation Menu**](../../../docs/intro/ff-ui/builder.md#navigation-menu) (left side of your 
+   screen).
+5. Click **+ Add**. This will add the default `newCloudFunction`.
 8. Set the **Cloud Function Name**.
 
 #### Boilerplate Settings
 
 On the right side, you can configure the following Boilerplate Settings:
 1. **Memory Allocation**: You can specify the amount of memory your function should have when 
     it's executed based on its complexity and needs. This setting is crucial as it influences the function's performance and the cost of running it. More memory can enhance performance for intensive tasks but also increase costs.
+
 5. **Timeout (s)**: This refers to the maximum amount of time, in seconds, that a function is allowed to run before it is automatically terminated. If your function takes longer to execute, increasing the timeout setting may be necessary. However, be aware that longer timeouts can incur higher costs since billing is based on execution time.
 8. **Require Authentication**: Turn on this setting if you want users to be authenticated to execute this cloud function.
 11. **Cloud Function Region**: This determines the geographical location of the servers where your functions are hosted and executed. Ideally, you should keep this same as your *Default GCP resource location* and the Cloud Function Region specified in the Firebase Advanced Settings.
@@ -96,6 +98,7 @@ by configuring the input and output.
 
 1. To receive output from a Cloud Function, enable the **Return Value** and choose an 
         appropriate Type for the output, like 'String' for text. For this example, set it to *ImagePath* to get the URL of the generated logo.
+
 5. To input data: Click **+ Add parameters**. **Name** the parameter, select its **Type**, choose single or multiple items (**Is List** option), and uncheck **Nullable** if the value can be null. For this example, add a parameter 'prompt' with *Type* set to *String*.
 8. When using [Custom Data Types](/data-and-backend/custom-data-types), Cloud Function expects JSON, matching each field in the Data Type to a key-value pair in the JSON. If the Data Type is a list, the function expects a list of JSONs. For example, for a custom data type named 'Person' with fields 'Name' and 'Age,' the function should return:
 
@@ -129,6 +132,7 @@ For a list, the function should return:
 #### To deploy
 1. Click the `[</>]` icon to view the boilerplate code; a popup will open with the updated 
 code, and then click **`</> Copy to Editor`**. **Tip**: To see if you are able to deploy the cloud function (before adding your own code), proceed directly with steps 8 and 9.
+
 2. Inside the code editor, add the cloud function code. **Tip**: You can copy the boilerplate code 
    to [ChatGPT](https://chat.openai.com/) and ask it to write the desired code based on that.
 3. Click **Save Cloud Function**.

docs/ff-concepts/adding-customization/custom-files.md

@@ -66,7 +66,8 @@ Future setStatusbarColor() async {
 }
 ```
 
-2. Now click on **Custom Functions** from the [*Navigation Menu*](/getting-started/ui-builder/navigation-menu) (left side of your screen) and open the **Custom Files > main.dart**.
+2. Now click on **Custom Functions** from the 
+[**Navigation Menu**](../../../docs/intro/ff-ui/builder.md#navigation-menu) and open the **Custom Files > main.dart**.
 5. Determine where to place the code (i.e., **Initial Action** or **Final Action**), click the **+** button, and select the custom action.
 8. Click **Save**.
 

docs/ff-integrations/authentication/types/firebase-auth/auth-initial-setup.md

@@ -52,8 +52,8 @@ You have already enabled 'Create User Collection' while creating a new
 project with [Firebase Setup](../../../firebase/connect-to-firebase-setup.md).
 :::
 
-1. Click on the Firestore tab from the Navigation Menu (left side of your
-  screen).
+1. Click on the Firestore tab from the 
+[**Navigation Menu**](../../../../../docs/intro/ff-ui/builder.md#navigation-menu).
 2. Click on the **+ Create Collection** button. If you have any other collection
   already added, you can click on the Plus button.
 3. Enter a collection_name (this can be anything, but we recommend 'users') and

docs/intro/ff-ui/builder.md

@@ -10,11 +10,12 @@ keywords: [App Builder, FlutterFlow, UI, Design]
 
 # App Builder
 
-On opening the project, you'll see the App Builder, which consists of four main sections: [Navigation Menu](#navigation-menu), [Toolbar](#toolbar), [Canvas](#canvas-area), and [Properties panel](#properties-panel).
+On opening the project, you'll see the App Builder, which consists of four main sections: 
+[Navigation Menu](#navigation-menu), [Toolbar](#toolbar), [Canvas](#canvas-area), and [Properties panel](#properties-panel).
 
 ![app-builder](imgs/builder.avif)
 
-## Navigation Menu {#navigation-menu}
+## Navigation Menu
 
 The Navigation Menu, located on the left side of the builder, allows you to switch between various FlutterFlow features. These include designing the UI, managing databases, setting up API, adjusting app settings, adding integrations, and more.
 
@@ -36,14 +37,14 @@ Here is a list of all the features accessible from the navigation menu:
 14. **Theme settings**: Customize visual appearance.
 15. **Settings and Integrations**: Access app-related settings and integrations.
 
-## ToolBar {#toolbar}
+## ToolBar
 
 From [ToolBar](toolbar), you can search for project resources, change canvas size, see project history, branching, optimization and enhancements, view-download code, and run your app.
 
-## Canvas Area {#canvas-area}
+## Canvas Area
 
 In the [Canvas Area](canvas), you can see a preview of a device's screen and build your app page.
 
-## Properties Panel {#properties-panel}
+## Properties Panel
 
 The Properties Panel lets you modify both the visual appearance and interactive behavior of UI elements on the canvas. It allows you to add [Actions](#), set up a [Backend Query](#), add [Animations](#) and more.

docs/intro/ff-ui/canvas.md

@@ -20,7 +20,8 @@ This is the canvas of the device screen where you can build the user interface.
 
 ## Show or hide Navigation Menu
 
-From here, you can open or close the [Navigation Menu](#).
+From here, you can open or close the 
+[Navigation Menu](../../../docs/intro/ff-ui/builder.md#navigation-menu).
 
 ## Zoom Controls
 

docs/resources/control-flow/backend-logic/backend-query/backend-query.md

@@ -36,7 +36,10 @@ We offer you the following types of Backend Queries that you can specify on any
 
 ## Change loading indicator
 
-While the backend query is busy retrieving results, it shows the default *Project Theme Loading Indicator* (which you can change from [*Navigation menu*](/getting-started/ui-builder/navigation-menu) *> Theme Settings > Design System > Loading Indicator*.) However, if you want to replace this with a custom loading indicator in a specific backend query, follow the instructions below:
+While the backend query is busy retrieving results, it shows the default *Project Theme Loading 
+Indicator* (which you can change from 
+[**Navigation menu**](../../../../../docs/intro/ff-ui/builder.md#navigation-menu) *> Theme 
+Settings > Design System > Loading Indicator*.) However, if you want to replace this with a custom loading indicator in a specific backend query, follow the instructions below:
 
 <div style={{
     position: 'relative',
@@ -138,7 +141,7 @@ For example, an e-commerce app can cache product data, such as product descripti
 Caching backend queries works for all [types of queries](/data-and-backend/backend-query#types-of-query).
 :::
 
-:::Tip[Single time Query]
+:::tip[Single time Query]
 For Firebase queries, enable Single Time Query if you want the query to fetch data only once. Otherwise, the query operates in real-time, updating automatically as soon as the data changes.
 :::
 

docs/resources/control-flow/backend-logic/backend-query/document-from-reference.md

@@ -14,7 +14,7 @@ This backend query would help you in retrieving information from a document refe
 :::info[Prerequisites]
 In order to use this backend query, you should have:
 * Completed all the steps of 
-[Firebase Setup](docs/ff-integrations/firebase/connect-to-firebase-setup.md) for 
+[Firebase Setup](../../../../../docs/ff-integrations/firebase/connect-to-firebase-setup.md) for 
   your project.
 * At least one **Firestore Collection** is defined in your project.
 :::