Board Thread:Watercooler/@comment-24473195-20150915112607/@comment-11733175-20150915125445

I'm all for adding user-facing documentation for modules, but I don't think this is the right approach and certainly not for the right reasons.
 * There is no Wikia support right now for a variety of reasons, but implementing a completely different method causes larger issues if Wikia ever do elect to upgrade.
 * Is there any evidence for confusion between docs and modules? It's a tried and tested system with templates and works fine there.
 * Both of the linked bugs stem from issues with ContentHandler, the latter more a lack of forward thinking in the importation process. Both are fixable, although neither seems to have an awful lot of progress.
 * Why are modules pages showing up in SpecialWanted* an issue?
 * Just because it's global, doesn't automatically make it an issue. As long as the documentation for how to use the module is observed, I don't see why it would cause any issues.

The correct titles for your examples are Module:Parser/doc, which documents Module:Parser, and Module:Parser/Data/doc, which documents Module:Parser/Data. In theory, the latter could be skipped as it might be better documented in the parent module's docs. It's how it's designed to be used in the extension. Again, I've never seen an issue in templates, so I'm confused why it suddenly becomes an issue in modules?

A wiki wasn't designed to store code, but unless you're proposing to move all code pages to git and build a mechanism to update them in production every time they're updated I don't see how it's going to work.