Thoughts on ebook parts and a sneak peek of STAR WANDERERS: DREAMWEAVER (aka Star Home)

There’s been some discussion on forums and the blogosphere recently about the different parts that should make up an ebook, and what order they should be in.  J.A. Konrath just did an interesting blog post on the subject, in which he picks his own books apart and gives some advice.  At the moment, here is how I’ve structured mine:

  1. Cover image (600×800).  Usually the same as the high res one I upload separately to publish, but may be different.
  2. Copyright page.  Very brief.
  3. Table of Contents, with hyperlinks to each chapter.
  4. The book blurb, which also appears in the book description on most retail sites.
  5. The book itself.  When you open up the ebook for the first time, this is where it automatically starts.
  6. A brief author’s note, in which I tell the story behind the story–how I came up with the idea, what the writing process was like, and any other relevant influences worth mentioning.
  7. The acknowledgment page, in which I list my first readers and anyone else who helped out with the book production.
  8. A couple of sample chapters for other books.  I only put these into the novels, though–for the novellas, they would take up more than 10% of the total ebook content.  That’s pushing it.
  9. A page promoting the Writer2ePub plugin which I use to build my ebooks.  It’s a really awesome plugin, and I figure the developer deserves some acknowledgment for his work.

I don’t totally agree with all of Konrath’s advice.  For example, I think the copyright page is small enough that it can go in the front without inflating the sample too much.  Then again, I keep the copyright page pretty brief–none of these ridiculous “unauthorized reproduction of this content is piracy and piracy is evil blah blah blah.” Not that I want to be pirated, but I figure my readers are smart enough to know all that stuff already.

In general, though, I think Konrath’s advice is mostly right, especially the part about not padding the end of the book with sample chapters.  I’ve seen a lot of readers complain about getting to the 90% mark of an ebook, only to find that the story is over and the rest of the content is filler.  As a reader, I’ve experienced that disappointment myself.

However, I do think it’s important to include at least some sort of mention of other available books in the back matter.  Until now, that’s meant sample chapters, as long as they take up less than 5% or so of the total content.  Since my Star Wanderers novellas are so short, I haven’t added any sample chapters to them–just a brief plug to sign up for the email list.  And for my novels, I only add a prologue or first chapter, so as not to take up too much space.

Recently, though, I’ve started to rethink this strategy.  When I finish a book, I’m not usually in the mood to read a sample chapter of the next one unless it’s a direct sequel that picks up right where the end of the book leaves off.  I will eagerly browse through book blurbs, though, especially if they’re in the same series or genre.  A good book blurb is much more likely to influence my decision on what to read next than a sample chapter, which I usually just skip over.

For that reason, I’ve decided to take out the sample chapters in my novels over the next few weeks, and replace them with a much shorter page containing a thumbnail cover image and book description for the next book.  I’ll still keep the author’s notes, since I enjoy writing them and I think they’re a good way to engage my readers.  It’s one of those things that makes it a Vasicek book.  But yeah, the sample chapters are gonna go.

This also opens up the possibility of trading book blurbs with other writers.  For example, my friend Kindal Debenham writes space opera stories in the same vein as my Gaia Nova series.  He shows up in my Also Boughts every now and again, so I know there’s a bit of a crossover in our readership.  I haven’t approached him with this idea yet, but if we both included short book blurbs for each other in the back matter of each of our books, we could cross-pollinate our fan base and point readers out to some books they’d be likely to enjoy.

That’s just a thought.  It will be interesting to run with it.

As for the sneak peek I promised in the title of this post, I’ve been playing around in Gimp the last couple of days, working on the cover art for the next Star Wanderers novella while waiting for my editor and illustrator to get back to me on Stars of Blood and Glory.  Here’s what I came up with:

SW-V Dreamweaver (cover)

What do you guys think?  That’s a pretty cool nebula, isn’t it? Hubble is so friggin awesome. 🙂 I took this from a new image of NGC 5189 that was featured on APOD a few months back.  The moment I saw it, I knew I’d be using it in a Star Wanderers cover. 😀

Dreamweaver is a parallel novella to Outworlder, and covers the events of that story from Noemi’s point of view.  I wrote it back in the spring of 2012, and put it on the back burner while I focused on finishing the other ones in the series.  In the author’s note of Fidelity, I think I referred to it as “Star Home,” which was originally its working title.  I was going to do all the other parallel novellas from Noemi’s point of view, but I’ve since decided to branch out with the other characters.  Right now, I’m writing a novella from Jakob’s point of view, which is turning out to be quite interesting.

After Stars of Blood and Glory is published, I plan to put up Star Wanderers: Dreamweaver, hopefully within a month or two.  After that, I’d like to bundle parts I-IV into an omnibus and put that up as The Jeremiah Chronicles, in ebook as well as print-on-demand.  A lot of that depends on cash flow, though, since I plan to hire an illustrator and go all out.  If any of you have any suggestions for a good artist / cover designer, please let me know!  The Star Wanderers books take place in the same universe as the Gaia Nova series, but they have their own distinctive feel and I’d like to find someone whose art reflects that.

That’s just about all for now.  It’s getting late, and I plan to wake up early to write.  President’s day is kind of a useless holiday–in fact, most one-day holidays are kind of useless when you’re a freelancer.  So yeah.  Later!

Adventures in ebook formatting

Under the hood of my latest ebook release, Star Wanderers: Part I.

So a couple of days ago, I set out on a quest to figure out a better way to build an ebook.  In the process, I ended up learning WAY more about ebooks than I’d bargained for, in the most awesome of possible ways.  Seriously, I don’t think I’ve ever felt so empowered as an indie author as I do right now.

My old process was extremely convoluted.  It basically involved saving my manuscript as HTML (introducing all kinds of excess code) and using four or five programs to cobble together a Frankenstein-like creation, with bolts sticking out of its forehead and extra arms and fingers sticking out of weird places.  The tools I was using were like blunt instruments, and I was operating them blindfolded.

So what changed?  Well, three things:

  1. I added the Writer2ePub plugin for Open Office / Libre Office,
  2. I downloaded an open-source epub editor called Sigil, and
  3. I watched this video:

So what did I learn?

<geek>

First of all, that ebooks are WAY simpler than I thought they were.  An epub is basically a zipped folder containing HTML files for the text, jpgs/gifs for the cover and any interior illustrations, a CSS stylesheet, maybe some extra fonts (if you want to get fancy), and two additional additional files ending in .opf and .ncx that look a lot like HTML files.

So why is this so exciting?  Because it means that if you know HTML/CSS, you can build a fully functional epub file using only notepad, windows explorer, and the command prompt.  THAT’S IT!  And if you want to learn HTML, you can do so for free at w3schools.com.

Basically, an epub is structured just like a website, except that an ebook reader reads it instead of an internet browser.  If you can build a website, you can build an epub with very little trouble.  Even if you can only tweak a website, you can build an epub with very little trouble.

</geek>

In other words, the barriers to entry for ebook publishing are ridiculously low.  If you’re patient and a good learner (or hell, just a good learner), there is not a single reason why you need to spend any money to format your ebooks, upload them directly to retailers, or do anything else.  Using tools that are 100% available for free, you can create a product that looks every bit as professional as anything coming out of New York–in many cases, even more professional.

So what’s my new process?

1) Format the master file in Open Office.

This includes adding the copyright page and table of contents, adding anchors (in OO they’re called “bookmarks”) and hyperlinks, adding the author’s note and acknowledgments, any teasers, etc.  I save the file in open document format, add “Smashwords Edition” on the copyright page and save it as a .doc file for Smashwords.

At some point, I’m going to upgrade to Libre Office, but I haven’t gotten around to it yet.  When I do, it’ll basically be the same thing.

2) Export as .epub using the Writer2ePub plugin.

I cannot tell you how happy I am with this Open Office / Libre Office plugin.  It pulls out all of the unnecessary formatting and breaks up every chapter into a separate, cleanly coded HTML file, all bundled together into a fairly simple epub.  SO MUCH BETTER THAN SAVING AS HTML.  Or Mark Coker’s “nuclear option,” for that matter.

I don’t add the cover at this point, though.  Writer2ePub adds some weird stuff if you do it that way, and I find it easier just to code it manually in the next step.

3) Finalize the .epub in Sigil.

Sigil is basically just an HTML editor with some extra functionality that allows it to build an epub from those HTML files.  It’s easy to learn, simple to use, and tells you exactly what’s wrong when something breaks.  Unlike Calibre and Mobipocket Creator, you can always see what’s going on underneath the hood.  Simple, clean, and elegant.  I love it.

This is the phase that takes the most work.  I add the cover, fill in the relevant metadata, tweak the CSS stylesheet for margins and indents, add the book guides, build the table of contents, etc.  If you want to know exactly how I do this, let me know and I’ll write up a post on it later.  It’s a little technical, but not too difficult.  Like I said, if you know even a modicum of HTML, you can figure it out.

Once this step is finished, I have the final epub version of my book.  I upload that to Pubit! and Kobo Writing Life, and just about anywhere else outside of Amazon where I sell my book.  Someday soon, Smashwords will hopefully allow you to directly upload an epub, at which point I’ll do that here as well.

4) Convert to .mobi with KindleGen.

Amazon uses its own proprietary format for ebooks, unlike everywhere else, which takes the open source epub format.  This is probably because of all the weird and funky stuff that Amazon likes to track for data collection purposes, although honestly, who knows?  A mobi file is about twice as large as an epub, and I suspect that that’s the reason.

KindleGen is a free program that Amazon has made available to developers in order to facilitate conversion of epubs and other ebook formats into mobi.  It’s a command line tool, which means that you have to get a little retro to use it.  But hey, I grew up in the 90s with DOS, so it’s actually kind of nostalgic.

Once you’ve got KindleGen installed to c:\kindlegen, all you basically need to do is go to the file folder where your ebook is saved and enter the following command:

c:\kindlegen\kindlegen mybook.epub -c1 -verbose

“mybook.epub” is whatever you named your epub file, “-c1” stands for standard DOC compression, and “-verbose” stands for verbose output (whatever that means).  There are other options you can enter, but I’m not sure what they do yet.  All I know is that if you want to convert from epub to mobi, this will give you a clean result.

There are a few small things that get lost in the conversion, so you need to add them as redundancies in the epub.  The biggest one I’ve noticed so far is the paragraph indents: if you go into the CSS stylesheet using Sigil and add p { … text-indent: 2em; … } that should fix it.

And that’s it!  Once this step is finished, I’ve got the final mobi version and can upload that directly to Amazon and my kindle.  Once that’s done, my book is available from every major ebook retailer in every country in the world.  Total time = maybe an hour (plus however long it takes for the retailers to publish the files to their stores).

I know it’s 2012 and this is old news by now, but do you have any idea how cool this is?  With one hour of work and two or three programs, all of which are available for free, I can produce a clean, professionally formatted ebook, and sell it around the world instantaneously with a marginal cost of zero.

And now, because I took the time to learn how to use the tools, I can be confident that there aren’t any bits of rogue or useless code in it either.  The only “black box” is really the mobi format, but I could probably crack that and figure it out if I wanted to.

So yeah, needless to say, I am extremely happy to be an indie writer. 🙂