We've activated ExperienceBundle metadata for communities. However, there's a known issue with it that is preventing us from actually being able to deploy using that metadata. In order to avoid having to make manual changes until they fix it, can I revert back to just using SiteDotCom in my deployments?
The documentation doesn't seem to be very clear on this
After you enable ExperienceBundle, Metadata API calls (retrieve and deploy) and Salesforce DX operations (pull, push, and status) use the ExperienceBundle type instead of SiteDotCom.
However, it doesn't seem to imply there's anything stopping us from specifying SiteDotCom to pull and deploy from the API. Only thing is, I won't really be able to tell if it's actually kept up-to-date with community changes since activating the new metadata type.
I pulled the SiteDotCom metadata and the lastModifiedDate on the Community I'm looking at seems to imply it hasn't changed with our recent changes which makes me think it's no longer an accurate representation.