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

layouts/index.html

@@ -6,12 +6,6 @@
 <title>{{ .Site.Title }} — the whole of PDF in Go, with no C anywhere</title>
 <meta name="description" content="go-pdfkit — read a PDF, write one, rearrange it, draw it, read it back as words and pictures, and edit it with other people. Pure Go, CGO_ENABLED=0, every library building for js/wasm, and measured against 118 863 real PDFs rather than a handful written to pass a test.">
 <link rel="icon" type="image/svg+xml" href="/favicon.svg">
-{{/* Ask the Dark Reader extension to stand aside. This page has its own
-     three-way theme and its own dark palette; Dark Reader recolours it on top
-     of that, which inverts a page that was already dark and leaves the brand
-     colours somewhere neither design chose. Same mechanism our Hextra fork
-     uses for the documentation. */}}
-<meta name="darkreader-lock">
 {{ partial "styles.html" . }}
 </head>
 <body class="lm">

layouts/partials/styles.html

@@ -1,3 +1,10 @@
+{{/* This page draws its own dark theme (prefers-color-scheme and the
+     System/Light/Dark toggle). The Dark Reader extension otherwise repaints it
+     on top -- the hero's brand wash vanished under it on go-fft while the
+     same CSS showed on go-ndarray -- so it is told to stand down, as
+     go-pdfkit's page and our Hextra fork already do. This partial is
+     included in <head>, so every landing on the kit gets the flag. */}}
+<meta name="darkreader-lock">
 {{/* The brand colours are the ONLY thing that differs between the orgs using
      this stylesheet, and they are read from [params.brand] rather than written
      in. Two byte-identical copies of this file already existed in go-authn and