SleekView reads Aiomatic data directly from the WordPress database, so any version that writes jobs to the standard tables works. Both the bundled free build and any premium license expose the same jobs schema, which means the kanban renders the same way regardless of which Aiomatic plan you run.

By default a drop only updates the Aiomatic job_status column. You can extend it with a hook that calls wp_update_post on the linked target post when a card lands in the published lane, but SleekView keeps the two actions separate so accidental drags never push a post live without confirmation.

Yes. SleekView views are configuration only, so you can build one board filtered to long-form keywords and another to shopping queries from the same Aiomatic jobs table. Each user picks their default board, and admins can pin shared boards to the WordPress sidebar.

SleekView reads distinct status values on every load, so a new status shows up automatically as its own lane at the end of the board. You can then drag it into the right position, assign a color, and decide which fields the lane's cards should surface, without rebuilding the view.

No. The drag handler updates the same job_status field that Aiomatic's own admin actions update, so the cron job sees the new state on its next tick and handles retries, regeneration, and post linking exactly as it would if a human clicked the status dropdown.

SleekView respects WordPress capabilities, so you can require publish_posts or a custom capability before a card can land in the published column. Writers see the lane and can scroll it, but the drop target rejects their card with an inline message instead of silently failing.

Each lane uses a virtual scroller, so a column with five hundred cards still renders fast and stays responsive on a laptop. The lane header shows the exact count, and the filter bar at the top of the board narrows large lanes without resetting the scroll position or dropped cards.

SleekView reads and writes the existing Aiomatic tables and never adds shadow tables for job data. View configuration sits in its own small options table, so uninstalling SleekView leaves your Aiomatic jobs untouched and your post pipeline exactly where it was.