Thanks for the clarification.
I think the argument of too many classes preventing the establishment of a
standard is putting the cart before the horse. I'd argue that if we had a list
of recommended standard classes there would not be quite as many around with
everybody inventing their own.
There is no comprehensive list of classes, because we simply have too
many of them. And they differ per skin, extension and subpart of the
wiki. And then there is the content where wiki's do whatever they
want...
This specifically, is why for widgets etc we are moving too OOUI, so
that the
On a tangent to T192752 ([1]), are there any general guidelines on which
classes are or should be used by core and extension devs on HTML elements for
styling?
On mw.org I found scattered remarks about mw-ui-progressive,
mw-ui-constructive, and the like and I found the page on OOUI ([2]),