Topic on Talk:Edit Review Improvements/New filters for edit review

Suggestion: A separate filter group for contentmodels

3
197.218.83.82 (talkcontribs)

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.
Trizek (WMF) (talkcontribs)

Flow is mostly handled by Topic: Namespace, which is not implemented yet (T62493). It will be possible to filter al Flow activity when it will be done.: new topics, edits on that namespace... Description of a Flow board would be included.

This said, how would you see those filters? There is a lot of ways to track those changes beyond namespaces: tagging changes for instance. Those are already handled by the filters.

197.218.89.141 (talkcontribs)

> This said, how would you see those filters?

Probably another drop-down for content-model.

You make a good point . Although, adding this will reduce the need for more development time for each new filter whenever some new tool comes around, e.g. Extension:CollaborationKit/Technical documentation#CollaborationHubContent can store stuff in the Project, and user namespace. Tags have the drawback that unless they are defined in mediawiki or extensions all wikis would need to implement it, and reinvent the wheel each time.

It also seems that Tabular Data and Map Data use different models within the same namespace each of which requires different knowledge to review the changes. Tabular data is relatively easier to understand than maps.

A user may want to monitor one but not the other.

Reply to "Suggestion: A separate filter group for contentmodels"