Use preview only for customer editing in CloudCannon. Keep the existing Site after publishing. Customers save, preview and publish through a pull request to main; successful checks are required, with no extra human approval.
Developers start branches from main and open PRs directly to main. Use the PR deploy preview for review. After developer changes reach main, use CloudCannon's Update from Publish Branch before the next publication.
Validate checks changed code formatting, the project's checks and its build. CloudCannon owns content formatting. CodeRabbit reviews eligible authors; its native skipped status allows CMS publications. Argos uses its native skipped build for ordinary content changes without uploading screenshots. Code and mixed changes still run the visual tests. Content-only merges do not refresh the Argos baseline, so a later developer comparison can include earlier CMS changes.