Interaction Guidelines

This document is used to clarify the general UX processing solutions that are not reflected in the prototype, and will be continuously updated.

General Copy Principles

All copy not provided in the system can be defined by the product team. For clear cases, developers can decide, but consistency must be maintained for the same operations. Chinese can be used initially, and the system will later conduct an overall localization review. Currently, the following copy principles serve as reference:

• Keep descriptions as brief as possible
• Avoid using pronouns such as you, I, he, we, they, etc. Remind the design and product teams to address any copy in the prototype that conflicts with the above principles.

Data Deletion (2025-03-21)

All operations in the system that use the API to delete data require secondary confirmation. Developers can decide whether to use Dialog or Popup based on the scenario. The copy is as follows: For deletions with sub-items, include the content in parentheses; for those without sub-items, remove the content in parentheses. English:

Confirm deletion (All linked items will be permanently removed. This action cannot be undone)

Chinese:

确定删除（所有关联数据将被永久删除，此操作无法撤销）

For deletions during the editing process, such as deleting a Rule when editing Tag Rules or deleting a file when editing Mapping, secondary confirmation is not required (because the deletion action does not immediately change the database).

Toast Interaction (2025-03-21)

Ensure that all user operations have clear feedback. Use Toast when existing page elements cannot provide feedback.

Toast Types

• Success: Green

English:

Operation successful

Chinese:

操作成功

• Warning: Orange

Scenario: Invalid operation (failure due to logical issues, not allowed, etc.)

Copy: Explain according to the actual situation

• Error: Red

English:

Operation failed

Chinese:

操作失败

• Information: Blue

Scenario: Need to alert the user

Copy: Explain according to the actual situation