1 The first version of this website had a theme switcher. It was
2 implemented with CSS variables (and a bit of javascript). Then the
3 javascript switcher was eventually removed, and the theme forced to be
4 dark, but I kept the CSS variables *just in case* (read: I'm lazy.)
5 
6 *Edit*: this is no longer the case. The current version of the website
7 is *yet another one*, with a 100% rewritten (and pure) CSS.
8 
9 The real reason I left the CSS variables was that I didn't wanted to
10 use a CSS preprocessor (such as `less` or `sass`) to manage such a
11 simple file (306 line, with blanks and comments). But, at the same
12 time, I didn't want to copy-paste the colors everywhere.
13 
14 ## Introducing the C preprocessor
15 
16 The C preprocessor is a simple and well-known beast (sort of, at
17 least), and it's included in the base system installation of most
18 (pratically all, I presume) OSes.
19 
20 If you have never used it, here's a quick howto.
21 
22 You can define constants with
23 ```
24 #define PI 3.141592653589793238462643383279502884197169
25 ```
26 and use them whenever you like, for instance
27 
28 ```css
29 double p = PI / 4;
30 ```
31 
32 The preprocessor is more powerful, it supports `#include`s and
33 function-like macro (even variadic). But `#define`s are enough to
34 manage a couple of CSS variables.
35 
36 Now, let's see how this applies to CSS. Given a file with the
37 following content
38 
39 	#define BASE1 #221635
40 	
41 	body {
42 	    background-color: BASE1;
43 	}
44 
45 we can *compile* it with
46 
47 	$ cpp -P file.css > a.css
48 
49 and obtain a valid CSS file `a.css`.
50 
51 ## Conclusions
52 
53 It's weird. It's weird to invoke `cpp` to *build* a CSS files.
54 
55 But it's also *satisfying*, in some sense.
56 
57 As a conclusion, I would like to note that another option is to use
58 m4, a general purpose macro language that should be present on every
59 POSIX system. Unfortunately, I don't know the language very well, so I
60 opted to `cpp`.