From f0c362b6888c1d50a0333c1c788e4acfd5b310cb Mon Sep 17 00:00:00 2001 From: iris Date: Tue, 18 Aug 2026 21:07:05 +0200 Subject: [PATCH] docs: clarify dynamic colour derivation still traces to base16 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per mara's follow-up: the doc shouldn't read as 'no dynamic colour at all' — mixing/lighter/darker derivation is fine and matches Material's own approach, the constraint is that every derived colour still traces back to the base16/stylix contract, not an independent source. --- docs/web-ui/design-guide.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/web-ui/design-guide.md b/docs/web-ui/design-guide.md index 5593710f..e8610471 100644 --- a/docs/web-ui/design-guide.md +++ b/docs/web-ui/design-guide.md @@ -32,9 +32,10 @@ repeated here. model selector living in a three-dot overflow menu instead of next to the thing that shows the current model. - Loosely influenced by Material Design's current (Material You) - generation, mainly for shape/elevation ideas — colour theming is - governed entirely by the base16/stylix contract below, not Material's - dynamic-colour system. + generation, mainly for shape/elevation ideas. Colour is dynamic too — + auto-derived shades (mixing, lighter/darker) are fair game, same as + Material's own approach — but every derived colour still traces back + to the base16/stylix contract below, never an independent source. ## Motion