Skin:Vector

Vector is a 3>Special:MyLanguage/Manual:Skins|skin for MediaWiki which became default in 2010 (, ), succeeding 4>Special:MyLanguage/Skin:MonoBook|MonoBook. It had been created in 2009 as part of the work done by the .

Vector provides a number of usability improvements over its predecessor. It was the first skin to separate the flat level   into the categorized  .

At the beginning the basic functionality was included in the core skin, while some of Vector's special features were handled by a separate extension (). The extension has since been merged into the skin itself.

In recent years the skin underwent a number of changes, e.g. the switch to  and the addition of new features. The latter are controlable by feature switches so that users can still be served to legacy layout.

Setting the default skin to Vector
A default skin should be set for new users of a wiki by setting the variable <tvar|1></> in <tvar|2> </> to the lowercase skin name specified in the skin file:

wgVectorUseIconWatch
use watch/unwatch text link
 * Watch and unwatch as an icon rather than a link.
 * — use an icon watch/unwatch button

wgVectorResponsive

 * Experimental setting to make Vector slightly more responsive. Not actively being tested or used in production (yet) but relatively stable and false by default.
 * — Use responsiveness to improve usability in narrow viewports
 * — No responsiveness

Note in the 1.36 release, the meaning of this flag will change and apply to only the newest iteration of Vector, and will require the following configuration:

wgVectorPrintLogo
Logo used in print styles. Keys are <tvar|1>, ,  </> (in pixels). Note that this solution only works correctly if the image pointed to by <tvar|1> </> is an SVG that does not specify width and height attributes, or its width and height match the corresponding variables below. Alternatively, a PNG or other type of image can be used, but its dimensions also need to match the corresponding variable below. That in turn may result in blurry images, though.

Features

 * Basic features of the Vector skin


 * Reduced clutter, primarily by reducing the number of lines on screen


 * More prominent placement of the search portal


 * Visual separation of the content-action and namespace links, the former of which being divided into view tabs and action menu items


 * Automatic increase/decrease of margins throughout the user interface based on browser size


 * Use of a star icon for watch and unwatch actions


 * Added features of the <tvar|1></> extension (some of these features have later been merged into the Vector skin or into the MediaWiki Core or have been removed)


 * Simplified search portal, including suggestions


 * Collapsible navigation portals


 * Alert when leaving an edit page without saving


 * Automatic hiding of tabs that do not fit on screen


 * Experimental Vector extension features


 * Simplified footer content


 * Search box expands on focus


 * Section edit links are moved to be directly next to heading instead of on the right, and use an icon


 * CollapsibleNav support via <tvar|1></> extension

Collapsible navigation
The collapsible navigation portals are now provided by the <tvar|1></> extension which will have to be installed additionally.

Experimental smartphone and tablet web design
Vector will work on many mobile devices, but it is not fully optimized for mobile devices. As we approach the 1.36 release, Vector has been optimized to work with most tablets and an experimental mobile mode is available. In the upcoming 1.36 users will be able to enable a responsive mode using the following configuration:

Vector currently has a poor implementation of responsive web design, in which the <tvar|1> </> buttons might overlap the <tvar|2> </> buttons due to width shortage, with no fallback icons like on <tvar|3></>, <tvar|4></> and <tvar|5></> viewed on narrow displays.

In addition, the left side bar navigation links inside <tvar|1> </>, as well as the top links inside <tvar|2> </>, move to the bottom of the page on narrow displays, beneath the content area, requiring the user to scroll to the bottom before being able to access it.