# Variations Beat New Blocks for Shipping Optional Behavior ## Claim Shipping a new capability as a variation on an existing block, instead of as a wholly new block, lowers the cost of trying it because users can switch modes without losing their existing settings. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when the new behavior shares an attribute shape close enough to the existing block that switching doesn't require re-entering configuration. - Breaks when the data model diverges enough that switching would silently drop attributes — at that point a genuinely new block, with its own migration path, is the honest choice. - Doesn't claim variations are always right — only that they lower adoption friction relative to a new-block launch when the underlying capability fits. ## Evidence Gutenberg 23.6 shipped a Dynamic Gallery mode as a variation on the existing Gallery block rather than as a new block in the inserter. A user can toggle from hand-picked images to post-attached dynamic media, and back, without losing their existing gallery settings — the switch is reversible and low-stakes. A new block would have required users to discover it separately in an already-crowded inserter, decide to switch, and re-configure from scratch, with no easy way back. ## Links - [[3. Resources/Permanent Notes/Developer-Tool Adoption Tracks Cognitive-Load Reduction Not Feature Count]] — extends: variations are a specific instance of the general pattern — adoption tracks removed overhead (here: reconfiguration cost), not raw feature count - [[3. Resources/Permanent Notes/Reproducible Environments Encode Repeated Setup as Config]] — contrasts: that note is about capturing setup as portable config across environments; this one is about avoiding the setup cost entirely by reusing the same attribute shape - [[3. Resources/MOCs/DevRel MOC]] — applies-in: block/API design choices that lower discovery and reconfiguration cost are the same class of decision DevRel evaluates for any developer-facing surface ## Tests / falsifiers - Compare adoption rate of a capability shipped as a variation versus a comparable capability shipped as a new block in the inserter, controlling for how prominently each is surfaced; if adoption rates are similar, the friction-reduction claim is weaker than stated. - Find a variation that DID cause silent attribute loss when switched — that would show the "shared attribute shape" precondition matters as much as the claim implies, and wasn't just a theoretical caveat. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Full Document Contents/Articles/What’s new in Gutenberg 23.6 (July 22, 2026)]] — the Dynamic Gallery variation (#78796) and its settings-preserving toggle.