Grow your CSS skills. Land your dream job.

New Poll: How do you format your CSS?

Published by Chris Coyier

The poll is in the sidebar, so jump down there to vote. You can see examples of the different ways to format CSS here. I think that covers most of the popular ways to format CSS, but if you have your own unique way, feel free to post some code or a link to an example CSS file in the comments!

I think it's an interesting topic because us all the implications it may have on a site and the working life of the front end coder. We spend so much time in CSS that how we choose to format it affects how efficiently we can write it, how easily re-acquainted we are with old CSS, and even potentially page loading times assuming you don't compress your CSS.

Comments

  1. Permalink to comment#

    for more than 3 arguments I use this:
    #id{
    [tab]color: #333;
    height: 20px
    }

    for 3 or less I use:
    .class{ color: #220000; text-decoration: underline; }

    • Amen! All the other methods are completely a waste of visual space, especially on large amounts of css.

      I find myself getting annoyed these days if it’s formatted any other way. Sad I know, but true.

    • Permalink to comment#

      like this:

      document.write(“hello world);

    • Permalink to comment#

      oops it acually used the html

      document.write(“hello world);

    • Gappa
      Permalink to comment#

      Yep, I’m doing something similiar – works nice. Only difference with my approach is that I try to indent the opening { of the declaration to the same place.
      Also – for more arguments I tend to indent them a bit.

      Something like:

      div.menu {..}
      div.menu ul {..}
      div.menu li {..}
      div.menu a {
      ...
      ...
      ...
      ...
      }

      It works, at least for me – I can easily orient in my CSS.

      The CSS gets minified in the end so I can get crazy about how it looks in the editor :)

    • Gappa
      Permalink to comment#

      Ups, it got messed up, hope you get the point anyway.

  2. lawrencek
    Permalink to comment#

    I almost always format my CSS using multi-line formatting with indenting, as well as having it sectioned by pre-defined HTML tags, ID’s, or classes, and then having the styles within that listed alphabetically (As best I can anyways!).

    For example:

    @charset "UTF-8";
    /* CSS Document */
    
    
    /* The following code styles pre-defined HTML tags */
    h1 {
    	font-size: 27px;
    }
    h2 {
    	font-size: 22px;
    }
    
    
    /* The following code styles custom ID's */
    #container {
    	margin: auto;
    	min-width: 960px;
    	width: 960px;
    }
    
    
    /* The following code styles custom classes */
    .attraction {
    	font-size: 25px;
    	margin: 0% 8% 4% 8%;
    
    }
    

    Then lastly, I usually style any large aspects of a site (Image slider, light window, etc.) as separate elements alphabetically at the end!

  3. st
    Permalink to comment#

    Always like that, it is compact and better reading for me.

    .style { font-size:100%; font-weight:900; … }

    • Permalink to comment#

      Amen brother!

    • JB
      Permalink to comment#

      Same way for me, it’s more compact in the file (don’t like to scroll too much) and Firebug organizes it well, so I can manipulate it easily.

    • Amen!

    • Same. I cannot stand scrolling up and down huge files.

    • mattvot
      Permalink to comment#

      Yeh! Single line is so much easier to read than most mulitline css coders think.

    • Permalink to comment#

      I agree completely. A couple years back I was a multiline CSS’er but now I mostly do single line. If there are a lot of selectors, I’ll separate them on multiple lines though.

    • Permalink to comment#

      Same for me, without the space before the { but it’s so much easier to read, and I put properties in alphabetical order (to avoid duplicates).

    • ySchaub
      Permalink to comment#

      I can’t understand why single lines should be more readable…especially if you have like >10 properties. That’s so confusing….multiline keeps it easy to read.
      I agree with lukas and Kieran. Theres no need to write multiline with 3 or less properties. But as soon as it gets more I have to search too long for everything.

      But maybe one day I’ll change…don’t know yet :D

      I apologize for my english, hope you could understand.

  4. Permalink to comment#

    /* Name for this section */

    selector
    {properties}

    /* Next section…

    This is simple since the most time you spend looking for a certain property in the document is looking for the right selector. By minimizing the space between selectors it goes much faster maintaining CSS this way, at least for me.

    I also try to keep properties alphabetically for the same cause.

  5. I use multi line with indents. When the site goes live I compress it so it’s single line with no unnecessary spaces. I alphabetize too.

  6. Permalink to comment#

    p {
    font-size: 1.25em;
    }

    I indent for everything.

  7. Permalink to comment#
    .class_name{property:value;other-property:other(val.ue) no-repeat)

    No whitespaces, long lines. I work on a large, widescreen monitor and like to have it all filled up with code.

    Oh, how do I cope with the mess? CMD+F

  8. Permalink to comment#

    I usually use multiline for everything except single rules.

    
    /*	Content blocks
    	Control main text flow
    	------------------------------ */
    
    #primaryContent
    {
    	float:left;
    	padding:5px;
    	background:#ebebeb;
    	width:590px;
    }
    
    #primaryContent + * { clear:both; }
    
    #primaryContent h1
    {
    	color:red;
    	font-size:xx-large;
    }
    

    I think what is more important is how the CSS document is structuredand if comments are used. As in my example above I will do a large comment block before a particular section, indicating what the elements there are for.

  9. Permalink to comment#

    I use both multi line with indenting and single line formatting. Depends on the situation. Like if a rule contains less than three selectors. I also use a lot of comments and if there’s something I’m totally anal about is avoiding to use padding. Urgh.
    Even if I don’t need a particular styling for an ID or class I still list them in my stylesheet.
    If I use float I usually also list the total width of the floats combined so that the math is easy to calculate.
    Top of it all, I try to use shorthand css as much as possible.

    * { padding: 0; margin: 0; }
    /******** LAYOUT *********/
    body { 
    	background: #eee;
    	}
    	#PageWrap { /* 1. level */
    		width: 750px;
    		margin: 50px auto;
    		background: #fff;
    		}
    		#PageHeader { height: 150px; }
    		#ContentWrap { margin: 30px; } 	/* 750 - (2x30) =  690 */
    		#col1, #col2, #col3 { 			/* 690 / 3 = 230 */
    			width: 230px;
    			float: left;
    			display: inline;
    			} 
    
    /******* TYPOGRAPHY ********/
    body { font: Arial,Helvetica,sans-serif; }
    #ContentWrap { font-size: 11px; }
    • Steveoismynameo
      Permalink to comment#

      I agree Danny. This is very similar to the way I format mine. By indenting children it makes the hierarchy much more clear and organized.

  10. I use compass which does all the formatting for me :)

  11. Single line formatting all the way. Multi-line CSS formatting makes your stylesheets way to long and you end up having to search forever to find stuff.

  12. Permalink to comment#

    Here’s some CSS from my actual site.

    /* Style */
    	
    			
    header, nav, footer, section				{ display: block; }	
    *											{ font-family: "Lucida Grande", Arial, sans-serif; }
    body										{ background-color: #333; }
    header.main									{ background-color: #757575; height: 450px; }
    .center										{ width: 700px; margin: 0 auto; }
    h1											{ font-size: 125px; color: #333; padding: 45px 0 0; font-weight: normal; }
    h2											{ font-size: 48px; color: #444; padding: 15px 0 0; font-weight: normal; } 
    h2 span										{ color: #639; }
    h2 strong									{ font-weight: normal; color: #A30; }
    h3											{ font-size: 20px; color: #555; line-height: 1.4em; padding: 15px 0 0; 
    											  font-weight: normal; }
    a											{ color: #666; text-decoration: none; }
    section p a									{ text-decoration: underline; }
    a:hover										{ color: #999; text-decoration: none; }
    .mainnav									{ background-color: #252525; padding: 5px 0; text-align: center; }
    .mainnav ul li								{ display: inline; color: #757575; font-size: 18px; }
    .mainnav ul li:after						{ content: " - "; }
    .mainnav ul li:last-child:after				{ content: ""; }
    .mainnav ul li:first-child:after			{ content: ""; }
    .mainnav ul li a							{ color: #777; text-decoration: none; }
    .mainnav ul li a:hover						{ color: #777; }
    h3 a										{ color: #444; text-decoration: none; }
    h3 a:hover									{ color: #A33; }

    I’m sure there’s an awful lot wrong with it, but it works, so its all cool as far as im concerned.

  13. Permalink to comment#

    I used to use multi-line, but for long css files the scrolling gets to be too much. Especially if you are editing the css in a tiny window built into a CMS.

    Single-line with indent/tabbing all the way!

    • Permalink to comment#

      yeah, i started on multiline too. When I changed to coda, I swapped, and then moving back to dreamweaver the habbit kinda stuck.

  14. I use single-line format.

  15. I wrote this message in Notepad first so I have no idea if it’s going to look ok after posting it since there’s no way to preview.

    After seeing Dan Rubin in a couple of Web Design World conferences, I tried to give it a shot at his method of writing CSS in a single line format, I’ve always wrote CSS the regular way, that is, multi-line format.

    I liked it, but most importantly, made it A LOT easier to manage the CSS rules.

    Something I tell everyone, and I told Dan as well, is that in today’s days monitors are wider and larger, so writing in a single line makes use of the width of your monitor, this means you can see more rules in one screen.

    I went one small step ahead of Dan’s single line writing, and implemented my own method when writing the properties.

    Here’s an example (this is from a real project):

    /****HEADER****/
    #header { padding-top:20px; }
    #header img { float:left; }
    #header div.address-header ul { float:right; width:960px; height:100px; text-align:right; margin-top:25px; color:#003247; font:italic 1.2em/1.4em Georgia, "Times New Roman", Times, serif; }
    #header div.address-header ul li + li { padding-left:27px; font-weight:bold; color:#000 ; }
    #header div.address-header ul li.email { background:url(../images/bg-sprites.png) 0 -605px no-repeat; }

    I leave the long declarations for last, like ‘background:’ and ‘font:’.
    I leave a space after the first ‘{‘ and before the last ‘}’.
    ‘float:’ comes first every single time if needed in the declaration.
    ‘widht:’ first, ‘height:’ comes second every time. That’s because coming from the printing world, when you refer to the dimensions of a document, the first dimension you say is the width.
    I always start with the simplest selector, and as I need more rules related to same selector, I keep them grouped. When a new set of rules for a selector is needed, I start a new group.
    Every group has a comment that describes it.

    Give it a try writing in single line, I didn’t think I was going to change my habit after so many years writing CSS the regular way.

    Later all.

    • The didn’t work, here it is again:

      1. I leave the long declarations for last, like ‘background:’ and ‘font:’.

      2. I leave a space after the first ‘{‘ and before the last ‘}’.

      3. ‘float:’ comes first every single time if needed in the declaration.

      4. ‘widht:’ first, ‘height:’ comes second every time. That’s because coming from the printing world, when you refer to the dimensions of a document, the first dimension you say is the width.

      5. I always start with the simplest selector, and as I need more rules related to same selector, I keep them grouped. When a new set of rules for a selector is needed, I start a new group.

      6.Every group has a comment that describes it.

    • That structure is how I roll.

    • Permalink to comment#

      Me too!

  16. Permalink to comment#

    E {
    ....property:value;
    ....}
    ....E>E {
    ........property:value;
    ........}

  17. Krinkle
    Permalink to comment#

    I used to do “Multi-line Format”, but for almost 2 years now, since I saw Chris doing it that way I’m using “Mosltly single line”, I feel like it really improved my CSS skils somehow.

    This single line format gives me a relatively short css-file which allows me to quickly scrub through and find what I’m looking for.

    One down side of single line is that tabs may be differently interpreted accros browsers/editors. But so what :) – as long as it’s good in my editor.

  18. Permalink to comment#

    #div
    {
    …..property:value;
    }

    curly braces that aren’t on there own line make me feel ill. Not sure why.

  19. Ahmed
    Permalink to comment#

    I use multi-line format, but I compress it after I finish the project and keep 2 copies while I load only the compressed one. I also use mod_deflate, so I’m good *I think*

    • +1 For this, it is WAY faster to find declarations with multi-line format. Then, when you compress it for production, it takes care of everything else.

    • Scott
      Permalink to comment#

      We do this too; basically use a multi-line format without tabbing / indenting, and utilize compression at build time. We also built a utility to alternatively use the uncompressed original files directly in the browser for easier debugging.

  20. Single line works best for me.

    When I’m working with CodeIgniter I’m using an asset library that combines all my CSS files into one file, and it also minifies the code with cssmin.

  21. silvers
    Permalink to comment#

    great idea for a poll. since i started web design i wondered how i should be formatting css. it’s changed a few times so i would like a well reasoned “best practice”. this poll is gonna be interesting and will probably shape how i do css in the future

  22. Lee Smith
    Permalink to comment#

    Single line rocks. CSS is not a programming language…more of a properties file. You waste so much time doing all the formatting.

  23. A bit of a snippet here from the recent redesign of my Blog.

    #nav {
    	position: absolute;
    	top: 25px;
    	left: 430px;
    }
    
    		#nav ul {
    			width: 100%;
    			list-style: none;
    			float: left;
    		}
    		
    		#nav ul li {
    			float: left;
    			display: inline;
    			width: 135px;
    			padding-right: 20px;
    		}
    		
    		#nav ul li a {
    			color: #fff;
    			font-size: 100%;
    			text-decoration: none;
    		}
    		
    		#nav ul li a span {
    			font-size: 80%;
    			color: #ccc;
    			text-transform: lowercase;
    		}
    		
    		#nav ul li a:hover {
    		}
    		
    		#nav ul li a:hover span {
    		}
    		
    
    
    #mainBody {
    	clear: both;
            }
    
    		#post {
    			width: 690px;
    			float: left;
    			border: 1px solid red;
    		}
    		
    
    		#content {
    			padding: 0 0 0 30px;
    			width: 510px;
    			border: 1px solid red;
    		}
    		
    				h2 {
    					margin: 30px 0 10px 0;
    					border-bottom: 2px solid #333;
    					color: #B52A0A;
    					font-family: Georgia, "Times New Roman", Times, serif;
    					font-weight: 100;
    					font-size: 175%;
    				}
    				
    				h2 a {
    					color: #B52A0A;
    					text-decoration: none;
    				}
    				
    				p {
    					font-size: 90%;
    					line-height: 150%;
    					padding: 20px 0 0 10px;
    				}
    				
    				img {
    					margin: 0 auto;
    					display: block;
    				}
    				
    		
    		#meta {
    			float: right;
    			width: 135px;
    			border: 1px solid red;
    		}
    		
    				#meta ul {
    					list-style: none;
    				}
    					
    						
    		#sidebar {
    			width: 150px;
    			float: right;
    		}
    
    • Sorry about how long that is, was the only way to show how I really do it, except none of the formatting has some of. Thought I would try (Although it failed) to post it because most people say I have quite a unique way of doing it!

  24. Permalink to comment#

    SASS (or LESS).

    That was easy!

    I struggled a bit at first, and I have to say that I lose the use of my favorite CSS editor (CSSEdit). But the gains by using SASS have been tremendous.

    Now, I would find it painful and tedious to return to the old days of raw CSS.

  25. EVula
    Permalink to comment#

    Multi-line formatting, though I’ll use single-line formatting for very specific rules (such as sprites).

  26. for inline elements:

    elem{ color:blue; text-decoration:underline;}

    for block elemens:

    .class{
    width:300px;
    height:344px;
    background:red;
    }

  27. Single Line For Life:

    #singleline { color:blue; text-decoration:underline;}
    
    /*------------------------------ */
    /*      Comment Banners to Separate!  */
    /*------------------------------ */
  28. For people who use something other than TextMate, I understand why you might think one way is faster than another. But for TextMate users, CMD+Shift+T lets you just to a selector by typing part of its name.

    Soo.. in my opinion, multi-line is the easiest to read since you are not trying to find declarations based on your eye picking them up as you scroll.

  29. Multiline formatting with indents. Indents are mostly a habit from programming but they also feel cleaner.

    Also to note, all styles within a selector are alphabetical.

  30. Single line with indenting, and with comments to separate biggest areas of html page.

    Furthermore, I always write css properties in a logical order for my mind… :-)

    For example, I write first the properties like margin, position, float, padding and at end the font properties.

    Beautiful contest! ;-)

  31. If I’m not using SASS or Less: single-line, with indentation since a couple weeks ago. The indents let me see see better the element nesting and scan better.

    As for sorting: basic elements, then classes, then basic layout and finally specific id’s.

  32. My example would be too long to paste here so I’ll just post a link to a recent project that I lead the initial theming on.

    http://gist.github.com/226212

    Website that’s using it: http://kysdc.com/

  33. Single lines with comments sectioning certain parts always, single lines allows you to scroll through long CSS stylesheets quickly and with the comments can find certain sections nice and easy. Also with this method i can usually have one style sheet and pretty much use it again for another site, i.e things like the footer styling and links usually stay the same maybe with a different color choice! At the end of the day its each to their own, and once you have learnt one way its hard to adapt to another.

  34. Multi-line with indenting.

    So my styles would appear as follows:

    #container {
         
    }
    
        #header {
    
        }
    
        #content {
    
        }
    
            #primary-content {
    
            }
    
            #secondary-content {
    
            }
    
        #footer {
    
        }

    This way you can show a hierarchy. Also, I organize in a structure similar to:

    /* General Tag Styles */
    
    body {
    
    }
    
    h1 {
    
    }
    
    p {
    
    }
    
    /* Custom Class Styles */
    
    .sup {
    
    }
    
    .clearfix {
    
    }
    
    /* Layout Styles */
    
    #container {
    
    }

    I know a lot of people like to do the organizing of styles alphabetically, but I prefer to do them in a manner of dependence… for example

    #header h1 a {
        display: block;
        height: 50px;
        width: 50px;
    }

    or

    #header h1 {
        position: absolute;
        top: 100px;
        left: 300px;
    }

    With the first one, height and width are dimensions that depend on display: block. And the second one, top and left depend on position: absolute. This makes more sense to me than doing it alphabetically.

    I also do not leave off the last semi-colon. Some people do this to save a file size, but I figure if I have to go in and add more styles, I’m going to have to add in that last semi-colon before I can start, so I just leave it on in the first place.

  35. Permalink to comment#

    I prefer multi-line because it looks more professional and makes it much easier to copy and paste single properties and refactor your CSS quickly.

    However, if there is a sequence of rules with very similar attributes (usually seems to happen with background-position if you use sprites) it looks much neater to do single lines.

  36. Multi-Line Format. Definitely.

  37. Permalink to comment#

    #MOTHER
    .CHILD

    //from SASS + COMPASS

  38. I personally don’t like the indenting.

    Multiline with good comments always makes me smile :-)

  39. recently i’ve started indenting, with a kind of single/multiline hybrid..

    I was always a straight forward single liner, but I always found myself wanting to infuse more structure into it. When a css file gets big i struggle to find what im looking for.

    I actually made a thread on this a while back, 68 views 0 replies, I guess you guys didn’t like my proposed style :P

    http://css-tricks.com/forums/viewtopic.php?f=4&t=4756

  40. I’m a multi-line with indenting guy, but I’m seriously considering moving to single-line with indenting as I’d love to save that amount of scrolling space.

  41. I write it on two lines…

    #selector
    { declarations in alphabetical order }

    …it does take getting used to writing rules in alphabetical order but it’s much easier to deal with months down the line when you come back to the project to make changes.

    My declarations match the core structure of my HTML file (the part of the page that never changes – such as my header > main content > footer).

    Then any styles that fall outside of that structure (such as the content for the home page and sub pages) go underneath the core declarations.

    Works for me, but I can appreciate that this is a very personal topic for CSS ninjas and what is good for one of us isn’t necessarily the best way for all of us.

  42. Permalink to comment#

    Whats funny is I learned CSS purely from you Chris, so I started with multi-line because I saw it that way in one of your screen casts, and then changed over to ‘mostly single line format’ as you did in your screencasts !

    Thanks for being a wicked teacher !

  43. Permalink to comment#
    .body-container {
           ......
           ..........
    }
           .container-top {
                   ...........
           }
                    .container-top a {
                             ..............
                    }
           .container-middle {
                   ......
           }
  44. Jillian
    Permalink to comment#

    I’m Single-line Format with Tabbing – I’m surprised that its currently only at 4% in the poll because I believe it is the Chris Coyier preferred method. My old sites are in multi-line format, and when I go back to update them I’m amazed/annoyed by how spaced out it all is!

  45. Permalink to comment#

    I use Multi-line Format with Indenting but some arguments at the same line – i.e.:
    div#something {
    [TAB]width:Xpx; height:Ypx;
    [TAB]margin:0; padding:0;
    [TAB]font:style weight size/height family;
    [TAB]color:#xxxxxx; background-color:#yyyyyy;
    [TAB]}

  46. Permalink to comment#


    #menu {
    display:block;
    float:left;
    }
    .active {
    color: #f1f2fa;
    font-weight: bold;
    }

    In this situation, my ‘active’ class is within the menu div tags.

  47. senshikaze
    Permalink to comment#

    clean code is next to godliness my mother always said

    so:
    #id
    {
    indent: stuff;
    }

    for me

  48. You know how I do it – I wrote an entire series on this topic over a year ago.

  49. I have two different styles for different use cases.

    My standard coding style:

    #blargh { color:black; background:white; }
    ..#blargh a { color:#9c0; text-decoration:none; }
    ....#blargh a:hover { color:#900; }

    Some projects I’ll have a separate file for hacks or browser specific stuff:

    #blargh { border-radius: 1em;
    ..-moz-border-radius: 1em;
    ..-webkit-border-radius: 1em; }

  50. Permalink to comment#

    multi-line, no intending, no spaces between property and value AND in alphabetical order ;)


    body {
    background:#222;
    color:#444;
    font-size:14px;
    font-family:Georgia,"Times New Roman",sans;
    text-align:center;
    }

  51. Permalink to comment#

    Multi-line Format with Indenting ftw!

  52. Jason
    Permalink to comment#
    #parent {attr: value;}
      (#parent) ./#child{attr: value; attr2: value;}
    
    #other_elm {a: v}
      (#other_elm) ./#child {a: v;}
  53. Permalink to comment#

    I like to use the One True Brace Style, with properties grouped together by what they do.

  54. Permalink to comment#

    I use multi-line with indention if the selector has more than 2 properties and single line if there is only 1.
    example

    ul {float: right;}
    
    ul li a {
    	float: left;
    	margin: 0 20px 0 0;
    	text-decoration: none;
    	
    }
  55. Permalink to comment#

    I use a combo, multi-line but grouping related properties. I find that gives me a balance between not having to scroll so much, the classes etc being easy to scan, but each property being easy to pick out quickly. I also use comments to help me find my way around the style sheet.

    Example

    .class {
         height: 100px; width: 200px; padding: 10px 0;
         background: black; color: white;}
  56. body {
    color:#333;
    margin:0 auto;
    font-family:Verdana, Arial, Helvetica, sans-serif
    font-size:12px;
    }

  57. Anthalus
    Permalink to comment#

    I tend to make it readable for me, and once I have everything where I would like it, I process the css through a compressor and use that one for the website. As long as I have the original, I have a more human-readable version.

  58. Permalink to comment#

    I style my css like:

    #selectorID
    ..........{
    .......... background:url(' valid url ');
    .......... height:100px;
    .......... width:100px;
    ..........}
    
    ...........#selectorID li
    .....................{
    ..................... color:#ffffff;
    ..................... font-size:14px
    .....................}
    • senshikaze
      Permalink to comment#

      you sir are a model css coder. I bow to your patience.

  59. I don’t compress besides gzip, so it’s important that I use single line considering how much CSS I use.

    Here’s my main CSS file, and yes I can read it all fine:

    http://cdn.myunv.com/css/uecore.css

    Instead of the “alphabetically ordered properties” I have my own order, like block properties and positioning first (margins, width) then colors, then stuff like font, text shadows, borders etc.

  60. Josh
    Permalink to comment#

    I generally block code into sections that are similar

    /* Page Layout */

    body {

    }

    #pagewrap {

    }

    /* Menu */

    #ul.nav {

    }

    etc.

    I do use the following method instead of on one line – I just hate how it looks when any editor wraps the text, and I hate scrolling to find it. So this method is much cleaner imo:

    #pagewrap {
    background;
    color:#ccc;
    padding: 5px 0;
    border:1px solid #000;
    }

  61. single line with properties in alphabetical order.

    also I try to use same ordering structure with my html order.

    – reset
    – page skeleton in the order (wrapper, header, navigation, content, sidebar, footer)
    than block specific declaration according to same order in skeleton
    – header elements declerations
    – navigation elements declerations
    – content
    – sidebar
    – footer

    and at the end
    form elements and errors

  62. Ross
    Permalink to comment#

    .class{
    border:1px solid;
    ass:big;
    eyes:blue;
    }

    Easy to discern.

    But, lots of scrolling.

    I’m kinda used to it.

  63. Permalink to comment#

    When developing I make mine as readable as possible, as I can always smush it down and remove line breaks when I output it at the end. Bracket goes with the object, and a tab before every style.

    #div {
    _____margin: 0 0 10px 0;
    _____padding: 5px;
    }
    
    #div2 {
    _____position: absolute;
    _____top: 0px;
    }

    etc.

  64. Permalink to comment#

    Single line, always has been, always will be. Apple does it too. Most of the big guys do :) Saves me time indenting and scrolling. Wouldn’t mind a tool that’d tidy up for me (put properties in alphabetical order), but with a bit of self-training I get to do the same.

  65. Justin
    Permalink to comment#

    Single-line Format with Indenting, no tabbing, often with variations:

    /*  -------------------------------------------------------- */
    /* - SECTION NAME ------------------------------ */
    .container {height:520px; overflow:auto; margin:10px; min-width:980px;}
    	.content {background:#fff; padding:4px;}
    	.footer {background:#fff; padding:12px 8px;}
    .longset {font-family:Verdana, Geneva, Arial, Helvetica, sans-serif; width:100%;
    	background:#000 url(http://cdn.css-tricks.com/images/global/bg_blugrad.gif) repeat-x top; font-size:12px;
    	line-height:1.5em; color:#000; padding-top:6px;}

    The last selector shows how I deal with really long attribute sets.

    Another variation I often use, typically when working on CSS created by someone else using the multi-line format:

    body {
    	font-family:Verdana, Geneva, Arial, Helvetica, sans-serif;
    	background:#000;
    	font-size:12px;
    	line-height:1.5em;
    	color:#000;
    	}
    	.container {
    		padding:6px;
    		margin:10px;
    		background:#fff;
    		}
    • I normally tab mine like the second example


      #id{
      color: red;
      }
      .class{
      font-size: 1.4em;
      }
      .class2{
      text-transform: lowercase;
      }

  66. Permalink to comment#

    Single line with indentation. Multiline css file takes around 1/5 of the width of the monitor, also, you have to v-scroll your a$$ off. But, at the end, it is a matter of personal preference.

  67. When writing CSS, I tend to have the selectors and such on one line, then having the properties on their own lines indented unless there are about four or less properties declared. I also like to have the braces at the beginning of the first declaration and the last.

    .toggle.button
    	{ width: 24px; height: 24px;
    	position: absolute; z-index: 2;
    	top: -12px;
    	left: -12px;
    	overflow: hidden;
    	background: url('images/toggle_normal.png') center no-repeat; }
    
    	.toggle.button a { display: block; width: 100%; height: 100%; text-indent: -9000em; } 
    
    
    .active { background: url('images/toggle_active.png') center no-repeat; }
    
  68. Permalink to comment#

    Wow, I’m surprised at the number of multi-liners out there, still.

    I’m mostly single-line, using multi-line only when it makes the most sense (custom class with a large number of declarations).

  69. docmiller
    Permalink to comment#

    I mostly use the multiline model.

    /* Name the section
    ------------------------------*/

    h1 {
    color: black; /* put a note why I did this */
    ...
    }

    For just one or two values I use the single line.
    .test {
    color: red;
    margin: 0 0 1em 1em; /* look section x */
    ...
    }

    /* next section
    -------------------------------------*/

  70. cjbates
    Permalink to comment#

    Some people get worked up about this and its ridiculous. Whatever helps you read your code, use it. But if you’re spending as much time formatting your code as you are writing it, you might want to re-think your life.

    For the record, I usually single line unless i have a bunch of declarations. Then I’ll use multi-line. I also add some comment blocks to divide major sections.

  71. Arch Focus
    Permalink to comment#

    I use a combination of multi and single line.
    Mostly single line but I really dislike horizontal scrolling so if there are more than about 5 argument and break them onto the next line.

    Also I often have numerous arguments for position and size and numerous arguments for background properties so I will break them up like that with position/size arguments on one line and background properties on another.

    It is far more compact and requires much less scrolling than full multiline. It also doesn’t cause horizontal scrolling (which I think is even worse than vertical scrolling). If you went single line but turned on wordwrap to avoid horizontal scrolling then you would end up with something about the same as I use anyway but you just wouldn’t have as much control over where exactly the lines break.

    I also section my css with big visible comment signs so I can scroll quickly and find what I’m looking for.

    /*----------------------------------*/
    /*------->> Globals <<------*/
    /*----------------------------------*/
    html, body {
    	height:100%; width:100%; text-align:center;
    	background-color:#FFF; color:#036;
    	font:normal normal normal 1em/150% Arial, Helvetica, sans-serif;
    	font-family: Arial, Helvetica, sans-serif;}
    .pagewrap_cs {
    	min-height:100%; width:100%; position:relative; text-align:center; min-width:760px; overflow:hidden;}
    td,th {
    	color:#036; font:normal normal normal 1em/1.5 Arial, Helvetica, sans-serif;}
    
    h1 {font-size: 2em; color: #036;}
    h2 {font-size: 1.8em; color: #036;}
    h3 {font-size: 1.8em; color: #036;}
    h4 {font-size: 1.6em; color: #036;}
    h5 {font-size: 1.4em; color: #006;}
    h6 {font-size: 1.2em; color: #666;}
  72. Scott
    Permalink to comment#

    I don’t see what it matters as long as everyone’s on the same page. Working with multiple people and them all having different styles of writing CSS is the only time I can see it being a problem. Also, mini-fying should make it a moot point once it’s on a production environment anyway :-)

  73. I prefer to use multi-line like most, but I group like objects on similar lines to save some space. For example:


    .col1 {
    float: left; margin: 2%; padding: 2%; width: 42%; /*This is my positioning line\*
    font-size: 1em; color: #333; /*This is my font properties line\*
    background: #ccc url() repeat-x; /*This is my decorative properties line\*
    }

    With certain elements you may have to use list-style-type, etc. in which case i normally include those on a separate line between positioning and font properties.

    Hopefully I make sense :o)

  74. Permalink to comment#

    Always multiline, and indented, so I know where I am, but when everything is ready, I usually compress it to the minimum possible with csstidy, you know why :)

    • Dkwad
      Permalink to comment#

      Here here,

      maintainability means I like the multiline format. I dont go in for indententing elements though.

      Great thing about csstidy is you can create a step in your deployment where all css is compressed on the fly.

  75. fjpoblam
    Permalink to comment#

    single-line; spaces squished out;

    declarations for “pure” html elements first; classes/other descendents within “pure” elements (showing differences);

    semantic divs at bottom;

    properties in alpha order

  76. I like short css sheets, so only hit the return key when I’m making a new selector.

  77. Felipe
    Permalink to comment#

    Until I read this poll yesterday I’ve always used multi-line with indents, but after reading some of the responses here i decided to give the single-line a try (with indenting), and I have officially changed over to it. Not having to scroll up and down constantly is really nice.

  78. Single line; no spaces and small comments. If the line becomes to long I sometimes use a single line break so I don’t have to scroll sideways.

    eg.

    /* = Ninja's protect my code. */
    .ninja{color:black;visibility:none;}

  79. Permalink to comment#

    Wow seems that a lot of people like doing things their own little way :-)
    I’m in the “I do multiline indented but also single line” camp. So when there is only one or two properties, they can go on a single line – but any more that, it becomes multiline and indented.

    I’ve heard a few people say that scrolling in small windows to edit CSS – (I’m looking at you WordPress!) – isn’t all that nice, but I personally prefer to scroll vertically than horizontally, it seems to me that if something is scrolled off the screen horizontally it’s easier to miss.

    I recently blogged about my own CSS formatting issues, basically if you need to work on someone elses CSS, you can use http://www.cleancss.com/ To both clean up and re-format the CSS for you.

  80. gregf
    Permalink to comment#

    I don’t format my css myself. I write it using tools like compass and sass which do the formating for me.

  81. Permalink to comment#

    I combine three approaches

    1- Multi-line formatting
    2- Indenting
    3- Alphabetical order

  82. I dont like the way you set up the poll, Chris :( the single line formats have 4 choices while the multi line have only two. Therefor the single line has a lot less chance of coming first :P I guess its not about winning though.

  83. Comibination of everything. ;)

  84. Linus
    Permalink to comment#

    Backgrounds and colors first, followed by positions/floats, sizes, margins and paddings, then fonts… and the rest


    #id {
    background: #eee;
    color: #333;
    min-width: 960px;
    width: 960px;
    min-height: 480px;
    overflow-y: scroll;
    border: 0px;
    margin: 0px;
    padding: 5px;
    font-family: 'Droid Sans', Helvetica, Arial, sans-serif;
    font-size: 1.4em;
    letter-spacing: -0.02em;
    line-height: 1.3;
    -ms-filter:"progid:DXImageTransform.Microsoft.Alpha(Opacity=80)";
    filter: alpha(opacity=80);
    opacity: 0.8;
    z-index: 20;
    }

  85. Straight line for everything, and I categories it with comments to start out, and three spaces after each section:

    /**** This is a section ****/
    h1 {}
    h1 a {}

  86. Permalink to comment#

    The main principles I follow while writing CSS code: readability and logical flow.

    The classic example of my code:


    .example
    {
    width: 400px;
    height: 25px;
    font: normal 15px/28px helvetica, tahoma, arial, sans-serif;
    color: #666;
    background-color: #f2f2f2;
    border-bottom: 1px solid #ccc;
    padding: 10px 10px 0;
    margin: 0 0 1px;
    }

    Putting { and } in new lines grants me a readability. Secondly, dimensional attributes are most important – priority number one. Secondly, typo and appearance. Finally – positioning and behavior among another HTML structures. Actually, I do not understand an alphabetic ordering, because it’s like having bananas, bread and dewberries, doughnuts in different shelves while it should be in this way: bread and doughnuts, dewberries and bananas.

    Anyway, it’s all about how your imagination works, have logic or not.

  87. Sathish
    Permalink to comment#

    I must say I’m very much messed up in this area, I multi-line all the time, if there more than 3 arguments.

    Otherwise its tabs tabs and tabs :D

This comment thread is closed. If you have important information to share, you can always contact me.

*May or may not contain any actual "CSS" or "Tricks".