Patterns
Last modified by Thiago Krieck on 2026/11/18 14:13
Patterns combine several components to handle a situation that comes up again and again, such as asking before something is destroyed or showing that a list has nothing in it. Each entry describes the whole flow, so that users meet the same steps wherever the situation appears.
When a screen runs into one of these situations, developers should follow the pattern rather than design a new flow.
- Delete confirmation: asking before something is destroyed
- Empty state: what to show when there is nothing to show
More
- Related: Components, Content
- Back to XWiki UI Standards