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
The Query Loop block is arguably one of the most advanced blocks out there, and its complexity can intimidate and cause frustration to less advanced users.
What is your proposed solution?
Once #37080 is in place, the Query Loop block should be hidden from the inserter unless advanced users specifically search for it. This way, less advanced users will get exposed to the Query Loop block only through patterns and its block variations, such as Posts List, but the block will still be available for power users.
The text was updated successfully, but these errors were encountered:
👋🏼 On today's hallway hangout with the FSE Outreach Program, this came up and it was suggested to actually rename the Pattern category to something more user friendly and I wanted to connect some dots by following up here for future reference. I can see how doing so would be problematic as it would likely lead to more folks adding in a complex block that they then aren't equipped to customize. This is ideally where having query loop variations power things like the post list will be very high impact though as I can imagine then patterns can be created using these easier to use blocks instead.
What problem does this address?
The
Query Loop
block is arguably one of the most advanced blocks out there, and its complexity can intimidate and cause frustration to less advanced users.What is your proposed solution?
Once #37080 is in place, the
Query Loop
block should be hidden from the inserter unless advanced users specifically search for it. This way, less advanced users will get exposed to theQuery Loop
block only through patterns and its block variations, such as Posts List, but the block will still be available for power users.The text was updated successfully, but these errors were encountered: