No. SleekView Feedback reads the compact_audio_player post type and option meta that Compact already writes. There is no separate roadmap table, no sync job, and nothing to migrate. Upvotes are stored as numeric meta on the same row your Compact reports chart against, so totals stay aligned across surfaces.

Yes. The Feedback view inherits the same query filters as SleekView Tables and Charts. You can restrict by player status, skin, playlist, review state, or any custom meta. Most Compact teams expose only player instances tagged Roadmap or Bug with statuses Planned, In progress, and Shipped on the public board and keep drafts hidden.

SleekView tracks upvotes per browser through a signed cookie and per user ID for logged-in WordPress users. You can also require a fan account before voting if you want stricter dedupe. Vote totals stay consistent across page loads and devices for known users, with cookie-based dedupe protecting anonymous voters from double counting.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync players across, then maintain two sources of truth. SleekView Feedback reads Compact data live through WordPress, so the board, the player editor, and the Compact admin always show the same numbers. There is one source of truth.

Yes. Any numeric meta key can act as the vote column, any taxonomy or text meta can be the status, and any taxonomy or meta can be the category. The SleekView block exposes a dropdown for each role so you map the Compact columns once through the block UI and never touch the underlying template to change which fields render.

By default upvotes update the meta silently to avoid spamming busy producers. You can opt in to firing a standard WordPress action on each upvote that you bridge into Slack or email if you want owners to see live demand, or threshold it to alerts every ten or fifty votes for a calmer notification cadence.

Yes. SleekView lets you scope the query to one or many terms in any taxonomy, so you can run a board per skin, per playlist, or per genre. Each board is a separate block on a separate page, all reading from the same underlying Compact store with their own filter and column mapping configured for the audience that sees it.

Because SleekView Feedback reads whatever query you point it at, you can swap the source from compact_audio_player to a different post type or table without rebuilding the board. The cards, badges, votes, and filters stay intact. You re-map the column roles in the block settings, and the URL stays the same for listeners and search engines alike.