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.
![Write Better JavaScript with Promises]()
You've probably heard the talk around the water cooler about how promises are the future. All of the cool kids are using them, but you don't see what makes them so special. Can't you just use a callback? What's the big deal? In this article, we'll...
![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...
![Submit Button Enabling]()
"Enabling" you ask? Yes. We all know how to disable the submit upon form submission and the reasons for doing so, but what about re-enabling the submit button after an allotted amount of time. After all, what if the user presses the "stop"...
![CSS Fixed Positioning]()
When you want to keep an element in the same spot in the viewport no matter where on the page the user is, CSS's fixed-positioning functionality is what you need.
The CSS
Above we set our element 2% from both the top and right hand side of the...
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.