docs/Skin.md
MediaWiki includes four core skins:
Several legacy skins were removed in the 1.22 release, as the burden of supporting them became too heavy to bear. Those were:
It is possible to customise the site CSS and JavaScript without editing any server-side source files. This is done by editing some pages on the wiki:
MediaWiki:Common.css for skin-independent CSSMediaWiki:Common.js for skin-independent JavaScriptMediaWiki:Vector.css, MediaWiki:Monobook.css, etc. for skin-dependent CSSMediaWiki:Vector.js, MediaWiki:Monobook.js, etc. for skin-dependent
JavaScriptThese can also be customised on a per-user basis, by editing
User:<name>/vector.css, User:<name>/vector.js, etc.
Several custom skins are available as of 2019. List of all skins is available at MediaWiki.org.
Installing a skin requires adding its files in a subdirectory under skins/ and
adding an appropriate wfLoadSkin line to LocalSettings.php, similarly to
how extensions are installed.
You can then make that skin the default by adding:
$wgDefaultSkin = '<name>';
Or disable it entirely by removing the wfLoadSkin line. (User settings will
not be lost if it's reenabled later.)
See https://www.mediawiki.org/wiki/Manual:Skinning for more information on writing new skins.
Until MediaWiki 1.25 it used to be possible to just put a <name>.php file in
MediaWiki's skins/ directory, which would be loaded and expected to contain
the Skin<name> class. This way has always been discouraged because of its
limitations (inability to add localisation messages, ResourceLoader modules,
etc.) and awkwardness in managing such skins. For information on migrating skins
using this old method, see
https://www.mediawiki.org/wiki/Manual:Skin_autodiscovery.