Exporting and packaging Experience Builder templates
How to export a customized Aura Experience Builder template, page or theme, reuse it in the same org, and package it in a managed package for other orgs, plus what the export leaves behind and why upgrades don't change existing sites.
Apply packaging, exporting, and importing a template.
~8 min read · 7 practice questions ·
What the exam expects
- Export a customized template from Experience Builder and name what blocks the export (an out-of-date template version, permissions).
- Reuse an exported template in the same org through the Experience Creation wizard, without packaging.
- Package a standalone template, theme or page in a managed package (from a Developer Edition org) to distribute it, and predict what an upgrade does to existing sites.
- List what the export leaves out and what changes on the way (flattened subpages, renamed templates, reset list views), so the destination admin can reconfigure it.
- Export a single page or theme instead of a whole template.
Key terms: exported template (a customized Aura site saved as a base for new sites; it appears in the Experience Creation wizard); Lightning Community Template (the Package Manager component type for a standalone template); managed package (an upgradeable package that avoids naming conflicts); default page variation (the only variation an export keeps); Lightning Bolt Solution (an optional wrapper that bundles a template with apps and flows).
Key facts
- Detail
- Experience Builder, Settings, Developer, Export a Template
- Detail
- Template not on the latest version
- Detail
- Exported template appears in the Experience Creation wizard
- Detail
- Flattened to the top level in new sites
- Detail
- Non-alphanumeric characters removed; names must be unique
- Detail
- Head markup, Google Tracking ID, CSS editor styles, localized content, non-default page variations
- Detail
- Existing sites aren't updated
- Detail
- Lightning Community Template, in a managed package from a Developer Edition org
- Detail
- Appears in the New Page dialog of every site in the org
- Detail
- No template, page or theme export
Sources for this section (5)
- Export a Templatehelp.salesforce.com (opens in a new tab)
- Export and Packaging Considerationshelp.salesforce.com (opens in a new tab)
- Package and Distribute a Bolt Solutionhelp.salesforce.com (opens in a new tab)
- Export a Pagehelp.salesforce.com (opens in a new tab)
- LWR Template Limitationsdeveloper.salesforce.com (opens in a new tab)
- Why does a site built from an exported template show all pages at the top level?
- Why does a subscriber's existing site not show a banner added in an upgraded managed template package?
- What does a template named My Template #2 become when exported?
- Where does an exported page show up for the org's other sites?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Experience Cloud Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 37 lessons of the Experience Cloud Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (7 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams