This skin is based on a fork of and complete rework of the layout of the Foreground skin. Added classes available in Foundation 5, 100% width like Vector, but is totally mobile responsive.
A [MediaWiki](http://www.mediawiki.org) skin that focuses on mobile first but will pivot to all viewports with elegance. Supports responsive layouts and has classes predefined for [Semantic MediaWiki](http://semantic-mediawiki.org/wiki/Semantic_MediaWiki). Built on the [Zurb Foundation 5](http://foundation.zurb.com) CSS framework.
First, copy the Pivot source files into your MediaWiki skins directory (see [skinning](https://www.mediawiki.org/wiki/Manual:Skinning) for general information on MediaWiki skins). You can either download the files and extract them from:
Use following features in `LocalSettings.php` to change the behavior.
-`showActionsForAnon => true` displays page actions for non-logged-in visitors.
-`NavWrapperType => 'divonly'`: only a div with id `navwrapper` will be created. `'0'` - no div will be created (old behavior), other values will be used as class.
-`showHelpUnderTools => true` a Link to "Help" will be created under "Tools".
-`showRecentChangesUnderTools => true` a Link to "recent changes" will be created under "Tools".
-`IeEdgeCode => 1` will produce a meta tag with "X-UA-Compatible" content="IE=edge", `2` will sent a header, `0` nothing will be done
These are the default values:
$wgPivotFeatures = array(
'showActionsForAnon' => true,
'NavWrapperType' => 'divonly',
'showHelpUnderTools' => true,
'showRecentChangesUnderTools' => true,
'IeEdgeCode' => 1
);
### Usage of NavWrapperType
With a setting like:
'NavWrapperType' => 'divonly'
and the created div called `navwrapper` anonymous visitors can change the setting of navbar (fixed or sticky) by
User-Script (Firefox-extensions like greasemonkey or scriptish), users can take a gadget or their JavaScript, CSS ... :
$('#navwrapper').addClass('sticky');
Or you set class in LocalSettings.php with:
'NavWrapperType' => 'contain-to-grid fixed'
and visitors will be able to remove this class by their own JavaScript or gadget ...
As you build a wiki out with Pivot you will likely use the responsive grid from Foundation. This is key to making a responsive wiki, and is one of the largest _migration_ requirements when you want to move a wiki that previously used Vector (and likely a lot of tables for layout) to Pivot. Once you do this, the ability of a user to select whatever skin will be removed. If you take full advantage of Pivot in your templates the lack of the Foundation grid will make viewing the wiki using [Vector](http://wikiapiary.com/wiki/Skin:Vector) or [MonoBook](http://wikiapiary.com/wiki/Skin:MonoBook) very difficult.
Because of this, it is suggested that you set the `$wgSkipSkins` variable to make sure that everyone sees the site as you intended it. This removes other skins from being user selectable options.