18
Quote:
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).
GitBook is really good for specific information about 1 thing, like a module. But for general documentation, e.g. setting up your site, getting your rights set up and all basic XOOPS things, I think that a Sphinx documentation site would be better.
Examples of Sphinx documentation are
CodeIgniter,
ReadTheDocs etc. It's really clean, fast and easy to maintain/edit.
And you can export it to HTML too.
And the search is really good too ;)
