Skip to content

team: drop Human Generated, and draw the nav caret instead of typing it - #44

Merged
yorkerhodes3 merged 4 commits into
mainfrom
agents/refresh-from-github-repo
Aug 25, 2026
Merged

team: drop Human Generated, and draw the nav caret instead of typing it#44
yorkerhodes3 merged 4 commits into
mainfrom
agents/refresh-from-github-repo

Conversation

@yorkerhodes3

Copy link
Copy Markdown
Contributor

What

Two content-layer fixes to /team and the site header.

1. Remove Human Generated by BlockApps

Dropped from the organisations grid — from about.clients.items and from teamOrgOrder. Its BACKLOG entry for a missing logo goes with it, and the stale "BlockApps already linked" note is corrected.

2. Draw the nav dropdown caret instead of typing it

Reported as a font inconsistency in the header: Home / Portfolio ▾ / Team did not match on spacing, style, or apparent typeface.

The caret was the character (U+25BE). next/font subsets Space Mono to latin, latin-ext and vietnamese and emits a matching unicode-range — and U+25BE falls outside all three. The browser was therefore never permitted to use Space Mono for it and substituted whatever the operating system supplies, so it rendered in a different typeface, at a different optical size, on its own baseline, immediately beside Space Mono text.

It is now an inline SVG, matching how LinkedInLink and ThemeToggle already draw their icons. That removes the dependency on the visitor's platform entirely.

appeared only in SiteHeader.tsx, so this creates no inconsistency anywhere else.

Reviewer notes

The rest of the symbols are deliberately left alone. The same subsetting affects and 📖. None is broken — they all fall back, so they are at least consistent with each other. Converting one arrow at a time is exactly what would break that, so they are recorded as UPD-017 for a single deliberate pass rather than changed piecemeal.

"Portfolio" being brighter than its siblings is not a bug. isActive intentionally keeps Portfolio active across its sub-tabs (/demos, /publications, /media, /newsletter). The active item is text-foreground against text-muted — on a dark ground that reads as a weight difference, but both are weight 400.

On the OSCE / ODIHR logo — there is nothing to recover. Checked properly rather than assumed:

  • git log --diff-filter=D over public/logos returns zero deletions — no logo file has ever been removed from this repository.
  • The entry has carried logo: "" since Carolina added it in a30def40 (2026-07-21), and its about text and url are byte-identical to that commit. Nothing was lost.
  • A code search across every repository in the organisation finds only text references.

So it needs a file sourced from OSCE/ODIHR, not restored. I did not grab the emblem off osce.org: it is a protected intergovernmental emblem with its own usage rules, which is a different question from the company wordmarks already in public/logos/. Recorded in BACKLOG §2.

Verification

  • Lint, typecheck, content invariants, image budgets, and build all pass locally.
  • Confirmed in the built output: U+25BE is gone, the SVG is emitted, Human Generated is absent from /team, and OSCE is still present and unchanged.
  • Snapshot integrity checked explicitly — 78 pages, 6,263 asset references, 0 missing. Worth stating because an earlier attempt at the snapshot cleanup deleted three legitimately-new JS/CSS chunks along with the platform-shaped __next.* files; that was caught by this check and redone with a correct filter.
  • The __next.* prefetch payloads are left as-is, as in the previous snapshot commit (UPD-004).

Yorke Rhodes III and others added 4 commits August 25, 2026 15:12
Two unrelated fixes to the same page, kept together because both are one-line
content-layer changes to /team.

Remove "Human Generated by BlockApps" from the organisations grid, from the
clients array and from the display order. Its BACKLOG entry for a missing logo
goes with it.

Draw the Portfolio dropdown caret as an inline SVG. It was the character
U+25BE. next/font subsets Space Mono to latin, latin-ext and vietnamese and
emits a matching unicode-range, and U+25BE is outside all three - so the
browser was never permitted to use Space Mono for it and substituted whatever
the operating system supplies. It rendered in a different typeface at a
different optical size on its own baseline, immediately beside Space Mono text,
which is what made the nav look inconsistent. Drawing it removes the dependency
on the visitor's platform.

The same is true of the other symbols used as affordances - the arrows, the
play triangle, the close cross. They are recorded as UPD-017 rather than
changed here: they all fall back today, so they are at least consistent with
each other, and converting one at a time is what would break that.

While checking, the OSCE / ODIHR entry was searched for a logo to restore.
There is nothing to recover: no logo file has ever been deleted from this
repository, and the entry has carried an empty logo since it was added in
a30def4, with its text and url byte-identical to that commit. It needs a file
sourced from OSCE/ODIHR. Recorded in BACKLOG.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Picks up the Human Generated removal and the SVG nav caret.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The drift check tells a maintainer that their snapshot disagrees with what Linux builds, but not how. On a manual run it now uploads the regenerated static-site/ as an artifact, so the difference can be inspected - or adopted - from a machine that cannot build on Linux.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The previous snapshot commit carried a CSS chunk built from a stale Turbopack
cache. It still contained `.text-\[0\.65em\]`, the utility for the class on the
caret span that the same pull request removed, so the file was 34 bytes larger
than a clean build produces and its content hash differed. CI caught it as
drift against Linux.

Nothing platform-specific was involved: after `rm -rf .next out` the Windows
build produces `2rl-zb5-19h8i.css` byte-for-byte identical to the CI runner's,
verified by SHA-256 against the artifact that run uploaded.

Worth knowing for the next time `sync:static` reports an unexplained diff:
removing the last use of a Tailwind class does not always evict its generated
utility from the incremental cache, so the snapshot can be stale in a way the
source no longer justifies.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@yorkerhodes3
yorkerhodes3 merged commit 6a6180a into main Aug 25, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant