Thread:Hackey5/@comment-4189499-20150409024114/@comment-4189499-20150409060837

Going through your points in order:

body { background-image:URL('http://vignette3.wikia.nocookie.net/geometry-dash/images/5/50/Wiki-background/revision/latest?cb=20150405143056'); background-repeat:repeat-x !important; background-position:top left; } If you need any further help, feel free to ask :)
 * Personally I'm a Chrome fan because I just like the easy layout with the incorporated Omnibox working as both a URL bar and search box making the top ribbon extremely uncluttered as well as easy access to settings and the browser console. But that's all just personal preference.
 * It's good to know you're working on it, because I'm again having to use Notepad to type out my reply.
 * The background image looks great, but the contrast of text to background simply isn't good enough. For example, on this page scrolled down here, the top line of text is #3A3A3A on #515DAC, which is a fail on the colour contrast checker.  Even for a person with good eyesight, it's annoying to have to read with such low contrast, and I don't want to turn up my brightness to read one website.  I like my brightness low.  The simplest way to fix that is to make the background of the content section a lighter colour or a higher opacity.  In fact, the colour you have is fine, and is easily readable when the screen is made small enough for the colour to be the only background, but you seriously need to fix the opacity so it's easier to read text when the background image is there, if for nothing other than having a consistent reading experience across the page.
 * It is true that the background image is removed when the width of the browser window is below a certain number. It was introduced with fluid width so that people with narrower screens (tablets mostly, and it also helps people who snap two windows beside each other when accessing two programs at once as I'm doing now) didn't have space wasted with huge bars of background on either side of their content.  It shouldn't matter where it is specified, and you should just go along with this default behaviour because it does work well.  The theme designer doesn't resize images and leaves them at their original resolution, therefore, if your image is, say 700px in height, it will be displayed in any browser on any computer set to 100% zoom as 700px high, unless you use CSS to specify otherwise, which I would advise against due to pixelation.  If the height of the image which is being tiled is less than the height of the screen, you will see the image being tiled vertically as well as horizontally.  If you just wanted the image to tile horizontally with a nice colour underneath for larger and longer screens, change the background in Theme Designer to be #6DB4CE and add to your CSS the following:
 * Many people think that the avatar looks better square as that's how it looks elsewhere and is usually what the user intended. Sadly, Wikia says we can't touch the global nav in any way shape or form other than via our personal CSS/JS.
 * I find that precious few people report when things go wrong, which is very frustrating when you need to know to fix things. I can see that on this page in Firefox, the menus are staying open as expected, however in Chrome they are only sometime working properly, and I haven't found any pattern to it yet.  Since this is not a phenomenon I am experiencing on other wikis, I have to conclude that it has to do with local styling.  IE is just throwing a hissy fit as usual and I can't even get it to load the page to test it.
 * Whitespace is a pain in the nether region. If you want to read a list of some of its various quirks, see Help:Whitespace.  But long story short, if you want to avoid annoying line breaks in templates, make sure your noinclude tags are on the same line as the last line of your code.  Also, do not use multiple noinclude sections after each other, because that's just silly and doesn't help anyone and in fact just makes things harder to read because you're filling your section breaks with useless code, not to mention white space from line breaks.  Just use normal line breaks inside the noinclude tags to divide sections and you won't have to worry about anything!  Or better yet, just use the documentation page provided and shove that inside noinclude tags.  It keeps the information about how the template works off the template page for editing, which makes life much easier when editing a big template with lots of documentation, but still displays the info normally on the page with as many sections as you'd like.  If you don't know how to get to the documentation to edit it, just go to the doc subpage of any template, eg Template:USERNAME/doc, and edit it.  The information from the documentation page is transcluded using  .  When it comes to other template tricks to pass along, I can't think of any at the moment, but do be aware that templates are very literal and will transclude anything that is not inside noinclude tags onto a page, including the whitespace separating the noinclude tags from the rest of the template code.