Osier

== Description ==

Core block locking is all or nothing per block, which means a locked layout is also an uneditable one. Osier separates the two: an editor can rewrite the heading and swap the image, and cannot delete the container or change its alignment.

Rules are attached to patterns rather than to individual blocks, so a pattern inserted next month inherits them without anyone remembering.

Locks are per role. An administrator gets an unlock affordance and a warning; an author does not see the option at all, which is kinder than showing a control that fails.

== Screenshots ==

Numbered the way they ship in /assets/. Click any one to see it full width.

== Installation ==

• Install and activate the plugin.
• Open a pattern in the editor and set which parts are structural.
• Assign the rule to roles under Settings → Editing.

Locks are editor affordances, not security. Anyone with the capability to edit can still edit via the API, and the readme says so.

== Frequently asked questions ==

Is this security?

No. It prevents accidents. Someone determined can still change anything they have permission to change.

Synced patterns?

Supported, with the lock rules travelling with the pattern.

== Changelog ==