I came across GitBook when reviewing documentation for a potential integration into a project I serve as Product Manager for. As the "audience," I was quickly impressed with the simple and clean presentation of the content I was reviewing. As we'd always lacked simple user documentation, and hated the help desk integrations with our web site's CMS, I decided to pilot GitBook the next day.
I had a very solid site up and running in mere hours starting from nothing. I really didn't have to find any work arounds - what I wanted to communicate could just happen since the platform handled everything I wanted - demo videos, screenshots, tips, narratives, cross links. Linking to our domain was simple as well. GitBook was intuitive and I did not really need to go into documentation. In addition to the combination of simplicity and clean presentation, having a commit-based versioning system is quite helpful and easy for our dev team to understand.
I've found that GitBook solves the problem of creating documentation sites efficiently - no unneccesary extras and nothing really missing. I'm an evangelizer internally for the product. Review collected by and hosted on G2.com.
There is nothing major missing or getting in the way. My dislikes are all small - make commit messages more prominent in the workflow, a little more layout customization for pages with more visual content. Review collected by and hosted on G2.com.
