SleekView for Smodin: rewritten posts and language meta as tables
SleekView reads the posts Smodin rewrites into wp_posts and the language and rewrite-mode meta it stamps in wp_postmeta. Source language, target language and mode become sortable, filterable columns in WP Admin.
♾️ Lifetime License available
Smodin rewrites and translates. The audit view should make that visible.
Smodin sends the source copy through its rewriter and translator and writes the result back into WordPress as a post. The vendor owns the language model. WordPress owns the artifact: a row in wp_posts with title, author and status plus wp_postmeta keys describing source language, target language and rewrite mode.
The default Posts screen shows title, status, author and date, and leaves the language pair and rewrite mode hidden in postmeta. SleekView reads the same rows and the same meta directly. Source language, target language and mode become first-class columns next to title and status. Sort by target language, filter to drafts in a specific mode, or pull every rewrite into Spanish without opening any post.
Edits route through wp_update_post, so post-save hooks still fire, taxonomy updates still propagate and the Smodin integration's meta stays consistent on update.
Workflow
How SleekView reads Smodin data
Pick the post type
wp_posts column plus the source language, target language and mode meta keys it finds in wp_postmeta.
Compose the column set
Save and scope the view
Edit inline or export
wp_update_post, or export the filtered set to CSV for a freelance translator.
Sample columns
A typical Smodin rewrites table
wp_posts with Smodin's postmeta keys so source language, target language and mode sit as real columns next to status and author.
wp_posts (post_type=post) + wp_postmeta (Smodin source language, target language, rewrite mode keys)
| Title | Status | Source | Target | Mode | Date |
|---|---|---|---|---|---|
| Outdoor furniture care guide | Published | en | es | Rewrite | Apr 24 |
| Smart thermostat FAQ | Draft | en | fr | Translate | Apr 23 |
| Indoor garden starter post | Pending | en | de | Rewrite | Apr 22 |
| Solar panel comparison | Trash | en | it | Translate | Apr 20 |
Comparison
Default Smodin admin vs SleekView
Default Smodin admin
- Drafts land on the regular Posts screen with no language column
-
Source and target language stay buried in
wp_postmeta - No filter for rewrite mode or target language in the default list table
- Bulk actions are limited to standard WordPress operations
- No saved per-role view for translators, editorial or governance
SleekView
-
Reads directly from
wp_postsjoined with Smodin'swp_postmetakeys - Source language, target language and mode as sortable, filterable columns
- Inline-edit status, author and category across many rows in one pass
- Save filtered views per locale ("Spanish drafts", "French translations")
- Switch between table and kanban of the same Smodin queue
Features
What SleekView gives you for Smodin for WordPress
Language pair as real columns
Surface Smodin's source and target language meta from wp_postmeta as filterable columns. The translation queue moves from buried meta to a sortable view.
Compose precise filters
Combine status, target language and mode into a saved filter. "Spanish rewrites pending review" becomes a single named view instead of a daily rebuild.
Inline edits through CRUD
Bulk-flip status, switch authors or fix category in the row. Edits route through wp_update_post so post-save hooks still fire.
Audience
Who uses SleekView for Smodin
Translators
Filter the table to target Spanish or German and review every pending rewrite. Source and target sit in the row, so the queue runs without opening each post.
Editorial leads
Filter to Smodin-rewritten drafts and bulk-update author or category before scheduling. The mode column flags which posts were translated vs rewritten.
Governance
Filter to AI-stamped rewrites to audit disclosure coverage in localised content and catch translations that have lingered in pending past their generation date.
The bigger picture
Why Smodin output needs a localised audit table
Smodin works at the seam between editorial and localisation, two teams that usually want different views of the same draft queue. The default Posts screen flattens that into one list of titles. SleekView reads the same wp_posts rows and the same wp_postmeta keys and exposes source language, target language and rewrite mode as real columns.
Locale teams can scope to their language. Editorial can filter to rewrites that are pending review. Governance can audit AI-stamped translations for disclosure coverage.
The integration writes are untouched, the view layer simply makes the meta first-class. Same data, same plugin, very different operating posture across editorial, locale and compliance teams.
Questions
Common questions about SleekView for Smodin for WordPress
Any meta key the Smodin integration writes to wp_postmeta. The agent UI scans your installation and lists the keys present, so you pick from a real list rather than guessing names.
No. SleekView never calls a vendor API. It reads what Smodin has already written to wp_posts and wp_postmeta. If a rewrite never reached WP, it cannot appear in the table.
Yes. Target language is stored as a meta key, so you can build saved filters scoped to a specific locale, like "es", "fr" or "de".
Yes. Select rows, pick a new status and SleekView writes through wp_update_post so post-status hooks and listening plugins still fire as expected.
Yes. If a translation plugin tags posts with a locale taxonomy, SleekView reads wp_term_relationships and exposes locale as a filter alongside the Smodin meta.
Yes. Smodin can target any writeable post type, and SleekView mirrors that. Build per-type tables or one combined table scoped by post type.
Yes. Each saved view captures columns, filters and sort order, and can be gated by WordPress capability so each locale team sees only its slice.
Yes. Any filtered table exports as CSV with the same columns the view shows. Useful for handing off to a freelance translator or archiving a snapshot.
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