✨ 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 Documentor Pro

SleekView reads the Documentor Pro article tables directly, groups every doc by its workflow state, and lets the docs team drag cards across Draft, In review, Published, Archived so the underlying record updates the moment the column changes.

♾️ Lifetime License available

SleekView Kanban board for Documentor Pro

Why Documentor Pro fits a kanban view

Documentor Pro stores each doc in wp_posts for the documentor post type with metadata in wp_postmeta for the section and order fields. Each row has an ID, a created timestamp, an author, a category tag, a workflow state, and the article body rendered to readers on the frontend knowledge base. The default Documentor admin lists articles in a paginated screen, fine for occasional editing and weak when a Documentor documentation lead needs to coordinate a content sprint across dozens of docs that all need a documented review.

SleekView Kanban reads the same wp_posts for the documentor post type rows the Documentor admin queries. Pick the workflow state field as the grouping column and every entry becomes a card under Draft, In review, Published, Archived. Card fronts can show the author, the category, the reviewer, the last update timestamp, and the word count so the docs lead can prioritize the publishing queue from a single board.

Dragging a card writes the new workflow state back to the Documentor record. A move from In review to Published flips the post status and timestamps the action. The plugin's hooks for category updates, search reindex, and analytics keep firing, so a manual move never breaks the live knowledge base index or the analytics pipeline that reports article health.

Workflow

From Documentor list to a live documentation board

1

Connect Documentor as a source

Point SleekView at the Documentor tables. Add filters for author, category, last update, or workflow state so the board scopes to this sprint of docs for one knowledge base instead of every article ever published across
2

Pick the workflow column

Choose the workflow state field as the grouping column. SleekView buckets docs by state so Draft, In review, Published, Archived columns appear without writing custom SQL against the Documentor schema or maintaining a se
3

Choose card front fields

Map fields from the Documentor tables onto the card front. Most docs teams show the author, the category, the reviewer, the last update timestamp, and the word count so the docs lead can prioritize the queue right from t
4

Enable drag-and-drop writeback

Turn writeback on and dragging a card writes the new workflow state back to the Documentor record. Capability checks honor the editor role, and every move is logged with the user, source column, destination, and timestam

Sample board

Sample Documentor editorial review board

Four real workflow states showing how a docs team moves Documentor docs across Draft, In review, Published, and Archived during one content sprint. across every channel handled today
Draft
22
Draft article about installation process
author jenna, doc draft
Draft article about table of contents
author ben, doc draft
Draft article about custom CSS styling
author tom, doc draft
In review
9
In review by editor for clarity polish
reviewer lara, due Monday
In review by lead for accuracy double
reviewer mark, due Tuesday
In review for screenshot consistency now
reviewer priya, due Friday
Published
176
Published install doc with portal link
author jenna, live today
Published TOC doc with example layouts
author ben, live Tuesday
Published CSS doc with copyable snippet
author tom, live Friday
Archived
39
Archived install doc for old 1.x branch
by lara, archived this month
Archived TOC doc replaced by new layout
by mark, archived last week
Archived CSS doc for old theme system
by priya, archived last week

Comparison

Default Documentor vs SleekView Kanban

Default Documentor list

  • Long article list with no review queue showing what is still pending
  • Filtering by category reloads the page and loses the author filter set
  • No visual sense of which docs are in review versus already live
  • Marking an article published needs the per-row context menu and dialog
  • Coordinating a content sprint needs editor rights and Documentor training

SleekView Kanban

  • Reads directly from wp_posts for the documentor post type and wp_postmeta
  • Drag a card to Published and the Documentor post status writes atomically
  • Cards show author, category, reviewer, last update, and word count
  • Column counts update live so a backlog of drafts surfaces instantly
  • Per-role caps tie writeback to edit_posts for the docs team

Features

What SleekView Kanban gives you for Documentor Pro

Native Documentor model

Every column maps to a real workflow state stored in the Documentor record. Category updates, search reindex, and analytics hooks keep firing for new docs, so a manual review move never breaks the live knowledge base index or down

Drag-and-drop with trail

Each move writes a state change into the Documentor record naming the editor who dragged it, the source column, the destination column, and the timestamp. If a lead pushes an article back from Published to In review, the chain sta

Saved board views per sprint

Filter to one category for the on-call writer, drafts older than seven days for the editor, and articles awaiting screenshots for the docs lead. Each saved view becomes a shareable URL that opens the right board for each editor.

Audience

Where a Documentor kanban changes editorial work

Weekly editorial sprint

Docs leads scope the board to this week's drafts, drag docs into In review, and confirm Published only when an editor has signed off. The next sprint starts with a board that already shows exactly wha

Stale draft cleanup

Editors filter to drafts older than thirty days, move stalled cards into In review for a recovery pass, and archive the truly dead ones so the active board reflects only docs a writer is actually work

Reviewer load balancing

Team leads scope to one reviewer's queue, see how many docs are pending review versus already cleared, and reassign work so no reviewer ends the sprint with twice the workload of the rest of the team.

The bigger picture

Why this view matters for Documentor editorial work

Documentor Pro captures every article, which is exactly what makes the default admin list hard to use across a docs team. The sortable list is fine when an editor knows what they want and almost useless when a Documentor documentation lead needs to coordinate a sprint across docs that all need a documented review and a publish decision. Most teams export a CSV, drop it into a sheet, and tag docs by hand.

The sheet drifts within a day. New docs keep landing in Documentor without a workflow tag, the sheet records publish dates that nobody copies back, and by the end of the week the two views disagree on what is still pending review. A kanban view that reads and writes the same Documentor record as the admin keeps the docs team and the source of truth aligned.

Draft cards surface immediately. In review cards stay visible across reviewers. Published docs carry a documented sign-off and a named editor, all without leaving WordPress.

Questions

Common questions about SleekView Kanban for Documentor Pro

Live. SleekView queries the same wp_posts for the documentor post type and wp_postmeta for the section and order fields rows the Documentor admin reads. Filters apply at the SQL level, so a board scoped to this sprint reflects docs that landed in this sprint, not a snapshot exported earlier this week.

 

No. SleekView writes the new workflow state into the Documentor record. Category hooks, search reindex, and analytics keep operating on the original record, so a card move never re-fires a publish event, never suppresses one, and never alters analytics already logged.

 

Yes. The category, author, and last update fields live on every Documentor row. SleekView exposes all of them as filters and board grouping options, so a docs lead can scope to one category, to one author, or to articles untouched for thirty days for a recovery pass.

 

Yes. Every move runs through current_user_can('edit_posts') and the Documentor editor capability before any record write. A contributor account can drag for personal sorting but the change does not persist, with a toast notification explaining why the move was rejected.

 

Filters apply at the database query level rather than in JavaScript. A typical board scopes to this sprint, to one category, or to drafts only, so the rendered card count stays well under a thousand. Older articles remain queryable in archive views without slowing the live board.

 

Yes. The last update timestamp lives on every Documentor row and the word count is derived from the article body or its meta. SleekView exposes both as card fields, so an editor can spot stale drafts across docs and queue them for a refresh without clicking into each one.

 

Yes. Premium add-ons attach analytics, feedback votes, and search data to every article. SleekView reads the same record fields, so premium signals like vote count, feedback ratings, and view counts continue to surface on each card while the board reflects state changes.

 

Yes. Every drag writes a state change entry into the Documentor record naming the editor, source column, destination column, and timestamp. The entry uses the Documentor metadata API so audits, exports, and downstream automations read the trail without a separate review log.

 

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