NetworkBranding - branding parameters for the main site (does not include page variations) and need to prefix cb.Audience - Built audiences added in recent releases.SiteDotCom - Site content, binary blob autogenerated for community.CustomSite - Associated site settings XML file.We will focus here on the Community itself that is stored in the following metadata components Note here we are dealing with new API Version 44.00 Winter 19 for Metadata for APEX code, Lightning aura components are well documented and known to most developers. Our community may consist of many different metadata artifacts, VF Pages, Configs settings, Lightning Components, APEX classes, and other things.

I created this GitHub repository sf-metadata-pkg for myself as a reminder maybe it will be a useful reference. There is no full set of documentation available on metadata items until Summer 18 Metadata Coverage Report that help with APIs but not for package ANT deployments. We need to make a package.xml file for this type of deployment. Then deploy this to the target Organization - QA or Production. Our next step is to export all these customizations and development into source control, in our case it is GitHub. We start with the existing community we already built with all configurations, pages, and Lightning components, etc. That is a need that has been recognized and hopefully is coming in some later releases.įor now, we need to deal with the current state and try to deploy our Community from DEV to QA sandbox and later to Production. Understanding these requirements Salesforce is working to change the initial idea and make the Community more source-driven with metadata and DX. However, the reality of development is most processes start in DEV sandbox and are expected to move through multiple test stages like QA, UAT, and then PROD. The Production org is expected as a source of truth. Going down from PROD to other QA/UAT environment distribution model. Communities Team initially expected Enterprises will be making changes and building Community direct in Production and then move it to sandboxes using the refresh sandbox feature. īased on what I learned from Salesforce one reason it is not easy to deploy Community is its design. This an updated blog for Summer 18 & Winter 19 releases as of. Here we will demonstrate how to use ANT script and Metadata API to deploy Communities and manage source in GitHub. If you recently worked with Salesforce Communities it is not easy to deploy or move to different environments.

Setup force migration tool