KingPin Posted December 8, 2015 Report Share Posted December 8, 2015 Currently the wiki has been having issues on and off for a bit. so we have three ways to go forward from this. fix what we have. I am throwing resources at it, im getting nothing in return... its like a bad relationship..... the error logs lead to old answers that either dont apply or dont work. some plugins broke on new versions so its partially broken and needs to be manually fixed. Benefit : we have more control over the data, plugins etc Con : I am not always around to update and fix it due to work and that real life bullshit. :| move out to atlassian cloud hosted wiki already done. https://trinitycore.atlassian.net/wiki it doesn't have some of the plugins so the fancy tabs and all that jazz weren't converted over so it needs to be fixed. Benefit : Atlassian maintain, upgrade and fix any issues so more stability and availability. Con : Less control over data, plugins, etc convert to another wiki software. I have barely found anything functional, and thanks to the tabs etc provided by the plugin the exports dont exactly work so more manual work is needed. 1 & 2 seem more practical. im open to any suggestions. Link to comment Share on other sites More sharing options...
Magnuss Posted December 8, 2015 Report Share Posted December 8, 2015 As I see the decision is already done without any discussion. So suggestions are not needed anymore. Link to comment Share on other sites More sharing options...
Nay Posted December 8, 2015 Report Share Posted December 8, 2015 The "decision" is not set to stone. Right now, the fastest way to get to a working wiki is removing tabs and hosting it on Atlassian Cloud. A better long term solution is moving it to some open source software however this can't be done without spending a lot of time on it. I've been talking with the boys on IRC about converting to Github Wiki (repo + markdown) or https://readthedocs.org/ but to get this done we'd need the help of everyone (with pull requests to a repository created for docs only). Here's an example for ASP.NET by Microsoft: Source: https://github.com/aspnet/Docs Output: https://docs.asp.net/en/latest/ 1 Link to comment Share on other sites More sharing options...
Timesplitters Posted December 8, 2015 Report Share Posted December 8, 2015 Following you guys for a long time. I am web developer for 3-4 years and I can really recommend the github solution. We are using it at work too. If everything is up first, it will be pretty easy to update without any work and it is really stable. Feel free to contact me if you need any help regarding github. btw.: does anyone has the documents of the wiki for me to download? Really need it for our LAN at weekend.. :D Link to comment Share on other sites More sharing options...
Nay Posted December 8, 2015 Report Share Posted December 8, 2015 I'd like to know about your "without any work" solution... There's an old backup of the wiki at http://dduarte.github.io/tc_335_wiki/TrinityCore-Requirements_10682398.html Link to comment Share on other sites More sharing options...
Magnuss Posted December 8, 2015 Report Share Posted December 8, 2015 Pleeeeeease no Github wiki !!!!!!!!! Than better let it as it is. The only solution imho can be to choose a free Wiki software and host it on a serious place. All this cloud based semi-commercial ideas makes you only dependent and it is in opposition to any free & open source philosophy. Mediawiki, DokuWiki, Twiki and a lot of other solutions are free available and proofed. Personally I still prefer Mediawiki, it's easy, it's simple and everybody knows how it works and mostly all wiki-editors knows the syntax. And yes, as I already told, it's manual work to be done. Link to comment Share on other sites More sharing options...
hilycker Posted May 21, 2020 Report Share Posted May 21, 2020 +1 for MediaWiki Link to comment Share on other sites More sharing options...
Recommended Posts