MultilingualPress treats every language as a separate site in a WordPress multisite network. Content relationships between sister posts live in mlp_content_relations with a relationship_id joining rows in different blogs, and language metadata lives in mlp_languages. The plugin's metabox lets an editor link a single post to its siblings, but there is no network-wide audit of coverage.

SleekView reads mlp_content_relations, joins it against each blog's wp_posts, and produces one row per relationship with a column per network site. Each cell shows the linked post's status on that site, or a missing badge if the relationship does not include a translation for that language yet. Saved views remember which post types and which subset of network sites a team is actually responsible for.

Edits route through the MultilingualPress API where supported, so creating or updating a relationship from a SleekView row triggers the same hooks the metabox does. Network admins keep one consistent dashboard instead of switching site context for every check.

MultilingualPress's design of one site per language scales technically because each language gets its own database tables and its own caching behaviour. The same design fragments operational visibility because every admin screen lives inside a single site's dashboard. A network with five language sites and four post types has twenty grids to check, and the relationship metabox only ever sees one post at a time.

Reading mlp_content_relations directly closes that gap. A network admin can see across every blog without switching contexts, a translator can pull a CSV of exactly the relationships missing on their site, and an editor can confirm pre-release coverage in one view. The plugin keeps doing what it does well at the schema level, and the audit layer is what the default admin never offered.