Using Gitbook for documentation

Speaker: joshmiller

Session Description

Drupal-based documentation: https://drupalcommerce.org/user-guidevs.Gitbook-based documentation: http://docs.drupalcommerce.org/

Documentation doesn't have to be a node. The idea of not using Drupal to write and publish documentation on Drupal may spark a bit of controversy. During this session the history of Drupal Commerce documentation will be discussed by the person who wrote the bulk of the documentation for both Drupal 7 and Drupal 8 versions.

My self-described effort for Drupal Commerce 2.x is to utilize any tool possible that both presents documentation clearer and empowers the community to add to the knowledge store in an easy and reliable way. I think Gitbook is that technology, and I would love to present my case and hear feedback from fellow Drupal contributors. Other big contributions (Drupal Console, Drupal Rules) have all started using Gitbook as well.

Since this is the community track and this topic may be controversial, the speaker would love to see audience participation, reactions to not using Drupal for such a content-heavy application. Perhaps even spark a larger discussion of whether other projects might be able to learn and use this approach to documentation in other parts of Drupal.

A live demonstration will be planned where we click edit on the Drupal Commerce documentation and it immediately lets us make a pull-request change, which will trigger a complete rebuild of the documentation with our changes.

https://2016.midcamp.org/session/using-gitbook-documentation