✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Feedback for Advanced Themer

Advanced Themer lives on top of Bricks, layering on shortcuts, classes, and design panels. SleekView Feedback turns the bug reports and workflow ideas your users post into a sortable, upvoteable board so the next release fixes what actually slows them down.

♾️ Lifetime License available

SleekView Feedback board for Advanced Themer

From scattered Bricks workflow notes to a live board

Advanced Themer is a productivity layer on top of Bricks Builder, and most of its real value shows up only after a user runs into a Bricks quirk and wishes the shortcut behaved differently. Those moments turn into Discord pings, support emails, and half finished GitHub issues. None of it ends up sorted by impact, which means the team ships fixes that feel important to the person who wrote them down last, not the ones the wider community keeps hitting.

SleekView Feedback reads the feedback custom post type, the meta keys, or any custom table where you already collect requests. It renders one card per idea, pulling the title, vote count, status, and category from columns you already use, including wp_posts, postmeta, or a dedicated at_feedback table. Voting writes back to the same column, so the score stays in your database and not in a third party tool.

The board becomes the public roadmap. Users see which class shortcut requests are planned, which dark mode bugs are fixed, and which Bricks integration ideas are still open. Power users stop reposting the same idea because they can find and upvote the existing card, and the team finally has a single sorted list to triage on release day.

Workflow

From Advanced Themer requests to a sorted board

1

Point at the feedback source

Choose the post type, table, or saved query where Advanced Themer requests live. A custom post type, a Fluent Forms entries table, or a hand rolled MySQL table all work. Apply WHERE clauses to scope by release, area of the builder, or tag so the board only shows what is in scope for the current cycle.
2

Map vote, status, category, author

Pick the column that holds upvotes, the column with status labels like New, Planned, In progress, Shipped, the category tag for which Bricks area the request touches, and the author column. SleekView reads them fresh on every page load so the board reflects whatever moderators changed last.
3

Embed on the roadmap page

Drop the SleekView block on the public roadmap page, or use the shortcode inside a Bricks template. Visitors land on a sorted feed of requests with title, votes, author, status pill, and category pill. The board filters by category and status without a full page reload.
4

Votes write back to your database

Every upvote increments the score column on the source row. That means your existing reports, Slack notifications, and Looker dashboards keep working, because the number lives where it always did. There is no parallel SaaS database to reconcile when you ship a release.

Sample board

Sample Advanced Themer feedback board

A peek at how Advanced Themer requests look once they land on a SleekView Feedback board, mixing Bricks class panel ideas, dark mode bugs, and shortcut requests with realistic upvotes and statuses.
312 votes
Class panel: bulk rename selected classes across the page
Mateusz K. Feature request Planned
184 votes
Dark mode flicker when switching breakpoints in Bricks
@brickscraft Bug Investigating
147 votes
Add a keyboard shortcut to wrap selection in a block element
Sara L. Feature request In progress
98 votes
Save Bricks templates as Advanced Themer presets per project
@divenheim Idea New
56 votes
Color variables panel sometimes drops the last custom color
Jana P. Bug Shipped
23 votes
Export class library as a JSON file for client handoff
Andre M. Idea New

Comparison

Discord requests vs SleekView Feedback

Discord and email triage

  • Requests scatter across Discord channels, email threads, and forum DMs with no shared backlog
  • Duplicate ideas get posted weekly because users cannot search a sorted board
  • Status of each request lives in the maintainer's head, never in front of the user
  • Votes are emoji reactions on chat messages and disappear from search results
  • Release notes feel disconnected from the requests users actually filed

SleekView Feedback

  • One card per Advanced Themer request with title, votes, status pill, and category tag
  • Upvote writes back to the source column so existing reports keep working
  • Filter by Bricks area, release version, or status using any column in wp_posts
  • Public or login gated using the same block, swap with a single attribute
  • Maintainers triage from the WordPress admin, users see the same view on the front end

Features

What SleekView Feedback gives you for Advanced Themer

Sort by what users care about

Each request becomes a card sorted by upvote count by default. Filters across category and status let maintainers see only Bricks shortcut bugs, only class panel feature requests, or only items already marked Shipped, without writing a custom query in the admin.

Status pills users trust

Statuses like New, Planned, In progress, and Shipped render as colored pills next to each card. When a maintainer flips a row from Planned to Shipped in the WordPress admin, the public board updates on the next load, so the changelog feels alive instead of static.

Community moderation

Trusted users can be granted moderator capabilities to merge duplicates, retag a card, or change its category. Their actions write back to the same row, which means the source of truth stays in WordPress and never depends on a third party SaaS.

Audience

How Advanced Themer teams use the board

Public roadmap

Replace the static roadmap page with a sorted feedback view. Visitors see what is planned, what is in progress, and what shipped last week, all with vote counts so they know which items the rest of the community already pushed for.

Bricks bug triage

Filter the same data to a Bug only view for the support team. Maintainers triage by upvote count, mark items as Fixed when a release ships, and the score drives which regressions get a hotfix in the same week.

Release planning

On release day, sort by status Planned and pick the top five by votes. Move them to In progress, ship them, flip them to Shipped, and the changelog post writes itself from the card titles plus the vote scores.

The bigger picture

Why a feedback board changes Advanced Themer development

Builder plugins live or die by how closely the next release matches what users actually hit while working. Advanced Themer adds dozens of small surfaces on top of Bricks, and each surface generates its own little stream of requests, bugs, and praise. Without a sorted board, that stream turns into noise.

Maintainers triage by recency, ship features that feel intuitive in isolation, and miss the small fixes that would make the daily workflow noticeably faster. A public board changes the dynamic. Users see their own requests turn into votes, which makes them more likely to file the next one with care instead of a Discord one liner.

Maintainers see the requests next to each other, which makes it obvious that ten small papercuts in the class panel are worth more than one shiny new feature. Clients and agencies who pay for the plugin see what is planned, which makes the renewal conversation about progress and not about marketing copy. Over a few release cycles the backlog becomes a living document of what the community wants, and the release notes start writing themselves from the cards that got shipped that week.

The plugin gets better in the places it is used most, not in the places that were loudest last Friday.

Questions

Common questions about SleekView Feedback for Advanced Themer

No. SleekView Feedback reads directly from whatever table or post type Advanced Themer is already using for feedback. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. No ETL, no sync, no duplicated data, and nothing to reconcile after a release.

 

Yes. SleekView ships with anonymous voting backed by cookies, so visitors can upvote ideas and bug reports without an account. You can also require login if you want the board restricted to paying users or beta testers, and the same view handles both modes through a single toggle.

 

Each visitor gets a cookie scoped vote token per item, and logged in users are tracked by their WordPress user ID. The plugin also exposes a rate limit so a single IP cannot spam the board, which keeps the score honest without forcing a signup wall in front of new users.

 

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to a specific category, release version, or any meta key Advanced Themer already stores. You can also build several boards on different pages, each scoped to a different release or area of the builder.

 

Status is a column on the row. Maintainers update it from the standard WordPress admin or from any custom screen you already use to triage. SleekView reads the new status on the next page load and re renders the pill, so there is no extra moderation tool to learn for the team.

 

Both. Because votes write back to the source column, any list table, REST endpoint, or Bricks loop that already sorts on that column starts ordering by the new score. Several teams use the same column to drive a private internal queue and the public board, with no extra wiring.

 

Both. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a classic shortcode. Developers can also call the render function from PHP and pass a configuration array, so you can mount the board on any Advanced Themer or Bricks template without touching the page editor.

 

The view paginates server side and only loads the rows it needs for the current page. Indexed columns stay fast even on long tables. For older backlogs, scoping the board by release or status keeps both the query and the audience focused, so the page feels snappy even when the archive is enormous.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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