About this block

Locale Coverage Matrix crosses 7 string namespaces with 5 target locales, 480 strings in total. Every cell shows the percent translated beside a small square that darkens as coverage climbs: solid at 100%, faded through the 80 and 50 bands, and outlined when an area needs work, like Korean emails at 22%. Namespace rows carry their string counts, nav at 42 up to settings at 120, and the All namespaces row totals each locale, Spanish at 99% down to Korean at 47%. A legend under the panel decodes the four bands and the header offers an Export coverage button.

Locales are typed with a LocaleCode union and every namespace carries a full Record of coverage values, so a missing cell is a type error rather than a blank. All percents use tabular-nums and the grid scrolls horizontally on small screens instead of wrapping.

When to use

Reach for this block on the localization dashboard when per language bars are not enough and the team needs to see which area of the product drags each locale down. Wire the cells to your translation store grouped by namespace prefix and keep the band thresholds in one function so the legend never drifts from the cells.

A natural flow around it on an Application Pro page:

Before

• Translation progress card
• Settings shell

After

• Translation table
• String editor panel

What you can display

One strong use is the namespace by locale coverage grid. Other matrix configurations:

• Feature areas as rows. Swap namespaces for product areas so each owner sees their own surface per locale.
• Release gate view. Only the locales in the next release train, with the gate percent marked per cell.
• Reviewed versus translated. Two numbers per cell when approval lags behind raw translation volume.

Tip: the outlined band is the call to action, sort the translator queue by the lightest cells and the matrix fills itself in.