## Background
- **Description:** An overarching guideline to recommend on interaction element hierarchy and choice between
-- links
-- normal buttons
-- quiet buttons
-- primary buttons
--- buttons with and without icons, or icon-only buttons
- **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 this guideline also live in DSG?
### Acceptance criteria for done
**Design**
[] Design the guideline
**Code**
[] Implement the guideline in Codex