Conversation
|
|
|
but why is this topic in exporting code folder? |
Earlier, the FF CLI was only used for exporting code, so it lived under the Export section. Now that it supports much more, it probably needs another location. Where do you think it would fit best? |
PoojaB26
left a comment
PoojaB26
left a comment
There was a problem hiding this comment.
I'll make some changes to the branch directly and then you can make any pending changes on top of it later.
| @@ -0,0 +1,239 @@ | |||
| --- | |||
| slug: /exporting/ff-cli | |||
| --- | ||
| slug: /exporting/ff-cli | ||
| title: FlutterFlow CLI | ||
| description: Learn how to download and manage your FlutterFlow projects locally using the FlutterFlow CLI. |
There was a problem hiding this comment.
description, keywords, tags also update
| ### Get API Token | ||
| To use the CLI, you'll need to create an API token and use it in your requests. See the documentation [here on how to generate an API token.](../../accounts-billing/account-management.md#how-do-i-generate-an-api-token) | ||
|
|
||
| ## Build Projects |
There was a problem hiding this comment.
| ## Build Projects | |
| ## Build Projects with AI |
|
|
||
| :::info[Remember] | ||
|
|
||
| - **FF CLI is not a replacement for the visual builder.** FlutterFlow is still faster for most visual work. FF CLI is for precision, repeatability, and automation. |
There was a problem hiding this comment.
dont call it "FF" cli, that's not an external name and can be confusing
| To use the CLI, you'll need to create an API token and use it in your requests. See the documentation [here on how to generate an API token.](../../accounts-billing/account-management.md#how-do-i-generate-an-api-token) | ||
|
|
||
| ## Build Projects | ||
| The FlutterFlow CLI lets you build and edit FlutterFlow apps in the terminal instead of in the visual builder. You can use it to create brand-new apps or for changes to ones you already have. It's designed for AI agents, so you can hand work off and review their changes like any other code. |
There was a problem hiding this comment.
this intro doesn't do justice to the capabilities this feature is providing, I'd say. need to update it.
| ## Build Projects | ||
| The FlutterFlow CLI lets you build and edit FlutterFlow apps in the terminal instead of in the visual builder. You can use it to create brand-new apps or for changes to ones you already have. It's designed for AI agents, so you can hand work off and review their changes like any other code. | ||
|
|
||
| :::info[Remember] |
There was a problem hiding this comment.
this info section seems a bit out of place, before we even introduce the topic, it looks like we're giving warnings what it is not.
ok, just let me know when you are done and what is left to do. |
…Exporting Projects' and enhance 'Build with AI Agents' section with more info about the mcp tool
|
@PoojaB26 broken links are fixed, and review comments are addressed! Only visuals are left! |
|
@ayushflow if you also want to review! |
…clarify project switching process.
| > mindfly | ||
| ``` | ||
| 2. **Environment.** Use ↑ / ↓ to highlight the FlutterFlow environment you want this workspace to target, then press **Enter**. | ||
| 3. **Link to an existing FlutterFlow project?** Press **Enter** (default `N`) to create a new app. Answer `y` to bind the workspace to an existing project — the wizard will then ask for the project ID. |
There was a problem hiding this comment.
@PoojaB26 For 'step 3. Link to an existing FlutterFlow project' I didn’t encounter this step. It directly prompts for the project ID, where pressing Enter creates a new project. There’s no separate Y/N step before entering the project ID.
There was a problem hiding this comment.
yep my bad. thanks for catching it.
2 participants
Description
Add Flash Docs.
Linear ticket and magic word Fixes DEVR-1255
Type of change