Pattern

Patterns can package common compositions such as heroes, calls to action, pricing sections or content layouts while leaving the inserted blocks editable. In practical terms, Pattern belongs to the publishing and site-management layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.

The common mistake is to use Pattern as if it also meant Template. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Know whether the pattern is synced or unsynced because that determines whether later edits propagate to existing uses.

In day-to-day work, Pattern matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.

A pattern can provide a reusable hero or pricing layout made from ordinary blocks that editors can insert quickly. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.

Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.