@nocobase/plugin-ai 2.2.0-beta.9 → 3.0.0-alpha.1

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/basic/password.md

@@ -1,13 +1,111 @@
+---
+title: "Password"
+description: "The Password field stores password or secret values and uses a masked input component."
+keywords: "Password,password,field,Field interface,NocoBase"
+---
+
 # Password
 
 ## Introduction
 
-## Field configuration
+In NocoBase, the **Password** field stores password or secret values.
+
+It is suitable for access passwords, connection secrets, and temporary passwords. Use it only when the value is required by business configuration; do not use it as a substitute for user authentication and authorization.
+
+## Use cases
+
+Password fields are suitable for these business scenarios:
+
+- Access passwords and temporary passwords
+- Connection secrets
+- Configuration values requiring masked input
+- Service account credential settings
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Password** to create this field.
+
+![Configure a Password field](https://static-docs.nocobase.com/20240512175917.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Password uses `password`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Access password`, `Connection secret`, or `Temporary password`. Use a name that business users can recognize. |
+| Field name | The field identifier used internally by APIs, relation fields, permissions, and workflows. It usually cannot be changed after creation. It supports only letters, numbers, and underscores, and must begin with a letter. |
+| Field type | The data-layer type. Password uses `password` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. Supports length, regular-expression, and required validation. |
+| Description | A field description. Record the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Field names are referenced by page blocks, permissions, workflows, and APIs after creation. Confirm the name before creating the field to avoid later configuration changes.
+
+:::
+
+## Field behavior
+
+The default behavior of a Password field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `password`. |
+| Default Field type | `password`. |
+| Available Field types | `password`, `string`. |
+| Page component | Uses a masked password input in edit mode. |
+| Filtering | It is usually not used as a primary filter field. |
+| Sorting | It is usually not used for sorting. |
+| Validation | Supports length, regular-expression, and required validation. |
+
+## Edit configuration
+
+After creation, click **Edit** beside the field to edit its configuration. Edit fields to adjust how they are displayed and used in NocoBase, such as the display name, description, default value, validation rules, or field-specific settings.
+
+When a field comes from a synchronized main-database table, editing usually maps the database field to a NocoBase Field type and Field interface.
+
+| Setting | Can be edited | Description |
+| --- | --- | --- |
+| Field display name | Yes | Changes the name displayed in the interface without changing the field identifier. |
+| Field name | No | The field identifier normally cannot be changed in the edit form after creation. |
+| Field interface | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Changes affect page input, display, and validation. |
+| Field type | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Confirm that existing values can be used by the new type first. |
+| Default value | Yes | Adjusts the default value for new records. |
+| Validation rules | Yes | Adjusts field validation rules. |
+| Description | Yes | Adds the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Changing a Field type or Field interface is more than changing a display name. It affects field storage, input components, validation rules, filters, and workflow-variable usage. When the field contains substantial existing data, confirm that its data format is compatible first.
+
+:::
+
+## Delete field
+
+Click **Delete** beside a Password field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Password field created in the main database usually also deletes the actual database column and its values. For a synchronized or external-data-source field, the impact depends on the corresponding data source and field origin.
+
+:::danger Warning
+
+Deleting a field can affect page blocks, forms, filters, permissions, workflows, APIs, imports and exports, and existing data. Confirm that the field is no longer referenced by business configuration before deleting it.
+
+:::
+
+## Use in pages
+
+Password fields are suitable for protected configuration values in forms.
 
+![Use a Password field in a page](https://static-docs.nocobase.com/20260709225244.png)
 
-![20240512175917](https://static-docs.nocobase.com/20240512175917.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Enter or change a password value. |
+| Details block | Display a masked value where supported. |
+| Configuration pages | Store protected configuration values. |
+| Workflows and APIs | Use only when business logic requires the value. |
 
-## Example
+## Related links
 
-To be added.
+- [Fields](../index.md) - Learn about field categories and mapping.
+- [General collection](../../../data-source-main/general-collection.md) - Create and manage fields in a collection.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/basic/percent.md

@@ -1,13 +1,112 @@
-# Percentage
+---
+title: "Percent"
+description: "The Percent field stores percentage values such as completion, discount, and conversion rates."
+keywords: "Percent,percent,field,Field interface,NocoBase"
+---
+
+# Percent
 
 ## Introduction
 
-## Field configuration
+In NocoBase, the **Percent** field stores percentage values.
+
+It is suitable for completion rates, discount rates, conversion rates, and other ratios. Use Number when the business value is not a percentage.
+
+## Use cases
+
+Percent fields are suitable for these business scenarios:
+
+- Task completion rates
+- Discount and tax rates
+- Conversion and pass rates
+- Progress and utilization rates
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Percent** to create this field.
+
+![Configure a Percent field](https://static-docs.nocobase.com/20240512175847.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Percent uses `percent`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Completion rate`, `Discount rate`, or `Conversion rate`. Use a name that business users can recognize. |
+| Field name | The field identifier used internally by APIs, relation fields, permissions, and workflows. It usually cannot be changed after creation. It supports only letters, numbers, and underscores, and must begin with a letter. |
+| Field type | The data-layer type. Percent uses `double` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. Supports minimum, maximum, and required validation. |
+| Description | A field description. Record the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Field names are referenced by page blocks, permissions, workflows, and APIs after creation. Confirm the name before creating the field to avoid later configuration changes.
+
+:::
+
+## Field behavior
+
+The default behavior of a Percent field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `percent`. |
+| Default Field type | `double`. |
+| Available Field types | `double`, `decimal`. |
+| Page component | Uses a percentage-aware number input in edit mode. |
+| Filtering | Supports numerical filters such as greater than, less than, equals, and is empty. |
+| Sorting | Supports sorting in Table blocks. |
+| Validation | Supports minimum, maximum, and required validation. |
+
+## Edit configuration
+
+After creation, click **Edit** beside the field to edit its configuration. Edit fields to adjust how they are displayed and used in NocoBase, such as the display name, description, default value, validation rules, or field-specific settings.
+
+When a field comes from a synchronized main-database table, editing usually maps the database field to a NocoBase Field type and Field interface.
+
+| Setting | Can be edited | Description |
+| --- | --- | --- |
+| Field display name | Yes | Changes the name displayed in the interface without changing the field identifier. |
+| Field name | No | The field identifier normally cannot be changed in the edit form after creation. |
+| Field interface | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Changes affect page input, display, and validation. |
+| Field type | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Confirm that existing values can be used by the new type first. |
+| Default value | Yes | Adjusts the default value for new records. |
+| Validation rules | Yes | Adjusts field validation rules. |
+| Description | Yes | Adds the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Changing a Field type or Field interface is more than changing a display name. It affects field storage, input components, validation rules, filters, and workflow-variable usage. When the field contains substantial existing data, confirm that its data format is compatible first.
+
+:::
+
+## Delete field
+
+Click **Delete** beside a Percent field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Percent field created in the main database usually also deletes the actual database column and its values. For a synchronized or external-data-source field, the impact depends on the corresponding data source and field origin.
+
+:::danger Warning
+
+Deleting a field can affect page blocks, forms, filters, permissions, workflows, APIs, imports and exports, and existing data. Confirm that the field is no longer referenced by business configuration before deleting it.
+
+:::
+
+## Use in pages
+
+Percent fields are suitable for percentage entry, display, statistics, and conditions.
 
+![Use a Percent field in a page](https://static-docs.nocobase.com/20260709225150.png)
 
-![20240512175847](https://static-docs.nocobase.com/20240512175847.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Enter a percentage value. |
+| Table block | Display, sort, and filter percentages. |
+| Details block | Display a percentage value. |
+| Workflows and permissions | Use the value in percentage conditions and calculations. |
 
-## Example
+## Related links
 
-to be added.
+- [Fields](../index.md) - Learn about field categories and mapping.
+- [General collection](../../../data-source-main/general-collection.md) - Create and manage fields in a collection.
+- [Number](./number.md) - Store ordinary numerical values.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/basic/phone.md

@@ -1,13 +1,113 @@
+---
+title: "Phone"
+description: "The Phone field stores mobile phone and contact phone numbers."
+keywords: "Phone,phone,field,Field interface,NocoBase"
+---
+
 # Phone
 
 ## Introduction
 
-## Field Configuration
+In NocoBase, the **Phone** field stores mobile phone numbers.
+
+It is suitable for mobile numbers, contact numbers, and service hotlines. Compared with normal Input fields, it provides clearer phone-number semantics and format validation.
+
+## Use cases
+
+Phone fields are suitable for these business scenarios:
+
+- Customer and contact mobile numbers
+- Employee contact numbers
+- Supplier and service hotlines
+- Emergency contact numbers
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Phone** to create this field.
+
+![Configure a Phone field](https://static-docs.nocobase.com/20240512175526.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Phone uses `phone`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Mobile number`, `Contact phone`, or `Service hotline`. Use a name that business users can recognize. |
+| Field name | The field identifier used internally by APIs, relation fields, permissions, and workflows. It usually cannot be changed after creation. It supports only letters, numbers, and underscores, and must begin with a letter. |
+| Field type | The data-layer type. Phone uses `string` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. Supports length, regular-expression, and required validation. |
+| Description | A field description. Record the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Field names are referenced by page blocks, permissions, workflows, and APIs after creation. Confirm the name before creating the field to avoid later configuration changes.
+
+:::
+
+## Field behavior
+
+The default behavior of a Phone field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `phone`. |
+| Default Field type | `string`. |
+| Available Field types | `string`. |
+| Page component | Uses an Input component with phone-number validation in edit mode. |
+| Filtering | Supports text filters such as contains, equals, is empty, and is not empty. |
+| Sorting | Supports sorting in Table blocks. |
+| Validation | Supports length, regular-expression, and required validation. |
+
+## Edit configuration
+
+After creation, click **Edit** beside the field to edit its configuration. Edit fields to adjust how they are displayed and used in NocoBase, such as the display name, description, default value, validation rules, or field-specific settings.
+
+When a field comes from a synchronized main-database table, editing usually maps the database field to a NocoBase Field type and Field interface.
+
+| Setting | Can be edited | Description |
+| --- | --- | --- |
+| Field display name | Yes | Changes the name displayed in the interface without changing the field identifier. |
+| Field name | No | The field identifier normally cannot be changed in the edit form after creation. |
+| Field interface | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Changes affect page input, display, and validation. |
+| Field type | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Confirm that existing values can be used by the new type first. |
+| Default value | Yes | Adjusts the default value for new records. |
+| Validation rules | Yes | Adjusts field validation rules. |
+| Description | Yes | Adds the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Changing a Field type or Field interface is more than changing a display name. It affects field storage, input components, validation rules, filters, and workflow-variable usage. When the field contains substantial existing data, confirm that its data format is compatible first.
+
+:::
+
+## Delete field
+
+Click **Delete** beside a Phone field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a Phone field created in the main database usually also deletes the actual database column and its values. For a synchronized or external-data-source field, the impact depends on the corresponding data source and field origin.
+
+:::danger Warning
+
+Deleting a field can affect page blocks, forms, filters, permissions, workflows, APIs, imports and exports, and existing data. Confirm that the field is no longer referenced by business configuration before deleting it.
+
+:::
+
+## Use in pages
+
+Phone fields are suitable for forms, details, filters, and notification contacts.
 
+![Use a Phone field in a page](https://static-docs.nocobase.com/20260709224555.png)
 
-![20240512175526](https://static-docs.nocobase.com/20240512175526.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Enter a phone number. |
+| Details block | Display a phone number. |
+| Filter block | Filter records by phone number. |
+| Workflows and notifications | Use the value as a contact source. |
 
-## Example
+## Related links
 
-to be added.
+- [Fields](../index.md) - Learn about field categories and mapping.
+- [General collection](../../../data-source-main/general-collection.md) - Create and manage fields in a collection.
+- [Input](./input.md) - Store ordinary short text.
+- [Email](./email.md) - Store email addresses.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/basic/textarea.md

@@ -1,22 +1,113 @@
-# Long Text
+---
+title: "Textarea"
+description: "The Textarea field stores longer plain-text content such as notes, opinions, and detailed addresses."
+keywords: "Textarea,textarea,field,Field interface,NocoBase"
+---
+
+# Textarea
 
 ## Introduction
 
-## Field Configuration
+In NocoBase, the **Textarea** field stores multi-line text.
+
+It is suitable for customer notes, processing opinions, detailed addresses, and other text that might span multiple lines. Use Input for short text and Rich text or Markdown for formatted content.
+
+## Use cases
+
+Textarea fields are suitable for these business scenarios:
+
+- Customer notes and internal remarks
+- Processing opinions and descriptions
+- Detailed addresses and supplementary information
+- Long plain-text content
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **Textarea** to create this field.
+
+![Configure a Textarea field](https://static-docs.nocobase.com/20240512165017.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. Textarea uses `textarea`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Customer notes`, `Processing opinion`, or `Detailed address`. Use a name that business users can recognize. |
+| Field name | The field identifier used internally by APIs, relation fields, permissions, and workflows. It usually cannot be changed after creation. It supports only letters, numbers, and underscores, and must begin with a letter. |
+| Field type | The data-layer type. Textarea uses `text` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. Supports minimum length, maximum length, fixed length, case, regular-expression, and required validation. |
+| Description | A field description. Record the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Field names are referenced by page blocks, permissions, workflows, and APIs after creation. Confirm the name before creating the field to avoid later configuration changes.
+
+:::
+
+## Field behavior
+
+The default behavior of a Textarea field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `textarea`. |
+| Default Field type | `text`. |
+| Available Field types | `text`, `string`, `json`. |
+| Page component | Uses a multi-line textarea in edit mode. |
+| Filtering | Supports text filters such as contains, equals, is empty, and is not empty. |
+| Sorting | Supports sorting in Table blocks where supported by the data source. |
+| Validation | Supports minimum length, maximum length, fixed length, case, regular-expression, and required validation. |
+
+## Edit configuration
+
+After creation, click **Edit** beside the field to edit its configuration. Edit fields to adjust how they are displayed and used in NocoBase, such as the display name, description, default value, validation rules, or field-specific settings.
+
+When a field comes from a synchronized main-database table, editing usually maps the database field to a NocoBase Field type and Field interface.
+
+| Setting | Can be edited | Description |
+| --- | --- | --- |
+| Field display name | Yes | Changes the name displayed in the interface without changing the field identifier. |
+| Field name | No | The field identifier normally cannot be changed in the edit form after creation. |
+| Field interface | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Changes affect page input, display, and validation. |
+| Field type | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Confirm that existing values can be used by the new type first. |
+| Default value | Yes | Adjusts the default value for new records. |
+| Validation rules | Yes | Adjusts field validation rules. |
+| Description | Yes | Adds the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Changing a Field type or Field interface is more than changing a display name. It affects field storage, input components, validation rules, filters, and workflow-variable usage. When the field contains substantial existing data, confirm that its data format is compatible first.
+
+:::
+
+## Delete field
+
+Click **Delete** beside a Textarea field to delete it. You can also select multiple fields and delete them in the main data source.
 
+Deleting a Textarea field created in the main database usually also deletes the actual database column and its values. For a synchronized or external-data-source field, the impact depends on the corresponding data source and field origin.
 
-![20240512165017](https://static-docs.nocobase.com/20240512165017.png)
+:::danger Warning
 
+Deleting a field can affect page blocks, forms, filters, permissions, workflows, APIs, imports and exports, and existing data. Confirm that the field is no longer referenced by business configuration before deleting it.
 
-## UI Configuration
+:::
 
-### Edit Mode
+## Use in pages
 
+Textarea fields are suitable for forms, details, and long plain-text content.
 
-![20240512164001](https://static-docs.nocobase.com/20240512164001.png)
+![Use a Textarea field in a page](https://static-docs.nocobase.com/20260709224428.png)
 
 
-### View Mode
+| Scenario | Use |
+| --- | --- |
+| Form block | Enter or edit multi-line text. |
+| Details block | Display long plain-text content. |
+| Table block | Display a shortened value in lists. |
+| Workflows and permissions | Use the value in text conditions and business rules. |
 
+## Related links
 
-![20240512164138](https://static-docs.nocobase.com/20240512164138.png)
+- [Fields](../index.md) - Learn about field categories and mapping.
+- [General collection](../../../data-source-main/general-collection.md) - Create and manage fields in a collection.
+- [Input](./input.md) - Store short text.
+- [Rich text](../media/rich-text.md) - Store formatted content.

package/dist/ai/docs/nocobase/data-sources/data-modeling/collection-fields/basic/url.md

@@ -1,13 +1,112 @@
+---
+title: "URL"
+description: "The URL field stores website, document, and other external addresses."
+keywords: "URL,url,field,Field interface,NocoBase"
+---
+
 # URL
 
 ## Introduction
 
-## Field configuration
+In NocoBase, the **URL** field stores URL addresses.
+
+It is suitable for official websites, document links, and external addresses. Compared with a normal Input field, it provides clearer URL semantics and URL-format validation.
+
+## Use cases
+
+URL fields are suitable for these business scenarios:
+
+- Official websites
+- Document and help links
+- External system addresses
+- Product and service URLs
+
+## Create and configure
+
+On the collection's **Configure fields** page, click **Add field** and select **URL** to create this field.
+
+![Configure a URL field](https://static-docs.nocobase.com/20240512175641.png)
+
+| Setting | Description |
+| --- | --- |
+| Field interface | The field interface. URL uses `url`, which determines how the field is entered and displayed in pages. |
+| Field display name | The name displayed for the field, such as `Official website`, `Document link`, or `External address`. Use a name that business users can recognize. |
+| Field name | The field identifier used internally by APIs, relation fields, permissions, and workflows. It usually cannot be changed after creation. It supports only letters, numbers, and underscores, and must begin with a letter. |
+| Field type | The data-layer type. URL uses `string` by default. |
+| Default value | The default value. When a new record has no value, NocoBase can fill this value automatically. |
+| Validation rules | Validation rules. Supports URL-format, length, and required validation. |
+| Description | A field description. Record the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Field names are referenced by page blocks, permissions, workflows, and APIs after creation. Confirm the name before creating the field to avoid later configuration changes.
+
+:::
+
+## Field behavior
+
+The default behavior of a URL field is as follows:
+
+| Behavior | Description |
+| --- | --- |
+| Default Field interface | `url`. |
+| Default Field type | `string`. |
+| Available Field types | `string`. |
+| Page component | Uses an Input component with URL-format validation in edit mode. |
+| Filtering | Supports text filters such as contains, equals, is empty, and is not empty. |
+| Sorting | Supports sorting in Table blocks. |
+| Validation | Supports URL-format, length, and required validation. |
+
+## Edit configuration
+
+After creation, click **Edit** beside the field to edit its configuration. Edit fields to adjust how they are displayed and used in NocoBase, such as the display name, description, default value, validation rules, or field-specific settings.
+
+When a field comes from a synchronized main-database table, editing usually maps the database field to a NocoBase Field type and Field interface.
+
+| Setting | Can be edited | Description |
+| --- | --- | --- |
+| Field display name | Yes | Changes the name displayed in the interface without changing the field identifier. |
+| Field name | No | The field identifier normally cannot be changed in the edit form after creation. |
+| Field interface | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Changes affect page input, display, and validation. |
+| Field type | Conditional | Main-database fields and synchronized fields can be adjusted during field mapping. Confirm that existing values can be used by the new type first. |
+| Default value | Yes | Adjusts the default value for new records. |
+| Validation rules | Yes | Adjusts field validation rules. |
+| Description | Yes | Adds the field meaning, entry requirements, data source, or maintainer. |
+
+:::warning Note
+
+Changing a Field type or Field interface is more than changing a display name. It affects field storage, input components, validation rules, filters, and workflow-variable usage. When the field contains substantial existing data, confirm that its data format is compatible first.
+
+:::
+
+## Delete field
+
+Click **Delete** beside a URL field to delete it. You can also select multiple fields and delete them in the main data source.
+
+Deleting a URL field created in the main database usually also deletes the actual database column and its values. For a synchronized or external-data-source field, the impact depends on the corresponding data source and field origin.
+
+:::danger Warning
+
+Deleting a field can affect page blocks, forms, filters, permissions, workflows, APIs, imports and exports, and existing data. Confirm that the field is no longer referenced by business configuration before deleting it.
+
+:::
+
+## Use in pages
+
+URL fields are suitable for forms, details, and external navigation.
 
+![Use a URL field in a page](https://static-docs.nocobase.com/20260709224747.png)
 
-![20240512175641](https://static-docs.nocobase.com/20240512175641.png)
 
+| Scenario | Use |
+| --- | --- |
+| Form block | Enter a URL address. |
+| Details block | Display and open a URL. |
+| Filter block | Filter records by URL value. |
+| Workflows and APIs | Pass an external address to business logic. |
 
-## Example
+## Related links
 
-To be added.
+- [Fields](../index.md) - Learn about field categories and mapping.
+- [General collection](../../../data-source-main/general-collection.md) - Create and manage fields in a collection.
+- [Input](./input.md) - Store ordinary short text.