WP Crowdfunding stores every campaign as a WooCommerce product with the crowdfunding product type. Each row lives in wp_posts with a post_status of draft, publish, or pending, plus metadata in wp_postmeta for the funding goal, deadline, raised amount, and project lead. Pledges land in wp_woocommerce_order_items with the matching order rows in wp_posts. The plugin's campaigns screen shows everything as a sortable list, which makes it hard to see how many projects are queued behind a launch versus already funded.

SleekView Kanban reads the same campaign rows you query with WP_Query or the WooCommerce REST API. Pick post_status as the group column and every campaign becomes a card slotted under Draft, Live, Funded, or Closed. Card fronts show the campaign title, the funding goal, the raised amount, the deadline from postmeta, and the project lead, so reviewers see the shape of the funding pipeline without opening individual campaign pages one at a time.

Dragging a card from Draft to Live runs the same publish flow WordPress uses internally, which fires transition_post_status and the WP Crowdfunding listeners that send launch notifications to followers. Funded campaigns transition with the plugin's payout helpers, closed campaigns archive the pledge data, and the WooCommerce hooks for related products refresh, exactly as they would after a manual publish in the admin editor.

Crowdfunding platforms juggle dozens of campaigns at every stage of life. Some are pitches that need vetting, some are live campaigns racing toward a deadline, and a steady stream are closed campaigns that need payouts or refunds. The default WP Crowdfunding screen treats them all the same, which means project leads chase status updates in Slack and finance keeps a spreadsheet of which payouts have cleared.

The disconnect shows up in the worst places. A live campaign that quietly stalled does not get a marketing nudge because nobody is watching the Live column. A funded campaign sits without a payout for a week because finance assumed the plugin handled it automatically.

A kanban view that reads and writes the same campaign product rows the storefront reads keeps the team and the funding state honest. Every drag is a real status change, every column count reflects the real funding pipeline, and the cards themselves carry enough context for a project lead to triage their portfolio without opening a single campaign edit screen.