Page History
Intro
This page contains product-specific UI text guidelines for Edge.One Inspire Design System.
About this guideline
The Edge.One Inspire Design text guidelines are not exhaustive. They build on the other writing guidelines at Edge.One, and cover only specific conventions for Edge.One applications. The guidelines have evolved on an as-needed basis to clarify questions that have arisen during Edge.One app development, or to reiterate points that recur in Edge.One app design reviews.
The guidelines are based on US English, the primary source language at Edge.One. There are no specific Edge.One text guidelines for other languages.
Finding your way
See the content overview at the beginning of each section to navigate. You can also return to the start of each section at any time using the anchors in the header area.
Toast Messages
To make the toast message easy to scan, keep the text as short as possible. Remember that the user will not have time to take in very much detail. Do not use the word “successfully” in the message text. This is implicit in a success message.
Patterns
For standard actions (such as create, save, delete, or send), we recommend using the following patterns, depending on your use case.
| Use Case | Use Case Variant | Pattern (EN) | Example (EN) |
|---|---|---|---|
| Single item | Object name is not needed. Hint: If the name or ID is not crucial feedback in your context, leave it out. | [object] [action taken] | Sales order created |
| Object name is needed. Hint: If you mention the object name, you can often leave out the object type (usually obvious in the context). | [name] [action taken] | SAP added to customer group | |
| Multiple items | [item count] [objects] [action taken] | 2 sales orders were deleted. | |
| Multiple actions | Single items, object names are not needed | 1 [object] [1st action taken], 1 [object] [2nd action taken] | 1 product added, 1 product removed |
| Single items, object names are needed. Hint: Only include object names if the user really needs the specific feedback. | [object] [name] [1st action taken], [object] [name] [2nd action taken] | Product A was added, product B was removed. | |
| Multiple items | [item count] [objects] [1st action taken], [item count] [objects] [2nd action taken] | 2 products added, 3 products removed |
Notes:
- The exact phrasing will depend on your target audience and the conventions in your app family. If an action is repeated regularly by heavy users, be as brief as possible (for example, Order deleted). If your app is typically for occasional users, a full sentence might be more appropriate (for example, Your request has been sent to the support team.).
- Bear in mind that long object names can increase the length of the message toast. Remember to allow for this when defining the toast duration. If long or multiple object names make the toast too cumbersome to read, leave them out. If you really need to list them in a success message, use the success message box instead.
| Do | Don't |
|---|---|
Product saved Toast without ID | Sales order has been created successfully Do not use "successfully" |
3 Products were deleted. Toast with item count | Products Machine A, Machine B and Machine C were deleted. Do not list names of multiple items |
If you are using Inspire Design elements, remember to replace the “object” placeholder with your business object.
| Do | Don't |
|---|---|
Purchase order deleted Replace "object" with your specific business object | Object deleted Do not leave the "object" placeholder |
