Yes. SleekView reads the Memberful plan meta that the official integration syncs onto each user, so you can gate the board, the post action, and the upvote action behind any plan including monthly, annual, and founding member tiers. When a plan changes or lapses, SleekView reflects the change on the next page render without any custom code on your side.

Yes. The upvote action can be gated independently of the read and post actions. A common setup is to let all paid plans read and post but only allow founding tier subscribers to vote on a private roadmap board, which keeps the signal focused on the people most committed to the publication.

Upvotes write to the meta column you bind during setup, on the same source post that the card came from. Any custom SQL query and any analytics tool that reads WordPress meta can read the vote count without extra wiring, since SleekView treats the source row as the system of record and not its own database.

No. SleekView paginates the board, caches the source query, and runs the vote write through the WordPress REST API rather than reloading the page. Even a board with tens of thousands of cards renders in a single fast query, and the only cost on a vote is one meta update on the source row.

Yes. SleekView ships with a small token list for spacing, radius, and accent colors, all of which can be set in your theme without writing custom CSS. The Feedback view inherits your site fonts and link colors automatically, so a board placed inside a subscriber dashboard or on an episode page looks like part of the publication.

It does. You can run a public board open to free plans, a paid board open only to active plans, and a founding board open only to founding members, all on the same WordPress install. Each board is a separate SleekView instance with its own source query and its own gating rules.

Each card has a status dropdown that writes the new value to the meta column you bind during setup. Subscribers see the new status pill on their next visit, and any opt-in notification flow can fire on the change since the source row update goes through standard WordPress hooks. Shipped cards stay searchable so subscribers can see what you delivered.

Yes. Most external tools export their cards as CSV with vote count, status, category, and author. SleekView pairs with the standard WordPress importer to create one post per card in the source post type you choose, and once the import finishes the existing vote counts and statuses render on day one without any further mapping on your side.