Hi Marc,
> I'm not trying to knock Exim's docs. But I think the perspective of a
> new user is helpful. Most of us learned Exim from back when it was
> small. We might want to rethink the docs to see if they can be improved.
I'm in favour of:-
(1) A combined reference manual and user guide with examples.
(2) At the top of pages can be the official documentation. This should
not be publicly changeable.
(3) Beneath it can be user comments, tips and advice. This should be
publicly changeable. Similar to PHP.
(4) Wiki entries should be directly referenced from the main Exim
documentation pages.
(5) The configuration file should be divided into several clearly
distinct parts and the documentation should follow the sequence of those
parts.
(6) If the configuration file does not allow includes, that could be
usefully implemented at the next revision. Includes will allow the bits
that frequently change to be kept separate from the configuration
details that are predominately static. I do this with Apache and it
works extremely well.
