Board Thread:Watercooler/@comment-24473195-20150915112607/@comment-24473195-20150915185029

The /doc idea only makes sense in wikipedia because the software supports it.

Pros:
 * Uses an existing system
 * Easy to locate and transclude

Cons:


 * There is no automatic transclusion here, and there might never be.
 * The module namespace is meant for modules not docs. Wikimedia's doc implementation is a hack (like that phabricator ticket clearly shows).
 * The module namespace has an automatic editor designed for writing code, not writing docs.
 * The visual editor is disabled for that namespace, so tools for adding images, links, simple formatting and references are non-existent.
 * Even complete newbies (who know no wikitext) can help improve/correct general docs using visual editor.

The only alternative I see is maybe having a "Lua Module" main page, and subpages, e.g. [], [], etc.

Speaking of documentation, I think it might be a good idea to rename the List of Lua Modules to "List of Global modules", that way it becomes clear that these can be used anywhere.