One thought is that page moves should be restricted to movement to a page name that would by default have the same content model. So, it'd be OK to rename foo.js to bar.js or foo.css to bar.css but not foo.js to bar.css(?)

In T403260#11222753, @Bugreporter2 wrote:

One thought is that page moves should be restricted to movement to a page name that would by default have the same content model. So, it'd be OK to rename foo.js to bar.js or foo.css to bar.css but not foo.js to bar.css(?)

This can only be done after T85847, since it would make it impossible to have a TemplateStyles page in userspace. (Right now the process is to create it in template space where the default is sanitized-css, and then move it to userspace.) Not sure if it really needs to be disallowed; a warning could be enough.

Another idea would be to restrict each namespace to a single content model. This would require some reshuffling of existing pages, and a handful of new namespaces like:

• Module_documetation
• Template_documentation
• Sitewide_JS
• Sitewide_CSS
• User_JS
• User_CSS

But I think it would make things somewhat tidier, and also futureproof wikis. The present system has grown organically but haphazardly over the years.

But especially if T85847: Grant editcontentmodel right to all logged in users is going to be nixed.