Design Guidelines

These guidelines explain the visual and structural decisions that shape an ADITO Web Client application. They help customizers decide what users see, how they move through the application, and which actions they can perform. The aim is a consistent interface that users can understand without having to learn a different pattern in every context.

They complement rather than replace the technical reference. The viewtemplates and layouts reference describes how to configure a component, while the device and accessibility support matrix shows its documented status.

A helpful workflow

1. The workflow starts with the user task and the information it requires.
2. A fitting viewtemplate and layout provide the next foundation.
3. All fields, actions, labels, and navigation remain focused on what users need.
4. A review on the intended devices and with the required accessibility settings completes the picture.

---

What belongs here

Customizers choose standard components, arrange them, select data and actions, and define contexts, menus, and labels. These decisions determine whether a screen supports a task or merely exposes the data that happens to be available. Themes define the global color system.

The interaction and accessibility behavior of a standard viewtemplate is not freely configurable. The documented options provide a reliable basis; reviewing the resulting screen in the client shows how they work together in the project.

For the detailed boundary, see Scope and responsibilities.

Guideline structure

Topic	Use this document for
ADITO design principles	Shared rules for design decisions.
Information, navigation, and labels	Content, menus, labels, icons, and wording.
Contexts	The scope and views of a context.
Standard view patterns	Task-oriented patterns for filter, preview, and main views.
Forms and validation	Data entry and validation messages.
Dashboards and dashlets	Dashboards as an overview.
Visual design and data presentation	Themes, color, charts, tables, and display types.
Actions and interaction	actions and action flows.
Permission-aware interfaces	Screens that differ by role.
Custom and embedded content	Content outside standard viewtemplates.
Devices and accessibility	Devices, accessibility, WCAG, and BITV.
UX review checklist	Release review.
Spelling and wording	English text conventions.
Best Practices	Planned examples.

note

The viewtemplate support matrix is the authoritative source for the documented device and accessibility status of each viewtemplate. Its status applies to the documented intended use and supported configuration. A different use case needs its own review.