Inserts a saved Theme Builder template — a section, header, footer, popup, loop card, or full page — dynamically into any page, rather than copy-pasting the same block of design onto every page that needs it. The distinction between this widget and simply duplicating a section is bigger than it first appears: a copy-pasted block is a snapshot, frozen the moment you pasted it, while this widget is a live reference — the content it displays is always whatever the referenced template currently contains, updated in real time everywhere it’s used.
Picking the template
Start by choosing the template type to filter the picker down to a manageable list — section, header, footer, popup, loop, or page — since a site with dozens of saved templates across every category quickly becomes hard to search through without that filter. From the filtered list, use the searchable template dropdown to find the specific one you want, or, if you already know its numeric ID (useful when scripting a build or copying settings between environments), paste it directly into the manual ID field instead of searching.
Why editing the original updates everywhere
Because the widget references the template by its ID at render time rather than embedding a static copy of its markup, editing the original template in the Theme Builder — changing a headline, swapping an image, adjusting a color — propagates to every single page that embeds it, instantly, with no re-publishing or manual sync step required on any of those pages. This is the same underlying pattern the Theme Builder already relies on for site-wide headers and footers, where a single header template applies across the entire site and a single edit updates it everywhere at once. This widget simply makes that same mechanism available for any arbitrary block of content you want to design once and reuse — a promotional banner that needs to appear on twelve different landing pages, a recurring "as featured in" press-logo strip, a call-to-action block that gets embedded at the bottom of every blog post template.
Performance: lazy rendering
A Lazy render toggle defers loading the referenced template’s markup, styles, and any scripts it depends on until the moment it actually scrolls into the visitor’s viewport, rather than loading it immediately as part of the initial page render. This matters most when the embedded template is itself heavy — a slider with several high-resolution images, an interactive map, a complex gallery — because loading that weight up front on every page that happens to embed it, even far below the fold, adds real time to the initial page load for content the visitor may never scroll down to see. With Lazy render on, an optional loading placeholder fills that space until the real content arrives, so the layout doesn’t visibly shift once it finally loads.
Use it for
The clearest use case is any block of content that’s genuinely meant to be identical across multiple pages and kept in sync as a single source of truth — a promotional CTA embedded at the end of every article, a feature comparison table reused across several product pages, a testimonial block that should update everywhere the moment a new review comes in. It’s a poor fit for content that’s superficially similar across pages but needs independent editing per instance — in that case, a genuine copy (via the Theme Builder’s own duplicate function, or by starting fresh) is the right tool, since this widget’s whole purpose is to keep every instance identical.
Practical tips
- Name your saved templates descriptively before relying on this widget across many pages — the searchable picker is only as useful as the names attached to what it’s searching, and a page full of "Section 1", "Section 2" entries defeats the point of a searchable list.
- Turn on Lazy render by default for anything embedded below the fold, and only disable it for content that genuinely needs to be visible immediately (an above-the-fold hero, for instance) — the performance cost of loading unseen content up front is easy to overlook until a page audit flags it.
- Before editing a heavily-reused template, check how many pages actually reference it — a change intended for one specific page can unexpectedly ripple across a dozen others if that template is more widely embedded than you remembered.