Gutenberg: Locking a Block and Block Outlines

Created on 22 Jun 2018 · 8Comments · Source: WordPress/gutenberg

Not sure about this, but as part of reducing the visual weight in nested contexts, I think we should not render most of the UI on locked templates. For example, if we have a wrapper block, with some column blocks inside, and the wrapper is set to be locked, we should avoid rendering individual column outlines, or fade the outline further.

Source

mtias

Most helpful comment

@kjellr this is about using blocks to define structure, but preventing its UI (selection state, outlines, toolbar, etc) from showing up. Imagine the current "post content" as a container block that has no interface — it just transparently contains all the blocks.

mtias on 8 Jul 2019

👍4

All 8 comments

I would +1 to fading the outline. I also am very aware nesting rapidly becomes quite a concentrated heavy interface.

karmatosed on 25 Jun 2018

But what if that wrapper block needs to be selectable because even though it is locked it has some attributes that have Inspector Controls?

kraftner on 26 Jun 2018

@kraftner I wonder if this is a situation where block breadcrumbs in the sidebar might be useful. See this comment on #6459.

ZebulanStanphill on 26 Jun 2018

👍1

👋 Block outlines have changed a bit since this issue was filed, and will likely change more if #14961 makes it in. In the meantime, I'm having a little trouble understanding the nature of this issue. I think a couple more examples (ideally visual ones, even if they're messy!) would help explain the concept here a little more clearly. Thanks!

kjellr on 2 Jul 2019

mtias on 8 Jul 2019

👍4

I would actually say this is even _more_ valuable if #14961 gets merged, because it gives container blocks an even greater visual weight/visibility. The changes in #14961 make a lot of sense _if visualising the container itself is important_, but in some cases the container itself is more of an implementation detail which should be invisible.