Integrations II (#37)

* Add GitHub integration

* Add Gemini integration (setup + howto)

* Add Google Analytics integration

* Add Mux Livestream docs

* Add Mux Livestream images

* Add One Signal notification docs

* Add Deep Dynamic Linking docs

* Add Push Notifications docs

* Add Supabase Auth docs

* Move old docs of Firestore (in progress)

* Add all docs of Firestore

* Add all docs of Firestore

* Add supabase & sqlite

Author: PoojaB26

docs/Integrations/authentication/types/supabase-auth/initial-setup.md

@@ -9,7 +9,7 @@ To use authentication, you will need to complete the following initial setup:
 
 
 :::info[Prerequisites]
-Before you begin, make sure you have completed the [Supabase setup](/data-and-backend/supabase/supabase-setup).
+Before you begin, make sure you have completed the [**Supabase setup**](/data-and-backend/supabase/supabase-setup).
 :::
 
 ### 1. Creating a "users" table

docs/Integrations/database/Supabase/database-actions.md

@@ -0,0 +1,201 @@
+---
+title: Database Actions
+toc_max_heading_level: 5
+
+---
+
+# Supabase Database Actions
+
+The Supabase Database Actions allow you to **Insert, Update**, or **Delete a Row** from a Supabase table.
+
+:::note[Prerequisites]
+Before getting started with this section, ensure you have,
+
+1. Completed all steps in the [**Supabase setup**](..%2F..%2Fsupabase%2Fsupabase-setup.md)
+2. Ensure you have a table created for adding, updating, and deleting data.
+:::
+
+
+## Types of Supabase Database Actions
+
+Following are the types of actions you can perform on a Supabase table.
+
+- [**Insert Row**](#insert-row-action): Adds a new row in a table.
+- [**Update Row**](#update-row-action)**:** Updates a row with the specified values.
+- [**Delete Row**](#delete-row-action)**:** Deletes a row from a table.
+- [**Query Rows**](#query-rows-action): Retrieves 
+	rows from a table based on specific criteria or conditions.
+
+### Insert Row [Action]
+
+1. Select the **Widget** (e.g., Button) on which you want to define the action.
+5. Select **Actions** from the Properties Panel (the right menu), and click **Open**. This will 
+   open an **Action Flow Editor** in a new popup window.
+
+	1. Click on **+ Add Action**.
+	5. On the right side, search and select the **Supabase** > **Insert Row** action.
+	8. Set the **Table** to your table name (e.g., assignments).
+	11. Under the **Set Fields** section, click on the **+ Add Field** button.
+	14. Click on the Field name.
+
+		1. Scroll down to find the **Value Source** dropdown and change it to **From Variable**.
+		5. Click on **UNSET** and select **Widget State > Name** of the TextField.
+	17. Similarly, add the field for the other UI elements.
+
+:::tip[Pro Tip]
+While adding this action, you can leave the **id** (if marked as *Primary*) and 
+        **created_at** (if default value is `now()`) fields. Supabase will automatically add values for these fields.
+:::
+
+<div class="video-container"><iframe src="https://www.loom.
+com/embed/f2a75f9b0e144f6aab06cc1f0965541b?sid=6f57ff8a-ca2a-4c47-833d-03fa928b8301" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
+
+
+
+### Update Row [Action]
+
+1. Select the **Widget** (e.g., Button) on which you want to define the action.
+5. Select **Actions** from the Properties Panel (the right menu), and click **Open**. This will 
+   open an **Action Flow Editor** in a new popup window.
+
+	1. Click on **+ Add Action**.
+	5. On the right side, search and select the **Supabase** > **Update Row** action.
+	8. Set the **Table** to your table name (e.g., assignments).
+	11. Optional: If you want to get the rows after the update is finished, enable the **Return Matching Rows** option.
+	14. Now, you must set the row you want to update. Usually, this is done by finding a row in a table that matches the current row ID. To do so, click **+ Add Filter** button inside the **Matching Rows** section.
+
+		1. Set the **Field Name** to the field that contains the IDs. Typically, this is the 
+        **id** column.
+		5. Set the **Relation** to **Equal To** because you want to find a row with the exact id.
+		8. Into the **Value Source**, you can select the **From Variable** and provide the id of the row for which you just updated values in the UI.
+	17. Under the **Set Fields** section, click on the **+ Add Field** button.
+	20. Click on the Field Name.
+	
+		1. Scroll down to find the **Value Source** dropdown and change it to **From Variable**.
+		5. Click on **UNSET** and select **Widget State > Name** of the TextField.
+	23. Similarly, add the field for the other UI elements.
+
+
+
+
+
+:::tip[How to & Tips]
+
+<div class="video-container"><iframe src="https://www.loom.
+com/embed/08cb8a851350428bbc226f2e7ce9d2b3?sid=b3d097cf-6f84-4f69-893a-3a363cbf7143" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
+
+<p></p>
+If you have a flow like this, *HomePage* -> *AssignmentDetailsPage* ->
+*UpdateAssignmentPage*, you can enable the **Replace Route** option (see point no. 5 [here](/actions/actions/navigation/navigate)) when you navigate from *AssignmentDetailsPage* to *UpdateAssignmentPage*. And then chain the [Navigate Back](/actions/actions/navigation/navigate-back#adding-navigate-back-action) action after the update action. This will directly open the *HomePage* after the row is updated.
+:::
+
+
+
+### Delete Row [Action]
+
+Go to your project page on FlutterFlow and follow the steps below to define the Action to any widget.
+
+1. Select the **Widget** (e.g., Button) on which you want to define the action.
+5. Select **Actions** from the Properties panel (the right menu), and click **Open**. This will open an **Action Flow Editor** in a new popup window.
+
+	1. Click on **+ Add Action**.
+	5. On the right side, search and select the **Supabase** -> **Delete Row** action.
+	8. Set the **Table** to your table name (e.g., assignments).
+	11. Optional: If you want to know which rows were deleted from a table, enable the **Return 
+		Matching Rows** option.
+	14. Now, you must set the row you want to delete. Usually, this is done by finding a row in a table that matches the current row ID. To do so, click **+ Add Filter** button inside the **Matching Rows** section.
+
+		1. Set the **Field Name** to the field that contains the IDs. Typically, this is the 
+        **id** column.
+		5. Set the **Relation** to **Equal To** because you want to find a row with the exact id.
+		8. Into the **Value Source**, you can select the **From Variable** and provide the id of the row you want to delete.
+
+<div class="video-container"><iframe src="https://www.loom.
+com/embed/309e0e40832146df8909c2e533e9b11e?sid=34f4ba89-cc53-47c3-8b8d-8859c03a0f6f" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
+
+<p></p>
+:::tip
+
+You can chain the [**Refresh Database Request**](../refresh-db-request.md) action after this action to remove the 
+deleted items from the list.
+
+:::
+
+### Query Rows [Action]
+
+There are certain scenarios where you may want to query a Supabase table manually. For example, you might want to only fetch data in response to a specific user action, such as clicking on a button.
+
+Additionally, if your app fetches different data under different conditions, you might find it more convenient to manually call queries. For example, you might fetch different tasks for admin and team members.
+
+To manually query a Supabase table, follow the steps below to define this action to any widget:
+
+1. Select the **Widget** (e.g., Button) on which you want to define the action.
+
+5. Select **Actions** from the Properties panel (the right menu), and click **Open**. This will open an **Action Flow Editor** in a new popup window.
+8. Click on **+ Add Action**.
+11. On the right side, search and select the **Supabase** > **Query Rows** action.
+14. Select the **Table** you want to query.
+17. You can also [Filter](#filtering-table-data) and [Order](#ordering-table-data) the query results.
+20. Provide the **Action Output Variable Name**. This will be used to store the query result.
+
+<p></p>
+
+<div class="video-container"><iframe src="https://www.loom.
+com/embed/99f47689b5b147678ed197c6ea0facf6?sid=615f2ecf-c8d0-4124-b2fa-ca9798893c92" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
+
+<p></p>
+
+
+8. Now, you can use the **Action Output Variable Name** provided in the previous step to generate 
+children from a variable on [ListView](/widgets-and-components/widgets/layout-elements/listview).
+5. Finally, you can display data in a [Text](/widgets-and-components/widgets/base-elements/text) widget. To do so, select the **Text widget > Properties Panel > Text > Set from Variable menu > ***[children\_from\_variable\_name]*** item > Get Row Field > select the row field** you want to display.
+
+<div class="video-container"><iframe src="https://www.loom.
+com/embed/d30acf8e4451459689b0d295b87bb5f9?sid=9a4f5aec-59ef-4fa3-9e76-0de72e75f278" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
+
+
+#### Filtering table data
+Sometimes you might want to filter a list based on a condition. For example, showing only 
+completed assignments. You can do so by adding the Filter while you query a Supabase table.
+
+Let's see how to filter the Supabase table to display only desired items:
+
+- In your **Action properties** of Query Rows action, scroll down and click on the **+ Add Filter** 
+  button at the bottom.
+
+- Find the **Field Name**, click on the Unset, and select a column on which you would like to apply 
+  the filter.
+- Find the **Relation** dropdown, click on the Unset, and choose the relation amongst the list.
+- Find the **Value** property and set it to an appropriate value and click Confirm.
+
+:::tip
+You could choose a Filter relation based on your requirements. For example, to show only completed assignments, set the Field Name to the column that holds completed status, e.g., is_done, set the Relation to Equal To, and set the Value to True. Here's another example. For showing only users older than 30, create a column called Age, set the Relation to Greater Than, and set the Value to 30.
+:::
+
+<div class="video-container"><iframe src="https://www.loom.
+com/embed/b5a62eac1f5d4d9698d30b064c395326?sid=4e8c4972-7fac-4c9b-b495-c9f0cb783717" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
+
+
+#### Ordering table data
+You might want to show a list from the Supabase table in a specific order. For example, showing assignments in order of the due date.
+
+To specify the order:
+
+- In your **Action properties** of Query Rows action, scroll down and click on the **+ Add Order** 
+button at the bottom.
+- Set the **Table Field Name** to the column you would like to choose for ordering.
+- Find **Order** dropdown, click on the Unset and choose the order either **Increasing** or **Decreasing** and 
+  click **Confirm**.
+
+:::tip
+You could choose the order based on your requirements. For example, to show assignments in order of due date, set Table Field Name to due_date and Order to Increasing.
+:::
+
+<div class="video-container"><iframe src="https://www.loom.
+com/embed/244eea2a4f694120b08524b7b8cf67de?sid=13d47ef5-5d48-4986-88da-d335ce23bd06" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
+
+
+
+
+
+

docs/Integrations/database/_category_.json

@@ -0,0 +1,3 @@
+{
+    "label": "Database"
+}

docs/Integrations/database/cloud-firestore/_category_.json

@@ -0,0 +1,4 @@
+{
+    "label": "Cloud Firestore",
+    "position": 1
+}

docs/Integrations/database/cloud-firestore/creating-collections.md

@@ -0,0 +1,101 @@
+---
+sidebar_position: 3
+---
+
+# Creating Collections
+
+A collection is a group of documents. For example, you could have a 'users*'* collection that contains a list of documents, each representing a single user.
+
+<figure>
+    ![img_20.png](img_20.png)
+  <figcaption class="centered-caption">User collection document model</figcaption>
+</figure>
+
+:::info[Getting Started: Things to Know First]
+
+- Get to know how to [**structure the Firebase Database**](getting-started.md#structuring-the-database).
+- Ensure you've gone through and completed every step in the [**Firebase Setup**](../../firebase/connect-to-firebase-setup.md) 
+  for your project.
+:::
+
+## Creating a collection
+
+Here are the steps to create a collection:
+
+2. Click on the **Firestore** from the Navigation Menu (left side of your screen).
+
+5. Click on the **(+)** Plus sign button.
+8. A popup will appear, Enter the collection name and click **Create** Button.
+11. Next, [define the collection schema](#define-schema-creating-fields) (create Fields) and 
+[add some data](firestore-actions.md#create-document-action) to the collection.
+
+:::info
+A collection will only appear on [**Firebase Console**](https://console.firebase.google.com/u/0/) if it contains at least one document.
+:::
+
+<div class="video-container"><iframe src="https://www.loom.
+com/embed/14d7680203494e2bbbffef58535a6499?sid=6a4620bc-0195-4c24-93b3-e5bcd9fd4c94" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
+
+
+
+### Define Schema (Creating Fields)
+
+A document represents a single item or entity, such as a user, post, animal, etc. To add data inside the document, you must define the document schema by creating Fields. Creating Fields helps you know what kind of data a document can contain.
+
+Although you can add more fields later on, it's always a good idea to add fields from the start.
+
+:::caution
+Field names cannot be changed, so ensure that you have used the correct Field names.
+:::
+
+To define the schema (create fields) for the document:
+
+1. Select your collection from the list on the left side.
+5. If you haven't added any fields yet:
+
+	1. You can choose from the template collections that have common fields needed in most 
+       applications. This will auto-add all the fields.
+	5. Click on **Start from scratch** to define your own schema.
+	8. Or, use [AI Gen Schema](#create-schema-using-ai-gen).
+8. To add a new field, start typing its name (e.g., title, description, date, etc.) and choose the suitable **Data Type**.
+11. While choosing the Data Type, you can set if it will be a list or not using **Is List?** toggle.
+
+	1. You can keep it disabled for storing only a single value. For example, fields such as title,
+    description, price, etc., can have only one value. You can't have multiple titles for a single post.
+	5. You can enable it to store multiple values of the same data type. For example, to store the list of accessory names for the field accessories.
+14. Click on the **Done** icon.
+
+:::tip
+You can also use *Tab* and *Enter* keys to navigate quickly while creating fields.
+:::
+
+<div class="video-container"><iframe src="https://www.loom.
+com/embed/7e7f80567cae477fbf97d937a76c4042?sid=84cbccd3-d084-4f9c-8dae-eff833cd2310" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
+
+
+### Create schema using AI Gen
+
+With **AI Gen Schema**, you can automatically generate a schema for your Firebase collection from a 
+simple prompt.
+
+:::tip[To get better results...]
+...you can try optimizing your prompt. i.e., make it more descriptive.
+:::
+
+Example prompts:
+
+- Generate a collection for books, their reviews, and their purchase history.
+- Create a database schema for music albums, their ratings, and sales records.
+- Generate a collection for video games, their user reviews, and purchase history.
+- Create a collection for art exhibits, visitor reviews, and ticket bookings.
+- Generate a collection for online courses, student feedback, and enrollment records.
+
+<div class="video-container"><iframe src="https://www.loom.
+com/embed/f3a3c7ad69194342926f83036f07b243?sid=e4ed8f7c-6465-42c3-a46e-0e80a4d1e202" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
+
+
+---
+
+
+:::note
+To learn more about custom data types within FlutterFlow, [check this doc](../../../resources/data-representation/data-types#built-in-data-types)