Writing made easy

get it
#1 Product of the WeekDecember 23, 2015
  • Michael Musgrove
    Michael MusgroveMarketing guy.

    Open Source, easy to use, minimal UI, perfect tool for what it's meant to be used for. Lightweight.


    Hard to think of any. It's under-rated.

    If you have a project that entails many chapters or is organized in an outline format, this is super-helpful. I love Git Book. Totally underrated software.

    Michael Musgrove has used this product for one year.
  • Anne Gentle
    Anne GentleProduct Manager

    Lets authors use a development-like workflow


    Some of the plugins were outdated or unmaintained; PDF was not print-ready to my specifications.

    I used GitBook to collaborate with other authors on my book quite related to the subject, Docs Like Code ( I loved the ebook output but for print I had to use additional tools.

    Anne Gentle has used this product for one year.
You need to become a Contributor to join the discussion.
Ingo Radatz
Ingo Radatz@llabball · CTO, R&D at HSH / Berlin, Germany
For me the change tracking (version control) is one of the most interesting aspects. Imagine a law text which have to adopt again and again the society's changing understanding of the regulated topic. Years later everyone can read why everything is like it is today.
Samy Pessé
Samy PesséMaker@samypesse · CTO, GitBook
@llabball Exactly, for example here is the source of the French civil laws on GitHub: and the output on GitBook:
Aaron O'Mullan
Aaron O'MullanMaker@aaronomullan · CEO, GitBook
Hi it's Aaron from GitBook here, I'm travelling today for the holidays, but I'll do my best to answer any questions you guys have ! P.S: You can also reach me by email at
Yoav Anaki
Yoav Anaki@yoavanaki
@aaronomullan What are some of the less-obvious use cases for this?
Aaron O'Mullan
Aaron O'MullanMaker@aaronomullan · CEO, GitBook
@yoavanaki Well here's a few things GitBook is currently used for: * Documentation: ** Public and API docs (e.g: open source projects) ** Internal documentation ** Enterprise documentation * Books ** Technical dev related books ** More traditional non-fiction books (politics, journalism, guides, etc ...) * White papers ** Both the french and taiwanese governments use it as part of their open-data efforts * Research papers ** There's a lot of interest from academics, I think GitBook is much more approachable than Latex for example There are many others. It's also been used for blogging or as an online public diary, which are odd but interesting use cases. There's many other interesting use cases, one answer is probably too short to cover them all, but we've seen teachers use GitBook with their students to write short novels. I think there's a lot of value in bringing powerful tools such as content-versioning to other non code related verticals, with tools that are accessible to most, not only devs or tech enthusiasts.
Zac Pappis
Zac Pappis@zacpappis · DuckDuckGo
@yoavanaki @aaronomullan We've been using it for DuckDuckGo's open source documentation: This seemed to be the one solution that allowed us to keep our docs hosted in an open repository (so anyone can contribute) that's synced perfectly (for instantaneous changes) while providing features like search, built-in Next/Previous buttons, ability for custom CSS, a good mobile experience, etc. Also, maybe more opinion than anything but unlike or, Gitbook is free-form markdown, but without the initial technical overhead of Github pages or something like
Ross Currie
Ross Currie@rossdcurrie · Founder, Brutal TearDowns
The collaboration aspect is cool, though this seems to be missing a lot of the features that I've come to expect from the various "writing made easy" tools out there right now. Things like Hemingway mode (no backspace), typewriter mode (keeping cursor centered as you carriage return), fullscreen/distraction-free mode, etc. Also, I feel like 'by default' I want my writing to be private (what I would consider to be a base feature) - being able to share my writing publicly feels like something I should need to pay for. Though I get that's not really the way github operates
John Tan
John Tan@john_tans · Growth & Product
Totally essential!!
Yoav Anaki
Yoav Anaki@yoavanaki
This is brilliant. Definitely think that version control should move beyond code. I know a company that does this for building plans. It feels like creation tools are years ahead of collaboration tools, so adapting git to support more mediums just makes sense, and I love the execution here on GitBook.