✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Blocksy: CPTs and Blocksy Pro content blocks as tables

Blocksy Pro includes a custom post types feature that registers portfolio, team, and case-study post types out of the box. SleekView reads those CPTs and any ACF or Meta Box fields attached to them so you can sort, filter, and inline-edit without opening each post.

♾️ Lifetime License available

SleekView table view for Blocksy theme

Blocksy Pro registers the CPTs — SleekView surfaces the data

Blocksy ships a header builder, content blocks, and a customizer that's earned a strong following. Blocksy Pro adds a custom post types feature that registers portfolio, team, and FAQ post types in a few clicks, plus content blocks that render those CPTs anywhere on the site. The admin side stays at WordPress defaults: title, author, date, click into the post for anything else. SleekView reads wp_posts joined to wp_postmeta directly so the meta Blocksy Pro content blocks render at the front becomes columns in the admin.

The picker lists the CPTs registered on the install — Blocksy Pro's own, plus any from a child theme or third-party plugin — and the meta keys actually present on each. ACF field groups attached through the customizer's content-block UI work the same way; sub-fields in repeaters and group fields are joinable as columns. Meta Box fields read out of the same postmeta table.

Inline edits route through wp_update_post and update_post_meta, so Blocksy's content-block hooks fire on save. Bulk-flip portfolio entries from draft to publish, update a feature flag across thirty FAQ items, correct a team-member role across the directory — every filter that would have run on a manual save still runs. The customizer stays where it is, content blocks keep rendering, and the admin gets a row-level workspace.

Workflow

How SleekView reads your Blocksy Pro CPT data

1

Pick the post type

SleekView lists Blocksy Pro CPTs (portfolio, team, FAQ, custom) plus any others on the install. Pick one and the meta picker populates with keys actually present on that CPT.
2

Compose the column set

Add core fields plus any meta key, including ACF group sub-fields and Meta Box repeater rows. Match the column set to the Blocksy content-block layout it corresponds to for editorial parity.
3

Save and scope the view

Name it ("Active team", "Stale FAQs", "Featured portfolio") and gate by WordPress capability so HR, design, and marketing each see the column set their work requires.
4

Edit inline and ship

Bulk-update visibility flags, flip hire dates, correct departments — all routed through wp_update_post and update_post_meta so Blocksy content blocks render the latest data.

Sample columns

A typical Blocksy Pro team-directory view

SleekView reads any CPT in wp_posts joined to wp_postmeta, so Blocksy Pro's portfolio, team, and FAQ post types work without configuration changes.
Source: wp_posts + wp_postmeta (Blocksy Pro CPTs and any companion-plugin post types)
Name Role Department Hire date Visible? Updated
Maya Holloway Senior designer Design Mar 04, 2022 Yes Apr 12
Daniel Park Engineering lead Engineering Jul 18, 2021 Yes Apr 11
Tomasz Kowalski Account manager Client services Sep 02, 2023 Yes Apr 09
Iris Calhoun Junior copywriter Content Jan 15, 2024 No Apr 21
Reza Anvari Operations Operations Nov 30, 2022 Yes Apr 18

Comparison

Default WP admin list vs SleekView on Blocksy

Default WP admin list

  • Blocksy Pro registers CPTs but doesn't customize their list tables
  • List shows title, author, date — Blocksy Pro meta hidden behind each post
  • Filters limited to status, taxonomy, and date
  • No saved column sets per role
  • Customizer is excellent for rendering, not for list management

SleekView

  • Reads wp_posts + wp_postmeta for Blocksy Pro CPTs and any companion-plugin CPTs
  • Inline-edit ACF, Meta Box, and core meta in the row
  • Picker lists meta keys actually present on each CPT
  • Save filtered views per role (designer, editor, HR)
  • Switch between table, kanban, and feedback-board views

Features

What SleekView gives you for Blocksy theme

Column sets that mirror Blocksy content blocks

If a Blocksy Pro content block renders the team CPT with name, role, and department, build a SleekView with the same fields as columns. The admin view matches the front-end fidelity the customizer set up.

Inline edits keep the customizer accurate

Updates route through wp_update_post and update_post_meta, so Blocksy content-block hooks stay accurate, ACF save filters fire, and bulk operations iterate the same path so side effects match a manual save.

Compose filters that match the team's vocabulary

Filter by department, hire-date range, visible flag, or any meta key. Save the filter as a named view ("Active engineering team", "Hidden roles for review") and reuse it across HR, design, and marketing.

Audience

Who uses SleekView on Blocksy sites

In-house teams running team or directory CPTs

Blocksy Pro's CPT feature is a common way to ship team and directory pages. SleekView gives HR and operations a real table for the data — names, roles, departments — so updates happen at row level instead of per-post.

Agencies on Blocksy Pro retainers

Multiple client sites on Blocksy Pro with portfolio and FAQ CPTs. SleekView surfaces those CPTs as tables for account managers and designers, with the same column set replicated across client installs through JSON config export.

FAQ and knowledge-base sites

Blocksy Pro's FAQ post type is a frequent pick. SleekView shows category, last-reviewed date, and visibility flag as columns so content owners can prioritize stale entries without opening every FAQ to check.

The bigger picture

Why Blocksy Pro CPTs deserve a row-level admin workspace

Blocksy Pro's custom post types feature lowered the barrier to registering portfolio, team, and FAQ CPTs — what used to take a code snippet now takes a customizer panel. Content blocks render those CPTs on the front end with the same care the customizer applies to headers and footers. The admin side, however, stayed at WordPress core defaults.

A title column, an author, a date, and the editor for everything else. The asymmetry shows up the moment a Blocksy site grows beyond a few entries: a studio with forty portfolio items, a company with eighty team members across departments, a FAQ catalog with a hundred entries spanning ten topics. The data is structured, the rendering is sharp, but the admin is a click-through marathon.

SleekView turns the same data into a workspace. The meta keys Blocksy Pro content blocks render become sortable, filterable columns. HR updates roles inline, designers flip portfolio featured flags, content owners review stale FAQs by last-reviewed date.

Blocksy keeps rendering with the customizer it's known for; SleekView gives the back end an interface that matches the structure of the data Blocksy Pro put there. Same database, same hooks, same rendering — much less clicking.

Questions

Common questions about SleekView for Blocksy theme

No. Blocksy's customizer, header builder, content blocks, and theme settings all stay exactly where they are. SleekView is a separate admin surface for the data inside CPTs. Blocksy keeps rendering with the same controls; SleekView gives the back end a row-level workspace for the data those renderings depend on.

 

Yes. Blocksy Pro registers CPTs (portfolio, team, FAQ, and any custom ones you add) using standard WordPress CPT registration. SleekView reads wp_posts joined to wp_postmeta, so any CPT registered through Blocksy Pro's UI surfaces in the SleekView post-type picker.

 

Yes. ACF and Meta Box are common pairings on Blocksy sites for richer fields than Blocksy Pro's built-in metaboxes. 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.

 

Yes. Blocksy Pro content blocks read meta at render time, so any inline edit through SleekView updates the data the next time a content block renders. SleekView routes through wp_update_post and update_post_meta, the standard WordPress save path, which Blocksy's hooks already cover.

 

Yes. WooCommerce orders, products, and customers each have their own SleekView integration. On Blocksy sites running WooCommerce, you can combine a WooCommerce orders view with custom CPT views (portfolio, team, FAQ) in one admin surface, switching between them with tabs or saved views.

 

Yes. Configs are stored as JSON. If two Blocksy installs share the same Blocksy Pro CPTs and meta keys, the same SleekView config works on both. Agencies running Blocksy retainers across multiple clients typically version-control a shared config repo and ship the same admin views everywhere.

 

Blocksy supports both classic and FSE workflows. SleekView reads database tables, not templates, so the rendering layer (FSE or classic) doesn't matter. The only consideration is which CPTs and meta keys are registered, and SleekView lists whatever's there.

 

Yes. SleekView joins wp_term_relationships and wp_terms when you add a taxonomy column or filter. Project category, team department, FAQ topic, and any custom taxonomy registered alongside Blocksy Pro CPTs all appear as filterable, sortable columns.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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