Repository navigation
docs(theme): align heading typography and fix the mobile theme-color - #19
Merged
Merged
Conversation
The Erigon docs site gained a typography pass in erigontech/erigon
a9135af285 ("enforce brand font consistency") that never reached the
sibling sites, so headings here have rendered slightly looser and
anchor links land under the sticky navbar.
Ports that block verbatim: h1/h2 negative letter-spacing, the uppercase
h6 treatment, font smoothing, --ifm-heading-line-height 1.2, h2/h3 top
margins, and scroll-margin-top so heading anchors clear the navbar.
Palette-agnostic -- no color token is touched.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The terminal-green theme recolored the stylesheet but left the theme-color meta tag at #EF7716. That tag tints the browser chrome on mobile -- Chrome's address bar on Android, the status bar area on iOS -- so the mobile site rendered an Erigon-orange bar above an otherwise green site. Point it at #1F9D3E to match --ifm-color-primary. This is the last unintentional orange in the site: every remaining #EF7716 is the shared corporate footer, which stays orange by design. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Summary
Two theme-alignment fixes, keeping the green body theme intact.
1. Heading typography (
src/css/custom.css)The Erigon docs site gained a typography pass in
erigontech/erigona9135af285 that never reached the sibling sites. Ports that block verbatim:h1/h2letter-spacing, uppercaseh6, font smoothing,--ifm-heading-line-height: 1.2,.markdown h2/h3margins, andscroll-margin-topso heading anchors clear the sticky navbar. Verified byte-identical to erigon's block at the same offset. Palette-agnostic.2. Mobile
theme-color(docusaurus.config.ts)The terminal-green theme recolored the stylesheet but left the
theme-colormeta tag at#EF7716. That tag tints the browser chrome on mobile — Chrome's address bar on Android, the status-bar area on iOS — so the mobile site rendered an Erigon-orange bar above an otherwise green site. Now#1F9D3E, matching--ifm-color-primary.A full sweep confirms this was the last unintentional orange: every remaining
#EF7716is the shared corporate footer, which stays orange by design (see #18).Comment corrections
The green theme changed hex values by find-and-replace and left the English labels behind, so the file documented
#1F9D3Eas "Erigon Orange" in two places — the header and the/* Erigon Orange scale */comment above the ramp. Both corrected to "Zilkworm Green", plus the Quantify wordmark role documented in the header.The header comment now states plainly that
docusaurus-design-spec.mdstill specifies orange site-wide and has not yet been amended (zilkworm-docs-spec.md:29,docusaurus-design-spec.md:233— "always orange — brand convention").The green was a deliberate product decision (#12, #16) and is being kept. But until
erigon-documentsrecords it, the code and the spec contradict each other, and any spec-compliance check will flag zilkworm's green as a violation. A follow-up PR toerigon-documentsshould ratify the exception.Verification
tsc --noEmitandnpm run buildclean--ifm-color-primary:#1f9d3eintact andtext-rendering:optimizeLegibilityapplied<meta name="theme-color" content="#1F9D3E">🤖 Generated with Claude Code