-
Notifications
You must be signed in to change notification settings - Fork 5
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
How to add contentOnly
editing support to a custom block
#303
Comments
Thanks for the ping. As you pointed out there is a lot of work around these features at the moment so it's definitely:
I have the following from my notes on the topic of Block Editing Mode which may be helpful to you. Block Editing ModeControls the editing behavior of individual blocks on a per-block basis, defining whether and how a block can be edited. State & Package:The state is Common selector/actions
Note: it is preferred to use the DescriptionBlock Editing Mode allows granular control over individual blocks, determining whether a block is fully editable, partially editable, or completely locked. There are three main options:
ExampleWhen switching to template-locked rendering mode, the editor automatically applies contentOnly to all blocks within the template, allowing users to edit only content attributes, such as text or images, while preventing changes to layout settings. Blocks within the core/post-content area remain in default mode, allowing full editing of the post content. |
The first draft is complete and ready for review: https://docs.google.com/document/d/12ZrWIH5rxrIdY9rOIs6CfU87EI6H0IBlmP3fm3zCRok/edit?tab=t.0 @getdave given your work on stabilizing the |
@ndiego I'll add to my todo. Just getting back to AFK and focusing on 6.7 now but will get around to this. What's your timeline here? |
I'd love to get this posted early this week if possible. I'm mainly just looking for a technical review to make sure there is nothing glaringly wrong or important info I am missing. If there is anyone else you recommend pinging, just let me know. 🙏 |
The first review is complete. Any further edits should still be added to the Google Doc, but I have proactively drafted the article (public preview). |
@ndiego I took a look and didn't notice anything obvious. Great job 👍 |
Thanks @getdave! Moving on to publication. |
Post has been published: https://developer.wordpress.org/news/2024/11/05/how-to-add-content-only-editing-support-to-a-block/ Social Post copy:
|
This is currently scheduled for November 12th on socials. |
@justintadlock, that's the date of the WordPress 6.7 release. Maybe we can move it to later in the week? I imagine there will be a lot of 6.7 posts on Tuesday. |
Ah, I forgot. It should get rescheduled. |
It's rescheduled for Thursday instead. |
Discussed in #300
Originally posted by ndiego September 3, 2024
A lot of work is being done on
contentOnly
editing. While this functionality has been around for a while, upcoming enhancements will make this editing mode commonplace, especially among new users of WordPress. Here are a few related issues/PRs:While work is being done to ensure Core blocks work as expect within this editing mode, block developers will need to make modifications to their custom blocks if they want to support this mode.
This article will detail what
contentOnly
editing is, how to apply it to blocks, and how to modify custom blocks to supportcontentOnly
editing.cc @getdave @noisysocks in case you guys have any thoughts on this article topic.
The text was updated successfully, but these errors were encountered: