✨ 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 Easy FancyBox

SleekView reads the posts where Easy FancyBox is active, groups them by post status or any taxonomy you nominate, and lets your team drag each card between columns so editorial review, scheduling, and publishing happen on one board instead of inside admin lists scattered across every post type on the site.

♾️ Lifetime License available

SleekView Kanban board for Easy FancyBox

Why Easy FancyBox sites need a board

Easy FancyBox by RavanH is a configuration plugin: it stores its settings inside wp_options under the easy_fancybox_options key and attaches FancyBox behavior to existing image, gallery, video, and iframe markup inside posts and pages stored in wp_posts. There is no custom post type and no admin screen listing every page that depends on a FancyBox treatment.

SleekView reads from wp_posts filtered to entries that contain markup Easy FancyBox treats, then surfaces every column as a possible grouping axis. The obvious starting point is post_status with draft, pending, publish, and private, but most teams add a custom media_review meta field with values like images selected, captions written, alt text checked, and approved, and group by that to track real editorial progress.

Dragging a card from one column to another updates the host post through wp_update_post, firing the standard save_post and transition_post_status hooks so caching plugins, image regeneration, and CDN purges all stay in sync. Posts without FancyBox-eligible markup can be filtered out so the board only shows content where Easy FancyBox actually matters for the editorial team.

Workflow

From scattered posts to one media board in four steps

1

Connect the host post type

Pick the posts, pages, or custom post types that Easy FancyBox treats. The plugin auto-detects every meta key on those posts and offers them as potential card fields, including any custom taxonomies your team uses to tag content by section, brand, or campaign assignment.
2

Pick the column to group by

Choose any field as your kanban grouping key. Most teams pick the built-in WordPress post status with draft, pending review, scheduled, and published, but a custom media review meta field or a category taxonomy can also serve as the column axis when needed.
3

Choose what shows on cards

Drag up to six fields onto the card face. Typical picks are post title, image and video count, last edited author, featured image thumbnail, and the assigned reviewer. Cards stay compact at a glance and expand on click to show every meta field on the host post.
4

Enable drag and drop

Flip on write-back and every card drag updates the host post through the standard WordPress API, firing post transition hooks so caching, image lazy load, and any analytics tied to publishing stay in sync. Lock columns for read-only review states if needed.

Sample board

Sample Easy FancyBox media board

A live preview of an Easy FancyBox board grouped by post status, with post title, FancyBox media count, and last edited author on each card and totals shown in each column header.
Draft
14
Long form annual report article
Sarah Mitchell, 18 images
Customer journey case study
James Park, 9 videos
Founder Q and A post
Priya Shah, 12 images
Pending review
6
Launch announcement page
Mark Lee, awaiting captions
Customer story feature post
Emma Carter, alt text check
Conference recap with media
Tom Wright, legal review
Scheduled
3
Holiday gift guide page
Linda Park, queued for Nov 28
Year in review long form post
Daniel Kim, queued for Dec 22
Product launch deep dive
Aisha Khan, queued for Jan 09
Published
198
Founder interview series part one
Sarah Mitchell, evergreen
Office tour photo and video set
James Park, on home page
Annual conference recap article
Priya Shah, featured

Comparison

Default WordPress post list versus SleekView Kanban

Default WordPress post list

  • Posts using Easy FancyBox sit in the same global list as plain text posts with no visual cue
  • Status changes require opening every post individually, no bulk drag between states
  • Custom media review fields cannot become the grouping axis without extra developer work
  • Scheduled posts mix into the publish queue with no separation from already live posts
  • Editor handoffs rely on private comments which are invisible from the post list view

SleekView Kanban

  • Reads directly from wp_posts filtered to FancyBox-enabled posts with no duplicate storage
  • Drag-and-drop writes back through wp_update_post so caching and hooks fire correctly
  • Group by built-in post_status or any custom meta field on the host post
  • Card face accepts up to six fields including FancyBox media count and reviewer
  • Works alongside Gutenberg, classic editor, and any page builder without extra config

Features

What SleekView Kanban gives you for Easy FancyBox

Group by any field on the host post

Built-in post status is the default grouping but any taxonomy, custom meta, or media review stage field becomes a column axis. Boards remember the grouping per user so your photo editor and your social manager can each see the same posts differently.

Drag-and-drop writes back to posts

Moving a card calls the standard WordPress post update API which fires every transition hook, webhook, and revision exactly as the editor would from the admin. Optimistic UI updates instantly and rolls back on API failure so nothing publishes by mistake.

Per-role column visibility

Hide the Published column from designers, hide the Draft column from approvers, or expose extra archive columns only to admins. Visibility rules use WordPress capabilities so they line up with whatever role plugin your team already uses for content roles.

Audience

Common Easy FancyBox boards teams build

Image-heavy editorial pipeline

Group every post by post status so the content team knows what is being drafted, what is waiting on captions, what is queued, and what went live this week without manually filtering every list.

Accessibility review queue

Group posts by an alt text audit meta field so accessibility leads see which posts still need captions and which already passed review against the published team checklist.

Editorial calendar board

Group posts by scheduled publish month so editors can see what is queued for each upcoming week and rebalance the calendar before launch dates slip past planned slots.

The bigger picture

Why a real board beats the WordPress post list

Easy FancyBox is great at giving image, video, and iframe content a polished modal viewer without dragging in a heavyweight gallery plugin, but it leaves you with no central admin screen that shows the editorial state of every post where FancyBox actually matters. The default WordPress list table mixes those posts in with plain text articles, hides status updates inside individual edit screens, and shows scheduled posts alongside long-published ones with no separation. A kanban board fixes the part the WordPress admin was never designed to fix: editorial visibility.

You see at a glance how deep each column is, which posts have been sitting in Draft the longest, and what the team published since yesterday. Status changes happen with a single drag and every change writes back through the proper WordPress API so caching, lazy loading, and any analytics tied to publishing keep working exactly as they did before. The result is your existing Easy FancyBox content shown the way an editorial team actually thinks about it.

Questions

Common questions about SleekView Kanban for Easy FancyBox

The drag calls the standard WordPress post update API so the change is persisted to wp_posts and triggers the usual transition_post_status hook chain. Caching plugins, CDN purges, and any analytics tied to publishing react exactly as if an editor moved the post through the regular admin screen.

 

Yes. SleekView accepts a content filter that scans post content for the image, gallery, video, and iframe markup Easy FancyBox treats and excludes everything else, so the board never gets cluttered with plain text posts that have no FancyBox media to manage.

 

Yes. Any taxonomy, custom meta field, or author assignment defined on the host post type can be the grouping axis. Most teams add a custom media_review meta key for review steps like images selected, captions written, alt text checked, and approved, and group by that field instead.

 

Scheduled posts appear in their own Scheduled column by default with the queued publish time shown on each card. Moving a scheduled post back to Draft clears the publish timestamp, and moving it forward to Published immediately fires the publish hook so any downstream integrations run right away.

 

Yes. Every action on a card uses the same capability checks as the standard post edit screen, so contributors cannot publish, editors cannot trash other people content unless their role allows it, and any role plugin you already use controls who can drag between which columns.

 

The post status changes back to draft through wp_update_post, which triggers the usual unpublish path. The post disappears from frontend listings on the next request, cached page versions are invalidated, and the original publish date is preserved on the post so republishing later keeps the canonical URL intact for SEO.

 

Yes. The kanban surface uses pointer events so it works with mouse, trackpad, touch, and pen input. Long press on a card initiates the drag on touch devices, and column scrolling works even while a card is mid drag so you can move a post across columns that do not fit on the same viewport.

 

Each card drag is a single atomic post update so two simultaneous drags resolve in the order the server receives them, with the second drag winning. The board polls for status changes every few seconds so the other editor sees the change land in near real time without refreshing the view.

 

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