## Background
Some suggestions include more than one action to solve the suggestion. For example, the `yearLink` suggestion can offer multiple resolution actions (e.g. “Use 2002”, “Use 2004”), in addition to secondary actions like {nav Dismiss}. At the moment, all these buttons are included as stacked buttons in the card, which is not a good solution.
{F71690303}
The Check/Suggestion card was originally designed to support two equal primary actions: Accept and Dismiss. When a suggestion requires more than one valid resolution action, we need to define a clearer grouping pattern so that resolve and decline remain visually balanced, while additional resolution options do not compete for space or attention.
### User stories
- As an editor, when a suggestion offers multiple valid ways to resolve it, I want the Accept + Dismiss options to be clearly structured so I can quickly understand and choose between them.
### Possible solution
If there are more than 1 action to solve the suggestion, we can group all them under a `MenuButton`.
{F71690424}
### Open questions
// Add here the questions to be answered in order to design and implement the component //
### Artifacts
//Design mockups, prototypes, etc.//
| Design proposal |
### Acceptance criteria (or Done)
[] Explore feasible solutions to group solving actions when there is more than 1 per suggestion
[] Test solution if needed
[] Implement decided solution