An unsynced pattern provides a reusable starting layout whose inserted copies can be edited independently. It suits repeatable structures such as a staff profile or service introduction where the design is similar but the actual content differs.
IN THIS ARTICLE
01 Prepare a clean starting point
Build the layout with meaningful headings, sensible spacing and placeholder content that editors can recognise. Avoid including real confidential details, expired offers or links that would be easy to overlook. Decide which images are genuinely reusable and which should always be replaced.
02 Save the layout as a pattern
- Select the relevant blocks, preferably inside one clear container when the design forms a complete section.
- Open the block options and choose Create pattern.
- Give it a descriptive name and leave synchronisation disabled for an independent layout.
- Insert the saved pattern on a new draft and replace its sample text, images and destinations.
- Preview and save the draft, checking that the original pattern and other inserted copies remain unchanged.
Do edits to an unsynced pattern update existing copies?
Editing the saved unsynced pattern changes the starting material for future insertions. Existing independent copies do not automatically receive that edit. If a business detail must stay identical across pages, put that detail in a synced component or use a different content model instead of relying on an unsynced layout.
Theme-level typography or global styles can still affect many pages, including independent pattern copies. Independence refers to the inserted block content, not immunity from every design change on the site.
03 Verify an editorial handoff
Ask another editor to create a draft from the pattern and identify what they should replace. If the result repeatedly contains forgotten placeholders, simplify the pattern or add a short internal checklist outside the public content.
If the inserted section appears locked or offers only limited editing controls, inspect the pattern's editing mode and permissions before assuming it is synced. Use the supported editing action to expose the intended controls. Keep a small organised pattern library so editors can find the approved layout rather than choosing from many almost-identical versions.