I'd use these rules-of-thumb for when :target is a good choice:
When a "state" is needed
When the jump-down behavior is acceptable
When it's acceptable to affect the browser history
esterday's post showed how to hack the :first-child pseudo-class into IE6 with jQuery and CSS. Continuing with that theme, today and tomorrow we'll show how to enable transparent PNG support in IE6
when a browser draws the borders, it draws them at angles. This technique takes advantage of that. One side of the border is colored for the color of the arrow, and the rest are transparent. Then you set the width of the border to something large
"If we set up a "ghost" element inside the parent that is 100% height, then we vertical-align: middle both that and the element to be centered, we get the same effect."
The list-style-position property defines where to position the list marker, and it accepts one of two values: "inside" or "outside". These are demonstrated below
Global and Section-Specific Sass Files Are just Table of Contents
In other words, no styles directly in them. Force yourself to keep all styles organized into component parts.
If you find yourself using a number other than 0 or 100% over and over, it likely deserves a variable.
List Vendor/Global Dependancies First, Then Author Dependancies, Then Patterns, Then Parts
In Deployment, Compile Compressed
Comments get stripped when compiling to compressed code, so there is no cost.
Partials are named _partial.scss
Variablize All Colors
Except perhaps white and black.
In your global stylesheet, @import a _shame.scss file last.