-
-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What we will do with the wiki? #259
Comments
See the wikiconvert.py from here. |
Here you go: |
It would be better it be a Gitbook multi-language. We already have in spanish (es). If you create the book and integrate it to GitHub (another repository), I will make pull requests with english (en) and brazilian portuguese (pt-br). I can create all and transfer to you at Gitbook and GitHub. Do you would want it? |
My experience with multi language wikis/documentation is that they are difficult to maintain and finally the changes only go to the main language (English). I prefer to maintain a small wiki -you'd probably noticed that I removed outdated pages- in English. Language that most of the people understand or at least can translate with Google Translator. |
Okay, all well. I was only thinking in enjoy what did done already (es). Gitbooks are elegant. But my notes in portuguese really can be managed in other sites or in private. |
Sorry for the delay, your wiki changes are merged now. |
You did not a merge and so my commits were not imported. The correct would be something like: git checkout yourbranch
git merge mybranch
git push yourbranch:master |
To convert to GitHub's wiki?
I want reactivate the project and finally use it on Arch Linux.
Or would you prefer the wiki as a Jekyll site in a
gh-pages
branch?I need to understand the full documentation.
The text was updated successfully, but these errors were encountered: