## Background
In the past we've been seeing confusion in product teams which of the various basic interaction elements to choose from in which context. The general user focus guidance would be improved by a guideline for an overarching page interaction element hierarchy.
**Description:** An overarching guideline to recommend on interaction element hierarchy and choice between:
- links
-- normal link
-- new/red link
-- neutral link (see below)
- normal buttons
- quiet buttons
- primary buttons
-- buttons with icons and label or
-- icon-only buttons
- secondary buttons, currently quiet progressive and quiet constructive buttons
- groups of buttons, see T327426
Related to be considered taken into account, when to use static icons?
**History:** We're currently missing strong guidelines in the Design Style Guide on when to choose which of the more basic interaction elements.
**Known use case(s):** Different interaction elements prioritized in siloed product teams lead to confusing page composition when skins, extensions and external user-interface library
**Considerations:**
### User stories
As a designer, I'd like to know which of the DS interaction elements are best used when.
### Guideline specification
| guideline spec sheet |
### Open questions
- Should a third type of link besides the new/red link be considered for the design system? A neutral link? Related task T311270
- Should this guideline also live in DSG?
### Acceptance criteria for done
**Design**
[] Design the guideline
**Code**
[] Implement the guideline in Codex