No. Ideas live as posts in any custom post type you choose, votes live as post meta or in a column on the source row, and SleekView reads those tables directly. You can reuse a post type you already have, like Suggestions or Roadmap, or create a new one in two minutes. There is no second database to back up and no sync job to monitor.

You decide per board. SleekView ties each action to a MemberPress rule, so you can let free members read and vote while only paid members post, or you can lock everything behind a paid plan. The rule check runs on every request, so a member who downgrades loses their post button at once with no extra plugin.

Past votes stay attached to the card, so historical signal is not lost. The lapsed member loses the upvote button on new cards immediately and can not post new ideas. If they renew, all rights come back instantly because SleekView reads the live MemberPress subscription status, not a cached token.

Yes. Each Feedback view is its own block, bound to its own post type or its own filter. You can have a public board for free members, a paid board for active subscribers, and a VIP board for lifetime members, each with its own categories, its own status pills, and its own gating rule from MemberPress.

Pick which statuses are public per board. Many sites show Open, Planned, and Shipped while keeping In progress and Declined for the admin view only. The status column on the source row is the source of truth, and SleekView just renders what you allow, so you control how much of the roadmap is visible.

Yes. The Feedback view ships as semantic HTML with proper button elements, keyboard focus order, ARIA labels for vote counts, and visible focus rings. It works on touch, mouse, and screen reader users out of the box, and the layout reflows from three columns down to one on phones with no extra config.

Yes. Admins see a status dropdown on every card and can move items between Open, Planned, In progress, Shipped, and Declined with one click. Public replies use post comments on the underlying idea post, so the conversation lives in WordPress and you can email subscribers when status changes.

No. SleekView renders the Feedback view from cached query results and only re-queries when a vote or status change happens. The block is lazy loaded below the fold, the JavaScript bundle is small, and there is no third party script call, so Core Web Vitals stay clean even on busy member dashboards.