You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've recently added "convert to blocks" as an option to the block level ellipsis menu on the Classic Text block. This feels like a natural place for this, since it's an advanced transformation at the block level.
Should we show other transforms in this menu? This would be a pattern that we could reuse from the current "Switcher" interface.
Mockups
When selecting on a single block:
When multiple blocks are selected:
In these mockups we show the most obvious transformation directly (that would be gallery when selecting multiple images, or perhaps quote when selecting multiple text blocks), as well as a "Transform into" popout menu.
Is this a good design? Is the popout menu too complex? Do we think it might be a scalable pattern to show all transformations directly in the menu?
Perhaps this issue could be tackled in phases, to test what works.
Reacted by Tammie Lister, Riley Brook and Miguel Fonseca
Yeah this makes sense! I think it would also solve the issue we found where people don't notice or recognize the block switcher in the toolbar (especially now that it has been moved to the top bar). Smart thinking to put them in a foldout menu also, the list might get quite long.
First, I'd like to say that I like this idea a lot. Moving the switcher to this menu. A small concern I have with this design is the double "popover". You need to open the foldout menu, hover (or click) the "Turn Into" button to show the transformations.
I'd be in favor of showing all the transformations in the foldout menu after the separator.
I really like this idea, to me it's the kind of magical nudge that takes the experience to one that really engages people. I like having after the separator also.
In these mockups we show the most obvious transformation directly (that would be gallery when selecting multiple images, or perhaps quote when selecting multiple text blocks)
Could you envision the set of rules required for "most obvious transformation" becoming too complicated? That complexity could be reduced by leaving "most obvious transformation" out of the foldout menu and just showing all transformation options, as planned for these early stages.
Could you envision the set of rules required for "most obvious transformation" becoming too complicated? That complexity could be reduced by leaving "most obvious transformation" out of the foldout menu and just showing all transformation options, as planned for these early stages.
I can come up with a couple of opinions, but you make a solid point: perhaps we don't want to be arbiters of which transformations are "the most obvious".
Regarding the "obvious transformations", I think our approach to making a test with no distinction between obvious and non-obvious is good, maybe we don't need this at all. But if we take the conclusion that we need this distinction, I think It should be up to the transform implementor to use a flag that sets that his transformation is important, the downside his every block developer want's to give relevance to his blocks so we may end up with many "obvious" transformations.
Activity
StaggerLeee commentedon Nov 10, 2017
Looks very modern and nice. At least for me.
hedgefield commentedon Nov 13, 2017
Yeah this makes sense! I think it would also solve the issue we found where people don't notice or recognize the block switcher in the toolbar (especially now that it has been moved to the top bar). Smart thinking to put them in a foldout menu also, the list might get quite long.
youknowriad commentedon Nov 13, 2017
First, I'd like to say that I like this idea a lot. Moving the switcher to this menu. A small concern I have with this design is the double "popover". You need to open the foldout menu, hover (or click) the "Turn Into" button to show the transformations.
I'd be in favor of showing all the transformations in the foldout menu after the separator.
jasmussen commentedon Nov 13, 2017
I think that's fine, especially as a start. Then we can see what becomes necessary.
karmatosed commentedon Nov 13, 2017
I really like this idea, to me it's the kind of magical nudge that takes the experience to one that really engages people. I like having after the separator also.
rileybrook commentedon Nov 14, 2017
Could you envision the set of rules required for "most obvious transformation" becoming too complicated? That complexity could be reduced by leaving "most obvious transformation" out of the foldout menu and just showing all transformation options, as planned for these early stages.
jasmussen commentedon Nov 15, 2017
I can come up with a couple of opinions, but you make a solid point: perhaps we don't want to be arbiters of which transformations are "the most obvious".
jorgefilipecosta commentedon Nov 15, 2017
Regarding the "obvious transformations", I think our approach to making a test with no distinction between obvious and non-obvious is good, maybe we don't need this at all. But if we take the conclusion that we need this distinction, I think It should be up to the transform implementor to use a flag that sets that his transformation is important, the downside his every block developer want's to give relevance to his blocks so we may end up with many "obvious" transformations.