Blocksy Pro extends the free Blocksy theme with Content Blocks, which are reusable layouts stored as a custom post type (typically ct_content_block). Each block carries metadata for hook placement, display conditions (URL patterns, post types, taxonomies, user roles), and priority that together determine where the block renders on the front end. The default WordPress admin lists Content Blocks but hides hook, condition, and priority details inside per-block settings panels.

SleekView reads every ct_content_block post plus its metadata and joins them into one queryable table with hook, condition summary, priority, status, and last edited as proper columns. Filter to active blocks on a specific hook to audit coverage. Filter by display condition to see which blocks target which URL patterns or post types. Sort by priority to spot conflicting blocks targeting the same hook.

Inline edits to status, hook assignment, and priority write through standard WordPress update calls so Blocksy's render pipeline picks up the changes on the next request. The block content (Gutenberg block markup in post_content) stays editable in the block editor where it belongs.

Blocksy Pro's Content Blocks are one of the most flexible hook-driven extension points in the WordPress theme ecosystem, which is why agencies pick Blocksy for sites that need precise control over where each block renders. That flexibility produces a familiar audit problem at scale: dozens of Content Blocks accumulate across years of campaigns, each with its own hook, conditions, and priority. The default Blocksy admin lists Content Blocks but hides the operationally important details inside per-block panels.

Conflicting blocks compete for the same hook without anyone noticing until the front end breaks visually. Stale holiday banners linger because nobody filters for last-edited dates. Blocks targeting URL patterns that no longer exist sit ignored.

None of this is Blocksy's fault, it's what happens when a flexible system meets long-running operations. A queryable inventory changes the audit from a per-block panel walkthrough to a one-pass review. Filter by hook to see coverage.

Sort by priority to spot conflicts. Surface stale blocks in batches. Agencies use this as a recurring client audit; in-house teams use it as the documentation they finally have, of which block renders where.