[HelpHub] Feedback on Query Loop Block

[zzap]

URL of the Page with the Issue

https://wordpress.org/documentation/article/query-loop-block/

Report content (issue description)

Under Post Types, it would be helpful if the text read:

“WordPress contains different types of content, and they are divided into collections called “Post types”. By default, there are a few different ones, such as blog posts and pages, but plugins could add more. If you’ve created a custom post type with your theme or plugin, you can add it to the Query Loop Block as an option by making sure that show_in_rest is set to true.”

By https://profiles.wordpress.org/cdevroe/

In the «Filters» section it says that you can use «any keywords» to filter posts. It should be clarified that multiple keywords will always be combined with the AND operator and that filtering by just one of multiple keywords is not available.

By https://profiles.wordpress.org/martinsauter/

[github-actions]

Heads up @WordPress/docs-issues-coordinators, we have a new issue open. Time to use 'em labels.

[kedarjoyner]

@zzap @estelaris I'm curious your thoughts on the following feedback in the issue description:

“ If you’ve created a custom post type with your theme or plugin, you can add it to the Query Loop Block as an option by making sure that show_in_rest is set to true.”

I wonder if this feels more like developer advice, and maybe out of scope for this document? Let me know your thoughts!

[kedarjoyner]

@zzap @estelaris I'm curious your thoughts on the following feedback in the issue description:

“ If you’ve created a custom post type with your theme or plugin, you can add it to the Query Loop Block as an option by making sure that show_in_rest is set to true.”

I wonder if this feels more like developer advice, and maybe out of scope for this document? Let me know your thoughts!

@estelaris Just closing the loop here! I will close this issue. We discussed this yesterday in the Docs meeting in Slack and decided we should not include this in HelpHub documentation because it's more for developers. The other item in the issue description is accounted for in the Query Loop documentation.