In postmeta on each page or post as Divi shortcodes. Reusable items live in the Divi Library custom post type, and Theme Builder templates have their own custom post type with URL conditions stored as meta. SleekView reads all three sources directly so the full Divi footprint surfaces in one queryable table.

No. Layout content (the Divi shortcode in postmeta) is still edited inside the Divi Builder where the visual editor, modules, and design controls live. SleekView edits status, slug, author, and other metadata that surrounds the layout. The shortcode itself never gets touched, which keeps the visual editor as the only source of truth for layout content.

Yes. SleekView includes a column for each Theme Builder template's URL conditions so you can audit coverage at a glance. Find templates targeting URLs that no longer exist after a content reorganization, or see which URLs have no Theme Builder coverage at all. That kind of audit takes one filter instead of opening the Theme Builder visual map.

Yes. Both store layouts the same way (postmeta with Divi shortcodes, the Divi Library CPT, and the Theme Builder CPT for Pro features), and SleekView reads from the same posts and postmeta in both cases. No version-specific configuration is needed for the audit grid to work.

Yes. Any view exports to CSV with your visible columns. Build the audit slice in the grid first (stale pages, orphan library items, Theme Builder coverage report), then export. Agencies use these as recurring client deliverables, and in-house teams use them as the inputs to redesign planning.

No. SleekView only reads metadata around layouts. The Divi editor, the front-end render, and the Theme Builder visual map all run unchanged because nothing about their loading path is affected by reading or editing the surrounding postmeta and CPT records.

Yes. Filter library items by reference count equals zero to surface saved sections, rows, or modules that no live page uses. Orphan library items inflate the database, slow the library picker in the editor, and confuse the next team. Pruning them is a high-value, low-risk audit task.

Theme Builder allows multiple templates to target overlapping URL conditions, with priority rules determining which applies. SleekView surfaces each template's conditions in the grid, so spotting overlapping templates becomes a filter pass instead of inferring conflicts from the visual map. Conflicts get resolved before they cause front-end inconsistencies.