To improve maintainability and reduce code repetition in Salesforce B2C Commerce ISML templates, developers use two primary techniques. First, local template includes (achieved with the tag) allow for breaking down a page into smaller, reusable components like product tiles or carousels. Second, template decorators (using ) define a common page structure (e.g., header, footer, main content area), which other templates can then populate using tags. This decorator pattern eliminates the need to repeat the entire page skeleton on every template, centralizing the layout logic and significantly improving maintainability.

1. Salesforce B2C Commerce Cloud Documentation

isinclude Tag: "The tag includes the output of another template in the current template... A local include is when the included template is in the same instance as the including template." This supports the use of local includes for modularity. (Reference: Salesforce B2C Commerce Developer Guide

"ISML Tags" section

isinclude syntax).

2. Salesforce B2C Commerce Cloud Documentation

isdecorate Tag: "The tag lets you decorate a template with another template. The decorating template can provide a common frame or layout for one or more templates... The template to be decorated uses tags to replace placeholders in the decorator template." This directly supports the decorator pattern for reducing layout repetition. (Reference: Salesforce B2C Commerce Developer Guide

"ISML Tags" section

isdecorate syntax).

3. Salesforce B2C Commerce Cloud Documentation

Reusing Code in Templates: "B2C Commerce provides two ways to reuse code in templates: includes and decorators... Includes are useful for smaller

repeated page elements... Decorators are useful for defining the look and feel of a set of pages." This source explicitly names these two techniques as the primary methods for code reuse. (Reference: Salesforce B2C Commerce Developer Guide

"Develop for the Storefront" -> "Templates" -> "Reuse Code in Templates").