Issue
There is now a multitude of contentmodels (Flow, newsletter, CSS, JSON, etc). Chances are that in the future there will be even more. Someone may easily break the rendering of a page in the main namespace by changing its content model.
Concrete issue:
Mediawiki is currently too flexible so any namespace can potentially contain any contentmodel. Flow and other tools can even be hosted in the main namespace.
- Namespace filters do not suffice - Flow conversations can happen in any namespace, Extension:TemplateStyles allows CSS to be stored in the template namespace, and potentially elsewhere.
Possible solutions
- Create a new filter for contentmodel, e.g. sanitized-css, flow, etc
- Create separate filters only for important content models as they appear, flow, sanitized css, etc.