DA Live version comparison can obscure section boundaries

Version comparison is useful only if it shows changes that alter the page. An open DA Live issue reports that section breaks are omitted from the comparison view. A recent tracking issue keeps comparison work visible. A reviewer who checks only changed words could restore a structurally different page without noticing its layout or block grouping.

Define what a meaningful diff includes

For a page with multiple sections, capture two versions that differ only by a section boundary, then compare in the current DA Live interface. Inspect text, section starts, block order and resulting rendered layout. Record the exact version identifiers. This is a narrow acceptance test for your tenant, not an assumption that every comparison loses structure.

Pair the diff with a rendered review

The DA Live version API and release notes describe version history and restore capabilities. Before a high-stakes rollback, open the candidate version in a preview or isolated copy and walk through each section boundary and component. Have the page owner confirm the expected layout, especially around forms, calls to action and legal text.

Preserve a rollback record

Save the current version ID, proposed target version ID, reason for restore, screenshot of each page state and reviewer name. If the comparison omits a structural change, report that precise gap with a minimal document. Do not treat a successful restore action as evidence that the restored page is correct.

Adovo’s view

History is useful only when it preserves meaning. A section boundary changes how a reader moves through a page, even if no sentence changes. Review the page people will see before using a version diff as approval.