No. SleekView reads the rewrite rows your existing Smodin WordPress connector already saves locally, so anything stored in the rewrites table or its meta keys is fair game. There is no second SaaS account to provision, no extra API token to manage, and no separate billing line to pay.

You pick the column at setup. Most teams add an integer votes column on the rewrites table or attach a meta key tied to each rewrite ID. SleekView reads and increments that value on click, so the editor signal survives Smodin connector updates and plugin reactivations and exports.

Yes. The card layout supports two body sections, one for source and one for rewritten output, and an editor can expand each one independently to read the full text. A diff highlight option underlines the words that changed between source and output for fast review by anyone.

Every click runs through a SQL increment statement that is safe under concurrent writes, so two simultaneous upvotes always land as plus two and never as plus one. The card subscribes to the new count and updates in place without a full page reload, so both voters see the right total.

Yes. The board accepts manual items, which is the standard path for language pair requests, rewrite mode ideas, and tone preset suggestions. The card carries the same status pill, the same category tag, and the same Upvote button as a real rewrite row, but it points at a manual record.

If the rewrites table carries a site or brand identifier column, SleekView can filter the view to a single site or expose a site pill so editors can switch on the fly. Each site can carry its own language pair palette, its own status list, and its own access rules so teams stay separate.

Yes, as long as you keep the columns you mapped at setup. SleekView does not own the schema, it reads what you point it at, so a connector update that adds new columns simply gives you more fields to surface on cards. Rename a column and you remap it in the view config quickly.

Yes. Place the SleekView block on a private page behind a login wall and grant the editor role read access. Localization editors see the cards, vote on rewrites, and post pair requests through that page without ever loading the WordPress admin or touching the full editor surface.