SleekView Feedback for Essential Grid
SleekView Feedback reads Essential Grid grid posts, item rows, and skin config straight from the WordPress database, then renders an upvotable card per row. Editors vote on grid polish, your team works the queue, and Essential Grid stays the canonical store.
♾️ Lifetime License available
Why Essential Grid sites need a feedback board
Essential Grid stores every grid as a standard custom post under essgrid, with skin choice, source filter, and item config in postmeta. The plugin handles content grids, lightbox transitions, and custom skins beautifully, but editor and viewer feedback usually arrives in scattered Slack pings and the occasional comment that nobody triages in the sprint window after the grid publishes.
SleekView Feedback turns an Essential Grid custom post or a dedicated requests CPT into a public style board. Each row becomes a card with the request title, the editor display name from the linked user, a category tag from a skin or layout taxonomy, a status pill, and a vote count. Editors vote on skin tweaks, and the queue orders itself by upvotes automatically.
Upvotes write straight back to the source row, so the count matches every Essential Grid export and every Sleek chart you point at the same data. A Charts view can plot top requested skins by client, a Kanban view groups items by production stage, and the Table view stays available for any creative lead who lives in a spreadsheet during grid review.
Workflow
From Essential Grid data to a board
Point SleekView at Essential Grid
Pick vote, status, category
Tie cards to grid id
Embed and let editors vote
Sample board
Sample Essential Grid feedback board
Comparison
Essential Grid admin vs SleekView Feedback
Essential Grid admin
- Essential Grid admin lists grids as a flat WordPress post table with no vote column
- Editor feedback lands in scattered Slack pings that no developer triages on time
- Status changes mean opening each grid in admin and editing the meta box by hand again
- Editors cannot rank what they want fixed, so skin decisions rely on producer hunches
- Canny and FeatureBase boards live outside WordPress and never see the grid item meta
SleekView Feedback
-
Reads any Essential Grid post type and joined
postmetaskin keys directly - Vote counts persist on the source grid post and flow into Sleek charts without drift
- Category pills come from skin or layout taxonomies with six built in colour choices
- Status badges mirror Open, Planned, In progress, and Resolved with custom labels too
- Cover image preview surfaces the grid so editors triage with fewer clicks per pass
Features
What SleekView Feedback gives you for Essential Grid
Upvotes that survive skin edits
Each upvote increments the chosen meta key on the source grid post inside one SQL update, so Essential Grid exports, custom queries, and Sleek charts all see the same total. The count matches the live front end state.
Cover aware grid cards
Each card surfaces the live grid cover image next to the title, so editors see exactly which grid is reported. No more guessing which version of a skin a colleague flagged in a chat thread last week.
Status pills for grid work
Open, Planned, In progress, Resolved, Declined, and any custom Essential Grid label renders as a coloured badge. Editors drag cards between statuses, and every move writes back to the grid row right away.
Audience
Three teams running an Essential Grid board
Editorial content desks
Editorial desks run a Grid Issues board where editors flag skin or filter problems. Top requests get triaged by the design team, and a Charts view shows which skins recur most in complaints.
WooCommerce product grids
WooCommerce shops use Essential Grid for product showcases, then add a SleekView board so owners can suggest grid tweaks. The board reads the same grid posts so reports stay tied to live grids.
Agency creative studios
Agencies maintain client grids built with Essential Grid. A shared board surfaces editor feedback across every site so the production team triages in one place rather than per client folder.
The bigger picture
Why a board beats email for grid reviews
Essential Grid handles content grids at scale, but every creative team eventually drowns in scattered editor email, skin feedback threads, and review comments nobody can rank by demand or filter by grid type. A board changes the shape of that workflow in one move. Every grid report becomes a public card with a cover image, a vote count, a skin pill, and a status badge that tells the editor exactly where their report sits in production.
The design team works an ordered queue, editors see issues acknowledged the moment they move to In progress, and the board keeps reports tied to live grids inside WordPress. Essential Grid already stores every grid and every item, so the data is right there. The board just gives editors a place to point at it before the next homepage refresh ships to production.
Questions
Common questions about SleekView Feedback for Essential Grid
SleekView reads Essential Grid data directly from the WordPress database, so any version of the plugin that writes posts and meta to the standard tables works. The free build and Essential Grid Pro expose the same schema, so the board renders the same way regardless of licence.
Yes. Voting uses the front end SleekView shortcode, so any signed in editor can click the upvote button on a board page without ever touching the admin area. Capabilities drive each role, and you can scope the board to authors and editors only if your site wants that.
Votes live on the source grid post as a meta field, so skin swaps, item reorders, and filter tweaks never touch the count. The plugin only writes to its own config keys, and the board count keeps accumulating across every change pass without drift over time.
Yes. SleekView reads the grid id on each report and renders the live cover next to the title using the standard WordPress image size your theme supports. Editors see which grid each report is about without clicking through to the front end.
SleekView marks the card as orphaned and surfaces it in a separate filter so staff can decide whether to remove the report or keep it as historical signal. The vote count is preserved either way, and you can flip a setting to auto archive orphans nightly.
Yes. Each card opens a detail panel with a comment thread powered by the standard WordPress comments table. Staff replies are flagged as official, and email notifications reuse whichever transactional mail layer your WordPress site uses for comment threads.
Yes. SleekView reads every meta key on the grid row, not just the standard Essential Grid ones, so custom skin fields for font, deeplink, or filter group can sort, filter, and group the same way as built in fields the plugin writes.
SleekView paginates results, indexes the vote column on first load, and caches rendered cards through the standard WordPress object cache. A board with thousands of grid requests and hundreds of voters renders well under a second on shared hosting infrastructure.
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