Skip to main content
User Experience

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • I totally understand your concern about the two buttons being next to each other. My solution was to space them out significantly to reduce confusion. Since this page is set up the way it is, the buttons need to be on the card header to minimize clicks. As for the header color, it’s part of our design system and is used consistently across the web app. It’s a great point, and I’ll keep it in mind when I get around to updating it. Thanks for your input! 🙏🏻 @drabsv Commented Jan 24 at 15:57
  • 1
    I'd rather increase the chevron visual weight, to demonstrate that it belongs to the header, that is, it belongs to visual hierarchy level 1, while anything else, inside the header should be of lower visual hierarchy level. Differentiation in visual weight, should make it easier for the user to figure out quickly the purpose of each one of those teo CTAs. Commented Jan 25 at 10:28
  • 1
    "As for the header color, it’s part of our design system" - I can guess, it is present as simple header in the design system kit, not crammed with so many strong elements inside? That is, in this particular case, the design system header should not be your reference, since this is a special type of header, never planned in the design system on the first place, isn't it? You should rather insist that this be added as a new element to the design system. Commented Jan 25 at 10:35