docs: use teal as the site primary colour - #16
Merged
Conversation
The three ecosystem doc sites shared an identical deep purple / amber palette and were indistinguishable side by side. Give this site a teal primary and keep amber as the shared ecosystem accent. Closes #13
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.
primary: deep purple→primary: tealin both palette entries ofmkdocs.yml.accent: amberis unchanged — it stays the shared ecosystemaccent, so the site still reads as part of the family.
Hue distance from
goldilocks-ml: 270° → 174°, 96° apart, which is enough totell the two sites apart as browser tabs.
tealhas adequate contrast in boththe
defaultandslateschemes, so no per-scheme override was needed.Verification
uv run --frozen mkdocs build --strictpassessite/index.htmlrendersdata-md-color-primary="teal"for both the lightand dark palette entries
Closes #13
Written by an agent on behalf of @junwen94.