No. SleekView reads whichever WordPress source you point it at and the Richpanel for WordPress plugin can stay on its default install. You only need to expose the feature request and bug report data as a custom post type, custom table, or any other WordPress source SleekView can query, then map the vote, status, and category co

Upvotes write back into the exact column you chose during board setup, whether that lives in wp_postmeta, a custom table you created for feedback items, or even a row in wp_options for prototyping. The source row stays the single point of truth for vote counts across every surface.

Yes. You can tag every item with a category like Feature request, Bug, UX, or Performance, and assign each category a distinct pill color from the supported palette. Filters above the board let visitors narrow to a single category, or compose with status filters to view only Open bugs or only Planned feature requests.

Status is whichever value sits in the column you mapped during setup. Common values are Open, Planned, In progress, Shipped, and Declined. Each gets a stable color from the palette so the meaning stays consistent across the board, and changing a status in the source row updates the pill on the next load.

Yes. The board tracks votes per visitor using a combination of the logged in WordPress user ID where available and an anonymous session token for guests, so the same person cannot inflate a feature request by mashing the button. Operators can purge the vote ledger if they need to reset signal during testing too.

Yes. The board reads from WordPress, not from Richpanel servers, so even if the cloud console is unreachable the feedback page continues to render with the latest known data. Upvotes still write into your local source. Only the Richpanel chat or ticket surface itself depends on the upstream service being available.

Both. The shortcode renders on any public WordPress page or post, which is the common pattern for a customer-facing roadmap or feature request hub. You can also pin the board as a SleekView page inside the WordPress admin for internal triage, where only logged in agents see Open and In progress items.

The board always sorts by current upvote count, with a stable tiebreak on the item ID. There is no recency boost, so a fresh item only outranks an older one once it accumulates more votes. That is intentional: it forces the board to reward real signal rather than recency theater, which keeps the top items honest.