Quote:
Originally Posted by BeccaPrice
unboggling, do you have information about changing the location of your library, as in if you change computers or for some similar reason? I've noticed that it's a fairly regular question, and I'm wondering whether it should be documented somewhere that can be pointed to rather than people having to answer the same question over and over again.
My help file originally was aimed at novice users, but I've gotten a little into more complex stuff with the mobi_unpack plugin and documenting tweak books. I definitely don't want to get into regex and recipes for news downloads. I'm not sure whether changing the location of a library falls under my area or not.
|
There are topics in the calibre FAQ about moving library to other computer and using the library icon to re-set calibre to point to a library at the new location,
http://manual.calibre-ebook.com/faq....ter-to-another. It's the "Switch/create library" command under library icon, pointing calibre with the file browser button (to right of Location box) to an existing library. So yes, including that in help file is a good idea. I didn't go into that in "How I Manage", except possibly in relation to creating a new library.
Seems like a lot of new users also need to learn a whole bunch of other things. One thing I try to keep in mind in my own project is "what is my value added"? There is already a manual, a blog, a FAQ, a Quick Start Guide. If the user doesn't bother to read them — which I didn't the first few months, either — why will that user bother to look at my/your project? So I think it's important to focus on the value added. Which for your project, seems to me that it's a simple web-help file that is less intimidating than the FAQ, the manual, etc. If you explain more advanced topics like Tweak Books simply without confusing them, that's good. If it's too advanced or confusing you'll lose them.
There's a large distinction between "what level of ebook & calibre experience I am learning at" and "what level is my target audience at", and both of those are hard to define — for me it has been a very difficult distinction to make, which was why I changed my project to be more a map of "how I do things now".