Skin:Minerva Neue/fr

L'habillage Minerva est utilisé pour le trafic mobile dans les projets Wikimedia à travers le monde. Comparé à d'autres habillages skins par exemple 'Vector', il fournit une interface utilisateur beaucoup plus simple et il est beacoup plus aggressif concernant l'optimisation des performance de sorte qu'il répond très bien aux utilisateurs de mobiles.

Il est optimisé pour son utilisation avec MobileFrontend comme wgMFDefaultSkinClass et à l'heure actuelle, la dépendance est forte.

Installation

 * Téléchargez et installez l'extension MobileFrontend.


 * Note: Setting  will make Minerva your default skin even in Desktop view. Ignore this line and instead use   if you want only MobileFrontend to use the Minerva skin.

Make sure the call to wfLoadSkin is installed after the call to wfLoadExtension.

Configuration of menu's
Certain URLs in the main menu can be tweaked. These include:
 * Random (via editing MediaWiki:Random-url)
 * Portal URL (of Advanced editing mode via MediaWiki:Portal-url)

Certain menu items will be enabled automatically when the relevant extension is added.
 * Nearby (provided by Extension:MobileFrontend).

Desktop vs mobile modes
MobileFrontend provides additional capabilities that are not available in MediaWiki core. You can compare desktop vs mobile mode.

When operating in mobile mode the following features are available: The desktop mode of the site is experimental. If you see a bug, patches are appreciated.
 * Sections can be collapsed and expanded
 * The menu contains different options e.g Special:Preferences is available on desktop
 * MediaWiki:Mobile.css (for mobile mode) or MediaWiki:Common.css (for desktop mode) will be loaded.
 * Various pages are optimised for mobile e.g. Special:Watchlist (compare desktop vs mobile)

When operating in desktop mode there are various issues that we are working towards fixing. Your patches and help are welcomed.

Questions and answers
If you have a question not answered by the page - please feel free to use the talk page to raise them.

Why does it depend on MobileFrontend?
We're working to fix this and have a whole project dedicated to it. Your patches and help are welcomed.