SleekView Kanban for GTranslate
GTranslate stores every auto-translation as a row in gtranslate_pages with state, source, and destination. SleekView Kanban reads that data, groups auto-translations by status, and lets the team drag a published card back to untranslated without leaving the admin.
♾️ Lifetime License available
Why GTranslate auto-translations fit a kanban view
GTranslate keeps every auto-translation as a row in gtranslate_pages with the state, the source, the destination, and the runtime stored alongside the slot. Related metadata lives in gtranslate_overrides. The default admin screen shows that data as a flat list sorted by date, which is fine for record lookup but slow when an overnight auto-translation has stalled and a site content lead needs to see whether it is untranslated, in progress, or has actually moved to published state.
SleekView Kanban points at the same auto-translation records and renders them as four columns: Untranslated, In progress, Reviewed, and Published. Each card surfaces the auto-translation label, the destination handle, and the runtime. When a published auto-translation needs another attempt, the team drags the card back into untranslated and GTranslate picks it up on the next pass. No second list, no manual retry through a settings screen that buries the action behind tabs.
The team can filter the board by destination, schedule, or scope, then save that filtered view as a board for one site or one client. The kanban reads from the live auto-translation records, so retrying a card here triggers the same code path that the standard run button uses, with the same hooks firing for notifications and logs.
Workflow
From the default GTranslate list to a live board
Connect GTranslate as the source
gtranslate_pages store and the gtranslate_overrides metadata so the board reads the same records as the admin screen
Group cards by the status field
Pick the card front fields
Enable drag-and-drop writeback
Sample board
Sample GTranslate board grouped by status
Comparison
Default GTranslate screen vs SleekView Kanban
Default GTranslate page
- Default screen is a flat sortable list hiding auto-translation status behind a small pill
- Updating a auto-translation status takes three clicks and a full page reload every time
- No live counts per state, so workload across auto-translations stays hidden from the team
- Bulk actions cover delete and trash but never bulk status moves across many rows
- Filtering by destination resets when navigating between pages of auto-translations listing
SleekView Kanban
-
Drag a card from
publishedtountranslatedand the status writes ba - Column counts update live so the content lead sees workload without filtering or scrolling
- Save filtered boards as URLs, one per destination, schedule, or scope across the site
- Card front maps to the auto-translation label, destination handle, runtime, and last log line
- Permissions inherit from GTranslate roles, no second auth layer to maintain inside admin
Features
What SleekView Kanban gives you for GTranslate
Status columns you can rename
GTranslate ships with Untranslated, In progress, Reviewed, Published as the four core states. Rename them to match the runbook, reorder them to match the flow, and recolor each column so the board makes published
Drag to publish not re-trigger
Every card move writes back to the same status field that GTranslate already reads, so retried auto-translations run through the same pipeline as fresh ones. No second queue, no shadow retry list, no risk of two runs racing for
Filter by destination or scope
Add a secondary filter on the destination handle, the scope, or the schedule slot and SleekView narrows the board to that subset. Ops sees the full board, the content lead sees one destination, and the manager keeps the
Audience
Where content leads use the GTranslate kanban first
Morning language triage
Open the board at 9am, scan the published column for overnight issues, drag failed auto-translations back into untranslated, and watch the in progress column drain as the next pass processes the
Pre-release language checkpoint
Before a release, fire a manual auto-translation card, watch it move from untranslated to in progress to reviewed, then promote the deploy. If the auto-translation fails, the card stays in published
Multi-site capacity view
Filter the board to one client site at a time and watch the in progress column count as a live capacity gauge. If running stays full while untranslated grows, stagger schedules before the queue
The bigger picture
Why a kanban beats the default GTranslate screen
GTranslate is a great language engine. The records hold the state, the destination map holds the targets, and the schedule slot holds the timing. What it does not give the team is a daily operating picture of which auto-translations are healthy and which are not.
The default screen is a record list, designed to inspect a single auto-translation, not to triage a column of published auto-translations at once. The site content lead ends up keeping a separate sticky note of failed runs or wiring a notification plugin just to know which auto-translation died overnight while the team slept. A kanban changes the shape of the work.
Instead of asking which auto-translations need attention today, the team sees the answer as soon as the page loads, because every published auto-translation is in the published column and every in progress one is in the in progress column. Moving a card writes the new status back to the record, so the picture stays accurate.
Questions
Common questions about SleekView Kanban for GTranslate
No. The board reads from the same gtranslate_pages store that the plugin already uses. When the team drags a card, SleekView writes the new status back to that store, so there is only one source of truth for every auto-translation on the site and every GTranslate hook still fires correctly during the run.
Yes. The column titles are display labels, not the underlying status values. Rename untranslated to waiting, published to broken, or anything else that matches how the team writes incident notes. SleekView stores the rename separately so the data still uses the standard GTranslate values.
SleekView Kanban inherits the GTranslate capability map. If a user can run a auto-translation or view the admin screen, they can drag the matching card on the board. If they only have view rights, the board renders in read-only mode and the drag handles stay hidden from each card.
Yes. Add a filter on the destination handle or the schedule slot, then save the filtered view as a named board. Each board gets its own URL so one destination board lives next to another, and a single board can stay open on a status monitor without losing the rest.
The kanban polls the GTranslate record store at a configurable interval, with two minutes as the default. New reviewed and published entries appear in the matching column within that window. Existing cards refresh in place so dragging a card never loses its position when a sibling updates.
Yes. SleekView reads every distinct value in the status field, including the extra states that add-ons register for cloud destinations and remote stores. The team chooses which of those columns to show on the board and hides the rest without removing the underlying data.
Yes. The card editor lets the team pick any field stored on the auto-translation record, including the destination handle, the runtime, and the last log line. A common layout shows the auto-translation label, destination, and runtime on the front, with the log line visible on hover for the engineer.
Yes. The plugins do not conflict because SleekView only reads and writes the same records that GTranslate already manages. Many teams use the admin screen for one-time setup and configuration, and the kanban for daily triage and retries from across the whole site at once.
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