Ready

Mechanics

This page provides guidelines for the mechanics of writing, including formatting for file sizes, file extensions, acronyms, abbreviations, punctuation, and capitalization in the Basis design system.

Ready

Mechanics

This page provides guidelines for the mechanics of writing, including formatting for file sizes, file extensions, acronyms, abbreviations, punctuation, and capitalization in the Basis design system.

Ready

Mechanics

This page provides guidelines for the mechanics of writing, including formatting for file sizes, file extensions, acronyms, abbreviations, punctuation, and capitalization in the Basis design system.

Capitalization

Capitalization

Capitalization

Sentence case is when you capitalize the first letter of the first word in a phrase or sentence only, and every other word starts with a lower case letter. Title case is when you capitalize the first letter of every word.

Even when using sentence case, you should capitalize the proper nouns or labels in the UI.

Use sentence case for:

  • Button / link text

  • Input placeholder text

  • Tooltip text

  • Body text

  • Empty state messages

  • Checkbox text

Title case should be used for:

  • Form field labels

  • Referring to form fields in sentences

  • Dropdown menu items

  • Headings

  • Wizard step names

  • Proper nouns

Punctuation

Punctuation

Punctuation

Minimize the amount of punctuation in the UI. Punctuation leads to clutter and can make it harder to parse or scan text quickly.

Always include question marks when appropriate and include commas where necessary, including the serial comma.

Periods

Avoid using periods for a single sentence or sentence fragment in these elements:

  • Tooltips

  • Flash messages

  • Error messages

  • Title tags

  • Bulleted lists

  • Notifications

  • Activity Feed items

Periods should always be used for:

  • Multiple sentences

  • Body text

  • Any sentence followed by a link

  • Any sentence that includes other punctuation that impacts the flow of the sentence, like commas, colons, or dashes.

Commas

Include commas before the last item in a list. This is known as the serial, or Oxford, comma.

Search for campaigns, groups, and tactics.

Search for campaigns, groups and tactics.

Colons

Don’t use colons in headings. In body text, include a colon to introduce a list.

Projected spend is calculated using historical data from the following data points:

  • Locations

  • Bid price

  • Device types

  • Inventory types

  • Creative types and dimensions

Projected spend is calculated using historical data from the following data points.

  • Locations

  • Bid price

  • Device types

  • Inventory types

  • Creative types and dimensions

Ampersand

Ampersands (&) can cause issues for localization and accessibility. Use “and” instead of an ampersand in almost all cases.

Only use ampersands where space is limited, such as column headers. To minimize confusion, the terms joined by an ampersand should be closely related or commonly paired.

Pixels & Audiences

Pizza & Pasta

Pixels and Audiences

Sushi & Borscht

Parentheses

Don’t include additional information in parentheses. Only use parentheses to define technical terms or provide the common abbreviation or acronym.

Put punctuation like periods or commas outside of parentheses.

Return on Ad Spend (ROAS) measures the revenue from ads.

Return on Ad Spend, or ROAS, measures the revenue from ads (this can be a useful metric to determine how effective your campaign was.)

Parenthetical plural (s) (es)

Don’t use “(s)” or “(es)” to indicate that something can be plural. Use the plural form instead or say “one or more” if it’s necessary to call out both.

Add deals

Select tactics

Add one or more exchange to the tactic

Add deal(s)

Select tactic(s)

Add exchange(s) to the tactic

Exclamation points

Avoid using exclamation points. They can come across as shouting and, if used too frequently, can be bothersome. One exception is for greetings.

Changes saved

RFP sent

Welcome to Basis!

Changes saved successfully!

RFP sent!

Campaigns not receiving delivery!

Acronyms

Acronyms

Acronyms

Acronyms may be used in place of common phrases or when it is industry standard. Acronyms are typically all uppercase. If there’s a chance your reader won’t recognize an acronym, spell it out.

Do

Do

Do

  • Accept IO

  • Sent RFP

  • CPM

  • KPI

Don't

Don't

Don't

  • Accept I.O.

  • Send rfp

Abbreviations

Abbreviations

Abbreviations

Field labels may be abbreviated if necessary. Abbreviations should be in lowercase with no period at the end. If an abbreviated label is being referenced directly, be consistent and use the abbreviated version. Write out the words where more explanation is required for understanding.

Do

Do

Do

  • imps

  • proj balance

Don't

Don't

Don't

  • imps.

  • IMPS

  • proj. balance

File sizes

File sizes

File sizes

To represent file sizes, use the abbreviated version in all caps with a space a er the file size number.

Do

Do

Do

  • 233 KB

  • 50 MB

  • 1 GB

Don't

Don't

Don't

  • 233 kb

  • 50mb

  • 1GB

File extensions

File extensions

File extensions

When referring to a file type in general, use all uppercase letters without a period. For specific files, the file extension should be lowercase.

Do

Do

Do

  • Attach a PDF, JPG, or PNG

  • Upload CSV...

  • IAB-standard-terms-conditions.pdf

  • sample-site-list.xlsx

Don't

Don't

Don't

  • Attach a .pdf, .jpg, or .png

  • Upload .csv...

  • IAB-standard-terms-conditions.PDF

  • sample-site-list.XLSX