Updating curation document to include content lock ability #44908
Conversation
Building off of the launch of this new functionality in 6.1, this updates the curation resource to include information about content lock ability: #43037
annezazu
requested review from
ajitbohra,
ryanwelcher,
juanmaguitar and
fabiankaegy
as code owners
|
Resolved all of the latest comments. Could I get additional reviews and, potentially, approvals? Of note, there's some discussion around implementing this on the dev note: https://make.wordpress.org/core/2022/10/11/content-locking-features-and-updates/ I might need to hold off on merging these doc updates depending on where things land. |
|
@ryanwelcher could you review this by chance? The feature is going to be in for 6.1 and I'd like to ensure the docs are ready. |
|
Throwing another thought out there about "content-only" editing: The phrasing is obviously weird because each of the other options refer to what they are locking. However, this particular option refers to what it allows. From a development perspective, I see this more as a "design locking." What we're actually doing here is locking down the design tools. It's a bit late to change |
|
Hmm. Thank you for the insights @justintadlock -- is this a blocker in your mind? I'm wondering if we can proceed as is considering the dev note and a "close enough" feeling. If you feel really strongly, happy to update though as I do not :) Curious what @richtabor thinks too. |
No strong feelings about it. Really, I was just making a note of this while the thought crossed my mind. |
There was a problem hiding this comment.
I also agree with the larger sentiment that the name still isn't ideal and I quite like the suggestion that @justintadlock posted. But I find this documentation update very valuable and should be merged now ahead of the 6.1 release to ensure we cover it in our documentation.
We can always follow up with additional improvements going forward.
What?
Building off of the launch of this new functionality in 6.1, this updates the curation resource to include information about content lock ability: #43037 While there is currently documentation in place https://developer.wordpress.org/block-editor/reference-guides/block-api/block-templates/#locking this rounds out the current resources to provide practical examples, explain the benefits, and properly align it with other similar methods.
@richtabor thanks to your excellent article on the topic and your great feedback around naming, I'd love to have a review from you on this if you have time. I'm personally happy to fully roll with "content only editing" but wanted to keep it closer to what it was implemented as for now.