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
Synced patterns are convenient as the design customization can be carried over to all the places that the pattern/block's used. But, if there's a need to change the underlying block content, there isn't a way to do that without detaching the pattern, thus losing the sync'd design.
Here's an example where a two columns block is published as a pattern, and when it's reused in another place, the only way to check the underlying content is by detaching:
Screen.Recording.2024-12-18.at.6.50.06.PM.mov
What is your proposed solution?
One of these two solutions would be ideal:
Ability to change the underlying block content without having to detach
Put the block back together into the same pattern, only if the content changed (without design changes)
Or perhaps patterns aren't designed for this use-case, in which case, is there a better way to approach this need?
What problem does this address?
Synced patterns are convenient as the design customization can be carried over to all the places that the pattern/block's used. But, if there's a need to change the underlying block content, there isn't a way to do that without detaching the pattern, thus losing the sync'd design.
Here's an example where a two columns block is published as a pattern, and when it's reused in another place, the only way to check the underlying content is by detaching:
Screen.Recording.2024-12-18.at.6.50.06.PM.mov
What is your proposed solution?
One of these two solutions would be ideal:
Or perhaps patterns aren't designed for this use-case, in which case, is there a better way to approach this need?