jarekmorawski

I like that approach, but it could get unwieldy when we throw custom fields into the mix. Additionally, the side-by-side layout in both explorations may break on languages like German,...

I see your point, but I'm still concerned about scalability. An image block may only have two attributes, but there may be blocks with a dozen or more. As far...

The accordion may make the popover grow awkwardly long for some attributes.  I wonder if we could use tabs instead?  

> Do you have some examples? The toolspanel scales reasonably well, but can always be improved for benefits across. I can't think of anything that'd have more than 4 or...

It's testing well for me in both editors. Nice work! 🙌 ### Site editor https://github.com/user-attachments/assets/0f0e9610-6e1d-4739-86ff-41754996cbcf ### Post editor https://github.com/user-attachments/assets/c1187f56-10e8-49d1-8b24-f74a7b5d3aae

How would that work? Can you give me a few examples? Is there a finite number of such errors?

Love those suggestions, @paaljoachim. I'd only include filters in the help text because they also modify the query and it's rather common for people to display a filterable list/grid of...

Maybe something like this could work? Even simpler. Given the user is editing the block in a template context, we'd inform them what _will_ happen on the front-end. > Maybe...

Could "items" work? We'd then use the copy in other situations, like displaying products, tags, etc.

Sounds good to me! Then QL derivatives like Product Collection could slightly tweak the copy while remaining aligned with the core block. The only thing I'm not sure of is...