@nocobase/plugin-ai 2.2.0-beta.1 → 2.2.0-beta.2

package/dist/ai/docs/nocobase/index.md

@@ -11,21 +11,21 @@ hero:
   actions:
     - theme: brand
       text: Get Started
-      link: /get-started/how-nocobase-works
+      link: /ai/how-nocobase-works
     - theme: alt
       text: GitHub
       link: https://github.com/nocobase/nocobase
 
 features:
   - title: Start
-    details: Get started with NocoBase the traditional way - install, configure, and explore step by step.
+    details: Get started with NocoBase quickly - install, configure, and explore step by step.
     items:
-      - title: NocoBase Getting Started
+      - title: How NocoBase Works
         details: Understand NocoBase's core concepts and basic operations.
-        link: /get-started/how-nocobase-works
-      - title: Install App
-        details: Quickly install and manage applications.
-        link: /get-started/installation/docker
+        link: /ai/how-nocobase-works
+      - title: Install NocoBase App
+        details: Use NocoBase CLI to install an application quickly.
+        link: /ai/install-nocobase-app
       - title: Tutorials
         details: Step-by-step tutorials to build real projects with NocoBase from scratch.
         link: /tutorials/v2/
@@ -33,9 +33,6 @@ features:
   - title: AI
     details: An AI-powered new way to get started - use natural language to build, use, and develop.
     items:
-      - title: Quick Start
-        details: Install NocoBase CLI, configure AI Skills, and connect your AI Agent, preparing for AI building, using, and developing NocoBase.
-        link: /ai/quick-start
       - title: AI Builder
         details: Build NocoBase applications from scratch with AI, covering the full process from data modeling, UI configuration, workflows to release management.
         link: /ai-builder

package/dist/ai/docs/nocobase/interface-builder/blocks/data-blocks/gantt.md

@@ -0,0 +1,204 @@
+---
+pkg: '@nocobase/plugin-gantt'
+title: 'Gantt Block'
+description: 'The Gantt block displays record start and end dates and progress on a timeline. It is suitable for project planning, task scheduling, and milestone tracking, and supports title fields, date fields, progress fields, color fields, time scale, the left table, and event popup settings.'
+keywords: 'Gantt block,Gantt,project planning,task scheduling,timeline,progress management,UI building,NocoBase'
+---
+
+# Gantt Block
+
+## Introduction
+
+The Gantt block displays record start and end dates and progress on a timeline. It is suitable for project planning, task scheduling, milestone tracking, and other scenarios where you need to view task duration by time.
+
+![](https://static-docs.nocobase.com/Project-tasks-06-11-2026_11_30_AM.png)
+
+## Installation
+
+This block is a built-in plugin and does not require additional installation.
+
+## Add Block
+
+After selecting the Gantt block and choosing a data table, configure the fields required by the Gantt block in the popup:
+
+1. Select the title field, which is used to display the task name
+2. Select the start date field, which is used to determine the task start time
+3. Select the end date field, which is used to determine the task end time
+4. Optionally select the progress field, which is used to display and drag to update task progress
+5. Optionally select the color field, which is used to distinguish different tasks
+6. Select the time scale, which controls the granularity of the timeline
+
+After completing the configuration, you can create the Gantt block.
+
+![](<https://static-docs.nocobase.com/Project-tasks-06-11-2026_11_27_AM%20(1).png>)
+
+![](https://static-docs.nocobase.com/Project-tasks-06-11-2026_11_27_AM.png)
+
+## Block Settings
+
+![](https://static-docs.nocobase.com/Project-tasks-06-11-2026_11_28_AM.png)
+
+### Gantt Fields
+
+Gantt fields determine how records are mapped to timeline tasks.
+
+They include:
+
+- The title field determines the name displayed on the task bar
+- The start date field determines where the task bar starts
+- The end date field determines where the task bar ends
+- The progress field determines the progress displayed inside the task bar
+- The color field determines the task bar color
+- The time scale determines whether the timeline is displayed by hour, day, week, month, and so on
+
+### Title Field
+
+Used to display the task name. Usually, you can select a string field such as task name, project name, or title.
+
+### Start Date Field
+
+Used to specify the task start time. The Gantt block uses this field to place the task on the timeline.
+
+### End Date Field
+
+Used to specify the task end time. When the start date and end date are the same, the task is displayed as a shorter time range.
+
+### Progress Field
+
+Used to display task completion progress, and supports updating it by dragging the progress handle on the task bar.
+
+The progress field uses a float field. Data is stored from `0` to `1`, and displayed as a percentage in the Gantt block. For example, `0.6` is displayed as `60%`.
+
+### Color Field
+
+Used to set the task bar color, making it easier to distinguish different task types, statuses, or priorities.
+
+The color field supports:
+
+- Single select field
+- Color field
+
+If a single select field is used, the Gantt block will prioritize the color configured for the selected option.
+
+### Time Scale
+
+Used to control the timeline display granularity.
+
+Currently supported:
+
+- Hour
+- Quarter of day
+- Half of day
+- Day
+- Week
+- Month
+- Year
+- Quarter
+
+For short task spans, use hour, half-day, or day. For longer task spans, use week, month, quarter, or year.
+
+### Show Table
+
+When enabled, the Gantt block displays a table area on the left. You can configure table columns to show key task attributes.
+
+When disabled, the block only displays the timeline on the right. This is suitable when page space is limited or you only need to view scheduling.
+
+### Table Width
+
+Used to set the width of the left table area. This setting only appears when Show table is enabled.
+
+If there are many table fields, increase the table width. If only a few fields are kept, reduce the width and leave more space for the timeline.
+
+### Enable Drag to Reschedule
+
+When enabled, you can drag task bars on the timeline to adjust start and end dates.
+
+Details:
+
+- Drag the whole task bar to adjust both the start date and end date
+- Drag the handles on both sides of the task bar to adjust the start date or end date
+- Drag the progress handle to update the progress field
+
+If you do not want users to modify schedules directly in the Gantt block, disable this option.
+
+### Scroll to Today on First Display
+
+When enabled, the Gantt block automatically scrolls to today when it is first displayed.
+
+This option is suitable for projects with long task spans. When the page opens, users can first see tasks near the current date.
+
+### Event Popup Settings
+
+Used to configure how a task bar opens after being clicked.
+
+You can configure:
+
+- Open mode, such as drawer, dialog, or page
+- Popup size
+- Popup template
+
+After clicking a task bar, NocoBase opens the current record according to this configuration, making it convenient to view or edit task details.
+
+### Data Scope
+
+Used to limit the data displayed in the Gantt block.
+
+For example: only show tasks under the current project, or only show unfinished tasks.
+
+For more details, refer to [Data Scope](../block-settings/data-scope).
+
+### Page Size
+
+Used to control the number of records loaded per page. When there are many records, users can switch pages to view more tasks.
+
+### Show Row Numbers
+
+When enabled, the left table displays row numbers, making it easier to locate records when there are many tasks.
+
+### Tree Table
+
+If the current data table is a tree table, the Gantt block can enable tree table mode. After enabling it, the left table displays records by parent-child hierarchy, and the timeline on the right displays tasks in the same hierarchy.
+
+In tree table mode, you can also configure Expand all rows by default.
+
+## Configure Fields
+
+The left table area uses table columns to display record fields.
+
+![](https://static-docs.nocobase.com/Project-tasks-06-11-2026_11_29_AM.png)
+
+### Add Fields
+
+After Show table is enabled, you can add field columns to the left table. Field settings can refer to [Table Column](../../fields/generic/table-column).
+
+### Actions Column
+
+The Gantt block includes an actions column by default. You can add record actions such as view, edit, and delete to the actions column.
+
+If Event popup settings have already been configured, you can also click the task bar on the right to open record details.
+
+## Configure Actions
+
+The Gantt block supports configuring global actions at the top. Available action types depend on the enabled capabilities in the current environment.
+
+![](<https://static-docs.nocobase.com/Project-tasks-06-11-2026_11_29_AM%20(1).png>)
+
+### Built-in Actions
+
+- Today: quickly scroll to today
+- Expand/Collapse: expand or collapse all rows in tree table mode
+
+### Global Actions
+
+- [Add New](../../actions/types/add-new)
+- [Popup](../../actions/types/pop-up)
+- [Link](../../actions/types/link)
+- [Refresh](../../actions/types/refresh)
+- [Filter](../../actions/types/filter)
+- [Bulk Edit](../../actions/types/bulk-edit)
+- [Bulk Update](../../actions/types/bulk-update)
+- [Trigger Workflow](../../actions/types/trigger-workflow)
+- [Custom Request](../../actions/types/custom-request)
+- [JS Item](../../actions/types/js-item)
+- [JS Action](../../actions/types/js-action)
+- [AI Employee](../../actions/types/ai-employee)

package/dist/ai/docs/nocobase/interface-builder/fields/field-settings/scan-input.md

@@ -0,0 +1,43 @@
+---
+title: "Scan Code Input"
+description: "Field settings: enable scan code input for text form fields, supporting writing field values through QR codes or barcodes."
+keywords: "scan code input,QR code,barcode,field settings,interface builder,NocoBase"
+---
+
+# Scan Code Input
+
+## Introduction
+
+Scan code input is used for text fields in editable forms. After it is enabled, a scan button appears on the right side of the field input. Users can scan a QR code or barcode, or select an image from the album for recognition, and write the recognized result into the current field.
+
+It is typically suitable for entering values such as device numbers, asset codes, order numbers, and tracking numbers that are inconvenient to type manually.
+
+## Supported Fields
+
+Scan code input is mainly used for text-based fields, such as:
+
+- Single line text
+- Mobile phone
+- Email
+- URL
+- UUID
+- Nano ID
+
+If the field is read-only, in reading mode, or does not support editable input itself, the scan code input configuration will not be shown.
+
+## Configuration
+
+Select the corresponding field in a form block, open the field configuration menu, and find `Scan Code Input Settings`.
+
+Options include:
+
+- `Enable scan code input`: after enabling, a scan button is shown on the right side of the input box
+- `Disable manual input`: after enabling, users can only write the field value by scanning and cannot edit the input box manually
+
+After `Enable scan code input` is turned off, `Disable manual input` also becomes inactive.
+
+## Usage
+
+After the user clicks the scan button on the right side of the field, they can use the camera to recognize a QR code or barcode. Browser-based scanning requires permission to access the camera. In mobile environments that support native scan capabilities, the native mobile scan capability is used first.
+
+If it is not convenient to use the camera directly, users can also click `Album` to select an image for recognition.

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/index.md

@@ -1,4 +1,4 @@
-# Quick start
+# NocoBase CLI Overview
 
 If this is your first time using this CLI, you don’t need to memorize all the commands at the beginning. Use `nb init --ui` to install an application first, and then continue looking at the rest according to the scenario.
 
@@ -20,7 +20,7 @@ Keep this in mind first, and the subsequent documents will be much smoother.
 
 If you're not sure where to start, it's usually easiest to follow this path:
 
-1. First read [Installation using CLI (recommended)](./installation/cli.md) and complete `nb init` once.
+1. First read [Install using CLI](./installation/cli.md) and complete `nb init` once.
 2. After the application is saved as env, look at [Multiple Environment Management](./operations/multi-environment.md) to confirm the current env, switch env, and check the status.
 3. For daily startup, stop, log and upgrade, continue to see [Manage Application](./operations/manage-app.md).
 4. Before making upgrades, migrations or important changes, see [Backup and Restore](./operations/backup-restore.md).
@@ -32,8 +32,8 @@ The first three steps cover most usage scenarios.
 
 | I want... | Where to look |
 | --- | --- |
-| There is no application yet, first install a new NocoBase and save it as CLI env | [Install using CLI (recommended)](./installation/cli.md) |
-| Already have a running NocoBase and want to access CLI management | [Install using CLI (recommended)](./installation/cli.md) |
+| There is no application yet and you want to install a new NocoBase and save it as a CLI env | [Install using CLI](./installation/cli.md) |
+| You already have a running NocoBase and want to bring it under CLI management | [Install using CLI](./installation/cli.md) |
 | Gradually migrate old installation methods to CLI | [Migrate from old installation methods to CLI](./installation/migration.md) |
 | See which envs are saved locally, switch the current env, and check the status | [Multiple environment management](./operations/multi-environment.md) |
 | Start, stop, restart the application, view logs, or continue the upgrade | [Manage Application](./operations/manage-app.md) |
@@ -44,11 +44,11 @@ The first three steps cover most usage scenarios.
 
 ## When to look at the command reference
 
-This set of quick start documents is more "what do I want to do now". If you already know which command you want to execute and just want to continue to see the complete parameters, just go to [NocoBase CLI Command Reference](../api/cli/index.md).
+This set of quick start documents is more about "what do I want to do now". If you already know which command you want to run and only want the full parameters, go straight to [NocoBase CLI Command Reference](../api/cli/index.md).
 
 The default suggestions are:
 
-- First use the Quick Start document to establish a sense of path
+- First use this overview and the quick start documents to establish a sense of path
 - Then check the parameter details on the specific command page
 
 This makes it easier to get started than reading the complete command tree at first glance.

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/installation/cli.md

@@ -1,4 +1,4 @@
-# Install using CLI (recommended)
+# Install using CLI
 
 After NocoBase 2.1.0, the official CLI-based installation and management method is provided. You can use it to complete installation, connection, upgrade and daily maintenance, and you can also prepare a connectable and operable environment for AI Agent.
 
@@ -9,7 +9,7 @@ Only executed when installing the CLI for the first time.
 First install the CLI globally:
 
 ```bash
-npm install -g @nocobase/cli@beta
+npm install -g @nocobase/cli
 nb --version
 ```
 
@@ -23,12 +23,6 @@ nb session setup
 
 :::
 
-If you plan to use the Chinese interface for a long time, it is usually enough to set the locale first:
-
-```bash
-nb config set locale zh-CN
-```
-
 The CLI checks for self-updates by default. You can adjust the update strategy according to your own habits:
 
 - `prompt`: Prompt when a new version is found

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/installation/env.md

@@ -2,7 +2,7 @@
 
 This page only applies to applications created or hosted via the NocoBase CLI.
 
-If you have just finished reading [Installation using CLI (recommended)](./cli.md) and have seen the "Installation Directory" section, then the most common problems you will encounter are usually the following:
+If you have just finished reading [Install using CLI](./cli.md) and have seen the "Installation Directory" section, then the most common problems you will encounter are usually the following:
 
 - Where is the `.env` file placed?
 - Which configurations are still suitable to be written into `.env`
@@ -17,7 +17,7 @@ Let’s talk about the conclusion first:
 
 ## Find `app-path` first
 
-In [Install using CLI (recommended)](./cli.md#Installation directory), the default directory structure of CLI env is as follows:
+In [Install using CLI](./cli.md#Installation directory), the default directory structure of CLI env is as follows:
 
 ```text
 <app-path>/
@@ -148,6 +148,6 @@ This is also the mentality that this page most wants to help you build:
 
 ## Where to look next
 
-- If you have not confirmed the application directory structure, first go back to [Install using CLI (recommended)](./cli.md#Installation directory)
+- If you have not confirmed the application directory structure, first go back to [Install using CLI](./cli.md#Installation directory)
 - If you want to modify basic configurations such as ports, time zones, database connections, and public access paths, continue to see [`nb env update`](../../api/cli/env/update.md)
 - If you want to start, restart or view application logs, continue to see [Manage Application](../operations/manage-app.md)

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/installation/migration.md

@@ -99,5 +99,5 @@ By default, it is enough to migrate the test environment first. Only migrate the
 
 ## Where to look next
 
-- If you are ready to install and manage applications in a new way, continue to [Installation using CLI (recommended)](./cli.md)
+- If you are ready to install and manage applications in a new way, continue to [Install using CLI](./cli.md)
 - If you just continue to use the original installation method, just go back to the installation and upgrade document entry above.

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/production/index.md

@@ -69,7 +69,7 @@ If you happen to be stuck here "Why do you need `nb app autostart`", just contin
 - If you are going to connect to the reverse proxy, `appPort` has been saved in env
 - If you are ready to officially open it to the outside world, you have already planned the domain name, entrance port and HTTPS solution.
 
-If you have not completed the CLI installation or env initialization, go back to [Installation using CLI (recommended)](../installation/cli.md).
+If you have not completed the CLI installation or env initialization, go back to [Install using CLI](../installation/cli.md).
 
 If the command prompts that env is missing `appPort`, first execute [`nb env update`](../../api/cli/env/update.md) to fill it in.
 

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/production/reverse-proxy/caddy.md

@@ -290,6 +290,6 @@ nb proxy caddy status
 
 - [Production environment reverse proxy](./index.md)
 - [Nginx](./nginx.md)
-- [Install using CLI (recommended)](../../installation/cli.md)
+- [Install using CLI](../../installation/cli.md)
 - [Application configuration with `.env`](../../installation/env.md)
 - [`nb proxy caddy` Command Reference](../../../api/cli/proxy/caddy/index.md)

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/production/reverse-proxy/index.md

@@ -45,4 +45,4 @@ It can usually be judged like this:
 | Follow the Nginx management site entrance | [Nginx](./nginx.md) |
 | Connect HTTPS as soon as possible | [Caddy](./caddy.md) |
 | First adjust the env configuration that will affect the proxy results, such as `app-port`, `app-public-path` | [`nb env update`](../../../api/cli/env/update.md) |
-| First confirm the installation and env configuration of the application | [Install using CLI (recommended)](../../installation/cli.md) |
+| First confirm the installation and env configuration of the application | [Install using CLI](../../installation/cli.md) |

package/dist/ai/docs/nocobase/{quickstart → nocobase-cli}/production/reverse-proxy/nginx.md

@@ -246,6 +246,6 @@ However, if you just want to get available HTTPS as soon as possible, and don't
 
 - [Production environment reverse proxy](./index.md)
 - [Caddy](./caddy.md)
-- [Install using CLI (recommended)](../../installation/cli.md)
+- [Install using CLI](../../installation/cli.md)
 - [Application configuration with `.env`](../../installation/env.md)
 - [`nb proxy nginx` Command Reference](../../../api/cli/proxy/nginx/index.md)

package/dist/ai/docs/nocobase/ops-management/version-control/index.md

@@ -1,12 +1,12 @@
 ---
 title: "Version control"
-description: "Version control plugin guide: create versions, restore versions, configure retention, set shortcuts, and include user collections in saved versions."
-keywords: "Version control,ops management,create version,restore version,NocoBase"
+description: "Version control plugin guide: automatically save versions during AI Builder sessions, create and restore versions manually, configure retention, set shortcuts, and include user collections in saved versions."
+keywords: "Version control,ops management,AI Builder,nocobase-revision,nb revision create,create version,restore version,NocoBase"
 ---
 
 # Version control
 
-In NocoBase, **Version control** lets you save a restorable version of the current application. You can create versions manually, restore the application to a saved version when needed, and use the plugin settings to control how many versions to keep, which shortcut to use, and which user collections should be saved with the version.
+In NocoBase, **Version control** lets you save a restorable version of the current application. You can create versions manually, restore the application to a saved version when needed, and let AI Builder automatically save versions after meaningful milestones.
 
 Version control depends on [Backup manager](../backup-manager/index.mdx) to save and restore application states. Before using Version control, enable Backup manager first.
 
@@ -16,17 +16,31 @@ Community and Standard editions do not include the Version control plugin. If yo
 
 :::
 
+## AI auto-saved versions
+
+After the Version control plugin is enabled, AI Builder gets an extra rollback safeguard. When an AI Agent starts working on a request, it checks the NocoBase Skills available to the current application. If it finds the `nocobase-revision` skill, it can save key building milestones as restorable versions.
+
+![AI detects the nocobase-revision skill when building starts](https://static-docs.nocobase.com/20260611115845.png)
+
+When AI completes a piece of work that can be reviewed on its own, such as building a page, creating a set of collections, or configuring a workflow, it runs `nb revision create` through the NocoBase CLI. You do not need to click 「Create version」 manually each time, and small adjustments will not create noisy version records.
+
+![AI creates a version after building](https://static-docs.nocobase.com/20260611115804.png)
+
+These versions appear in the versions list. If later changes do not match your expectations, you can restore to the previous clear building milestone and continue adjusting from there.
+
 ## Open the plugin
 
-You can open the plugin from 「System settings」 → 「Version control」. A Version control button also appears in the top bar. Click it to create a version directly or jump to the versions list. The default shortcut for creating a version is `Ctrl + K`, and you can change it in the settings tab.
+After the plugin is enabled, a 「Version control」 menu appears in the top bar. You can create a version directly from there or open the versions list.
+
+You can also open the plugin from 「System settings / Version control」. The default shortcut for creating a version is `Ctrl + K`, and you can change it in the settings tab.
 
-![](https://static-docs.nocobase.com/20260526220402.png)
+![Version control menu](https://static-docs.nocobase.com/20260611112317.png)
 
 ## Create a version
 
 Click 「Create version」, enter a description, and save it. The description can be up to 2000 characters. It is useful for recording the background of the change, such as “Adjusted approval fields and permissions”.
 
-![](https://static-docs.nocobase.com/20260526220510.png)
+![Create version](https://static-docs.nocobase.com/20260611112739.png)
 
 After you click save, the list first shows a temporary “Saving” entry. When the task finishes, the saved version appears in the list.
 
@@ -77,3 +91,4 @@ If you include a user collection, NocoBase also includes related collections aut
 - [Backup manager](../backup-manager/index.mdx) — the underlying capability required by Version control
 - [Migration manager](../migration-manager/index.md) — move application configuration across environments
 - [Release management](../release-management/index.md) — plan release workflows with backups, migrations, and variables
+- [AI Builder quick start](../../ai-builder/index.md) — use natural language to complete data modeling, page configuration, and workflow orchestration

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-acl/index.md

@@ -1,15 +1,17 @@
 ---
-displayName: "Access Control"
+title: "Access control"
+keywords: "Users & permissions"
+displayName: "Access control"
 packageName: '@nocobase/plugin-acl'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Based on roles, resources, and actions, Access Control can precisely manage Interface Configuration permissions, data operation permissions, menu access permissions, and plugin permissions.
+  Based on roles, resources, and actions, access control can precisely manage interface configuration permissions, data operation permissions, menu access permissions, and plugin permissions.
 isFree: true
 builtIn: true
 defaultEnabled: true
 editionLevel: 0
 ---
 
-# Access Control
+# Access control

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-bulk-edit/index.md

@@ -1,15 +1,17 @@
 ---
-displayName: "Action: Bulk edit"
+title: "Action: Batch edit"
+keywords: "Actions"
+displayName: "Action: Batch edit"
 packageName: '@nocobase/plugin-action-bulk-edit'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Bulk edit all or selected data.
+  Batch edit all records or selected records.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Bulk edit
+# Action: Batch edit

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-bulk-update/index.md

@@ -1,15 +1,17 @@
 ---
-displayName: "Action: Bulk update"
+title: "Action: Batch update"
+keywords: "Actions"
+displayName: "Action: Batch update"
 packageName: '@nocobase/plugin-action-bulk-update'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Bulk update all or selected records.
+  Batch update all records or selected records.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Bulk update
+# Action: Batch update

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-custom-request/index.md

@@ -1,14 +1,17 @@
 ---
+title: "Action: Custom request"
+keywords: "Actions"
 displayName: "Action: Custom request"
 packageName: '@nocobase/plugin-action-custom-request'
 supportedVersions:
   - 1.x
+  - 2.x
 description: |
-  Sends requests to any HTTP service and supports sending context data to the target service.
+  Sending a request to any HTTP service supports sending context data to the target service.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Custom request
+# Action: Custom request

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-duplicate/index.md

@@ -1,15 +1,17 @@
 ---
+title: "Action: Duplicate record"
+keywords: "Actions"
 displayName: "Action: Duplicate record"
 packageName: '@nocobase/plugin-action-duplicate'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Duplicate a record. You can either duplicate it into a form and edit it before submitting, or you can duplicate it directly to generate a new record.
+  Duplicate a record, you can either duplicate it into a form and edit it before saving it, or you can duplicate it directly to generate a new record.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Duplicate record
+# Action: Duplicate record

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-export/index.md

@@ -1,15 +1,17 @@
 ---
+title: "Action: Export records"
+keywords: "Actions"
 displayName: "Action: Export records"
 packageName: '@nocobase/plugin-action-export'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Export filtered records to Excel, you can configure which fields to export.
+  Export filtered records to excel, you can configure which fields to export.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Export records
+# Action: Export records

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-export-pro/index.md

@@ -1,4 +1,6 @@
 ---
+title: "Action: Export records Pro"
+keywords: "Actions"
 displayName: "Action: Export records Pro"
 packageName: '@nocobase/plugin-action-export-pro'
 supportedVersions:
@@ -12,4 +14,4 @@ defaultEnabled: false
 editionLevel: 1
 ---
 
-# Action: Export records Pro
+# Action: Export records Pro

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-import/index.md

@@ -1,15 +1,17 @@
 ---
+title: "Action: Import records"
+keywords: "Actions"
 displayName: "Action: Import records"
 packageName: '@nocobase/plugin-action-import'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Import records using Excel templates. You can configure which fields to import and templates will be generated automatically.
+  Import records using excel templates. You can configure which fields to import and templates will be generated automatically.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Import records
+# Action: Import records