feat: switch color scheme from catppuccin to ayu #2

Merged
lytedev merged 1 commit from ayu into master 2026-07-07 16:13:00 -05:00
Owner

Replaces catppuccin (latte/mocha) with ayu (light/dark) as the site color scheme.

Stacked on #1 — this branch includes the dark-mode commits; merge #1 first, and this diff reduces to just the ayu swap (theme.styl + two var usages in core.styl).

What changed

  • Palette values are the canonical ones from the ayu npm package v8.0.1, declared once via light-dark().
  • Catppuccin-named vars (--Rosewater--Crust) → ayu-named (--tag, --func, --entity, --string, --keyword, --constant, --accent, --panel-bg, …); semantic vars (--bg, --fg, --link-fg, --syntax-*) now reference them.
  • Chroma mapping: keywords → orange, functions/names → yellow, strings → green, literals → purple, tags → cyan, comments → ayu comment (translucent), errors → ayu error.
  • Links: entity blue, darkened 30% in light mode for contrast (same approach the old theme used with sapphire). Code-block left edges highlight with the ayu accent gold.
  • Blockquotes now use --panel-bg / --syntax-ledgbq (the only places that referenced catppuccin names directly).

Verification

Headless Chromium: 20/20 — toggle cycle + persistence unchanged, exact-color spot checks for link color (#1772b2 light / #59c2ff dark) and code-block bg (#f3f4f5 / #0f131a), screenshots of a syntax-heavy post in both schemes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TKabGxxNaNoocaxN8B4BFG

Replaces catppuccin (latte/mocha) with **ayu** (light/dark) as the site color scheme. **Stacked on #1** — this branch includes the dark-mode commits; merge #1 first, and this diff reduces to just the ayu swap (`theme.styl` + two var usages in `core.styl`). ## What changed - Palette values are the canonical ones from the [`ayu` npm package v8.0.1](https://github.com/ayu-theme/ayu-colors), declared once via `light-dark()`. - Catppuccin-named vars (`--Rosewater`…`--Crust`) → ayu-named (`--tag`, `--func`, `--entity`, `--string`, `--keyword`, `--constant`, `--accent`, `--panel-bg`, …); semantic vars (`--bg`, `--fg`, `--link-fg`, `--syntax-*`) now reference them. - Chroma mapping: keywords → orange, functions/names → yellow, strings → green, literals → purple, tags → cyan, comments → ayu comment (translucent), errors → ayu error. - Links: entity blue, darkened 30% in light mode for contrast (same approach the old theme used with sapphire). Code-block left edges highlight with the ayu accent gold. - Blockquotes now use `--panel-bg` / `--syntax-ledgbq` (the only places that referenced catppuccin names directly). ## Verification Headless Chromium: 20/20 — toggle cycle + persistence unchanged, exact-color spot checks for link color (`#1772b2` light / `#59c2ff` dark) and code-block bg (`#f3f4f5` / `#0f131a`), screenshots of a syntax-heavy post in both schemes. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01TKabGxxNaNoocaxN8B4BFG
Replace the catppuccin latte/mocha palettes with ayu light/dark. Exact
values come from the ayu npm package (v8.0.1, the canonical published
palette): https://github.com/ayu-theme/ayu-colors

The catppuccin-named variables (--Rosewater..--Crust) are replaced by
ayu-named ones (--tag, --func, --entity, --string, --keyword, ...);
semantic variables (--bg, --fg, --link-fg, --syntax-*) now reference
those. Chroma token mapping: keywords -> ayu keyword (orange),
names/functions -> func (yellow), strings -> string (green),
literals -> constant (purple), tags -> tag (cyan), comments -> comment,
errors -> error. Links use entity blue (darkened in light mode for
contrast, mirroring the old darkened-sapphire approach); code-block
edges highlight with the ayu accent.

The only users of the old named vars (blockquote bg/border, inline code
fg) now use --panel-bg, --syntax-ledgbq, and --keyword.

Verified with headless Chromium: toggle/persistence still pass, plus
exact-color spot checks for link color and code-block background in
both schemes on a syntax-highlighted post.
lytedev merged commit 862010fb13 into master 2026-07-07 16:13:00 -05:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lytedev/site.lyte.dev!2
No description provided.