docs: write up everything that arrived after v1.1.0
Six pages, with the release on each new heading the way the v1.1.0 ones were.
Variables gains the stand-ins - `default:` and `or:`, what counts as a gap, and
how they differ from `?`, which removes the key rather than filling it - the
`json` step, and the three resolvers that complete the set: `floor`, and the
`area_id` and `device_id` that are for building an entity id rather than showing
a name.
Repeating a Template gains the half of it that was missing: narrowing by device
class, integration and `exclude`; ordering, `limit` and the `total` that outlives
it; `range`; the `empty` card; reaching into a nested item; and a card per area
that knows what is in it, which is the shape people actually build and now has a
screenshot of it working.
Styling gains `gap` and the `grid_options` a template can declare once, both with
a note on why they are custom properties rather than rules.
Visual Editors gains what the editors learned to do - say what a repeat matches
before you save it, warn that something uses this template, reorder the declared
variables, duplicate, move a dashboard off the original card's names, and start
from the built-in library - with screenshots of each.
Troubleshooting gains the template that uses itself, which used to take the tab
with it, along with did-you-mean, `debug`, `strict` and the note about a repeat
that matched half the house.
The reference tables carry all of it, including a table of what every copy of a
repeat is given and where it comes from.
Every internal link and anchor across all 22 pages checks out.
docs: show the five pages that had no picture on them
docs: write up the v1.1.0 features, with the release on each new heading
New headings now carry the release they arrived in, the way TaskMate's wiki does, so
you can tell from the page whether the version you are running has the thing it
describes. Only headings for things that are actually new are tagged - the pages that
predate the convention are left alone.
Covers what has landed since v1.0.0: asking Home Assistant what an entity is called,
optional placeholders, escaping brackets, repeating over the registry, numbering
copies, leaving out a copy with nothing to show, fit: contents, shared dashboard
defaults, and the Result panel in the card editor.
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 describing variables, repeating a template, transforms and where used
Five things landed in the card that the wiki did not cover:
- a template can describe its variables, so cards using it get real controls
- a card can render its template once per item with for_each
- a placeholder can ask for its value in a different shape with |slug and friends
- the template editor can turn a card you already have into a template
- the template editor lists everywhere a template is used
Two new pages, Describing Variables and Repeating a Template, since both are
whole topics rather than paragraphs. Transforms went into Variables next to the
other placeholder forms, and the two editor actions into Visual Editors beside
the tabs they belong to. Configuration Reference, Troubleshooting, Home and the
sidebar follow.
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.