This page outlines the tone guidelines for the Basis design system, emphasizing being dedicated to others, honest, positive, smart, professional, and clear and direct in communication.

Content is a critical part of the user interface, so words and writing are an essential part of design. These language and grammar writing principles help make our UX copy clear to all readers.

Everybody should be able to understand and enjoy our product. The language that we use should be clear and unambiguous to all readers. Following these guidelines allows readers of all levels to understand our content and makes it easier to translate to other languages.

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.

This page provides guidelines for formatting numbers, dates, times, and null values in the Basis design system.

A confirmation dialog informs a person about the consequences of an action to make sure that they want to complete it. For example, if the user is about to undertake a destructive action or an action that cannot be reversed, it is helpful to confirm that they want to proceed before completing it. Confirmation messages should pose a question to the user, explain the consequences, and provide options to reaffirm their decision or to back out.

Error messages are used to inform the user about an error state. Errors can be associated with specific elements or contexts, or they can occur as the result of a user action. They may take the form of an issue indicator, a form input message, a flash message, or a message card.

It’s sometimes necessary to link to a page in the Help Center to provide more information about a feature. A link should be added after another message in the app, like help text or an error. It should never exist on its own without context.

This word list provides usage guidelines for terms that you may use in Basis's UI.

It's important to use consistent language across the UI when describing user actions. Avoid device-specific terms like "click", "tap", or "swipe". Instead, choose generic verbs that work with any device.