How do I find the keys I need to work on?

A project with three thousand keys is unusable until you can cut it down to the forty you are actually working on. The editor's toolbar exists for that, and the useful trick is that you can save the combination once you find it.

Search #

One box, top of the editor: Search keys, source text, or visible translations…

It matches three things at once:

the full key path, including its namespace
the source-language text
the translated values in the language columns you have visible

That last one is why searching for a Turkish phrase finds its key: the Turkish column has to be on screen for its values to be searched.

Matching is plain substring, case-insensitive. login finds auth.login_button; lgn finds nothing. Type the piece of the key or sentence you actually remember.

Only missing #

The one filter you will use daily is the Only missing switch: it keeps only keys that are missing at least one translation in your visible languages. Combined with a single visible language, that is your worklist for that language.

Missing first is the softer version — nothing is hidden, the gaps just sort to the top.

Namespaces #

The namespace filter is a multi-select, not a single choice: tick auth and checkout to see both. Select all and Clear are there for when the list is long. Filtering happens on the server, so narrowing by namespace makes a big project faster to load, not just tidier.

Grouping #

Three ways to organise what survives the filters:

Mode	What it does
Namespace	One section per namespace
Group prefixes	Splits on the shared dot-prefix — `auth.login.title` and `auth.login.subtitle` land in an `auth.login` group
Rules	Your own groups, written as `Name: pattern` — e.g. `Widget: ^widget\.`

Prefix grouping is the one to reach for in a flat namespace where the real structure lives in the key names.

Languages on screen #

You choose which language columns are visible, and that choice feeds both the search and the Only-missing filter — the editor only knows about what it can see.

Order them by Display order (the order set on the Languages page) or by Least complete, which puts the language needing the most work on the left.

Save the view #

Once a combination is right, name it and save it. It keeps the search, the namespace selection, the grouping mode, the switches, and the visible languages — so "Turkish, only missing, checkout namespace" is one click next time instead of five.

Saved views are the reason not to bookmark URLs for this: they carry the parts a URL does not.

What a shared URL does carry #

The editor writes some of its state into the address bar, so a link reproduces roughly where you were:

Code

?searchQuery=login&filterNamespace=auth&activeLanguage=tr

selectedKeyId is in there too, which is the useful one for pointing a colleague at a specific key rather than a general area.

How do I use the translation editor? — editing, not finding
How do I manage languages and track coverage? — where display order comes from