Directly from wp_posts.post_content parsed with WordPress's parse_blocks() API. SleekView extracts the list of themeisle-blocks/* block names found in each post and exposes that list as a real column, so chart cards can group by block name like any other field. No export, no shadow copy.

Yes. Group a Donut or Bar card by the parsed block name and SleekView ranks Otter 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 themeisle-blocks/posts-grid before a query argument changes in an Otter update.

Group an Area or Line card by post_modified truncated to week or month, aggregated by Count, scoped to posts that carry themeisle-blocks/* 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 Otter 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.

Yes. The parsed block column lists every block name found in post_content, core blocks and themeisle-blocks/* blocks side by side. Filter to posts that contain both themeisle-blocks/* and specific core blocks to map the overlap, useful before swapping an Otter block for a core equivalent.

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 themeisle-blocks/* block) and open the row in the block editor from there. Inline edits route through the standard WordPress update path.

Otter Blocks 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 Otter already writes, so the plugin keeps owning the block library and the chart view owns the cross-site summarisation.