Updated Understanding the interface (markdown)
Rename Reading the panel to Understanding the interface, link Settings tab This page already covered 2 of the panel's 3 tabs plus the detail dialog; the new title says so without implying it's only about badges. Added a closing section pointing at the Settings tab's own page, since this page now explicitly enumerates every tab.
Pad the vote badges to the same 222x48 canvas, visually consistent with the other table
Table again, plain markdown images with no width/height attributes this time Direct user feedback: the table scanned much better than the list. Every image already shares a uniform canvas size per group (222x48 / 92x48), so plain ![]() syntax, no HTML img tag, lets the browser use the file's own real intrinsic size instead of fighting an explicit attribute, a different render path than the three earlier attempts.
Move the bold label to the front of each bullet, for easier scanning Direct user feedback: the list read as much less scannable than the table it replaced, mostly because the label (what a reader actually scans for) used to sit after the image instead of leading the line.
Replace both badge tables with plain lists, images inline GitHub's own table-cell image handling on a narrow browser viewport kept overriding explicit width/height attributes inconsistently (confirmed: different distortion each of three attempts), likely a mobile table readability rule that doesn't apply outside a <table> at all. The screenshots already elsewhere on this wiki/README, never inside a table, render fine.
Merge: keep both the backtick section-value styling and the new community-vote section
Document the community-vote verdict pill, a separate badge next to the timer one
Updated Reading the panel (markdown)
Reorder the badge table by lifecycle: not ready, ready, HA-managed, installing
Pad the four table badges to a uniform canvas, add a Section column Different source widths in the same table column let something (GitHub's own rendering, not the HTML attributes themselves, which checked out fine in the raw page source) squeeze the widest one down to match the others. Padding every crop to the same 222x48 canvas (left-aligned, transparent fill) means every row's image is now identical in size, nothing left to render inconsistently between them. The new Section column answers the issue #16 question directly: which badges actually mean "blocked on a newer Core" (only the pause-icon one), and which can appear under either Ready to update or Postponed depending on context (the download+time one, projected vs. actually scheduled).
Add the missing no-badge row: Ready with nothing scheduled, install it yourself
Pin explicit width alongside height so the aspect ratio can't be stretched Height-only let a responsive max-width (GitHub's own mobile CSS) squeeze the widest badge (postponed_core, 222x48 natively) out of proportion. Browsers derive an intrinsic aspect-ratio from width+height together, which holds even once something else constrains one of the two.
Pin badge image heights explicitly (table: 32px, inline: 20px) Rather than relying on the source crops happening to already share a height.
Show each Updates-tab/History badge as an actual screenshot, not just text Turns the badge list into a table with a real crop of each one, plus the History tab's own auto-installed badge. Found worth doing after issue #16, where two of the four Updates-tab badges look similar enough in words alone to mix up.
Clarify that Postponed groups staging-wait and HA-version-blocked entries together Found via issue #16: a plain staging-wait entity on the always-exclude list was mistaken for one blocked on a newer HA Core, since both show up under the same Postponed section heading. Also fixes a stale claim that the version-gate detection only ever happens after a failed install.
Fix a stale citation: point to the current local brand/ folder docs, not the old brands repo
Document the optional brand/icon.png fallback for card authors
Document the new pending/failed-installs sensors
Drop the Skip button mention, Blueprint now only has Install
Add the missing install-failed example, link the real notify Blueprint
Simplify the three examples back to basics, point to a separate Blueprint for the advanced version
Add Install/Skip action buttons to the manual-install notification, one notification per entity
Add a third example: notify when something gets installed
Rename the manual-install example back to what it does, not how (both examples now share the tag+clear pattern)
Document the three native automation triggers (beta)
Clear the scheduled-install notification once it actually installs, same pattern as the manual-install example
Improve automation examples: relative+absolute time, and a second example for manual-install notifications with a stable tag and clear_notification
Fix em dashes, stale switch entity_id, and the clock-badge description
Add Reading the panel: statuses, badges, and the detail dialog's timeline