Quickly create boxes with directional arrows.

> I could just generate the content on the body element:
>
> @media all and (min-width: 45em) {
> body:after {
> content: 'widescreen';
> display: none;
> }
> }
>
> It isn’t visible, but it is readable from JavaScript:
> var size = window.getComputedStyle(document.body,':after').getPropertyValue('content');
> And with that, I can choose whether or not to load some secondary content into the page depending on the value returned:
>
> if (size == 'widescreen') {
> // Load some more content.
> }
>
> Nice!

A cool little playground with some nifty ideas.

> Collect, test, and experiment with interface pattern pairings of CSS & HTML. Pears is an open source WordPress theme, enabling people like you to get your own pattern library up and running quickly.

> We are standing in a new age. We need to stop saying one thing, separation, and doing another, divergence. In the end we can pretend that the principle of separation is still relevant but it doesn’t support the current movement of the web. It doesn’t help standards, browser makers don’t care.

> Most importantly we need practical principles to guide us. So we know when to say yes or no to new features in CSS and HTML. So that we can keep one eye on the vendors and the other on the web’s future. We need to accept the fact that separation of structure, presentation and behavior is dead.

Nothing groundbreaking, but a nice reference.

For when you *really* need that drop shadow in every browser. (Not often, if ever.)

“A simple, lightweight approach”

I have been doing CSS for quite some time, yet still I found the section on CSS Specificity insightful. I have never seen it spelled out that well.