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

Cqm wrote: Why are you going to cater to people who might not know about onlyinclude when if they're using #invoke they're technically minded enough to have some grasp of lua? If the module doesn't have proper error handling that's the fault of the author who probably created the template in the first place and therefore has an idea of what's gone wrong. The only possible way to use lua template in another wikia is by using #invoke. Unless you believe that only experienced editors will add lua templates to their wikis. As far as error handling is concerned, you're perhaps you're assuming that only experienced scripters(lua coders) will design modules, which is unlikely.

If you're going to use   Module:If   as an example, I'm at a loss to understand why you'd use modules instead of parser functions for that use case? Why would I add an #invoke call to a page when #if does all I want in less space and is more recognisable to most wiki editors? You're reinventing the wheel to be more complicated than it needs to be.

I just used module:if as a random example and only created it as a proof of concept, although it could possibly be expanded to cover the uses of several #if  parser functions, instead of using different syntax for each. Anyway, a more applicable example is either the Module:Switch or Module:String which is far more efficient than any wikitext or parserfunction.

Beyond simply reinventing the wheel as you put it, the style guide is meant to be accessible to both experienced scripters and beginners. What you, or I, or even scribunto developers believe is "simple" is different from what a novice may perceive. Many people learn  to script by observing other people's code, so good guidelines may help with lua template adoption.