DevXMachina
Menu
EN RO
EN RO

Operational workflows

Use Cases

DXM Block Toolkit is most useful when a vague content question needs to become a source-backed worklist, a content-specific change scope, a validated impact review, or a previewed replacement batch. These workflows show how indexing, source drill-down, block-content filtering, and Refactor fit together in 2.0.0.

Content changes

Content Scope

Which exact pages still contain a CTA, disclaimer, copy fragment, or similar content variant that needs review, updating, or replacement?

  • How it helps: Start from block inventory, open View sources for the repeated block, then narrow the source list by block content so only the relevant wording variant or content pattern stays in scope.
  • Why it fits: Block-content filtering defines the exact scope of a content change. When that scope needs controlled execution, it can move into Refactor.
  • Output: A filtered source list or CSV export that can become a worklist for review, updates, replacement planning, QA, or handoff.
Read related docs
Sources modal showing search, filters, export controls, and exact source rows in DXM Block Toolkit.

Content Scope

Sources modal showing search, filters, export controls, and exact source rows in DXM Block Toolkit.

Redesign impact

Redesign impact review

Will this redesign touch a small set of sources or a broad slice of the site?

  • How it helps: Use the block inventory to identify affected blocks, then inspect source rows across posts, templates, reusable content, and navigations before design changes land.
  • Why it fits: Inventory totals, source counts, and filtered source evidence make it easier to separate a contained change from a broader surface area.
  • Output: A source-backed impact list for planning, stakeholder review, or release notes.
Read related docs
Sources modal filtering block source rows by class token for redesign impact review.

Redesign impact review

Sources modal filtering block source rows by class token for redesign impact review.

Safe bulk replacement

Safe bulk block replacement

How do we replace one block variant or old copy fragment across many sources without editing them one by one?

  • How it helps: Start from a fresh scan, configure the target and scope in Refactor, add block-content filters when only one wording variant should change, generate a read-only preview, then apply only the changed rows you actually want to update.
  • Why it fits: Refactor separates Configure, Preview, Apply, and Rollback so the batch stays deterministic and reviewable, while content-aware scope keeps the replacement from becoming a blind content write.
  • Output: A previewed replacement batch with explicit apply and rollback checkpoints before content changes are finalized.
Read related docs
DXM Block Toolkit Refactor Review step showing the configured batch summary before apply.

Safe bulk block replacement

DXM Block Toolkit Refactor Review step showing the configured batch summary before apply.

Mode selection

Shared definition vs reference updates

Should we change the shared definition itself, or only replace where it is referenced?

  • How it helps: Choose entity definition when the shared pattern, template part, or navigation itself should change everywhere. Choose entity reference when only matching sources should stop using that shared entity.
  • Why it fits: Refactor keeps block instance, entity reference, and entity definition modes separate so preview, apply, and rollback stay explicit.
  • Output: A clearer change boundary before work starts, plus operation history that supports validation, rollback, and follow-up.
Read related docs
DXM Block Toolkit Refactor Target step showing mode selection for a shared definition or shared reference update.

Shared definition vs reference updates

DXM Block Toolkit Refactor Target step showing mode selection for a shared definition or shared reference update.

Next step

Tie the audit to the next piece of work.

View pricing Read the bulk replacement guide Read Refactor docs