Yes. Moving a card calls wp_update_post, the same function the editor uses, so transition_post_status hooks fire normally and the GrowthBar plugin meta link stays intact through every move. GrowthBar keeps syncing the target keyword data to the WordPress editor side without any extra plugin glue.

SleekView reads the WordPress posts table directly, filters to posts with a GrowthBar document meta key, and joins the GrowthBar target keyword and volume hint meta in the same query. You pick the posts table as the source, choose the stage field to group by, and SleekView renders one card per post.

Yes. SleekView ships with role-based permissions, so SEO leads can have a single page that holds the GrowthBar pipeline board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so writers cannot publish their own drafts without an editor's approval move.

Custom keyword fields appear automatically because SleekView reads distinct values from the chosen field. You can group by any custom field, show it on the card front, and decide whether editors can drag cards between any two columns or only along the official GrowthBar pipeline path for the team.

Yes. The target keyword is read from the post meta saved by the GrowthBar plugin and shown on each card front. Editors can sort columns by keyword volume so drafts with the highest SEO value stay near the top, and any custom keyword field added by the team also lands on the card front.

Dragging never deletes data and never touches the GrowthBar plugin meta link. It changes the post_status field SleekView is grouping by, which matches what the editor does through the Publish dropdown. The GrowthBar document ID stays in post meta so the plugin keeps syncing target keyword data.

Yes. Each card can show the time since the post was created or last modified, so an outline that has been sitting for weeks looks visibly different from a fresh one. Sort options can also place the oldest cards at the top of every column so stale outlines never silently drift out of view.

No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on the posts table for the status and GrowthBar meta filters. Sites with tens of thousands of GrowthBar-linked posts stay responsive because heavy fields are only fetched for cards on screen.