Board Thread:News and Announcements/@comment-11733175-20150728100346/@comment-4405550-20150728152951

Just throwing my 2 cents in about the whole github idea, I don't think that is the best solution (by itself anyway). Wikia is far better as a CDN than files hosted on github; it's not even a fair fight. You would have to inevitably have to move every build back on to wikia's servers. which brings us back to the original problem. It's a nice place to collaborate, but it does nothing to solve the glaring security hole that pimp-slapped wikia.

We first need a comprehensive peer-review process to have your script added to the script list page.

Next, we should work together and create a github repo, and write a simple "github sync script". When an official release is made, a hook is called and the release is processed and the wikia pages are updated. It's just a simple deployment script, nothing special. I'm using a similar concept for a "SteamAPI" I wrote (ex ). I have the server space to spare if y'all need it.

The repo structure would probably work something like this: /Module_Name /Module_Name/package.json /Module_Name/deployment.json // file names and destinations for deployment /Module_Name/src/ /Module_Name/dist/ /Module_Name/test/ // All packages will have to provide stability tests (and pass) before being deployed

idk, maybe i'm over thinking this. But it just seems like this wiki in particular needs the support, security, and stability of an actual coding community. Hell, we could probably write some elegant integration scripts that dynamically show development progress.