serverguide

[Matthew East]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,

The serverguide needs some significant changes to bring it into line
with the structural changes to the help system we've been making.

Some basic changes I'd like to make include:

* Removing things which make it seem like a stand-alone guide, instead
of a coherent part of a help system, such as the preface, introduction,
installation, etc.
* Restructuring so that the good stuff appears as high level structure.
So, things like "Web server", "Email server" and so on would be top
level sections.

The question again arises of how to do this. As we discussed in relation
to the switching from windows guide, the serverguide clearly has some
merit as a standalone book as well as a part of an integrated help
system. Things like "installation" which aren't relevant to an installed
desktop system might still be of use elsewhere, because the server
installation process is different to the regular one.

So what do people think about the best way to do this? Preserve an
original copy of the serverguide and fork a version for the desktop help
system? Not include it in the desktop help system at all, on the grounds
that it is not relevant to desktops (I'd be against this because I think
people expect to find all documentation relevant to their system in the
help centre)? Or other ideas?

Matt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFlFLetSaF0w5rBv8RAgzuAJ4tfph20mH3RxkvQYLddz+LDyrmlQCeJLqq
zc2RS510pTEja9vsuQg0YAY=
=f0GB
-----END PGP SIGNATURE-----