# Another Website Redesign - CSS Naked Day Prep

2025-03-23 - [54] 1:3

If there's one thing I certainly like to do (possibly a little too much?), it's modify the look of my website! I think that's an issue with a lot of folks who enjoy playing around with HTML, CSS, and Javascript. This design change is, funny enough, to get rid of ALL CSS. I had already gotten rid of all Javascript quite a while back ago and very recently was surfing through some old websites and noticed one that had somewhat less CSS than I was already using.

April 9th is CSS Naked Day, where some websites decide to spend 50 hours (yupp, 50, in order to make sure everyone on Earth experiencing April 9th can experience CSS Naked Day) with absolutely 0 CSS. The CSS Naked Day website is linked below.

CSS Naked Day Website [HTTPS]

It's related to JS Naked Day, where websites spend April 24th with absolutely 0 Javascript, which I have spent quite a while participating in every single day, heh.

JS Naked Day Website [HTTPS]

To set myself up for CSS Naked Day, I have set my website to use absolutely no CSS. My site even uses the Content-Security-Policy of `style-src 'none'` now to block CSS, just as it also uses `script-src 'none'` to block Javascript and quite a lot of other content security policies to block other things, like form actions and frames.

A shame to officially participate in CSS Naked Day, I am required to have a github account... No thanks to that, but I'll still celebrate the spirit of the day, likely for an extended period of time!

In the process of setting up my website to use absolutely no CSS, I accidentally introduced a bug in my static HTML page generator that I will hopefully fix soon. It's a pretty minor bug, but it does mean that there will be an extra <br> tag after some link <a> tags if the original gemtext file contained 2 blank text lines after a link line.

## Consequences of Absolutely No CSS

If viewed on a small screen, images will not be scaled to fit the screen. Code blocks inside <pre> tags may also extend past the width of the screen. That means there may be a horizontal scroll bar if an image or <pre> tag is on the page. Others might be slightly annoyed with that, but I'm completely fine with that consequence.

This may impact printing as well, but I try to keep images and pre tags within reasonable sizes, usually about 600px to 800px wide for images and about 72 to 80 columns preformatted content. There are some exceptions, particularly with images, but I'm not too worried about that honestly. If someone REALLY needs to print out in those cases, they can shrink the size of the page they are printing or print in landscape mode.

## Contact/Reply

If you would like to reply to this post, feel free to send me an email.

Email: vi@vigrey.com [Email]
PGP Public Key [515F AD67 F931 0A2B 9B93 CE19 814F ECB1 A398 63CE]