Salesforce DevOps for Experience Cloud

Experience Cloud sites need manual activation after deploy. Here's what that means for release planning.

What's hard to deploy

A site's Network, ExperienceBundle, and template metadata deploy through the standard API, but the site itself doesn't go live until someone manually activates it in Setup afterward, metadata deployment alone won't publish it. Branding, navigation menus, and theme components also reference each other in ways that break if they land in the target org out of dependency order.

Where it gets hard

A deployed site still isn't a live site

Network, ExperienceBundle, and template metadata deploy cleanly through the standard API, but the site itself stays offline until someone manually activates it in Setup afterward.

Branding and navigation break out of order

Theme components, navigation menus, and branding assets reference each other, so landing them in the wrong dependency order in the target org can break the site even though every component deployed.

In practice

How Serpent helps

Serpent tracks every Experience Cloud change, template swaps, navigation menu edits, branding, as a task with full history instead of a raw metadata diff, so reviewers can see what changed and why before a site goes live. See task-based workflow in Serpent for how changes get reviewed before they ship.

Cross-team coordination dashboard in Serpent

Typical release for Experience Cloud

Task the site change
Template swaps, navigation edits, and branding updates get tasked and reviewed together, not shipped as a raw metadata diff.
Delta deploy in dependency order
Serpent resolves the order theme, navigation, and template components need to land in, so the target org doesn't end up with a half-wired site.
Activate and verify
Confirm the site is live in Setup after the deploy; Serpent's task history shows exactly what changed and why, so reviewers aren't guessing.
Roll back a single component
If a branding change breaks something, revert just that piece without touching the rest of the release.

Common questions

Experience Cloud DevOps, answered

Does Serpent activate an Experience Cloud site automatically after deploy?

No. Site activation is a manual step in Salesforce Setup on any tool. Serpent gets everything the site needs, template, navigation, branding, deployed cleanly and in the right order so activation is the only step left.

How does Serpent handle Experience Cloud's component dependencies?

Navigation menus, theme components, and templates deploy in the order they actually depend on each other, so a release doesn't land a page pointing at a menu that isn't there yet.

Can we review a site change before it ships?

Yes. Every Experience Cloud edit, template swap, navigation change, branding, is tracked as a reviewable task with full history, not a raw metadata diff.

Start free. No credit card, no install, no commitment.

Set up in under 15 minutes. No DevOps hire needed.

Start free Book a demo