Skip to content
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

Decouple Query/Post Block Experiment from Site Editor Experiment #26316

Closed
ianstewart opened this issue Oct 20, 2020 · 7 comments
Closed

Decouple Query/Post Block Experiment from Site Editor Experiment #26316

ianstewart opened this issue Oct 20, 2020 · 7 comments
Assignees
Labels
[Block] Query Loop Affects the Query Loop Block [Status] In Progress Tracking issues with work in progress [Type] Task Issues or PRs that have been broken down into an individual action to take

Comments

@ianstewart
Copy link
Contributor

It looks like the Query Blocks and suite of Post Blocks are currently gated behind the same experiment as Full-Site Editing. I'd like to propose that we decouple those two experiments allowing users to experiment with those separately.

I can see this being advantageous for users in at least one possible future scenario: the Query/Post Blocks being ready to leave their experimental status before the Site Editor, allowing users to create static pages with clever Post Loop layouts in the Block Editor.

@mtias
Copy link
Member

mtias commented Oct 20, 2020

This makes sense to me. There could be value in releasing some of these blocks in 5.7 as well ahead of site editing.

@simison
Copy link
Member

simison commented Oct 20, 2020

Totally! For example people who build single-page sites using page editor might find this useful.

@GlennMartin1
Copy link

Any progress on this? I'd love to be able to use the Query block while keeping experiments turned off. Perhaps 9.4?

@skorasaurus
Copy link
Member

skorasaurus commented Nov 27, 2020

Highly agree; I'm considering using the query block on my site (specifically within a page template where I want to customize the most recent posts of a particular post type but that will be just a small part of the page's content) but am not ready to go to FSE it.

@mtias mtias added the [Type] Task Issues or PRs that have been broken down into an individual action to take label Nov 27, 2020
@github-actions github-actions bot added the [Status] In Progress Tracking issues with work in progress label Dec 18, 2020
@GlennMartin1
Copy link

@mtias What's the timeframe for moving forward on this?

(hopefully soon!)

@rmorse
Copy link
Contributor

rmorse commented Apr 12, 2021

Just thought I would add on here some ideas about the query building UI - and if we decouple the this from FSE, does that introduce new use cases.

Would it be safe to say, users of FSE are advanced users, and therefor can handle more advanced query controls (and possibly need them)?

And would it be a fair assumption that blocks available for general use (ie intalled everywhere), might need to be more accessible, and possibly simpler, for most use cases (but of course, we'll still need the advanced stuff for advanced users)?

I see a query builder UI - one that in the end has most options of WP_Query - as an essential for site builders and FSE in the long run (you may disagree, I'm just thinking out loud), but I can see that being totally full on and overwhelming for most uses cases everywhere else.

Perhaps Im overthinking it - at the end of the day a Query is quite an advanced concept already... But I'm starting to lean towards the idea that this will need to fullfill two use cases:

  1. Site builders need more options and more technical query controls
  2. The current query builder UI is probably technical enough (and pretty much functional enough) as it is for a most use cases and shouldn't get much more complicated

I think this could still be captured all in one block (by having a drill down to "advanced" controls or something similar) but thought I would mention on here as I think FSE implies advanced users will be using this, and bringing it out of there would surely target another set of users.


Update: I see this was somewhat touched on here:
https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/

This is potentially too powerful for users—you can edit everything from the blocks in this block. Flag was seconded.

I'll be keeping my eyes peeled on updates around this!

@ntsekouras
Copy link
Contributor

Closing as this is tracked/handled here: #28744

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Query Loop Affects the Query Loop Block [Status] In Progress Tracking issues with work in progress [Type] Task Issues or PRs that have been broken down into an individual action to take
Projects
None yet
Development

No branches or pull requests

7 participants