Thanks to Patrick, James, Brunno and Ilario for the inputs.
From what was talked:
* GitHub Wiki could be a good starting point
* Support for multiple languages could be useful
* Adding new infrastructure that needs to be maintained would be better
to be avoided
Also, Ilario proposed a list of steps after enabling the GitHub wiki to
enhance the integration:
* move the whole lime-web/docs directory content (which is the
documentation) or even all the *.txt files from lime-web (all the
contents from the website) to the wiki of lime-packages repository
* continue using asciidoc syntax also for wiki
* keep the repository open for write to everyone
* fetch contents from the wiki and include them in our static website
built with Jekyll, this would be painless
* use directories for separating different languages on the Github wiki
(sub-optimal but easy), while on our website the multilingual stuff
is already implemented (I checked: Jekyll finds the files even when
moved to another directory)
Based on all this information, I've done the first step towards testing
this approach and enabled the lime-packages github wiki:
https://github.com/libremesh/lime-packages/wiki
I invite you for the following two weeks to start using the wiki.
Then we can review the usage and see if it fits or no, and which
improvement can be done.
Great job all! :)