A dialog is a interaction between the system and the user. It is prompted when the system urgently needs input or confirmation from the use. There are two types of dialogs, modal and dialog.
Dialogs work best when used for singular, short tasks or to notify the user of task-relevant information. They keep the user anchored on the current page and allow for easy snap back once the purpose of the dialog is completed. However, dialogs are disruptive to the workflow they inhabit and thereby should be used sparingly. They should only be used for the most necessary interactions.
A dialog is triggered by an action of the user, appears above the main content of the page and remains until it is closed. The purpose of a dialog should be immediately apparent to the user, with a clear and obvious path to completion.
Dialogs always have an overlay. The overlay has the same color as the BG of the dashboard, but only in 70% transparency. The entire background behind the dialog or modal is 15% blurred. The header of the dashboard is always excluded.
Title: The title should be brief and clearly describe the dialogues’s task or purpose. Use the optional label above the title set the context for the information in the dialogue. When using modals, the title is optional.
Toolbar: The toolbar contains all actions for the body as well as the modal or dialogue. More Infos you will find in the Action Placement. When using modals, the toolbar is optional.
Body: Contains the information and/or controls needed to complete the dialogue’s task. It can include message text and components.
Actions: The main actions needed to complete or cancel the dialogue task. Use descriptive words for the actions like Add, Delete, Save and avoid vague words like Done or OK.
A Dialog can vary in the height and width, with the dimensions depending on the context. The width of the modal is based on breakpoints within the window while the content.
Rules on the maximum height of dialogs will follow soon.
A dialogue is used when the system requires the user to enter data or perform tasks. The body of the dialogue is variable and can be freely edited. It is only important that the dialogue does not become too long. In such a case, please separate the interaction into partial interactions.
When a dialogue is active, the content of the underlying page is hidden and not accessible until the user completes the task or closes the modal dialogue.
The Inspire UI kit separates all its dialogues into two types: Basic and Process Dialog.
The basic dialogue consists only of a dialogue without a sidebar. This type of dialogue may be used for all conceivable simple interactions.
The process dialogue may only be used for interactions that specify a sequence of different interaction sections. The different sections are shown in the sidebar, and the user can move backwards and forwards within the process sections.
There are several possible ways to exit a non-modal dialog.
A modal dialogue triggers a state that focuses the user's attention exclusively on a task or relevant information. Modals interrupt a user's workflow by design. When active, a user is blocked from the one-page content and cannot return to their previous workflow until the modal task is completed or the user dismisses the modal. While effective when used correctly, modals should be used sparingly to limit disruption to the user.
How a modal is dismissed and the effects thereof depend on the content of the modal. For more information, read "Use Cases for Modals".
Dialogues are triggered by a user's action and not generated by the system. Common components that can trigger a dialogue include buttons, links or icons.
Once the dialogue box is open, set the initial focus to the first location that allows user input. The focus should then remain in the dialogue until it is closed.
The modal component has a fixed maximum height. If the content of the dialogue is longer than the height of the dialogue, the main part should be divided into so that the user can scroll through the process. For this case, only the process dialogue may be used.
Validate a user's input before closing the dialogue. If an input is invalid, the dialogue should remain open with the input marked with an error status and an inline error message. The message should inform the user what has happened and give advice on next steps or possible solutions. An effective and immediate error message can help the user understand and resolve the problem.
Look for footerbar actions
When placing buttons, Cancel is always the outmost left button option and the primary action is always the outmost right button. There should only ever be one primary action per dialog. Dialog buttons are always full bleed and attached to the bottom of a dialog.
Single buttons are placed across the entire page. The single button format is most commonly used for confirmation dialogues. In most scenarios, a primary button is used when only one button is needed.
When using two buttons, the secondary or ghost button is on the left and the primary button is placed on the right. Each button spans 50% of the dialog and are full bleed to the edge.
If three buttons are required, each takes up 33.33 % of the dialogue width. Only the rightmost button may be a primary button, the other two are secondary buttons. If all three actions have the same weight, all three should be secondary buttons.
Passive modals present information the user needs to be aware of concerning their current workflow. It contains no actions for the user to take and should not include any data that needs to be submitted. They should serve as a type of notification alerting the user to urgent information such as reporting system errors or conveying a consequence of a user's action. [Link to Notifications]
Active modals are used to validate user decisions it to gain secondary conformation from the user. Active modals require an action to be taken in order for the modal to be completed and closed. It contains a cancel and primary action button.
Acknowledgement modals are used to validate user decisions or to gain secondary confirmation form the user. Transactional modals require an action to be taken in order for the modal to be completed and closed. It contains a cancel and primary action button.
Focus modals are used to contain very important user decisions. The focus here is the focused headline. The focused modals have only ghost buttons. After confirming, the user will be informed about their conformation via inline notification.
