carlos / contra Public

design: the overprint was uppercasing the build hash

Two from the third capture. The footer's serial printed centred, which
no ticket does, and the caps that make the overprint an overprint were
being applied to the build hash inside it — so the page rendered
0D6ACAF for a value that is 0d6acaf in git, in `carlos channels` and in
GET /api/version.

That is not a styling preference. The footer exists to say which build
you are looking at, and it was the one element on the page misreporting
a value it was put there to report. The caps stop at the serial.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Paul Campbell pushed by paul@keymail.dev 1 month ago 0292a4f84ad338a9e2e36d848308d3ce76a30b95 parent 0d6acaf

1 file changed, +9 −0

internal/contra/static/contra.css +9 −0

diff --git a/internal/contra/static/contra.css b/internal/contra/static/contra.css

index f85d3f8..90780a8 100644

--- a/internal/contra/static/contra.css

+++ b/internal/contra/static/contra.css

@@ -590,9 +590,18 @@ code {

letter-spacing: 0.12em;

margin: 0;

padding: var(--rst-sp-3) 0;

+ text-align: start;

text-transform: uppercase;

}

+/* The caps stop at the serial. A build hash is an identifier somebody

+ copies, pastes and compares against `carlos channels`; printing it

+ uppercase when it is lowercase everywhere else makes the page lie

+ about a value in the one place the page exists to report it. */

+[data-overprint] code {

+ text-transform: none;

[rst-shell-foot] {

margin: 0 auto;

max-width: 60rem;