-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Enabling Full Site Editor blocks in classic themes #28744
Comments
There's an issue about this for the Query Block at #26316 |
I would find the post excerpt useful. |
All in all, it seems we kind of need most blocks except the "template part" block, which only makes sense in a Site Editing context. |
As far as the Query block is concerned, we need to include all individual block variations built on top of the main Query block (e.g., "Posts block", "Pages block", which are the ones that end-users will be facing in the inserter, as well as Query block patterns (#28891) |
Updated the issue to exclude the "comments" related ones, since those make more sense for |
Added to the list the 3 new theme blocks that landed in 10.3 (Login/Out, Term Description, and Archive Title) for tracking purposes, although they don't seem to make a lot of sense with the Landing page scope of 5. Moreover, without #30679 the archive blocks can be used in any template even if they are not meant to. |
Added the Login/Out as it can indeed be useful if added to a Widget Area thanks to the Widgets Editor project. |
Reopening because there are some blocks left that we'd want to reconsider.
|
The postAuthor block was not included in WP 5.8 #31983 |
With the upcoming inclusion of Full Site Editing in WP 5.8, many of the site-editing-oriented blocks currently enabled only with FSE should also be available to use in classic themes. The goal of this issue is to list all these blocks and determine whether each of them should also be enabled in non-FSE contexts.
These blocks will be categorized in the block inserter as defined in #26639
The text was updated successfully, but these errors were encountered: