Reply to thread

Message

<blockquote data-quote="citizenkeys" data-source="post: 475472" data-attributes="member: 91851">to be honest, i think that wiki is quite cluttered.i find a pdf to be much more useful than a wiki for manual-type documentation.after printing the manual to pdf, i found myself reading pages of the documentation that i never would've bothered to click around to read in the wiki.i vote to simply abandon the wiki.&nbsp; from a management standpoint, it's just too much of a hassle.alternatively, it would not be difficult to do some sort of cron script to print the manual pages to pdf, combine them into a single pdf, and replace any existing pdf of the manual.&nbsp; then we could have the best of both worlds.even if the manual were only updated, say, once a month then it would still be somewhat accurate and &quot;good enough&quot; for most people's uses.does one person need to be designated to manage the manual?&nbsp; why not just make it available in html/word so that anyone can edit it.&nbsp; i'm probably going to need to get the thing in html/word format anyway just to format it more reader-friendly and add a front cover to it anyway.i still think using html's named anchors to keep the FAQ entries, glossary entries, and tips/tricks all on a single page each is much better than having each faq, glossary entry, tip on its own page.</blockquote>

[QUOTE="citizenkeys, post: 475472, member: 91851"] to be honest, i think that wiki is quite cluttered. i find a pdf to be much more useful than a wiki for manual-type documentation. after printing the manual to pdf, i found myself reading pages of the documentation that i never would've bothered to click around to read in the wiki. i vote to simply abandon the wiki. from a management standpoint, it's just too much of a hassle. alternatively, it would not be difficult to do some sort of cron script to print the manual pages to pdf, combine them into a single pdf, and replace any existing pdf of the manual. then we could have the best of both worlds. even if the manual were only updated, say, once a month then it would still be somewhat accurate and "good enough" for most people's uses. does one person need to be designated to manage the manual? why not just make it available in html/word so that anyone can edit it. i'm probably going to need to get the thing in html/word format anyway just to format it more reader-friendly and add a front cover to it anyway. i still think using html's named anchors to keep the FAQ entries, glossary entries, and tips/tricks all on a single page each is much better than having each faq, glossary entry, tip on its own page. [/QUOTE]

Verification