Loco Translate is unusual in the WordPress translation ecosystem because it stores nothing in the database. Every translation sits in a PO file inside wp-content/languages, theme directories, or plugin folders. That makes the data portable and turns coverage reporting into a directory walk. The default admin groups projects by source — Author, Custom, System — and shows per-project numbers, but offers no sortable cross-project chart.

SleekView Charts indexes the PO file footprint and exposes project, project_type, language, translated_count, total_count, and last_modified as chart inputs. Four cards cover the meeting: a total-translated KPI, a coverage-by-language bar, a project-type donut, and a last-modified area showing when language packs were last touched.

The string editing work still happens inside the Loco editor, which is the right place for in-context translation. SleekView Charts handles the audit and prioritisation that file-based tools were never designed to support at scale.

Loco Translate's filesystem design is a strength for portability, version control, and multilingual deployments. It is also the reason cross-project audits are slow in the default admin. The per-project screen shows coverage one project at a time, so the answer to which-language-packs-need-work-before-Friday's-deploy is gathered by clicking through a dozen theme and plugin entries.

Charts change the rhythm. A localization manager sees the highest-leverage gaps on one screen: WooCommerce missing 600 strings in French, Storefront at 65% in Spanish, Yoast SEO not started in Italian. Maintainers spot the PO-versus-MO drift that causes mid-flow English to leak onto a German checkout.

The string editing still happens inside the Loco editor, where the in-context UI is a better fit. The audit and prioritisation move to a place where they can be done at speed.