Skip to content

Tell the Dark Reader extension to stand aside (darkreader-lock) - #10

Merged
tannevaled merged 1 commit into
mainfrom
darkreader-lock
Oct 12, 2026
Merged

tannevaled merged 1 commit into
mainfrom
darkreader-lock

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

This landing draws its own dark theme (prefers-color-scheme and/or a theme toggle). The Dark Reader browser extension repaints such pages on top of their own palette; on go-fft it hid the hero's brand gradient. <meta name="darkreader-lock"> asks it to stand aside.

The change is one meta tag in layouts/index.html, right after the viewport meta, plus a one-line Hugo comment saying why.

Local check: hugo build failed locally (pkgx: no recipe for hugo in https://raw.githubusercontent.com/go-pkgx/pantry-overlay/main/projects or https://raw.github) (hugo 0.167.0).

The landings built on go-fleettools/landingkit already get this tag from the kit's styles.html.

🤖 Generated with Claude Code

This landing draws its own dark theme. The Dark Reader browser extension
repaints such pages on top of it, which on go-fft hid the hero's brand
gradient. <meta name="darkreader-lock"> asks it not to.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@tannevaled
tannevaled merged commit 64b4dca into main Oct 12, 2026
3 checks passed
@tannevaled
tannevaled deleted the darkreader-lock branch October 12, 2026 09:16
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