Exercise 1: Editing a Reusable Block Used on 15 Pages — Possible Solution ==================================================================== WHAT ACTUALLY HAPPENS ------------------------------ The phone number changes on all 15 pages simultaneously, not just the one the site owner was editing. WHY THIS HAPPENS ------------------------------ Per this chapter, "a reusable block... stays permanently linked across every page it appears on," and "editing a reusable block updates it everywhere it's used, simultaneously." A reusable block is not 15 separate, independent copies of the same content that happen to look identical - it's a single shared piece of content that is merely DISPLAYED in 15 different places. Editing it from any one of those locations is editing the one real underlying block, and every page referencing it reflects that same underlying change immediately. WHY THE SITE OWNER'S EXPECTATION WAS WRONG ------------------------------ The site owner's expectation - that editing it in one place would only affect that one page - is exactly how an ordinary pattern behaves, per this chapter's own comparison table: "editing one instance affects only that instance." The site owner appears to have confused a reusable block with an ordinary pattern, which is precisely the mix-up this chapter's own warn-box warns about: "someone who doesn't realize a block is a reusable/synced one can make what they think is a small, one-off edit... and unintentionally change that same content everywhere else it's used." WHAT THE SITE OWNER SHOULD HAVE DONE INSTEAD ------------------------------ If truly independent, page-specific phone numbers were the actual goal, the site owner would need to either convert that specific instance to an ordinary (non-reusable) set of blocks first, or use plain, unlinked blocks for that particular page from the start rather than the shared reusable block, since a reusable block is designed specifically for content meant to stay identical everywhere. WHY THIS WORKS AS AN ANSWER ------------------------------ It states the actual outcome plainly, explains the underlying mechanism (one shared block displayed in many places, not many independent copies), identifies exactly which chapter concept the site owner confused it with, and names the concrete fix.