Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggested improvements to reusable block flow #4041

Closed
karmatosed opened this issue Dec 15, 2017 · 4 comments · Fixed by #4139
Closed

Suggested improvements to reusable block flow #4041

karmatosed opened this issue Dec 15, 2017 · 4 comments · Fixed by #4139
Assignees
Labels
[Feature] Blocks Overall functionality of blocks [Feature] Synced Patterns Related to synced patterns (formerly reusable blocks) Needs Dev Ready for, and needs developer efforts
Milestone

Comments

@karmatosed
Copy link
Member

It's worth noting that these mocks do not include #3810 and the potential name change as that is still being worked through.

Currently the flow of reusable blocks is this:

resuaable1

I want to suggest we change a few things to give this as the flow:

reusable2

The biggest change is that 'Edit | Detached' are no longer together. We give an option to detach anyway and by moving everything to the ellipsis we can have a new section. Here you can delete and detach. This helps avoid misclicking with 2 very different actions being beside each other.

I also changed 'Edit' to say what it does. This is a little improvement on clarity. We could reduce the text there to say 'Edit name', I am open to suggestion there.

The 'save / cancel' being beside each other I'm still not totally sold on, but it's a trap pattern we have in WordPress and for now leaving that.

As this includes the deletion, it ties in with #3792 also.

@karmatosed karmatosed added [Feature] Blocks Overall functionality of blocks Needs Design Feedback Needs general design feedback. labels Dec 15, 2017
@afercia
Copy link
Contributor

afercia commented Dec 18, 2017

I also changed 'Edit' to say what it does.

While I'm all for control labels that are as explicit as possible, seems to me the Edit button makes the whole block editable, not only its name. Currently, to edit the content of a reusable block users have to click Edit.

One more thing: maybe the first "Delete" should be "Remove"?

34050308-50088fc2-e1b2-11e7-9a9a-100db07e8492

This is visible also in the current menu, where "Delete" doesn't really delete the reusable block: it just removes it from the post and the saved wp_block post type is still saved in the database.

@jasmussen
Copy link
Contributor

Intellectually I like moving "Detach" to the ellipsis menu, not only because it's a slightly "destructive" action, but because then there's more room for a label. But I'm also not over the moon convinced that it's a good change. The toolbar that pops out at the bottom seems like a great place to surface actions that are contextual to the reusable block, and another way to make the detach action less destructive would be to make a JavaScript confirm dialog, which could also in descriptive text describe what detaching really means.

Adding Delete Reusable Block to the ellipsis menu, I kind of feel the same about. It's good to put it in the advanced settings because it's destructive. But at the same time it feels like we are optimizing for the current interface, where I think we should presume that there is a separate "Manage Reusable Blocks" page somewhere in the future, for example under the Presentation menu item?

But all that said, this feedback isn't helping what we have today, and I completely acknowledge that a future interface can easily become a resting pillow for not doing anything. As such, I do think adding the delete in the ellipsis menu is a good change for now, especially if combined with a JavaScript prompt. Though I'd echo Andrea's feedback, if we use the delete phrase for the reusable block, we should use "Remove" for the block thing.

@karmatosed
Copy link
Member Author

@afercia I am ok with changing delete to remove, thanks for the suggestion.

@jasmussen I also agree this is possibly a halfway step, but I think it's an important one to take. We are just starting to see the potential of reusable blocks. I fully expect that will grow and with it what our solution should be.

@karmatosed karmatosed added Needs Dev Ready for, and needs developer efforts and removed Needs Design Feedback Needs general design feedback. labels Dec 19, 2017
@karmatosed karmatosed added this to the 2.0.0 milestone Dec 19, 2017
@aduth aduth added the [Feature] Synced Patterns Related to synced patterns (formerly reusable blocks) label Dec 19, 2017
@noisysocks noisysocks self-assigned this Dec 20, 2017
@noisysocks
Copy link
Member

noisysocks commented Dec 20, 2017

Thanks @karmatosed! I'll look at implementing this as part of #4031.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Blocks Overall functionality of blocks [Feature] Synced Patterns Related to synced patterns (formerly reusable blocks) Needs Dev Ready for, and needs developer efforts
Projects
None yet
5 participants