screenshots | ||
.gitignore | ||
contrast-ratios.org | ||
COPYING | ||
ef-autumn-theme.el | ||
ef-day-theme.el | ||
ef-night-theme.el | ||
ef-spring-theme.el | ||
ef-summer-theme.el | ||
ef-themes.el | ||
ef-winter-theme.el | ||
README.md |
Ef (εὖ) themes for GNU Emacs
WORK-IN-PROGRESS
Colourful and legible themes.
Screenshots (PRE-RELEASE and WORK-IN-PROGRESS)
Those will be removed from the repo before the actual package is released.
The themes in order:
ef-spring
ef-summer
ef-day
ef-night
ef-winter
ef-autumn
Principles
-
No customisation options! Either you like them or you don't.
-
Curated list of supported packages. I will only cover what I use and/or know is in a well-maintained state.
-
Minimum contrast ratio of 4.5:1 against the main background (WCAG AA standard). Use my
modus-themes
package (also built into Emacs 28 or higher) if you need top-class accessibility.
Minimal VS maximal scope
The ef-themes
are meant to be minimal in scope, as opposed to my
modus-themes
whose accessibility requirements make them maximalist by
necessity. The modus-themes
are such because:
- Accessibility is not a one-size-fits-all. Customisation options are necessary to empower users.
- Accessibility is as good as its weakest link. If the user spends all day using FOO package, it needs to be perfectly legible, otherwise the whole theme fails to deliver on its promise.
The ef-themes
can afford to be minimal because they do not have such a
lofty accessibility target.
FAQ
Will you stop using the modus-themes?
No. For my workflow, accessibility is the most important quality. The
modus-themes
will remain my default choice.
Then why develop the ef-themes?
Because I think that users deserve "pretty" themes that (i) do make some considerations for legibility, and (ii) are not designed on a whimsy.
In other words, the ef-themes
are my answer to those who like my
modus-themes
but want something with a bit more flair.