You create a Lightning Bolt Solution by exporting a customized Experience Builder site and bundling it for distribution. This is a feature configuration done in Setup and Experience Builder, not a single record you save. The high-level path below mirrors the Salesforce Help flow.
- Build and customize the site
In Experience Builder, configure the template, theme, pages, and components until the site reflects the industry pattern you want to reuse.
- Export the customized assets
Use the export options to capture the customized template, theme, and pages as reusable building blocks for the solution.
- Add flows and apps
Attach the relevant flows and any custom Lightning apps so the solution delivers automation and functionality, not just layout.
- Package and distribute
Bundle the solution into a managed or unmanaged package, then optionally upload it to AppExchange to share or sell it to other orgs.
The label that identifies your Lightning Bolt Solution to admins who install it. Choose something that signals the industry or use case.
The base template, theme, and pages you export. Including a template is optional, but most bolts ship one so installers get a ready-to-run site.
The business process flows you add so the solution carries its guided automation, not just static pages.
Managed or unmanaged, depending on whether you plan to maintain and version the solution or let installers edit it freely.
- Including an Experience Builder template is optional, so confirm yours is actually exported if installers expect a full site.
- A packaged bolt does not auto-update in target orgs. Plan versioning and communicate upgrades, or installers drift onto stale configurations.
- For brand new builds, weigh a standard Experience Cloud template or an Industry Cloud first, since both are maintained while the bolt brand is legacy.