Topic on Talk:Reading/Web/Projects/Mobile Page Issues/Flow

Project independent approach required.

1
PerfektesChaos (talkcontribs)

Several comments already mention that the proposal is guided by English Wikipedia and cloned modules and template systems.

There are other wikis who have similar templates, more than a decade for establishing their own classification and issues and maintenance procedures, but other appearance and not a matching distinction.

The proposal needs to be an abstraction from enWP which might be a test case, but not the role model all other wikis have to follow now.

On the level of CSS selectors (classes) a neutral formulation is reasonable, which can be assigned by local template implementations and enWP might map into their system:

  • mw-page-issue-urgent
  • mw-page-issue-severe
  • mw-page-issue-important
  • mw-page-issue-error
  • mw-page-issue-warning
  • mw-page-issue-normal
  • mw-page-issue-neglectable

or whatever.

A simple three-value distinction called high-medium-low seems to be too simple and blocks later extension by additional levels which might become necessary. E.g. some registered authors who claim to maintain articles in preferences should see error and even warning messages, which are hidden from normal and anonymous users.

MediaWiki software is supposed to identify such <div> or other block element and show the appropriate level in current presentation.

Reply to "Project independent approach required."