Remove component from unit

[sdaitzman]

Not the same as deleting a component from within a unit! This workflow shows the distinction.

Screenshots

Spec

• Users can remove a component from a unit
• The component is NOT deleted, and remains present in the library
• A toast shows that the component was removed, and allows the user to undo

In Scope

• Remove from unit overflow menu item
• Overflow menu item appears in sidebar for selected components in unit
• Overflow menu item appears directly on components in full page unit view

Not in scope

• Bulk remove / selection

Additional States

Hover	Overflow menu active	Removed

[bradenmacdonald]

The component is NOT deleted, and remains present in the library

Is this the case even if the component was originally created in the unit?

If so, is every component created in a unit also available separately in the library? Let's specify the answer clearly on #1619 too.

[sdaitzman]

Yes, I think every component created in a unit should appear at the top level when viewing "All My Content" and be available separately. Otherwise, I think some of the reuse and deletion logic gets a bit messy and users may have some unexpected downstream effects.

When a user deletes a section, I'm hoping to avoid a complex downward deletion cascade where some components, units, and subsections are fully deleted and others remain in the library depending on their reuse within the library / outside it. It adds some complexity if users want to delete a bunch of content at once, but I think we should fix that in a future workflow.

Added this to the spec in #1619