Content Editor Components - Module Dropzone Card

[ceyerkes]

Hi again! I wanted to continue to chat about the Drag & Drop components, but thought it would make more sense to divide up this work into a couple different conversations to help focus future office hours sessions on specific areas of the drag & drop pattern. I'm working on what i'm calling the module drop zone card (name suggestions welcome).

All drop zone cards will be slightly different in what actions need to be included (3 need HTML buttons, the rest don't) as well as what the body of the card will contain. All require delete, copy, and move/drag.

This one is basically a Pastified version of current MC:

This is a Pastified Lightning drop zone component (ish):

Looking forward to chatting during office hours after the holidays, thanks!

[nkrantz]

Hey @ceyerkes, thanks for coming to Office Hours.

Here's the recording from yesterday (find the password in #help-design-system slack).

This is definitely a unique type of flow, so some of these UX patterns will have to be learned. Generally we don't love controls that appear on hover, but it makes sense here, especially because they also show up in the focus/selected state. Also consider whether any of your smaller components/modules can exist without the same type of container, or whether that might be more confusing for users.

All in all, your work is coming along wonderfully, we're excited to see how it progresses! Feel free to keep using these threads for more questions/updates.

[ceyerkes]

Thanks Nora, appreciate all the feedback as usual!

[ceyerkes]

Drop Zone Card update via Loom as requested!

I ran out of time, but i'm wondering if i can use an icon-only menu dropdown for the modules that are dropped inside of columns to save space, kind of like how MC handles this now:

I can bring this back to office hours, or we can chat async, whatever works!