[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] externals/ef-themes 8d263a2788 2/5: Re-organise headings in the m
From: |
ELPA Syncer |
Subject: |
[elpa] externals/ef-themes 8d263a2788 2/5: Re-organise headings in the manual |
Date: |
Fri, 19 Aug 2022 08:57:38 -0400 (EDT) |
branch: externals/ef-themes
commit 8d263a2788576af24d0480226960f813270bf23c
Author: Protesilaos Stavrou <info@protesilaos.com>
Commit: Protesilaos Stavrou <info@protesilaos.com>
Re-organise headings in the manual
---
README.org | 80 +++++++++++++++++++++++++++++++-------------------------------
1 file changed, 40 insertions(+), 40 deletions(-)
diff --git a/README.org b/README.org
index 262c019399..142c2b7bfc 100644
--- a/README.org
+++ b/README.org
@@ -278,46 +278,6 @@ will retain the original aesthetic for that level. For
example:
(t . t))) ; default style for all other levels
#+end_src
-* Principles
-:PROPERTIES:
-:CUSTOM_ID: h:a6dd030c-6b6c-4992-83e8-3438b4607b51
-:END:
-
-+ No customization options that affect the style of individual
- components (e.g. change the color of the mode line, remove bold,
- etc.)! Either you like them or you don't. To change faces, it is
- better to do it in user-level configurations (report the issue and we
- can help with the relevant code). Providing customizations that
- refashion a wide set of themes is not maintainable.
-
-+ Curated list of supported packages. I will only cover what I use
- and/or know is in a well-maintained state. Styling a package requires
- a lot of work as one must (i) know how the package works, (ii) see all
- its interfaces in action, (iii) make sure that the color combinations
- look consistent with the rest of the theme.
-
-+ 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
-:PROPERTIES:
-:CUSTOM_ID: h:fb219b87-ab95-401a-a742-a2fc451bf9f7
-:END:
-
-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:
-
-1. Accessibility is not a one-size-fits-all. Customisation options are
- necessary to empower users.
-2. 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.
-
* Loading a theme
:PROPERTIES:
:CUSTOM_ID: h:75d74aea-d17f-497f-a3b8-f0bf4c372de0
@@ -461,6 +421,46 @@ made. Though please note that some tweaks to individual
hues or color
mapping are still possible. At any rate, we will not outright break any
code that uses ~ef-themes-with-colors~.
+* Principles
+:PROPERTIES:
+:CUSTOM_ID: h:a6dd030c-6b6c-4992-83e8-3438b4607b51
+:END:
+
++ No customization options that affect the style of individual
+ components (e.g. change the color of the mode line, remove bold,
+ etc.)! Either you like them or you don't. To change faces, it is
+ better to do it in user-level configurations (report the issue and we
+ can help with the relevant code). Providing customizations that
+ refashion a wide set of themes is not maintainable.
+
++ Curated list of supported packages. I will only cover what I use
+ and/or know is in a well-maintained state. Styling a package requires
+ a lot of work as one must (i) know how the package works, (ii) see all
+ its interfaces in action, (iii) make sure that the color combinations
+ look consistent with the rest of the theme.
+
++ 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
+:PROPERTIES:
+:CUSTOM_ID: h:fb219b87-ab95-401a-a742-a2fc451bf9f7
+:END:
+
+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:
+
+1. Accessibility is not a one-size-fits-all. Customisation options are
+ necessary to empower users.
+2. 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
:PROPERTIES:
:CUSTOM_ID: h:a6d5c6f1-84c5-4d74-ba39-b5ccda05497a