Action labels
Last modified by Thiago Krieck on 2026/11/18 14:13
English source strings only. Each language's style is left to the Weblate translators.
The standard
Labels of buttons, menu items, links and icon tooltips that trigger an action should tell users exactly what will happen.
- Form: Should start with a verb, followed by the object when it isn't obvious from the context: Save, Add comment, Create user. See Buttons.
- Casing: Should use sentence case (Add comment, Save & view), with capitals only for the first word and proper names, since it reads more naturally and is what newer screens already use. Never all lowercase, never in brackets.
- Delete vs Remove: Delete should be used when the item is destroyed (a page, a user, an object), and Remove when it is only taken out of a collection and still exists elsewhere (a member from a group, a tag from a page), so that users know whether they can get it back.
- Create vs Add: Create should be used for something new that stands on its own (page, wiki, user, group), and Add for something attached to an existing item (comment, tag, member, property).
- One label per operation: The same operation should have the same label in the menu, the dialog title and the confirm button, so that users recognize it at every step.
- Ellipsis: A label should end with an ellipsis (Create user…) when the action opens a dialog asking for more input before anything happens, and not when it acts at once or only asks for confirmation (Delete). It should be the single character … (U+2026), with no space before it.
- Confirmations: Should repeat the action, never Yes, No or OK. See Delete confirmation.
Reference example: Administration → Users and Groups. The Create user and Create group buttons, the Edit user and Delete user dialog titles, and their Cancel and Delete buttons all start with a verb, use sentence case and say Delete for destroying.

Action labels: Administration → Groups
Notes
- Repeated labels in a list (Delete on every comment or row) should have an accessible name that includes the item, such as Delete comment by Alice Martin rather than only Delete, so that screen reader users know which one they act on. See Accessibility.
- Translation keys: a new key should be named after its module and context, with a suffix for its role (.label, .hint, .submit), such as livedata.action.addEntry, rather than a flat key like save. Fixing the casing or punctuation of a value can keep its key; changing the meaning needs a new key, with the old one moved to the deprecated section, so that translators update it. The full rules are in the dev.xwiki.org L10N conventions.
- Values should be stored as plain text, not HTML-escaped: Save & view, not Save & view.