Companion to the change adding di to the btravstack landing page, which needs a package accent for it.
The problem
docs/.vitepress/theme/custom.css sets --accent: #2a62b8 — the logo's deep blue. The reasoning in that comment is right and stays right: blue is plumbing, and the hex should be the logo's own so chrome and artwork stay one color. Only the specific blue is wrong.
The landing paints each package name in the raw --pkg-* token against --card (#100F12). #2A62B8 measures 3.22 there. The four established accents sit at:
| token |
hex |
dark card |
darkened 30% on white |
--pkg-unthrown |
#3FB0A5 |
7.25 |
5.01 |
--pkg-amqp |
#FF6600 |
6.51 |
5.53 |
--pkg-entity |
#C8871F |
6.32 |
5.63 |
--pkg-temporal |
#6B76F2 |
5.00 |
6.75 |
#2A62B8 |
|
3.22 |
9.46 |
So it is not marginally below the band, it is well outside it — and design.md records contrast: pass for that page.
The fix
#3E7FD4 — still the logo's own blue, just the lighter one already painted on the barrel rim, the plunger and the needle hub. 4.72 on the dark card, 7.10 as darkened text on white. It keeps the "one color across chrome and artwork" argument intact, because it is a hex the mark already uses.
--pkg-di: #3E7FD4 has landed in @btravstack/theme; this issue is di's half, so the docs site and the landing don't show two different blues for the same package.
What moves
--accent in docs/.vitepress/theme/custom.css, and the hex named in the comment above it.- Anything in
docs/public/icons/ that hardcodes #2a62b8 rather than deriving from the token — worth a grep, since that is how it went for entity.
The logo itself needs no change: #2A62B8 stays in the artwork as the deep blue of the thumb rest and plunger rod, where it is a shading value rather than a text color.
Companion to the change adding di to the btravstack landing page, which needs a package accent for it.
The problem
docs/.vitepress/theme/custom.csssets--accent: #2a62b8— the logo's deep blue. The reasoning in that comment is right and stays right: blue is plumbing, and the hex should be the logo's own so chrome and artwork stay one color. Only the specific blue is wrong.The landing paints each package name in the raw
--pkg-*token against--card(#100F12).#2A62B8measures 3.22 there. The four established accents sit at:--pkg-unthrown#3FB0A5--pkg-amqp#FF6600--pkg-entity#C8871F--pkg-temporal#6B76F2#2A62B8So it is not marginally below the band, it is well outside it — and
design.mdrecordscontrast: passfor that page.The fix
#3E7FD4— still the logo's own blue, just the lighter one already painted on the barrel rim, the plunger and the needle hub. 4.72 on the dark card, 7.10 as darkened text on white. It keeps the "one color across chrome and artwork" argument intact, because it is a hex the mark already uses.--pkg-di: #3E7FD4has landed in@btravstack/theme; this issue is di's half, so the docs site and the landing don't show two different blues for the same package.What moves
--accentindocs/.vitepress/theme/custom.css, and the hex named in the comment above it.docs/public/icons/that hardcodes#2a62b8rather than deriving from the token — worth a grep, since that is how it went for entity.The logo itself needs no change:
#2A62B8stays in the artwork as the deep blue of the thumb rest and plunger rod, where it is a shading value rather than a text color.