Actions
Actions trigger a modal to open or a function to be carried out. They are usually verbs or a verb form.
Actions are found in the action bar, context menu, or button.
✅ Yes | ❌ No | Notes | |
---|---|---|---|
1 | Edit details | Edit name and description, Rename | Calls modal to change name and description |
2 | Edit [item type] | Calls modal to change item configuration or settings | |
3 | Close | Quit | Used for modal primary buttons |
4 | Create new | Create new tree item | |
5 | Create [item type] | Applies to any item that requires a save to initiate creation | |
6 | Delete | ||
7 | Copy | Copy to clipboard or to paste | |
8 | Duplicate | Clone | Duplicate whole items |
9 | Remove | ||
10 | Download | ||
11 | Export | ||
12 | Upload | Browse | |
13 | Duplicate | ||
14 | Run, Rerun, Refresh | Re-run | |
15 | Train | ||
16 | Build | ||
17 | Select | Click, Press | |
18 | Sign-in / Sign-out | Log in / Log out | Verb |
19 | Signing-in | Verb | |
20 | Sign-in settings | Adjective | |
21 | Sign-in | Noun |
Metadata
Metadata provides information about the state of an item or object. Metadata is often located in table column headers or a details panel.
✅ Yes | ❌ No | Notes | |
---|---|---|---|
1 | Item name | Object name | |
2 | Last run | Workflows, Parent Segments | |
3 | Last build | Insights Model | |
4 | Last trained | Predictive Scoring | |
5 | Last attempt | ||
6 | Last updated | Last modified | |
7 | Updated by | Last modified by | |
8 | Created by | ||
9 | Created on | Created at | |
10 | Column |
Proper Nouns
Proper nouns are always title-capitalized regardless of the context and do not follow capitalization rules that have been set.
Proper nouns are identified based on whether the company invented the term for an object in console. If it is an industry standard term, then it should not be a proper noun.
Abbreviations
Abbreviations are a shortened form of a word or phrase.
Spell out the full word of abbreviated terms if space accommodates and it is not a frequently used term. Place abbreviation in parentheses after.
e.g. Identity Provider (IdP)
Limit Usage
Certain words add unnecessary filler text or complicate reading. Some words are difficult to understand. This is a guidance, not a mandate.
Limit Usage | Notes | |
---|---|---|
1 | please | Unless used in a dynamite modal, avoid usage of “please”. It implies to a user that an action is optional. |
2 | click / click on | Someone may not always be using a mouse |
3 | fill in | Use “type”, “edit”, or “enter” |
4 | now | |
5 | soon | |
6 | once | Means one time, not after. Use “after” instead |
7 | above | Avoid directional words, bad for localization |
8 | below | Avoid directional words, bad for localization |
9 | in order to | Can be shortened: “to” |
10 | note that | |
11 | in the future | |
12 | should | |
13 | may | use might |
14 | either | |
15 | neither | |
16 | as well as | use “and” |
17 | difficult | use “complex” for positive connotation |
18 | complicated | use “complex” |
19 | here | Don’t use this as a link, instead link the name of an object |
20 | Latin words | via, vs. , etc. , i.e.Exception:e.g. can be used if an example needs to be given |
21 | Slang | We have many international users. Slang is varies across cultures. |
22 | Complex jargon | |
23 | Negative words:failed, error, gone wrong | Avoid pessimism. Focus on what the user can do to solve issues |
Treasure Data Portfolio
- Information architecture. Complete redo of the UI.
- Access control security structure
- Segmentation UI
- Figma design system
- Journey building UI
- Data Model UI
- Workflow Editor
- Illustrations for empty states
- Schema template for advanced database management
- Advanced Tree Search
- Microcopy design guide