Frontend Post Submission writes every frontend submission as a real WordPress post in wp_posts with form context stamped on wp_postmeta under a plugin-specific meta key. Post status follows the standard draft, pending, publish, and trash values so the data lives where any editor already expects to find it on the WordPress posts list.

The default WordPress posts screen lists those submitted posts alongside every other post on the site, with status as a filter at the top. That works for a site with twenty submissions a month. It stops working the moment a community or content site runs real moderation on dozens of pending posts a day, because the list view mixes editor-created posts with submitted ones and gives no signal about how deep the pending moderation queue is right now this morning.

SleekView Kanban reads wp_posts filtered by the Frontend Post Submission meta, joins to wp_postmeta for the chosen card fields, and uses the WordPress post status as the natural grouping axis. Each card shows the author, the post title, the submission date, and any custom field your form captures. Dragging a card updates the post status through the standard WordPress data layer and fires the post status transition hooks so audit logs stay accurate.

Frontend Post Submission lets visitors create WordPress posts from a public form, which is why community sites and content sites use it to expand contributor reach. The capture works well at the front of the form. The moderation side is where the default admin runs out of road.

Submitted posts land on the standard WordPress posts list alongside editor-created posts, with status as a filter at the top and no signal about how deep the pending queue is right now. A moderation team running real review on dozens of pending posts a day ends up scrolling the list, opening each post, reading it, and clicking publish or trash. A kanban view fixes that by exposing the post status as columns and the most useful fields on the card.

Pending posts cluster in one lane, drafts in another, published posts in a third, and moderators move them with one drag instead of a click into the editor. Because the board writes back through the standard WordPress data layer, every post status transition hook fires and audit logs stay honest.