-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consolidating the Query Loop block, Latest Posts block and Post Lists block #32332
Comments
Combining those four blocks into one is a great idea. In the case of Post Lists block, it would be quite easy since it’s the same block under a different name. Page List block would also be trivial to combine, and the users would benefit from having more control over the results since this block just spits out a list of all the pages the user has. The only thing users would lose if we got rid of this block would be the possibility to create a bulleted list, something that I’m not sure it’s possible to achieve in an easy way using the Query block. Latests Posts (LP) would be a little more difficult to remove right away because it has some nice settings that are a bit difficult to achieve with the Query block . Here’s a table with the equivalent methods and some pros/cons for the alternative method in the Query block (QB):
Finally, the Latest Posts filters are similar to the ones in the Query block, but in the Latest Posts block, users can change the number of items from the sidebar. |
While I was thinking about this issue, I thought of another idea: instead of consolidating these blocks into one, would it make sense to leave them as independent blocks but make them all use the Query block internally? The only difference would be that initially, they would have different settings to render each kind of list. |
After thinking for a while about this issue, I think that my second idea makes more sense. The basic Query block should be a powerful and "content agnostic" block, probably more oriented towards advanced users with specific needs (like theme developers). The other blocks would use the Query block internally but start with a different set of defaults, reducing the number of blocks to maintain and offering a similar experience to the user while at the same time helping them to find an appropriate block faster. Another important thing we'd need to pay attention to is the name of the block in the sidebars. Right now, if a user inserts a |
I found this ticket by @jameskoster that has a more comprehensive list of enhancements and ideas about the Post List block #32268 |
Hey @jarekmorawski Thank you for the feedback to various issues! It is greatly appreciated! Thank you again! |
Noting that the Posts Lists variation was removed in 6.7 #63404 |
Description
At the moment there exists three blocks that to me seems to do the same thing.
The Query block, Latest Posts block and the Post Lists block.
It seems like the settings vary a bit between the blocks as well.
My expectation is to have one block that covers what is needed to show Posts or a CPT, with a few different filters on how I would like to show the Posts/CPT on each page. Having three block options to choose from is very confusing.
Consolidating the three blocks into one block would be helpful, as a user would then be able to select the specific block to do what is needed to show the specific content.
The text was updated successfully, but these errors were encountered: