Repository navigation
Two things the landing did that its three neighbours do not - #20
Merged
Merged
Conversation
The four landings share one styles.html — go-authn, go-fileshare and
go-pdfkit are byte for byte identical and go-pkgx is the documented
superset — so "aligned" could not be checked by diffing the design system.
What drifts is what each page PUTS IN it.
Measured, with the other three as the control:
go-authn go-fileshare go-pkgx go-pdfkit
headline line 1, characters 14 10 19 23
items in the trust band 3 3 3 4
blocks in the strip 1 1 1 2
## The headline
"The whole of PDF in Go," is 23 characters where the fleet sets 10 to 19,
and at 54px in a column of about 600 it wrapped — leaving "Go," alone on a
line of its own. The break moves rather than the words: "The whole of PDF"
then "in Go, with no C anywhere.", which is 16 and 26 against go-authn's 14
and 26, and renders in the same three lines with the last word on its own.
⛔ A count did not find this and could not have. Twenty-three characters
against ten, fourteen and nineteen is not a categorical exception, it is a
line too long for the column it is set in — a fact about rendering. It was
found by screenshotting the four pages and looking at them.
## The trust band
Four items where every other landing has three, so the fourth wrapped onto a
line of its own and sat there unbalanced. The one dropped is the coverage,
which is said better by its own heading further down the page.
## What is NOT changed, and why
The strip carries two blocks here and one everywhere else: the libraries,
and then the architectures the suite RUNS on. That second band was asked
for, it is derived from [params.arches] rather than typed, and the comment
above it says so. An outlier that the history explains is not drift.
Nothing else is alone: the hero keeps two buttons like the rest, and the
grids carry four cards, which the fleet uses as readily as three or nine —
a rule I nearly invented before counting.
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 four landings share one
styles.html— go-authn, go-fileshare and go-pdfkit are byte for byte identical, go-pkgx is the documented superset — so "aligned" could not be checked by diffing the design system. What drifts is what each page puts in it.Measured, with the other three as the control:
The headline
The whole of PDF in Go,is 23 characters where the fleet sets 10 to 19, and at 54px in a column of about 600 it wrapped — leaving "Go," alone on a line of its own.The break moves rather than the words:
16 and 26 characters, against go-authn's 14 and 26 — and it renders in the same three lines with the last word on its own, which is what the house hero looks like.
The trust band
Four items where every other landing has three, so the fourth wrapped onto a line of its own and sat there unbalanced. The one dropped is the coverage — said better by its own heading further down the page.
What is not changed, and why
The strip carries two blocks here and one everywhere else: the libraries, then the architectures the suite runs on. That second band was asked for, it is derived from
[params.arches]rather than typed, and the comment above it says so.An outlier that the history explains is not drift. This is the trap I walked into last week — removing a deliberate loong64 pin because it was the odd one out — so the rule now is to read the comment on the line before touching it.
Nothing else is alone: the hero keeps two buttons like the rest, and the grids carry four cards, which the fleet uses as readily as three or nine — a rule I nearly invented before counting.
🤖 Generated with Claude Code