Style Classic vBulletin 3 skin --- development log

Don't ask me why.... I don't understand it either..... But more than often simply doing a color change without !important does not guarantee a color change. So I've just gotten into the habit now to do it "as is" (with the important command). Rather than having to keep double checking my work :confused:
It's a bad habit, it becomes a nightmare when you intend to do changes. If you intend to make this only for your self, it doesn't matter, if you intend to release it, you should make it friendly for changes and also make use of style properties rather than extra.
 
It's a bad habit, it becomes a nightmare when you intend to do changes. If you intend to make this only for your self, it doesn't matter, if you intend to release it, you should make it friendly for changes and also make use of style properties rather than extra.
Sure....

Please correct XenForo's styling properties. :p

Seriously, you change 1 thing in there and like 5 or 10 things change with it.

I also find the properties hard to understand because it will clearly say X property does Y, but it end up having nothing to do with Y.

I spent forever trying to learn vBulletin's and I could never remember it all... I started spending forever trying to learn XenForo's... I no longer care to try. Extra.css works just fine.

Until there is a clear, easy, and free way to follow the properties ....
 
XF's style properties system was intended for basic use. The style property changes a lot of other properties so that simple usage (such as the slider) mean it retains the same style framework.

It's a pain in the ass if you want to modify things to be different, but then again so is any forum software!
 
The text coloring in the side bar.

I broke it down for people who may want to change things a little more

PHP:
.sidebar .section .primaryContent h3, .sidebar .section .secondaryContent h3, .profilePage .mast .section.infoBlock h3 {
color: black !important;
}

PHP:
.sidebar .section .secondaryContent .footnote, .sidebar .section .secondaryContent .minorHeading {
color: black !important;
}

PHP:
.sidebar .section .primaryContent h3 a, .sidebar .section .secondaryContent h3 a {
color: black !important;
}
 
XF's style properties system was intended for basic use. The style property changes a lot of other properties so that simple usage (such as the slider) mean it retains the same style framework.

It's a pain in the ass if you want to modify things to be different, but then again so is any forum software!
.... ie.... global settings

And not always properly labeled global setting either.... ie... X has nothing to do with Y and is on a completely different part of the site, let along page, and yet.....:rolleyes:

But let's just agree to disagree. :)

I use the properties normally last to clean up a few lose ends. Extra.css is where most of everything is resolved.
 
Coloring for the section footer (or in general relationship with that nice little menu that allows you to change the order of the thread display)

PHP:
.sectionFooter {
background-color: #767F9E !important;
}
 
Coloring for all the footer and the text down there

(I kept it bold. I didn't want to enlarge the text, but also wanted it easier to read)

PHP:
.footer a, .footer a:visited {
color: black !important;
font-weight: bold;
}

.footer .pageContent {
background-color: #D9DAE6 !important;
}

#copyright {
text-align: left !important;
color: black !important;
font-weight: bold;
}

#copyright a {
text-align: left !important;
color: black !important;
font-weight: bold;
}

#legal a {
color: black !important;
font-weight: bold;
}
 
The text coloring in the side bar.

I broke it down for people who may want to change things a little more


PHP:
.sidebar .section .secondaryContent .footnote, .sidebar .section .secondaryContent .minorHeading {
color: black !important;
}

Changed the coloring to thus

#576288
 
Site detail text coloring in the side bar

PHP:
.pairs dt, .pairsInline dt, .pairsRows dt, .pairsColumns dt, .pairsJustified dt {
color: #576288 !important
}

user title coloring in the sidebar
PHP:
.sidebar .avatarList .userTitle {
color: #576288 !important
}
 
It corrected the overlay on the header on the quick navigation

PHP:
.heading, .xenForm .formHeader {
background-color: #767F9E !important;
color: white !important;
}
 
Coloring for all the footer and the text down there

(I kept it bold. I didn't want to enlarge the text, but also wanted it easier to read)

PHP:
#copyright a {
text-align: left !important;
color: black !important;
font-weight: bold;
}
 
#legal a {
color: black !important;
font-weight: bold;
}
Changed from black to white. Better display (visually).
 
The text coloring in the side bar.

I broke it down for people who may want to change things a little more

PHP:
.sidebar .section .primaryContent h3, .sidebar .section .secondaryContent h3, .profilePage .mast .section.infoBlock h3 {
color: black !important;
}

PHP:
.sidebar .section .secondaryContent .footnote, .sidebar .section .secondaryContent .minorHeading {
color: black !important;
}

PHP:
.sidebar .section .primaryContent h3 a, .sidebar .section .secondaryContent h3 a {
color: black !important;
}
Revisited this and change a little coloring for the text and the sidebar header coloring.

PHP:
.sidebar .section .primaryContent h3, .sidebar .section .secondaryContent h3, .profilePage .mast .section.infoBlock h3 {
background-color: #757E9D !important;
color: white !important;
}

PHP:
.sidebar .section .primaryContent h3 a, .sidebar .section .secondaryContent h3 a {
color: white !important;
}

www.sociallyuncensored.net 2012-11-14.webp
 
section header for thread list headers or discussion list header, whichever you prefer to call them (I simply say threads)

PHP:
.discussionList .sectionHeaders {
color: white !important;
background-color: #767f9e !important;
border-top: 0px !important;
border-bottom: 0px !important;
}
 
.discussionList .sectionHeaders a {
color: white !important;
background-color: #767f9e !important;
}

Removed these 2 lines

border-top: 0px !important;
border-bottom: 0px !important;

Was originally going to do it border less, but as someone pointed out.... There are a few add-ons which depend on that spacing. So for compatibility they need to be there.
 
Top Bottom