No. The mirrored custom post type gives WordPress everything it needs to render threads natively, so the iframe becomes optional. You can keep it as a fallback during a transition, hide it once the SleekView board is stable, or run both side by side for a comparison period before fully replacing the iframe.

The integration plugin queues incoming webhook events into the WordPress action scheduler so spikes never overwhelm the database. SleekView reads from the mirrored post type, which means even during a vote burst the board renders from already persisted data while the queue catches up in the background safely.

SleekView writes the vote locally first, then retries the API call through the WordPress action scheduler with exponential back off. If the central API is unreachable, the local board still reflects the upvote, and the queued retry pushes the change up to GraphComment as soon as the connection recovers.

Yes. Each WordPress site keeps its own mirrored custom post type filtered by the GraphComment thread identifier, so a SleekView board per site only renders threads that belong to that property. The moderation team still sees the unified view in the GraphComment dashboard regardless of which site a thread originated on.

No. The integration plugin can backfill the mirrored post type from the GraphComment REST API on the first run, so every existing thread, vote count, and status is brought into WordPress before the board goes live. After backfill the webhook keeps the mirror current with every new event from the hosted side.

Yes. The webhook fires on every moderation event, which updates the mirrored post type immediately. SleekView's live mode then pushes that change over websockets to anyone currently viewing the board, so readers see status pills update in seconds rather than waiting for a manual page refresh themselves.

Yes. The SleekView toolbar includes a CSV export that respects the current filter, so you can pull the top fifty threads, every Open thread tagged as a feature request, or any other slice into a spreadsheet in one click. The export carries titles, vote totals, authors, statuses, and category tags.

Yes. The mirrored custom post type and the webhook integration are independent of SleekView. Removing the board only removes the rendering layer, so every mirrored thread, vote count, and moderation state stays in WordPress for any future board, report, or alternative front end you choose to build later.