Theme creation with Aether, as in Omarchy #70
Labels
No labels
approved
bug
changes-requested
ci
decision
declined
discuss
docs
feature
meta
now
packaging
refactor
release
repo/core
repo/krystal
repo/plugins
repo/themes
status/backlog
status/in-progress
status/next
status/review
ux
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
joshquinlan/donbox#70
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adopt the Aether theme-creation flow: generate a palette from a wallpaper or a seed colour, preview it live across the shell and templates, and write a complete theme directory (colours.toml, theme.toml, fonts, motion, backgrounds, preview) that passes donbox theme check. Offer it from the menu (Style > New theme) and as
donbox theme new. Study how Omarchy integrates Aether (aether.nvim palette and the Aether app) and what can be reused versus written in Donbox terms.Approach decided in #77: native donbox theme new (median-cut from a wallpaper, OKLab seed-colour palette, contrast-gated accents, preview generation, live preview via a staging theme); Aether-made themes import through donbox theme install.
Integrated on master (
1b961c1): donbox theme new from a wallpaper (median cut over a 200 px PPM) or a seed colour, OKLCH roles with 7:1 ground and 4.5:1 accents, modes normal/muted/pastel/vibrant/mono, preview with restore, interactive flow from the menu row style.new-theme; 33 Python and 180 shell assertions; tagged m3-theme.