Yes. SleekView reads the synced data the Feature Upvote WP plugin populates on the WordPress side, so any working sync setup is sufficient. No additional Feature Upvote configuration is needed beyond what the plugin already requires for syncing posts and vote totals.

It depends on the sync mode the Feature Upvote WP plugin supports. Two-way sync forwards votes through the Feature Upvote API on submission, while one-way sync keeps WordPress votes local. SleekView respects the sync mode the plugin supports and never bypasses the API directly.

Yes, when the Feature Upvote WP plugin supports multiple boards. SleekView accepts a board source filter, so each SleekView block can scope to a specific Feature Upvote board, and a multi-board view can aggregate them with category pills marking the source board.

Yes. The status pill maps to the synced Feature Upvote status taxonomy, so a status change in Feature Upvote flows through the next sync cycle and the SleekView board reflects the new status on its next render without any manual reconfiguration on the WordPress side.

Yes, through the sync's existing filter. The Feature Upvote WP plugin controls which posts and boards get synced into WordPress in the first place, and SleekView only queries the rows that were synced. Private Feature Upvote content that the sync excludes never appears on the SleekView board.

Archived Feature Upvote posts are removed by the next sync cycle, and the SleekView board reflects the removal on its next cache refresh. The sync layer owns the lifecycle of the synced rows, so the board always renders the current sync state without any manual cleanup required.

No. SleekView paginates the underlying query, caches the sorted set, and uses indexed meta and taxonomy joins. A board with thousands of synced posts renders at the same speed as a smaller board because the database does the sort once per cache window.

The board keeps rendering against the synced rows already in the WordPress database, but new Feature Upvote posts and vote updates stop arriving until the sync plugin is reactivated. Existing data remains intact, so reactivating the sync later resumes the flow without any SleekView reconfiguration.