Show HN: Softcover – A publishing platform from the author of the Rails Tutorial
softcover.io
softcover.io
As the first author on the platform, http://conqueringthecommandline.com, and as the author of two other books (http://books.markbates.com), I can say that this was the easiest, and nicest tool chain I've worked with.
It took me from saying "I'm never going to write another book again" to "I have so many books I want to write now!".
1. Am I allowed to sell the files elsewhere? For example, sell the .mobi file on Amazon Kindle and publish a printed version via CreateSpace.
2. Are the files watermarked at all with Softcover's branding?
3. Is this open to authors everywhere or are there restrictions?
4. Will this handle sale taxes for authors? I'm a Canadian author with a PST/GST account, will I be able to collect that from Canadian customers?
PS: The Browse and Setup links on conqueringthecommandline.com are meant to point to softcover.io, so they are broken at the moment.
1. Am I allowed to sell the files elsewhere? For example, sell the .mobi file on Amazon Kindle and publish a printed version via CreateSpace.
Yes, you retain copyright on everything you make and can do anything you want with the files. They get built on your system by Softcover's open-source toolchain, so you have complete control.
2. Are the files watermarked at all with Softcover's branding?
No, the books have no Softcover branding. The online version has an inconspicuous Softcover-branded footer by default, but even that can be removed with a simple config setting, as described in the manual (http://manual.softcover.io/book/marketing#additional_informa...).
3. Is this open to authors everywhere or are there restrictions?
Softcover is open to anyone, and there are no restrictions.
4. Will this handle sale taxes for authors? I'm a Canadian author with a PST/GST account, will I able to collect that from Canadian customers?
I don't know about this one. If you join the [Softcover Google Group](https://groups.google.com/forum/#!forum/softcover-publishing), I'll introduce you to my cofounder Nick Merwin, who is in charge of stuff like this. If we don't currently support collecting Canadian sales tax, we might be able to add it.
Long answer: Over the course of development there had been some thought as to whether or not the Softcover site would just be an informational site for the Softcover gem and a place for authors to get their sales stats, and then each book page would be its own separate thing that would be more or less fully-customizable by the author. Point is that most people would have had to be interacting with the site on a desktop because that's where they'd need to do things like install gems and run the server.
We've kind of moved away from the idea of having a Myspace free-for-all, towards something that is more of a designed garden, planning on allowing a good deal of customization on the book side – each book page loads a completely separate stylesheet from what is used on the rest of the site for that reason.
With that I'm going to be focusing on redoing a lot of the presentation side to meet what we'll need, and a part of that will be responsive styling.
Looks like it's time to start reading and comparing.
I see that Michael is answering questions here, so here is one. If someone decides to publish... let's skip anarchy, let's say erotic and porn novels, is this still game?
Now that I think this through, someone can use toolchain and get their stuff published anyway, I would just like to know, where are boundaries of your service?
I'll also look into using the sales / hosting platform too. I'm a little hesitant to put that in someone else's hands, but you guys have done such a great job that I'll probably end up giving in.
Can't wait to start working with this!
We've definitely looked into print. It's a tough nut to crack, and the ecosystem might not be mature enough yet for automatic integration. Lulu, for example, built an API, but not enough people used it, so they closed it to new developers. I'd love to offer a print solution at some point, though, so we'll keep an eagle eye on it.
In any case, the Softcover production system uses LaTeX, which is designed to make print-quality PDFs. The default output is optimized for tablets, but adapting it to a print-ready version is fairly straightforward. I expect we'll incorporate that into the typesetting system at some point. But unfortunately right now you'll have to do a lot of work by hand no matter which production system you use.
Also if anyone out there hasn't read Michael's Rails Tutorial, read it now. The best and most thorough tutorial I have ever read on any topic, it opened my eyes to modern web programming.
Kind of reminds me of a LaTeX for the web. Source code files -> properly formatted documents. I may use this in a future project. Looks awesome!
One of the main concerns for any new book is marketing. Are you planning to address this issue?
I'm on os x, using ruby 193
Reminded of when of a youtube video where you talked about this idea and how you solved your money problems through the rails tutorial.
Softcover just pulls in the HTML and eBooks that are compiled from the source code, as well as the book config files, and generates the views and links.
It's a model that has worked in the past for some people, including this recent example I heard about on NPR: http://www.sciencefriday.com/segment/02/14/2014/andy-weir-th...
He slowly published each chapter, then when he finally finished the book, he posted the ebook versions for free on his site. Eventually he added it to Amazon (and had to attach a price to it because they don't let you give away ebooks) to help people load the ebook onto their Kindle with less friction than making them download and transfer the file, he found that he was selling more copies of the book than he was giving away for free on his site.
It's exactly that model of openly sharing what you are working on with the people that are going to use or be entertained by it that we want Softcover to encourage.
-bowerbird
- Softcover comes with an industrial-strength, open-source production system. This means you can write heavily formatted books with cross-references, code listings, tables, etc., and interactively build them locally, all without being locked in to a proprietary system.
- Softcover's HTML books are first-class citizens. The online version of the Rails Tutorial is a key part of its marketing strategy, so it has to be polished and prominent.
- Softcover gives you your customer list. Letting customers opt-in to share their email is fine for more casual authors, but it isn't ideal if (like me) you're trying to build a business.
- Softcover supports custom domains. It's important to me to use a custom domain for branding/SEO and so that I own my own traffic.
you've seen other competitors before, and will probably see a whole lot more, and all of them won't be as incompetent as those you have faced down in the past.
ok, for those of you who might not know, peter is the force behind leanpub.com...
which is highly similar to this site, but has been around for a few years already.
so, no, this is not a "new" model, and there _will_ be similar tool-chains that will come soon, and i can guarantee it, because i'll be releasing one that i've been working on for over a _decade_ now.
but we do not need internal squabbling, because killing corporate publishers is gonna be hard, no matter how many of us are committed and dedicated to doing it.
yes, they are dinosaurs, and yes, they _will_ go extinct, eventually, even if we do absolutely nothing. but they are also dinosaurs with _very_ deep pockets, and that's a significant factor in the greedy money-ruled world we have today.
so welcome to the revolution, softcover. strap on a helmet, and let's get to work.
-bowerbird