You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To help showcase how folks can curate pieces of the Site Editing experience, I am opening an issue to create a Twenty Twenty-Four with locked patterns, including content only editing. Here's the documentation for the locking APIs.
We might even take this further with a playground environment where someone can view the experience as an admin who can lock/unlock vs a lower user permissions role who doesn't have access to unlock.
I'm hoping to then use this as an example in a WordPress.org/news post highlighting curation tooling and adoption pathways to help encourage adoption and raise awareness on these features alongside broader documentation updates.
The text was updated successfully, but these errors were encountered:
I dig the first pass! To help demo it, I think it would make sense to throw it into a Page in the Site Editor alongside a pattern without any locking just for comparison in experiences. We can even use the Group block renaming to name each group appropriately.
To help showcase how folks can curate pieces of the Site Editing experience, I am opening an issue to create a Twenty Twenty-Four with locked patterns, including content only editing. Here's the documentation for the locking APIs.
We might even take this further with a playground environment where someone can view the experience as an admin who can lock/unlock vs a lower user permissions role who doesn't have access to unlock.
I'm hoping to then use this as an example in a WordPress.org/news post highlighting curation tooling and adoption pathways to help encourage adoption and raise awareness on these features alongside broader documentation updates.
The text was updated successfully, but these errors were encountered: