Content guidelines
Capitalization and authored-label rules for interface content.
Tab labels
Use sentence case for tabs: capitalize the first word, then use lowercase unless a word is a proper name or acronym. Use the same rule for in-page tabs and tabs that navigate to another route.
| Use | Avoid |
|---|---|
| Connected apps | Connected Apps / CONNECTED APPS |
| Quality checks | Quality Checks |
| Purchase orders | Purchase Orders |
| My assistants | My Assistants |
| Release notes | Release Notes |
| Beat versions | Beat Versions |
| GitHub connections | Github connections |
| API settings | Api settings |
Single-word labels such as Profile and Preferences remain capitalized. Preserve proper names such as Harmonica, Cajon, GitHub and Slack, and acronyms such as API, SSO and PII. Product entity nouns follow sentence case too: Work items and Beat versions.
Write the intended casing in each label definition. Tab components must render
that text unchanged; do not use CSS uppercase, lowercase, or capitalize,
or change the string's case at runtime. A blanket transformation cannot
preserve names and acronyms or handle translated content correctly.
Keep visible and accessible tab names aligned. Preserve counts and user-authored names. When navigation and tabs use the same label definition, keep that shared wording consistent rather than introducing a second capitalization variant.
This convention applies to Tabs,
TabList, tab-mode SegmentedControl, and application
adapters such as legacy MUI tabs. Other component types retain their documented conventions.
Decision record
Approved for Harmonica and Cajon on October 20, 2026, in Harmonica decision N-4E09-10735, superseding the earlier Profile-only title-case choice. The rule removes the mixture of title case, sentence case, and automatic uppercase presentation. It follows the web convention in Fluent's content guidance.