View Single Post
Old 12-12-2020, 06:05 PM   #9
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by mst View Post
Great, thank you! I think I figured it out now.

Do you think it makes sense for me to write up a newbie's guide to organizing books on KoReader with Calibre, or does this exist already? I think this would help new users clear the fog. Happy to do it, unless it's redundant.
Guides are great as a resource and can help newbies with specific workflows. Any guide is welcome no matter how specific the workflow is and how the writter approached its target. It has the status as "works for me" and indeed can works for others too.

For the wiki the expectations are different. From the README in github:

Quote:
document lesser-known features on the wiki
So it depends on the approach. There's a wiki page for the calibre plugin that doesn't cover the metadata search (because it wasn't part of the plugin until recently)

In wiki pages it is better to document what can be done with the plugin.

Elsewhere you can use a more natural language and document what you want any way you want, without too much restriction.

See, for instance, https://medium.com/@candide.uyanze/h...e-f727f04e197d

It is a valid workflow for the author but very difficult to translate to wiki pages. It is also not the only specific way of getting that done.

So, to sum up:

1. All contributions are welcome.

2. The wiki is expected to document features and use specific bits as examples. You're welcome to write a guide using a new wiki page and adds link where you see it fits. Keep in mind that the wiki is a moving target and any workflow you wrote can be rewritten by somebody else in a way that matches better their needs.

3. There's other places on the web to write these guides, keep autorship and prevent others from modifying your workflow in a way you don't agree with.

tl;dr: All contributions are welcome.
pazos is offline   Reply With Quote