Docs cli 2.0

src/redirects.json

@@ -55,10 +55,6 @@
         "link": "/docs/command-line",
         "redirect": "/docs/tooling/command-line/installation"
     },
-    {
-        "link": "/docs/command-line-deployment",
-        "redirect": "/docs/tooling/command-line/deployment"
-    },
     {
         "link": "/docs/command-line-commands",
         "redirect": "/docs/tooling/command-line/commands"

src/routes/docs/products/auth/teams/+page.markdoc

@@ -187,6 +187,35 @@ val response = teams.createMembership(
 
 {% /multicode %}
 
+# CLI {% #CLI %}
+
+{% info title="CLI setup" %}
+Before you can deploy with the Appwrite CLI, make sure you've [installed and initialized](/docs/tooling/command-line/installation) the CLI and [logged-in](/docs/tooling/command-line/installation#get-started) into your Appwrite account.
+{% /info %}
+
+To manually deploy your Appwrite teams, you need to pull in your current Appwrite teams by using the following command:
+
+```sh
+appwrite pull teams
+```
+
+Push any configurations or changes you made to the generated code by using the following command:
+
+```sh
+appwrite push teams
+```
+{% arrow_link href="/docs/tooling/command-line/teams#commands" %}
+Learn more about the CLI team commands
+{% /arrow_link %}
+
+## Overwrite warning {% #overwrite-warning %} 
+
+If you made changes in the Appwrite Console that are different from your `appwrite.json,` using the CLI deploy command will overwrite your console changes. Update your `appwrite.json` manually before deploying.
+
+{% arrow_link href="/docs/tooling/command-line/teams#appwritejson" %}
+Learn more about appwrite.json
+{% /arrow_link %}
+
 # Permissions {% #permissions %}
 
 You can grant permissions to all members of a team using the `Role.team(<TEAM_ID>)` role or

src/routes/docs/products/databases/collections/+page.markdoc

@@ -274,3 +274,31 @@ The following indexes are currently supported:
 | `fulltext` | For searching within string attributes. Required for the [search query method](/docs/products/databases/queries#query-class).     |
 
 You can create an index by navigating to your collection's **Indexes** tab or by using your favorite [Server SDK](/docs/sdks#server).
+
+# CLI {% #cli %}
+
+{% info title="CLI setup" %}
+Before you can deploy with the Appwrite CLI, make sure you've [installed and initialized](/docs/tooling/command-line/installation) the CLI and [logged-in](/docs/tooling/command-line/installation#get-started) into your Appwrite account.
+{% /info %}
+
+```sh
+appwrite pull collections
+```
+
+Push any configurations or changes you made to the generated code by using the following command:
+
+```sh
+appwrite push collections
+```
+
+{% arrow_link href="/docs/tooling/command-line/collections#commands" %}
+Learn more about the CLI collections commands
+{% /arrow_link %}
+
+## Overwrite warning {% #overwrite-warning %} 
+
+If you made changes in the Appwrite Console that are different from your `appwrite.json,` using the CLI deploy command will overwrite your console changes. Update your `appwrite.json` manually before deploying.
+
+{% arrow_link href="/docs/tooling/command-line/collections#appwritejson" %}
+Learn more about appwrite.json
+{% /arrow_link %}

src/routes/docs/products/functions/deploy-manually/+page.markdoc

@@ -16,28 +16,37 @@ you can also create deployments manually or through the Appwrite CLI.
 Before you can deploy with the Appwrite CLI, make sure you've [installed and initialized](/docs/tooling/command-line/installation) the CLI.
 {% /info %}
 
-To deploy with the Appwrite CLI, your function must be added to `appwrite.json`. 
-Use the `appwrite init function` method to create a starter function, then paste in your function code.
+Your function must be added to `appwrite.json` to deploy with the Appwrite CLI.
+You can pull an existing function:
 
-```bash
+```sh
+appwrite pull functions
+```
+
+Or you can create a function:
+
+```sh
 appwrite init function
 ```
 
-Edit the generated code, add dependencies, and deploy the function using the following command:
+Edit the generated code, add dependencies, and push the function using the following command:
 
-```bash
-appwrite deploy function
+```sh
+appwrite push function
 ```
+{% arrow_link href="/docs/tooling/command-line/functions#commands" %}
+Learn more about the CLI functions commands
+{% /arrow_link %}
 
 ## Overwrite warning {% #overwrite-warning %} 
 
-If you made changes in the Appwrite Console that are different from your `appwrite.json`, using the CLI deploy command will overwrite your console changes. Update your `appwrite.json` manually before deploying.
+If you made changes in the Appwrite Console that are different from your `appwrite.json,` using the CLI deploy command will overwrite your console changes. Update your `appwrite.json` manually before deploying.
 
 ## Configure CLI deployments {% #configure-cli-deployments %}
 If you need to target a different project, API endpoint, change the path or entry point of your function, or update any of the other configuration options, 
 you can do so by editing the `appwrite.json` file.
 
-{% arrow_link href="/docs/tooling/command-line/deployment#function-options" %}
+{% arrow_link href="/docs/tooling/command-line/functions#appwritejson" %}
 Learn more about appwrite.json
 {% /arrow_link %}
 

src/routes/docs/products/functions/deployments/+page.markdoc

@@ -45,4 +45,4 @@ After updating the configuration, redeploy your function for changes to take eff
 3. Under the **Deployments** tab, find the status of the current active deployment.
 4. Redeploy by clicking the triple-dots beside an execution, and hitting the **Redeploy** button.
 
-Redeployment behavior varies depending on how the initial deployment was created.
+Redeployment behavior varies depending on how the initial deployment was created.

src/routes/docs/products/functions/functions/+page.markdoc

@@ -66,21 +66,28 @@ Remember to specify the build commands for your function to install dependencies
 {% /tabsitem %}
 
 {% tabsitem #cli title="CLI" %}
-You can create functions using the CLI, without needing to access the Console.
+You can create functions using the CLI without needing to access the Console.
 Before you can deploy with the Appwrite CLI, make sure you've [initialized the CLI.](/docs/tooling/command-line/installation)
 
-To deploy with the Appwrite CLI, your function must be added to your `appwrite.json` config file. 
-Use the `appwrite init function` method to create a starter function, then paste in your function code.
+Your function must be added to `appwrite.json` to deploy with the Appwrite CLI. 
 
-```bash
+You can pull an existing function:
+
+```sh
+appwrite pull functions
+```
+
+Or you can create a function:
+
+```sh
 appwrite init function
 ```
 
 The init command will initialize a folder with a starter function code.
-To deploy the generated code, add dependencies, and deploy the function using the following command:
+To push the generated code, add dependencies, and deploy the function using the following command:
 
-```bash
-appwrite deploy function
+```sh
+appwrite push function
 ```
 {% /tabsitem %}
 {% /tabs %}

src/routes/docs/products/messaging/topics/+page.markdoc

@@ -266,6 +266,36 @@ let topic = try await messaging.createTopic(
 {% /tabsitem %}
 {% /tabs %}
 
+# CLI {% #CLI %}
+
+{% info title="CLI setup" %}
+Before you can deploy with the Appwrite CLI, make sure you've [installed and initialized](/docs/tooling/command-line/installation) the CLI and [logged-in](/docs/tooling/command-line/installation#get-started) into your Appwrite account.
+{% /info %}
+
+To manually deploy your Appwrite topics, you need to pull in your current Appwrite topics by using the following command:
+
+```sh
+appwrite pull topics
+```
+
+Push any configurations or changes you made to the generated code by using the following command:
+
+```sh
+appwrite push topics
+```
+{% arrow_link href="/docs/tooling/command-line/topics#commands" %}
+Learn more about the CLI topic commands
+{% /arrow_link %}
+
+## Overwrite warning {% #overwrite-warning %} 
+
+If you made changes in the Appwrite Console that are different from your `appwrite.json,` using the CLI deploy command will overwrite your console changes. Update your `appwrite.json` manually before deploying.
+
+{% arrow_link href="/docs/tooling/command-line/topics#appwritejson" %}
+Learn more about appwrite.json
+{% /arrow_link %}
+
+
 # Permissions {% #permissions %}
 Before you can subscribe to a topic, a user needs the appropriate permission.
 You can set permission by navigating to **Messaging** > **Topics** > select a topic to configure > **Subscription access**.

src/routes/docs/products/storage/buckets/+page.markdoc

@@ -8,7 +8,37 @@ Storage buckets are a group of files, similar to collections in Appwrite Databas
 Buckets let you limit file size and extensions, whether or not to encrypt the files, and more.
 
 # Create Bucket {% #create-bucket %}
-You can create your bucket from the Appwrite Console or a [Server SDK](/docs/sdks#server).
+You can create your bucket from the Appwrite Console or a [Server SDK](/docs/sdks#server). You can also create buckets using the [CLI](/docs/tooling/command-line/installation), requiring only a single [command](/docs/tooling/command-line/buckets) to create buckets and handle server-side tasks with buckets and storage.
+
+# CLI {% #cli %}
+
+{% info title="CLI setup" %}
+Before you can deploy with the Appwrite CLI, make sure you've [installed and initialized](/docs/tooling/command-line/installation) the CLI and [logged-in](/docs/tooling/command-line/installation#get-started) into your Appwrite account.
+{% /info %}
+
+To manually deploy your Appwrite buckets, you need to pull in your current Appwrite buckets by using the following command:
+
+```sh
+appwrite pull buckets
+```
+
+Push any configurations or changes you made to the generated code by using the following command:
+
+```sh
+appwrite push buckets
+```
+{% arrow_link href="/docs/tooling/command-line/buckets#commands" %}
+Learn more about the CLI buckets commands
+{% /arrow_link %}
+
+## Overwrite warning {% #overwrite-warning %} 
+
+If you made changes in the Appwrite Console that are different from your `appwrite.json,` using the CLI deploy command will overwrite your console changes. Update your `appwrite.json` manually before deploying.
+
+{% arrow_link href="/docs/tooling/command-line/buckets#appwritejson" %}
+Learn more about appwrite.json
+{% /arrow_link %}
+
 
 {% tabs %}
 {% tabsitem #console title="Console" %}

src/routes/docs/tooling/command-line/+layout.svelte

@@ -19,15 +19,36 @@
 					label: 'Commands',
 					href: '/docs/tooling/command-line/commands'
 				},
-				{
-					label: 'Deployment',
-					href: '/docs/tooling/command-line/deployment'
-				},
 				{
 					label: 'Non interactive',
 					href: '/docs/tooling/command-line/non-interactive'
 				}
 			]
+		},
+		{
+			label: 'Deployments',
+			items: [
+				{
+					label: 'Collections',
+					href: '/docs/tooling/command-line/collections'
+				},
+				{
+					label: 'Functions',
+					href: '/docs/tooling/command-line/functions'
+				},
+				{
+					label: 'Teams',
+					href: '/docs/tooling/command-line/teams'
+				},
+				{
+					label: 'Topics',
+					href: '/docs/tooling/command-line/topics'
+				},
+				{
+					label: 'Buckets',
+					href: '/docs/tooling/command-line/buckets'
+				}
+			]
 		}
 	];
 </script>