serverguide methodology

[Kevin Cole]

P.S. I also favor using nano as the example editor.

     Also, I wanted to address the bit about anticipating the audience:  You
     can try, but this is "Linux for Human Beings (TM)" and as such, assuming
     that only techno-geek high priests should lay eyes on the "Holy Book of
     Server" isn't an approach I'd recommend. Stating up front "Here be
     dragons" is fine, but glossing over stuff because "readers should already
     know x, y and z" is a tough call.  If there are prerequisites, and the
     server guide cannot cover them all, they should be clearly stated up
     front, and if possible, there should be a list of documents presented in
     the order which they should be read.

-- 
 Kevin Cole                    |  Key ID: 0xE6F332C7
 Gallaudet University          |     WWW: http://gri.gallaudet.edu/~kjcole/
 Hall Memorial Bldg  S-419     |   V/TTY: (202) 651-5135
 Washington, D.C.  20002-3695  |     FAX: (202) 651-5746

 "Using vi is not a sin. It's a penance." -- St. IGNUcious, Church of Emacs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-doc/attachments/20051218/11e78798/attachment.pgp>