✨ 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 Essential Grid

Essential Grid pulls source items from WordPress posts, custom post types, WooCommerce products and a custom grid item post type. SleekView Kanban renders those source items as draggable cards grouped by status or skin, so editors can move items from draft to live without the Essential Grid backend.

♾️ Lifetime License available

SleekView Kanban board for Essential Grid

Group Essential Grid source items by status or skin

Essential Grid renders grids of items from any source the user picks, including the core WordPress posts table and a custom grid item post type the plugin registers. Each item carries the standard post_status column plus per-grid skin and category meta, which is exactly the data needed to drive a kanban board.

The default Essential Grid admin is a builder focused on configuring a single grid, with a separate item editor for the custom item type. It is great for tweaking how a grid looks, but it does not surface the editorial pipeline across the whole library of grid items.

SleekView Kanban reads the same source items Essential Grid renders and lays them out as lanes. Cards show the thumbnail, source type, grid name and last edit. Dragging a card writes post_status back through standard hooks, so caching, CDN purges and any notification plugin react exactly as they do from the standard post editor.

Workflow

From Essential Grid items to a board

1

Pick the Essential Grid source

Choose the Essential Grid custom item post type as the data source, or point at the same posts and CPTs the grid uses on the front end. SleekView reads them directly, so a board can mirror the exact pool a public grid renders from.
2

Group by status, skin or category

Pick post_status for Draft, Pending review, Scheduled and Published lanes. Pick the Essential Grid skin meta to group by skin during a design migration. Pick the grid item category taxonomy to organise the board around editorial sections.
3

Choose the card fields that help triage

Add the thumbnail, source type, grid name, last edit and any custom field that drives the front end grid. The thumbnail uses the same image source Essential Grid uses on the public grid, so cards feel like a small preview of the actual grid.
4

Drag to change status or skin

Dragging a card between status lanes writes post_status back through wp_update_post and fires the standard hooks. Dragging between skin lanes updates the per-item skin meta, which Essential Grid reads on the next front end render with no extra config.

Sample board

How the Essential Grid board looks in use

Four lanes covering the editorial workflow from draft through review and scheduling to live, with thumbnail, source type and grid name on every Essential Grid card.
Draft
16
Case study: Casa Verde launch
Source CPT, skin Modern
Portfolio item: Brand refresh
Source Item, skin Minimal
Press feature: Industry Times
Source Post, skin News
In review
7
Client story: Halo Studio
Reviewer Mia, skin Modern
Team profile: Lina the photographer
Reviewer Sam, skin Minimal
Press feature: Design Weekly
Reviewer Priya, skin News
Scheduled
5
Launch campaign showcase item
Live Mon, skin Modern
Charity event recap card
Live Wed, skin Minimal
Quarterly recap article
Live Fri, skin News
Live
184
Portfolio archive 2025
Live 18d, 3,420 views
Case study: Acme rebrand
Live 9d, 1,820 views
Press feature: Founders weekly
Live 3d, 940 views

Comparison

Default Essential Grid admin vs SleekView Kanban

Default Essential Grid admin

  • Grid builder is great for skin design but hides the pool of source items behind tabs.
  • Tracking which items are draft, scheduled or live across all grids needs a separate sheet.
  • Status changes still require the standard WordPress post editor, one item at a time.
  • No counts per stage, so a swelling review backlog goes unnoticed until the launch slips.
  • Skin migrations are painful because the admin cannot show which items still use the old skin.

SleekView Kanban

  • Reads Essential Grid item posts and any other source the public grid uses on the front end.
  • Group by post_status, the Essential Grid skin meta or item category taxonomy.
  • Drag and drop writes back through wp_update_post and standard WordPress hooks.
  • Card thumbnails match the public grid because SleekView reads the same image source.
  • Stacked filters let one editor see only items in their section while leads see everything.

Features

What SleekView Kanban gives you for Essential Grid

Preview cards mirror the public grid

Each card uses the same image source Essential Grid renders on the public grid. The board feels like a small editorial preview rather than a database admin, which makes it obvious which items are visually ready to ship and which still need a cover image.

Skin migration lanes

Group by the Essential Grid skin meta and each lane becomes a skin. Mid-migration the board makes it obvious how many items still use the legacy skin, and dragging an item between lanes updates the skin meta which the front end reads on next render.

Status writes back through standard hooks

Dragging a card to Scheduled flips post_status to future and writes a publish date. The standard transition_post_status, save_post and Essential Grid hooks fire, so caching, CDN purge and notification plugins react as they do from the post editor.

Audience

Where Essential Grid teams use kanban view

Portfolio and case study grids

Agencies group portfolio items by client tag and drag them through draft, review, scheduled and live. Counts per stage surface bottlenecks immediately, so the lead can see whether the portfolio has enough new work ready for the next pitch deck.

News and press feature grids

Publishers group press features by section and use the board for triage. Each lane becomes a section, dragging a card between sections reassigns it across the whole site, and counts make it clear which section needs more articles before the homepage refresh.

Product showcase grids

Ecommerce teams point the board at the same product pool an Essential Grid renders. Lanes split by launch status help merchandisers see which products are scheduled for the weekend drop and which still need photography before they can go live.

The bigger picture

Why Essential Grid benefits from a board

Essential Grid is built around a polished grid builder, which is the right tool for designing how a single grid looks on the front end. What it does not do is offer a pipeline view across the underlying pool of source items. A site that publishes dozens of case studies, press features or portfolio pieces ends up tracking the editorial state of each item in a separate document, because the standard admin only shows the source posts as a flat list.

SleekView Kanban removes that split. Cards are the same source items Essential Grid renders on the public grid. Lanes are real post status values, real skin meta values or item category taxonomy terms.

Drag and drop writes the status change back through the same hooks the post editor uses, so caching, CDN purge and notification plugins all react as they would normally. Counts per lane expose backlogs in seconds, and filters layered on top of the board let a single editor focus on their section without losing the shared content pool underneath. Combined with Essential Grid's polished public grids, the result is one system that designs and ships editorial content with the workflow visible at every step.

Questions

Common questions about SleekView Kanban for Essential Grid

Both. SleekView can point at the Essential Grid custom item post type or at any post type Essential Grid uses as a source on the front end. The same pool that powers the public grid can power the board, so the two views never drift apart.

 

SleekView calls wp_publish_post, which flips post_status to publish and clears the scheduled date. Standard hooks fire, so caching, CDN purge and Essential Grid's own front end cache update exactly as they do from the standard publish flow in the post editor.

 

Yes. The group-by column can be the Essential Grid skin meta, the item category taxonomy or any other field on the source item. Different SleekView boards can use different group-by columns over the same pool of Essential Grid source items.

 

Yes. SleekView reads the same image source Essential Grid uses, including featured image, custom field overrides and source-specific image keys. The board feels like a small preview of the public grid so visual issues are caught before the item goes live.

 

Yes. A shortcode and a block render any saved board on the front end. Scope the board to a client tag and disable drag, and the client sees a read-only progress view of their own items while the internal team keeps full edit access in the admin.

 

Yes. SleekView honours the standard edit_post and publish_posts checks core uses for any post type. An author can move their own draft item to Pending review, but cannot drag a card to Live unless their role has the publish capability assigned.

 

Lanes paginate and lazy load card content as you scroll. The board only fetches the fields shown on the card, not full post content, so a Live lane with thousands of source items renders quickly on standard WordPress hosting plans.

 

Yes. Each board is a saved configuration with its own group-by, fields and filters. A production board grouped by post status can sit beside a skin migration board and a section board, all reading the same pool with no duplication of underlying data.

 

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