When editing a page, the Content panel surfaces the sections of the document that can be directly manipulated. My understanding is that it does this by looping through the document looking for instances of specific blocks; Title, Featured Image, and Content. When found they are listed in the panel for easy selection:
However, if the Content block also contains instances of these blocks – for instance if there's a custom query in the page content – then those blocks are repeated:
For a number of reasons this makes for a strange UX:
- There's no benefit to highlighting nested featured images, titles, etc because as properties of separate entities they cannot be edited
- It's not clear which is the document-level version of the block
- They add weight to the Content panel, diluting its usefulness
- Selecting a nested block creates a confusing UI where both the block and the parent appear to be selected
Solution
It would seem sensible to omit these blocks in the Content panel when they are nested within the Content block.
cc @noisysocks as (iirc) you worked on this feature.
When editing a page, the Content panel surfaces the sections of the document that can be directly manipulated. My understanding is that it does this by looping through the document looking for instances of specific blocks; Title, Featured Image, and Content. When found they are listed in the panel for easy selection:
However, if the Content block also contains instances of these blocks – for instance if there's a custom query in the page content – then those blocks are repeated:
For a number of reasons this makes for a strange UX:
Solution
It would seem sensible to omit these blocks in the Content panel when they are nested within the Content block.
cc @noisysocks as (iirc) you worked on this feature.