Variables can be a mapping, and template cards can be nested
Two fixes landed in the card that these pages had backwards.
Variables written as a mapping used to lose every key after the first, so the
wiki told people to use a list and Troubleshooting listed the mapping form as a
cause of stray placeholders. Both shapes now work everywhere, so Variables shows
both, Troubleshooting drops that cause, and the reference says so.
Template cards were only found at the top level of a view, so Defining Templates
saying 'any view' was not quite true for one tidied away inside a stack. It is
now, and the page says as much.
The card editor's message for a variables block that is neither shape changed
with it.
Document the card in full: 18 pages with worked examples and screenshots
Covers installation, a five-minute quick start, the two ways to define
templates, all four content types (card, badge, row, element), variables
and their substitution rules, cross-dashboard template sharing,
visibility conditions, styling, the visual editors, a configuration
reference, ten recipes, a migration guide and troubleshooting.
Screenshots are captured from a real Home Assistant instance.