Design Guidelines

Design Guidelines

It is important that the UI is consistent and systematic in the way information is organised and presented. This page brings together guidelines that should apply throughout the application. Deviations are allowed, but it must be clear why a deviation is required, and any such deviation should also be an opportunity to revisit the corresponding guidelines to see is these need to change.

Widgets and Pages Guidelines

• Table
• Page with Table
• Page with Cards
• Modal dialogue
• Parameters

General remarks

Page should by default be filled on load. If this is not the appropriate behaviour (e.g. no reasonable default exist), then the page should clearly indicate that no data was loaded and the user is expected to provide information.

Note that the CIMI page is a special case, which does not follow these guidelines. The CIMI page is designed to follow the SlipStream API, inspired by CIMI, and therefore follows it as closely as possible.