Enfold's per-page customisation lives in a long list of meta keys: _avia_builder_shortcode_tree for the layout, header/header_title_bar/footer for which sections show, _avia_* overrides for everything else. The default WordPress Pages list shows title, author, date. Click into a page and you finally see whether the title bar is hidden, whether the footer is custom, whether the page uses a layout template. SleekView reads those meta keys directly so you build the columns you actually need, then sort by header style or filter by hidden footer without leaving the list.

Avia Layout Builder stores its tree as a serialised structure; SleekView decodes the parts useful for an audit (which top-level elements are in use, which colour set is referenced, which layout template the page extends) so a content review can show every page still using a deprecated element or every page on the legacy builder before you migrate. On large Enfold installs it falls back gracefully when meta is missing, so the same view works across staging, prod, and freshly imported demo content.

Inline edits go through update_post_meta, which is what Enfold itself uses, so Avia's caching and front-end render path pick up the change on the next request. Bulk-flip twenty pages from "show title bar" to "hide title bar" by editing the header_title_bar column directly — no clicking through the Enfold meta-box twenty times. The same applies to footer visibility, sidebar choice, and any ACF or Meta Box fields layered on top of Enfold.

Enfold has a customisation surface most themes do not: every page can override header style, title-bar visibility, footer choice, sidebar position, and a layout template. That flexibility helps designers ship distinctive sites; it also makes long-running Enfold installs hard to govern. The default WordPress Pages list shows title, author, date.

The _avia_* meta keys that drive per-page behaviour are invisible — the only way to see what's set is to open each page and scroll through Enfold's meta-box. That works for a small brochure site. It does not work for an agency maintaining dozens of Enfold builds, a business mid-rebrand swapping header styles, or a content team trying to standardise after years of ad-hoc per-page choices.

SleekView turns the same data into the workspace each team needs: designers see every page using a deprecated layout template, editors see header and footer columns next to titles, ops bulk-update title-bar visibility before a redesign. Same database, same hooks, dramatically less clicking through Enfold's per-page meta-box.