9 CSS Ethics Every Designer Should Have
No need to get any more complicated structure than you need to. Writing a CSS Stylesheet That is Easy to Maintain is really easy, just by following these 9 rules.
How deeply you organize your CSS can greatly hinder any necessary tweaks that arise in the future. So, I proposed the question to my team to take a close look at some of the most interesting CSS coding structure and listed them below where you can probably use in every project you are developing.
1) Indent descendant and related rules:
This allows you to easily recognize page structure within your CSS and how sections related to each other. [Erratic Wisdom]
#main {
width: 530px;
padding: 10px;
float: left;
}
#main #nav{
background: #fff;
width:100%
}
#main #left-col {
background: #efefef;
margin: 8px 0;
}
2)Grouping and commenting your CSS rules
Setup certain sections in your CSS files that always exists: page structure, links, header, footer, lists, etc. Those sections are always CSS commented to name each section appropriately.
/* Header Styles Go Here **************/
...CSS Code Goes Here…
/* End Header Styles *************/
Header
Structure
Navigation
Forms
Links
Headers
Content
Lists
Common Classes
And a sample separator that is most easily noticeable
/* -----------------------------------*/
/* >>>>>>>>>>>>> Menu<<<<<<<<<<<<<<<<-*/
/* -----------------------------------*/
3) Keep style type on single line
Combine properties onto a single line by using shorthand properties means that your CSS will be easier to understand and edit.
Instead of this:
h2{ color: #dfdfdf;
font-size: 80%;
margin: 5px;
padding: 10px;
}
Do this:
h5{color: #dfdfdf; font-size: 80%; margin: 5px; padding: 10px;}
4)Break your CSS into sheets
Separate your CSS stylesheets for different sections, use one stylesheet for layout, another for typography and another for colors .Mixing layout / typography properties will make you find that you are needlessly repeating yourself.
#main { @import "/css/layout.css";
@import "/css/typography.css";
@import "/css/design.css";
@import "/css/design-home.css";
@import "/css/extra.css";
5)Reset your elements
Many designers clear the styling of their sheets with a global reset which has an impact on some elements like form buttons and fieldsets that are completely destroyed with the global reset.Instead, you should pick-and-choose the elements you want to reset.
So instead of doing this
*{ margin: 0; padding: 0; }
Do This
html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, font, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td {
margin: 0;
padding: 0;
border: 0;
outline: 0;
font-weight: inherit;
font-style: inherit;
font-size: 100%;
font-family: inherit;
vertical-align: baseline;
}
6)Place color scheme in one place for refrence.
Before you start your CSS file, comment your common colors and add it to the top of your style sheet.This will save you ton of time and will insure that your site has one color scheme.
/* Colors: Dark Brown #473B38 Light Blue #A8EFEE Pink FF4095 */
7)Use a meaning naming system.
Having a naming system for classes and id's saves you a lot of time when updating your document or debugging, you can use parent/child structure. The parent would be the container. So if our DIV is named “header”, and two divs nested called “menu” and “logo”. The naming structure in your css would be:
#header #header_menu #header_logo
8)Alphabetical Properties
It makes specific properties much easier to find.
body {
background:#fdfdfd;
color:#333; font-size:1em;
line-height:1.4;
margin:0;
padding:0; }
9)Keep a library of helpful CSS classes.
Useful for debugging, but should be avoided in the release version (separate markup and presentation). Since you can use multiple class names, make use of them debugging your markup.[Richard K. Miller]
.width100 { width: 100%; }
.width75 { width: 75%; }
.floatLeft { float: left; }
.alignLeft { text-align: left; }
.alignRight { text-align: right; }
Keep it Simple
No need to get any more complicated structure than you need to. Simplicity will save you time and efforts.
It would be great if you share with us your organizing tips to make this post a refrence to many of us. Don't forget to mention your site and name as it will be mentioned below your tip.
For me the best rule is number 6. Due to my day job (SEO) I am checking lots of time checking on websites and so far I havent seen a CSS file using a comment with all the color’s values. Is a simple idea which can save a lot of time…
Thanks
Nikos
Nice article, thanks!
I’d never thought about doing #1 – seems like a good idea.
I switched to #3 a while ago and wouldn’t want to go back to putting every element on a separate line.
I used #4 for a work project and I have to say, I’m not a big fan. Mainly because it increases the number of server request and considering styles can bleed across functional uses, it can be difficult to organize correctly.
#8 is a good idea. I tend to group mine first by HTML elements (div, p, table, etc.) then according to the page layout.
Great article! Thank you
Great tips!
Thankyou very much!
I agree with most of these, but this one about breaking stylesheets into few files I can’t agree. Just, when you’re doing a bigger website with few thousand visitors, it’s pretty much important not to make too many HTTP requests..
These are great. Bookmarked for later use!