Comments on: Improving Your Process: CSS Techniques Part 1 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/ A resource for Web designers and developers to read about and discuss their craft. Wed, 28 Jul 2010 19:29:20 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Fear not. I Have Conquered IE6, and You Can Too - Monday By Noon http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-4753 Fear not. I Have Conquered IE6, and You Can Too - Monday By Noon Mon, 12 Jan 2009 06:52:11 +0000 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-4753 [...] I’ve said before, something I always keep in mind is to avoid box model inconsistencies. Find a way to prevent [...] [...] I’ve said before, something I always keep in mind is to avoid box model inconsistencies. Find a way to prevent [...]

]]> By: Improving Your Process: CSS Techniques Part 2 - Monday By Noon http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1200 Improving Your Process: CSS Techniques Part 2 - Monday By Noon Mon, 14 Jan 2008 15:04:22 +0000 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1200 [...] a year ago, I jotted down a few CSS techniques that I use day to day. Some tips included controlling browser defaults, avoiding box model headaches, [...] [...] a year ago, I jotted down a few CSS techniques that I use day to day. Some tips included controlling browser defaults, avoiding box model headaches, [...]

]]> By: Paul - Design Mancester http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1199 Paul - Design Mancester Sun, 06 Jan 2008 17:44:48 +0000 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1199 Johnathan, I like the header comments like this: /* Theme Name: Theme URI: Description: Version: Author: Author URI: */ I agree with you that it is better to avoid IE bugs than use hacks. Johnathan, I like the header comments like this:
/*
Theme Name:
Theme URI:
Description:
Version:
Author:
Author URI:
*/

I agree with you that it is better to avoid IE bugs than use hacks.

]]> By: Jonathan Christopher http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1198 Jonathan Christopher Fri, 04 Jan 2008 15:33:52 +0000 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1198 @Paul - Design Mancester: There are a number of ways I've seen people comment their CSS. At the end of the day it comes down to what's most useful to you. One thing I've seen from time to time is using a specific syntax (that you've come up with yourself) for finding particular areas of your stylesheet, i.e.: <code>/* !footer */</code> That way, after using your own namespaces, you're able to use the exclamation point as a bit of a flag for the top of a section in your CSS. You could use various characters to outline various sections of CSS based on your needs. Other types of commenting that I've used include blatant attention-getting, such as: <code>/* -------------------------------------------------------- SIDEBAR -------------------------------------------------------- */</code> Using comments such as these can help you to section your CSS to easily find a particular area when scrolling through the stylesheet. Sometimes, it's helpful to include some notes as reminders, especially if you <a href="http://mondaybynoon.com/2006/05/15/i-vote-conditional-comments/" rel="nofollow">use conditional comments</a>. It can help to jot down a note reminding you that this particular element has ties with another IE-specific stylesheet. I hope you find these notes helpful, but please be sure to inquire if you have any further questions, or if I've interpreted your request incorrectly. Thanks for taking the time to comment! @Paul – Design Mancester: There are a number of ways I’ve seen people comment their CSS. At the end of the day it comes down to what’s most useful to you.

One thing I’ve seen from time to time is using a specific syntax (that you’ve come up with yourself) for finding particular areas of your stylesheet, i.e.:

/* !footer */

That way, after using your own namespaces, you’re able to use the exclamation point as a bit of a flag for the top of a section in your CSS. You could use various characters to outline various sections of CSS based on your needs.

Other types of commenting that I’ve used include blatant attention-getting, such as:

/* --------------------------------------------------------

SIDEBAR

-------------------------------------------------------- */

Using comments such as these can help you to section your CSS to easily find a particular area when scrolling through the stylesheet.

Sometimes, it’s helpful to include some notes as reminders, especially if you use conditional comments. It can help to jot down a note reminding you that this particular element has ties with another IE-specific stylesheet.

I hope you find these notes helpful, but please be sure to inquire if you have any further questions, or if I’ve interpreted your request incorrectly. Thanks for taking the time to comment!

]]> By: Paul - Design Mancester http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1197 Paul - Design Mancester Fri, 04 Jan 2008 13:18:04 +0000 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1197 Jon, it would be good if you add a few examples of comments. I keep improving them in my CSS files and I would like to find how others deal with this issue. Jon, it would be good if you add a few examples of comments. I keep improving them in my CSS files and I would like to find how others deal with this issue.

]]> By: Year in Review: Highlights from 2007 - Monday By Noon http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1196 Year in Review: Highlights from 2007 - Monday By Noon Mon, 24 Dec 2007 15:24:01 +0000 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1196 [...] Improving Your Process: CSS Techniques Part 1 [...] [...] Improving Your Process: CSS Techniques Part 1 [...]

]]> By: A Semantic Breakdown of Restaurant Menus - Monday By Noon http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1195 A Semantic Breakdown of Restaurant Menus - Monday By Noon Mon, 14 May 2007 12:14:35 +0000 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1195 [...] the word about POSH in starting a sporadic series of articles on the subject, much like the ‘Improving your Process‘ series. In the articles I’ll take a real world example that will hopefully be found [...] [...] the word about POSH in starting a sporadic series of articles on the subject, much like the ‘Improving your Process‘ series. In the articles I’ll take a real world example that will hopefully be found [...]

]]> By: RobotZoo » Blog Archive » Improving Your Process: CSS Techniques Part 1 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1194 RobotZoo » Blog Archive » Improving Your Process: CSS Techniques Part 1 Fri, 23 Mar 2007 21:58:57 +0000 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1194 [...] More… [...] [...] More… [...]

]]> By: Jon http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1192 Jon Sat, 10 Mar 2007 15:16:29 +0000 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1192 @Brian: I could never work productively when splitting my CSS into separate files for typography, layout, colors, etc. It just didn't make sense to me. To change the appearance of a single element, it's very likely you'll have to open up two (or three!) files just to make the change. @Brian: I could never work productively when splitting my CSS into separate files for typography, layout, colors, etc. It just didn’t make sense to me. To change the appearance of a single element, it’s very likely you’ll have to open up two (or three!) files just to make the change.

]]> By: Brian http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1193 Brian Thu, 08 Mar 2007 18:58:38 +0000 http://mondaybynoon.com/2007/02/26/improving-your-process-css-techniques-part-1/#comment-1193 I tried splitting up my CSS files into layout/typography/colors/etc., but I found it too time consuming to be flipping back and forth between files as I coded. I prefer to keep everything in one well-commented file. Love the color glossary idea--I'm going to use that from now on. I tried splitting up my CSS files into layout/typography/colors/etc., but I found it too time consuming to be flipping back and forth between files as I coded. I prefer to keep everything in one well-commented file. Love the color glossary idea–I’m going to use that from now on.

]]>