Bricks Builder stores layouts in _bricks_page_content meta on standard pages, plus reusable templates as the bricks_template post type. Conditions describing where each template applies live as arrays inside that template's meta. The default Bricks admin lists pages and templates on separate screens and hides conditions inside modal dialogs. SleekView reads both, decodes conditions, and exposes them as chartable rows.

Charts then describe a Bricks build at site scale: template-type spread, condition target distribution, edit cadence per template type, count of pages with Bricks content versus pages without. The dashboard sits next to the Table view used for the inline audit work.

Reads only. Inline edits in the Table view route through update_post_meta so Bricks's render cache invalidates and the next render reflects the change. The builder keeps owning design; SleekView Charts owns the audit and handoff surface.

Bricks Builder shines on production sites with dozens of templates and conditional rules. The trade-off is that the admin presents pages and templates as two separate screens and hides conditions inside modals. SleekView Charts joins them, decodes the conditions, and renders the result as configurable cards.

The agency running an audit gets a one-screen baseline before opening the editor, and the client handoff stops being a screenshot exercise. The builder keeps owning the design surface; SleekView surfaces the inventory.