Theme Builder Conditions and Reuse

Step 1: Choose the Template Role
Open Theme Builder and choose the job first: header, footer, page shell, post, archive, search, 404, popup, or canvas page. Giving the template one clear role keeps the same layout from appearing twice or being inserted once for every archive result.

Step 2: Build Reusable Structure
Open the template in Studio and insert only the reusable structure that belongs to its role. Keep page-specific copy in the page layout or dynamic fields. A global header or footer should not quietly contain content meant for one campaign or one customer.

Step 3: Set Narrow Conditions
Set scope, content type, includes, excludes, and priority as narrowly as the job requires. Start with a draft assignment, confirm a representative route, and avoid competing templates with the same priority. Specific exclusions should win when a checkout or canvas page needs a different shell.

Step 4: Test Assigned Routes
Check Studio and public output on a normal page, a matching singular item, an archive, search, 404, and mobile navigation where relevant. Confirm exactly one assigned template renders, required assets load, interactive controls work, and an unrelated route remains unchanged.
