Each part of the book is a directory and each of the chapters in that part are files in that directory. You can see the source code that creates this book here.
It is an alpha - lots to neaten up and lots of details to work out, but a good starting point for discussion. You can see the result here: (this link will likely stop working once we find it a proper home). I wrote a simple script that takes output from booki (our current tool) and turns it into something suitable for gitbook. Gitbook "Modern book format and toolchain using Git and Markdown" seemed to tick a lot of boxes and so (while waiting for my plane at Denver airport) I thought I would take advantage of the free wifi and give it a test drive. Uses widely used standards that will outlive any particular platform choices we makeįollowing a few different conversations at different sprints over the years we grew fond of the idea of markdown stored in a git repository as a solid base that will help us meet many of the above requirements and started to look for a set of open source tools that would allow us to do this. Translation infrastructure, so that our language communities can easily create different language versions of the manual, and can easily keep these up to date when the manual is updatedĬan handle growing documentation needs (including end user documentation for extensions) Version control so that people can work on different 'branches' of the documentation at the same time (that we can merge independently when ready for publication)
#GITBOOK EDITOR DOWNLOAD PDF#
Produces a 'good looking' html version of the bookĪbility to export to different format (including ebook and pdf and output suitable for traditional publishing) Simple user interface that makes it easy for people to contribute
We'd like to move the guide somewhere that has better support for more of the features that we want, which include For a while we have been thinking about some new infrastructure for CiviCRM's user and administrator documentation.
0 kommentar(er)
