`dxb diff` shows what would change on your live documentation site if you pushed right now. It compares your local files to the published state and reports added...
`dxb diff` shows what would change on your live documentation site if you pushed right now. It compares your local files to the published state and reports added...
dxb diff shows what would change on your live documentation site if you pushed right now. It compares your local files to the published state and reports added, modified, and removed pages — so you publish with confidence and never push a surprise.
Run a diff
From your project root:
dxb diffThe output summarizes every pending change — new pages, modified pages, and removals — across your content and docs.json.
Diff a single path
Limit the diff to one docs-relative path:
# One page
dxb diff get-started/quickstart
# A folder/space
dxb diff guidesMachine-readable output
Use the global --json flag for CI tooling that posts diff summaries on pull requests:
dxb diff --jsonDiff vs. status
These answer related but different questions:
dxb status— a quick summary of whether local and cloud are in sync.dxb diff— the detailed, page-by-page view of what differs.
Use status for a glance; use diff to review before publishing.
A safe publish loop
dxb lint --strict to catch errors.
dxb diff to review exactly what will change.
dxb push --publish once the diff looks right.