> For the complete documentation index, see [llms.txt](https://tech.x2bee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tech.x2bee.com/dev-guide/developer-guide-en/pjt-prepare/ui-ux-guide/screen-detail-guide/button-creation-guide.md).
# Button Creation Guide
## Button Label Notation
1. All button labels are written as nouns.
* \[Save], \[Confirm], \[Next], \[Previous], etc.
* Noun forms of verbs or adjectives are restricted.\
ex) \[Saving]
2. When writing button labels, use a label that expresses the user's action rather than a feature title.
* Since the task/feature description already appears on the workspace screen, use a label that expresses the user's action.
* As an exception, to avoid confusion when interpreting the button's function via a user-action label, the task/feature name may be prefixed.
* When two or more different tasks must be handled on the same screen, use task name + action, e.g. \[Out-of-Stock Product List]
3. For a unique task where the button label itself needs to describe it, e.g. \[Translation Request], \[Reset], etc.
4. When clicking a button opens a popup to process a task, use the '↗︎' icon to visually indicate that a popup will appear.
5. For popup or related-screen buttons, the target screen name may be used as the button label.
6. Order execution buttons according to the screen's functionality.
## Button Display Sizes
* Text button minimum size: 60\*36
* Icon button: 20\*20
