WPML String Translation captures every translatable string from themes, plugins, and admin labels into icl_strings. Each translation lives in icl_string_translations with a status column that the default screen renders inside a heavy paginated list. On large sites that list crosses 100,000 rows and the built-in filters reset between visits, so a translator looking for Spanish drafts opens the same combo box every morning.

SleekView reads icl_strings joined to icl_string_translations directly and renders the result server-paginated, with one column per configured language and a status badge per cell. Saved views remember filter combinations like missing-in-Spanish-for-plugin-woocommerce or draft-since-last-release, so the morning audit loads with one click instead of rebuilding the filters.

Edits route through the WPML String Translation CRUD layer, so saving a row triggers the same cache and ICL hooks that the default screen uses. Bulk operations work the same way: mark fifty rows as complete and they all hit the WPML status update path, not a direct table write that would skip plugin logic.

WPML String Translation is the only realistic way to translate theme and plugin labels at scale, but the screen that comes with it was designed for sites with a few thousand strings rather than the hundred-thousand-row tables that real ecommerce and SaaS sites accumulate. Localization managers respond by exporting icl_strings to spreadsheets and tracking status outside the plugin. That works until a developer registers new strings, the spreadsheet drifts, and a German checkout launches with English error messages.

Reading icl_strings and icl_string_translations directly closes that loop because the saved view always reflects the live database. Translators receive scoped briefs instead of full .po dumps, agencies bill against concrete row counts, and developers can verify that every new __() string has coverage in every active language. The translation work itself still happens inside WPML and routes through the same CRUD layer the plugin maintains, so SleekView never replaces WPML's logic.

It just makes the state legible enough that nobody needs the spreadsheet anymore.