[Resource page debt] Reorganize the resource actions (order, segmentation, unfolding criteria)

[oboc-sts]

Problem / Opportunity
Each resource type has a set of actions a user can perform. Some actions are generic, available for most resource types (e.g. view config, edit config, delete, etc), whilst other actions are specific to a particular resource type. Some are more (frequently) used than others. Some are more critical than others. Some are specific to particular user roles, whilst others are universally applicable to all users.

Currently, regardless of the type of actions or the type of resource or the type of user, all resource pages "promote" the same actions (view / edit config) for all resource types.

Added value / Impact

• Improved ease and speed of use
• Reduced interaction cost
• Reduced cognitive load
• Increased trust and loyalty (we are the authority that knows best and we show this at every step)

Solution / Proposal
For all resource types in Rancher redefine:

• the order of actions: least to most critical actions, most to least used actions, etc.
• the segmentation: max 3 brackets = 2 horizontal separators (e.g. specific, generic, management, etc.)
• the unfolding criteria: what we show by default as actions on the resource page (e.g. the most used 3 actions, the first 5 actions based on the order, etc)

Mind the accessibility:

• Use labels or find ways to make the icons self explanatory

Preview

Associated links
Resource page redesign epic