Carry the dejima marks, and say who owns them #15

2026-08-28T22:58:01-07:00

dejima-agent commented

2026-08-28 22:58:01 -07:00

Summary generated by LLM agent

Brings the branding across from the two hardener repositories: the dejima wordmark above the title, the "Developed in dejima" badge under the nav table, and assets/ with both wordmark modes and the badge.

The comment above the <img> tag comes with it, because the decision it records is not obvious. The wordmark is deliberately not preference-aware: prefers-color-scheme reports the browser's setting and never the site's, and this is read on a forge that renders dark whichever way the browser is set — so anything conditional would show dark ink on a dark page to a reader whose browser prefers light, and would do it silently. Both modes are committed so a mirror on a light-themed host changes one line instead of needing a file it does not have.

The marks are not code, and GPL-3.0 says nothing about them. The attribution is in the README's licence section and in assets/README.md, linking absolutely to dejima's ATTRIBUTION.md so that a fork resolves it to the canonical terms rather than to its own copy of them.

Two tests come across too: that every image the README references is a file this repository ships — checking both the <img>/png pair and the markdown/svg pair, since a test written for one would not see the other — and that the attribution link is present in both places.

Checked by rendering the header in a browser: both images load and the wordmark reads correctly on a dark background.

Tested: 79 passing.

**Summary generated by LLM agent** Brings the branding across from the two hardener repositories: the dejima wordmark above the title, the "Developed in dejima" badge under the nav table, and `assets/` with both wordmark modes and the badge. The comment above the `<img>` tag comes with it, because the decision it records is not obvious. The wordmark is deliberately not preference-aware: `prefers-color-scheme` reports the browser's setting and never the site's, and this is read on a forge that renders dark whichever way the browser is set — so anything conditional would show dark ink on a dark page to a reader whose browser prefers light, and would do it silently. Both modes are committed so a mirror on a light-themed host changes one line instead of needing a file it does not have. The marks are not code, and GPL-3.0 says nothing about them. The attribution is in the README's licence section and in `assets/README.md`, linking absolutely to dejima's `ATTRIBUTION.md` so that a fork resolves it to the canonical terms rather than to its own copy of them. Two tests come across too: that every image the README references is a file this repository ships — checking both the `<img>`/png pair and the markdown/svg pair, since a test written for one would not see the other — and that the attribution link is present in both places. Checked by rendering the header in a browser: both images load and the wordmark reads correctly on a dark background. Tested: 79 passing.

dejima-agent added 1 commit 2026-08-28 22:58:02 -07:00

Carry the dejima marks, and say who owns them d30a5b8d8e

The wordmark and the badge, matching the two hardener repositories. The
comment above the tag comes with them: the wordmark is not preference-aware
on purpose, because prefers-color-scheme reports the browser's setting rather
than the page's, and a forge that renders dark either way would show dark ink
on a dark page to anyone whose browser prefers light. Both modes ship, so a
mirror on a light host edits one line rather than needing a file it does not
have.

The marks are not code and the GPL says nothing about them, so the attribution
is here and in assets/README.md, linking absolutely to dejima's ATTRIBUTION.md
- a fork resolves an absolute link to the canonical terms rather than to its
own copy.

Checked by rendering it: both images load and the wordmark reads on a dark
background.

branderson approved these changes 2026-08-28 23:07:05 -07:00

branderson merged commit aed2a2b2fa into main

2026-08-28 23:07:10 -07:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dejima/dejima-guard#15