SleekView for Astra: surface child-theme CPTs and ACF data as tables
Astra ships clean, but production sites layer on portfolio, team, testimonial, and case-study post types via child themes, Astra Pro, or ACF. SleekView reads those post types and their meta directly so you can sort, filter, and inline-edit without opening each post.
♾️ Lifetime License available
Astra is fast — its admin still treats every post as a destination
Astra itself is intentionally minimal — it doesn't register custom post types or fields. But almost every Astra site ends up with them: a portfolio CPT from the child theme, a team CPT from a starter template, testimonial fields from ACF, service-page meta from Meta Box. WordPress's default list table shows the title, author, and date for each, then sends you into the editor for anything else. SleekView reads wp_posts joined to wp_postmeta directly so a portfolio table can show client name, project type, launch date, and live-site URL in real columns.
The pattern is the same for any post type Astra child themes or companion plugins register. Astra Pro adds advanced hooks and layouts but doesn't change how content is stored — it's still posts and postmeta. SleekView lists the post types actually present on the install, scans the meta keys in use for each, and lets you compose a column set without typing field slugs. ACF group fields and Meta Box repeaters work the same way, with sub-fields surfaced as joinable columns.
Inline edits route through wp_update_post and update_post_meta, so Astra hooks like astra_primary_header_after and any save_post handlers continue to fire. Bulk-update fifty portfolio entries' status from draft to publish, or correct a typo in a meta key across forty service pages, and every filter that would have run on a manual save still runs.
Workflow
How SleekView reads your Astra child theme's data
Pick the post type
Compose the column set
Save and scope the view
Edit inline and ship
wp_update_post and update_post_meta so ACF and Astra hooks fire.
Sample columns
A typical Astra child-theme portfolio view
wp_posts joined to wp_postmeta, so portfolio, team, and case-study post types registered by Astra child themes work without configuration changes.
wp_posts + wp_postmeta (any CPT registered by the child theme or companion plugins)
| Title | Client | Project type | Launch date | Status | Live URL |
|---|---|---|---|---|---|
| Northwind rebrand | Northwind Studio | Identity | Mar 18 | Published | northwind.studio |
| Coastal Roasters site | Coastal Roasters | Web design | Apr 02 | Published | coastalroasters.co |
| Plenum app marketing | Plenum Health | Landing page | Apr 15 | Draft | — |
| Halberd retainer Q2 | Halberd Legal | Retainer | Apr 21 | Published | halberd.law |
| Riverbed packaging | Riverbed Tea Co | Packaging | Apr 23 | Draft | — |
Comparison
Default WP admin list vs SleekView on Astra
Default WP admin list
- List shows title, author, date — meta from ACF or Meta Box stays hidden
- Editing any custom field requires opening each post
- Filters limited to category, tag, and date for most CPTs
- No way to save a column set as a named view per role
- Astra Pro adds layout features but not list-table customization
SleekView
-
Reads
wp_posts+wp_postmetafor any CPT registered by an Astra child theme - Inline-edit ACF, Meta Box, and core meta without opening posts
- Compose column sets from real meta keys present on the install
- Save filtered views per WordPress role (designer, editor, account manager)
- Switch between table, kanban, and feedback-board views of the same CPT
Features
What SleekView gives you for Astra theme
One column set per workflow
Designers see project type and launch date; account managers see client and retainer status. Each saved view picks columns from postmeta, ACF groups, and Meta Box fields without changing the underlying CPT registration.
Inline-edit meta in place
Update launch dates, flip draft to publish, or correct client names directly in the row. Edits go through wp_update_post and update_post_meta, so Astra hooks and ACF save filters fire as expected.
Filter on real fields
Compose filters across project type, status, and any meta key — date ranges, taxonomy terms, ACF select fields. Save the filter as a named view your team reuses every week without rebuilding it.
Audience
Who uses SleekView on Astra sites
Agencies running Astra retainers
One installation, dozens of client microsites built on Astra child themes. SleekView gives every project manager a portfolio and case-study table they can scan, filter, and update without opening each post in the WP admin.
In-house teams with team and testimonial CPTs
Astra starter templates ship team and testimonial post types. SleekView surfaces role, headshot URL, hire date, and approval status as columns so HR and marketing can keep them current without a developer.
Service-business sites
Service-page CPTs with pricing, duration, and category meta. SleekView shows them all in one table so the operations team can update a price tier across thirty pages without clicking into each one.
The bigger picture
Why Astra sites outgrow the default WP admin list
Astra positions itself as a fast, lightweight foundation, and that's exactly what it is. The catch is what gets layered on top. Production Astra sites almost always carry a child theme, a starter template, and a stack of CPT registrations from Astra Pro Sites or a companion plugin — portfolio, team, testimonial, case study, service.
ACF or Meta Box fields attach to those CPTs to hold client names, launch dates, pricing tiers, and segment tags. The default WordPress list table doesn't surface any of that. It shows title, author, and date, then asks you to open every single post for anything else.
Agencies running Astra retainers feel this most: thirty client microsites, each with a portfolio CPT and ten meta keys, every update a click-through marathon. SleekView turns the same data into a workspace. Designers see project type and launch date, account managers filter by retainer status, marketing scans approvals across testimonial entries.
The CPTs, the meta, the hooks — everything Astra and its companion plugins set up — keep working exactly as before. SleekView just gives the admin a row-level view that matches how teams actually think about the work.
Questions
Common questions about SleekView for Astra theme
No. Astra's customizer, hooks, and Astra Pro options stay exactly where they are. SleekView is an additional admin surface for the content stored in your custom post types and their meta. Astra continues to render the front end; SleekView gives the back end better row-level views of the data it renders.
Any of them. SleekView doesn't read theme files — it reads wp_posts, wp_postmeta, and the post-type registrations. Astra's own starter templates, the Pro Sites pack, and any third-party Astra child theme that registers CPTs all work the same way: SleekView lists the post types present and exposes their meta keys.
Yes. ACF and Meta Box are the most common pairings on Astra sites. SleekView reads ACF field groups directly through the ACF API where useful and falls back to postmeta otherwise; Meta Box fields read out of postmeta with the same column-picker UI. Sub-fields in repeaters and group fields are joinable as columns.
Yes. SleekView writes through wp_update_post and update_post_meta, which is the same path ACF and Meta Box hook into. acf/save_post, Meta Box save filters, and any save_post handler your theme adds all fire on inline edits — bulk operations iterate through the same path so the side effects match a manual save.
SleekView's queries hit the same indexed columns Astra's front end does — post_type, post_status, post_date, plus any meta keys you sort on. For large CPTs we recommend keeping aggregate columns off the default view since they're heavier; Astra's reputation for fast TTFB is preserved because SleekView only loads when you visit its admin pages.
Yes, as long as the destination site has the same post types and meta keys. SleekView configs are stored as JSON, exportable from one install and importable into another. Agencies running Astra retainers across many sites typically maintain a shared config repo and ship the same portfolio and testimonial views to every client.
Astra has both classic and FSE-compatible variants. Either way, SleekView reads the database, not the templates — so block themes, classic themes, and hybrid setups all work. The only consideration is taxonomy and CPT registrations, which Astra leaves to child themes or companion plugins regardless of FSE status.
Astra Pro's hooks operate on rendering, not data — header layouts, page-builder integrations, sticky sidebars. SleekView doesn't touch any of that. The two coexist cleanly: SleekView gives the admin a row-level view of CPT data, Astra Pro keeps doing what it does for the front end and the customizer.
Pricing
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.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
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