Directly from wp_posts.post_content parsed with WordPress's parse_blocks() API. SleekView extracts the list of stackable/* and legacy ugb/* block names found in each post and exposes them as a real column, so chart cards can group by block name like any other field.

Yes. Group a Donut or Bar card by the parsed block name and SleekView ranks Stackable blocks by how often they appear across the site. Filter further to a single block when an audit focuses on, for example, every page using stackable/card before a card variant changes in an update.

Yes. The parsed block column exposes both namespaces, so a Donut or Bar grouped by namespace shows how much of the site is still on the legacy ugb/* blocks versus the current stackable/* blocks. The split makes migration prioritisation a chart, not a manual audit.

Group an Area or Line card by post_modified truncated to week or month, aggregated by Count, scoped to posts that carry stackable/* blocks. The curve shows when those pages are being touched, useful for tracking campaign cadence and stretches of zero activity.

Yes. View-level filters such as post type, author, status, date range, and parsed Stackable block name apply to every chart card on the dashboard. One saved configuration drives both the audit table and the chart view, so reporting and housekeeping stay aligned.

Yes. The expensive operation is calling parse_blocks() on every post_content. SleekView caches the parsed block name list per post so subsequent chart renders hit a lightweight indexed column instead of re-parsing the block markup, even on sites with tens of thousands of posts.

Charts are read-only summaries by design. To act on a chart insight, switch to the audit table filtered to the same slice (for example, every page using a specific stackable/* block) and open the row in the block editor from there. Inline edits route through the standard WordPress update path as usual.

Stackable does not ship a reporting screen for block usage, so there is nothing to replace. SleekView Charts adds a reporting surface on top of the post_content markup Stackable already writes, so the plugin keeps owning the block library and the chart view owns the cross-site summarisation.