Exercise 2: When a Pattern Beats a Reusable Block — Possible Solution ==================================================================== THE GENERAL RULE, PER THIS CHAPTER ------------------------------ Per this chapter's own comparison table, a pattern is "best for: a layout you want to reuse but customize differently each time," while a reusable block is "best for: content that must always stay identical everywhere." The deciding question is whether every future use of the content is supposed to independently diverge over time, or whether every use must always match exactly. A NEW EXAMPLE: A "TEAM MEMBER PROFILE" LAYOUT ------------------------------ A company site wants a consistent visual layout for introducing each team member on an "About the Team" page - a photo, a name heading, a job-title line, and a short bio paragraph, arranged the same way every time. This is a strong candidate for a pattern rather than a reusable block: the LAYOUT should stay consistent (same visual structure for every team member), but the actual CONTENT - each person's specific photo, name, title, and bio - is obviously meant to be completely different for every individual team member. WHY A REUSABLE BLOCK WOULD BE THE WRONG CHOICE HERE ------------------------------ If this were built as a single reusable block instead, per this chapter's own mechanism, editing any one team member's bio would change that same bio text on every other team member's profile too - clearly not the intended behavior, since each person's information is meant to be independent. WHY A PATTERN IS EXACTLY RIGHT HERE ------------------------------ Per this chapter, "a pattern, once inserted, becomes an ordinary, independent set of blocks you can freely edit without affecting anything else." Inserting the "Team Member Profile" pattern once per team member gives every profile the same consistent starting layout, while each inserted copy can then be filled in independently with that specific person's own photo, name, title, and bio, with zero risk of one team member's edits leaking into another's. WHY THIS WORKS AS AN ANSWER ------------------------------ It restates the chapter's own general deciding question, applies it to a genuinely new example not already used in the chapter (team member profiles rather than book reviews or newsletter signups), and explains concretely why a reusable block would produce the wrong behavior in this specific scenario while a pattern produces exactly the right one.