It can be explained as removing the styling veil from the “source code” of the web, exposing the truth beneath. While no longer being eye-candy, the website should still look and work just fine. Unless you have used superficial styling to cover up some fundamental mistakes…
The next occasion will be different though, as I have recently moved from Symfony to Jekyll as my website engine. That means I can not do any server-side processing outside of the few times I rebuild the entire site.
So I had to rethink the solution.
The result is CSSNakedDay.js; the client-side style stripper!
onload event and, when triggered, removes all CSS from the page. It does so by first disabling all external stylesheets and then removing any inline styles. You do not even get to keep your undies.
Your site should be naked for the user on her April 9th, not depending on what timezone your server is in. Some current solutions works around this by nuding for a full 48 hours, just to be sure. With a client based solution we solve this the right way.
Doing these computations for every page load, all year around, is unnecessary work for your server. Offload it to the clients instead!
Stripping away external CSS files is easy but I have yet to see a server side solution remove inline styles, as CSSNakedDay.js does.
If you are on Jekyll or any other static side generator then you really do not have an option.