About this block

Translation Table is the string editor for a single target locale, French (fr-FR), showing 5 of 8 strings translated. Each row carries the key in monospace, billing.upgrade_cta and onboarding.invite_prompt for example, the source English beside it, the French translation or an italic Missing placeholder, and a status Badge: Translated in secondary, Fuzzy and Missing in outline. A Pencil button on every row opens the edit flow. The footer draws the hard line: missing strings fall back to English at runtime, never to a blank, and fuzzy strings are machine-translated and need a human review before shipping.

The strings array is typed with a TranslationStatus union so every row carries the same shape. Two rows have an empty target string, surfaced as italic Missing copy rather than a blank cell.

When to use

Reach for this block on the localization management page of a developer or admin settings area, wired to your translation store and an edit modal. Scope one table per target locale and pair it with the progress card above.

A natural flow around it on an Application Pro page:

Before

• Translation progress card

After

• Translation progress card
• Settings shell

What you can display

One strong use is the per-locale string review queue. Other translation table shapes:

• Filtered to missing only. The same table scoped to status missing so translators see only their work.
• Fuzzy review queue. Filtered to fuzzy with an Approve action alongside Edit for machine translations.
• Namespace scoped. Table filtered to a single namespace prefix, nav.* or billing.*, for focused work.

Tip: never leave a cell blank for a missing string, the italic Missing label plus the footer note stop the support ticket before it starts.