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.
![fetch API]()
One of the worst kept secrets about AJAX on the web is that the underlying API for it, XMLHttpRequest, wasn't really made for what we've been using it for. We've done well to create elegant APIs around XHR but we know we can do better. Our effort to...
![5 Ways that CSS and JavaScript Interact That You May Not Know About]()
CSS and JavaScript: the lines seemingly get blurred by each browser release. They have always done a very different job but in the end they are both front-end technologies so they need do need to work closely. We have our .js files and our .css, but...
![Detect Vendor Prefix with JavaScript]()
Regardless of our position on vendor prefixes, we have to live with them and occasionally use them to make things work. These prefixes can be used in two formats: the CSS format (-moz-, as in -moz-element) and the JS format (navigator.mozApps). The awesome X-Tag project has...
![MooTools & Printing – Creating a Links Table of Contents]()
One detail we sometimes forget when considering print for websites is that the user cannot see the URLs of links when the page prints. While showing link URLs isn't always important, some websites could greatly benefit from doing so. This tutorial will show you...
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.