SleekView Feedback for Discourse Bridge
SleekView Feedback reads Discourse topics, the like counts, and the category taxonomy the Bridge mirrors into WordPress, ranks every topic by Discourse engagement, and renders an upvote board so high-signal threads stop sinking under Latest, Top, and the chronological category lists nobody scrolls.
♾️ Lifetime License available
Why Discourse communities benefit from an upvote view
The Discourse Bridge mirrors Discourse topics into the WordPress wp_posts table as a custom post type, with like counts stored in _discourse_likes meta, the Discourse category in _discourse_category meta, and the reply count in _discourse_posts. The native Discourse view sorts by Latest or Top, so a high-signal topic that gathers steady likes over weeks gets eclipsed by hotter recent threads.
SleekView Feedback reuses those mirrored fields. Pick a numeric column for vote weight (the Discourse like count, the reply tally, or a custom _score meta), then a status column from a WordPress topic tag, then a category column from the Discourse category taxonomy the Bridge already populates. The result is one board sorted by total Discourse engagement on a public WordPress page.
Clicking Upvote on a card calls the Discourse like API through the Bridge, which means the same signal feeds Discourses native Top view, the daily digest emails Discourse sends, and any badge logic running on the Discourse side. Status pill changes update the WordPress topic tag, so moderators triage WordPress-side without juggling two interfaces.
Workflow
From Discourse topics to a WordPress feedback board
Connect to the mirrored Discourse data
Pick the upvote column
Map status and category
Embed the board on a public WordPress page
Sample board
Sample Discourse feedback board on WordPress
Comparison
Discourse Latest tab versus SleekView Feedback
Default Discourse Latest tab
- Latest tab is chronological by last post, so popular topics sink under quiet threads with one new reply.
- Top tab needs a time filter (day, week, month) and never gives you a stable cross-period sort by total likes.
- Cross-category discovery is limited to the home view, which mixes signal across every category at once.
- Status labels are not part of the default Discourse UI, so admins maintain roadmap state through topic tags only.
- Discourse has no first-party public read-only embed for non-members beyond a category landing page link.
SleekView Feedback
- Sorts every mirrored Discourse topic by your chosen numeric column with one config click in the picker.
- Status pills write to a WordPress topic tag so moderation stays on the WordPress side as planned.
-
Reads the
_discourse_likesmeta directly, no second sync layer or custom Discourse webhook code. - Category pills reuse the Discourse category taxonomy the Bridge already populates on every topic.
- Upvotes hit the Bridge API so likes still count in Discourses Top view and the daily digest emails.
Features
What SleekView Feedback gives you for Discourse Bridge
Discourse likes as native votes
SleekView Feedback reads the like meta the Discourse Bridge already mirrors on every synced topic. No second vote system for the community to learn, no duplicate counts to reconcile, and every like collected over the lifetime of the Discourse instance becomes the sort order for the public WordPress board on the first render.
Category-aware pills
The category column maps straight to the Discourse category taxonomy the Bridge maintains, so a topic inside the Designers category lands under a Designers pill on the board. New Discourse categories appear as new pills automatically the next time the board renders without any taxonomy work on the WordPress side.
Public WordPress roadmap
Status pills like Planned, In progress, and Shipped come from a WordPress topic tag of your choice. Editing the tag updates the pill on the board, so the public roadmap stays maintained in WordPress while Discourse keeps owning conversation, notifications, and badges inside the community itself.
Audience
Where Discourse communities use the WordPress board
Public-facing roadmap
Most Discourse communities require login for full participation, but a public WordPress roadmap helps prospective members see the project is actively maintained. Embed the SleekView board on the marketing site so visitors see real Discourse topics moving through Planned, In progress, and Shipped pills.
Course-led community board
Course communities running Discourse next to a WordPress LMS point SleekView at a course-specific Discourse category. Each course gets its own feedback board powered by enrolled-student likes, so instructors see which lessons need the next iteration without skimming Discourse Latest by hand each week.
Internal moderator triage
Set the board to admin-only and filter by category to triage incoming asks by team. Moderators move cards from New to Investigating as they pick work up, and every WordPress topic tag edit feeds the existing audit trail without adding more tools to the Discourse moderation panel.
The bigger picture
Why a feedback view beats the Discourse Latest tab
Discourse is excellent for hosting deep conversation, but its default Latest tab is chronological by last post and the Top tab needs a fixed time filter. Together they make it hard to see which threads have the highest absolute signal across the lifetime of the community. A feature request that quietly gathered eighty likes over six months is invisible on the Latest tab and disappears off the Top week and Top month views, even though it has more total support than the hot thread that briefly peaked yesterday.
The moderation team gets pulled into recent threads, the product roadmap is written from gut feel, and members eventually stop posting longform asks because the platform consistently buries them. Mirroring Discourse into WordPress through the Bridge moves the data but not the rendering. SleekView Feedback completes the loop by ranking every mirrored topic by total Discourse likes on a clean board.
Discourse keeps owning conversation, badges, and notifications, but WordPress now owns a public roadmap that reflects real cumulative signal instead of the timestamp-driven views Discourse renders by default.
Questions
Common questions about SleekView Feedback for Discourse Bridge
Yes. SleekView reads the WordPress data the Bridge mirrors, so the only requirement is a working Discourse Bridge installation. Whether your Discourse instance is self-hosted or runs on the official hosted plan does not change how the Bridge stores topics and likes in WordPress, so SleekView behaves identically across deployments.
They do. The Discourse mobile app records likes through the same Discourse API the Bridge polls, so a like tapped in the app shows up on the WordPress SleekView board on the next sync cycle. Vote totals stay consistent across desktop browsers, the mobile app, and any embedded Discourse widgets across the site.
Yes. The data source picker accepts a filter on the Discourse category taxonomy and on Discourse topic tags, so a single category, a group of categories, or topics carrying a specific tag can each get a dedicated SleekView board on a separate WordPress page without code changes.
Yes, if the Bridge API has write permissions. SleekView calls the Discourse like endpoint through the Bridge, which records the like under the WordPress members linked Discourse identity. If write access is disabled, the upvote stays WordPress-side and is stored in a SleekView-native vote table without writing into Discourse.
Private category content is only mirrored into WordPress if the Bridge has been authorized for that category. SleekView respects whatever the Bridge exposes, so a staff-only category stays staff-only unless an admin explicitly enables public mirroring for it. The board never shows topics the Bridge has not synced.
No. SleekView paginates the underlying WP_Query, caches the sorted set, and only loads the rows needed for the current page. A board with twenty thousand mirrored Discourse topics serves in roughly the same time as a board with five hundred because the sort runs once and the cache covers every subsequent visit.
Anonymous voting is off by default because the Discourse API expects an authenticated user. You can enable a SleekView session-based fallback that stores guest votes in its own table and merges them on login, useful for public roadmap pages where most visitors are not yet Discourse members but should still vote.
The SleekView config travels with the source mapping. Repoint the data source picker at the new schema (BuddyBoss, bbPress, or any forum tables you can query) and the board renders again. Mirrored Discourse data stays in WordPress until you remove it, so a rollback during a migration window is always possible.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout