Thread:MasterSlenderTR/@comment-188432-20180730181231/@comment-188432-20180731195243

Hey guys :)

Glad to see you guys are having a lively debate on all this stuff in the hours following my initial changes! Thanks for trying to stay creative, but in-bounds!

I've reverted a few — but only a few! — of the changes you made overnight. The basic rule of thumb with local customisation is that you can change only that stuff in the middle of the page. So that essentially means: nothing above or including the line underneath the page title and nothing below or including the Fan Feed. Understand that's not precise, it's just to give you a general notion of what you can mess with (outside of the changes you can effect through the ThemeDesigner).

So that means you can't change the font of the Edit button or the menu underneath it, or the font of the header on the editing pane or anything about the local nav header, or other standard elements of the FANDOM interface.

A quick word about a coupla other things:
 * In general,  is sufficiently qualified.  There are some use cases for , but in general the class is okay. That said, the best thing for a lot of use cases is actually   because that's a class that exists only on the reading view of an article page. So if you limit things to that class, you'll know you're not affecting, say, the header of the editing page.
 * Common.css doesn't need to be imported into Wikia.css. This wiki was only started in 2016, so it's always had automatic importation. Forcing it to do it again slightly slows down page serving for no gain.
 * You might want to consider modernising all your CSS. It looks like maybe some of your CSS was cut and paste from older wikis where legacy selectors were in place. Some of the classes and IDs to which your code refers hasn't been active on FANDOM for considerable periods of time. In particular, some of your called right rail modules are ancient.  hasn't been used at any point during this wiki's entire history. So maybe take some time to actually see whether the various selectors in your code are still active on FANDOM — and ruthlessly cut away the waste. The more you can compress your code, the leaner your wiki will run!
 * Speaking of modernisation, you might well give some thought to blanking Common.css, in favour of Wikia.css. In the wake of the elimination of Monobook, Common.css is effectively irrelevant. If your Common.css is empty, that's just one less thing to have to load. I'd suggest — though this is only a suggestion, that you make Wikia.css a combo of Wikia.css and Core.css. That way, all the CSS affecting the general shape of the wiki will be in Wikia.css. Then, you could perhaps move the bulk of Common.css to something like "Pages.css", since that's what the code of Common now does here. It might make things clearer to everyone reading your CSS — and eliminate a whole style sheet!