No. SleekView reads the trello_card CPT that Trello for WordPress mirrors locally, and any upvote increment lands on a WordPress postmeta key. Status pill edits update the Trello list id meta, which the Trello for WordPress connector can mirror back during the next sync cycle.

Yes. The Upvote button supports guest votes with a per-IP and per-session lock to keep counts honest. If you would rather restrict votes to logged-in users or specific roles like Editor or Stakeholder, you can flip that in the view settings without touching any code at all on the WordPress site.

You map the synced Trello list id as the status pill source when you build the view. SleekView shows a colored pill for each list, and any card without a list simply renders without a pill rather than blocking the card from showing on the board at all in public on the site.

Yes. SleekView reads whatever Trello for WordPress has mirrored. Multiple boards, multiple Trello accounts, and archived boards can be filtered into separate saved views, so a marketing page can show one board and a support page can show another without conflicting chips at all.

Yes. Every saved view has its own role and capability scope, so you can publish a public client feedback board on an agency page and a separate internal triage queue that only PMs and Admins can see. Both views share the same Trello data underneath the surface today.

When the underlying trello_card record is removed by the next sync, SleekView removes the card on the next refresh. If the card is archived rather than deleted, the card disappears from the public view but the upvote meta is preserved on the archived row for export and history.

Yes. SleekView views render as shortcodes, Gutenberg blocks, and short HTML snippets. Most agencies drop a Top votes view scoped to a single client board inside a password-protected portal page so clients see the upvote board without needing a Trello seat at all today on the site.

SleekView paginates and sorts at the database level rather than loading every trello_card into memory, so a sync history with tens of thousands of synced cards still renders the top of the feedback board in well under a second on a normal shared host with default caching enabled today.