TranslateWP shares the TranslatePress engine and stores translations in per-language dictionary tables with names like trp_dictionary_en_us_de_de, where en_us is the source locale and de_de the target. Each row carries original, translated, status, and a block_type column for inline strings, with separate gettext tables for theme and plugin strings under trp_gettext_*. The admin offers a translation editor on the frontend and a string-list view in WP Admin, but the corpus roll-ups live outside any default screen.

That format is great for visual editing and weak for management reporting. The translation editor confirms one string at a time; the string list paginates through thousands of rows. Neither answers "how many strings are still untranslated in Spanish" or "which target language has the most reviewed strings" without running SQL across each dictionary table.

SleekView Charts reads each trp_dictionary_* table and the trp_gettext_* tables and renders four cards on top of them. A Number for total translated strings across languages. A Pie split by target language. A Bar of approval status per language. An Area of new rows per week from the dictionary tables. TranslateWP keeps owning the editor and the string detection. SleekView only reads what is already in the database.

TranslateWP already records the data any translation report needs: every original, every translated value, every status, in a per-language dictionary table. The default admin shows that data one row at a time inside a paginated list and confirms whether a single string is translated. Neither the admin nor the visual editor answers "how many machine rows are still waiting for review across all languages" or "how fast is the team converting machine to human status" without SQL across every dictionary table.

SleekView Charts reads the same trp_dictionary and trp_gettext tables and renders four cards that answer those questions in one glance. The data is already correct because TranslateWP wrote it. Charts just gives the team a dashboard to look at it.

Stale machine translations on production pages are bad for brand and SEO, and a live status dashboard makes them visible.