✨ 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 AIthor

SleekView Kanban turns the AIthor article queue into a drag-and-drop board grouped by generation status, so editors can see exactly which posts are queued, which are mid-generation, and which are waiting on a human review without scrolling through an undifferentiated list.

♾️ Lifetime License available

SleekView Kanban board for AIthor

From AIthor queue to publishing pipeline

AIthor stores every article generation as a row in its own queue table, with a generation_status field, a target_post_id, the source topic, and timestamps for queued, started, and completed times. The plugin's own admin screen lists these in a flat table that mirrors WordPress's default styling, which works when you have a handful of generations open and becomes a wall of identical rows once the queue grows past a single screen.

SleekView Kanban reads the same wp_aithor_queue rows and groups them by generation_status, which is the obvious pipeline column for an AI writer. Each card on the board shows the article topic, target post slug, model tier, and an age indicator so editors can pick the oldest waiting work first. Tooltips expose the source brief, target word count, and selected tone profile without forcing a click into a separate edit screen.

Dragging a card from review into published rewrites generation_status on the same row, so AIthor's own dashboards and any connected webhooks see the updated state immediately. Cards that share a topic cluster stay linked so an editor can move an entire content series across lanes in one motion, and the drag handler refuses drops that would skip required review steps.

Workflow

Connect AIthor to SleekView in four steps

1

Pick AIthor as the source

Inside SleekView, choose AIthor from the data source dropdown. SleekView introspects the queue table, the linked post type, and every meta key AIthor writes so you do not need to copy any SQL or describe the schema by hand before building the board.
2

Group by generation_status

Set the group-by column to generation_status. Every distinct value AIthor uses, including queued, generating, review, published, and failed, becomes its own lane with a count, so the board mirrors AIthor's actual pipeline rather than a generic backlog metaphor.
3

Choose card fields for editors

Editors usually want the topic, target post slug, model tier, and queued-at timestamp on the card front. Hidden fields stay searchable, so a brief, tone profile, or target keyword can still drive filters without crowding the card with too much copy at once.
4

Enable drag and drop writes

Switch on the writable mode and SleekView starts pushing generation_status changes back to AIthor on drop. Each move respects WordPress capabilities, so junior writers can drag drafts to review but only editors with the right role can promote a card all the way to published.

Sample board

Sample AIthor article board

AIthor generations grouped by generation_status, with card fronts showing topic, target slug, and model tier across queued, generating, review, and published lanes.
Queued
21
Beginner Guide to Backyard Composting
topic: composting, gpt-4o
How to Choose a Robot Vacuum in 2026
topic: robot vacuums, gpt-4o-mini
Best Wireless Earbuds Under 100 Dollars
topic: earbuds, gpt-4o-mini
Generating
5
Complete Indoor Cycling Setup Guide
started 3m ago, gpt-4o
Smart Home Hubs Compared Side by Side
started 5m ago, gpt-4o
How to Start a Subscription Newsletter
started 8m ago, gpt-4o-mini
Review
29
Best Lawn Mowers for Small Yards
1,640 words, with Sarah
Beginner Sourdough Bread Recipe
1,420 words, with Marcus
How to Start a Vegetable Garden
1,930 words, with Priya
Published
152
How to Plan a Cross Country Road Trip
live 6h ago, 2,140 words
Best Air Fryers Compared and Ranked
live 1d ago, 1,810 words
Guide to Choosing a Tent for Camping
live 3d ago, 1,620 words

Comparison

Default AIthor queue vs SleekView Kanban

Default AIthor queue list

  • Long flat list of generations sorted only by queued or created timestamp
  • Status badges in a column that you have to read row by row to scan
  • Changing status means opening a row, picking a dropdown, and clicking save
  • No filter bar to narrow by topic cluster, assigned editor, or model tier
  • Bulk delete is the only multi-row action, so review queues clear one row at a time

SleekView Kanban

  • Groups AIthor rows by generation_status with live counts per lane
  • Drag a card to change status and write the value back to the AIthor queue table
  • Card fronts surface topic, target slug, model tier, and a relative time stamp
  • Per-user filters let each editor focus on their own assigned articles
  • Failed and rate-limited generations sit in a dedicated lane for retry triage

Features

What SleekView Kanban gives you for AIthor

Reads the AIthor queue natively

SleekView understands AIthor's queue schema out of the box, including the linked target post, the brief, the tone profile, and timestamps. There is no field mapping screen to fill out, just a confirmation that the right rows appear before you publish the board to other editors.

Drag updates generation_status

Drops write the new generation_status to the same row AIthor uses, so the plugin's own retry logic, dashboards, and webhooks stay accurate. There is no parallel state file, no sync job, and no risk of the board drifting away from the actual queue table over time.

Per-user board filters

Each editor saves a personal filter so the board only shows their assigned articles, their model tier, or their topic cluster. Saved filters are scoped per user, so two editors looking at the same Aithor data see two completely different boards without disturbing each other.

Audience

Where AIthor teams use the kanban

Multi-author content sites

Sites with several writers use the board to assign generations, track who is reviewing what, and avoid two editors picking up the same draft. The lane counts also help editors plan their day before opening a single article.

SEO agencies producing at scale

Agencies producing dozens of AIthor articles per client use one board per client. Filters by topic cluster show which content gaps are still queued and which silos already have published coverage live on the destination site.

Triage of failed generations

A failed lane surfaces every generation that errored out or hit a rate limit. Editors drag those cards back into queued with one motion, and AIthor's worker picks them up again on the next cron cycle without manual SQL.

The bigger picture

Why kanban fits AIthor better than a list

AIthor is built around a queue, and queues are pipelines. Flat tables are great for inspection, but they hide the most important question a content editor asks every morning, which is what should I work on next. A kanban answers that question with one glance, because the lane with the highest count and the oldest cards is always where the next decision lives.

The list view treats each generation as an isolated row. The kanban treats them as work moving through stages, which matches how a content team actually thinks about its day. When you can drag instead of dropdown, the friction of moving work forward drops by an order of magnitude, and the rate at which articles ship goes up without anyone touching the underlying generation engine.

The AI does the writing, but the team still does the judgment, and the board makes that judgment fast.

Questions

Common questions about SleekView Kanban for AIthor

SleekView reads every column AIthor writes, including topic cluster identifiers and any custom meta keys you add through hooks. Cards can show cluster names directly, and filters can narrow the board to one cluster at a time, so siloed campaigns stay separate without duplicating the data.

 

Yes. SleekView does not replace AIthor's admin screens, it adds a new view on top of the same data. Editors who prefer the original list can keep using it, and the kanban will reflect any status changes they make from the old screen on the next refresh.

 

SleekView polls the queue rows it has on screen, so a generation that finishes while the card is open updates the badge and the displayed status without losing the editor's place. If the status changes lane, the card slides smoothly into the new column with a short animation.

 

Yes. SleekView ties drag permissions to WordPress capabilities, so writers can move cards between queued and review while only editors with publish_posts can drop a card into the published lane. The board surfaces an inline message when a drop is rejected.

 

Scheduled posts keep their schedule. SleekView shows the scheduled timestamp on the card and adds a small clock badge so editors know not to expect immediate publication. Dragging a card to published does not override the scheduled time, only the AIthor generation_status field.

 

SleekView only queries the queue rows that fit in the current board view, plus the small set of meta fields the card surfaces. It uses the same indexes AIthor relies on, so a board with several hundred cards loads on roughly the same query budget as a standard admin list view.

 

Yes. SleekView ships a shortcode and a Gutenberg block, both of which render the same kanban inside any WordPress page or dashboard widget. The embedded board respects the visitor's role, so a logged-out user simply sees nothing instead of any AIthor queue contents.

 

New statuses appear as their own lane at the end of the board, complete with a count and a placeholder color. You can drag the lane into the right position, set a color and icon, and decide which fields the cards in that lane should surface, without ever touching the AIthor database.

 

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