From bfb467b1b50d11b57dae46b4b848baae21bab109 Mon Sep 17 00:00:00 2001 From: Rocco Rutte Date: Tue, 30 Dec 2008 00:53:47 +0100 Subject: [PATCH] Documentation: Update TODO --- doc/TODO | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/doc/TODO b/doc/TODO index 76b0c38c..75b9596b 100644 --- a/doc/TODO +++ b/doc/TODO @@ -17,8 +17,7 @@ Style/Technical If the filename ends with a vertical bar (|) - We need to choose either style and use it. Probably we want to add - a short typography section explaining layout details. + We need to choose either style and use it. * Think about some way of templating to a) help improve consistency (i.e. some sort of macro to refer to key, options, functions, etc.) @@ -31,12 +30,6 @@ Style/Technical perl already to build docs, think about/look for simple perl templating engine. -* Maybe add a mutt.css to contrib to make it look better. - -* As for sending patches, maybe add a short text file for documentation - hackers with guidelines. (Though nobody really seems to provide input - on the manual) - * Find a way (XSLT?) to trim the TOC for the option reference; it's ugly but we probably want to keep the TOC depth as-is for other sections. @@ -44,12 +37,6 @@ Style/Technical Content ------- -* Especially the introduction needs to be reworked quite a bit, - the current reference-like way is unfriendly for new users. There - should be an introduction chapter explaining concepts (config, menus, - hooks, etc.) E.g. the intro for hooks should come _before_ their - syntactical definition, not after. - * Some sections maybe should be better grouped by topic, instead of one section per task (e.g. hooks should be grouped under a section 'hooks' in the config chapter). -- 2.40.0