Documentation

Updating pages when the blueprint changes

Change the blueprint and forty pages are suddenly behind it. Sync brings them up to date with one unbreakable rule: a block you have edited is yours, and nothing overwrites it. Ever.

How the plugin knows what you edited

At generation time every top-level block’s content is fingerprinted. When you edit a generated page, the edited block no longer matches its fingerprint and is marked detached — permanently yours. Everything still matching is managed and safe for sync to update. There are no hidden markers inside your content and nothing to clean up; the bookkeeping lives in page meta.

What a sync does

  • Managed blocks are rewritten from the new blueprint, with that page’s tokens and variants resolved fresh.
  • Detached blocks are kept exactly as you left them.
  • A block you deleted stays deleted — sync never re-adds it.
  • Blocks newly added to the blueprint are added to the page.

Where you run it

Three places, all explicit — there is no silent background rewriting:

  1. The Sync screen (Local Pages → Sync) lists every page behind its blueprint with a side-by-side diff of exactly what would change, and a per-page Apply.
  2. Inside the editor, a “Blueprint update” panel appears on any behind page, summarises how many regions would update and how many of your edits stay untouched, and applies in place.
  3. The command line: wp lpe sync lists behind pages; wp lpe sync --page=ID applies one; --all queues the lot (Pro).

After any sync the page is re-scored automatically, so the Quality screen reflects the new content within moments.

Next: Schema, sitemaps and the command line.