Help:FandomDesktop conversion guide

Admins, you should definitely check out the new Theme Designer and the FandomDesktop preparation guide for advanced customization. When you feel that your wiki is ready for the new experience, there’s a button in your Admin Dashboard to let us know. This may impact the order in which your wiki moves to FandomDesktop as a default experience for all editors, admins, and readers, but we make no guarantee of earlier placement in rollout waves. Note: This will not be available on historically Gamepedia wikis immediately on release, but will follow within days.

= Opting in or out =

To opt-in for FandomDesktop, either click the link in the banner inviting you to do so or head to My Preferences and click the Appearance tab. On that page, you will have the option to select Oasis/Hydra or FandomDesktop. When FandomDesktop is selected, you will have additional preferences to control your experience.

That same tab is how you opt-out to switch back to the legacy design for testing purposes as your community prepares for full rollout early this summer.

= New custom CSS / JS files = MediaWiki:Fandomdesktop.css and MediaWiki:Fandomdesktop.js

= Features that will change for both GP and Fandom wikis =

Tabber
.tabber class for the tabber container will remain. All other class names are removed and replaced with Fandom Design System classes: wds-tabs__tab for tabs and wds-tabs__contentfor tabs content.

Base layout

 * Migrating from GP wiki
 * the whole page container (with navigation) #pageWrapper can be now accessed by .resizable-container class, but navigation is now on the top of the page
 * there is now the main page wrapper with .page class which contains the content container and the right rail (if right rail is present, this element also contains .has-right-rail class)
 * there is now the main content container with .page__main class which contains page header, content, and the page footer
 * article content #content or .mw-body can be now accessed by #content id or .page-content class
 * page header can be accessed by .page-header class
 * page footer can be accessed by .page-footer class
 * right rail can be accessed by #WikiaRailWrapper id or .WikiaRail class
 * Migrating from Fandom wiki
 * the whole page container (with navigation) .WikiaPage can be now accessed by .resizable-container class
 * main page wrapper (with right rail) .WikiaPageContentWrapper can be now accessed by .page class (if right rail is present, this element also contains .has-right-rail class). It contains the content container and the right rail
 * main content container #WikiaMainContentContainer or .WikiaMainContentContainer can be now accessed by .page__main class. It contains page header, content, and the page footer
 * article content #content or .WikiaArticle can be now accessed by #content id or .page-content class
 * page header (accessed by #PageHeader or .page-header ) can be now accessed by .page-header class
 * page footer can be accessed by .page-footer class
 * right rail (accessed by #WikiaRailWrapper or .WikiaRail ) can now be accessed .right-rail-wrapper class

Visual changes

 * border around infobox container is added by default

title’s (.pi-title) and headers' (.pi-header) default background is set to accent color (--theme-accent-color) and font color is calculated dynamically and set to --theme-accent-label-color. For some customizations this may cause the header’s (or title’s) label to be illegible.

Recommended solution:

Changed markup for tabs

 * HTML markup for panel’s tabs and image collection’s tabs has changed completely, which means that no current customizations for the tabs is applied or supported.

Old markup for image-colection (simplified):

New markup for image-collection (simplified):

Old markup for panels (simplified):

New markup for panels (simplified):

Community background image
The new theme designer will provide some extended possibilities for customizing the appearance of the community background image. However, if you’re willing to port your existing CSS/JS customizations of the background there’s a new class name:.

= Features that will change in comparison to Oasis =

Galleries
Galleries on FandomDesktop will be based on the MediaWiki native gallery solution.

See https://www.mediawiki.org/wiki/Help:Images#Gallery_syntax.

There are two major changes in gallery syntax:


 * To determine gallery style you'll need to use mode instead of type property. In order to ensure backward compatibility with all the galleries created on Oasis, type property will still be supported after the FandomDesktop rollout. However, it is encouraged to create new galleries using the new  property.
 * Support for certain gallery properties will be discontinued. See below for full list:

element attributes
Additional notes:


 * Fandom gallery images are "frameless" by default, whereas MW gallery images are displayed in a thick frame. In order to preserve the same looks of a gallery, it has to be either handled by custom styling or mode="nolines" has to be added to all galleries as part of the migration.

= Features that will change in comparison to Hydra/HydraDark =

New gallery mode - slider
Gamepedia communities will now have a new slider gallery mode available.

Usage:

Slider gallery accepts one additional attribute named orientation, which accepts values bottom (default) or right and determines the position of the slider navigation.

= Theming variables = In the FandomDesktop skin, users will have access to variables representing theme colors. These variables will be accessible in CSS.

Example hex value:

Example Red, Green, Blue color values: 0,0,0

Dynamic Colors
Dynamic colors are established on the basis of their background. They are calculated to reach the best contrast ratio possible.


 * dynamic-color-1 is fandom-black (#0E191A) for light backgrounds and white (#FFFFFF) for dark backgrounds.
 * dynamic-color-2 is dark grey (#3A3A3A) for light backgrounds and light grey (#E6E6E6) for dark backgrounds.

Theme-specific selectors
You can also specify each theme for the instances where you need different behaviour based purely on the theme choice.
 * is for elements that are themed for the light theme.
 * is for elements that are themed for the dark theme.

Further help and feedback
de:Hilfe:Leitfaden_zur_Vorbereitung_auf_FandomDesktop fr:Aide:Guide de préparation pour FandomDesktop it:Aiuto:Guida di preparazione a FandomDesktop ja:ヘルプ:FandomDesktop/準備ガイド ru:Справка:Руководство по подготовке к FandomDesktop zh:Help:FandomDesktop準備指南