Couple of things, some of which I could help with.

• The the page-to-page navigation needs to be improved. I've been thinking about this a bit (I'm taking a course on this very subject right now) and have a few ideas on improving it.
• Use a san-serif font like arial or helvetica for the text type. San-serif is much easier to read onscreen then serif'd fonts. Serifs are hard to render onscreen thanks to the low resolution of monitors and thus make the characters less easy to recognize, slowing your reading down by like 10% -> 20%.*
• Get rid of the numbering on section headers. That kind of stuff is pretty irrelivant to online stuff and makes scaning for a particular section harder. The best example I have of section numbering gone bad is the PHP docs which insist on using roman numbering and make it really hard to scan.
• We could also probably do a re-ordering of the outline. Anything more then about 7 section headings suggests a re-order. Our memory can only hold so much information, and some of these lists are quite large (21 headings under "features and customization"). This makes it hard to scan and find what you are looking for.

  For example "comments & views", "trusted users & mojo" seem like one group, "story selection", "archiving", "digest emails", "user diaries" are another. Perhaps we move to a more task-oriented heiarchy like "Handling Comments", "Handling Stories", etc. The PHP guys could probably take this tip too.

• Lastly, I could probably do some editing for you in my spare time. Ve Shalt Zee. I might be able to use the design of this documentation for a class project. Features would then include good looking navigation and other things that would make it look nice and professional. Plus I could get credit for it :-)

• How do I get the "source" for this document?
• I have *no* clue how to use LaTEX or even really what the hell it is. Can I just edit this puppy in word and then somehow magically make it LaTEX (which then does what?)
• Can I then take this LaTEX thingy and put it into dreamweaver, or somehow use an HTML page as a stylesheet for LaTEX?
• Is LaTEX even a good choice for this document? Do most scoop programmers know it? It it ideal for a document that will be used on the great InterWeb but probably never wind up on a dead tree? Can we do something simpler like make a template in Dreamweaver and pour the content into that? In that case, all the headings would be simple HTML tags that would then get their formatting from a CSS file.

Actually, the most important question is, how do we edit this online? I have a lot of feedback that I'd like to give, but have no way of actually doing so. If it was a word document, we could use the track changes. I have no clue how to edit a LaTEX document, or even if such tools exist.