Sem;colon wrote:You know what the problem with the wiki was/is? No one has access to it!
Exactly, and that's why I'm very excited about the work dequi is doing. However, if the wiki content is moved to a GitHub repository anyone can submit a pull request but if nobody with the privileges to merge the pull request bothers to do so then it's not going to be much of an improvement over the current system.
Aha, would have told... but some one broke the forum
so in the spirit of better to ask for forgiveness, then waiting for permission (doesn't really happen here I've noticed). I just went for it.
The goal was to see how far can I go without needing any sort of administration rights. Well here it is: pretty far, the only limitation I had was not being able to add images directly to the wiki repository when adding a tutorial (I could have used image links but in the long run could just break stuff if the image sources disappear)
So I've set up a basic framework that I think could replace the complete website and old wiki. https://github.com/EventGhost/EventGhost/wiki
To bypass the 'image upload problem' when porting the tutorial 'getting started' from the old wiki, I've created my own repository https://github.com/dequi/EventGhostWiki/wiki
used the wiki from that, mirrored the footer, sidebar and breadcrumb trail and added the tutorial with the images as I have full rights on my own repository, and just added a link to the https://github.com/EventGhost/EventGhost/wiki/Tutorials = this ensures a smooth user experience
, but in theory anybody can host their tutorials anywhere and add a link to it on the GitHub Wiki. We could even add links to youtube videos. In practice anybody could also come in and edit my tutorial and fix mistakes (well it's not actually my tutorial but you get the gist). If links break anybody can fix them.
go have a look: https://github.com/EventGhost/EventGhost/wiki
. The 'Getting Started' tutorial is on my repository, the rest is on the EventGhost repository (in my opinion the official documentation should be only text and in the Eventghost repository) but you shouldn't notice.
I think this way solves practically all problems, nobody needs to be merging pull requests, nothing needs to be build, anybody can start their own repository with tutorials, anybody can update the GitHub Wiki and add links to their own tutorials/documentation/plugins. nobody needs to be actively involved for the long haul. The website can just be a landing page that links to the GitHub Wiki or parts of the GitHub Wiki or just be the GitHub Wiki itself.
Sem;colon wrote:I can only speak for me of course, but if there was a centralized place to put/list plugins I would so going to use it. (If I have the possibility to, of course)
Feel free and go add them on https://github.com/EventGhost/EventGhost/wiki/plugins
- but be responsible
pearbear wrote:So why spend a bunch of time trying to make and maintain a plugin list for the website when we already have one and likely will have another in the future?
1. the one(s) we have is outdated and messy, nobody can update.
2. Topix needs a updated organised place to start from.
pearbear wrote:The only way I could see to automatically generate a full list would be if the Plugin Support section topics followed a strict format, which would require someone to go through and edit all the old topics.
Sem;colon wrote:btw. Not all plugins are stored in the Forum, krambriw for example, uses his own webspace to host plugins and just linked it in the forum.
Isn't it easier just to start a organised list? don't need no forum admin rights for that.
big issue is we need to be able to clean up after ourselves when were done moving.