Remember: April 9 Is CSS Naked Day

Published on March 19, 2015 (↻ April 20, 2024), filed under (RSS feed for all categories).

This and many other posts are also available as a pretty, well-behaved ebook: On Web Development.

CSS Naked Day is coming up!

Why the excitement? Because CSS Naked Day is a magnificent custom; the magnificent custom to, on one day of the year, strip websites of all styling. It’s awesome because when we, web developers, have done our job, it takes pretty much one move of the finger to completely unstyle—undress—a website. Which shows not only the power of CSS, but also of HTML, and of Separation of Concerns.

(Dustin Diaz, the inventor of CSS Naked Day, has explained a bit more on the original CSS Naked Day site, and so has Taylor Satula then on the last CSS Naked Day site.)

To make sure this event doesn’t get forgotten I’ve decided to post this note here, but also to set up a reminder mailing list: css-naked-day@googlegroups.com. Please join.

It’s a reminder list for I just do a little countdown and point to whoever is organizing the main event (I’m not sure Taylor is doing it again this year, after Dustin had handed over). I’ll do enough to help keep the awesomeness alive. Forever—for I’ve always loved the idea behind CSS Naked Day.

Please join in, on CSS Naked Day 2015—and the Naked Days of the future!

Was this useful or interesting? Share (toot) this post, or support my work by buying one of my books (they’re affordable, and many receive updates). Thanks!

About Me

Jens Oliver Meiert, on September 30, 2021.

I’m Jens (long: Jens Oliver Meiert), and I’m a frontend engineering leader and tech author/publisher. I’ve worked as a technical lead for companies like Google and as an engineering manager for companies like Miro, I’m close to W3C and WHATWG, and I write and review books for O’Reilly and Frontend Dogma.

I love trying things, not only in web development (and engineering management), but also in other areas like philosophy. Here on meiert.com I share some of my views and experiences.

If you’d like to do me a favor, interpret charitably (I speak three languages, and they do collide), yet be critical and give feedback for me to fix issues, learn, and improve. Thank you!