Quote:
Originally Posted by eschwartz
Hmm, I don't personally see much difference in using a Wiki vs. markdown -- except that many people can edit a Wiki, but only a collaborator can edit a github repository.
Unless you mean ease of actual editing?
|
Hm, there's just something about a Github repo that seems more lucid than the MobileRead wiki. Maybe because everything is in folders? Hard to put my finger on it.
Interestingly enough, I found that Github repos do
come with a wiki automatically, and they can be
edited by anyone if you configure it that way.
But yes, I do prefer markdown to markup for editing. The syntax highlighting and various other features of GH-flavored markdown are very tailored towards code, which is what we're dealing with when we talk about the ins and outs of advanced eBook creation. GH is also suitable for holding scripts for processing markup/CSS (maybe nobody else has those, but I do).
Anyway...maybe I'm being elitist, but I'm very tempted.
Quote:
Originally Posted by Hitch
Bear in mind that there is yet another part of the publishing process, called the PW (Publishing Workflow) that happens AFTER you hit "save and publish" that yet alters the book further. For example, setting the SRL (Start Reading Location): that is set in the PW, not before one hits "save and publish."
|
I'll admit that, while I have months of eBook coding and testing under my belt, I haven't actually run anything through KDP to date, which means you far outrank me in experience there. I've never even heard of the PW, and my impression on the SRL was that you simply have <reference type="text"/> in your OPF guide, and that's taken care of. Do you have any articles, threads, or on-the-spot wisdom on PW and the SRL that you'd care to share?
Overall, I am glad that K4iOS is shaping up! (Just in time for me...)
Quote:
Originally Posted by Hitch
I don't know of any centralized repository, above and beyond what's here. Liz Castro started her blog way back and sought support for it, and even though a number of us did (support it), it went the way of the dodo, vis-a-vis eBooks. Maybe she just didn't feel that there was enough interesting stuff left to investigate. ;-)
And other than here, everybody else is either a) making their own books, to publish, as Indy Authors/Publishers, and not that interested in a repository, or b) they're like me, with their own shops, and we're more focused on trying to stay ahead of the horrors of the retailers, or those of the clients, than we are on contributing to a repository. Not to mention, speaking for myself, it gets sort of tiring. I mean, there are things (like the SRL) that have changed 3, 4 5 times in fewer years. NCXes, TOC's, and the like--what works one day doesn't the next. It's hard to keep up with, but you have to if you're doing it commercially.
|
(Aside: does Liz ever hit up MobileRead? Her blog has helped me out of some tight spots and I really respect her trailblazing ways.)
I definitely get what you mean. It's a bit like, if you do it every day, all the data is in your head, so putting it online is just more effort. To me, there are really three primary sources of information for eBook creators:
- MobileRead Forums & Wiki
- Official Guidelines From Companies
- Random Articles & Forum Threads
...Basically, your best friend is Google.