✨ 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 Kanban for Custom Fields Suite

SleekView Kanban reads any Custom Fields Suite-backed post type with its CFS field groups, groups records by a CFS Select field or post_status, and lets editors drag entries between Draft, In review, Approved, and Published for a real review surface.

♾️ Lifetime License available

SleekView Kanban board for Custom Fields Suite

Why Custom Fields Suite sites need a kanban view

Custom Fields Suite stores field group definitions in the cfs post type and field values in the wp_cfs_values table keyed by the field id and the parent post id. The default admin shows CFS-backed records as flat lists with the standard title and date columns, with no built-in surface for the CFS field values that hold the actual workflow shape of the record for the editorial team.

SleekView Kanban points at the CFS-backed post type, lets you pick a CFS Select field or the standard post_status as the group field, and renders one card per record. Each card shows the title, the author, the modified date, and any CFS field you choose for the card front, like a Select field for stage, a Date field for due date, a User field for the owner, or a Text field for context.

When an editor drags a card from Draft into In review or Approved, SleekView writes the new value to the wp_cfs_values table through the standard CFS save path, fires the cfs_save hook, and updates column counts. Editorial calendar plugins continue to fire on every change.

Workflow

Build a Custom Fields Suite board in four steps

1

Connect SleekView to CFS

Install SleekView, pick the CFS-backed post type as the source, and list the CFS field group to load per row. SleekView reads through the standard CFS API, so live records drive the board with no exports or sync jobs.
2

Pick a CFS Select for columns

Choose the CFS Select field that holds the review state. Draft, In review, Approved, and Published map cleanly. Derive a state from several CFS fields when the workflow needs a stage and a flag in one column.
3

Set what shows on cards

Pick the CFS fields shown on each card front: a Date field for due date, a User field for owner, a Select for priority, and any Text field for context. Cards stay compact so a reviewer scans a full column at a glance.
4

Enable drag-and-drop rules

Enable drag-and-drop, set which roles can move cards, and pick the CFS save path per column. Moving a card calls the standard CFS save method for the chosen Select field, so cfs_save and custom code fire on every move.

Sample board

Sample Custom Fields Suite review board

A live CFS board for a Resource post type with a stage CFS Select field, showing draft work, in review, approved, and published resources so editors drag resources between lanes by stage.
Draft
32
Resource, retail trends 2026 brief
Owner: Maya R, updated today
Resource, healthcare compliance guide
Owner: Sam D, updated yesterday
Resource, fintech audit checklist draft
Owner: Jordan V, two days old
In review
14
Resource, ecommerce holiday playbook
Owner: Leo K, in review now
Resource, online education whitepaper
Owner: Lena M, day two of review
Resource, manufacturing safety brief
Owner: Joe T, second review pass
Approved
10
Resource, travel route planning guide
Approved by Lead Anna today
Resource, SaaS billing migration plan
Approved by Lead Anna yesterday
Resource, hospitality venue handbook
Approved by Chris L this week
Published
176
Resource, vendor onboarding handbook
Published three days ago by Anna
Resource, summer sales operations memo
Published last week by Chris L
Resource, partner integration guide v2
Published yesterday by Sam D

Comparison

Default CFS admin vs SleekView Kanban

Default CFS admin view

  • Custom Fields Suite records show as flat WordPress lists with limited columns.
  • Workflow stages live in CFS Select fields with no visual queue around values.
  • Bulk actions cannot group records by a CFS Select across the editor dashboard.
  • Filtering by CFS field is limited, reviewers cannot drag between review queues.
  • Site builders write custom admin pages to give CFS records a board-like surface.

SleekView Kanban

  • Group any CFS-backed post type by a cfs Select field or post_status cleanly.
  • Show owner, due date, priority, and modified date on the card front for context.
  • Drag a card from Draft into In review and SleekView writes via the standard CFS path.
  • Run one board per CFS-backed post type, for resources, projects, or proposals each.
  • Roles can be limited to record owners so general subscribers never see the board.

Features

What SleekView Kanban gives you for Custom Fields Suite

Review surface for every model

Any CFS-backed post type becomes a review board, with a CFS Select field or post_status defining columns. Site builders skip custom admin pages, and the standard CFS save lifecycle stays intact through every move.

Owners, dates, priority on cards

CFS User, Date, and Select fields land on the card front, so a reviewer sees ownership and importance without opening the record. The cfs_save hook fires on every move so audit plugins keep running.

Drag writes back via CFS API

When a card moves, SleekView writes the new value through the standard CFS save method, the same path CFS uses on save. The cfs_save hook and any custom code listening continue to fire on every change.

Audience

Site builders that put it on the editor dashboard

Content teams running libraries

Content teams model resources as a CFS-backed post type with a stage CFS Select. Drafts land in Draft, reviewers drag through In review and Approved, and CFS save hooks keep calendars running.

Agencies reviewing proposals

Agencies model proposals as a CFS-backed post type with CFS Date fields for due date. The board shows which proposals are still in In review against the calendar, and CFS save hooks update audit logs.

Operations with task queues

Operations model tasks as a CFS-backed type with a workflow_state CFS Select. In review tracks live work, Approved captures sign-off, and Published doubles as an audit trail across every quarter.

The bigger picture

Why a CFS kanban makes field groups feel real

Custom Fields Suite is a long-standing free alternative to ACF for adding custom fields to WordPress post types. Field groups define the shape of every record, and field values live in the wp_cfs_values table keyed by field id and parent post id. CFS is great at modeling parts of a site that the default WordPress post types do not cover, but the default admin still shows CFS-backed records as flat lists with standard columns, which means workflow only lives in people's heads.

A kanban view changes that shape. A CFS Select field or the standard post_status becomes the columns, the most important CFS fields land on the cards, and the board gives every model a real review surface without writing a custom admin page. The In review column becomes the work, Approved makes the handoff visible across the team, and Published doubles as a recent-history view.

Moving cards keeps the standard CFS save method in play.

Questions

Common questions about SleekView Kanban for Custom Fields Suite

Yes. Moving a card calls the standard CFS save method for the chosen Select field, which is the same path CFS uses on save. The cfs_save hook and any custom code listening to the standard WordPress hooks continue to fire without any extra plugin glue or workaround for the workflow.

 

SleekView reads any CFS-backed post type through the standard CFS API, including any CFS field group attached to the post type. You pick the source, choose a CFS Select field or post_status to group by, and SleekView renders one card per record with the fields you select.

 

Yes. SleekView ships with role-based permissions, so record owners can have a single page that holds the review board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so contributors cannot move records into Approved without an editor.

 

Derived states are first-class in SleekView. You can define a workflow_state computed from several CFS fields, such as treating a record as In review when an approval Select equals false and a stage Select equals submitted, and SleekView groups by that derived value.

 

Each board has one source so the rules stay clear, but most setups run one board per CFS-backed post type on the same editor dashboard. Column counts at the top of each show waiting work at a glance, so the team sees resources, proposals, and tasks without losing boundaries.

 

Dragging never deletes data. It writes only the chosen CFS Select field through the standard CFS save path, which is the same thing a save in the CFS editor does. Other CFS field values are not touched, so Date, User, and Text fields remain exactly as saved before.

 

Yes. Each card can show the time since the record was last modified or since the chosen CFS Select field was last updated, so a record stuck in Draft for a week looks visibly different from a fresh one. Sort options can place the oldest cards at the top of every column.

 

No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on wp_posts and wp_cfs_values. Sites with hundreds of thousands of CFS-backed records stay responsive because heavy CFS field groups are only fetched for cards currently on screen.

 

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