Board Thread:Watercooler/@comment-5590118-20150701035141/@comment-24473195-20150710211957

Cqm wrote:

Perhaps it hasn't occurred to anyone here, but a style guide is only good to have when developing modules. Once it's on dev wiki, any changes to could cause errors on any number of wikis with no way to trace those errors. I'm not sure it's actually worth the time to make it. Indeed, I was mainly highlighting descriptive names.

You've raised an excellent point, a broken, unreadable or problematic module adopted by many wikias will automatically cause problems in all of them, and if the code is not readable, that would require a lot of time to fix or alternatively be deleted or blanked (return "").

As far as style guide is concerned I think it is almost always a good idea to have. This wikia could serve as a central hub where scripters come to learn, "train in sandboxes" and create modules. The style guide could, as an example, serve a way to certify modules that will be recommended / added / stable / beta.

One could also imagine 3 or more people collaborating on a single script/module/project suggested by Wikia staff/admins. If there aren't any projects to tackle, dev wiki module developers could always assist wikipedia to complete/fix their modules, and then port them here. It would be nice though, to have a common portal like the one wikipedia uses.

The point is that all this collaboration and module maintenance requires some sort of common ground, standards or guidelines.