And what's wrong with GitBook?

- One single, easy to read and write, Github rendered source format (i.e. Markdown) for different output formats such as HTML, PDF, MOBI, EPUB,

- A documentation build is triggerable via Github Webhook, i.e. you can edit the documentation either with the GitBook Editor and it will upload the changes to GitHub, or you can make the changes on GitHub, and it will trigger rebuild of the book, so the readers will always have the latest and greatest version of the book, and you can choose whatever method you prefer to make changes.

The big issue with GitBook is that it's a book: it's hard to search inside of it, and if you need information about something, it's hard to find it (unless you know how or where to find it/in which GitBook it is).

And you can export it to HTML too.

Mamba wrote:
Quote:

The big issue with GitBook is that it's a book: it's hard to search inside of it, and if you need information about something, it's hard to find it (unless you know how or where to find it/in which GitBook it is).

It seems to me that you didn't spend any time of GitBook

Why are you saying that it's really to search inside of it???? What is wrong with the search inside a Gitbook?

And if you want to link several GitBooks into one, you can do it as well. The process is the same everywhere else:

a) you can have several small books, or
b) you can create a one monster book

Quote:

And you can export it to HTML too.

What do you mean by that??? The Gitbook is HTML as default:
https://xoops.gitbooks.io/xoops-installation-guide/content/