Pods is unusual among content modeling plugins because its Advanced Content Types live in their own custom database tables instead of wp_posts and wp_postmeta. Standard custom post types still use the WordPress meta tables, and Pods relationships can be either meta-based or table-based. The default Pods admin handles each storage path with limited list-screen options: ACT rows live outside WP_Query, so the standard list filters do not apply, and bulk editing custom field values usually means Pods Templates or custom code.

SleekView reads both storage paths. Each Pod becomes a workable view with the fields, taxonomies, and related Pods shown as proper columns, regardless of whether the data lives in postmeta or a Pods custom table. ACTs keep their performance benefits because SleekView queries the dedicated tables directly. Inline edits go through Pods' update functions so validation and pods_api hooks still fire, and bidirectional relationships update both sides exactly as they do from a Pods edit form.

Both meta-based and table-based field storage are supported, so a Pod that mixes both works as one table. SleekView coexists with Pods Pro and add-ons like List Tables because it reads the same Pods data layer instead of replacing it. Saved views per role, exports to CSV, and inline relationship editing make catalog-style Pods (books, products, locations) feel like the inventory tools they actually are, without leaving WP Admin.

Pods made an early bet that not every content model belongs in postmeta. Advanced Content Types live in their own custom database tables, which is what makes them fast for catalog-style data with hundreds of thousands of rows: there's no postmeta join overhead, and queries can use proper indexes on the columns that matter. The downside has always been the admin experience.

WordPress's list table machinery assumes WP_Query, and ACTs sit outside it. Pods provides admin lists, but the default columns are limited and bulk editing tends to require Pods Templates or custom code. Teams running serious ACT-based catalogs end up either building one-off admin pages or accepting that day-to-day editing is awkward.

SleekView closes that gap. The same Advanced Content Type that gives you ten-thousand-row queries in milliseconds becomes a sortable, filterable, inline-editable table without writing a custom List Table or moving data into postmeta. Standard custom post types and ACTs share the same UI, relationships resolve inline regardless of storage, and Pods' own validation and hooks continue to fire on every edit.

The performance benefits stay where Pods put them, and editors finally get an admin that matches the data model.