Loading

Deploy Experience Builder Sites

發佈日期: May 3, 2023
描述
Deploying the Experience Cloud site from one environment to another is not fully automated. There are additional steps to take when moving the site components. The extent of this effort will depend on your site and what you’ve built.

This article is a guideline for site deployment and provides an idea of what to expect and what to plan for when deploying a site from development to QA and then on into production.

Tool Selection:
The first three options above all use the metadata API and depend on the package.xml content for extract and deployment. There are essentially 3 metadata types that define a site:
  • Network - Mostly Community Management configuration elements (Reputation, Membership)
  • CustomSite - Domain and page setting information (indexPage, siteAdmin, URL)
  • SiteDotCom - a binary file of your community layout, its the same file produced by the Site.com Export

The Exporting a Site.com Site  & Overwrite option is manual and requires you to log in to your source org Site Studio and select the Export This Site option from the gear icon on the far right. This will export the site in .site file format for you to save to local file storage. You would then need to perform the import of this file in your target org by again going to the Site Studio and using the Overwrite This Site option and point to the .site file. Details can be found in Importing a Site.com Site. 

Change sets can be used to move Experience Builder sites and Salesforce Tabs + Visualforce Sites between orgs that have deployment connections.
 
解決方案


Migrating Experience Builder Sites consists of migrating custom Lightning components and site pages.

 
  1. Custom Lightning Components: These can be deployed using standard metadata api with the tools mentioned above.
  2. Export of Sites (Pages/Assets): This can be done in two automatic ways:
  1. Using Site.com, you can Export the entire site from the source org and then overwrite it in the target org.  
  2. Using site metadata tags, move the sites.
Note: The most reliable option when you have object pages is to build the site manually or export the site by deleting the object pages in the source org and then create these pages in the target org manually.


In order to deploy new sites from any org into any other org, here are the suggested steps:
  1. Manually create the new site in the target org with the same parameters (domain, name, template).
  2. Use metadata to deploy the network and custom Site metadata types into the target org.
  3. Use metadata to extract the siteDotCom metadata type, or use the Site.com Export This Site option from your source org.
  4. Use metadata to extract all ApexClass and AuraDefinitionBundle metadata types that are used by Lightning Components in your site from your source org.
  5. Deploy all ApexClass and AuraDefinitionBundle metadata types that are used by Lightning Components in your site to your target org.
  6. Manually use the Overwrite This Site from Site.com in your target org.
  7. Remember to Publish Changes from Site.com after the import of the .site file.
  8. Access the Experience Builder in your target org and now perform the side-by-side comparison of each page and correct as needed.
 
Typical community project migration consists of: 

1. Platform Metadata    
  • Custom Objects
  • Custom Fields
  • Page Layouts
  • Custom Lightning Components
  • Reports/Dashboards
  • Apex Classes

Standard metadata tools can be used to migrate these artifacts. 

2. Site (Pages)
  • Modified Standard Pages
  • New Custom object pages
  • New standard content pages
  • General Builder settings
  • Builder images

Site pages either can be migrated using the metadata API or Site.com or by manually creating the pages.

3. Settings and Data 
  • Administrative Settings
  • Topics
  • Moderation Criteria

Go to the Community Management console and update your administrative settings, topics, moderation criteria, etc.; as these do not carry over automatically.
知識文章編號

000384878

 
正在載入
Salesforce Help | Article