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
It would be handy if there was a clickable label that appears inside the query block and before the <!-- wp:post-template --> and <!-- wp:wp-curate/post --> blocks that are contained within, so that there is something within the block editor interface to click on in order to make the query block focusable without using the Document Overview sidebar or the breadcrumbs. It doesn't necessarily need to be an interactive element, so long as it takes up some space so that something in the query block is clickable. I think this would significantly improve the user experience of the curate plugin.
Use Case
When a user edits a page which uses wp-curate to control queries, making the query block directly clickable would allow users to edit the query parameters without selecting a child block and then using supplemental navigation elements to select the query block. We implemented this on a client project that used a different curation interface that followed a similar principle (a container block that controlled query parameters and child blocks which represented individual posts) and it made the editorial experience much more intuitive.
The text was updated successfully, but these errors were encountered:
Description
It would be handy if there was a clickable label that appears inside the query block and before the
<!-- wp:post-template -->
and<!-- wp:wp-curate/post -->
blocks that are contained within, so that there is something within the block editor interface to click on in order to make the query block focusable without using the Document Overview sidebar or the breadcrumbs. It doesn't necessarily need to be an interactive element, so long as it takes up some space so that something in the query block is clickable. I think this would significantly improve the user experience of the curate plugin.Use Case
When a user edits a page which uses wp-curate to control queries, making the query block directly clickable would allow users to edit the query parameters without selecting a child block and then using supplemental navigation elements to select the query block. We implemented this on a client project that used a different curation interface that followed a similar principle (a container block that controlled query parameters and child blocks which represented individual posts) and it made the editorial experience much more intuitive.
The text was updated successfully, but these errors were encountered: