About this block

String Editor Panel is the focused review surface for one translation at a time. The key strip carries onboarding.invite_prompt in monospace with a namespace badge and a Fuzzy status. Below it the source English renders its inviteCount placeholder as a mono chip and adds the developer context line, then a machine suggestion row offers its own French take with a Use suggestion button. The target Textarea holds the translator draft with a character counter, 51 of 80, and a placeholder check reading 1 of 1 present. Previous and next buttons in the header step through the queue and the footer pairs Skip with Save and next.

The panel is one card with ruled sections, so each zone reads separately: key, source, suggestion, target, actions. The footer states the guardrail plainly: placeholders must appear unchanged or the save is blocked.

When to use

Reach for this block as the editing surface a translator lands on after picking a row in the translation table. Wire previous and next to your review queue, prefill the suggestion from your machine translation provider, and validate placeholders on save exactly as the footer promises.

A natural flow around it on an Application Pro page:

Before

• Translation table
• Translation progress card

After

• Locale preview card

What you can display

One strong use is the fuzzy review queue for machine translations. Other editor panel shapes:

• Missing strings first. The queue scoped to untranslated strings with an empty target draft.
• Plural forms. Two stacked targets, one and other, for languages with plural rules on the count token.
• Reviewer mode. The same panel with Approve and Request changes replacing Save and next.

Tip: keep the placeholder counter right under the textarea, a broken token in production is the bug users screenshot first.