Ship content like you ship code

Editing never changes the live site directly. Changes are saved to a draft, reviewed in preview, and published when ready. When publishing, editors can compare the draft to what is live, and add a short message describing the change — or let Root AI write one from the differences.

Only people with an Editor or Admin role can publish, so contributors can prepare content that someone else approves.

Pick a date and time, and the page publishes itself. There is no need for someone to be online at midnight to flip a switch, and the schedule is visible to the whole team in the doc’s status.

A release groups many docs, and data such as a pricing spreadsheet, so they go live together. Teams build the release over days or weeks, preview it, and then publish it in one step or schedule it for launch time. Nothing in the release leaks out early, and nothing is left behind.

Publishing checks run automatically when someone publishes. A built-in check flags missing translations, and developers can add checks for anything your organization cares about: broken links, missing image descriptions, legal copy, SEO rules. Each check can block publishing or simply warn, so teams move fast without skipping the essentials.

The CMS keeps a version every time a doc is saved, and a tagged version every time it is published. Anyone can compare two versions side by side, restore an earlier version, or copy one into a new doc. Individual fields have their own history too, so one paragraph can be rolled back without undoing the rest of the page.