'Inherit query from template' setting is confusing

[jameskoster]

The 'inherit query from template' setting asks users to comprehend complex details within the context of an already-complex block.

Inherit query from template
Toggle to use the global query context that is set with the current template, such as an archive or search. Disable to customize the settings independently.

There are likely longer-term fundamental changes to make that would eliminate the need for this setting, but that doesn't mean we can't attempt to make the control more intuitive in the short term.

[jameskoster]

One idea is to use a segmented control rather than a toggle. I acknowledge it's a little unconventional for a boolean setting, but I think provides space to better describe both options. Toggles work better for really intuitive settings, but in this case it oversimplifies.

cc @WordPress/gutenberg-design for feedback.

[carolinan]

Can we find a way to inform users when the default query does not work? Like in the post content, or in a custom page template.

[paaljoachim]

Thank you for adding this issue James!

Thinking out loud / brainstorming.

Looking at the phrase used today:
"Toggle to use the global query context that is set with the current template, such as an archive or search. Disable to customize the settings independently."

The following words can be difficult to understand: global query context ........ in current template
One has to know what global and query is and what is meant with the current template. A lot to try to understand within one sentence.

Ideas....
Toggle off to customise which posts are displayed.
Toggle on to use default query, such as an archive or search.

The main issue is to make it easier to understand what is going on here with as few as possible words. The more words the more difficult it can be to not understand what is going on. Explaining what happens with toggle on or off can be helpful so the user understands what both do.

[jarekmorawski]

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 posts or other items.

If we stick to a toggle, we should only use one copy variant to avoid confusing people ("is the feature enabled or not?"). In that case, Jay's early suggestion can work better, allowing us to describe each outcome clearly.

What if we put the button in a dedicated Content section? I tweaked the copy a bit to make it feel actionable, practical, and concise. I also replaced template with page because, well, on the front-end the block will always be shown on a page and never in a template.

[jameskoster]

Good input, thanks y'all.

I also replaced template with page because, well, on the front-end the block will always be shown on a page and never in a template.

Maybe we could even simplify even further: "Use the default query e.g. category archive or search results". Additionally, since the help text uses the word default explicitly I would lean towards that being the label control too. 'Follow' seems a bit ambiguous to me.

I appreciate filtering archives is a common pattern in WooCommerce, but it's not really possible (except for search) in core, so I'd probably omit that part for the sake of simplicity. Start with less.

The Content panel is an interesting idea and does resonate. But it would be antithetical with other Content panels, which exist to help users locate editable blocks in the current context. That one might be worth visiting separately.

Can we find a way to inform users when the default query does not work?

This is an excellent point. I can't think of a single use case for a Query inside a Content block to inherit (can you?). Maybe the option should be automatically set to custom, and the control hidden from the UI when Query Loop is placed inside Content?

[jarekmorawski]

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 the option should be automatically set to custom, and the control hidden from the UI when Query Loop is placed inside Content?

I like that.

[jameskoster]

I feel like we're closing in on something here, and could potentially think about opening a PR, but would welcome wider feedback :)

[richtabor]

Copy wise, can we reduce the technical terminology further? Terms like "global query settings" and 'primary query in a template" don't connect well for most folks.

Maybe something along the lines of:

Use the current template's blog settings to display posts.

Customize which posts are displayed.