Files
dejima-ci-hardener/assets/dejima-wordmark-darkmode.png
T
branderson 9c49451529
tests / runner-env (confined) (pull_request_target) Successful in 1m25s
tests / tests (pull_request_target) Successful in 1m50s
tests / compose-schema (pull_request_target) Successful in 1m34s
tests / runner-env (privileged) (pull_request_target) Successful in 1m23s
Put the wordmark on the README, and point at the canonical terms
The suffix names the mode a file is for, not the colour of its ink, so `-darkmode` is the pale wordmark that belongs on a dark page. Naming by ink reads backwards at the moment someone is picking a file in a hurry, and it collides with the logo variants, which are already named by mode.

The README points at one file unconditionally rather than switching on `prefers-color-scheme`, which reports the browser's setting and never the site's. A forge that renders dark whichever way the browser is set would then show dark ink on a dark page, silently, to a reader whose browser prefers light. Both files ship, so a mirror on a light-themed host changes one line where someone can see whether it worked.

The artwork is not covered by the GPL. Both the README and assets/README.md point at dejima's ATTRIBUTION.md for who holds the marks and what may be done with them, by absolute link, so a fork resolving it does not find its own divergent copy of the terms.
2026-08-08 23:26:01 -07:00

47 KiB
2007x492px