[Resource page debt] Use specific action verbs in a consistent way throughout the platform (show more, view more, etc)

[oboc-sts]

Problem / Opportunity
Whenever an action verb is used throughout the UI to reflect a call to action, it should also give the user a hint about the type of interaction that's about to happen to set up the right expectations. Here are a couple of concerns users have if we don't do this properly:

• is this button going to perform this action on the same page, or in a different page?
• will I be able to come back to this (state of the) page after I click on this element?
• should I open this link in a new tab just in case?

... I really don't want to lose my current configuration of this page (filters, scroll position, unfolded elements, etc).

Added value / Impact

• Improved usability
• Reduced cognitive load
• Increased transparency and trust (predictable behaviour)

Solution / Proposal
Check out the solution we've adopted in the SUSE Observability (preview below) and try to aim for a similar approach. Keep it consistent throughout the UI.

E.g. use "View..." for CTAs that will take the user to another page, use "Show..." for CTAs that will display additional content on the same page, use "Learn more..." for documentation links, etc.

Comment from Ken: reach out to the docs team to get this consistent across the portfolio.

Preview
StackState Guidelines - Interaction Verbs.pdf

Associated links
Resource page redesign epic