My Thoughts on CSS Naked Day
I've received numerous questions about this over the past two days so I might as well address it. As you probably know, this Wednesday was CSS Naked Day. CSS Naked Day's "official" website says the following about why you should do this:
The idea behind this event is to promote Web Standards. Plain and simple. This includes proper use of (x)html, semantic markup, a good hierarchy structure, and of course, a good 'ol play on words. It's time to show off your <body>.
While the idea is creative, I wasn't compelled to "expose" my website's <body>. I think the best way to appreciate XHTML, semantic markup, and Web Standards is to just do it. Truth be told, none of my readers want to come to my website and see an unstyled XHTML document. I'm sure advertisers would be thrilled with it too.
It's a really cool idea but it just wasn't practical for my blog.
![Chris Coyier’s Favorite CodePen Demos]()
David asked me if I'd be up for a guest post picking out some of my favorite Pens from CodePen. A daunting task! There are so many! I managed to pick a few though that have blown me away over the past few months. If you...
![CSS @supports]()
Feature detection via JavaScript is a client side best practice and for all the right reasons, but unfortunately that same functionality hasn't been available within CSS. What we end up doing is repeating the same properties multiple times with each browser prefix. Yuck. Another thing we...
![MooTools 1.2 OpenLinks Plugin]()
I often incorporate tools into my customers' websites that allow them to have some control over the content on their website. When doing so, I offer some tips to my clients to help them keep their website in good shape. One of the tips...
![Introducing MooTools Templated]()
One major problem with creating UI components with the MooTools JavaScript framework is that there isn't a great way of allowing customization of template and ease of node creation. As of today, there are two ways of creating:
new Element Madness
The first way to create UI-driven...
I have to agree with you – all it serves to do is alienate and confuse anyone visting your site who is unaware of the idea (which would be roughly everyone).
Every day is CSS Naked Day in a way. Anyone could just turn off styles with the Web Developer extension. Now to work on something similar for humans… ;)
@Eric: Agreed and AGREED!
Forget about the advertisers for one day. Give your readers more credit. @Phil may be confused by pure content but your average tech reader wouldn’t. @Eric is right we know how to turn off styles, but that just begs the question: Is your content be well formed enough to exist without css?
We `Developers` know how to turn off css but the adverage user wouldn’t know how too/or want too. So I disagree that ‘Anyone’ could do this. ‘Anyone with the knowledge’ could.