<\/p>\n<\/p>\n
It\u2019s inevitable: the longer you work with CSS, the longer your CSS files will grow. And the longer your files get, the tougher it will be to find what you\u2019re looking for when you go back to edit your website\u2019s styles later on down the road. This is where CSS comments can really come in handy.<\/p>\n
The syntax is amazingly simple: You start a CSS comment with \/* and end them with *\/ \u2013 like so:<\/p>\n
\/* This is a CSS Comment. *\/\nbody {\n\tfont-size: 80%;\n}<\/pre>\nA single CSS comment can also span multiple lines, like this:<\/p>\n
\/* This CSS was written by Rob.\n He thinks of it as his own child, so\n you'd be best off asking permission\n to use it. ;)\n*\/\nbody {\n\tfont-size: 80%;\n}<\/pre>\nSo what are CSS comments good for? Well, in addition to identifying the creator of a CSS file (as shown above), you can also use your comments to keep your CSS more organized. For example, I use comments to organize my CSS into sections, like this:<\/p>\n
\/* Top navigational elements. *\/\nul#topnav {\n\tproperty: value; \n}\n\n\/* Main content area. *\/\n#content {\n\tproperty: value;\n}<\/pre>\nThis makes it much easier to come back though and add or remove values from a stylesheet later on.<\/p>\n
I also use comments to identify any \u201chacking\u201d I\u2019ve been forced to do.<\/p>\n
.column {\n\theight: 1%; \/* Makes IE behave itself. *\/\n}<\/pre>\nThat way, if the hack ever becomes unnecessary or causes a different problem down the line, it\u2019s that much easier to find it.<\/p>\n
What else do you use CSS comments for?<\/p>\n