For the fourth year in a row, Dustin Diaz is bringing back CSS Naked Day. CSS Naked Day was brought about by Dustin as an effort to celebrate the goodness that is semantic markup and good document hierarchy.
The idea is this: for one day, each bit of CSS is removed from your website. For real. While the makeup has been removed, your website should remain proud. CSS Naked Day usually generates quite a bit of chatter, but there are plenty of designers who don’t know much about it.
The point of it all
Much of the (minimal) negative feedback about CSS Naked Day surrounds the concept that completely removing the style layer from a website will bring businesses to a screeching halt, turn clients into enemies, and generally wreak havoc on every website it touches. They’re missing the point.
We can safely assume that it wasn’t Dustin’s intention for shops to remove the style from client websites in celebration of CSS Naked Day. Instead, he’s trying to actively spread the word about the good things behind markup structure by enticing the Web design community to show that solid markup can indeed be a beautiful thing.
The idea behind CSS Naked Day is that you the designer remove the style layer from, say, your personal website. In doing so, you show the world that you truly know and understand what you’re doing under the hood and you make it look good. Your confidence in removing the CSS from your website is an act of community participation, not a hostile act against business.
Why I participate
I’ve participated in CSS Naked Day each year since its inception, and I hope Dustin continues the tradition for many years to come. I think it’s great to see that so many people appreciate the value of Web design, and I feel that CSS Naked Day helps bring us back to our roots for a few hours. All the while we’re spreading the words about semantic HTML to up-and-coming designers who are still wrapping their heads around the concepts and purpose of semantic markup.
I enjoy checking out the websites of participants and seeing what creative solutions others have implemented on one of the lowest levels we work. I check out nearly all the websites listed on the participant list and it’s great to see such an abundance of style-less documents for a short time. The worst part is not being able to view every site in the short window that is CSS Naked Day. The best part, though, is being able to easily make use of the website given that the style layer has been completely removed.
CSS Naked Day is a great way for a knowledgeable Web designer to get back to basics and be reminded of the fact that (X)HTML alone is an impressive markup language, allowing us to convey meaning on levels that many people will never see.
Will you participate this year?
CSS Naked Day has been around for years — what’s your track record? If you’ve participated before, do you plan on doing so again? If you haven’t, how come? If you’d like to find out the more technical details on participation, specifically how to implement a date check on your website to remove all of your CSS, there are a number of code snippets and plugins available on the official CSS Naked Day website.
Absolutely, although some people tell me that my site looks like it doesn’t have a stylesheet anyway 🙂
“Much of the (minimal) negative feedback about CSS Naked Day surrounds the concept that completely removing the style layer from a website will bring businesses to a screeching halt, turn clients into enemies, and generally wreak havoc on every website it touches. They’re missing the point.”
You say it is for personal websites – this is what the supports of CSS Naked Day say every year, and every year people respond with “you’re just preaching to the choir”. And this is where I stand within this self-promotion concept.
“The worst part is not being able to view every site in the short window that is CSS Naked Day.” — alt+shift+s (with the web developer toolbar) does me fine every single hour of every single day on any website I choose, I can even persist the feature while browsing the domain.
I think providing people with the correct tools and an idea of what to look for is much more beneficial than these back-patting promotional gimmicks. Although, it’s funny to see the amount of WordPress blogs on there, all using pretty much the same code.
Anyway, hope you have fun on the day. I’ll be browsing the other part of the web that day, with nice easy to read line-lengths, hierarchal typography and pretty graphics!
@Leon Paternoster: Glad to hear you’ll be participating!
@trovster: It’s good to hear from you! It’s been quite a long time since you’ve commented I thought you may have parted ways! I can absolutely see your point — at the end of the day the majority of people reading anything about CSS Naked Day are others who are participating.
You’re right, having a more focused game plan in displaying the benefits of semantic markup which has been abstracted from the style would definitely be more beneficial and I appreciate you taking the time to write up your thoughts.
I actually take part in the same practice as you by simply disabling the style for a site on my end (the client side), and now that I look back on it, that passage was terribly worded. I think it’s probably safe to say that designers will stick to their side of the fence persistently when it comes to an event such as this, as there are absolute pros and cons from both sides.
I’d hate to think of CSS Naked Day as a back-patting self promotional gimmick as I see it as more of a community gathering, but my opinion is no more valuable than anyone else’s, and I’m very thankful that instead of brushing off my article, you took time out of your day to express your thoughts! I hope to hear more from you soon.