DevXMachina
Menu
EN RO
EN RO

Blocks & Sources

This is the main workflow when you need to answer where a block is used and how much cleanup, replacement, or redesign work it could touch. Start in block inventory, then open exact sources when you need evidence you can act on.

What block inventory shows #

  • Each row is grouped by block name, such as core/paragraph.
  • Instances counts how many indexed block occurrences were found across the scanned source set.
  • Sources counts how many distinct indexed sources contain that block.
  • Together, those numbers help you separate broad usage from repeated use in a smaller number of sources.

When to use filters first #

On larger sites, narrow the table before you open drill-down. Use the available search, source-type, or status filters to isolate the slice of content you actually need to review.

  • Use source type filters when the question is editorial versus theme-related.
  • Use status filters when drafts or unpublished work should be excluded.
  • Sort or search first when you are comparing a known block against a large inventory.

What "View sources" gives you #

Source drill-down is where the inventory becomes actionable. It answers where exactly is this used instead of only how much of it exists.

  • Exact indexed pages, posts, templates, or other indexed sources.
  • Source context you can inspect before cleanup or replacement work starts.
  • Exportable evidence for QA, reporting, and migration handoff.

Best-fit workflows #

  • Estimate cleanup or replacement scope before touching production content.
  • Verify whether a redesign affects only a few sources or a broad slice of the site.
  • Confirm that a deprecated block is still present before you schedule remediation.
  • Give QA or delivery teams a source-backed list instead of a verbal estimate.

Continue with Content Coverage if you need to distinguish Blocks from Patterns, Template Parts, and Navigations, or move to Exports once you are ready to hand findings off.