However, there are many downsides of using the website for editing (like you can't combine changes to multiple files in a single commit). I prefer using a real editor locally, but using any other Markdown processor might give slightly different results. Therefore I use flavor [1] to filter the Markdown document through the GitHub API for reviewing it locally before pushing.
[1] http://brettterpstra.com/2012/09/16/easy-command-line-github...
It is a semantically readable text document, that is easy to write and understand by humans too. It really shines when you do something with it after you wrote it (e.g. make a html and style it).
I use it as a plain file/folder wiki and to have a future-proof format for the wiki.
I've always found wiki's and the like extremely difficult to organize. Lots of knowledge and little things, but it always runs out of hand quick.
The problem is the associative/ribosomal nature of information and the quickly missing context.
We'd need to build a brain that gathers and understands context and files in all the cross-connections. Until google is done with that we are stuck with what's manageable: A hierarchy (folders) with some limited manual cross-links and full-text search.
I'm using the yellow cms, with a wiki plugin:
http://developers.datenstrom.se/edit/plugins/wiki-plugin/
All running in a local http server. It's synced to my phone via Owncloud. On my phone I edit the plain files with JotterPad and sync with Foldersync.
But I'm not super happy with yellow:
- missing a tree view (I hacked together something but it's ugly) - special syntax for the title (but you can ignore it mostly) - special syntax for the wiki stuff - was difficult find the setting to change to .md file endings (bad/missing documentation) - requires an index.md in every folder
What is really nice: i can drop a file in to a public version of the wiki and send a pretty link to someone.