From 4069ee12f6ab6f4b0fccb56183912a3ab7b6a0e3 Mon Sep 17 00:00:00 2001 From: inference-bot Date: Tue, 3 Nov 2026 20:22:45 +0000 Subject: [PATCH] docs site: use Material's custom palette so the co-op colours actually apply The theme was configured with primary: teal and accent: deep orange, so every page shipped data-md-color-primary="teal" / data-md-color-accent="deep-orange" and Material set --md-primary-fg-color and friends on . Those variables then beat brand.css, which sets them on , because a value on the nearer ancestor wins for descendants regardless of specificity. The result: cream background and ink from brand.css applied, but the header, links and accents stayed Material's defaults. primary/accent are now "custom", Material emits no palette of its own, and the co-op variables in publishing/brand.css take effect. --- mkdocs.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/mkdocs.yml b/mkdocs.yml index e04cfd3..6acc00e 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -40,15 +40,15 @@ theme: # Light is listed first, so a fresh visitor gets the bright theme. - media: "(prefers-color-scheme: light)" scheme: default - primary: teal - accent: deep orange + primary: custom + accent: custom toggle: icon: material/weather-night name: Switch to dark mode - media: "(prefers-color-scheme: dark)" scheme: slate - primary: teal - accent: deep orange + primary: custom + accent: custom toggle: icon: material/weather-sunny name: Switch to light mode