The steps
- Freeze the new brand with a note:
npx briefatto-board freeze . lead --note "Signal weight from orange to green". - Run
npx briefatto-board statusfor the pieces that still declare the old version. - Run
npx briefatto-board check . "outputs/*.html". Each leftover colour comes back as a note naming the version and role it belonged to, such as a colour that was v1's signal. - Redraw what needs it and record the new version on each piece.
Why the rendered page
The check reads what each piece paints, so a hardcoded hex, an old CSS variable and a leftover utility class all show up as the colour they produce. board status works from the guide version each piece declares, so its stale list is exact. In the Plumb example, after the signal colour changed in v2, board status marked the link card and post stale.
Tighter still
Add --consistency for a kit format, and board check lists each colour off the frozen palette with its nearest frozen colour.
Questions and answers
Does it search my source for old hex codes?
It reads the rendered page instead, which catches the old colour however it reached the page, and names the version and role it came from.
Does it repaint the pieces for me?
You decide what to redraw. Board names every leftover, and board status lists the stale pieces.
Is Briefatto Board free?
Yes. It is open source under the Apache-2.0 licence and installs with npx briefatto-board install.