Two named options — the only method that labels both poles.
Inline — the default; a radio set is short, so it earns one line:
Stacked — the exception, for long labels (mk-check-group--stacked):
The radio editor: two named options
for one boolean — the only method in the Toggle family that
labels both poles, and the only one where neither state has to be the
default.
Both states deserve a word. Live and Draft, Public and Private,
Yes and No spelled out. A switch or a checkbox names one state and
leaves the other implied, which is fine for show_map and quietly
unhelpful for a field where "unchecked" means something specific that
the author has to infer.
It is also the honest choice when there is no sensible default — a cleared switch says "off"; an untouched radio pair says "not answered yet", and the difference matters in a form someone must complete.
| Label | Visibility |
| Key | is_live |
| Data type | boolean |
| Editor | radio |
| Settings | trueLabel: Live, falseLabel: Draft (Yes/No by default) |
The labels are presentation. The stored value is still true/false,
and renaming a pole later changes what authors read without touching a
single record.
This is the method that makes it possible to get the model wrong, so the
test lives here: Live/Draft passes ("is it published?"). Blue/Green
fails — two things rather than two answers, which-is-true becomes a
convention someone has to be told, and a third colour has nowhere to go.
Two named things are an options field with two choices.