“ Class naming conventions Since styles from multiple sources can be present on a single page, it is important to avoid name clashes between these style rules. For example, MediaWiki itself as well as the skin (Vector, etc.) will add some classes, the Extension:Wikisource and Extension:Proofread Page extensions may add others, and there are classes used by templates. To reduce the likelihood of collisions we have developed some conventions for how to name classes from different sources, based on giving the name a prefix indicating its origin. ”
Quotes from Page styles ()
“ A CSS "stylesheet" can be applied to a Index page, which will allow every Page: namespace page within it to share the same styling. This CSS is automatically included when pages are transcluded using thetag.You do not need to use CSS for a work if you don't want to. It is provided to make life easier, not harder.How to apply CSS The CSS is read from the /styles.css subpage of the Index page. If this page does not exist, no styles will be applied by default by the ProofreadPage extension. ”
“ The following bare CSS in the work's page content is bad form:Avast, ye, Long John Silver! This is to say: the classes defined in CSS (including work-specific CSS) should nearly always be invoked via a template, not directly. It is much easier to reason about and maintain templates than HTML/CSS, even if the template itself constructs HTML/CSS.CSS vs templates Some things are suitable to be handled by work-specific CSS, and other things are more suitable for a template. ”
