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.
![7 Essential JavaScript Functions]()
I remember the early days of JavaScript where you needed a simple function for just about everything because the browser vendors implemented features differently, and not just edge features, basic features, like addEventListener and attachEvent. Times have changed but there are still a few functions each developer should...
![Write Simple, Elegant and Maintainable Media Queries with Sass]()
I spent a few months experimenting with different approaches for writing simple, elegant and maintainable media queries with Sass. Each solution had something that I really liked, but I couldn't find one that covered everything I needed to do, so I ventured into creating my...
![dat.gui: Exceptional JavaScript Interface Controller]()
We all love trusted JavaScript frameworks like MooTools, jQuery, and Dojo, but there's a big push toward using focused micro-frameworks for smaller purposes. Of course, there are positives and negatives to using them. Positives include smaller JS footprint (especially good for mobile) and less cruft, negatives...
![Detect DOM Node Insertions with JavaScript and CSS Animations]()
I work with an awesome cast of developers at Mozilla, and one of them in Daniel Buchner. Daniel's shared with me an awesome strategy for detecting when nodes have been injected into a parent node without using the deprecated DOM Events API.
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.