What does Theme Builder control?

It controls global templates such as header, footer, and reusable sections across the website.

Can templates target only specific pages?

Yes. You can use include/exclude rules and template priority settings for scoped assignments.

How do I avoid template conflicts?

Set one default global template per role and use higher priority only where exceptions are needed.

Help4 Theme Builder Guide

Use Theme Builder to control global header/footer and reusable template parts across the site.

Global Header & Footer

Create/update header and footer templates.
Assign scope to entire site or specific page types.
Use include/exclude rules for targeted pages.

Template Conditions

Choose role: header, footer, section, popup.
Set scope: entire site, include list, exclude list.
Use priority values to resolve template conflicts.

Best Practice

Keep header nav consistent and lightweight.
Use reusable templates for repeated sections.
Verify each template at desktop and mobile breakpoints.

Build A Site Shell In The Right Order

Start with the global header and footer because those parts frame every normal page. Add the logo, navigation hierarchy, contact route, primary call to action, legal links, and customer support path before creating special page exceptions. Then build a default page shell, a canvas landing-page shell, a 404 template, and any archive or single-content layouts the site actually uses.

Create each reusable template and give it a name that explains its role.
Assign the normal header and footer to the entire site.
Add narrower include rules only for pages that truly need a different shell.
Use exclusions for checkout, funnels, or canvas pages that intentionally remove normal navigation.
Set priorities only when two valid rules can match the same request.

Menus, Dropdowns, And Mobile Navigation

Use the real WordPress menu hierarchy for parent and child links so desktop dropdowns and the mobile menu share one source. Test the pointer path from a parent item into its submenu, keyboard focus, touch opening, menu close behavior, and the space between the trigger and submenu. A dropdown should not disappear while the visitor is moving toward it.

Before Publishing A Template Change

Preview the homepage, one normal page, one long page, one conversion page, and the 404 route. Check desktop and phone widths for clipped content, duplicate headers, missing footers, unreadable contrast, broken fixed positioning, and links hidden behind the mobile menu. Clear page/CDN caches only after the saved template and assignment rules are confirmed.

Troubleshooting

If a template does not appear, confirm it is published, its role is correct, and its include/exclude rules match the current URL. If two templates appear, review overlapping conditions and priority values. If the canvas has a white frame, inspect the page layout and HTML block wrapper controls for background and padding before adding site-specific CSS.

View Starter Templates Builder Guide

Theme Builder Support