docs(site): Quantify brand wordmark + minimal theme-aware footer

[bloxster]

What

Three things, in order: restore the Quantify brand wordmark this site was missing, replace the five-column footer with the minimal one the docs sites now share, then fix what an adversarial review found in both.

Targets release/3.5 because that is the only branch carrying docs-deploy.yml — changes landed elsewhere do not publish. Needs forward-porting to main and release/3.6 after it deploys.

Commit	Change
3d1e5b9812	Quantify wordmark (navbar title + footer), linked brand lockup
ca20c484ff	Five-column footer → minimal, theme-aware
db81e1667e	Review fixes: contrast, dark boundary, dead config, in-repo spec

1. Quantify

docusaurus-design-spec.md §7 specifies Quantify 700 for the navbar title and footer wordmark. This site was the only Erigon property not following it — it rendered both in Montserrat 800 and had no Quantify at all: no .woff2, no @font-face, no usage. cocoon.erigon.tech, zilkworm.erigon.tech and erigon.tech all had it. The font was dropped here during a licensing question later resolved in Quantify's favour, and never restored.

The vendored Quantify.woff2 is byte-identical to the copy already shipping on all three siblings (md5 8ea91606884b1e451c15ea8295c21c7e). Licence is confirmed by the holder to cover use across Erigon properties, public-repo vendoring included.

2. Minimal footer

A docs site already has a sidebar, a navbar and search, so five columns of links duplicate navigation the reader is standing in. The full footer stays on erigon.tech, where it is a primary navigation surface. Design spec §6.0 records the split.

Now: brand lockup → tagline → icon-only socials, then a bottom bar (copyright, Privacy / Cookie / Contact / hello@erigon.tech). Nunito Sans with the Quantify wordmark. Every interactive element hovers Erigon Orange #EF7716.

The surface is now theme-aware — white in light, black in dark, via --footer-* custom properties. It was hardcoded #000000 in both modes before. The text ramp had to move to fixed alpha values in the same change: Infima's emphasis vars invert with the theme and would have rendered dark-on-black.

⚠️ What this drops

• The Products / Developers / Company / Community link columns — including the cross-site discovery links (Zilkworm Docs / Cocoon Docs / Erigon Docs). If those carried referral traffic between the properties, this is a real regression and worth a deliberate decision.
• The Erigon Technologies AG postal address (Dammstrasse 16, 6300 Zug). If that is an imprint expectation for a Swiss AG, it needs adding back as a compact line.

Both were left out because minimal was the explicit ask; both are one-line additions.

3. Review fixes (db81e1667e)

Reviewed adversarially by GPT-5.5 and Claude Fable; every finding verified against the files before acting.

• WCAG AA failure. --footer-fine at 0.35 alpha computed to 2.44:1 on white and 3.01:1 on black — both below the 4.5:1 needed at 0.8rem, covering the copyright line and all four legal links. Now 0.55 → 4.75:1 / 6.26:1. The premise behind 0.35 was wrong: equal alpha is not equal perceived contrast across inverted surfaces, so mirroring the dark ramp made light mode worse than the value it copied. The dark failure was inherited from the old black footer and is fixed here too.
• Dark mode had no footer boundary. #000000 against the #0A0A0A page body is imperceptible — the footer read as the page petering out. Dark now carries a top edge. A code comment claiming black "separates unaided" was false and is corrected in place.
• Light social borders 0.15 → 0.25; at 0.15 the boxes nearly vanished on white, while 0.15 white-on-black reads fine.
• Dead themeConfig.footer removed — ignored since the footer was swizzled, and its discord.gg/erigon disagreed with the real footer's dsc.gg/erigon, so it was actively misleading.
• In-repo DESIGN-SPEC.md §6 still described the black five-column footer and a Montserrat wordmark, contradicting the two commits before it. Rewritten to summarise and point at the canonical spec rather than duplicate it.

Known and deliberate

color-mix() (the 12% hover tint) is Chrome 111+, while the default production browserslist resolves to Chrome 109, so the tint no-ops on 109–110. Left as-is: colour and border hover still fire, and the obvious fix — a hardcoded rgba — would break theme awareness. Documented in the spec.

Verification

• npm ci && npm run build clean; npm run typecheck clean
• python3 docs/site/scripts/generate-llms.py --check → OK, 4 files match (74 pages)
• Font actually resolves rather than silently falling back: document.fonts reports Quantify:loaded; built CSS has .navbar__title{font-family:Quantify,sans-serif;font-weight:700}; build/fonts/Quantify.woff2 present
• Footer probed over the DevTools protocol in both colour modes: bg #FFFFFF / #000000, body Nunito Sans, wordmark Quantify, accent #EF7716, and --footer-fine serving as #0000008c / #ffffff8c

Companion PRs: erigontech/cocoon (same footer), erigontech/erigon-documents (the spec this implements — worth reviewing first), erigontech/zilkworm-docs#22.

🤖 Generated with Claude Code

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 5 changed files in this pull request and generated no new comments.

Suppressed comments (3)

docs/site/src/css/custom.css:469

• The footer palette block comment is unusually long and contains commentary about earlier revisions plus detailed contrast math. This kind of forensic detail is difficult to maintain; it should be condensed to a short, durable description of the invariants (theme-aware surface, fixed alpha ramp, 1px top edge, 0.55 fine text for AA).

/* ─── Footer palette ─────────────────────────────────────────────────────── */
/* The footer surface follows the colour mode: white in light, black in dark.
   Text is a fixed alpha ramp rather than Infima's emphasis vars, because those
   invert with the theme and would render dark-on-black (or light-on-white)
   depending on mode. Ramp values come from the

docs/site/src/css/custom.css:16

• The new font licensing note is very long and includes forensic/historical assertions (e.g., “confirmed by the licence holder”, “no redistribution question to re-litigate”). This is hard to keep accurate over time; consider keeping only the actionable constraint (self-host, don’t switch to a third‑party CDN) and move details to the canonical design spec or PR description.

This issue also appears on line 465 of the same file.

/* Self-hosted fonts — no Google Fonts or CDN. See docusaurus-design-spec.md §7.
   Quantify is a non-free webfont. Erigon Technologies AG holds a commercial
   extended license that covers its use across Erigon properties, including
   vendoring this woff2 in a public repo — confirmed by the licence holder,
   so there is no redistribution question to re-litigate here. Self-hosting is

docs/site/DESIGN-SPEC.md:158

• The DESIGN-SPEC summary references a specific date (“pre-2026-08”), which is brittle and will go stale. Prefer a timeless description like “previous five-column footer” without embedding dates in the spec.

- Theme-aware surface via `--footer-*` custom properties in `src/css/custom.css`: white in light mode, black in dark. It is **not** always black — that was the pre-2026-08 five-column footer.

[bloxster]

Copilot's 3 suppressed comments — all addressed in faf2ec46ae

These arrived inside the collapsed Suppressed comments block of the review body rather than as inline threads, so there is nothing to resolve. Tabulating them here instead.

#	File	Finding	Action
1	docs/site/src/css/custom.css:469	Footer palette comment is long and carries commentary about earlier revisions plus contrast arithmetic; condense to durable invariants	Fixed. Rewritten as a short invariants list
2	docs/site/src/css/custom.css:16	Font licence note is long and makes forensic assertions ("confirmed by the licence holder", "no redistribution question to re-litigate"); keep only the actionable constraint	Fixed. Reduced to: keep self-hosting, do not switch to the CDN copy. Licence scope lives in the design spec
3	docs/site/DESIGN-SPEC.md:158	"pre-2026-08 five-column footer" embeds a date that will go stale	Fixed. Now "previous five-column footer"

The distinction I applied on #1 and #2: keep the reasons that stay true — why the ramp is fixed rather than Infima vars, why both colour modes need a top edge, why fine print is 0.55 and not 0.35 — and drop the "an earlier version claimed X" narration, which is the part that actually rots. The invariants a future editor needs are still there; the changelog-in-a-comment is gone.

Same two comments ship on the cocoon footer, so erigontech/cocoon#46 got the identical change (3ab6686) to keep the sites in step.

For context on the earlier red marks on this PR: every one was CANCELLED, not a test failure — a GitHub Actions incident (Failed to resolve action download info: Service Unavailable) plus this workflow's cancel-in-progress on PR pushes. mainnet-rpc-integ-tests passes 6/6 on release/3.5. Separately, qa-rpc-integration-tests.yml has no path filter, so a docs-only diff occupies the self-hosted QA runners; worth a paths-ignore in its own PR rather than here.

🤖 Generated with Claude Code