Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Hey, I was writing a very long comment about GitBook, Penflip, Leanpub, Softcover... then found your profile and realized you're Penflip's owner.

I'll still reproduce the comment here in case you can get some insights or anyone else is interested.

---

I've been researching on Markdown+Git book publishing (inspired by 'Markdown to Ebook'[0]) and found that there are already three 'GitHubs for writers': GitBook[1], Penflip[2] and Arturo.io[3]. Each has its own strengths and weaknesses:

# GitBook

Just a publishing platform backed by Git.

## Like:

- Standalone app.

- It is a bookstore.

- Publishes to major stores.

## Dislike:

- Ugly MSWord-like typesetting.

- There's no "social collaboration" at all, seems like it's just backed by Git. Not sure if small-scale collaboration (couple authors) is supported in the app or you have to deal with Git complexities yourself.

- Seems technical-oriented. No fiction categories.

# Penflip

Penflip seems to fit your idea more (note: now I know why it fits your idea :P), being collaborative like GitHub.

## Like:

- Collaborative.

## Dislike:

- It has no integration with bookstores.

- It's not a bookstore and you can't discover books easily.

- Looks more like a "free books" platform using 'free' in the FSF sense.

- It's hard to find a complete book to peek into, but the output seems to be just as ugly as GitBook's. AFAIK they let you customize output, but seems typesetting is not LaTeX-like and suspect won't be up to the job. Defaults are very important, it should be beautiful right out of the box.

# Arturo.io

Arturo.io's page is currently down (some cert error). It looked just like a bunch of webhooks for GitHub. Seemed immature and not for less technical users (still requires Git/Hub knowledge).

---

As non-Git alternatives I found Leanpub[4] and Softcover[5].

# Leanpub

Social bookstore and publishing platform.

## Like:

- Lean Publishing.

- The author-reader interaction is awesome.

- Their PDF output is beautiful.

- It's a bookstore (90% royalties!) with social-network aspects.

- Makes it really easy to create bundles, sharing royalties with other authors, etc. Really awesome feature.

- Tools for marketing are awesome. Integrated with Google Analytics.

## Dislike:

- I can't download their toolchain (but a local workflow is somewhat reproducible following 'Markdown to Ebook'[0])

- Does not rely on Git, but in Dropbox. No proper version control.

- No collaboration.

- Does not publish to major bookstores (but allows you to do so).

# Softcover

Major Leanpub competitor. In the publishing aspect seems to be pretty much the same, but their store philosophy is different. Their aim is not to be a bookstore but just a payment processor. You deal with your own marketing, set up your own domain.

## Like:

- I can download their toolchain. As far as I can tell, I could self-publish not using their platform without hassle. Not being tied to a provider is a HUGE selling point for me.

- AFAICT still supports Lean Publishing with their generated landing pages.

- Their PDF output is beautiful.

- It's a book payments processor. 90% royalties!

- Lets you control your own marketing, domain, etc. (has downsides)

## Dislike:

- Since you control your own marketing there are no social network aspects. Each book is supposed to be its own page. No bookstore. No way to explore and discover other books.

- A bit too technical.

- DIY version control, no integrated collaboration.

- Does not publish to major bookstores (but allows you to do so AFAICT).

Even though I'd love a Git-backed workflow I'll stick with one of Leanpub or Softcover because of how beautiful they look. I can still Git it myself. Major selling point for me and the non-techie friends I've been talking to.

The bookstore integration in both is a big selling point too!

I still consider Leanpub since I can replicate their toolchain and seems so easy and powerful for my non-tech friends. Letting users discover your book in the bookstore is really useful.

--- EDIT:

Now that I know you're from Penflip I will summarize:

I can see you're not a competitor with publishing platforms. As far as I can tell, you're more like GitHub, in the private-repo business instead of taking a cut from sales. Penflip seems great for social collaborative stuff, but I wouldn't choose it if I planned on selling my book.

As I said typesetting is very important. Your platform is awesome, but rendering really put off my friends. Penflip books like like HTML rendered to a PDF (which I guess they actually are). Did you consider moving to LaTeX-based rendering for PDFs? Markdown -> LaTeX -> PDF is the way to go.

Git is a great selling point, but secondary. Book authors just don't know it yet, even though it's one of those features that you just love when you try.

---

[0] https://leanpub.com/markdown-to-ebook

[1] https://www.gitbook.io/

[2] https://www.penflip.com/

[3] https://arturo.io/

[4] https://leanpub.com/

[5] https://www.softcover.io/



This is a fantastic overview of this part of the publishing space. GITenberg has a mailing list, and needs to start collecting breakdowns like this. I would love it if you would join us: https://groups.google.com/forum/#!forum/gitenberg-project


Thanks for your kind words, I recently researched the topic and thought someone might benefit from it.

I fail to realize how this could be useful for GITenberg though. Do you intend to publish the books or automate the publishing perhaps? If so, as far as I can tell GITenberg files are not structured, and won't lend themselves easily to automated publishing.

I guess the great thing about GITenberg is anyone could do their own structured .md version and request a pull. Would be cool with some automation to generate and release cool PDFs if .md file is available.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: