Repository navigation
Give the README Trinity's own identity - #79
Merged
Merged
Conversation
The logo is the one already in use on the platform's other project, copied in rather than reinterpreted: docs/assets/trinity-icon.png, resized from 1024px and stripped of metadata, 1.5 MB down to 182 KB. The wordmark is block letters on a 37x5 grid, emitted as one rectangle per run of filled cells rather than as text. No font is involved, so it renders the same wherever it is shown and stays sharp at any size, and the neon gradient is taken from the logo so the two read as one mark. Horizontal and vertical runs are both merged, because emitting a cell at a time left the glow filter scalloping the edges of every stem. Responsive by having two compositions rather than by hoping one scales. The wide one carries outer padding; the narrow one, served under 600px by a picture element, runs edge to edge, because on a phone the mark is scaled to the viewport and padding is width the letters could have used. Checked at desktop and phone widths, on GitHub's dark ground and on white, by rendering it in a browser rather than by looking at the file. The header also gains the badge row, the one-line statement of what Trinity is, and links to the five documents a reader actually wants first: quick start, architecture, security model, assurance case, roadmap. Corrected while here: the status line said 25 slices and there are 26, since the supply chain slice landed after that sentence was written. Signed-off-by: Ayla Croft <aylacroft@proton.me>
HackTuah
force-pushed
the
docs/readme-identity
branch
from
September 23, 2026 21:13
6e66e14 to
70cfa54
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README opened with a plain
# Trinityand one badge. It now opens with the project's mark.The logo
docs/assets/trinity-icon.png— the logo already in use on the platform's other project, copied in rather than reinterpreted. Resized from 1024px and stripped of metadata: 1.5 MB down to 182 KB.The wordmark
Block letters on a 37×5 grid, emitted as one rectangle per run of filled cells rather than as text. No font is involved, so it renders identically wherever it is shown and stays sharp at any size, and the neon gradient is taken from the logo so the two read as one mark.
Both horizontal and vertical runs are merged. Emitting a cell at a time left the glow filter scalloping the edge of every vertical stem — visible in the first render, fixed before it shipped.
Responsive by having two compositions
Not by hoping one scales. The wide mark carries outer padding; the narrow one, served under 600px by a
<picture>element, runs edge to edge — on a phone the mark is scaled to the viewport, so padding is width the letters could have used.Verified by rendering it in a browser at desktop and phone widths, on GitHub's dark ground and on white, rather than by looking at the file. ImageMagick's internal SVG renderer drops the gradient and the filter entirely, so checking with it would have proved nothing.
Also in the header
The badge row (OpenSSF silver, gate status, licence, runtime), the one-line statement of what Trinity is, and links to the five documents a reader wants first: quick start, architecture, security model, assurance case, roadmap.
Corrected while here
The status line said 25 slices. There are 26 — the supply chain slice landed after that sentence was written.
Evidence
mix gateexit 0; 576 passed, 18 excluded; coverage 80.31%.