For the English language, we recommend using English capitalization rules for titles (i.e. generally, capitalize the first letter of each word). Titles include the following user interface elements:
- Page titles
- Panel titles
- Section headings
- Form section titles
- Table headers
- Dialog titles (reference rule #8: grammarbook.com)
Capitalize only the first letter of data labels unless a word used in the data label otherwise deserves capitalization because of English capitalization rules (i.e. proper names, abbreviations, etc).
Data labels include the following UI elements:
- Radio button labels
- Checkbox labels
- Form property labels
- Panel property labels
- Button labels
- Action menu items
- Hyperlinks to actions
- Hint text
- Help text
Capitalize only the first letter of attributes unless a word used in the attribute otherwise deserves capitalization because of English capitalization rules (i.e. proper names, abbreviations, etc). User-entered attributes will retain the user’s capitalization.
The English language is full of exceptions, so we felt compelled. For attribute values which indicate the property or data field that hasn’t been set or the location is intentionally left empty, we use the non-capitalized words or phrases such as “empty”, “none”, “not set”, “unassigned”, or “no alerts”.
Some specific words and acronyms are always capitalized for branding or common industry recognition.
Capitalization in APIs
Yes, our application users make use of our APIs, so it’s important to provide a familiar voice to our users, regardless of the interface they are using.
- Schema names
- Schema enum values
The following API elements should be rendered in camelCase:
- Schema attribute names