mutt stable branch with some hacks
Documentation: Update TODO
+1
-14
+1
-14
doc/TODO
+1
-14
doc/TODO
···
17
17
18
18
If the filename ends with a vertical bar (|)
19
19
20
-
We need to choose either style and use it. Probably we want to add
21
-
a short typography section explaining layout details.
20
+
We need to choose either style and use it.
22
21
23
22
* Think about some way of templating to a) help improve consistency
24
23
(i.e. some sort of macro to refer to key, options, functions, etc.)
···
31
30
perl already to build docs, think about/look for simple perl
32
31
templating engine.
33
32
34
-
* Maybe add a mutt.css to contrib to make it look better.
35
-
36
-
* As for sending patches, maybe add a short text file for documentation
37
-
hackers with guidelines. (Though nobody really seems to provide input
38
-
on the manual)
39
-
40
33
* Find a way (XSLT?) to trim the TOC for the option reference; it's
41
34
ugly but we probably want to keep the TOC depth as-is for other
42
35
sections.
43
36
44
37
Content
45
38
-------
46
-
47
-
* Especially the introduction needs to be reworked quite a bit,
48
-
the current reference-like way is unfriendly for new users. There
49
-
should be an introduction chapter explaining concepts (config, menus,
50
-
hooks, etc.) E.g. the intro for hooks should come _before_ their
51
-
syntactical definition, not after.
52
39
53
40
* Some sections maybe should be better grouped by topic, instead of
54
41
one section per task (e.g. hooks should be grouped under a section