Publishing · Branches & publishing

Working alongside developers

Editors and developers can work at the same time. Every publish — and every Go live — gets the latest version first, then sends your changes. So if a developer has changed the site’s code (a layout, a style, a dependency) while you were editing, your publish simply goes through on top of it.

The only time Orbit stops is when someone else changed the same page you’re publishing, in a different way. Then you see both versions side by side and choose which to keep (or combine them by hand) — before anything is published. If both sides made the same change, there’s nothing to choose and Orbit just carries on. This works even for a change Orbit saved while you were offline and hadn’t sent yet.

The Get latest badge only counts content changes, so a developer’s code update doesn’t ask you to do anything.

If a developer changes something straight on the live site, Unpublished lists it under Changed on the live site: the preview site has an older copy, so it can’t be published over the newer one. A developer clicks Bring in live’s changes to copy the newer version to the preview site (nothing changes on live).