Usability Issue: "Edit" should be elevated out of the three-dot context menu in Libraries

[ormsbee]

While doing development, the majority of the time that I was selecting a Component, it was for the purpose of editing it. This is such a common action that the Studio course unit editing page keeps the "Edit" button out of the context menu, so that users can do this in one click:

In content libraries, there are two paths, both of which require two clicks:

• click on component card, and then click on the "Edit component" in the sidebar
• click on the three-dot context menu for the component card, and then click "Edit"

Acceptance criteria:

• Edit icon/button appears on Component cards, to the left of the context menu, echoing the style currently used in the course screenshot. It should be exactly equivalent to clicking on "Edit" in the context menu today.
• "Edit" is no longer an option in the context menu for a Component.

[ormsbee]

FYI @jmakowski1123, @bradenmacdonald

[bradenmacdonald]

It "feels" to me like double-clicking a card should open the editor / open the collection. That would be an easy fix with no UI changes?

[ormsbee]

I personally dislike the double-click metaphor for web stuff because it's not really a standard interaction, and it's not at all discoverable.

[ormsbee]

But then again, I'm a web luddite who used Google Apps for years and years before realizing you could double-click there, so I'll defer to Product and UX. 😛

[jmakowski1123]

Pulling in @lizc577

[rpenido]

Hi team! @jmakowski1123 @lizc577 @bradenmacdonald @ormsbee

Can we move forward with the proposal of promoting the "Edit" item to the title header?

Note that we use the same menu on the sidebar, where we already have an Edit option outside the menu.

[jmakowski1123]

It makes sense to me from a page hierarchy standpoint. Do we now need the edit in both the header space and the 3-dot dropdown? Seems like unnecessary redundancy? @sdaitzman