Yes. Block snippets and content snippets are stored in the same snippets table as PHP, CSS, and JS snippets, just with a different scope. SleekView reads them all and lets you filter by scope so block snippet authors and PHP authors can each see only the rows that concern them.

You add one numeric column or meta key during setup, and SleekView increments it on every vote. Most teams add a single votes integer column; teams that want audit trails add a sibling table with one row per vote so they can also track voter, timestamp, and an optional comment.

Yes. Map the status pill directly to the active column and the pill flips whenever the snippet is toggled on or off. You can also map status to a custom workflow field like review_state with values such as draft, reviewing, shipped, and deprecated for a richer process.

Conditions live in their own table linked from the snippet row. SleekView can show the linked condition name on the card and filter by it as a facet, so you can run a board that only shows snippets attached to a given condition or hide condition driven snippets from a public board entirely.

Yes. Each SleekView block accepts its own source query, so you can run an internal engineering board on every snippet, a public board on a curated tag, and a per client board scoped by tag or scope. All boards read the same library, just with different filters and permissions.

Code Snippets Pro cloud sync replicates the snippet body and metadata, including any custom columns you add. If you sync the vote column, votes propagate; most teams choose to keep votes per site, since a vote on a staging site is rarely meaningful on production.

Yes. You can allow anonymous voting with rate limiting based on IP and cookie, which is fine for public roadmaps. For client portals, most teams require login and lean on the standard WP role system to scope which boards each client account can read and vote on.

GitHub and Linear are great trackers but live outside WordPress, so the link between an issue and the actual snippet row is informal. SleekView Feedback runs on top of the Pro snippets table itself, so a vote, a flag, or a status change stays attached to the snippet and travels with database migrations and cloud sync.