Stop building admin-only templates with Advanced Views Framework

Advanced Views Framework (AVF) by WPLake is a templating plugin that reads ACF, Meta Box, JetEngine, and Pods fields and renders them into Twig or Blade templates on the front end. Its strength is keeping templates type-safe and tidy. AVF doesn't store its own content, so the source of truth stays in whichever field plugin you use: wp_postmeta for ACF and Meta Box, the JetEngine CCT or relations tables for JetEngine, and the Pods registry for Pods.

SleekView reads the same field sources directly. ACF and Meta Box meta keys become sortable, filterable columns. JetEngine CCTs are first-class table sources. Pods Advanced Content Types stay in their own tables. The admin table approach removes the need to build AVF templates whose only purpose is to give editors a workable backend, which lets AVF stay focused on the front-end and email templates it's actually designed for.

Inline edits route through whichever update API the source field uses: ACF's update_field, Meta Box's rwmb_set_meta, JetEngine's data classes, or Pods' field handlers. Validation and hooks for each source plugin continue to fire, and AVF templates pick up the new state on the next render. Saved views per role replace one-off admin templates and keep AVF templates lean.

Workflow

From Advanced Views Framework sources to an admin table

1

Pick a data source

Choose an ACF group, a Meta Box group, a JetEngine CCT or post type, or a Pods CPT or ACT. SleekView reads the source plugin's registry to know which fields are available.

2

Compose columns

Drag fields, taxonomies, and relations into the order your workflow uses. JetEngine CCT tables and Pods ACT tables stay fast because joins target their own indexes.

3

Filter and group

Filter by status, date, or any field. Each filter goes through the source plugin's typed lookup, so numeric and date sorts behave correctly.

4

Edit through the source

Inline edits route through ACF, Meta Box, JetEngine, or Pods. Each plugin's validation and hooks continue to fire as if the change came from its own form.

Sample columns

A typical Advanced Views Framework data source

An ACF-backed CPT exposed by AVF, shown as a SleekView table instead of an admin-only AVF template.

Source: wp_posts + wp_postmeta (ACF/Meta Box) or JetEngine CCT tables or Pods custom tables, depending on the AVF source

Title	Owner	Category	Price	Updated	Status
Coastal cabin	Alex Reyes	Cabins	£185 / night	Apr 22	Bookable
Forest yurt	Ria Bell	Yurts	£140 / night	Apr 23	Holding
Lakeside lodge	Tom Park	Lodges	£245 / night	Apr 24	Bookable
Old shed listing	Mia Lin	Cabins	n/a	Feb 14	Archived

Comparison

Advanced Views Framework alone vs AVF + SleekView

AVF alone

AVF is template-first, so a back-end column set means a back-end template
ACF and Meta Box meta fields aren't sortable on the default WP list table
JetEngine CCT data needs a separate admin path for non-template use
Pods ACT data sits outside WP_Query so default lists are limited
Sharing a curated column set per role means another AVF template

AVF + SleekView

Same field sources, no AVF template needed for admin
ACF, Meta Box, JetEngine, and Pods meta as columns
Inline edits route through each source plugin's API
JetEngine CCT and Pods ACT custom tables queried directly
Saved views per role replace admin-only AVF templates

Features

What SleekView gives you for Advanced Views Framework

Source-aware reads

SleekView detects whether a field is ACF, Meta Box, JetEngine, or Pods and queries the right storage. JetEngine CCT tables and Pods ACT tables are read directly for speed.

Admin without templates

AVF stays focused on front-end and email templates. SleekView gives the same data a sortable, filterable admin table with no template to maintain.

Source-routed writes

Inline edits go through ACF's update_field, Meta Box's rwmb_set_meta, JetEngine's data classes, or Pods' field handlers. Each plugin's hooks fire normally.

Audience

Who uses SleekView for Advanced Views Framework

Agency developers

Stop building AVF templates whose only job is to be a back-end column set. SleekView handles the admin and lets AVF focus on the front end where it earns its keep.

Booking and listing sites

Edit cabins, yurts, and listings from one table with price and status columns. Filters work against ACF or Meta Box meta without writing posts_clauses handlers.

Editorial teams

Saved views per role mean editors see the columns and filters that match their workflow without learning the AVF template syntax.

The bigger picture

Why Advanced Views Framework shouldn't own admin column sets

Advanced Views Framework's value is putting front-end and email templates on a tidy, type-safe foundation. ACF, Meta Box, JetEngine, and Pods provide the data; AVF turns that data into Twig and Blade templates. The pull to use AVF for back-end column sets is real because the templating is so good, but it leads to a familiar tax: each new admin column means a template change, each role with a different column set means another template, and the admin gets coupled to AVF.

SleekView lets AVF stay focused. The same ACF, Meta Box, JetEngine, and Pods data powers both: AVF renders the front end, SleekView renders the admin. Edits go through each source plugin's API so hooks and validation keep firing.

AVF templates pick up the new state on the next render. Front-end templates stay lean. Admin tables stop being a side project.

The data model stays the single source of truth for both surfaces.

Questions

Common questions about SleekView for Advanced Views Framework

Yes. SleekView supports the same sources AVF reads: ACF, Meta Box, JetEngine, and Pods. The right storage is queried per source (postmeta, CCT tables, or Pods custom tables) without extra configuration.

Yes. Writes go through ACF's update_field, Meta Box's rwmb_set_meta, JetEngine's data classes, or Pods' field handlers. Each plugin's validation and hooks continue to fire on cell edits.

Yes. AVF reads the same field sources on render, so a SleekView edit becomes visible on the next AVF template render. There is no caching layer between the two.

Yes. Meta Box's default postmeta storage and its custom-table storage option are both supported. SleekView reads the Meta Box registry to know which storage path each field uses and queries the right table.

Yes. JetEngine Custom Content Types are first-class sources. SleekView queries the jet_cct_* tables directly and exposes relations from jet_rel_* as inline columns.

Yes. Pods ACTs in their own tables are read directly through Pods' API. Field validation and bidirectional relationship updates continue to fire through Pods' update functions.

Yes. Any view exports from the table header with active filters and column order respected. Source-specific fields export as their resolved values rather than raw meta or relation IDs.

Rarely. AVF is for type-safe templates on the front end and in emails. SleekView is for the admin table layer. Both read the same field sources, so they coexist on the same content without competing.

Other plugins SleekView pairs well with

SleekView for WPGraphQL

SleekView reads WPGraphQL's query log (or the GRAPHQL_DEBUG payload) and renders every resolved operation as a row, with name, root type,...

SleekView for Intuitive Custom Post Order

SleekView reads wp_posts.menu_order and wp_terms.term_order, the two ordering signals Intuitive Custom Post Order maintains, then renders...

SleekView for PublishPress Series

SleekView reads the PublishPress Series taxonomy and the part-order postmeta and joins them with the posts table, so every series and par...

SleekView for Echo Knowledge Base: articles as tables

Echo Knowledge Base registers articles as a custom post type with a category taxonomy that nests five levels deep. SleekView reads the co...

SleekView for FluentComm: developer comments, threads & moderation as tables

FluentComm stores threads and reactions in wp_comments, wp_commentmeta, and its own tables. SleekView turns the...

SleekView for Documentor: documentation as tables

Read the documentation custom post type, join the category taxonomy, and surface every entry in one flat list. Inline-edit ordering, pare...

Pricing

Q: Do inline edits fire each plugin's hooks?

Yes. Writes go through ACF's update_field, Meta Box's rwmb_set_meta, JetEngine's data classes, or Pods' field handlers. Each plugin's validation and hooks continue to fire on cell edits.

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

Get started

3 websites
1 year of updates
1 year of support

Pro

€149

EUR

per year

Get started

Unlimited websites
1 year of updates
1 year of support

Lifetime ♾️

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

SleekAI
SleekByte
SleekMotion
SleekPixel
SleekRank
SleekView

€749

Continue to checkout

Browse more

Ecommerce

Email

Security

Membership

SleekView for Advanced Views Framework: ACF and Meta Box data as tables

Stop building admin-only templates with Advanced Views Framework