No. SleekView Feedback reads the existing docs posts, post meta, and section taxonomies that weDocs already writes. Article feedback rows live in the meta or feedback table weDocs already provisions. There is no separate roadmap table, no sync job, and nothing to migrate. Upvotes are stored as numeric meta on the same row your tech writers see in the admin.

Yes. The Feedback view inherits the same query filters as SleekView Tables and Charts. You can restrict by article status, section, language, or any custom meta. Most weDocs teams expose only feedback tagged Roadmap or Doc improvement with statuses Planned, In progress, and Shipped on the public board and keep the rest internal.

SleekView tracks upvotes per browser through a signed cookie and per user ID for logged-in WordPress users. You can also require an account before voting if you want stricter dedupe. Vote totals stay consistent across pageloads and devices for known users, with cookie-based dedupe protecting anonymous readers from accidental double-counting from another tab open.

A separate roadmap tool is a different product with its own database, login, and pricing. You sync docs feedback across, then maintain two sources of truth. SleekView Feedback reads weDocs data live, so the public board, the article admin, and any tech writer dashboards always agree on totals. There is nothing to sync because there is only one source of truth in WordPress.

Yes. Any numeric meta key can act as the vote column, any taxonomy or text meta can be the status, and any taxonomy or meta can be the category. The SleekView block exposes a dropdown for each role so you map the weDocs columns once through the block UI and never touch the underlying template to change which fields render later on.

By default upvotes update the meta silently to avoid notification spam in busy tech writer inboxes. You can opt in to firing a standard WordPress action on each upvote that you can hook into your weDocs author notification if you want writers to see live demand, or threshold it to alerts every ten or fifty votes for a calmer notification cadence.

Yes. SleekView lets you scope the query to one or many terms in any weDocs section taxonomy, plus any language taxonomy if you use a multilingual setup. Each board is a separate block on a separate page, all reading from the same underlying docs store with their own filter and column mapping configured for that audience cleanly.

Because SleekView Feedback reads whatever query you point it at, you can swap the source from docs to a different post type or table without rebuilding the board. The cards, badges, votes, and filters stay intact. You re-map the column roles in the block settings, and the public URL stays the same for visitors and search engines alike.