Digital Jedi
09-27-2011, 10:00 PM
Introducing Fugly. The butt-ugliest style you will ever meet.
So what's the point of Fugly, if it's so horrible? Developing skins for vBulletin can be frustrating. All those slightly different shades of grey and...grey. It's tough trying to remember what CSS controls what. So Fugly was designed to aid developers in figuring things out by enlarging some fonts and using horribly contrasting colors. In addition to that, I've replaced the gradients so their use across the forums become painfully obvious. All this will help you single out areas that you normally can't find in the CSS editor. It will also reduce any tendencies you might have to overlook vB default colors that creep into custom styles.
I've included two versions of the XML, one with categories already separated, and one with default vB templates. You can import both if you want. (Please refer to the special instructions below if you use Separated Categories.)
INSTALLATION
Download and Unzip the contents of the ZIP file.
Upload the fugly folder to your forum's root directory. (This is the directory where your vBulletin is physically installed.)
Go to Styles & Templates >> Download/Upload Styles >> Import Style XML File and import the style-fugly.xml and/or the style-fugly_separate_cats.xml file.
ADDITIONAL INSTRUCTIONS
If you import the Separate Categories XML, you'll need to make a few changes to one of your templates to make it work properly, and to be XHTML valid. Be sure to include these instructions if you decide to distribute styles based off of this one.
In forumhome_forumbit_level1_nopost look for:
<!-- DJs Category Separation -->
<!-- Change the X,Y,Z to the IDs of the uppermost CATEGORY on forumhome.php and each instance of forumdisplay.php -->
<if condition="!in_array($forumid, array(X,Y,Z))">
Change the code in red to the forum IDs of the uppermost category on forumhome.php and each instance of forumdisplay.php. The reason you do this is to prevent incomplete tables from being constructed at the top of each of those pages. As stated above, be sure you let people using styles built off of this one know what they need to do and explain why.
So what's the point of Fugly, if it's so horrible? Developing skins for vBulletin can be frustrating. All those slightly different shades of grey and...grey. It's tough trying to remember what CSS controls what. So Fugly was designed to aid developers in figuring things out by enlarging some fonts and using horribly contrasting colors. In addition to that, I've replaced the gradients so their use across the forums become painfully obvious. All this will help you single out areas that you normally can't find in the CSS editor. It will also reduce any tendencies you might have to overlook vB default colors that creep into custom styles.
I've included two versions of the XML, one with categories already separated, and one with default vB templates. You can import both if you want. (Please refer to the special instructions below if you use Separated Categories.)
INSTALLATION
Download and Unzip the contents of the ZIP file.
Upload the fugly folder to your forum's root directory. (This is the directory where your vBulletin is physically installed.)
Go to Styles & Templates >> Download/Upload Styles >> Import Style XML File and import the style-fugly.xml and/or the style-fugly_separate_cats.xml file.
ADDITIONAL INSTRUCTIONS
If you import the Separate Categories XML, you'll need to make a few changes to one of your templates to make it work properly, and to be XHTML valid. Be sure to include these instructions if you decide to distribute styles based off of this one.
In forumhome_forumbit_level1_nopost look for:
<!-- DJs Category Separation -->
<!-- Change the X,Y,Z to the IDs of the uppermost CATEGORY on forumhome.php and each instance of forumdisplay.php -->
<if condition="!in_array($forumid, array(X,Y,Z))">
Change the code in red to the forum IDs of the uppermost category on forumhome.php and each instance of forumdisplay.php. The reason you do this is to prevent incomplete tables from being constructed at the top of each of those pages. As stated above, be sure you let people using styles built off of this one know what they need to do and explain why.