Regarding forking github wiki's, you can via the wiki's git repo, eg: https://github.com/iron-io/iron_mq_ruby/wiki/_access , but you can only access it via git cli.
Perhaps better is using Github Pages, http://pages.github.com/ , then you get full github support for it so people can use github forking, pull requests, issues, etc. Makes it much more collaborative. And you can use Jekyll with it so you can write pages in markdown and/or HTML. We do all our public docs with it for those reasons, eg: https://github.com/iron-io/docs On Fri, Jun 28, 2013 at 9:22 AM, Marc Weber <marco-owe...@gmx.de> wrote: > Excerpts from phreedom's message of Fri Jun 28 18:15:44 +0200 2013: > > Using git as a backend for wiki is a huge win. Not sure how easy it is > to > > start contributing to github wiki for a > $RANDOM_PERSON_WHO_SPOTTED_A_TYPO. > It can be done trivially. As experiment I wrote a "vim-wiki": > > http://vim-wiki.mawercer.de/wiki/index.html > > There is an edit link, no login required. My hope is that its non > standard so bots fail. > > Till now it seems to work. > > I neither say the syntax nor the implementation is pretty, but it > actually gets the job done I wrote it for. > > Code is here: > https://github.com/MarcWeber/vim-git-wiki > > I'm not responsible for making any decisions about the wiki. > I also think that we have enough developpers to get anything done we can > imagine. But we have to know where to go. > > The nixos wiki also gets it job done - even containing spam. > However I still feel bad about it hosting spam. > > So which is the best we should manage this? > > Marc Weber > _______________________________________________ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev >
_______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev