This is the wikiengine github itself uses:
https://github.com/gollum/gollum
We could provide a readonly wiki on our page and link to gh to make changes. This would prevent spam mostly and provide a nice webinterface to make changes without doing user management by ourselves.
A general note: We switched our wiki system from gh pages to mediawiki because nobody contributed at github. I'd like to know what goal we want to achieve with a switch and how we can achieve this with a technology switch.
Note that it was a lot of work to setup mediawiki and make a void theme for it. If you like to throw that away, then your solution needs to solve problems in the long term and safe us enough time to be worth the effort. For that, I want to know what problems we need to solve and how you plan to solve them.
I'm very new to Void but from what I have seen:
Is our problem spam? -> Nope
Is it the lack of contribution? -> Yes
Is it the poor quality of our documentation? -> Yes
In my opinion I rather have something hosted on github an pushed to a wiki than having to open an account and create a system of reviewing and publishing around this platform.
It could be something easy as just a few markdown-files with yaml-variables which generate html-pages that are hosted on github.
Editing/Creating new content is as easy as making a pull-request and can go through formatters and alike.
A `Makefile` would be enough of a command line tool to fit the needs. Don't make it too complicated.
On Tue, Oct 25, 2016 at 12:47:47AM -0700, Anachron wrote:
> In my opinion I rather have something hosted on github an pushed to a wiki than having to open an account and create a system of reviewing and publishing around this platform.
^this
Although I doubt a technology switch would encourage contribution, I do feel like this would better follow the spirit of Void.
Our distro wouldn't exist without the wonders of git, at least it wouldn't look anything like it does today. Our repo is similar to the AUR in that anyone can contribute packages, but the community reviews every package before it becomes part of the repository. Why should our wiki be any different?
As fun and "wild west" as Void feels sometimes, I also know that Void is held to a fairly high standard, and I think the same should be of our documentation. Do we want to just create another Arch Wiki? What's the point? We can just use the Arch wiki, if we're going to bother with documentation in the form of a wiki it should be held to a very high standard to differentiate itself.
Otherwise what's the point? In that case, we should just write documentation for Void specific nuances, we don't need to bother with an actual wiki at all, nor go into the type of detail that the Arch wiki does for most individual applications.
But if we want to do this, perhaps jekyll could be of use.
I've been playing around with modifying https://github.com/voidlinux/voidlinux.github.com all day to generate a wiki. I have been moderately successful so far, with a few things to be resolved:
1. Navigation: There's sitemaps - probably using this data could be used to generate navigation
2. Search: There's https://github.com/christian-fei/Simple-Jekyll-Search
3. Layout: The current layout of the void website has a gargantuan logo with a blurb rendered on every page... I think that needs to only appear on the home page.
Stop.
Discussing.
Platforms.
When there is content, there will also be some means to display it.
Until then, please stop throwing out solutions for a problem that doesn't exist.
Probably spam is the greatest issue - for those responsible for deleting it I imagine.
Looking here:
https://www.mediawiki.org/wiki/MediaWiki
This is quite a big professional project, bringing Wikipedia to the Web for example.
Why not ask them how to stop the spam, surely Wikipedia doesn't delete it manually?
The wiki is already pretty good, it would take a long while to read it all, although it can always be improved or extended. All distro's have some outdated and incomplete documentation which can still contain much useful information.
I put together a proof of concept of the proposal at https://github.com/pbui/void-docs
I've only ported three pages from the existing wiki, but the document generating infrastructure works:
- http://weasel.h4x0r.space:8000/void/installation-guide.html
- http://weasel.h4x0r.space:8000/void/live-images.html
- http://weasel.h4x0r.space:8000/general/disks.html