Quote:
Originally Posted by Dopedangel
I always thought if someone collected all the questions asked in the forum and their answers. And then set them up by each device they are for we could get a very comprehensive manual not technically correct but still.
May be some of us regular forum users if we are willing to divide the work by Topics/(Devices)
I am willing to collect the questions and answers that I can find about all Hanlin v3 clones that come up as thats the device I use plus maybe directory structure as thats what my device uses (no wait I don't want to take the folder structure headache  ) |
I wouldn't necessarily start with the forum and pick out single topics from there. The relevant topics are so fragmented across many, many threads, I fear that it might take more time collecting them than writing them from scratch.
Quote:
Originally Posted by unboggling
1. Beginner's Guide to calibre. Overview, not technical. The conceptual framework. So technical revisions would rarely need to be included/updated. Authors/contibutors, a group of anyone willing who is past beginner stage.
|
This, in my opinion, is already nicely covered by the documentation as it is today.
Quote:
|
2. Power Users Guide to calibre, or Programming calibre. Authors/contributors, any willing power users, vetted but not written by developers.
|
This is the part that, perhaps, ought to be created. Although I see no need fo the developers to necessarily be involved, if they don't want to.
Quote:
|
3. Developer's Documentation. Whatever they think it should be since it's primarily for them, with perhaps a few power users looking at it once in awhile.
|
This would probably be rather useless. Users on this stage will be able to figure things out on their own, if not, they don't belong here. Also, it would take away precious time from development for little to no benefit. Chaleys post about why he doesn't like writing docs applies here.