Detach a synced pattern when one page needs an independent variation of a shared section. The detached blocks can then be edited locally, while other pages continue to use the original synced pattern.
IN THIS ARTICLE
01 Confirm the intended scope
Check whether the requested change belongs on every page or only this one. Correcting a shared telephone number normally belongs in the original pattern. Replacing a generic call to action with a page-specific destination may justify detaching that occurrence.
Once detached, the section stops receiving future changes to the original pattern. Record that exception if several people maintain the site, especially for contact information, terms or campaign content that is updated regularly.
02 Make the local copy
- Open the page and use List View to select the synced pattern wrapper, not just a paragraph inside it.
- Confirm the pattern's name and that it is the occurrence you intend to change.
- Use the available Detach or Detach pattern action. If the action is unavailable, review permissions and any pattern lock rather than deleting the original.
- Edit the resulting local blocks, then save the page. Review the save panel to ensure an unintended shared-pattern change is not included.
How do I confirm that the detached pattern is independent?
Open the edited page and another page that still uses the original pattern. Confirm that only the intended page shows the new wording or destination. Check layout at different widths because the local variation may be longer than the shared version.
If the other page also changed, stop and inspect whether the original was edited before detachment. Restore the shared original carefully and preserve the desired local text before making further changes.
03 Rejoin the shared pattern later
To return to the standard section, remove the local copy after preserving anything valuable and insert the existing synced pattern again. Recreating a similar-looking Group does not reconnect it automatically.
Do not delete the pattern from the management library merely to make this page independent. That is a global action with different consequences. For many pages needing the same new variation, consider a second clearly named synced pattern instead of producing a large collection of untracked exceptions.