- This feature is not currently available on new wikis which use the new Unified Community Platform (UCP).
See this page for more information on the new platform.
Local customization offers great challenge and satisfaction to many editors, so we at Fandom encourage you to try your hand at it. But there are two important things to keep in mind as you do:
- Use the Theme designer first, before attempting any CSS customization. It'll make your life a lot easier.
Each week we release notes on upcoming changes that might affect your community's customizations: Technical Update blog posts.
- On all wikis created after July 2014
- MediaWiki:Common.css is loaded. The contents will be applied before MediaWiki:Wikia.css. For most communities, this doesn't matter, but if you use
@importrules (like for importing custom fonts), it is best they are added to the top of MediaWiki:Common.css.
- On most wikis created before July 2014
- MediaWiki:Common.css is not loaded. If you want to use MediaWiki:Common.css, ask Fandom Staff to enable this. If you do so, make sure to clean up any old CSS in MediaWiki:Common.css beforehand, otherwise, it may cause unexpected effects.
Before you can edit your community's JS, you must ask Fandom to turn it on for you. After it's enabled, you'll probably want to edit the main JS page, MediaWiki:Common.js. Whatever is there will be loaded for all visitors to your community, whether they're logged in or not. So be aware of the following:
- For security reasons, edits to community JS must go through an approval process.
- JS errors can break basic functionality in your community. Please be careful to avoid introducing errors.
- Please do not include JS that you do not understand, nor import from sources that you do not fully trust. Additionally, do not import JS from personal JS pages, or from insecure pages.
- A number of common scripts are stored at the Fandom Developers Wiki and can be added to your wiki using ImportJS. Using ImportJS bypasses the need for the review process.
- As with the CSS pages, both Common.js and Wikia.js affect the whole wiki, but they may be consolidated in the future.
Changes you make to either CSS or JS are usually not immediately seen upon publication. This is because of a concept called "caching". If you're in the middle of a lengthy period of editing your CSS and JS, you may have to frequently bypass your cache to see your changes.
Also, Fandom's load order—the priority given to each of the various pages used to customize your wiki—is crucial for administrators to understand. A common reason that some customizations aren't seen is because a later-loading page effectively cancels a declaration made on an earlier-loading page.
- Help:CSS best practices – some best practice suggestions for CSS customization
- Help:Personal CSS and JS – creating customizations that only affect you
- Help:Advanced CSS and JS – more info for those delving further into the world of CSS and JS editing
- Help:CSS and JS customization – the hub page for all CSS and JS details
- Help:Including additional CSS and JS – Importing CSS and JS onto your wiki
Further help and feedback
- Browse and search other help pages at Help:Contents
- Check Fandom Community Central for sources of further help and support
- Check Contacting Fandom for how to report any errors or unclear steps in this article
- Learn how to use Fandom in Fandom University: short how-to videos for all levels of experience